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 " + +# 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 d19f215e62..8f1fdb3f04 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -1,5 +1,6 @@ // For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: // https://github.com/microsoft/vscode-dev-containers/tree/v0.177.0/containers/javascript-node +// - { "name": "docs.github.com", "build": { 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/.dockerignore b/.dockerignore index bf645012d0..aa9b89a064 100644 --- a/.dockerignore +++ b/.dockerignore @@ -10,3 +10,5 @@ tests/ lib/rest/static/dereferenced # Folder is cloned during the preview + prod workflows, the assets are merged into other locations for use before the build docs-early-access/ +# During the preview deploy untrusted user code may be cloned into this directory +user-code/ diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 4c6ff3c4fd..f54c51ee4e 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -11,7 +11,6 @@ /script/ @github/docs-engineering /includes/ @github/docs-engineering /lib/search/popular-pages.json @github/docs-engineering -app.json @github/docs-engineering Dockerfile @github/docs-engineering package-lock.json @github/docs-engineering package.json @github/docs-engineering diff --git a/.github/actions-scripts/content-changes-table-comment.js b/.github/actions-scripts/content-changes-table-comment.js index 91a62cb95f..bb7258b957 100755 --- a/.github/actions-scripts/content-changes-table-comment.js +++ b/.github/actions-scripts/content-changes-table-comment.js @@ -36,7 +36,7 @@ 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 previewLink = `https://${APP_URL}/${fileUrl}` + const previewLink = `${APP_URL}/${fileUrl}` const productionLink = `https://docs.github.com/${fileUrl}` let markdownLine = '' diff --git a/.github/actions-scripts/get-preview-app-info.sh b/.github/actions-scripts/get-preview-app-info.sh index e7f9f87366..f48c25ff10 100755 --- a/.github/actions-scripts/get-preview-app-info.sh +++ b/.github/actions-scripts/get-preview-app-info.sh @@ -10,9 +10,10 @@ [[ -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; } +[[ -z $APP_NAME_SEED ]] && { echo "Missing APP_NAME_SEED. Exiting."; exit 1; } -# Number of resource groups that we use to split preview envs across -PREVIEW_ENV_RESOURCE_GROUPS=4 +PREVIEW_ENV_LOCATION="eastus" +echo "PREVIEW_ENV_LOCATION=${PREVIEW_ENV_LOCATION}" >> $GITHUB_ENV REPO_NAME="${GITHUB_REPOSITORY#*\/}" echo "REPO_NAME=${REPO_NAME}" >> $GITHUB_ENV @@ -20,22 +21,17 @@ 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_BASE="${REPO_NAME}-preview-${PR_NUMBER}" +echo "APP_NAME_BASE=${APP_NAME_BASE}" >> $GITHUB_ENV -APP_NAME_SHORT="${REPO_NAME}-preview-${PR_NUMBER}" -echo "APP_NAME_SHORT=${APP_NAME_SHORT}" >> $GITHUB_ENV +# pseudo random string so guessing a preview env URL is more difficult +APP_SHA=$(echo -n "${APP_NAME_SEED}-${APP_NAME_BASE}" | sha1sum | cut -c1-6) + +APP_NAME="${APP_NAME_BASE}-${APP_SHA}" +echo "APP_NAME=${APP_NAME}" >> $GITHUB_ENV + +APP_URL="https://${APP_NAME}.${PREVIEW_ENV_LOCATION}.azurecontainer.io" +echo "APP_URL=${APP_URL}" >> $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/actions-scripts/prod-deploy.js b/.github/actions-scripts/prod-deploy.js deleted file mode 100755 index 387e1397be..0000000000 --- a/.github/actions-scripts/prod-deploy.js +++ /dev/null @@ -1,51 +0,0 @@ -#!/usr/bin/env node - -import getOctokit from '../../script/helpers/github.js' -import deployToProduction from '../../script/deployment/deploy-to-production.js' - -const { - GITHUB_TOKEN, - HEROKU_API_TOKEN, - HEROKU_PRODUCTION_APP_NAME, - SOURCE_BLOB_URL, - DELAY_FOR_PREBOOT, - RUN_ID, -} = 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!') -} - -// 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!') -} - -if (!RUN_ID) { - throw new Error('$RUN_ID not set') -} - -// This helper uses the `GITHUB_TOKEN` implicitly! -// We're using our usual version of Octokit vs. the provided `github` -// instance to avoid versioning discrepancies. -const octokit = getOctokit() - -try { - await deployToProduction({ - octokit, - includeDelayForPreboot: DELAY_FOR_PREBOOT !== 'false', - // These parameters will ONLY be set by Actions - sourceBlobUrl: SOURCE_BLOB_URL, - runId: RUN_ID, - }) -} catch (error) { - console.error(`Failed to deploy to production: ${error.message}`) - console.error(error) - throw error -} diff --git a/.github/actions-scripts/prune-for-preview-env.sh b/.github/actions-scripts/prune-for-preview-env.sh index 6126c13b7e..ccad39c271 100755 --- a/.github/actions-scripts/prune-for-preview-env.sh +++ b/.github/actions-scripts/prune-for-preview-env.sh @@ -20,5 +20,4 @@ mkdir translations # front-matter will be at play. # These static redirects json files are notoriously large echo '[]' > lib/redirects/static/archived-frontmatter-fallbacks.json -echo '{}' > lib/redirects/static/developer.json echo '{}' > lib/redirects/static/archived-redirects-from-213-to-217.json diff --git a/.github/actions-scripts/staging-commit-status-success.js b/.github/actions-scripts/staging-commit-status-success.js deleted file mode 100755 index e7e1a6ba97..0000000000 --- a/.github/actions-scripts/staging-commit-status-success.js +++ /dev/null @@ -1,42 +0,0 @@ -#!/usr/bin/env node - -import * as github from '@actions/github' - -import getOctokit from '../../script/helpers/github.js' - -const { GITHUB_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!') -} - -// This helper uses the `GITHUB_TOKEN` implicitly! -// We're using our usual version of Octokit vs. the provided `github` -// instance to avoid versioning discrepancies. -const octokit = getOctokit() - -const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env -if (!CONTEXT_NAME) { - throw new Error('$CONTEXT_NAME not set') -} -if (!ACTIONS_RUN_LOG) { - throw new Error('$ACTIONS_RUN_LOG not set') -} -if (!HEAD_SHA) { - throw new Error('$HEAD_SHA not set') -} - -const { context } = github -const owner = context.repo.owner -const repo = context.payload.repository.name - -await octokit.repos.createCommitStatus({ - owner, - repo, - sha: HEAD_SHA, - context: CONTEXT_NAME, - state: 'success', - description: 'Successfully deployed! See logs.', - target_url: ACTIONS_RUN_LOG, -}) diff --git a/.github/actions-scripts/staging-deploy.js b/.github/actions-scripts/staging-deploy.js deleted file mode 100755 index 26dadc4157..0000000000 --- a/.github/actions-scripts/staging-deploy.js +++ /dev/null @@ -1,55 +0,0 @@ -#!/usr/bin/env node - -import parsePrUrl from '../../script/deployment/parse-pr-url.js' -import getOctokit from '../../script/helpers/github.js' -import deployToStaging from '../../script/deployment/deploy-to-staging.js' - -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!') -} - -// This helper uses the `GITHUB_TOKEN` implicitly! -// We're using our usual version of Octokit vs. the provided `github` -// instance to avoid versioning discrepancies. -const octokit = getOctokit() - -const { RUN_ID, PR_URL, SOURCE_BLOB_URL } = process.env -if (!RUN_ID) { - throw new Error('$RUN_ID not set') -} -if (!PR_URL) { - throw new Error('$PR_URL not set') -} -if (!SOURCE_BLOB_URL) { - throw new Error('$SOURCE_BLOB_URL not set') -} - -const { owner, repo, pullNumber } = parsePrUrl(PR_URL) -if (!owner || !repo || !pullNumber) { - throw new Error( - `'pullRequestUrl' input must match URL format 'https://github.com/github/(docs|docs-internal)/pull/123' but was '${PR_URL}'` - ) -} - -const { data: pullRequest } = await octokit.pulls.get({ - owner, - repo, - pull_number: pullNumber, -}) - -await deployToStaging({ - octokit, - pullRequest, - forceRebuild: false, - // These parameters will ONLY be set by Actions - sourceBlobUrl: SOURCE_BLOB_URL, - runId: RUN_ID, -}) diff --git a/.github/workflows/azure-preview-env-deploy.yml b/.github/workflows/azure-preview-env-deploy.yml index 2a54474359..eb0d0ef153 100644 --- a/.github/workflows/azure-preview-env-deploy.yml +++ b/.github/workflows/azure-preview-env-deploy.yml @@ -1,12 +1,13 @@ 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 +# **What it does**: Build and deploy an Azure preview environment for this PR +# **Why we have it**: It's our preview environment deploy mechanism, to docs-internal and docs public repo # **Who does it impact**: All contributors. -# This whole workflow is only guaranteed to be secure in the *private -# repo* and because we repo-sync these files over the to the public one, -# IT'S IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs-internal! +# !!! +# ! This worflow has access to secrets, runs in the public repository, and clones untrusted user code. +# ! Modify with extreme caution +# !!! on: # The advantage of 'pull_request' over 'pull_request_target' is that we @@ -15,13 +16,17 @@ on: # From a security point of view, its arguably safer this way because # unlike 'pull_request_target', these only have secrets if the pull # request creator has permission to access secrets. - pull_request: + pull_request_target: workflow_dispatch: inputs: PR_NUMBER: description: 'PR Number' type: string required: true + COMMIT_REF: + description: 'The commit SHA to build' + type: string + required: true permissions: contents: read @@ -34,18 +39,23 @@ concurrency: jobs: build-and-deploy-azure-preview: - if: ${{ github.repository == 'github/docs-internal' }} 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 }} + # The environment variable is computer later in this job in + # the "Get preview app info" step. + # That script sets environment variables which is used by Actions + # to link a PR to a list of environments later. + url: ${{ env.APP_URL }} env: 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' }} + COMMIT_REF: ${{ github.event.pull_request.head.sha || github.event.inputs.COMMIT_REF }} + BRANCH_NAME: ${{ github.head_ref || github.ref_name }} + IS_INTERNAL_BUILD: ${{ github.repository == 'github/docs-internal' }} + # This may also run in forked repositories, not just 'github/docs' + IS_PUBLIC_BUILD: ${{ github.repository != 'github/docs-internal' }} steps: - name: 'Az CLI login' @@ -57,16 +67,25 @@ jobs: uses: azure/docker-login@81744f9799e7eaa418697cb168452a2882ae844a with: login-server: ${{ secrets.NONPROD_REGISTRY_SERVER }} - username: ${{ env.NONPROD_REGISTRY_USERNAME }} + username: ${{ secrets.NONPROD_REGISTRY_USERNAME }} password: ${{ secrets.NONPROD_REGISTRY_PASSWORD }} - name: Set up Docker Buildx uses: docker/setup-buildx-action@94ab11c41e45d028884a99163086648e898eed25 - - name: Check out repo + - if: ${{ env.IS_PUBLIC_BUILD == 'true' }} + name: Check out main branch uses: actions/checkout@1e204e9a9253d643386038d443f96446fa156a97 with: - ref: ${{ github.event.pull_request.head.sha }} + ref: 'main' + persist-credentials: 'false' + lfs: 'true' + + - if: ${{ env.IS_INTERNAL_BUILD == 'true' }} + name: Check out PR code + uses: actions/checkout@1e204e9a9253d643386038d443f96446fa156a97 + with: + ref: ${{ env.COMMIT_REF }} # To prevent issues with cloning early access content later persist-credentials: 'false' lfs: 'true' @@ -75,19 +94,21 @@ jobs: run: git lfs checkout - name: Get preview app info + env: + APP_NAME_SEED: ${{ secrets.PREVIEW_ENV_NAME_SEED }} 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 + echo "DOCKER_IMAGE=${{ secrets.NONPROD_REGISTRY_SERVER }}/${IMAGE_REPO}:${{ env.COMMIT_REF }}-${{ github.run_number }}-${{ github.run_attempt }}" >> $GITHUB_ENV - - if: ${{ env.ENABLE_EARLY_ACCESS }} + - if: ${{ env.IS_INTERNAL_BUILD == 'true' }} name: Determine which docs-early-access branch to clone id: 'check-early-access' uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d env: - BRANCH_NAME: ${{ github.head_ref || github.ref_name }} + BRANCH_NAME: ${{ env.BRANCH_NAME }} with: github-token: ${{ secrets.DOCUBOT_REPO_PAT }} result-encoding: string @@ -112,7 +133,7 @@ jobs: return 'main' } - - if: ${{ env.ENABLE_EARLY_ACCESS }} + - if: ${{ env.IS_INTERNAL_BUILD == 'true' }} name: Clone docs-early-access uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 with: @@ -121,10 +142,27 @@ jobs: path: docs-early-access ref: ${{ steps.check-early-access.outputs.result }} - - if: ${{ env.ENABLE_EARLY_ACCESS }} + - if: ${{ env.IS_INTERNAL_BUILD == 'true' }} name: Merge docs-early-access repo's folders run: .github/actions-scripts/merge-early-access.sh + - if: ${{ env.IS_PUBLIC_BUILD == 'true' }} + name: Check out user code to temp directory + uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 + with: + path: ./user-code + ref: ${{ env.COMMIT_REF }} + + # Move acceptable user changes into our main branch checkout + - if: ${{ env.IS_PUBLIC_BUILD == 'true' }} + name: Move acceptable user changes + run: | + # Make sure recursive path expansion is enabled + shopt -s globstar + rsync -rptovR ./user-code/content/./**/*.md ./content + rsync -rptovR ./user-code/assets/./**/*.png ./assets + rsync -rptovR ./user-code/data/./**/*.{yml,md} ./data + # In addition to making the final image smaller, we also save time by not sending unnecessary files to the docker build context - name: 'Prune for preview env' run: .github/actions-scripts/prune-for-preview-env.sh @@ -144,7 +182,7 @@ jobs: # Succeed despite any non-zero exit code (e.g. if there is no deployment to cancel) - name: 'Cancel any existing deployments for this PR' run: | - az deployment group cancel --name ${{ env.DEPLOYMENT_NAME }} -g ${{ env.RESOURCE_GROUP }} || true + az deployment group cancel --name ${{ env.DEPLOYMENT_NAME }} -g ${{ secrets.PREVIEW_ENV_RESOURCE_GROUP }} || true # Deploy ARM template is idempotent # Note: once the resources exist the image tag must change for a new deployment to occur (the image tag includes workflow run number, run attempt, as well as sha) @@ -152,15 +190,18 @@ jobs: id: deploy uses: azure/arm-deploy@841b12551939c88af8f6df767c24c38a5620fd0d with: - resourceGroupName: ${{ env.RESOURCE_GROUP }} + resourceGroupName: ${{ secrets.PREVIEW_ENV_RESOURCE_GROUP }} subscriptionId: ${{ secrets.NONPROD_SUBSCRIPTION_ID }} template: ./azure-preview-env-template.json deploymentName: ${{ env.DEPLOYMENT_NAME }} - parameters: appName="${{ env.APP_NAME_SHORT }}" - location="${{ env.APP_LOCATION }}" - linuxFxVersion="DOCKER|${{ env.DOCKER_IMAGE }}" - dockerRegistryUrl="https://${{ secrets.NONPROD_REGISTRY_SERVER }}" - dockerRegistryUsername="${{ env.NONPROD_REGISTRY_USERNAME }}" + parameters: appName="${{ env.APP_NAME }}" + location="${{ env.PREVIEW_ENV_LOCATION }}" + containerImage="${{ env.DOCKER_IMAGE }}" + dockerRegistryUrl="${{ secrets.NONPROD_REGISTRY_SERVER }}" + dockerRegistryUsername="${{ secrets.NONPROD_REGISTRY_USERNAME }}" dockerRegistryPassword="${{ secrets.NONPROD_REGISTRY_PASSWORD }}" - - - run: echo ${{ steps.deploy.outputs.defaultHostName }} + storageAccountName="${{ secrets.AZURE_STORAGE_ACCOUNT_NAME }}" + storageAccountKey="${{ secrets.AZURE_STORAGE_ACCOUNT_KEY }}" + # this shows warnings in the github actions console, because the flag is passed through a validation run, + # but it *is* functional during the actual execution + additionalArguments: --no-wait diff --git a/.github/workflows/azure-preview-env-destroy.yml b/.github/workflows/azure-preview-env-destroy.yml index d9fe2c5a5a..94463d846f 100644 --- a/.github/workflows/azure-preview-env-destroy.yml +++ b/.github/workflows/azure-preview-env-destroy.yml @@ -5,7 +5,7 @@ name: Azure - Destroy Preview Env # **Who does it impact**: All contributors. on: - pull_request: + pull_request_target: types: - closed - locked @@ -16,15 +16,16 @@ on: type: string required: true +permissions: + contents: read + jobs: destory-azure-preview-env: name: Destroy - if: ${{ github.repository == 'github/docs-internal' }} runs-on: ubuntu-latest timeout-minutes: 5 env: PR_NUMBER: ${{ github.event.number || github.event.inputs.PR_NUMBER }} - NONPROD_REGISTRY_NAME: ghdocs steps: - name: 'Az CLI login' @@ -37,28 +38,29 @@ jobs: - name: Get preview app info env: - FULL_APP_INFO: 1 + APP_NAME_SEED: ${{ secrets.PREVIEW_ENV_NAME_SEED }} 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 + az deployment group cancel --name ${{ env.DEPLOYMENT_NAME }} -g ${{ secrets.PREVIEW_ENV_RESOURCE_GROUP }} || true # 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 ${{ env.APP_NAME_FULL }} -g ${{ env.RESOURCE_GROUP }} + az container delete -n ${{ env.APP_NAME }} -g ${{ secrets.PREVIEW_ENV_RESOURCE_GROUP }} -y # 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 - name: 'Untag all docker images for this PR' run: | - az acr repository delete -n ${{ env.NONPROD_REGISTRY_NAME }} --repository ${{ env.IMAGE_REPO }} -y || true + az acr repository delete -n ${{ secrets.NONPROD_REGISTRY_NAME }} --repository ${{ env.IMAGE_REPO }} -y || true # Remove all GitHub deployments from this environment and remove the environment - uses: strumwolf/delete-deployment-environment@45c821e46baa405e25410700fe2e9643929706a0 with: + # The token provided by the workflow does not have the permissions to delete created environments token: ${{ secrets.DOCUBOT_REPO_PAT }} environment: preview-env-${{ env.PR_NUMBER }} diff --git a/.github/workflows/content-changes-table-comment.yml b/.github/workflows/content-changes-table-comment.yml index 8b9127dec9..798fe8a0da 100644 --- a/.github/workflows/content-changes-table-comment.yml +++ b/.github/workflows/content-changes-table-comment.yml @@ -48,17 +48,12 @@ jobs: 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 + APP_NAME_SEED: ${{ secrets.PREVIEW_ENV_NAME_SEED }} run: .github/actions-scripts/get-preview-app-info.sh - name: Setup Node diff --git a/.github/workflows/hubber-contribution-help.yml b/.github/workflows/hubber-contribution-help.yml index 8f84d851e8..7aa4d0d7f4 100644 --- a/.github/workflows/hubber-contribution-help.yml +++ b/.github/workflows/hubber-contribution-help.yml @@ -41,7 +41,7 @@ jobs: run: | gh pr comment $PR --body "Thanks so much for opening this PR and contributing to GitHub Docs! - - When you're ready for the Docs team to review this PR, apply the **ready-for-doc-review** label and your PR will be added to the [Docs Content review board](https://github.com/orgs/github/memexes/901?layout=table&groupedBy%5BcolumnId%5D=11024). **Please factor in at least 72 hours for a review, even longer if this is a substantial change.** + - When you're ready for the Docs team to review this PR, request a review by *docs-content* and your PR will be added to the [Docs Content review board](https://github.com/orgs/github/memexes/901?layout=table&groupedBy%5BcolumnId%5D=11024). **Please factor in at least 72 hours for a review, even longer if this is a substantial change.** - If this is a major update to the docs, you might want to go back and open an [issue](https://github.com/github/docs-content/issues/new/choose) to ensure we've covered all areas of the docs in these updates. Not doing so may result in delays or inaccurate documentation." env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/main-preview-docker-cache.yml b/.github/workflows/main-preview-docker-cache.yml index 92bebd90cc..a42239c1f1 100644 --- a/.github/workflows/main-preview-docker-cache.yml +++ b/.github/workflows/main-preview-docker-cache.yml @@ -24,8 +24,6 @@ jobs: timeout-minutes: 15 env: ENABLE_EARLY_ACCESS: ${{ github.repository == 'github/docs-internal' }} - NONPROD_REGISTRY_USERNAME: ghdocs - NONPROD_REGISTRY_NAME: ghdocs DOCKER_IMAGE_CACHE_REF: ${{ secrets.NONPROD_REGISTRY_SERVER }}/${{ github.repository }}:main-preview steps: @@ -38,7 +36,7 @@ jobs: uses: azure/docker-login@81744f9799e7eaa418697cb168452a2882ae844a with: login-server: ${{ secrets.NONPROD_REGISTRY_SERVER }} - username: ${{ env.NONPROD_REGISTRY_USERNAME }} + username: ${{ secrets.NONPROD_REGISTRY_USERNAME }} password: ${{ secrets.NONPROD_REGISTRY_PASSWORD }} - name: Set up Docker Buildx diff --git a/.github/workflows/optimize-images.yml b/.github/workflows/optimize-images.yml index 9abe9bb34b..7318444b4e 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" --reviewer "@github/docs-engineering" + gh pr create --title "Optimize images" --body "Optimize images" --reviewer "github/docs-engineering" env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/ping-staging-apps.yml b/.github/workflows/ping-staging-apps.yml deleted file mode 100644 index b5654ff1e2..0000000000 --- a/.github/workflows/ping-staging-apps.yml +++ /dev/null @@ -1,31 +0,0 @@ -name: Ping staging apps - -# **What it does**: This keeps our staging applications from automatically spinning down. -# **Why we have it**: Staging applications can hiberate without use. -# **Who does it impact**: Anyone with a pull request in docs-internal. - -on: - schedule: - - cron: '10,30,50 * * * *' # every twenty minutes - -permissions: - contents: read - -jobs: - ping_staging_apps: - name: Ping - if: github.repository == 'github/docs-internal' - runs-on: ubuntu-latest - env: - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - steps: - - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - name: npm ci - run: npm ci - - name: Run script - run: script/ping-staging-apps.js diff --git a/.github/workflows/prod-build-deploy-azure.yml b/.github/workflows/prod-build-deploy-azure.yml index 805cb6a6e6..eb53eb61bd 100644 --- a/.github/workflows/prod-build-deploy-azure.yml +++ b/.github/workflows/prod-build-deploy-azure.yml @@ -90,12 +90,12 @@ jobs: run: | sed 's|#{IMAGE}#|${{ env.DOCKER_IMAGE }}|g' docker-compose.prod.tmpl.yaml > docker-compose.prod.yaml - - name: 'Apply updated docker-compose.prod.yaml config to preview slot' + - name: 'Apply updated docker-compose.prod.yaml config to staging slot' run: | - az webapp config container set --multicontainer-config-type COMPOSE --multicontainer-config-file docker-compose.prod.yaml --slot preview -n ghdocs-prod -g docs-prod + az webapp config container set --multicontainer-config-type COMPOSE --multicontainer-config-file docker-compose.prod.yaml --slot staging -n ghdocs-prod -g docs-prod - # Watch preview slot instances to see when all the instances are ready - - name: Check that preview slot is ready + # Watch staging slot instances to see when all the instances are ready + - name: Check that staging slot is ready uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d env: CHECK_INTERVAL: 10000 @@ -115,7 +115,7 @@ jobs: let hasStopped = false const waitDuration = parseInt(process.env.CHECK_INTERVAL, 10) || 10000 async function doCheck() { - const states = getStatesForSlot('preview') + const states = getStatesForSlot('staging') console.log(`Instance states:`, states) // We must wait until at-least 1 instance has STOPPED to know we're looking at the "next" deployment and not the "previous" one @@ -136,10 +136,10 @@ jobs: doCheck() - # TODO - make a request to verify the preview app version aligns with *this* github action workflow commit sha - - name: 'Swap preview slot to production' + # TODO - make a request to verify the staging app version aligns with *this* github action workflow commit sha + - name: 'Swap staging slot to production' run: | - az webapp deployment slot swap --slot preview --target-slot production -n ghdocs-prod -g docs-prod + az webapp deployment slot swap --slot staging --target-slot production -n ghdocs-prod -g docs-prod - name: Purge Fastly edge cache env: diff --git a/.github/workflows/prod-build-deploy.yml b/.github/workflows/prod-build-deploy.yml deleted file mode 100644 index 31094bf7db..0000000000 --- a/.github/workflows/prod-build-deploy.yml +++ /dev/null @@ -1,199 +0,0 @@ -name: Production - Build and Deploy - -# **What it does**: Builds and deploys the default branch to production -# **Why we have it**: To enable us to deploy the latest to production whenever necessary rather than relying on PR merges. -# **Who does it impact**: All contributors. - -on: - push: - branches: - - main - workflow_dispatch: - -permissions: - contents: read - deployments: write - -# This allows a subsequently queued workflow run to take priority over -# previously queued runs but NOT interrupt currently executing runs -concurrency: - group: '${{ github.workflow }}' - cancel-in-progress: false - -jobs: - build-and-deploy: - if: ${{ github.repository == 'github/docs-internal'}} - runs-on: ubuntu-latest - timeout-minutes: 15 - steps: - - name: Check out repo - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - with: - persist-credentials: 'false' - lfs: 'true' - - - name: Check out LFS objects - run: git lfs checkout - - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - # Required for `npm pkg ...` command support - - name: Update to npm@^7.20.0 - run: npm install --global npm@^7.20.0 - - - name: Install dependencies - run: npm ci - - - name: Clone early access - run: node script/early-access/clone-for-build.js - env: - DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }} - GIT_BRANCH: main - - - name: Cache nextjs build - uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed - with: - path: .next/cache - key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }} - - - name: Build - run: npm run build - - - name: Remove development-only dependencies - run: npm prune --production - - - name: Remove all npm scripts - run: npm pkg delete scripts - - - name: Set npm script for Heroku build to noop - run: npm set-script heroku-postbuild "echo 'Application was pre-built!'" - - - name: Create a gzipped archive - run: | - tar -cz --file=app.tar.gz \ - node_modules/ \ - .next/ \ - assets/ \ - content/ \ - data/ \ - includes/ \ - lib/ \ - middleware/ \ - translations/ \ - server.mjs \ - package*.json \ - .npmrc \ - feature-flags.json \ - next.config.js \ - app.json \ - Procfile - - - name: Install the development dependencies again - run: npm install - - - name: Create a Heroku build source - id: build-source - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - with: - script: | - const { owner, repo } = context.repo - - if (owner !== 'github') { - throw new Error(`Repository owner must be 'github' but was: ${owner}`) - } - if (repo !== 'docs-internal') { - throw new Error(`Repository name must be 'docs-internal' but was: ${repo}`) - } - - const Heroku = require('heroku-client') - const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) - - try { - const { source_blob: sourceBlob } = await heroku.post('/sources') - const { put_url: uploadUrl, get_url: downloadUrl } = sourceBlob - - core.setOutput('upload_url', uploadUrl) - core.setOutput('download_url', downloadUrl) - } catch (error) { - if (error.statusCode === 503) { - console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/') - } - throw error - } - - # See: https://devcenter.heroku.com/articles/build-and-release-using-the-api#sources-endpoint - - name: Upload to the Heroku build source - env: - UPLOAD_URL: ${{ steps.build-source.outputs.upload_url }} - run: | - curl "$UPLOAD_URL" \ - -X PUT \ - -H 'Content-Type:' \ - --data-binary @app.tar.gz - - - name: Deploy - id: deploy - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - HEROKU_PRODUCTION_APP_NAME: ${{ secrets.HEROKU_PRODUCTION_APP_NAME }} - HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }} - HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }} - SOURCE_BLOB_URL: ${{ steps.build-source.outputs.download_url }} - DELAY_FOR_PREBOOT: 'true' - ALLOWED_POLLING_FAILURES_PER_PHASE: '15' - RUN_ID: ${{ github.run_id }} - run: .github/actions-scripts/prod-deploy.js - - - name: Mark the deployment as inactive if timed out - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - if: ${{ steps.deploy.outcome == 'cancelled' }} - env: - DEPLOYMENT_ID: ${{ steps.deploy.outputs.deploymentId }} - LOG_URL: ${{ steps.deploy.outputs.logUrl }} - with: - script: | - const { DEPLOYMENT_ID, LOG_URL } = process.env - const { owner, repo } = context.repo - - if (!DEPLOYMENT_ID) { - throw new Error('A deployment wasn't created before a timeout occurred!') - } - - await github.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: DEPLOYMENT_ID, - state: 'error', - description: 'The deployment step timed out. See workflow logs.', - log_url: LOG_URL, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - console.log('⏲️ Deployment status: error - The deployment timed out...') - - # - name: Purge Fastly edge cache - # env: - # FASTLY_TOKEN: ${{ secrets.FASTLY_TOKEN }} - # FASTLY_SERVICE_ID: ${{ secrets.FASTLY_SERVICE_ID }} - # FASTLY_SURROGATE_KEY: 'every-deployment' - # run: .github/actions-scripts/purge-fastly-edge-cache.js - - - name: Send Slack notification if workflow failed - uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 - if: ${{ failure() }} - with: - channel: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }} - bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} - color: failure - text: Production deployment failed at commit ${{ github.sha }}. See https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }} diff --git a/.github/workflows/ready-for-doc-review.yml b/.github/workflows/ready-for-doc-review.yml index 6959b98158..34a4c006fa 100644 --- a/.github/workflows/ready-for-doc-review.yml +++ b/.github/workflows/ready-for-doc-review.yml @@ -1,12 +1,12 @@ name: Ready for docs-content review -# **What it does**: Adds pull requests in the docs-internal repository to the docs-content review board when the "ready-for-doc-review" label is added +# **What it does**: Adds pull requests in the docs-internal repository to the docs-content review board when the "ready-for-doc-review" label is added or when a review by docs-content is requested # **Why we have it**: So that other GitHub teams can easily request reviews from the docs-content team, and so that writers can see when a PR is ready for review # **Who does it impact**: Writers working in the docs-internal repository on: pull_request_target: - types: [labeled] + types: [labeled, review_requested] permissions: contents: read @@ -14,7 +14,9 @@ permissions: jobs: request_doc_review: name: Request a review from the docs-content team - if: github.event.label.name == 'ready-for-doc-review' && github.repository == 'github/docs-internal' + if: >- + github.repository == 'github/docs-internal' && + (github.event.label.name == 'ready-for-doc-review' || github.event.requested_team.name == 'docs-content') runs-on: ubuntu-latest steps: - name: Check out repo content diff --git a/.github/workflows/remove-stale-staging-resources.yml b/.github/workflows/remove-stale-staging-resources.yml deleted file mode 100644 index 5375869132..0000000000 --- a/.github/workflows/remove-stale-staging-resources.yml +++ /dev/null @@ -1,69 +0,0 @@ -name: Remove stale staging resources - -# **What it does**: -# This cleans up any rogue staging applications and environments that outlasted -# the closure of their corresponding pull requests. -# **Why we have it**: -# Staging applications and environments should be destroyed after their -# corresponding pull request is closed or merged, especially to save money spent -# on Heroku App staging deployments for closed PRs. -# **Who does it impact**: -# Anyone with a closed, spammy, or deleted pull request in docs or docs-internal. - -on: - schedule: - - cron: '15,45 * * * *' # every thirty minutes at :15 and :45 - -permissions: - actions: read - contents: read - deployments: write - pull-requests: write - -jobs: - remove_stale_staging_apps: - name: Remove stale staging apps - if: ${{ github.repository == 'github/docs-internal' }} - runs-on: ubuntu-latest - steps: - - name: Check out repo's default branch - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - - - name: Setup Node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - - name: Install dependencies - run: npm ci - - - name: Run script - run: script/remove-stale-staging-apps.js - env: - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - - remove_stale_staging_envs: - name: Remove stale staging environments - runs-on: ubuntu-latest - steps: - - name: Check out repo's default branch - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - - - name: Setup Node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - - name: Install dependencies - run: npm ci - - - name: Run script - run: script/remove-stale-staging-envs.js - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - ELEVATED_TOKEN: ${{ secrets.DOCS_BOT_FR }} - REPO: ${{ github.repository }} - RUN_ID: ${{ github.run_id }} diff --git a/.github/workflows/staging-build-and-deploy-pr.yml b/.github/workflows/staging-build-and-deploy-pr.yml deleted file mode 100644 index 45db1bf149..0000000000 --- a/.github/workflows/staging-build-and-deploy-pr.yml +++ /dev/null @@ -1,210 +0,0 @@ -name: Staging - Build and Deploy PR (fast and private-only) - -# **What it does**: Builds and deploys PRs to staging but ONLY for docs-internal -# **Why we have it**: Most PRs are made on the private repo. Let's make those extra fast if we can worry less about security. -# **Who does it impact**: All staff. - -# This whole workflow is only guaranteed to be secure in the *private -# repo* and because we repo-sync these files over the to the public one, -# IT'S IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs-internal! - -on: - # The advantage of 'pull_request' over 'pull_request_target' is that we - # can make changes to this file and test them in a pull request, instead - # of relying on landing it in 'main' first. - # From a security point of view, its arguably safer this way because - # unlike 'pull_request_target', these only have secrets if the pull - # request creator has permission to access secrets. - pull_request: - -permissions: - actions: read - contents: read - deployments: write - pull-requests: read - statuses: write - -# 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: - build-and-deploy-pr: - # Important. This whole file is only supposed to run in the PRIVATE repo. - if: ${{ github.repository == 'github/docs-internal' }} - - # The assumption here is that self-hosted is faster (e.g CPU power) - # that the regular ones. And it matters in this workflow because - # we do heavy CPU stuff with `npm run build` and `tar` - # runs-on: ubuntu-latest - runs-on: self-hosted - - timeout-minutes: 5 - - steps: - - name: Check out repo - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - with: - lfs: 'true' - # To prevent issues with cloning early access content later - persist-credentials: 'false' - - - name: Check out LFS objects - run: git lfs checkout - - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - - name: Install dependencies - run: npm ci - - - name: Cache nextjs build - uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed - with: - path: .next/cache - key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }} - - - name: Build - run: npm run build - - - name: Clone early access - run: node script/early-access/clone-for-build.js - env: - DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }} - GIT_BRANCH: ${{ github.head_ref || github.ref }} - - - name: Create a Heroku build source - id: build-source - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - with: - script: | - const { owner, repo } = context.repo - - if (owner !== 'github') { - throw new Error(`Repository owner must be 'github' but was: ${owner}`) - } - if (repo !== 'docs-internal') { - throw new Error(`Repository name must be 'docs-internal' but was: ${repo}`) - } - - const Heroku = require('heroku-client') - const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) - - try { - const { source_blob: sourceBlob } = await heroku.post('/sources') - const { put_url: uploadUrl, get_url: downloadUrl } = sourceBlob - - core.setOutput('upload_url', uploadUrl) - core.setOutput('download_url', downloadUrl) - } catch (error) { - if (error.statusCode === 503) { - console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/') - } - throw error - } - - - name: Remove development-only dependencies - run: npm prune --production - - - name: Remove all npm scripts - run: npm pkg delete scripts - - - name: Set npm script for Heroku build to noop - run: npm set-script heroku-postbuild "echo 'Application was pre-built!'" - - - name: Delete heavy things we won't need deployed - run: | - - # The dereferenced file is not used in runtime once the - # decorated file has been created from it. - rm -rf lib/rest/static/dereferenced - - # Translations are never tested in Staging builds - # but let's keep the empty directory. - rm -rf translations - mkdir translations - - # Delete all the big search indexes that are NOT English (`*-en-*`) - pushd lib/search/indexes - ls | grep -ve '\-en\b' | xargs rm - popd - - # Note! Some day it would be nice to be able to delete - # all the heavy assets because they bloat the tarball. - # But it's not obvious how to test it then. For now, we'll have - # to accept that every staging build has a copy of the images. - - # The assumption here is that a staging build will not - # need these legacy redirects. Only the redirects from - # front-matter will be at play. - # These static redirects json files are notoriously large - # and they make the tarball unnecessarily large. - echo '[]' > lib/redirects/static/archived-frontmatter-fallbacks.json - echo '{}' > lib/redirects/static/developer.json - echo '{}' > lib/redirects/static/archived-redirects-from-213-to-217.json - - # This will turn every `lib/**/static/*.json` into - # an equivalent `lib/**/static/*.json.br` file. - # Once the server starts, it'll know to fall back to reading - # the `.br` equivalent if the `.json` file isn't present. - node .github/actions-scripts/compress-large-files.js - - - name: Make the tarball for Heroku - run: | - # We can't delete the .next/cache directory from the workflow - # because it's needed for caching, but we can at least exclude it - # from the tarball. Then it can be cached but not weigh down the - # tarball we intend to deploy. - tar -zc --exclude=.next/cache --file=app.tar.gz \ - node_modules/ \ - .next/ \ - assets/ \ - content/ \ - data/ \ - includes/ \ - lib/ \ - middleware/ \ - translations/ \ - server.mjs \ - package*.json \ - .npmrc \ - feature-flags.json \ - next.config.js \ - app.json \ - Procfile - - du -sh app.tar.gz - - # See: https://devcenter.heroku.com/articles/build-and-release-using-the-api#sources-endpoint - - name: Upload to the Heroku build source - env: - UPLOAD_URL: ${{ steps.build-source.outputs.upload_url }} - run: | - curl "$UPLOAD_URL" \ - -X PUT \ - -H 'Content-Type:' \ - --data-binary @app.tar.gz - - # 'npm install' is faster than 'npm ci' because it only needs to - # *append* what's missing from ./node_modules/ - - name: Re-install dependencies so we get devDependencies back - run: npm install --no-audit --no-fund --only=dev - - - name: Deploy - id: deploy - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }} - HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }} - PR_URL: ${{ github.event.pull_request.html_url }} - SOURCE_BLOB_URL: ${{ steps.build-source.outputs.download_url }} - ALLOWED_POLLING_FAILURES_PER_PHASE: '15' - RUN_ID: ${{ github.run_id }} - run: .github/actions-scripts/staging-deploy.js diff --git a/.github/workflows/staging-build-pr.yml b/.github/workflows/staging-build-pr.yml deleted file mode 100644 index 91c54cc037..0000000000 --- a/.github/workflows/staging-build-pr.yml +++ /dev/null @@ -1,135 +0,0 @@ -name: Staging - Build PR - -# **What it does**: Builds PRs before deploying them. -# **Why we have it**: Because it's not safe to share our deploy secrets with forked repos: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ -# **Who does it impact**: All contributors. - -# IT'S CRUCIALLY IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs! - -on: - pull_request: - -permissions: - contents: read - -# This allows a subsequently queued workflow run to interrupt previous runs -# These are different from the concurrency in that here it checks if the -# whole workflow runs again. The "inner concurrency" is used for -# undeployments to cleaning up resources. -concurrency: - group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}' - cancel-in-progress: true - -jobs: - build-pr: - # Important. This whole file is only supposed to run in the PUBLIC repo. - if: ${{ github.repository == 'github/docs' }} - - runs-on: ${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }} - timeout-minutes: 5 - # This interrupts Build and Deploy workflow runs in progress for this PR branch. - concurrency: - group: 'PR Staging @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}' - cancel-in-progress: true - steps: - - name: Check out repo - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - - # Make sure only approved files are changed if it's in github/docs - - name: Check changed files - if: ${{ github.event.pull_request.user.login != 'Octomerger' }} - uses: dorny/paths-filter@eb75a1edc117d3756a18ef89958ee59f9500ba58 - id: filter - with: - # Base branch used to get changed files - base: 'main' - - # Enables setting an output in the format in `${FILTER_NAME}_files - # with the names of the matching files formatted as JSON array - list-files: json - - # Returns list of changed files matching each filter - filters: | - notAllowed: - - '*.js' - - '*.mjs' - - '*.cjs' - - '*.ts' - - '*.tsx' - - '*.json' - - '.npmrc' - - '.babelrc*' - - '.env*' - - 'script/**' - - 'Procfile' - - # When there are changes to files we can't accept - - name: Fail when disallowed files are changed - if: ${{ steps.filter.outputs.notAllowed == 'true' }} - run: exit 1 - - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - # Required for `npm pkg ...` command support - - name: Update to npm@^7.20.0 - run: npm install --global npm@^7.20.0 - - - name: Install dependencies - run: npm ci - - - name: Cache nextjs build - uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed - with: - path: .next/cache - key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }} - - - name: Build - run: npm run build - - - name: Remove development-only dependencies - run: npm prune --production - - - name: Remove all npm scripts - run: npm pkg delete scripts - - - name: Set npm script for Heroku build to noop - run: npm set-script heroku-postbuild "echo 'Application was pre-built!'" - - - name: Create an archive - run: | - tar -c --file=app.tar \ - node_modules/ \ - .next/ \ - assets/ \ - content/ \ - data/ \ - includes/ \ - lib/ \ - middleware/ \ - translations/ \ - server.mjs \ - package*.json \ - .npmrc \ - feature-flags.json \ - next.config.js \ - app.json \ - Procfile - - # We can't delete the .next/cache directory from the workflow - # because it's needed for caching, but we can at least delete it - # from within the tarball. Then it can be cached but not - # weigh down the tarball we intend to deploy. - tar --delete --file=app.tar .next/cache - - # Upload only the files needed to run this application. - # We are not willing to trust the rest (e.g. script/) for the remainder - # of the deployment process. - - name: Upload build artifact - uses: actions/upload-artifact@82c141cc518b40d92cc801eee768e7aafc9c2fa2 - with: - name: pr_build - path: app.tar diff --git a/.github/workflows/staging-deploy-pr.yml b/.github/workflows/staging-deploy-pr.yml deleted file mode 100644 index 52c382a675..0000000000 --- a/.github/workflows/staging-deploy-pr.yml +++ /dev/null @@ -1,466 +0,0 @@ -name: Staging - Deploy PR - -# **What it does**: To deploy PRs to a Heroku staging environment. -# **Why we have it**: To deploy with high visibility in case of failures. -# **Who does it impact**: All contributors. - -# IT'S CRUCIALLY IMPORTANT THAT THIS WORKFLOW IS ONLY ENABLED IN docs! - -on: - workflow_run: - workflows: - - 'Staging - Build PR' - types: - - completed - -permissions: - actions: read - contents: read - deployments: write - pull-requests: read - statuses: write - -# IMPORTANT: Intentionally OMIT a `concurrency` configuration from this workflow's -# top-level as we do not have any guarantee of identifying values being available -# within the `github.event` context for PRs from forked repos! -# -# The implication of this shortcoming is that we may have multiple workflow runs -# of this running at the same time for different commits within the same PR. -# However, once they reach the `concurrency` configurations deeper down within -# this workflow's jobs, then we can expect concurrent short-circuiting to begin. - -env: - CONTEXT_NAME: '${{ github.workflow }} / deploy (${{ github.event.workflow_run.event }})' - ACTIONS_RUN_LOG: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }} - BUILD_ACTIONS_RUN_ID: ${{ github.event.workflow_run.id }} - BUILD_ACTIONS_RUN_LOG: https://github.com/${{ github.repository }}/actions/runs/${{ github.event.workflow_run.id }} - -jobs: - pr-metadata: - # This is needed because the workflow we depend on - # (see on.workflow_run.workflows) might be running from pushes on - # main. That's because it needs to do that to popular the cache. - if: >- - ${{ - github.repository == 'github/docs' && - github.event.workflow_run.event == 'pull_request' && - github.event.workflow_run.conclusion == 'success' - }} - runs-on: ubuntu-latest - outputs: - number: ${{ steps.pr.outputs.number }} - url: ${{ steps.pr.outputs.url }} - state: ${{ steps.pr.outputs.state }} - head_sha: ${{ steps.pr.outputs.head_sha }} - head_branch: ${{ steps.pr.outputs.head_branch }} - head_label: ${{ steps.pr.outputs.head_label }} - head_ref: ${{ steps.pr.outputs.head_ref }} - steps: - - name: Find the originating pull request - id: pr - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - BUILD_ACTIONS_RUN_ID: ${{ env.BUILD_ACTIONS_RUN_ID }} - with: - script: | - - // Curious about what version of node you get - console.log('Node version:', process.version) - - // In order to find out the PR info for a forked repo, we must query - // the API for more info based on the originating workflow run - const { BUILD_ACTIONS_RUN_ID } = process.env - const { owner, repo } = context.repo - const { data: run } = await github.actions.getWorkflowRun({ - owner, - repo, - run_id: BUILD_ACTIONS_RUN_ID, - }) - - // Gather PR-identifying information from the workflow run - const { - head_branch: headBranch, - head_sha: headSha, - head_repository: { - owner: { login: prRepoOwner }, - name: prRepoName - } - } = run - - const prIsInternal = owner === prRepoOwner && repo === prRepoName - let headLabel = `${prRepoOwner}:${headBranch}` - - // If the PR is external, prefix its head branch name with the - // forked repo owner's login and their fork repo name e.g. - // "octocat/my-fork:docs". We need to include the fork repo - // name as well to account for an API issue (this will work fine - // if they don't have a different fork repo name). - if (!prIsInternal) { - headLabel = `${prRepoOwner}/${prRepoName}:${headBranch}` - } - - // If the PR is external, prefix its head branch name with the - // forked repo owner's login, e.g. "octocat:docs" - const headRef = prIsInternal ? headBranch : headLabel - - // Retrieve matching PRs (up to 30) - const { data: pulls } = await github.pulls.list({ - owner, - repo, - head: headLabel, - sort: 'updated', - direction: 'desc', - per_page: 30 - }) - - // Find the open PR, if any, otherwise choose the most recently updated - const targetPull = pulls.find(pr => pr.state === 'open') || pulls[0] || {} - - const pullNumber = targetPull.number || 0 - const pullUrl = targetPull.html_url || 'about:blank' - const pullState = targetPull.state || 'closed' - - core.setOutput('number', pullNumber.toString()) - core.setOutput('url', pullUrl) - core.setOutput('state', pullState) - core.setOutput('head_sha', headSha) - core.setOutput('head_branch', headBranch) - core.setOutput('head_label', headLabel) - core.setOutput('head_ref', headRef) - - debug-originating-trigger: - needs: pr-metadata - runs-on: ubuntu-latest - steps: - - name: Dump info about the originating workflow run - env: - PR_NUMBER: ${{ needs.pr-metadata.outputs.number }} - PR_URL: ${{ needs.pr-metadata.outputs.url }} - PR_STATE: ${{ needs.pr-metadata.outputs.state }} - HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }} - HEAD_BRANCH: ${{ needs.pr-metadata.outputs.head_branch }} - HEAD_LABEL: ${{ needs.pr-metadata.outputs.head_label }} - HEAD_REF: ${{ needs.pr-metadata.outputs.head_ref }} - BUILD_ACTIONS_RUN_ID: ${{ env.BUILD_ACTIONS_RUN_ID }} - BUILD_ACTIONS_RUN_LOG: ${{ env.BUILD_ACTIONS_RUN_LOG }} - run: | - echo "Originating workflow info:" - echo " - PR_NUMBER = $PR_NUMBER" - echo " - PR_URL = $PR_URL" - echo " - PR_STATE = $PR_STATE" - echo " - HEAD_SHA = $HEAD_SHA" - echo " - HEAD_BRANCH = $HEAD_BRANCH" - echo " - HEAD_LABEL = $HEAD_LABEL" - echo " - HEAD_REF = $HEAD_REF" - echo " - BUILD_ACTIONS_RUN_ID = $BUILD_ACTIONS_RUN_ID" - echo " - BUILD_ACTIONS_RUN_LOG = $BUILD_ACTIONS_RUN_LOG" - - notify-of-failed-builds: - needs: pr-metadata - if: >- - ${{ - needs.pr-metadata.outputs.number != '0' && - github.event.workflow_run.conclusion == 'failure' - }} - runs-on: ubuntu-latest - timeout-minutes: 1 - # Specifically omitting a concurrency group here in case the build was not - # successful BECAUSE a subsequent build already canceled it - steps: - - name: Verify build workflow run was not cancelled - id: check-workflow-run - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - BUILD_ACTIONS_RUN_ID: ${{ env.BUILD_ACTIONS_RUN_ID }} - with: - script: | - const { owner, repo } = context.repo - const { data: { jobs: buildJobs } } = await github.actions.listJobsForWorkflowRun({ - owner, - repo, - run_id: process.env.BUILD_ACTIONS_RUN_ID, - filter: 'latest' - }) - const wasCancelled = ( - buildJobs.length > 0 && - buildJobs.every(({ status, conclusion }) => { - return status === 'completed' && conclusion === 'cancelled' - }) - ) - core.setOutput('cancelled', wasCancelled.toString()) - - - if: ${{ steps.check-workflow-run.outputs.cancelled == 'false' }} - name: Send Slack notification if build workflow failed - uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 - with: - channel: ${{ secrets.DOCS_STAGING_DEPLOYMENT_FAILURES_SLACK_CHANNEL_ID }} - bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} - color: failure - text: Staging build failed for PR ${{ needs.pr-metadata.outputs.url }} at commit ${{ needs.pr-metadata.outputs.head_sha }}. See ${{ env.BUILD_ACTIONS_RUN_LOG }}. This run was ${{ env.ACTIONS_RUN_LOG }}. - - prepare-for-deploy: - needs: pr-metadata - if: ${{ needs.pr-metadata.outputs.state == 'open' }} - runs-on: ubuntu-latest - timeout-minutes: 5 - # This interrupts Build and Deploy workflow runs in progress for this PR branch. - concurrency: - group: 'PR Staging @ ${{ needs.pr-metadata.outputs.head_label }}' - cancel-in-progress: true - outputs: - source_blob_url: ${{ steps.build-source.outputs.download_url }} - steps: - - name: Create initial status - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - CONTEXT_NAME: ${{ env.CONTEXT_NAME }} - ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }} - HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }} - with: - script: | - const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env - const { owner, repo } = context.repo - await github.repos.createCommitStatus({ - owner, - repo, - sha: HEAD_SHA, - context: CONTEXT_NAME, - state: 'pending', - description: 'The app is being deployed. See logs.', - target_url: ACTIONS_RUN_LOG - }) - - - name: Check out repo's default branch - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - with: - # To prevent issues with cloning early access content later - persist-credentials: 'false' - lfs: 'true' - - - name: Check out LFS objects - run: git lfs checkout - - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - # Install any additional dependencies *before* downloading the build artifact - - name: Install Heroku client development-only dependency - run: npm install --no-save heroku-client - - # Download the previously built "app.tar" - - name: Download build artifact - uses: dawidd6/action-download-artifact@af92a8455a59214b7b932932f2662fdefbd78126 - with: - workflow: ${{ github.event.workflow_run.workflow_id }} - run_id: ${{ env.BUILD_ACTIONS_RUN_ID }} - name: pr_build - path: ${{ runner.temp }} - - # gzip the app.tar to meet Heroku's expected format - - name: Create a gzipped archive (docs) - run: gzip -9 < "$RUNNER_TEMP/app.tar" > app.tar.gz - - - name: Create a Heroku build source - id: build-source - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - with: - script: | - const { owner, repo } = context.repo - - if (owner !== 'github') { - throw new Error(`Repository owner must be 'github' but was: ${owner}`) - } - if (repo !== 'docs') { - throw new Error(`Repository name must be 'docs' but was: ${repo}`) - } - - const Heroku = require('heroku-client') - const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) - - try { - const { source_blob: sourceBlob } = await heroku.post('/sources') - const { put_url: uploadUrl, get_url: downloadUrl } = sourceBlob - - core.setOutput('upload_url', uploadUrl) - core.setOutput('download_url', downloadUrl) - } catch (error) { - if (error.statusCode === 503) { - console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/') - } - throw error - } - - # See: https://devcenter.heroku.com/articles/build-and-release-using-the-api#sources-endpoint - - name: Upload to the Heroku build source - env: - UPLOAD_URL: ${{ steps.build-source.outputs.upload_url }} - run: | - curl "$UPLOAD_URL" \ - -X PUT \ - -H 'Content-Type:' \ - --data-binary @app.tar.gz - - - name: Create failure status - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - if: ${{ failure() }} - env: - CONTEXT_NAME: ${{ env.CONTEXT_NAME }} - ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }} - HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }} - with: - script: | - const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env - const { owner, repo } = context.repo - await github.repos.createCommitStatus({ - owner, - repo, - sha: HEAD_SHA, - context: CONTEXT_NAME, - state: 'error', - description: 'Failed to deploy. See logs.', - target_url: ACTIONS_RUN_LOG - }) - - - name: Send Slack notification if deployment preparation job failed - uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 - if: ${{ failure() }} - with: - channel: ${{ secrets.DOCS_STAGING_DEPLOYMENT_FAILURES_SLACK_CHANNEL_ID }} - bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} - color: failure - text: Staging preparation failed for PR ${{ needs.pr-metadata.outputs.url }} at commit ${{ needs.pr-metadata.outputs.head_sha }}. See ${{ env.ACTIONS_RUN_LOG }}. - - check-pr-before-deploy: - needs: [pr-metadata, prepare-for-deploy] - runs-on: ubuntu-latest - timeout-minutes: 1 - # This interrupts Build and Deploy workflow runs in progress for this PR branch. - concurrency: - group: 'PR Staging @ ${{ needs.pr-metadata.outputs.head_label }}' - cancel-in-progress: true - outputs: - pull_request_state: ${{ steps.check-pr.outputs.state }} - steps: - - name: Check pull request state - id: check-pr - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - PR_NUMBER: ${{ needs.pr-metadata.outputs.number }} - with: - script: | - const { owner, repo } = context.repo - const { data: pullRequest } = await github.pulls.get({ - owner, - repo, - pull_number: process.env.PR_NUMBER - }) - core.setOutput('state', pullRequest.state) - - deploy: - needs: [pr-metadata, prepare-for-deploy, check-pr-before-deploy] - if: ${{ needs.check-pr-before-deploy.outputs.pull_request_state == 'open' }} - runs-on: ubuntu-latest - timeout-minutes: 10 - # This interrupts Build and Deploy workflow runs in progress for this PR branch. - concurrency: - group: 'PR Staging @ ${{ needs.pr-metadata.outputs.head_label }}' - cancel-in-progress: true - steps: - - name: Check out repo's default branch - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - - name: Install dependencies - run: npm ci - - - name: Deploy - id: deploy - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }} - HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }} - HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }} - PR_URL: ${{ needs.pr-metadata.outputs.url }} - SOURCE_BLOB_URL: ${{ needs.prepare-for-deploy.outputs.source_blob_url }} - ALLOWED_POLLING_FAILURES_PER_PHASE: '15' - RUN_ID: ${{ github.run_id }} - run: .github/actions-scripts/staging-deploy.js - - - name: Create successful commit status - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - CONTEXT_NAME: ${{ env.CONTEXT_NAME }} - ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }} - HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }} - run: .github/actions-scripts/staging-commit-status-success.js - - - name: Mark the deployment as inactive if timed out - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - if: ${{ steps.deploy.outcome == 'cancelled' }} - env: - DEPLOYMENT_ID: ${{ steps.deploy.outputs.deploymentId }} - LOG_URL: ${{ steps.deploy.outputs.logUrl }} - with: - script: | - const { DEPLOYMENT_ID, LOG_URL } = process.env - const { owner, repo } = context.repo - - if (!DEPLOYMENT_ID) { - throw new Error('A deployment wasn't created before a timeout occurred!') - } - - await github.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: DEPLOYMENT_ID, - state: 'error', - description: 'The deployment step timed out. See workflow logs.', - log_url: LOG_URL, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - console.log('⏲️ Deployment status: error - The deployment timed out...') - - - name: Create failure status - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - if: ${{ failure() }} - env: - CONTEXT_NAME: ${{ env.CONTEXT_NAME }} - ACTIONS_RUN_LOG: ${{ env.ACTIONS_RUN_LOG }} - HEAD_SHA: ${{ needs.pr-metadata.outputs.head_sha }} - with: - script: | - const { CONTEXT_NAME, ACTIONS_RUN_LOG, HEAD_SHA } = process.env - const { owner, repo } = context.repo - await github.repos.createCommitStatus({ - owner, - repo, - sha: HEAD_SHA, - context: CONTEXT_NAME, - state: 'error', - description: 'Failed to deploy. See logs.', - target_url: ACTIONS_RUN_LOG - }) - - - name: Send Slack notification if deployment job failed - uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 - if: ${{ failure() }} - with: - channel: ${{ secrets.DOCS_STAGING_DEPLOYMENT_FAILURES_SLACK_CHANNEL_ID }} - bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} - color: failure - text: Staging deployment failed for PR ${{ needs.pr-metadata.outputs.url }} at commit ${{ needs.pr-metadata.outputs.head_sha }}. See ${{ env.ACTIONS_RUN_LOG }}. diff --git a/.github/workflows/test-windows.yml b/.github/workflows/test-windows.yml deleted file mode 100644 index 52d77dd42c..0000000000 --- a/.github/workflows/test-windows.yml +++ /dev/null @@ -1,76 +0,0 @@ -# NOTE: Changes to this file should also be applied to './test.yml' - -name: Node.js Tests - Windows - -# **What it does**: This runs our tests on Windows. -# **Why we have it**: We want to support Windows contributors to docs. -# **Who does it impact**: Anyone working on docs on a Windows device. - -on: - workflow_dispatch: - pull_request: - schedule: - - cron: '50 19 * * *' # once a day at 19:50 UTC / 11:50 PST - -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: - test: - runs-on: windows-latest - if: (github.event_name != 'pull_request') || (github.event_name == 'pull_request' && (contains(github.event.pull_request.labels.*.name, 'Windows') || contains(github.event.pull_request.labels.*.name, 'windows'))) - timeout-minutes: 60 - strategy: - fail-fast: false - matrix: - test-group: - [ - content, - graphql, - meta, - rendering, - routing, - unit, - linting, - translations, - ] - steps: - - name: Check out repo - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 - with: - # Enables cloning the Early Access repo later with the relevant PAT - persist-credentials: 'false' - - - name: Setup node - uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 - with: - node-version: 16.13.x - cache: npm - - - name: Install dependencies - run: npm ci - - - name: Cache nextjs build - uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed - with: - path: .next/cache - key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }} - - - if: ${{ github.repository == 'github/docs-internal' }} - name: Clone early access - run: npm run heroku-postbuild - env: - DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }} - GIT_BRANCH: ${{ github.head_ref || github.ref }} - - - if: ${{ github.repository != 'github/docs-internal' }} - name: Run build script - run: npm run build - - - name: Run tests - run: npm test -- tests/${{ matrix.test-group }}/ diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 87a8347b79..1db6685fae 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -1,5 +1,3 @@ -# NOTE: Changes to this file should also be applied to './test-windows.yml' - name: Node.js Tests # **What it does**: Runs our tests. @@ -51,6 +49,53 @@ jobs: # Enables cloning the Early Access repo later with the relevant PAT persist-credentials: 'false' + - name: Figure out which docs-early-access branch to checkout, if internal repo + if: ${{ github.repository == 'github/docs-internal' }} + id: check-early-access + uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d + env: + BRANCH_NAME: ${{ github.head_ref || github.ref_name }} + with: + github-token: ${{ secrets.DOCUBOT_REPO_PAT }} + result-encoding: string + script: | + // If being run from a PR, this becomes 'my-cool-branch'. + // If run on main, with the `workflow_dispatch` action for + // example, the value becomes 'main'. + const { BRANCH_NAME } = process.env + try { + const response = await github.repos.getBranch({ + owner: 'github', + repo: 'docs-early-access', + BRANCH_NAME, + }) + console.log(`Using docs-early-access branch called '${BRANCH_NAME}'.`) + return BRANCH_NAME + } catch (err) { + if (err.status === 404) { + console.log(`There is no docs-early-access branch called '${BRANCH_NAME}' so checking out 'main' instead.`) + return 'main' + } + throw err + } + + - name: Check out docs-early-access too, if internal repo + if: ${{ github.repository == 'github/docs-internal' }} + uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 + with: + repository: github/docs-early-access + token: ${{ secrets.DOCUBOT_REPO_PAT }} + path: docs-early-access + ref: ${{ steps.check-early-access.outputs.result }} + + - name: Merge docs-early-access repo's folders + if: ${{ github.repository == 'github/docs-internal' }} + run: | + mv docs-early-access/assets assets/images/early-access + mv docs-early-access/content content/early-access + mv docs-early-access/data data/early-access + rm -r docs-early-access + - name: Checkout LFS objects run: git lfs checkout @@ -78,13 +123,6 @@ jobs: - name: Install dependencies run: npm ci - - name: Clone early access - if: ${{ github.repository == 'github/docs-internal' }} - run: script/early-access/clone-for-build.js - env: - DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }} - GIT_BRANCH: ${{ github.head_ref || github.ref }} - - name: Cache nextjs build uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed with: diff --git a/.github/workflows/triage-unallowed-contributions.yml b/.github/workflows/triage-unallowed-contributions.yml index 0cb30cdd6f..caae155b4a 100644 --- a/.github/workflows/triage-unallowed-contributions.yml +++ b/.github/workflows/triage-unallowed-contributions.yml @@ -10,7 +10,6 @@ on: - '.github/actions-scripts/**' - '.github/workflows/**' - '.github/CODEOWNERS' - - 'app.json' - 'assets/fonts/**' - 'data/graphql/**' - 'Dockerfile*' @@ -20,7 +19,6 @@ on: - 'lib/webhooks/**' - 'lib/search/indexes/**' - 'package*.json' - - 'Procfile' - 'script/**' - 'translations/**' @@ -58,7 +56,6 @@ jobs: - '.github/actions-scripts/**' - '.github/workflows/**' - '.github/CODEOWNERS' - - 'app.json' - 'assets/fonts/**' - 'data/graphql/**' - 'Dockerfile*' @@ -68,7 +65,6 @@ jobs: - 'lib/webhooks/**' - 'lib/search/indexes/**' - 'package*.json' - - 'Procfile' - 'scripts/**' - 'translations/**' @@ -83,7 +79,6 @@ jobs: '.github/actions-scripts/**', '.github/workflows/**', '.github/CODEOWNERS', - 'app.json', 'assets/fonts/**', 'data/graphql/**', 'Dockerfile*', @@ -93,7 +88,6 @@ jobs: 'lib/webhooks/**', 'lib/search/indexes/**', 'package*.json', - 'Procfile', 'scripts/**', 'translations/**', ] @@ -111,7 +105,7 @@ jobs: body: reviewMessage, }) - workflowFailMessage = `${workflowFailMessage} Please see ${createdComment.data.html_url} for details.` + workflowFailMessage = `${workflowFailMessage} Please see ${createdComment.data.html_url} for details.` } catch(err) { console.log("Error creating comment.", err) } diff --git a/.github/workflows/triage-unallowed-internal-changes.yml b/.github/workflows/triage-unallowed-internal-changes.yml index f839c016e9..4a505b2afc 100644 --- a/.github/workflows/triage-unallowed-internal-changes.yml +++ b/.github/workflows/triage-unallowed-internal-changes.yml @@ -1,7 +1,7 @@ name: Check for unallowed internal changes -# **What it does**: If someone changes app.json or search indexes, we fail the check. -# **Why we have it**: app.json should rarely be edited, so we'll require an admin merge if the file really needs to be changed. The search indexes are synced every 4 hours, so changes should not need to be made. +# **What it does**: If someone changes search indexes, we fail the check. +# **Why we have it**: The search indexes are synced every 4 hours, so changes should not need to be made. # **Who does it impact**: Docs engineering and content writers. on: @@ -44,19 +44,8 @@ jobs: # Returns list of changed files matching each filter filters: | - notAllowed: - - 'app.json' notAllowedSearchSyncLabel: - 'lib/search/indexes/**' - notAllowed: - needs: check-internal-changes - if: ${{ needs.check-internal-changes.outputs.notAllowed == 'true' }} - runs-on: ubuntu-latest - steps: - - name: Fail if unallowed changes were made - run: | - echo "Please admin merge if you really need to update app.json!" - exit 1 notAllowedSearchSyncLabel: needs: check-internal-changes if: ${{ needs.check-internal-changes.outputs.notAllowedSearchSyncLabel == 'true' }} diff --git a/.gitignore b/.gitignore index 510858060f..c530087090 100644 --- a/.gitignore +++ b/.gitignore @@ -16,4 +16,8 @@ coverage/ blc_output.log blc_output_internal.log broken_links.md -lib/redirects/.redirects-cache_*.json +lib/redirects/.redirects-cache.json + +# During the preview deploy untrusted user code may be cloned into this directory +# We ignore it from git to keep things deterministic +user-code/ diff --git a/Dockerfile b/Dockerfile index 912301bc55..cad07f06c9 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,6 +1,4 @@ -# This Dockerfile can be used for docker-based deployments to platforms -# like Now or Moda, but it is currently _not_ used by our Heroku deployments -# It uses two multi-stage builds: `install` and the main build to keep the image size down. +# This Dockerfile is used for docker-based deployments to Azure for both preview environments and production # -------------------------------------------------------------------------------- # BASE IMAGE @@ -23,7 +21,7 @@ FROM base as all_deps COPY --chown=node:node package.json package-lock.json ./ -RUN npm ci --no-optional +RUN npm ci --no-optional --registry https://registry.npmjs.org/ # For Next.js v12+ # This the appropriate necessary extra for node:16-alpine diff --git a/Procfile b/Procfile deleted file mode 100644 index 4bec004287..0000000000 --- a/Procfile +++ /dev/null @@ -1 +0,0 @@ -web: NODE_ENV=production node server.mjs diff --git a/README.md b/README.md index fadb39c8de..715c2d4fda 100644 --- a/README.md +++ b/README.md @@ -60,4 +60,4 @@ When using the GitHub logos, be sure to follow the [GitHub logo guidelines](http ## Thanks :purple_heart: -Thanks for all your contributions and efforts towards improving the GitHub documentation. We thank you being part of our :sparkles: community :sparkles: ! +Thanks for all your contributions and efforts towards improving the GitHub documentation. We thank you being part of our :sparkles: community :sparkles:! diff --git a/app.json b/app.json deleted file mode 100644 index 14f8ba9f54..0000000000 --- a/app.json +++ /dev/null @@ -1,17 +0,0 @@ -{ - "name": "docs.github.com", - "env": { - "NODE_ENV": "production", - "ENABLED_LANGUAGES": "en", - "WEB_CONCURRENCY": "1" - }, - "buildpacks": [ - { "url": "heroku/nodejs" } - ], - "formation": { - "web": { - "quantity": 1, - "size": "standard-2x" - } - } -} diff --git a/assets/images/commonmark-lists.png b/assets/images/commonmark-lists.png new file mode 100644 index 0000000000..2c8739f967 Binary files /dev/null and b/assets/images/commonmark-lists.png differ diff --git a/assets/images/create_app.png b/assets/images/create_app.png index 20f24d95f6..3a1dca57f8 100644 Binary files a/assets/images/create_app.png and b/assets/images/create_app.png differ diff --git a/assets/images/deploy-key.png b/assets/images/deploy-key.png index 2043f710cf..30d2b8c999 100644 Binary files a/assets/images/deploy-key.png and b/assets/images/deploy-key.png differ diff --git a/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png b/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png new file mode 100644 index 0000000000..c92015c8d2 Binary files /dev/null and b/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png differ diff --git a/assets/images/help/2fa/2fa-password-reset.png b/assets/images/help/2fa/2fa-password-reset.png index 6cfa78f40d..397fa4e296 100644 Binary files a/assets/images/help/2fa/2fa-password-reset.png and b/assets/images/help/2fa/2fa-password-reset.png differ 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/billing/actions-packages-spending-limit-notifications.png b/assets/images/help/billing/actions-packages-spending-limit-notifications.png new file mode 100644 index 0000000000..0cd8f9cb49 Binary files /dev/null and b/assets/images/help/billing/actions-packages-spending-limit-notifications.png differ diff --git a/assets/images/help/billing/codespaces-spending-limit-notifications.png b/assets/images/help/billing/codespaces-spending-limit-notifications.png new file mode 100644 index 0000000000..709278c773 Binary files /dev/null and b/assets/images/help/billing/codespaces-spending-limit-notifications.png differ diff --git a/assets/images/help/dependabot/dependabot-alert-pr-link.png b/assets/images/help/dependabot/dependabot-alert-pr-link.png index 9028b6cf8e..4e1f857b0d 100644 Binary files a/assets/images/help/dependabot/dependabot-alert-pr-link.png and b/assets/images/help/dependabot/dependabot-alert-pr-link.png differ diff --git a/assets/images/help/dependabot/dependabot-security-update-error.png b/assets/images/help/dependabot/dependabot-security-update-error.png deleted file mode 100644 index 09b33196ba..0000000000 Binary files a/assets/images/help/dependabot/dependabot-security-update-error.png and /dev/null differ diff --git a/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png b/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png new file mode 100644 index 0000000000..078dab35da Binary files /dev/null and b/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png differ diff --git a/assets/images/help/graphs/dependabot-alerts-filters.png b/assets/images/help/graphs/dependabot-alerts-filters.png new file mode 100644 index 0000000000..876b494e06 Binary files /dev/null and b/assets/images/help/graphs/dependabot-alerts-filters.png differ diff --git a/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png b/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png index 4d1a369f23..4147d54d16 100644 Binary files a/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png and b/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png differ diff --git a/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png b/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png new file mode 100644 index 0000000000..be29a07ae9 Binary files /dev/null and b/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png differ diff --git a/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png b/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png new file mode 100644 index 0000000000..de77c4b109 Binary files /dev/null and b/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png differ diff --git a/assets/images/help/repository/dependabot-alerts-view.png b/assets/images/help/repository/dependabot-alerts-view.png index 5392ee6c2c..b8c20c500e 100644 Binary files a/assets/images/help/repository/dependabot-alerts-view.png and b/assets/images/help/repository/dependabot-alerts-view.png differ diff --git a/assets/images/help/repository/dependabot-vulnerabilities-number.png b/assets/images/help/repository/dependabot-vulnerabilities-number.png deleted file mode 100644 index 7b5b0a4a7b..0000000000 Binary files a/assets/images/help/repository/dependabot-vulnerabilities-number.png and /dev/null differ diff --git a/assets/images/help/repository/headings_toc.png b/assets/images/help/repository/headings_toc.png new file mode 100644 index 0000000000..9370750baf Binary files /dev/null and b/assets/images/help/repository/headings_toc.png differ diff --git a/assets/images/help/repository/legacy-dependabot-alerts-view.png b/assets/images/help/repository/legacy-dependabot-alerts-view.png new file mode 100644 index 0000000000..110991e20d Binary files /dev/null and b/assets/images/help/repository/legacy-dependabot-alerts-view.png differ diff --git a/assets/images/help/repository/secret-scanning-create-custom-pattern.png b/assets/images/help/repository/secret-scanning-create-custom-pattern.png index c92015c8d2..16f4801f13 100644 Binary files a/assets/images/help/repository/secret-scanning-create-custom-pattern.png and b/assets/images/help/repository/secret-scanning-create-custom-pattern.png differ diff --git a/assets/images/help/repository/secret-scanning-publish-pattern.png b/assets/images/help/repository/secret-scanning-publish-pattern.png new file mode 100644 index 0000000000..281f05edc1 Binary files /dev/null and b/assets/images/help/repository/secret-scanning-publish-pattern.png differ diff --git a/assets/images/help/settings/sso-allowlist-button.png b/assets/images/help/settings/sso-allowlist-button.png index 46fecd7cd6..ee0675d90f 100644 Binary files a/assets/images/help/settings/sso-allowlist-button.png and b/assets/images/help/settings/sso-allowlist-button.png differ diff --git a/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png b/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png index b996e80656..88817f8a6d 100644 Binary files a/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png and b/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png differ diff --git a/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png b/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png index 6ebd1ebb82..ce39e05a05 100644 Binary files a/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png and b/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png differ diff --git a/assets/images/help/settings/token-authorize-button.png b/assets/images/help/settings/token-authorize-button.png index 281c1b54a9..1032813464 100644 Binary files a/assets/images/help/settings/token-authorize-button.png and b/assets/images/help/settings/token-authorize-button.png differ diff --git a/assets/images/help/writing/mermaid-flow-chart.png b/assets/images/help/writing/mermaid-flow-chart.png new file mode 100644 index 0000000000..900b3b6c39 Binary files /dev/null and b/assets/images/help/writing/mermaid-flow-chart.png differ diff --git a/assets/images/install_permissions.png b/assets/images/install_permissions.png index 3ece4e3eb9..8540bcda46 100644 Binary files a/assets/images/install_permissions.png and b/assets/images/install_permissions.png differ diff --git a/assets/images/private_key.png b/assets/images/private_key.png index f5b0a2364b..ebc1c58e7c 100644 Binary files a/assets/images/private_key.png and b/assets/images/private_key.png differ diff --git a/assets/images/settings/developer_settings.png b/assets/images/settings/developer_settings.png index 455deba228..4eb1d920da 100644 Binary files a/assets/images/settings/developer_settings.png and b/assets/images/settings/developer_settings.png differ diff --git a/azure-preview-env-template.json b/azure-preview-env-template.json index 911a103d15..82667ab87b 100644 --- a/azure-preview-env-template.json +++ b/azure-preview-env-template.json @@ -2,109 +2,170 @@ "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { - "appName": { - "type": "String" - }, - "location": { - "type": "String" - }, - "linuxFxVersion": { - "type": "String" - }, - "dockerRegistryUrl": { - "type": "String" - }, - "dockerRegistryUsername": { - "type": "String" - }, - "dockerRegistryPassword": { - "type": "SecureString" + "appName": { + "defaultValue": null, + "type": "string", + "minLength": 5, + "maxLength": 63, + "metadata": { + "description": "A unique name for the app" } - }, - "variables": { - "appServicePlanName": "[concat('ASP-', parameters('appName'))]", - "dnsName": "[concat(parameters('appName'), '-', take(uniqueString(subscription().subscriptionId, resourceGroup().id, deployment().name), 6))]" + }, + "location": { + "type": "String" + }, + "containerImage": { + "type": "string", + "defaultValue": null, + "metadata": { + "description": "Container image to deploy" + } + }, + "dockerRegistryUrl": { + "type": "String", + "metadata": { + "description": "Should be a valid host name without protocol" + } + }, + "dockerRegistryUsername": { + "type": "String" + }, + "dockerRegistryPassword": { + "type": "SecureString" + }, + "storageAccountName": { + "type": "String" + }, + "storageAccountKey": { + "type": "SecureString" + } }, "resources": [ - { - - "type": "Microsoft.Web/serverfarms", - "apiVersion": "2021-02-01", - "name": "[variables('appServicePlanName')]", - "location": "[parameters('location')]", - "sku": { - "name": "B2" + { + "type": "Microsoft.ContainerInstance/containerGroups", + "name": "[parameters('appName')]", + "apiVersion": "2021-07-01", + "location": "[resourceGroup().location]", + "properties": { + "containers": [ + { + "name": "app", + "properties": { + "image": "[parameters('containerImage')]", + "ports": [ + { + "protocol": "TCP", + "port": 4000 + } + ], + "environmentVariables": [ + { + "name": "PORT", + "value": "4000" + }, + { + "name": "NODE_ENV", + "value": "production" + }, + { + "name": "WEB_CONCURRENCY", + "value": "1" + }, + { + "name": "ENABLED_LANGUAGES", + "value": "en" + } + ], + "resources": { + "requests": { + "memoryInGB": 4, + "cpu": 1 + } + } + } }, - "kind": "linux", - "properties": { - "reserved": true - } - }, - { - "type": "Microsoft.Web/sites", - "apiVersion": "2018-11-01", - "name": "[variables('dnsName')]", - "location": "[parameters('location')]", - "dependsOn": [ - "[resourceId('Microsoft.Web/serverfarms', variables('appServicePlanName'))]" - ], - "tags": { - "DocsAppName": "[parameters('appName')]" - }, - "properties": { - "name": "[variables('dnsName')]", - "siteConfig": { - "appSettings": [ - { - "name": "DOCKER_REGISTRY_SERVER_URL", - "value": "[parameters('dockerRegistryUrl')]" - }, - { - "name": "DOCKER_REGISTRY_SERVER_USERNAME", - "value": "[parameters('dockerRegistryUsername')]" - }, - { - "name": "DOCKER_REGISTRY_SERVER_PASSWORD", - "value": "[parameters('dockerRegistryPassword')]" - }, - { - "name": "WEBSITES_ENABLE_APP_SERVICE_STORAGE", - "value": "false" - }, - { - "name": "NODE_ENV", - "value": "production" - }, - { - "name": "PORT", - "value": "4000" - }, - { - "name": "DEPLOYMENT_ENV", - "value": "azure" - }, - { - "name": "ENABLED_LANGUAGES", - "value": "en" - } - ], - "linuxFxVersion": "[parameters('linuxFxVersion')]", - "appCommandLine": "", - "alwaysOn": false, - "numberOfWorkers": 1, - "healthCheckPath": "/healthz", - "httpLoggingEnabled": true, - "logsDirectorySizeLimit": 35 + { + "name": "caddy-ssl-server", + "properties": { + "image": "caddy:2.4.6", + "command": [ + "caddy", + "reverse-proxy", + "--from", + "[concat(parameters('appName'), '.', parameters('location'), '.azurecontainer.io')]", + "--to", + "localhost:4000" + ], + "ports": [ + { + "protocol": "TCP", + "port": 443 + }, + { + "protocol": "TCP", + "port": 80 + } + ], + "environmentVariables": [], + "resources": { + "requests": { + "memoryInGB": 1, + "cpu": 1 + } }, - "serverFarmId": "[concat('/subscriptions/', subscription().id, '/resourcegroups/', resourceGroup().name, '/providers/Microsoft.Web/serverfarms/', variables('appServicePlanName'))]", - "clientAffinityEnabled": false + "volumeMounts": [ + { + "name": "caddy-data", + "mountPath": "/data" + } + ] + } } + ], + "volumes": [ + { + "name": "caddy-data", + "azureFile": { + "shareName": "caddy", + "storageAccountName": "[parameters('storageAccountName')]", + "storageAccountKey": "[parameters('storageAccountKey')]" + } + } + ], + "imageRegistryCredentials": [ + { + "server": "[parameters('dockerRegistryUrl')]", + "username": "[parameters('dockerRegistryUsername')]", + "password": "[parameters('dockerRegistryPassword')]" + } + ], + "restartPolicy": "Always", + "ipAddress": { + "ports": [ + { + "protocol": "TCP", + "port": 443 + }, + { + "protocol": "TCP", + "port": 4000 + }, + { + "protocol": "TCP", + "port": 80 + } + ], + "type": "Public", + "dnsNameLabel": "[parameters('appName')]" + }, + "osType": "Linux" } + } ], "outputs": { - "defaultHostName": { - "type": "string", - "value": "[concat('https://', variables('dnsName'), '.azurewebsites.net')]" - } + "defaultHostName": { + "value": "[reference(resourceId('Microsoft.ContainerInstance/containerGroups', parameters('appName'))).ipAddress.fqdn]", + "type": "string" + } } } diff --git a/components/Search.tsx b/components/Search.tsx index 662ff49e76..f567feee94 100644 --- a/components/Search.tsx +++ b/components/Search.tsx @@ -132,9 +132,9 @@ export function Search({ if (router.pathname === '/') { // Don't include router.locale so next doesn't attempt a // request to `/_next/static/chunks/pages/en.js` - router.replace(`/?${params.toString()}`, asPath) + router.replace(`/?${params.toString()}`, asPath, { shallow: true }) } else { - router.replace(asPath) + router.replace(asPath, undefined, { shallow: true }) } } }, [debouncedQuery]) diff --git a/components/playground/PlaygroundArticle.tsx b/components/playground/PlaygroundArticle.tsx index d3906f2b52..ebd171e138 100644 --- a/components/playground/PlaygroundArticle.tsx +++ b/components/playground/PlaygroundArticle.tsx @@ -27,7 +27,7 @@ export const PlaygroundArticle = () => { {article.prerequisites && (
- +
@@ -44,7 +44,7 @@ export const PlaygroundArticle = () => { {/* toc */}
- +
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 6b8b438787..e529d774e8 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 @@ -37,7 +37,7 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y 1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%} {% data reusables.repositories.click-collaborators-teams %} 1. Click **Invite a collaborator**. !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png) diff --git a/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/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 423f53ac6b..46a1815b00 100644 --- a/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/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 @@ -29,7 +29,7 @@ While forks of private repositories are deleted when a collaborator is removed, {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} 4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png) 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 d0aef51457..9083c088b7 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 @@ -20,7 +20,7 @@ topics: shortTitle: Remove yourself --- {% data reusables.user_settings.access_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index d8335fc89f..5c314444e4 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -22,7 +22,7 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% note %} -**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} diff --git a/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 1160178a3c..ff3f745117 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -69,7 +69,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build ``` @@ -106,7 +106,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Run the Gradle package task - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: -b ci.gradle package ``` @@ -135,7 +135,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build - uses: actions/upload-artifact@v2 diff --git a/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index 3e95e6376a..ee474908d4 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -54,9 +54,9 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6 + uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108 with: - ruby-version: 2.6 + ruby-version: '3.1' - name: Install dependencies run: bundle install - name: Run tests @@ -65,7 +65,7 @@ jobs: ## Specifying the Ruby version -The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). +The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information and available Ruby versions, see [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. @@ -75,9 +75,9 @@ The `setup-ruby` action takes a Ruby version as an input and configures that ver ```yaml steps: - uses: actions/checkout@v2 -- uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6 +- uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108 with: - ruby-version: 2.6 # Not needed with a .ruby-version file + ruby-version: '3.1' # Not needed with a .ruby-version file - run: bundle install - run: bundle exec rake ``` @@ -87,13 +87,13 @@ Alternatively, you can check a `.ruby-version` file into the root of your repos ## Testing with multiple versions of Ruby -You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version. +You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 3.1, 3.0, and 2.7. {% raw %} ```yaml strategy: matrix: - ruby-version: [2.7.x, 2.6.x, 2.5.x] + ruby-version: ['3.1', '3.0', '2.7'] ``` {% endraw %} @@ -119,12 +119,12 @@ jobs: strategy: matrix: - ruby-version: [2.7.x, 2.6.x, 2.5.x] + ruby-version: ['3.1', '3.0', '2.7'] steps: - uses: actions/checkout@v2 - name: {% raw %}Set up Ruby ${{ matrix.ruby-version }}{% endraw %} - uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6 + uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108 with: ruby-version: {% raw %}${{ matrix.ruby-version }}{% endraw %} - name: Install dependencies @@ -141,9 +141,9 @@ The `setup-ruby` action will automatically install bundler for you. The version ```yaml steps: - uses: actions/checkout@v2 -- uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6 +- uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108 with: - ruby-version: 2.6 + ruby-version: '3.1' - run: bundle install ``` {% endraw %} @@ -157,7 +157,7 @@ To enable caching, set the following. {% raw %} ```yaml steps: -- uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6 +- uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108 with: bundler-cache: true ``` diff --git a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md index b40a64343b..671a5db72b 100644 --- a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md +++ b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md @@ -89,10 +89,14 @@ This procedure demonstrates how to create the service account for your GKE integ {% raw %} ``` $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ - --member=serviceAccount:$SA_EMAIL \ - --role=roles/container.admin \ - --role=roles/storage.admin \ - --role=roles/container.clusterViewer + --member=serviceAccount:$SA_EMAIL \ + --role=roles/container.admin + $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ + --member=serviceAccount:$SA_EMAIL \ + --role=roles/storage.admin + $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ + --member=serviceAccount:$SA_EMAIL \ + --role=roles/container.clusterViewer ``` {% endraw %} 1. Download the JSON keyfile for the service account: diff --git a/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index b1bd8075ff..52cc87e50c 100644 --- a/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New self-hosted runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %} {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} @@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} @@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise {% data reusables.enterprise-accounts.actions-runners-tab %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product 1. Click **Add new**, then click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} -{% ifversion ghec or ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -{% endif %} ### Making enterprise runners available to repositories diff --git a/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index a0afa6e963..a77a01a315 100644 --- a/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -45,7 +45,7 @@ Self-hosted runners are automatically assigned to the default group when created When creating a group, you must choose a policy that defines which repositories have access to the runner group. -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} @@ -60,12 +60,11 @@ When creating a group, you must choose a policy that defines which repositories {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. In the "Self-hosted runners" section, click **Add new**, and then **New group**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**. ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png) 1. Enter a name for your runner group, and assign a policy for repository access. @@ -94,7 +93,7 @@ Self-hosted runners are automatically assigned to the default group when created When creating a group, you must choose a policy that defines which organizations have access to the runner group. -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -112,8 +111,7 @@ When creating a group, you must choose a policy that defines which organizations {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -143,7 +141,7 @@ When creating a group, you must choose a policy that defines which organizations ## Changing the access policy of a self-hosted runner group You can update the access policy of a runner group, or rename a runner group. -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} 1. Modify the access options, or change the runner group name. @@ -157,8 +155,7 @@ You can update the access policy of a runner group, or rename a runner group. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} @@ -180,20 +177,21 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## Moving a self-hosted runner to a group If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion ghec or ghes > 3.1 or ghae %} + {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} 1. In the "Runners" list, click the runner that you want to configure. 2. Select the Runner group dropdown menu. 3. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} -1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. +{% elsif ghae or ghes < 3.4 %} +1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) 2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} + ## Removing a self-hosted runner group Self-hosted runners are automatically returned to the default group when their group is removed. @@ -203,8 +201,7 @@ Self-hosted runners are automatically returned to the default group when their g 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 2. To remove the group, click **Remove group**. 3. Review the confirmation prompts, and click **Remove this runner group**. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} +{% elsif ghes < 3.2 %} 1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) diff --git a/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 49a1a6d3d0..759f3c3332 100644 --- a/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -30,20 +30,20 @@ shortTitle: Remove self-hosted runners To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Removing a runner from an organization {% note %} @@ -57,19 +57,20 @@ To remove a self-hosted runner from a user repository you must be the repository To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghes > 3.3 or ghec %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% else %} +{% elsif ghes < 3.4 or ghae %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Removing a runner from an enterprise {% ifversion fpt %} @@ -84,18 +85,17 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove {% endnote %} -{% data reusables.github-actions.self-hosted-runner-reusing %} +To remove a self-hosted runner from an enterprise, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). -{% ifversion ghec %} -To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). +{% data reusables.github-actions.self-hosted-runner-reusing %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% elsif ghae or ghes %} -To remove a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 42ac880513..4b4b6edb5b 100644 --- a/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -19,14 +19,14 @@ For information on how to use labels to route jobs to specific types of self-hos {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} ## Creating a custom label -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}. 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**. The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} @@ -36,34 +36,37 @@ For information on how to use labels to route jobs to specific types of self-hos The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## Assigning a label to a self-hosted runner -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. Click on a label to assign it to your self-hosted runner. {% endif %} + ## Removing a custom label from a self-hosted runner -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## Using the configuration script to create and assign labels You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner. diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md index ffad10c4e1..bf23322ffd 100644 --- a/content/actions/learn-github-actions/contexts.md +++ b/content/actions/learn-github-actions/contexts.md @@ -76,7 +76,7 @@ The following table indicates where each context and special function can be use | concurrency | github, inputs | | | env | github, secrets, inputs | | | jobs.<job_id>.concurrency | github, needs, strategy, matrix, inputs | | -| jobs.<job_id>.container | github, needs, strategy, matrix, inputs | | +| jobs.<job_id>.container | github, needs, strategy, matrix, secrets, inputs | | | jobs.<job_id>.container.credentials | github, needs, strategy, matrix, env, secrets, inputs | | | jobs.<job_id>.container.env.<env_id> | github, needs, strategy, matrix, job, runner, env, secrets, inputs | | | jobs.<job_id>.continue-on-error | github, needs, strategy, matrix, inputs | | 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/publishing-packages/publishing-java-packages-with-gradle.md b/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index b406a3b1a0..41f661c6f7 100644 --- a/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -96,7 +96,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -167,7 +167,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -246,7 +246,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: {% raw %} diff --git a/content/actions/security-guides/automatic-token-authentication.md b/content/actions/security-guides/automatic-token-authentication.md index b86900fd20..8394d835de 100644 --- a/content/actions/security-guides/automatic-token-authentication.md +++ b/content/actions/security-guides/automatic-token-authentication.md @@ -85,8 +85,8 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau | actions | read/write | none | read | | checks | read/write | none | read | | contents | read/write | read | read | -| deployments | read/write | none | read | -| id-token | read/write | none | read | +| deployments | read/write | none | read |{% ifversion fpt or ghec %} +| id-token | read/write | none | read |{% endif %} | issues | read/write | none | read | | metadata | read | read | read | | packages | read/write | none | read | diff --git a/content/actions/security-guides/security-hardening-for-github-actions.md b/content/actions/security-guides/security-hardening-for-github-actions.md index 13e8802953..eacf476ed3 100644 --- a/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/content/actions/security-guides/security-hardening-for-github-actions.md @@ -202,6 +202,10 @@ The same principles described above for using third-party actions also apply to {% data reusables.actions.outside-collaborators-internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." {% endif %} +## Using OpenSSF Scorecards to secure workflows + +[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions. + ## Potential impact of a compromised runner These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. 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`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | Last commit in the tagged release | Tag of release | +| [`release`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | Last commit in the tagged release | Tag ref of release `refs/tags/` | {% note %} diff --git a/content/actions/using-workflows/workflow-commands-for-github-actions.md b/content/actions/using-workflows/workflow-commands-for-github-actions.md index f2cd424a80..d9c7e21aa1 100644 --- a/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -313,7 +313,9 @@ During the execution of a workflow, the runner generates temporary files that ca {% warning %} -**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. Make sure you write files using the correct encoding. For example, you need to set UTF-8 encoding when you set the path: +**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. + +When using `shell: powershell`, you must specify UTF-8 encoding. For example: ```yaml jobs: @@ -324,21 +326,7 @@ jobs: run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Or switch to PowerShell Core, which defaults to UTF-8: - -```yaml -jobs: - modern-pwsh-example: - uses: windows-2019 - steps: - - shell: pwsh - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8 -``` - -More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow answer](https://stackoverflow.com/a/40098904/162694): - -> ### Optional reading: The cross-platform perspective: PowerShell _Core_: -> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - **defaults to *BOM-less UTF-8***, in line with Unix-like platforms. +Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8. {% endwarning %} 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 f3c3379e0b..440edcc597 100644 --- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -757,6 +757,8 @@ strategy: ## `jobs..container` +{% data reusables.github-actions.docker-container-os-support %} + {% data reusables.actions.jobs.section-running-jobs-in-a-container %} ### `jobs..container.image` diff --git a/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index 5026c04d1a..21a26ccc9c 100644 --- a/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -70,7 +70,22 @@ If you set up the {% data variables.product.prodname_codeql %} action sync tool, 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + +## Running code scanning using the {% data variables.product.prodname_codeql_cli %} + +If you don't want to use {% data variables.product.prodname_actions %}, you should run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %}. + +The {% data variables.product.prodname_codeql_cli %} is a command-line tool that you use to analyze codebases on any machine, including a third-party CI/CD system. For more information, see "[Installing CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." + + +{% if codeql-runner-supported %} + ## Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} + +{% data reusables.code-scanning.deprecation-codeql-runner %} + If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." + +{% endif %} \ No newline at end of file diff --git a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 61e750cc30..e92b04b449 100644 --- a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -458,6 +458,16 @@ You can use these additional options with the utility: ghe-ssl-ca-certificate-install -c /path/to/certificate ``` +### ghe-ssl-certificate-setup + +This utility allows you to update an SSL certificate for {% data variables.product.product_location %}. + +For more information about this command or for additional options, use the `-h` flag. + +```shell +ghe-ssl-certificate-setup +``` + ### ghe-ssl-generate-csr This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." @@ -699,7 +709,7 @@ All Storage tests passed `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}. -For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/). +For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). ### git-import-detect diff --git a/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md index 40a22785f7..f1207be0a5 100644 --- a/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md +++ b/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md @@ -79,3 +79,7 @@ If your {% data variables.product.prodname_ghe_server %} appliance interacts wit ```shell $ ghe-ssl-ca-certificate-install -c rootCA.crt ``` + +## Updating an SSL certificate + +You can generate a new self-signed certificate or update an existing SSL certificate for {% data variables.product.product_location %} with the `ghe-ssl-certificate-setup` command line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-setup)." \ No newline at end of file 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/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 8dba3031c4..5d4788be74 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -19,6 +19,8 @@ shortTitle: Add actions in your enterprise {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +## About actions on {% data variables.product.product_name %} + {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. {% data reusables.actions.enterprise-no-internet-actions %} @@ -39,8 +41,14 @@ Each action is a repository in the `actions` organization, and each action repos ## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} +{% ifversion ghes %} +Before you can configure access to actions on {% data variables.product.prodname_dotcom_the_website %}, you must configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +{% endif %} + {% data reusables.actions.access-actions-on-dotcom %} -The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %} +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +{% data reusables.actions.enterprise-limit-actions-use %} Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index d3ee731724..3535c80c42 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -29,9 +29,11 @@ To use actions from {% data variables.product.prodname_dotcom_the_website %}, yo ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions -{% data reusables.actions.enterprise-github-connect-warning %} +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} for your enterprise, you must{% ifversion ghes %}: +- Configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +- Enable{% else %} enable{% endif %} {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." +{% data reusables.actions.enterprise-github-connect-warning %} {% data reusables.enterprise-accounts.access-enterprise %} {%- ifversion ghes < 3.1 %} diff --git a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md index 7645108960..d7d6f208f7 100644 --- a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md +++ b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md @@ -46,7 +46,7 @@ IdP | SAML | Team synchronization | --- | :--: | :-------: | 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" %} | +Okta | {% 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/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md index a7050867ed..df44d96e0e 100644 --- a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md @@ -33,6 +33,10 @@ redirect_from: {% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." +{% data reusables.saml.cannot-update-existing-saml-settings %} + +{% data reusables.saml.saml-disabled-linked-identities-removed %} + {% data reusables.scim.enterprise-account-scim %} {% elsif ghae %} diff --git a/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md index 69ae03d4eb..f2139298f9 100644 --- a/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md +++ b/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -25,6 +25,8 @@ With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO t After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. For more information, see "[Saving your recovery codes](#saving-your-recovery-codes)." +{% data reusables.saml.cannot-update-existing-saml-settings %} + ## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} To configure SAML SSO for your {% data variables.product.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. diff --git a/content/admin/index.md b/content/admin/index.md index 7b8cedcc2b..d34933c907 100644 --- a/content/admin/index.md +++ b/content/admin/index.md @@ -10,9 +10,7 @@ redirect_from: - /github/installing-and-configuring-github-insights/key-metrics-for-collaboration-in-pull-requests - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization + - /github/site-policy/github-insights-and-data-protection-for-your-organization - /insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise - /github/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise @@ -134,4 +132,3 @@ children: - /release-notes - /all-releases --- - diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md index 949c933e99..de27d99c43 100644 --- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md +++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md @@ -10,7 +10,7 @@ redirect_from: - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account - - github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account versions: ghec: '*' ghes: '*' @@ -73,7 +73,7 @@ Enterprise owners can restrict access to assets owned by organizations in an ent {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %} -{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} +{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md index f3d8b48da6..689660934f 100644 --- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md +++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md @@ -98,7 +98,7 @@ shortTitle: Export from your enterprise > logout > Connection to hostname closed. ``` -9. Copy the migration archive to your computer using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID: +9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID: ```shell $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop ``` diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md index 12b0ae88e1..177d878409 100644 --- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md +++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md @@ -19,7 +19,7 @@ shortTitle: Prepare to migrate data --- ## Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %} -1. Using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target: +1. Using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target: ```shell $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/ @@ -43,7 +43,7 @@ shortTitle: Prepare to migrate data $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv ``` - If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)". -2. If there are conflicts, using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer: +2. If there are conflicts, using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer: ```shell $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop ``` @@ -133,7 +133,7 @@ The same process can be used to create mappings for each record that supports cu ### Applying modified migration data -1. After making changes, use the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance: +1. After making changes, use the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance: ```shell $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/ diff --git a/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index cd89fcbb59..a7f9bb720f 100644 --- a/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -19,10 +19,9 @@ You can authorize an existing personal access token, or [create a new personal a {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -3. Next to the token you'd like to authorize, click **Enable SSO** or **Disable SSO**. - ![SSO token authorize button](/assets/images/help/settings/sso-allowlist-button.png) -4. Find the organization you'd like to authorize the access token for. -4. Click **Authorize**. +3. Next to the token you'd like to authorize, click **Configure SSO**. + ![Screenshot of the dropdown menu to configure SSO for a personal access token](/assets/images/help/settings/sso-allowlist-button.png) +4. To the right of the organization you'd like to authorize the token for, click **Authorize**. ![Token authorize button](/assets/images/help/settings/token-authorize-button.png) ## Further reading diff --git a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md index 480901f678..858faf9151 100644 --- a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md +++ b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md @@ -29,7 +29,7 @@ You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP add These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds. -These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges. +These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool to convert from CIDR notation to IP address ranges, for example: [CIDR to IPv4 conversion site](https://www.ipaddressguide.com/cidr). We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API. 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 7fef226524..ebba929003 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,7 +17,7 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index 7c4aa867d4..03a5ca35b7 100644 --- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -21,7 +21,7 @@ shortTitle: Security log The security log lists all actions performed within the last 90 days. {% data reusables.user_settings.access_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 1. In the user settings sidebar, click **Security log**. diff --git a/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 8ca974ea4b..fe97513d90 100644 --- a/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -24,7 +24,7 @@ shortTitle: Update access credentials 2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) 3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. -4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**. +4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your authentication code or one of your recovery codes and click **Verify**. If you have added a security key to your account, you can insert the key and click **Use security key** instead of typing an authentication code. ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png) 5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)." {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} 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..021e173134 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 up to three 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 three 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/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index d4af46b468..4404dabc62 100644 --- a/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -75,7 +75,7 @@ At the end of the month, {% data variables.product.prodname_dotcom %} calculates ### Sample minutes cost calculation -For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. +For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. - 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD). - 3,000 Linux minutes at $0.008 USD per minute = $24 USD. diff --git a/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md index 9ab94e5001..d3200508d6 100644 --- a/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md +++ b/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md @@ -54,11 +54,13 @@ Enterprise owners and billing managers can manage the spending limit for {% data {% data reusables.codespaces.exporting-changes %} ## Managing usage and spending limit email notifications -Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit. +Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit. You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. +![Screenshot of the billing email notification settings](/assets/images/help/billing/codespaces-spending-limit-notifications.png) + ## Further reading - "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" -- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)" \ No newline at end of file +- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)" diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index af256d5d03..c5a58625aa 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -29,14 +29,17 @@ shortTitle: Configure code scanning {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} +{% ifversion ghes or ghae %} +{% note %} + +**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} + +{% endnote %} +{% endif %} + ## About {% data variables.product.prodname_code_scanning %} configuration -You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or -{%- ifversion fpt or ghes > 3.0 or ghae %} -"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." -{%- else %} -"[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." -{% endif %} +You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions. diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index 1d95a64c7d..728fb5b8ea 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -25,17 +25,12 @@ topics: {% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.deprecation-codeql-runner %} ## About {% data variables.product.prodname_code_scanning %} with a containerized build If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled. -{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)." -{% else %} -You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)." -{% endif %} +You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}{% if codeql-runner-supported %}, the {% data variables.product.prodname_codeql_runner %},{% endif %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} {% if codeql-runner-supported %}or the {% data variables.product.prodname_codeql_runner %}{% endif %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)"{% if codeql-runner-supported %} or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)." ## Dependencies @@ -47,6 +42,14 @@ You may have difficulty running {% data variables.product.prodname_code_scanning ## Example workflow +{% ifversion ghes or ghae %} +{% note %} + +**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container) for information on the latest features.{% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} + +{% endnote %} +{% endif %} + This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)." ``` yaml diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 49df6f9929..ba3abc88d4 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -43,6 +43,14 @@ Enterprise owners, organization and repository administrators can add self-hoste ## Setting up {% data variables.product.prodname_code_scanning %} using actions +{% ifversion ghes or ghae %} +{% note %} + +**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} + +{% endnote %} +{% endif %} + {% ifversion fpt or ghec %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %} {% data reusables.repositories.navigate-to-repo %} diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index c60e7ff48f..e2f6f8c0c1 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -31,6 +31,14 @@ topics: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.not-available %} +{% ifversion ghes or ghae %} +{% note %} + +**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} + +{% endnote %} +{% endif %} + ## Producing detailed logs for debugging To produce more detailed logging output, you can enable step debug logging. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)." diff --git a/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index c1fc8e6166..88765f488b 100644 --- a/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -24,7 +24,6 @@ topics: {% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.deprecation-codeql-runner %} ## About SARIF support @@ -32,10 +31,7 @@ SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https: To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json). -If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. 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)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." - -{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} +If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %}{% if codeql-runner-supported %}, using the {% data variables.product.prodname_codeql_runner %},{% endif %} or using the {% data variables.product.prodname_codeql_cli %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. 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)"{% if codeql-runner-supported %}, "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)",{% endif %} or "[Installing CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." {% ifversion fpt or ghes > 3.1 or ghae or ghec %} You can upload multiple SARIF files for the same commit, and display the data from each file as {% data variables.product.prodname_code_scanning %} results. When you upload multiple SARIF files for a commit, you must indicate a "category" for each analysis. The way to specify a category varies according to the analysis method: @@ -57,7 +53,7 @@ Each time the results of a new code scan are uploaded, the results are processed {% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. -SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." +SARIF files created by the {% data variables.product.prodname_codeql_workflow %}, {% if codeql-runner-supported %}using the {% data variables.product.prodname_codeql_runner %}, {% endif %}or using the {% data variables.product.prodname_codeql_cli %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)." diff --git a/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md index 0beaf40ec0..8f21ec78df 100644 --- a/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md +++ b/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md @@ -28,7 +28,6 @@ topics: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -{% data reusables.code-scanning.deprecation-codeql-runner %} ## About SARIF file uploads for {% data variables.product.prodname_code_scanning %} @@ -36,12 +35,12 @@ topics: You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)." -You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use: +You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API,{% if codeql-runner-supported %} the {% data variables.product.prodname_codeql_runner %},{% endif %} or the {% data variables.product.prodname_codeql_cli %}. The best upload method will depend on how you generate the SARIF file, for example, if you use: - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis. -- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). {% ifversion fpt or ghes > 3.0 or ghae or ghec %} - - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% endif %} -- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"). +- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). + - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% if codeql-runner-supported %} +- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %} - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"). {% data reusables.code-scanning.not-available %} @@ -143,7 +142,6 @@ jobs: ## Further reading - "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" -- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- ifversion fpt or ghes > 3.0 or ghae %} -- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %} -- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} +- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)" +- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)" - "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)" diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index c8ad424e59..16ce02b338 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -54,9 +54,9 @@ For more information, see "[Installing {% data variables.product.prodname_codeql {% data reusables.code-scanning.licensing-note %} {% ifversion ghes = 3.2 %} - + -{% data reusables.code-scanning.use-codeql-runner-not-cli %} +Since version 2.6.3, the {% data variables.product.prodname_codeql_cli %} has had full feature parity with the {% data variables.product.prodname_codeql_runner %}. {% data reusables.code-scanning.deprecation-codeql-runner %} @@ -65,39 +65,25 @@ For more information, see "[Installing {% data variables.product.prodname_codeql {% endif %} -{% ifversion ghes = 3.1 %} +{% ifversion ghes < 3.2 %} You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}. +[{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.6.3 is available now for {% data variables.product.prodname_ghe_server %} 3.0 and later versions. For more information on migrating to the {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." + {% data reusables.code-scanning.upload-sarif-ghas %} ## Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %} {% data reusables.code-scanning.what-is-codeql-cli %} -The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case. +The {% data variables.product.prodname_codeql_runner %} is a deprecated command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. -Use the {% data variables.product.prodname_codeql_cli %} to analyze: - -- Dynamic languages, for example, JavaScript and Python. -- Codebases with a compiled language that can be built with a single command or by running a single script. +{% data variables.product.prodname_codeql_cli %} 2.6.3 is a complete replacement for the runner with full feature parity. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly. For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." -{% data reusables.code-scanning.use-codeql-runner-not-cli %} - {% data reusables.code-scanning.deprecation-codeql-runner %} -For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." +For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." -{% endif %} - - -{% ifversion ghes = 3.0 %} -{% data reusables.code-scanning.upload-sarif-ghas %} - -You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}. - -{% data reusables.code-scanning.deprecation-codeql-runner %} - -To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." -{% endif %} +{% endif %} \ No newline at end of file diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 0ecb4a0c59..16d884751c 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -8,7 +8,7 @@ redirect_from: - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system versions: fpt: '*' - ghes: '>=3.1' + ghes: '>=3.0' ghae: '*' ghec: '*' type: how_to @@ -24,6 +24,14 @@ topics: --- {% data reusables.code-scanning.enterprise-enable-code-scanning %} +{% ifversion ghes or ghae %} +{% note %} + +**Note:** This article describes features present in the version of {% data variables.product.prodname_codeql_cli %} available at the time of the release of {% data variables.product.product_name %}. If your enterprise uses a more recent version of {% data variables.product.prodname_codeql_cli %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system) instead. + +{% endnote %} +{% endif %} + ## About generating code scanning results with {% data variables.product.prodname_codeql_cli %} Once you've made the {% data variables.product.prodname_codeql_cli %} available to servers in your CI system, and ensured that they can authenticate with {% data variables.product.product_name %}, you're ready to generate data. @@ -329,22 +337,6 @@ By default, {% data variables.product.prodname_code_scanning %} expects one SARI If you want to upload more than one set of results to the {% data variables.product.prodname_code_scanning %} API for a commit in a repository, you must identify each set of results as a unique set. For repositories where you create more than one {% data variables.product.prodname_codeql %} database to analyze for each commit, use the `--sarif-category` option to specify a language or other unique category for each SARIF file that you generate for that repository. -### Alternative if your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} - -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} - -If your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} autobuild and you cannot specify a command line for the build, you can use indirect build tracing to create {% data variables.product.prodname_codeql %} databases for compiled languages. For more information, see [Using indirect build tracing](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) in the documentation for the {% data variables.product.prodname_codeql_cli %}. - -{% endif %} - -{% ifversion ghes < 3.3 %} - -{% data reusables.code-scanning.use-codeql-runner-not-cli %} - -{% data reusables.code-scanning.deprecation-codeql-runner %} - -{% endif %} - {% endif %} ## Further reading diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index 6105ca77b6..41a315479f 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -11,10 +11,7 @@ redirect_from: - /code-security/secure-coding/configuring-codeql-runner-in-your-ci-system - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: 'codeql-runner-supported' type: how_to topics: - Advanced Security diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md index fbd14eae91..89fab216d9 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md @@ -6,7 +6,7 @@ product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 versions: fpt: '*' - ghes: '>=3.1' + ghes: '>=3.0' ghae: '*' ghec: '*' type: how_to @@ -44,6 +44,17 @@ You should download the {% data variables.product.prodname_codeql %} bundle from - A compatible version of the queries and libraries from https://github.com/github/codeql - Precompiled versions of all the queries included in the bundle +{% ifversion ghes %} + +{% note %} +{% ifversion ghes = 3.0 %}For {% data variables.product.prodname_ghe_server %} 3.0, we recommend {% data variables.product.prodname_codeql_cli %} version 2.6.3.{% endif %} +{% ifversion ghes = 3.1 %}For {% data variables.product.prodname_ghe_server %} 3.1, we recommend {% data variables.product.prodname_codeql_cli %} version 2.6.3.{% endif %} +{% ifversion ghes = 3.2 %}For {% data variables.product.prodname_ghe_server %} 3.2, we recommend {% data variables.product.prodname_codeql_cli %} version 2.6.3.{% endif %} +{% ifversion ghes > 3.2 %}For {% data variables.product.prodname_ghe_server %} 3.3 and greater, we recommend {% data variables.product.prodname_codeql_cli %} version 2.7.6 or greater.{% endif %} +{% endnote %} + +{% endif %} + You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms. {% data reusables.code-scanning.beta-codeql-packs-cli %} diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index e7a43d0f10..29d3758a0b 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -5,7 +5,7 @@ intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to comp product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' - ghes: '>=3.1' + ghes: '>=3.0' ghae: '*' ghec: '*' topics: diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index 74078a9855..4bfcdfa805 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -28,6 +28,8 @@ topics: +{% if codeql-runner-supported %} + {% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} @@ -182,3 +184,17 @@ This example is similar to the previous example, however this time the repositor - "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)" - "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)" + +{% else %} + +## About the {% data variables.product.prodname_codeql_runner %} + +The {% data variables.product.prodname_codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity. + +For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." + +## Further reading + +- [CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) in the GitHub Blog + +{% endif %} \ No newline at end of file diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md index 13bf915705..2558ebaa9b 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md @@ -10,10 +10,7 @@ redirect_from: - /code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: 'codeql-runner-supported' 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/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md index 25412c70df..d27d4e08ce 100644 --- a/content/code-security/getting-started/securing-your-organization.md +++ b/content/code-security/getting-started/securing-your-organization.md @@ -36,7 +36,7 @@ You can create a default security policy that will display in any of your organi {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. 1. Click your profile photo, then click **Organizations**. 2. Click **Settings** next to your organization. diff --git a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 947533b214..6e7ae7a841 100644 --- a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -67,7 +67,14 @@ Before defining a custom pattern, you must ensure that {% data variables.product {% data reusables.repositories.navigate-to-security-and-analysis %} {% data reusables.repositories.navigate-to-ghas-settings %} {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} -{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} +1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**. +1. When the dry run finishes, you'll see a sample of results (up to 1000) from the repository. Review the results and identify any false positive results. + ![Screenshot showing results from dry run](/assets/images/help/repository/secret-scanning-publish-pattern.png) +1. Edit the new custom pattern to fix any problems with the results, then click **Save and dry run** to test your changes. +{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %} +{% endif %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." @@ -116,6 +123,7 @@ Before defining a custom pattern, you must ensure that you enable {% data variab {% data reusables.repositories.navigate-to-ghas-settings %} {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." @@ -139,6 +147,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin {% data reusables.enterprise-accounts.advanced-security-security-features %} 1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." diff --git a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index a4c299c3dd..9b97e577a9 100644 --- a/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -30,11 +30,17 @@ shortTitle: Use Dependabot with Actions {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently. -For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply: +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply: +{% endif %} - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %} - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available. +{% endif %} + For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). {% ifversion fpt or ghec or ghes > 3.3 %} diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 8b835ed644..9a41ccbd2a 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -58,7 +58,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md index 6d2de3a534..f0e5dc57aa 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md @@ -46,8 +46,6 @@ There are three reasons why an alert may have no pull request link: If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert. -![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) - ## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %} When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab. diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 2e0ad140d1..4a967cf2fb 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -103,17 +103,17 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the {% ifversion fpt or ghec %} ## Does each dependency vulnerability generate a separate alert? -When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability. +When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png) +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. -When you click to display the alert details, you can see how many vulnerabilities are included in the alert. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png) +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} ## Further reading diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index c2a6b0c128..4029faa7f6 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -25,7 +25,7 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% ifversion fpt or ghec or ghes > 3.2 %} You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." @@ -37,11 +37,30 @@ You can enable automatic security updates for any repository that uses {% data v ## About updates for vulnerable dependencies in your repository {% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. + +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`). + +Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %} {% endif %} ## Viewing and updating vulnerable dependencies -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-dependabot-alerts %} +1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. + ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png) +1. Click the alert that you would like to view. + ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png) +1. Review the details of the vulnerability and, if available, the pull request containing the automated security update. +1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**. + ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) +1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, 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)." +1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. + ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) + +{% elsif ghes = 3.3 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} @@ -54,7 +73,7 @@ You can enable automatic security updates for any repository that uses {% data v 1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) -{% elsif ghes > 3.0 or ghae-issue-4864 %} +{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 9dfc90486b..0956aede41 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -88,7 +88,7 @@ The recommended formats explicitly define which versions are used for all direct | 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`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | -{%- ifversion fpt or ghes > 3.3 %} +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} | 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` | diff --git a/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md index 89bcf4cde1..74c583d24e 100644 --- a/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md +++ b/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md @@ -21,6 +21,8 @@ You can report users that have violated {% data variables.product.prodname_dotco If reported content is enabled for a public repository, you can also report content directly to repository maintainers. +Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer). + ## Reporting a user {% data reusables.profile.user_profile_page_navigation %} 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/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md index edf1015910..a23805bf67 100644 --- a/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md +++ b/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md @@ -60,4 +60,4 @@ For an example of an incident response workflow, see the "Data Breach Response P You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. -If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)." diff --git a/content/developers/overview/github-developer-program.md b/content/developers/overview/github-developer-program.md index 96e2797844..ddbde08f70 100644 --- a/content/developers/overview/github-developer-program.md +++ b/content/developers/overview/github-developer-program.md @@ -28,7 +28,7 @@ Email partnerships@github.com to re ## Have an integration that works with GitHub? Awesome! We'd love to have you be part of the program. Here’s how you can spread the word:

-* [Let us know about your integration](https://github.com/contact?form[subject]=New+GitHub+Integration) +* [Let us know about your integration](https://support.github.com/contact?tags=rr-general-technical&form[subject]=New+GitHub+Integration) * Use the [Octocat or GitHub logo](https://github.com/logos) to identify that your product works with GitHub * Post a video or a blog on your website about your integration diff --git a/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 086fc51c68..e477a3f6a3 100644 --- a/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -45,10 +45,10 @@ You can integrate your personal or organization account on {% data variables.pro ### 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. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, 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. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, 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/content/get-started/getting-started-with-git/managing-remote-repositories.md b/content/get-started/getting-started-with-git/managing-remote-repositories.md index 0914d2a7ea..e61fe385d4 100644 --- a/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -194,6 +194,8 @@ Use the `git remote rm` command to remove a remote URL from your repository. The `git remote rm` command takes one argument: * A remote name, for example, `destination` +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. + ## Example These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. diff --git a/content/get-started/learning-about-github/about-github-advanced-security.md b/content/get-started/learning-about-github/about-github-advanced-security.md index c8b27e59df..0231b06a5a 100644 --- a/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/content/get-started/learning-about-github/about-github-advanced-security.md @@ -36,10 +36,31 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **Security overview** - Review the security configuration and alerts for an 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 %} +{% ifversion fpt or ghec %} +The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. + +{% ifversion fpt %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | +| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | +| Code scanning | Yes | No | Yes | +| Secret scanning | Yes **(limited functionality only)** | No | Yes | +| Dependency review | Yes | No | Yes | +{% endif %} +{% ifversion ghec %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | +| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | +| Code scanning | Yes | No | Yes | +| Secret scanning | Yes **(limited functionality only)** | No | Yes | +| Dependency review | Yes | No | Yes | +| Security overview | No | No | Yes | +{% endif %} + +{% endif %} + For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion fpt or ghec %} -{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} {% ifversion ghes or ghec %} @@ -59,9 +80,9 @@ The site administrator must enable {% data variables.product.prodname_advanced_s Once your system is set up, you can enable and disable these features at the organization or repository level. {%- elsif ghec %} -For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. +For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {%- elsif ghae %} You can enable and disable these features at the organization or repository level. diff --git a/content/get-started/using-git/about-git-rebase.md b/content/get-started/using-git/about-git-rebase.md index e6fc3b9603..008dcea289 100644 --- a/content/get-started/using-git/about-git-rebase.md +++ b/content/get-started/using-git/about-git-rebase.md @@ -2,7 +2,7 @@ title: About Git rebase redirect_from: - /rebase - - articles/interactive-rebase/ + - /articles/interactive-rebase - /articles/about-git-rebase - /github/using-git/about-git-rebase - /github/getting-started-with-github/about-git-rebase diff --git a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 4956d47f3f..07bf02fa30 100644 --- a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -24,6 +24,11 @@ To create a heading, add one to six # symbols before your heading tex ![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png) +When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section. + +![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png) + + ## Styling text You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files. diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md index 46ca346425..b9f21c56e7 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md @@ -66,6 +66,13 @@ For example, to syntax highlight Ruby code: We use [Linguist](https://github.com/github/linguist) to perform language detection and to select [third-party grammars](https://github.com/github/linguist/blob/master/vendor/README.md) for syntax highlighting. You can find out which keywords are valid in [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). +{% if mermaid %} +## Creating diagrams + +You can use Mermaid syntax to add diagrams. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)." + +{% endif %} + ## Further reading - [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md new file mode 100644 index 0000000000..4f4f1a2e26 --- /dev/null +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -0,0 +1,33 @@ +--- +title: Creating diagrams +intro: Create diagrams to convey information through charts and graphs +versions: + feature: mermaid +shortTitle: Create diagrams +--- + +You can use Mermaid syntax to create diagrams. Mermaid is a Markdown-inspired tool that renders text into diagrams. For example, Mermaid can render flow charts, sequence diagrams, pie charts and more. For more information, see the [Mermaid documentation](https://mermaid-js.github.io/mermaid/#/). + +To create a Mermaid diagram, add Mermaid syntax inside a fenced code block with the `mermaid` language identifier. For more information about creating code blocks, see "[Creating and highlighting code blocks](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)." + +For example, you can create a flow chart: + +
+Here is a simple flow chart:
+
+```mermaid
+graph TD;
+    A-->B;
+    A-->C;
+    B-->D;
+    C-->D;
+```
+
+ +![Rendered Mermaid flow chart](/assets/images/help/writing/mermaid-flow-chart.png) + +{% note %} + +**Note:** You may observe errors if you run a third-party Mermaid plugin when using Mermaid syntax on {% data variables.product.company_short %}. + +{% endnote %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index 26651f391d..9e52880793 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -13,6 +13,7 @@ children: - /organizing-information-with-tables - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks + - /creating-diagrams - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/content/github/site-policy/github-community-guidelines.md b/content/github/site-policy/github-community-guidelines.md index 7011d661da..aafe5ee415 100644 --- a/content/github/site-policy/github-community-guidelines.md +++ b/content/github/site-policy/github-community-guidelines.md @@ -23,7 +23,7 @@ We want people to work better together. Although we maintain the site, this is a * **Be welcoming and open-minded** - Other collaborators may not have the same experience level or background as you, but that doesn't mean they don't have good ideas to contribute. We encourage you to be welcoming to new collaborators and those just getting started. -* **Respect each other.** Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions. +* **Respect each other** - Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions. You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Avoid name-calling, ad hominem attacks, responding to a post’s tone instead of its actual content, and knee-jerk contradiction. Instead, provide reasoned counter-arguments that improve the conversation. diff --git a/content/github/site-policy/submitting-content-removal-requests.md b/content/github/site-policy/submitting-content-removal-requests.md index 47ed2f1985..6b9e4bf1af 100644 --- a/content/github/site-policy/submitting-content-removal-requests.md +++ b/content/github/site-policy/submitting-content-removal-requests.md @@ -23,3 +23,5 @@ The GitHub Trademark Policy can be used to report content that appears to use yo ## [GitHub Private Information Removal Policy](/github/site-policy/github-private-information-removal-policy) The GitHub Private Information Removal Policy can be used to report data that is private (confidential and poses a security risk), but that is not necessarily protected by copyright or trademark. + +Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer). diff --git a/content/graphql/overview/about-the-graphql-api.md b/content/graphql/overview/about-the-graphql-api.md index 383475690c..cecb92c150 100644 --- a/content/graphql/overview/about-the-graphql-api.md +++ b/content/graphql/overview/about-the-graphql-api.md @@ -12,7 +12,7 @@ topics: ## Overview -Here are some quick links to get you up and running with the GraphQL API v4: +Here are some quick links to get you up and running with the GraphQL API: * [Authentication](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) * [Root endpoint](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) @@ -36,9 +36,9 @@ The [GraphQL](https://graphql.github.io/) data query language is: ## Why GitHub is using GraphQL -GitHub chose GraphQL for our API v4 because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over the REST API v3 endpoints. GraphQL lets you replace multiple REST requests with _a single call_ to fetch the data you specify. +GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. GraphQL lets you replace multiple REST requests with _a single call_ to fetch the data you specify. -For more details about why GitHub has moved to GraphQL, see the original [announcement blog post](https://githubengineering.com/the-github-graphql-api/). +For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/). ## About the GraphQL schema reference diff --git a/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md index ad79f17b59..be212dc476 100644 --- a/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md +++ b/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md @@ -27,6 +27,20 @@ To track how smaller issues fit into the larger goal, use task lists, milestones Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected. +## Make use of the description and README + +Use your project's description and README to share information about the project. + +For example: + +- Explaining the purpose of the project. +- Describing the project views and how to use them. +- Including relevant links and people to contact for more information. + +Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. + +For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#updating-your-project-description-and-readme)." + ## Use views Use project views to look at your project from different angles. diff --git a/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/content/issues/trying-out-the-new-projects-experience/creating-a-project.md index 9f0e4cc09d..6c71d9d2f5 100644 --- a/content/issues/trying-out-the-new-projects-experience/creating-a-project.md +++ b/content/issues/trying-out-the-new-projects-experience/creating-a-project.md @@ -25,6 +25,10 @@ Projects are a customizable collection of items that stay up-to-date with {% dat {% data reusables.projects.create-user-project %} +## Updating your project description and README + +{% data reusables.projects.project-description %} + ## Adding items to your project Your project can track draft issues, issues, and pull requests. diff --git a/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md index 0e92893d8d..c0e785f37e 100644 --- a/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md +++ b/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md @@ -15,7 +15,7 @@ topics: ## About project access -Admins of organization-level projects can manage access for the entire organization, for teams, and for individual organization members. +Admins of organization-level projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators. Admins of user-level projects can invite individual collaborators and manage their access. @@ -37,18 +37,18 @@ The default base role is `write`, meaning that everyone in the organization can ### Managing access for teams and individual members of your organization -You can also add teams, and individual organization members, as collaborators. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." +You can also add teams, external collaborators, and individual organization members as collaborators for an organization-level project. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." -You can only invite an individual user to collaborate on your organization-level project if they are a member of the organization. +You can only invite an individual user to collaborate on your organization-level project if they are already a member of the organization or an outside collaborator on at least one repository in the organization. {% data reusables.projects.project-settings %} 1. Click **Manage access**. -1. Under **Invite collaborators**, search for the team or organization member that you want to invite. -1. Select the role for the collaborator. +2. Under **Invite collaborators**, search for the team or individual user that you want to invite. +3. Select the role for the collaborator. - **Read**: The team or individual can view the project. - **Write**: The team or individual can view and edit the project. - **Admin**: The team or individual can view, edit, and add new collaborators to the project. -1. Click **Invite**. +4. Click **Invite**. ### Managing access of an existing collaborator on your project diff --git a/content/issues/trying-out-the-new-projects-experience/quickstart.md b/content/issues/trying-out-the-new-projects-experience/quickstart.md index 35106a7f2e..3b08dca27d 100644 --- a/content/issues/trying-out-the-new-projects-experience/quickstart.md +++ b/content/issues/trying-out-the-new-projects-experience/quickstart.md @@ -35,6 +35,10 @@ First, create an organization project or a user project. {% data reusables.projects.create-user-project %} +## Setting your project description and README + +{% data reusables.projects.project-description %} + ## Adding issues to your project Next, add a few issues to your project. diff --git a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md index 30113d0498..fa774f0930 100644 --- a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md +++ b/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md @@ -365,6 +365,43 @@ The response will contain the node ID of the newly created item. If you try to add an item that already exists, the existing item ID is returned instead. +### Updating a project's settings + +The following example will update your project's settings. Replace `PROJECT_ID` with the node ID of your project. Set `public` to `true` to make your project public on {% data variables.product.product_name %}. Modify `description` to make changes to your project's README. + +{% curl %} +```shell +curl --request POST \ +--url https://api.github.com/graphql \ +--header 'Authorization: token TOKEN' \ +--data '{"query":"mutation { updateProjectNext(input: { projectId: \"PROJECT_ID\", title: \"Project title\", public: false, description: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectNext { id, title, description, shortDescription }}}"}' +``` +{% endcurl %} + +{% cli %} +```shell +gh api graphql -f query=' + mutation { + updateProjectNext( + input: { + projectId: "PROJECT_ID", + title: "Project title", + public: false, + description: "# Project README\n\nA long description", + shortDescription: "A short description" + } + ) { + projectNext { + id + title + description + shortDescription + } + } + }' +``` +{% endcli %} + ### Updating a custom text, number, or date field The following example will update the value of a date field for an item. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to update. Replace `FIELD_ID` with the ID of the field that you want to update. diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md index ad7be37a60..72722f6626 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md @@ -19,9 +19,9 @@ shortTitle: Review installed integrations {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 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 %} diff --git a/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index 172b741d51..e08fcb498f 100644 --- a/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -40,7 +40,7 @@ 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 or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} {% data reusables.organizations.invite-teams-or-people %} 5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches. diff --git a/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md index dca2061c91..175582a2d2 100644 --- a/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ b/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -28,9 +28,9 @@ When you remove a collaborator from a repository in your organization, the colla {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} -{% elsif ghes < 3.4 or ghae %} +{% else %} {% data reusables.repositories.navigate-to-manage-access %} {% endif %} {% data reusables.organizations.invite-teams-or-people %} diff --git a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md index 69be8ae11c..c83355b58f 100644 --- a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md +++ b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md @@ -23,7 +23,7 @@ When you disable project boards, you will no longer see project board informatio {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects": diff --git a/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md index 4d62131020..9a7937c0b6 100644 --- a/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md +++ b/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -9,13 +9,13 @@ versions: ghae: '*' shortTitle: Integrate Jira --- -{% ifversion ghes > 3.3 or ghae-issue-5658 %} +{% ifversion ghes > 3.4 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 tab in the left sidebar](/assets/images/help/organizations/org-oauth-applications-ghe.png) 1. Click **New OAuth App**. -{% elsif ghes < 3.4 or ghae %} +{% else %} {% data reusables.user_settings.access_settings %} 1. In the left sidebar under **Organization settings**, click the name of your organization. ![Sidebar organization name](/assets/images/help/settings/organization-settings-from-sidebar.png) diff --git a/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index 7f1c181bd9..e64b4978fc 100644 --- a/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -15,11 +15,15 @@ topics: shortTitle: Restrict repository creation --- -You can choose whether members can create repositories in your organization. If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}. +You can choose whether members can create repositories in your organization. {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository. + +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization). +{% endif %} -Organization owners can always create any type of repository. {% ifversion ghec or ghae or ghes %} -{% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %} +Enterprise owners can restrict the options you have available for your organization's repository creation policy. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." +{% endif %} {% warning %} @@ -36,5 +40,12 @@ Organization owners can always create any type of repository. ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + + {% note %} + + **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + + {% endnote %} {%- endif %} + 6. Click **Save**. diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 00cc0a8af6..4c23e7614b 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -20,6 +20,10 @@ If you enable but don't enforce SAML SSO, organization members who choose not to {% data reusables.saml.outside-collaborators-exemption %} +{% data reusables.saml.saml-disabled-linked-identities-removed %} + +{% data reusables.saml.cannot-update-existing-saml-settings %} + ## Enabling and testing SAML single sign-on for your organization Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)." diff --git a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md index 8cb00329e2..4e14267508 100644 --- a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md +++ b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md @@ -57,7 +57,7 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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** @@ -73,7 +73,7 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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** diff --git a/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md index 308d6f4aa6..ecea99fe3b 100644 --- a/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md +++ b/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -3,7 +3,7 @@ title: Managing scheduled reminders for your team intro: You can get reminders in Slack when your team has pull requests waiting for review. redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests - - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team versions: fpt: '*' ghec: '*' diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 1408b3e897..fb1dedf12d 100644 --- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -21,7 +21,7 @@ topics: **Note:** When working with pull requests, keep the following in mind: * If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes. -* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. +* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index f9a5eda3a6..6a9ee0d344 100644 --- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -16,7 +16,7 @@ topics: --- Forking a repository is similar to copying a repository, with two major differences: -* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository. +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. * You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository. {% data reusables.repositories.you-can-fork %} diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index d6ac9ce97e..9112cf8d90 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -17,7 +17,7 @@ topics: --- People with admin or owner permissions can set up a CODEOWNERS file in a repository. -The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. +The people you choose as code owners must have read permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. ## About code owners @@ -42,7 +42,7 @@ For code owners to receive review requests, the CODEOWNERS file must be on the b CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. -To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. +To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. {% endif %} ## CODEOWNERS syntax @@ -103,11 +103,11 @@ apps/ @octocat # 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` +# 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. /apps/ @octocat -/apps/github +/apps/github ``` ### Syntax exceptions There are some syntax rules for gitignore files that do not work in CODEOWNERS files: @@ -116,7 +116,7 @@ There are some syntax rules for gitignore files that do not work in CODEOWNERS f - Using `[ ]` to define a character range ## 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)." +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)." ## Further reading diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md index 374e9a889b..1ba761c11c 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md @@ -21,7 +21,7 @@ If you use Zendesk to track user-reported tickets, for example, you can referenc {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. In the left sidebar, click **Autolink references**. diff --git a/content/rest/reference/billing.md b/content/rest/reference/billing.md index 8876b25d3f..fe0cf42be4 100644 --- a/content/rest/reference/billing.md +++ b/content/rest/reference/billing.md @@ -4,6 +4,7 @@ intro: 'With the Billing API, you can monitor the charges and usage {% data vari versions: fpt: '*' ghec: '*' + ghes: '>=3.4' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/content/rest/reference/enterprise-admin.md b/content/rest/reference/enterprise-admin.md index d903396303..230e3f76b5 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 @@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 %} ## Billing {% for operation in currentRestOperations %} diff --git a/content/support/contacting-github-support/providing-data-to-github-support.md b/content/support/contacting-github-support/providing-data-to-github-support.md index 86e8c3ef8e..39ba3414b7 100644 --- a/content/support/contacting-github-support/providing-data-to-github-support.md +++ b/content/support/contacting-github-support/providing-data-to-github-support.md @@ -21,6 +21,24 @@ topics: Diagnostic files contain information about a {% data variables.product.prodname_ghe_server %} instance's settings and environment, support bundles contain diagnostics and logs from the past two days, and extended support bundles also contain diagnostics and logs but from the past seven days. +## About log file sanitization + +Authentication tokens, keys, and secrets are removed from log files in the following log directories contained within a support bundle or diagnostics file: + +* `alambic-logs` +* `babeld-logs` +* `codeload-logs` +* `enterprise-manage-logs` +* `github-logs` +* `hookshot-logs` +* `lfs-server-logs` +* `semiotic-logs` +* `task-dispatcher-logs` +* `pages-logs` +* `registry-logs` +* `render-logs` +* `svn-bridge-logs` + ## Creating and sharing diagnostic files Diagnostic files are an overview of a {% data variables.product.prodname_ghe_server %} instance's settings and environment that contains: diff --git a/contributing/content-markup-reference.md b/contributing/content-markup-reference.md index fc414ee0f5..8d71dffedd 100644 --- a/contributing/content-markup-reference.md +++ b/contributing/content-markup-reference.md @@ -2,24 +2,48 @@ ## Table of contents - [Writing in Markdown](#writing-in-markdown) -- [Callout tags](#callout-tags) +- [Lists](#lists) - [Usage](#usage) -- [Code sample syntax highlighting](#code-sample-syntax-highlighting) +- [Callout tags](#callout-tags) - [Usage](#usage-1) -- [Octicons](#octicons) +- [Code sample syntax highlighting](#code-sample-syntax-highlighting) - [Usage](#usage-2) -- [Operating system tags](#operating-system-tags) +- [Octicons](#octicons) - [Usage](#usage-3) -- [Tool tags](#tool-tags) +- [Operating system tags](#operating-system-tags) - [Usage](#usage-4) +- [Tool tags](#tool-tags) + - [Usage](#usage-5) - [Reusable and variable strings of text](#reusable-and-variable-strings-of-text) ## Writing in Markdown -[Markdown](http://daringfireball.net/projects/markdown/) is a human-friendly syntax for formatting plain text. Our documentation is written with [GitHub Flavored Markdown](https://docs.github.com/en/github/writing-on-github/about-writing-and-formatting-on-github), a custom version of Markdown used across GitHub. +[Markdown](http://daringfireball.net/projects/markdown/) is a human-friendly syntax for formatting plain text. Our documentation is written with [GitHub Flavored Markdown](https://docs.github.com/en/github/writing-on-github/about-writing-and-formatting-on-github), a custom version of Markdown based on the [CommonMark specification](https://github.github.com/gfm/), and it is used across GitHub. This site's Markdown rendering is powered by [`/lib/render-content`](/lib/render-content), which is in turn built on the [`remark`](https://remark.js.org/) Markdown processor. +## Lists + +In a list item, the general rules for additional content after the first paragraph are: + +* Images and subsequent paragraphs should each **be on their own line and separated by a blank line**. +* All subsequent lines in a list item **must match up with the first text after the list marker**. + +### Usage + +For example, this is the correct way to write list items with multiple paragraphs or objects: + +```markdown +1. Under your repository name, click **Actions**. + + ![Actions tab in the main repository navigation](/assets/images/help/repository/actions-tab.png) + + This is another paragraph in the list. +1. This is the next item. +``` + +![Image demonstrating how to write CommnMark-compliant Markdown lists](/assets/images/commonmark-lists.png) + ## Callout tags Callouts highlight important information that customers need to know. We use standard formatting and colors for different types of callouts: notes, warnings, and danger notices. Use tags before and after the text you’d like included in the callout box. diff --git a/data/features/codeql-runner-supported.yml b/data/features/codeql-runner-supported.yml new file mode 100644 index 0000000000..f1ea3ca57b --- /dev/null +++ b/data/features/codeql-runner-supported.yml @@ -0,0 +1,6 @@ +# Tracking deprecation of CodeQL runner +versions: + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' diff --git a/data/features/mermaid.yml b/data/features/mermaid.yml new file mode 100644 index 0000000000..7923730060 --- /dev/null +++ b/data/features/mermaid.yml @@ -0,0 +1,7 @@ +# Issue 5812 and 6172 +# Mermaid syntax support +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-6172' 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/enterprise-github-connect-warning.md b/data/reusables/actions/enterprise-github-connect-warning.md index 64995d5178..77ddb99f3b 100644 --- a/data/reusables/actions/enterprise-github-connect-warning.md +++ b/data/reusables/actions/enterprise-github-connect-warning.md @@ -1,7 +1,7 @@ {% ifversion ghes > 3.2 or ghae-issue-4815 %} {% note %} -**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom_the_website%}. If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." +**Note:** When a workflow uses an action by referencing the repository where the action is stored, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom_the_website %}. If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." {% endnote %} {% endif %} @@ -9,7 +9,7 @@ {% ifversion ghes < 3.3 %} {% note %} -**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom_the_website%}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow. +**Note:** When a workflow uses an action by referencing the repository where the action is stored, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom_the_website %}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow. {% endnote %} {% endif %} diff --git a/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md index 708257ab9e..43018f4392 100644 --- a/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md +++ b/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md @@ -2,6 +2,8 @@ 1. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern. 1. You can click **More options {% octicon "chevron-down" aria-label="down" %}** to provide other surrounding content or additional match requirements for the secret format. 1. Provide a sample test string to make sure your configuration is matching the patterns you expect. - + {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} ![Create a custom {% data variables.product.prodname_secret_scanning %} pattern form](/assets/images/help/repository/secret-scanning-create-custom-pattern.png) -1. When you are satisfied with your new custom pattern, click {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. + {% else %} + ![Create a custom {% data variables.product.prodname_secret_scanning %} pattern form](/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png) + {% endif %} diff --git a/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md new file mode 100644 index 0000000000..8f4453f9fc --- /dev/null +++ b/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md @@ -0,0 +1 @@ +1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern**{% elsif ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. diff --git a/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md index d8ec9ca1bb..6cc2c183fd 100644 --- a/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md +++ b/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 1. In the Settings sidebar, click **Audit log**. diff --git a/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md index a717da6991..a6e00e1dc8 100644 --- a/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md +++ b/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 3. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 3. In the left sidebar, click **Audit log**. diff --git a/data/reusables/billing/email-notifications.md b/data/reusables/billing/email-notifications.md index 56e9d3f6ac..8dff9b48f5 100644 --- a/data/reusables/billing/email-notifications.md +++ b/data/reusables/billing/email-notifications.md @@ -1,3 +1,5 @@ -Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's included usage and when spending reaches 50%, 75%, and 90% of your account's spending limit. +Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit. You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. + +![Screenshot of the billing email notification settings](/assets/images/help/billing/actions-packages-spending-limit-notifications.png) diff --git a/data/reusables/code-scanning/deprecation-codeql-runner.md b/data/reusables/code-scanning/deprecation-codeql-runner.md index 2583a9304c..22f942d9b6 100644 --- a/data/reusables/code-scanning/deprecation-codeql-runner.md +++ b/data/reusables/code-scanning/deprecation-codeql-runner.md @@ -1,7 +1,23 @@ {% note %} -**Note:** The {% data variables.product.prodname_codeql_runner %} is being deprecated. Please use the [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.6.2 or greater instead. -{% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql_runner %}. On {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_codeql_runner %} will be supported until March 2022. -For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). +{% ifversion fpt or ghec %} + +**Note:** The {% data variables.product.prodname_codeql_runner %} is being deprecated. On {% data variables.product.product_name %}, the {% data variables.product.prodname_codeql_runner %} will be supported until March 2022. You should upgrade to the latest version of [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). + +{% elsif ghes > 3.3 %} + +**Note:** The {% data variables.product.prodname_codeql_runner %} has been deprecated and is not included in {% data variables.product.prodname_ghe_server %} 3.4. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.7.6. + +{% elsif ghes < 3.4 %} + +**Note:** The {% data variables.product.prodname_codeql_runner %} is being deprecated. On {% data variables.product.prodname_ghe_server %} 3.0 and greater, you can install [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.6.3 to replace {% data variables.product.prodname_codeql_runner %}. + +{% elsif ghae %} + +**Note:** The {% data variables.product.prodname_codeql_runner %} has been deprecated. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). + +{% endif %} + +For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." {% endnote %} diff --git a/data/reusables/code-scanning/enabling-options.md b/data/reusables/code-scanning/enabling-options.md index ad4eded9d1..5e5bf62734 100644 --- a/data/reusables/code-scanning/enabling-options.md +++ b/data/reusables/code-scanning/enabling-options.md @@ -1,8 +1,4 @@ | Type of analysis | Options for generating alerts | |------------------|-------------------------------| -{%- ifversion fpt or ghes > 3.0 or ghae %} | {% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)"). -{%- else %} -| {% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)"). -{%- endif %} | Third‑party | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)").| diff --git a/data/reusables/code-scanning/use-codeql-runner-not-cli.md b/data/reusables/code-scanning/use-codeql-runner-not-cli.md deleted file mode 100644 index feac9dd20d..0000000000 --- a/data/reusables/code-scanning/use-codeql-runner-not-cli.md +++ /dev/null @@ -1,9 +0,0 @@ -{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -If the {% data variables.product.prodname_codeql_cli %} is unsuitable for use in your CI system, the {% data variables.product.prodname_codeql_runner %} is available as an alternative. Typically, this is needed if the CI system would need to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)." -{% endif %} - -{% ifversion ghes = 3.1 %} -You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to: -- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis. -- Analyze more than one language in a repository. -{% endif %} diff --git a/data/reusables/dependabot/dependabot-secrets-button.md b/data/reusables/dependabot/dependabot-secrets-button.md index 72625bc19f..cb57bb6485 100644 --- a/data/reusables/dependabot/dependabot-secrets-button.md +++ b/data/reusables/dependabot/dependabot-secrets-button.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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%} +{% else %} 1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**. ![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png) {% endif %} diff --git a/data/reusables/github-actions/docker-container-os-support.md b/data/reusables/github-actions/docker-container-os-support.md index 8dc5f40b5c..e334bce18c 100644 --- a/data/reusables/github-actions/docker-container-os-support.md +++ b/data/reusables/github-actions/docker-container-os-support.md @@ -1,6 +1,6 @@ {% note %} -**Note:** If your workflows use Docker container actions or service containers, then you must use a Linux runner: +**Note:** If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runner: * If you are using {% data variables.product.prodname_dotcom %}-hosted runners, you must use an Ubuntu runner. * If you are using self-hosted runners, you must use a Linux machine as your runner and Docker must be installed. diff --git a/data/reusables/github-actions/github-token-available-permissions.md b/data/reusables/github-actions/github-token-available-permissions.md index 98b309435b..fbb68588ad 100644 --- a/data/reusables/github-actions/github-token-available-permissions.md +++ b/data/reusables/github-actions/github-token-available-permissions.md @@ -5,8 +5,8 @@ permissions: actions: read|write|none checks: read|write|none contents: read|write|none - deployments: read|write|none - id-token: read|write|none + deployments: read|write|none{% ifversion fpt or ghec %} + id-token: read|write|none{% endif %} issues: read|write|none discussions: read|write|none packages: read|write|none diff --git a/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index 2efea4d2c3..39720ea972 100644 --- a/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -12,6 +12,6 @@ 2. In the left sidebar, click **Enterprise overview**. 3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 2. Navigate to the "Runner groups" settings: - * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %} - * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghec %}, then click the **Runners groups** tab{% endif %}.{% endif %} + * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %} + * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %} {% endif %} diff --git a/data/reusables/github-actions/sidebar-secret.md b/data/reusables/github-actions/sidebar-secret.md index f5c22b01b3..896d920ff4 100644 --- a/data/reusables/github-actions/sidebar-secret.md +++ b/data/reusables/github-actions/sidebar-secret.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left sidebar, click **Secrets**. {% endif %} diff --git a/data/reusables/gpg/desktop-support-for-commit-signing.md b/data/reusables/gpg/desktop-support-for-commit-signing.md index 024918e294..5093127a3e 100644 --- a/data/reusables/gpg/desktop-support-for-commit-signing.md +++ b/data/reusables/gpg/desktop-support-for-commit-signing.md @@ -1,5 +1,5 @@ {% note %} -**Note:** [GitHub Desktop](https://desktop.github.com/) does not support commit signing. +**Note:** [GitHub Desktop](https://desktop.github.com/) only supports commit signing if your Git client is configured to sign commits by default. {% endnote %} diff --git a/data/reusables/organizations/billing_plans.md b/data/reusables/organizations/billing_plans.md index 0d48d771db..35dc04461a 100644 --- a/data/reusables/organizations/billing_plans.md +++ b/data/reusables/organizations/billing_plans.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In your organization's Settings sidebar, click **Billing & plans**. ![Billing settings](/assets/images/help/billing/settings_organization_billing_plans_tab.png) {% endif %} diff --git a/data/reusables/organizations/github-apps-settings-sidebar.md b/data/reusables/organizations/github-apps-settings-sidebar.md index e130e6b624..1e835a9141 100644 --- a/data/reusables/organizations/github-apps-settings-sidebar.md +++ b/data/reusables/organizations/github-apps-settings-sidebar.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left sidebar, click **{% 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/data/reusables/organizations/member-privileges.md b/data/reusables/organizations/member-privileges.md index 96da580be3..66589d5bad 100644 --- a/data/reusables/organizations/member-privileges.md +++ b/data/reusables/organizations/member-privileges.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 4. In the left sidebar, click **Member privileges**. ![Member privileges option in org settings](/assets/images/help/organizations/org-settings-member-privileges.png) {% endif %} diff --git a/data/reusables/organizations/repository-defaults.md b/data/reusables/organizations/repository-defaults.md index 05d921fb76..0356b367d1 100644 --- a/data/reusables/organizations/repository-defaults.md +++ b/data/reusables/organizations/repository-defaults.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left sidebar, click **Repository defaults**. ![Repository defaults tab](/assets/images/help/organizations/repo-defaults-tab.png) {% endif %} diff --git a/data/reusables/organizations/security-and-analysis.md b/data/reusables/organizations/security-and-analysis.md index 9ab6f7bfe5..a641b5b0fd 100644 --- a/data/reusables/organizations/security-and-analysis.md +++ b/data/reusables/organizations/security-and-analysis.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left sidebar, click **Security & analysis**. !["Security & analysis" tab in organization settings](/assets/images/help/organizations/org-settings-security-and-analysis.png) {% endif %} diff --git a/data/reusables/organizations/security.md b/data/reusables/organizations/security.md index 049c20a7b9..31ea8e9ce9 100644 --- a/data/reusables/organizations/security.md +++ b/data/reusables/organizations/security.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. In the left sidebar, click **Organization security**. diff --git a/data/reusables/organizations/teams_sidebar.md b/data/reusables/organizations/teams_sidebar.md index 338fe6bc8e..812304b4bc 100644 --- a/data/reusables/organizations/teams_sidebar.md +++ b/data/reusables/organizations/teams_sidebar.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/organizations/verified-domains.md b/data/reusables/organizations/verified-domains.md index 83b44b4715..079ac23d2d 100644 --- a/data/reusables/organizations/verified-domains.md +++ b/data/reusables/organizations/verified-domains.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png) {% endif %} diff --git a/data/reusables/pages/sidebar-pages.md b/data/reusables/pages/sidebar-pages.md index 03ae79d84f..61e7afdbb2 100644 --- a/data/reusables/pages/sidebar-pages.md +++ b/data/reusables/pages/sidebar-pages.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %} +{% ifversion fpt or ghes > 3.4 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. In the left sidebar, click **Pages**. diff --git a/data/reusables/projects/project-description.md b/data/reusables/projects/project-description.md new file mode 100644 index 0000000000..e393f00aac --- /dev/null +++ b/data/reusables/projects/project-description.md @@ -0,0 +1,10 @@ +You can set your project's description and README to share the purpose of your project, provide instructions on how to use the project, and include any relevant links. + +{% data reusables.projects.project-settings %} +1. To add a short description to your project, under "Add a description", type your description in the text box and click **Save**. +1. To update your project's README, under "README", type your content in the text box. + - You can format your README using Markdown. For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)." + - To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}. +1. To save changes to your README, click **Save**. + +You can view and make quick changes to your project description and README by navigating to your project and clicking {% octicon "sidebar-expand" aria-label="The sidebar icon" %} in the top right. \ No newline at end of file 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/navigate-to-security-and-analysis.md b/data/reusables/repositories/navigate-to-security-and-analysis.md index 2407a1cd4f..79b226c3b5 100644 --- a/data/reusables/repositories/navigate-to-security-and-analysis.md +++ b/data/reusables/repositories/navigate-to-security-and-analysis.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left sidebar, click **Security & analysis**. !["Security & analysis" tab in repository settings](/assets/images/help/repository/security-and-analysis-tab.png) {% endif %} diff --git a/data/reusables/repositories/repository-branches.md b/data/reusables/repositories/repository-branches.md index a004e202d0..c51576f4ff 100644 --- a/data/reusables/repositories/repository-branches.md +++ b/data/reusables/repositories/repository-branches.md @@ -1,6 +1,6 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. In the left menu, click **Branches**. ![Repository options sub-menu](/assets/images/help/repository/repository-options-branch.png) {% endif %} diff --git a/data/reusables/repositories/sidebar-notifications.md b/data/reusables/repositories/sidebar-notifications.md index 1a5edf0d3d..ab2fd8d2be 100644 --- a/data/reusables/repositories/sidebar-notifications.md +++ b/data/reusables/repositories/sidebar-notifications.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/saml/cannot-update-existing-saml-settings.md b/data/reusables/saml/cannot-update-existing-saml-settings.md new file mode 100644 index 0000000000..8983c45e8e --- /dev/null +++ b/data/reusables/saml/cannot-update-existing-saml-settings.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** When SAML SSO is enabled, the only setting you can update on {% data variables.product.prodname_dotcom %} for your existing SAML configuration is the SAML certificate. If you need to update the Sign on URL or Issuer, you must first disable SAML SSO and then reconfigure SAML SSO with the new settings. + +{% endnote %} \ No newline at end of file diff --git a/data/reusables/saml/saml-disabled-linked-identities-removed.md b/data/reusables/saml/saml-disabled-linked-identities-removed.md new file mode 100644 index 0000000000..a81dc090df --- /dev/null +++ b/data/reusables/saml/saml-disabled-linked-identities-removed.md @@ -0,0 +1 @@ +When SAML SSO is disabled, all linked external identities are removed from {% data variables.product.product_name %}. \ No newline at end of file diff --git a/data/reusables/secret-scanning/beta-dry-runs.md b/data/reusables/secret-scanning/beta-dry-runs.md new file mode 100644 index 0000000000..2d3121b0cd --- /dev/null +++ b/data/reusables/secret-scanning/beta-dry-runs.md @@ -0,0 +1,6 @@ + +{% note %} + +**Note:** The dry run feature is currently in beta and subject to change. + +{% endnote %} diff --git a/data/reusables/user_settings/access_applications.md b/data/reusables/user_settings/access_applications.md index efc6abe024..812666b807 100644 --- a/data/reusables/user_settings/access_applications.md +++ b/data/reusables/user_settings/access_applications.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/account_settings.md b/data/reusables/user_settings/account_settings.md index 7edd6e2f14..10074924fe 100644 --- a/data/reusables/user_settings/account_settings.md +++ b/data/reusables/user_settings/account_settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/appearance-settings.md b/data/reusables/user_settings/appearance-settings.md index d201a2de59..f7f2c3d0c8 100644 --- a/data/reusables/user_settings/appearance-settings.md +++ b/data/reusables/user_settings/appearance-settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/developer_settings.md b/data/reusables/user_settings/developer_settings.md index f8fc22316f..8b13c1d91d 100644 --- a/data/reusables/user_settings/developer_settings.md +++ b/data/reusables/user_settings/developer_settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/emails.md b/data/reusables/user_settings/emails.md index dd47cf76a9..e19a8634fd 100644 --- a/data/reusables/user_settings/emails.md +++ b/data/reusables/user_settings/emails.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/organizations.md b/data/reusables/user_settings/organizations.md index cf4c3cf6c5..519e8f0a96 100644 --- a/data/reusables/user_settings/organizations.md +++ b/data/reusables/user_settings/organizations.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/repo-tab.md b/data/reusables/user_settings/repo-tab.md index be39213129..8a8cd80c04 100644 --- a/data/reusables/user_settings/repo-tab.md +++ b/data/reusables/user_settings/repo-tab.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/saved_replies.md b/data/reusables/user_settings/saved_replies.md index 0d007727eb..51c59de438 100644 --- a/data/reusables/user_settings/saved_replies.md +++ b/data/reusables/user_settings/saved_replies.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/security-analysis.md b/data/reusables/user_settings/security-analysis.md index 0f79b730ae..d525a3d6ed 100644 --- a/data/reusables/user_settings/security-analysis.md +++ b/data/reusables/user_settings/security-analysis.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/security.md b/data/reusables/user_settings/security.md index 56cc87e20a..9e83e2c052 100644 --- a/data/reusables/user_settings/security.md +++ b/data/reusables/user_settings/security.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/data/reusables/user_settings/ssh.md b/data/reusables/user_settings/ssh.md index 08e50ade35..b2c942ca79 100644 --- a/data/reusables/user_settings/ssh.md +++ b/data/reusables/user_settings/ssh.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. diff --git a/lib/enterprise-dates.json b/lib/enterprise-dates.json index 605d83cb3d..fd5411945d 100644 --- a/lib/enterprise-dates.json +++ b/lib/enterprise-dates.json @@ -118,5 +118,13 @@ "3.6": { "releaseDate": "2022-07-19", "deprecationDate": "2023-08-16" + }, + "3.7": { + "releaseDate": "2022-10-04", + "deprecationDate": "2023-11-08" + }, + "3.8": { + "releaseDate": "2023-02-07", + "deprecationDate": "2024-03-07" } } \ No newline at end of file diff --git a/lib/find-page.js b/lib/find-page.js index 071882e2c9..9c2c9ee0e5 100644 --- a/lib/find-page.js +++ b/lib/find-page.js @@ -1,11 +1,14 @@ import { getLanguageCode } from './patterns.js' +import getRedirect from './get-redirect.js' export default function findPage(href, pageMap, redirects) { // remove any fragments href = href.replace(/#.*$/, '') + const redirectsContext = { redirects, pages: pageMap } + // find the page - const page = pageMap[href] || pageMap[redirects[href]] + const page = pageMap[href] || pageMap[getRedirect(href, redirectsContext)] if (page) return page // get the current language @@ -13,5 +16,5 @@ export default function findPage(href, pageMap, redirects) { // try to fall back to English if the translated page can't be found const englishHref = href.replace(`/${currentLang}/`, '/en/') - return pageMap[englishHref] || pageMap[redirects[englishHref]] + return pageMap[englishHref] || pageMap[getRedirect(englishHref, redirectsContext)] } diff --git a/lib/get-redirect.js b/lib/get-redirect.js new file mode 100644 index 0000000000..d9c5b5ec81 --- /dev/null +++ b/lib/get-redirect.js @@ -0,0 +1,201 @@ +import { languageKeys } from './languages.js' +import nonEnterpriseDefaultVersion from './non-enterprise-default-version.js' + +import { allVersions } from './all-versions.js' +import { latest, supported } from './enterprise-server-releases.js' + +const languagePrefixRegex = new RegExp(`^/(${languageKeys.join('|')})/`) +const nonEnterpriseDefaultVersionPrefix = `/${nonEnterpriseDefaultVersion}` + +// Return the new URI if there is one, otherwise return undefined. +export default function getRedirect(uri, context) { + const { redirects, pages } = context + + let language = 'en' + let withoutLanguage = uri + if (languagePrefixRegex.test(uri)) { + language = uri.match(languagePrefixRegex)[1] + withoutLanguage = uri.replace(languagePrefixRegex, '/') + } + + let destination + + // `redirects` is sourced from more than one thing. The primary use + // case is gathering up the `redirect_from` frontmatter key. + // But we also has `developer.json` which contains legacy redirects. + // For example, the `developer.json` will have entries such + // `/enterprise/v4/enum/auditlogorderfield` which clearly is using + // the old formatting of the version. So to leverage the redirects + // from `developer.json` we'll look at it right away. + if (withoutLanguage in redirects) { + return `/${language}` + redirects[withoutLanguage] + } + + let basicCorrection + + if (withoutLanguage.startsWith(nonEnterpriseDefaultVersionPrefix)) { + // E.g. '/free-pro-team@latest/foo/bar' or '/free-pro-team@latest' + basicCorrection = + `/${language}` + withoutLanguage.replace(nonEnterpriseDefaultVersionPrefix, '') + } else if (withoutLanguage.replace('/', '') in allVersions && !languagePrefixRegex.test(uri)) { + // E.g. just '/github-ae@latest' or '/enterprise-cloud@latest' + basicCorrection = `/${language}` + withoutLanguage + return basicCorrection + } + + if ( + withoutLanguage === '/enterprise-server' || + withoutLanguage.startsWith('/enterprise-server/') + ) { + // E.g. '/enterprise-server' or '/enterprise-server/3.0/foo' + basicCorrection = + `/${language}` + withoutLanguage.replace('/enterprise-server', `/enterprise-server@${latest}`) + // If it's now just the version, without anything after, exit here + if (withoutLanguage === '/enterprise-server') { + return basicCorrection + } + // console.log({ basicCorrection }) + } else if (withoutLanguage.startsWith('/enterprise-server@latest')) { + // E.g. '/enterprise-server@latest' or '/enterprise-server@latest/3.3/foo' + basicCorrection = + `/${language}` + + withoutLanguage.replace('/enterprise-server@latest', `/enterprise-server@${latest}`) + // If it was *just* '/enterprise-server@latest' all that's needed is + // the language but with 'latest' replaced with the value of `latest` + if (withoutLanguage === '/enterprise-server@latest') { + return basicCorrection + } + } else if ( + withoutLanguage.startsWith('/enterprise/') && + supported.includes(withoutLanguage.split('/')[2]) + ) { + // E.g. '/enterprise/3.3' or '/enterprise/3.3/foo' + + // If the URL is without a language, and no redirect is necessary, + // but it has as version prefix, the language has to be there + // otherwise it will never be found in `req.context.pages` + const version = withoutLanguage.split('/')[2] + if (withoutLanguage === `/enterprise/${version}`) { + // E.g. `/enterprise/3.0` + basicCorrection = + `/${language}` + + withoutLanguage.replace(`/enterprise/${version}`, `/enterprise-server@${version}`) + return basicCorrection + } else { + basicCorrection = + `/${language}` + + withoutLanguage.replace(`/enterprise/${version}/`, `/enterprise-server@${version}/`) + } + } else if (withoutLanguage === '/enterprise') { + // E.g. `/enterprise` exactly + basicCorrection = `/${language}/enterprise-server@${latest}` + return basicCorrection + } else if ( + withoutLanguage.startsWith('/enterprise/') && + !supported.includes(withoutLanguage.split('/')[2]) + ) { + // E.g. '/en/enterprise/user/github/foo' + // If the URL is without a language, and no redirect is necessary, + // but it has as version prefix, the language has to be there + // otherwise it will never be found in `req.context.pages` + basicCorrection = + `/${language}` + + withoutLanguage + .replace(`/enterprise/`, `/enterprise-server@${latest}/`) + .replace('/user/', '/') + } else if (withoutLanguage.startsWith('/insights')) { + // E.g. '/insights/foo' + basicCorrection = uri.replace('/insights', `${language}/enterprise-server@${latest}/insights`) + } + + if (basicCorrection) { + return ( + getRedirect(basicCorrection, { + redirects, + pages, + }) || basicCorrection + ) + } + + if (withoutLanguage.startsWith('/admin/')) { + const prefix = `/enterprise-server@${latest}` + let suffix = withoutLanguage + if (suffix.startsWith('/admin/guides/')) { + suffix = suffix.replace('/admin/guides/', '/admin/') + } + const newURL = prefix + suffix + destination = redirects[newURL] || newURL + } else if ( + withoutLanguage.split('/')[1].includes('@') && + withoutLanguage.split('/')[1] in allVersions + ) { + // E.g. '/enterprise-server@latest' or '/github-ae@latest' or '/enterprise-server@3.3' + const majorVersion = withoutLanguage.split('/')[1].split('@')[0] + const split = withoutLanguage.split('/') + const version = split[1].split('@')[1] + let prefix + let suffix + + if (supported.includes(version) || version === 'latest') { + prefix = `/${majorVersion}@${version}` + suffix = '/' + split.slice(2).join('/') + + if ( + suffix.includes('/user') || + suffix.startsWith('/admin/guide') || + suffix.startsWith('/articles/user') + ) { + suffix = tryReplacements(prefix, suffix, context) || suffix + } + } + + const newURL = prefix + suffix + if (newURL !== withoutLanguage) { + // At least the prefix changed! + destination = redirects[newURL] || newURL + } else { + destination = redirects[newURL] + } + } else if (withoutLanguage.startsWith('/desktop/guides/')) { + // E.g. /desktop/guides/contributing-and-collaborat + const newURL = withoutLanguage.replace('/desktop/guides/', '/desktop/') + destination = redirects[newURL] || newURL + } else { + destination = redirects[withoutLanguage] + } + + if (destination !== undefined) { + // There's hope! Now we just need to attach the correct language + // to the destination URL. + return `/${language}${destination}` + } +} + +// Over time, we've developed multiple ambiguous patterns of URLs +// You can't simply assume that all `/admin/guides` should become +// `/admin` for example. +// This function tries different string replacement on the suffix +// (the pathname after the language and version part) until it +// finds one string replacement that yields either a page or a redirect. +function tryReplacements(prefix, suffix, { pages, redirects }) { + const test = (suffix) => { + const candidateAsRedirect = prefix + suffix + const candidateAsURL = '/en' + candidateAsRedirect + return candidateAsRedirect in redirects || candidateAsURL in pages + } + + let attempt = suffix.replace('/user', '/github') + if (test(attempt)) return attempt + + attempt = suffix.replace('/user', '') + if (test(attempt)) return attempt + + attempt = suffix.replace('/admin/guides', '/admin') + if (test(attempt)) return attempt + + attempt = suffix.replace('/admin/guides/user', '/admin/github') + if (test(attempt)) return attempt + + attempt = suffix.replace('/admin/guides', '/admin').replace('/user', '/github') + if (test(attempt)) return attempt +} diff --git a/lib/languages.js b/lib/languages.js index 962f6a8b17..2460cbfea7 100644 --- a/lib/languages.js +++ b/lib/languages.js @@ -53,8 +53,12 @@ if (process.env.ENABLED_LANGUAGES) { export const languageKeys = Object.keys(languages) -const languagePrefixPathRegex = new RegExp(`^/(${languageKeys.join('|')})/`) +export const languagePrefixPathRegex = new RegExp(`^/(${languageKeys.join('|')})(/|$)`) +/** Return true if the URL is something like /en/foo or /ja but return false + * if it's something like /foo or /foo/bar or /fr (because French (fr) + * is currently not an active language) + */ export function pathLanguagePrefixed(path) { return languagePrefixPathRegex.test(path) } diff --git a/lib/page.js b/lib/page.js index b0a3625a9e..9d9ee7c914 100644 --- a/lib/page.js +++ b/lib/page.js @@ -135,14 +135,16 @@ class Page { } buildRedirects() { - // create backwards-compatible old paths for page permalinks and frontmatter redirects - this.redirects = generateRedirectsForPermalinks( - this.permalinks, - this.redirect_from, - this.applicableVersions - ) + if (!this.redirect_from) { + return {} + } + // this.redirect_from comes from frontmatter Yaml + // E.g `redirect_from: /old/path` + const redirectFrontmatter = Array.isArray(this.redirect_from) + ? this.redirect_from + : [this.redirect_from] - return this.redirects + return generateRedirectsForPermalinks(this.permalinks, redirectFrontmatter) } // Infer the parent product ID from the page's relative file path diff --git a/lib/path-utils.js b/lib/path-utils.js index bcd735a642..5053a85799 100644 --- a/lib/path-utils.js +++ b/lib/path-utils.js @@ -33,7 +33,7 @@ export function getPathWithoutVersion(href) { } // Return the version segment in a path -export function getVersionStringFromPath(href) { +export function getVersionStringFromPath(href, supportedOnly = false) { href = getPathWithoutLanguage(href) // Return immediately if this is a link to the homepage @@ -65,6 +65,16 @@ export function getVersionStringFromPath(href) { return allVersions[planObject.latestVersion].version } + // If the caller of this function explicitly wants to know if the + // version part is *not* supported, they get back `undefined`. + // But this function is used in many other places where it potentially + // doesn't care if the version is supported. + // For example, in lib/redirects/permalinks.js it needs to know if the + // URL didn't contain a valid version. + if (supportedOnly) { + return + } + // Otherwise, return the first segment as-is, which may not be a real supported version, // but additional checks are done on this segment in getVersionedPathWithoutLanguage return versionFromPath diff --git a/lib/permalink.js b/lib/permalink.js index ba5ad88a27..35dda6e7db 100644 --- a/lib/permalink.js +++ b/lib/permalink.js @@ -13,9 +13,12 @@ class Permalink { const permalinkSuffix = this.constructor.relativePathToSuffix(relativePath) - this.href = removeFPTFromPath( - path.posix.join('/', languageCode, pageVersion, permalinkSuffix) + this.hrefWithoutLanguage = removeFPTFromPath( + path.posix.join('/', pageVersion, permalinkSuffix) ).replace(patterns.trailingSlash, '$1') + this.href = `/${languageCode}${ + this.hrefWithoutLanguage === '/' ? '' : this.hrefWithoutLanguage + }` this.pageVersionTitle = allVersions[pageVersion].versionTitle diff --git a/lib/redirects/README.md b/lib/redirects/README.md index d1aa5e0089..77c1718af2 100644 --- a/lib/redirects/README.md +++ b/lib/redirects/README.md @@ -14,16 +14,27 @@ Precompiled redirects account for the majority of the docs site's redirect handl When [`lib/warm-server.js`](lib/warm-server.js) runs on server start, it creates all pages in the site by instantiating the [`Page` class](lib/page.js) for each content file, then passes the pages to `lib/redirects/precompile.js` to create redirects. The precompile script runs `lib/redirects/permalinks.js`, which: -1. Loops over each page's [permalinks](contributing/permalinks.md) and creates an array of legacy paths for each one (via `lib/redirects/get-old-paths-from-permalink.js`). For example, a permalink that starts with `/en/enterprise-server@2.22` results in an array that includes `/en/enterprise/2.22`, `/enterprise/2.22`, etc. +1. Includes all legacy redirects from `static/developerjson` 2. Loops over each page's [frontmatter `redirect_from` entries](content/README.md#redirect_from) and creates an array of legacy paths for each one (using the same handling as for permalinks). +3. Any other exceptions from the `static/redirect-exceptions.txt` file -The results comprise the `page.redirects` object, where the **keys are legacy paths** and the **values are current permalinks**. - -Additionally, a [static JSON file](lib/redirects/static/developer.json) gets `require`d that contains keys with legacy developer.github.com paths (e.g., `/v4/object/app`) and values with new docs.github.com paths (e.g., `/graphql/reference/objects#app`). +The results comprise the `page.redirects` object, whose keys are always only the path without language. +Sometimes it contains the specific plan/version (e.g. `/enterprise-server@3.0/v3/integrations` to `enterprise-server@3.0/developers/apps`) and sometimes it's just the plain path +(e.g. `/articles/viewing-your-repositorys-workflows` to `/actions/monitoring-and-troubleshooting-workflows`) All of the above are merged into a global redirects object. This object gets added to `req.context` via `middleware/context.js` and is made accessible on every request. -Because the redirects are precompiled via `warm-server`, that means `middleware/redirects/handle-redirects.js` just needs to do a simple lookup of the requested path in the redirects object. +In the `handle-redirects.js` middleware, the language part of the URL is +removed, looked up, and if matched to something, redirects with language +put back in. Demonstrated with pseudo code: + +```js +var fullPath = '/ja/foo' +var newPath = redirects['/foo'] +if (newPath) { + redirect('/ja' + newPath) +} +``` ### Archived Enterprise redirects @@ -51,4 +62,4 @@ This is admittedly an inefficient brute-force approach. But requests for archive Redirect tests are mainly found in `tests/routing/*`, with some additional tests in `tests/rendering/server.js`. -The `tests/fixtures/*` directory includes `developer-redirects.json`, `graphql-redirects.json`, and `rest-redirects.json`. \ No newline at end of file +The `tests/fixtures/*` directory includes `developer-redirects.json`, `graphql-redirects.json`, and `rest-redirects.json`. diff --git a/lib/redirects/get-old-paths-from-permalink.js b/lib/redirects/get-old-paths-from-permalink.js deleted file mode 100644 index 6c9b3b05e4..0000000000 --- a/lib/redirects/get-old-paths-from-permalink.js +++ /dev/null @@ -1,151 +0,0 @@ -import { - latest, - deprecated, - lastReleaseWithLegacyFormat, - firstRestoredAdminGuides, -} from '../enterprise-server-releases.js' -import { - getPathWithoutLanguage, - getPathWithLanguage, - getVersionStringFromPath, -} from '../path-utils.js' -import patterns from '../patterns.js' -import versionSatisfiesRange from '../version-satisfies-range.js' -import { allVersions } from '../all-versions.js' -import nonEnterpriseDefaultVersion from '../non-enterprise-default-version.js' -const currentlySupportedVersions = Object.keys(allVersions) - -// This function takes a current path, applies what we know about historically -// supported paths, and returns an array of ALL possible associated old -// paths that users might try to hit. -export default function getOldPathsFromPath(currentPath, languageCode, currentVersion) { - const oldPaths = new Set() - - const versionFromPath = getVersionStringFromPath(currentPath) - - // This only applies to Dotcom paths, so no need to determine whether the version is deprecated - // create old path /free-pro-team@latest/github from new path /github (or from a frontmatter `redirect_from` path like /articles) - if ( - versionFromPath === 'homepage' || - !( - currentlySupportedVersions.includes(versionFromPath) || deprecated.includes(versionFromPath) - ) || - (versionFromPath === nonEnterpriseDefaultVersion && - !currentPath.includes(nonEnterpriseDefaultVersion)) - ) { - oldPaths.add( - currentPath.replace(`/${languageCode}`, `/${languageCode}/${nonEnterpriseDefaultVersion}`) - ) - } - - // ------ BEGIN LEGACY VERSION FORMAT REPLACEMENTS ------// - // These remain relevant to handle legacy-formatted frontmatter redirects - // and archived versions paths. - - // create old path /insights from current path /enterprise/version/insights - oldPaths.add( - currentPath.replace(`/${languageCode}/enterprise/${latest}/user/insights`, '/insights') - ) - - // create old path /desktop/guides from current path /desktop - if (currentPath.includes('/desktop') && !currentPath.includes('/guides')) { - oldPaths.add(currentPath.replace('/desktop', '/desktop/guides')) - } - - // create old path /admin/guides from current path /admin - if (currentPath.includes('admin') && !currentPath.includes('/guides')) { - // ... but ONLY on versions <2.21 and in deep links on all versions - if ( - versionSatisfiesRange(currentVersion, `<${firstRestoredAdminGuides}`) || - !currentPath.endsWith('/admin') - ) { - oldPaths.add(currentPath.replace('/admin', '/admin/guides')) - } - } - - // create old path /user from current path /user/github on 2.16+ only - if ( - currentlySupportedVersions.includes(currentVersion) || - versionSatisfiesRange(currentVersion, '>2.15') - ) { - oldPaths.add(currentPath.replace('/user/github', '/user')) - } - - // create old path /enterprise from current path /enterprise/latest - oldPaths.add(currentPath.replace(`/enterprise/${latest}`, '/enterprise')) - - // create old path /enterprise/foo from current path /enterprise/user/foo - // this supports old developer paths like /enterprise/webhooks with no /user in them - if (currentPath.includes('/enterprise/')) { - oldPaths.add(currentPath.replace('/user/', '/')) - } - - // ------ END LEGACY VERSION FORMAT REPLACEMENTS ------// - - // ------ BEGIN MODERN VERSION FORMAT REPLACEMENTS ------// - if ( - currentlySupportedVersions.includes(currentVersion) || - versionSatisfiesRange(currentVersion, `>${lastReleaseWithLegacyFormat}`) - ) { - new Set(oldPaths).forEach((oldPath) => { - // create old path /enterprise/ from new path /enterprise-server@ - oldPaths.add(oldPath.replace(/\/enterprise-server@(\d)/, '/enterprise/$1')) - - // create old path /enterprise//user from new path /enterprise-server@/github - oldPaths.add(oldPath.replace(/\/enterprise-server@(\d.+?)\/github/, '/enterprise/$1/user')) - - // create old path /insights from new path /enterprise-server@/insights - oldPaths.add(oldPath.replace(`/enterprise-server@${latest}/insights`, '/insights')) - - // create old path /admin from new path /enterprise-server@/admin - oldPaths.add(oldPath.replace(`/enterprise-server@${latest}/admin`, '/admin')) - - // create old path /enterprise from new path /enterprise-server@ - oldPaths.add(oldPath.replace(`/enterprise-server@${latest}`, '/enterprise')) - - // create old path /enterprise-server from new path /enterprise-server@ - oldPaths.add(oldPath.replace(`/enterprise-server@${latest}`, '/enterprise-server')) - - // create old path /enterprise-server@latest from new path /enterprise-server@ - oldPaths.add(oldPath.replace(`/enterprise-server@${latest}`, '/enterprise-server@latest')) - - if (!patterns.adminProduct.test(oldPath)) { - // create old path /enterprise//user/foo from new path /enterprise-server@/foo - oldPaths.add(currentPath.replace(/\/enterprise-server@(\d.+?)\//, '/enterprise/$1/user/')) - - // create old path /enterprise/user/foo from new path /enterprise-server@/foo - oldPaths.add(currentPath.replace(`/enterprise-server@${latest}/`, '/enterprise/user/')) - } - }) - } - // ------ END MODERN VERSION FORMAT REPLACEMENTS ------// - - // ------ BEGIN ONEOFF REPLACEMENTS ------// - - // create special old path /enterprise-server-releases from current path /enterprise-server@/admin/all-releases - if ( - versionSatisfiesRange(currentVersion, `=${latest}`) && - currentPath.endsWith('/admin/all-releases') - ) { - oldPaths.add('/enterprise-server-releases') - } - - // ------ END ONEOFF REPLACEMENTS ------// - - // For each old path added to the set above, do the following... - new Set(oldPaths).forEach((oldPath) => { - // for English only, remove language code - if (languageCode === 'en') { - oldPaths.add(getPathWithoutLanguage(oldPath)) - } - - // add language code - oldPaths.add(getPathWithLanguage(oldPath, languageCode)) - }) - - // exclude any empty old paths that may have been derived - oldPaths.delete('') - oldPaths.delete('/') - - return oldPaths -} diff --git a/lib/redirects/permalinks.js b/lib/redirects/permalinks.js index 7b4b832a9d..65f61e6dbe 100644 --- a/lib/redirects/permalinks.js +++ b/lib/redirects/permalinks.js @@ -1,77 +1,48 @@ -import path from 'path' -import patterns from '../patterns.js' -import { allVersions } from '../all-versions.js' -import getOldPathsFromPermalink from './get-old-paths-from-permalink.js' import { getVersionStringFromPath } from '../path-utils.js' -import { getNewVersionedPath } from '../old-versions-utils.js' -import removeFPTFromPath from '../remove-fpt-from-path.js' -const supportedVersions = new Set(Object.keys(allVersions)) +import nonEnterpriseDefaultVersion from '../non-enterprise-default-version.js' -export default function generateRedirectsForPermalinks(permalinks, redirectFrontmatter, versions) { - // account for Array or String frontmatter entries - const redirectFrontmatterOldPaths = redirectFrontmatter - ? Array.from([redirectFrontmatter]).flat() - : [] +export default function generateRedirectsForPermalinks(permalinks, redirectFrontmatter) { + if (!Array.isArray(redirectFrontmatter)) { + // TypeScript could have prevented this from ever happening. + throw new Error(`redirectFrontmatter is supposed to be an array`) + } const redirects = {} - // for every permalink... - permalinks.forEach((permalink) => { - // get an array of possible old paths, e.g., /desktop/guides/ from current permalink /desktop/ - const possibleOldPaths = getOldPathsFromPermalink( - permalink.href, - permalink.languageCode, - permalink.pageVersion - ) - - // for each old path, add a redirect to the current permalink - possibleOldPaths.forEach((oldPath) => { - redirects[oldPath] = permalink.href - }) - - // for every redirect frontmatter old path... - redirectFrontmatterOldPaths.forEach((frontmatterOldPath) => { - // remove trailing slashes (sometimes present in frontmatter) - frontmatterOldPath = frontmatterOldPath.replace(patterns.trailingSlash, '$1') - - // support hardcoded versions in redirect frontmatter - if (supportedVersions.has(frontmatterOldPath.split('/')[1])) { - redirects[frontmatterOldPath] = permalink.href - redirects[`/en${frontmatterOldPath}`] = permalink.href + redirectFrontmatter.forEach((frontmatterOldPath) => { + if (!frontmatterOldPath.startsWith('/')) { + throw new Error( + `'${frontmatterOldPath}' is not a valid redirect_from frontmatter value because it doesn't start with a /` + ) + } + permalinks.forEach((permalink) => { + // Exceptions where the `redirect_from` entries are too old + if (frontmatterOldPath.startsWith('/enterprise/admin/guides/')) { + // Let's pretend we didn't see that. + frontmatterOldPath = ('/' + frontmatterOldPath.split('/').slice(2).join('/')).replace( + '/admin/guides/', + '/admin/' + ) + } else if (frontmatterOldPath.startsWith('/enterprise/')) { + // Let's pretend we didn't see that. + frontmatterOldPath = '/' + frontmatterOldPath.split('/').slice(2).join('/') } - // get the old path for the current permalink version - let versionedFrontmatterOldPath = path.posix.join( - '/', - permalink.languageCode, - getNewVersionedPath(frontmatterOldPath) - ) - const versionFromPath = getVersionStringFromPath(versionedFrontmatterOldPath) - versionedFrontmatterOldPath = removeFPTFromPath( - versionedFrontmatterOldPath.replace(versionFromPath, permalink.pageVersion) - ) - - // add it to the redirects object - redirects[versionedFrontmatterOldPath] = permalink.href - - // then get an array of possible alternative old paths from the current versioned old path - const possibleOldPathsForVersionedOldPaths = getOldPathsFromPermalink( - versionedFrontmatterOldPath, - permalink.languageCode, - permalink.pageVersion - ) - - // and add each one to the redirects object - possibleOldPathsForVersionedOldPaths.forEach((oldPath) => { - redirects[oldPath] = permalink.href - }) + // We're only interested in the version string if it's a supported version. + const ver = getVersionStringFromPath(permalink.hrefWithoutLanguage, true) + // This tests if the permalink's version was free-pro-team. + // If that's the case, put an entry into the `redirects` without + // any version prefix. + // Some pages don't have a version which means it's supported by all + // versions (you'll find `versions: '*'` in frontmatter). + // E.g. /en/get-started/learning-about-github + if (!ver || ver === nonEnterpriseDefaultVersion) { + redirects[frontmatterOldPath] = permalink.hrefWithoutLanguage + } else if (ver) { + redirects[`/${ver}${frontmatterOldPath}`] = permalink.hrefWithoutLanguage + } }) }) - // filter for unique entries only - Object.entries(redirects).forEach(([oldPath, newPath]) => { - if (oldPath === newPath) delete redirects[oldPath] - }) - return redirects } diff --git a/lib/redirects/precompile.js b/lib/redirects/precompile.js index c854d6816d..0ddcaef23a 100755 --- a/lib/redirects/precompile.js +++ b/lib/redirects/precompile.js @@ -5,9 +5,9 @@ import { isPromise } from 'util/types' import { fileURLToPath } from 'url' import { readCompressedJsonFileFallback } from '../read-json-file.js' -import { latest } from '../../lib/enterprise-server-releases.js' import getExceptionRedirects from './exception-redirects.js' -import { languageKeys } from '../languages.js' + +import { latest } from '../enterprise-server-releases.js' function diskMemoize(filePath, asyncFn, maxAgeSeconds = 60 * 60) { // The logging that the disk memoizer does is pretty useful to humans, @@ -35,28 +35,25 @@ function diskMemoize(filePath, asyncFn, maxAgeSeconds = 60 * 60) { const promise = asyncFn(...args) assert(isPromise(promise), "memoized function didn't return a promise") return promise.then(async (value) => { - await fs.writeFile(filePath, JSON.stringify(value), 'utf-8') + await fs.writeFile( + filePath, + JSON.stringify(value, undefined, process.env.NODE_ENV === 'development' ? 2 : 0), + 'utf-8' + ) + return value }) } } const __dirname = path.dirname(fileURLToPath(import.meta.url)) -const DISK_CACHE_FILEPATH = path.join(__dirname, `.redirects-cache_${languageKeys.join('_')}.json`) +const DISK_CACHE_FILEPATH = path.join(__dirname, '.redirects-cache.json') // This function runs at server warmup and precompiles possible redirect routes. // It outputs them in key-value pairs within a neat Javascript object: { oldPath: newPath } const precompileRedirects = diskMemoize(DISK_CACHE_FILEPATH, async (pageList) => { const allRedirects = readCompressedJsonFileFallback('./lib/redirects/static/developer.json') - // Replace hardcoded 'latest' with real value in the redirected path - Object.entries(allRedirects).forEach(([oldPath, newPath]) => { - allRedirects[oldPath] = newPath.replace( - 'enterprise-server@latest', - `enterprise-server@${latest}` - ) - }) - // Exception redirects are those that are essentially unicorn one-offs. // For example, we have redirects for documents that used to be on // `free-pro-team@latest` but have now been moved to @@ -65,16 +62,29 @@ const precompileRedirects = diskMemoize(DISK_CACHE_FILEPATH, async (pageList) => // comments and it's also possible to write 1 destination URL once // for each N redirect origins const exceptions = getExceptionRedirects() - Object.entries(exceptions).forEach(([fromURL, toURL]) => { - allRedirects[fromURL] = `/en${toURL}` - for (const languageCode of languageKeys) { - allRedirects[`/${languageCode}${fromURL}`] = `/${languageCode}${toURL}` - } - }) + Object.assign(allRedirects, exceptions) // CURRENT PAGES PERMALINKS AND FRONTMATTER // create backwards-compatible old paths for page permalinks and frontmatter redirects - pageList.forEach((page) => Object.assign(allRedirects, page.buildRedirects())) + pageList + .filter((page) => page.languageCode === 'en') + .forEach((page) => Object.assign(allRedirects, page.buildRedirects())) + + Object.entries(allRedirects).forEach(([fromURI, toURI]) => { + // If the destination URL has a hardcoded `enterprise-server@latest` in + // it we need to rewrite that now. + // We never want to redirect to that as the final URL (in the 301 response) + // but it might make sense for it to be in the `developer.json` + // file since that it static. + // + // + if (toURI.includes('/enterprise-server@latest')) { + allRedirects[fromURI] = toURI.replace( + '/enterprise-server@latest', + `/enterprise-server@${latest}` + ) + } + }) return allRedirects }) diff --git a/lib/redirects/static/archived-redirects-from-213-to-217.json b/lib/redirects/static/archived-redirects-from-213-to-217.json index ab6cfe5d69..e1b8ee66c1 100644 --- a/lib/redirects/static/archived-redirects-from-213-to-217.json +++ b/lib/redirects/static/archived-redirects-from-213-to-217.json @@ -1,28239 +1,8480 @@ { - "/en/enterprise/2.13/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.13/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.13/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.13/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.13/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.13/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/en/enterprise/2.13/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.13/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.13/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.13/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.13/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.13/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/en/enterprise/2.13/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.13/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.13/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.13/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.13/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.13/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/en/enterprise/2.13/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.13/admin/articles/using-github-task-runner", - "/enterprise/2.13/admin/articles/using-github-task-runner": "/en/enterprise/2.13/admin/articles/using-github-task-runner", - "/enterprise/2.13/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.13/admin/articles/using-github-task-runner", - "/en/enterprise/2.13/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.13/admin/clustering/about-cluster-nodes", - "/enterprise/2.13/admin/clustering/about-cluster-nodes": "/en/enterprise/2.13/admin/clustering/about-cluster-nodes", - "/enterprise/2.13/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.13/admin/clustering/about-cluster-nodes", - "/en/enterprise/2.13/admin/guides/clustering/clustering-overview": "/en/enterprise/2.13/admin/clustering/clustering-overview", - "/enterprise/2.13/admin/clustering/clustering-overview": "/en/enterprise/2.13/admin/clustering/clustering-overview", - "/enterprise/2.13/admin/guides/clustering/clustering-overview": "/en/enterprise/2.13/admin/clustering/clustering-overview", - "/en/enterprise/2.13/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.13/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.13/admin/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.13/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.13/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.13/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/en/enterprise/2.13/admin/guides/clustering": "/en/enterprise/2.13/admin/clustering", - "/enterprise/2.13/admin/clustering": "/en/enterprise/2.13/admin/clustering", - "/enterprise/2.13/admin/guides/clustering": "/en/enterprise/2.13/admin/clustering", - "/en/enterprise/2.13/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.13/admin/clustering/initializing-the-cluster", - "/enterprise/2.13/admin/clustering/initializing-the-cluster": "/en/enterprise/2.13/admin/clustering/initializing-the-cluster", - "/enterprise/2.13/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.13/admin/clustering/initializing-the-cluster", - "/en/enterprise/2.13/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.13/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.13/admin/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.13/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.13/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.13/admin/clustering/managing-a-github-enterprise-server-cluster", - "/en/enterprise/2.13/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.13/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.13/admin/clustering/monitoring-cluster-nodes": "/en/enterprise/2.13/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.13/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.13/admin/clustering/monitoring-cluster-nodes", - "/en/enterprise/2.13/admin/guides/clustering/network-configuration": "/en/enterprise/2.13/admin/clustering/network-configuration", - "/enterprise/2.13/admin/clustering/network-configuration": "/en/enterprise/2.13/admin/clustering/network-configuration", - "/enterprise/2.13/admin/guides/clustering/network-configuration": "/en/enterprise/2.13/admin/clustering/network-configuration", - "/en/enterprise/2.13/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.13/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.13/admin/clustering/replacing-a-cluster-node": "/en/enterprise/2.13/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.13/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.13/admin/clustering/replacing-a-cluster-node", - "/en/enterprise/2.13/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.13/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.13/admin/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.13/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.13/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.13/admin/clustering/setting-up-the-cluster-instances", - "/en/enterprise/2.13/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.13/admin/clustering/upgrading-a-cluster", - "/enterprise/2.13/admin/clustering/upgrading-a-cluster": "/en/enterprise/2.13/admin/clustering/upgrading-a-cluster", - "/enterprise/2.13/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.13/admin/clustering/upgrading-a-cluster", - "/en/enterprise/2.13/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.13/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.13/admin/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.13/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.13/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.13/admin/developer-workflow/about-pre-receive-hooks", - "/en/enterprise/2.13/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.13/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.13/admin/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.13/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.13/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.13/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/en/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/en/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/en/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/en/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.13/admin/developer-workflow/blocking-force-pushes", - "/en/enterprise/2.13/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.13/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.13/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.13/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.13/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.13/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/en/enterprise/2.13/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.13/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.13/admin/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.13/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.13/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.13/admin/developer-workflow/continuous-integration-using-jenkins", - "/en/enterprise/2.13/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.13/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.13/admin/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.13/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.13/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.13/admin/developer-workflow/continuous-integration-using-travis-ci", - "/en/enterprise/2.13/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.13/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/en/enterprise/2.13/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.13/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/en/enterprise/2.13/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.13/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.13/admin/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.13/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.13/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.13/admin/developer-workflow/customizing-your-instance-with-integrations", - "/en/enterprise/2.13/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.13/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.13/admin/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.13/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.13/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.13/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/en/enterprise/2.13/admin/guides/developer-workflow": "/en/enterprise/2.13/admin/developer-workflow", - "/enterprise/2.13/admin/developer-workflow": "/en/enterprise/2.13/admin/developer-workflow", - "/enterprise/2.13/admin/guides/developer-workflow": "/en/enterprise/2.13/admin/developer-workflow", - "/en/enterprise/2.13/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.13/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.13/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/en/enterprise/2.13/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.13/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.13/admin/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.13/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.13/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.13/admin/developer-workflow/managing-projects-using-jira", - "/en/enterprise/2.13/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.13/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.13/admin/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.13/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.13/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.13/admin/developer-workflow/troubleshooting-service-hooks", - "/en/enterprise/2.13/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.13/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.13/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.13/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.13/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.13/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/en/enterprise/2.13/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.13/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.13/admin/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.13/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.13/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.13/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/en/enterprise/2.13/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.13/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.13/admin/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.13/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.13/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.13/admin/enterprise-support/about-github-enterprise-support", - "/en/enterprise/2.13/admin/guides/enterprise-support/about-github-premium-support": "/en/enterprise/2.13/admin/enterprise-support/about-github-premium-support", - "/enterprise/2.13/admin/enterprise-support/about-github-premium-support": "/en/enterprise/2.13/admin/enterprise-support/about-github-premium-support", - "/enterprise/2.13/admin/guides/enterprise-support/about-github-premium-support": "/en/enterprise/2.13/admin/enterprise-support/about-github-premium-support", - "/en/enterprise/2.13/admin/guides/enterprise-support": "/en/enterprise/2.13/admin/enterprise-support", - "/enterprise/2.13/admin/enterprise-support": "/en/enterprise/2.13/admin/enterprise-support", - "/enterprise/2.13/admin/guides/enterprise-support": "/en/enterprise/2.13/admin/enterprise-support", - "/en/enterprise/2.13/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.13/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.13/admin/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.13/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.13/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.13/admin/enterprise-support/preparing-to-submit-a-ticket", - "/en/enterprise/2.13/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.13/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.13/admin/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.13/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.13/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.13/admin/enterprise-support/providing-data-to-github-support", - "/en/enterprise/2.13/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.13/admin/enterprise-support/reaching-github-support", - "/enterprise/2.13/admin/enterprise-support/reaching-github-support": "/en/enterprise/2.13/admin/enterprise-support/reaching-github-support", - "/enterprise/2.13/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.13/admin/enterprise-support/reaching-github-support", - "/en/enterprise/2.13/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.13/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.13/admin/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.13/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.13/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.13/admin/enterprise-support/receiving-help-from-github-support", - "/en/enterprise/2.13/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.13/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.13/admin/enterprise-support/submitting-a-ticket": "/en/enterprise/2.13/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.13/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.13/admin/enterprise-support/submitting-a-ticket", - "/en/enterprise/2.13/admin/guides": "/en/enterprise/2.13/admin", - "/enterprise/2.13/admin": "/en/enterprise/2.13/admin", - "/enterprise/2.13/admin/guides": "/en/enterprise/2.13/admin", - "/en/enterprise/2.13/admin/guides/installation/about-geo-replication": "/en/enterprise/2.13/admin/installation/about-geo-replication", - "/enterprise/2.13/admin/installation/about-geo-replication": "/en/enterprise/2.13/admin/installation/about-geo-replication", - "/enterprise/2.13/admin/guides/installation/about-geo-replication": "/en/enterprise/2.13/admin/installation/about-geo-replication", - "/en/enterprise/2.13/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.13/admin/installation/about-high-availability-configuration", - "/enterprise/2.13/admin/installation/about-high-availability-configuration": "/en/enterprise/2.13/admin/installation/about-high-availability-configuration", - "/enterprise/2.13/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.13/admin/installation/about-high-availability-configuration", - "/en/enterprise/2.13/admin/guides/installation/about-license-files": "/en/enterprise/2.13/admin/installation/about-license-files", - "/enterprise/2.13/admin/installation/about-license-files": "/en/enterprise/2.13/admin/installation/about-license-files", - "/enterprise/2.13/admin/guides/installation/about-license-files": "/en/enterprise/2.13/admin/installation/about-license-files", - "/en/enterprise/2.13/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.13/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.13/admin/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.13/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.13/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.13/admin/installation/about-the-github-enterprise-server-api", - "/en/enterprise/2.13/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.13/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.13/admin/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.13/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.13/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.13/admin/installation/accessing-the-administrative-shell-ssh", - "/en/enterprise/2.13/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.13/admin/installation/accessing-the-management-console", - "/enterprise/2.13/admin/installation/accessing-the-management-console": "/en/enterprise/2.13/admin/installation/accessing-the-management-console", - "/enterprise/2.13/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.13/admin/installation/accessing-the-management-console", - "/en/enterprise/2.13/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.13/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.13/admin/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.13/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.13/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.13/admin/installation/accessing-the-monitor-dashboard", - "/en/enterprise/2.13/admin/guides/installation/activity-dashboard": "/en/enterprise/2.13/admin/installation/activity-dashboard", - "/enterprise/2.13/admin/installation/activity-dashboard": "/en/enterprise/2.13/admin/installation/activity-dashboard", - "/enterprise/2.13/admin/guides/installation/activity-dashboard": "/en/enterprise/2.13/admin/installation/activity-dashboard", - "/en/enterprise/2.13/admin/guides/installation/audit-logging": "/en/enterprise/2.13/admin/installation/audit-logging", - "/enterprise/2.13/admin/installation/audit-logging": "/en/enterprise/2.13/admin/installation/audit-logging", - "/enterprise/2.13/admin/guides/installation/audit-logging": "/en/enterprise/2.13/admin/installation/audit-logging", - "/en/enterprise/2.13/admin/guides/installation/audited-actions": "/en/enterprise/2.13/admin/installation/audited-actions", - "/enterprise/2.13/admin/installation/audited-actions": "/en/enterprise/2.13/admin/installation/audited-actions", - "/enterprise/2.13/admin/guides/installation/audited-actions": "/en/enterprise/2.13/admin/installation/audited-actions", - "/en/enterprise/2.13/admin/guides/installation/command-line-utilities": "/en/enterprise/2.13/admin/installation/command-line-utilities", - "/enterprise/2.13/admin/installation/command-line-utilities": "/en/enterprise/2.13/admin/installation/command-line-utilities", - "/enterprise/2.13/admin/guides/installation/command-line-utilities": "/en/enterprise/2.13/admin/installation/command-line-utilities", - "/en/enterprise/2.13/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.13/admin/installation/configuring-a-hostname", - "/enterprise/2.13/admin/installation/configuring-a-hostname": "/en/enterprise/2.13/admin/installation/configuring-a-hostname", - "/enterprise/2.13/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.13/admin/installation/configuring-a-hostname", - "/en/enterprise/2.13/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.13/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.13/admin/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.13/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.13/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.13/admin/installation/configuring-an-outbound-web-proxy-server", - "/en/enterprise/2.13/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.13/admin/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.13/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-backups-on-your-appliance", - "/en/enterprise/2.13/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.13/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.13/admin/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.13/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.13/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.13/admin/installation/configuring-built-in-firewall-rules", - "/en/enterprise/2.13/admin/guides/installation/configuring-collectd": "/en/enterprise/2.13/admin/installation/configuring-collectd", - "/enterprise/2.13/admin/installation/configuring-collectd": "/en/enterprise/2.13/admin/installation/configuring-collectd", - "/enterprise/2.13/admin/guides/installation/configuring-collectd": "/en/enterprise/2.13/admin/installation/configuring-collectd", - "/en/enterprise/2.13/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.13/admin/installation/configuring-dns-nameservers", - "/enterprise/2.13/admin/installation/configuring-dns-nameservers": "/en/enterprise/2.13/admin/installation/configuring-dns-nameservers", - "/enterprise/2.13/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.13/admin/installation/configuring-dns-nameservers", - "/en/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.13/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.13/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/en/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.13/admin/installation/configuring-git-large-file-storage": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.13/admin/installation/configuring-git-large-file-storage", - "/en/enterprise/2.13/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.13/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.13/admin/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.13/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.13/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.13/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/en/enterprise/2.13/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.13/admin/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.13/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-github-pages-on-your-appliance", - "/en/enterprise/2.13/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.13/admin/installation/configuring-rate-limits", - "/enterprise/2.13/admin/installation/configuring-rate-limits": "/en/enterprise/2.13/admin/installation/configuring-rate-limits", - "/enterprise/2.13/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.13/admin/installation/configuring-rate-limits", - "/en/enterprise/2.13/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.13/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.13/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.13/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/en/enterprise/2.13/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.13/admin/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.13/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/installation/configuring-the-github-enterprise-server-appliance", - "/en/enterprise/2.13/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.13/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.13/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.13/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.13/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.13/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/en/enterprise/2.13/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.13/admin/installation/configuring-time-synchronization", - "/enterprise/2.13/admin/installation/configuring-time-synchronization": "/en/enterprise/2.13/admin/installation/configuring-time-synchronization", - "/enterprise/2.13/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.13/admin/installation/configuring-time-synchronization", - "/en/enterprise/2.13/admin/guides/installation/configuring-tls": "/en/enterprise/2.13/admin/installation/configuring-tls", - "/enterprise/2.13/admin/installation/configuring-tls": "/en/enterprise/2.13/admin/installation/configuring-tls", - "/enterprise/2.13/admin/guides/installation/configuring-tls": "/en/enterprise/2.13/admin/installation/configuring-tls", - "/en/enterprise/2.13/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.13/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.13/admin/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.13/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.13/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.13/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/en/enterprise/2.13/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.13/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.13/admin/installation/creating-a-high-availability-replica": "/en/enterprise/2.13/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.13/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.13/admin/installation/creating-a-high-availability-replica", - "/en/enterprise/2.13/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.13/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.13/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.13/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.13/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.13/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.13/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.13/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.13/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.13/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.13/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/en/enterprise/2.13/admin/guides/installation/downloading-your-license": "/en/enterprise/2.13/admin/installation/downloading-your-license", - "/enterprise/2.13/admin/installation/downloading-your-license": "/en/enterprise/2.13/admin/installation/downloading-your-license", - "/enterprise/2.13/admin/guides/installation/downloading-your-license": "/en/enterprise/2.13/admin/installation/downloading-your-license", - "/en/enterprise/2.13/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.13/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.13/admin/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.13/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.13/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.13/admin/installation/enabling-and-scheduling-maintenance-mode", - "/en/enterprise/2.13/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.13/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.13/admin/installation/enabling-automatic-update-checks": "/en/enterprise/2.13/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.13/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.13/admin/installation/enabling-automatic-update-checks", - "/en/enterprise/2.13/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.13/admin/installation/enabling-private-mode", - "/enterprise/2.13/admin/installation/enabling-private-mode": "/en/enterprise/2.13/admin/installation/enabling-private-mode", - "/enterprise/2.13/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.13/admin/installation/enabling-private-mode", - "/en/enterprise/2.13/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.13/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.13/admin/installation/enabling-subdomain-isolation": "/en/enterprise/2.13/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.13/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.13/admin/installation/enabling-subdomain-isolation", - "/en/enterprise/2.13/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.13/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.13/admin/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.13/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.13/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.13/admin/installation/increasing-cpu-or-memory-resources", - "/en/enterprise/2.13/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.13/admin/installation/increasing-storage-capacity", - "/enterprise/2.13/admin/installation/increasing-storage-capacity": "/en/enterprise/2.13/admin/installation/increasing-storage-capacity", - "/enterprise/2.13/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.13/admin/installation/increasing-storage-capacity", - "/en/enterprise/2.13/admin/guides/installation": "/en/enterprise/2.13/admin/installation", - "/enterprise/2.13/admin/installation": "/en/enterprise/2.13/admin/installation", - "/enterprise/2.13/admin/guides/installation": "/en/enterprise/2.13/admin/installation", - "/en/enterprise/2.13/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.13/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.13/admin/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.13/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.13/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.13/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-aws", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-azure", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-vmware", - "/en/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-xenserver", - "/en/enterprise/2.13/admin/guides/installation/log-forwarding": "/en/enterprise/2.13/admin/installation/log-forwarding", - "/enterprise/2.13/admin/installation/log-forwarding": "/en/enterprise/2.13/admin/installation/log-forwarding", - "/enterprise/2.13/admin/guides/installation/log-forwarding": "/en/enterprise/2.13/admin/installation/log-forwarding", - "/en/enterprise/2.13/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.13/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.13/admin/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.13/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.13/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.13/admin/installation/managing-your-github-enterprise-server-license", - "/en/enterprise/2.13/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.13/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.13/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.13/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.13/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.13/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/en/enterprise/2.13/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.13/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.13/admin/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.13/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.13/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.13/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/en/enterprise/2.13/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.13/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.13/admin/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.13/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.13/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.13/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/en/enterprise/2.13/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.13/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.13/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.13/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.13/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.13/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/en/enterprise/2.13/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.13/admin/installation/monitoring-using-snmp", - "/enterprise/2.13/admin/installation/monitoring-using-snmp": "/en/enterprise/2.13/admin/installation/monitoring-using-snmp", - "/enterprise/2.13/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.13/admin/installation/monitoring-using-snmp", - "/en/enterprise/2.13/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.13/admin/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.13/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.13/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/en/enterprise/2.13/admin/guides/installation/network-ports": "/en/enterprise/2.13/admin/installation/network-ports", - "/enterprise/2.13/admin/installation/network-ports": "/en/enterprise/2.13/admin/installation/network-ports", - "/enterprise/2.13/admin/guides/installation/network-ports": "/en/enterprise/2.13/admin/installation/network-ports", - "/en/enterprise/2.13/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.13/admin/installation/recommended-alert-thresholds", - "/enterprise/2.13/admin/installation/recommended-alert-thresholds": "/en/enterprise/2.13/admin/installation/recommended-alert-thresholds", - "/enterprise/2.13/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.13/admin/installation/recommended-alert-thresholds", - "/en/enterprise/2.13/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.13/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.13/admin/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.13/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.13/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.13/admin/installation/recovering-a-high-availability-configuration", - "/en/enterprise/2.13/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.13/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.13/admin/installation/removing-a-high-availability-replica": "/en/enterprise/2.13/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.13/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.13/admin/installation/removing-a-high-availability-replica", - "/en/enterprise/2.13/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.13/admin/installation/searching-the-audit-log", - "/enterprise/2.13/admin/installation/searching-the-audit-log": "/en/enterprise/2.13/admin/installation/searching-the-audit-log", - "/enterprise/2.13/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.13/admin/installation/searching-the-audit-log", - "/en/enterprise/2.13/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.13/admin/installation/setting-git-push-limits", - "/enterprise/2.13/admin/installation/setting-git-push-limits": "/en/enterprise/2.13/admin/installation/setting-git-push-limits", - "/enterprise/2.13/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.13/admin/installation/setting-git-push-limits", - "/en/enterprise/2.13/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.13/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.13/admin/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.13/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.13/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.13/admin/installation/setting-up-a-github-enterprise-server-instance", - "/en/enterprise/2.13/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.13/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.13/admin/installation/setting-up-a-staging-instance": "/en/enterprise/2.13/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.13/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.13/admin/installation/setting-up-a-staging-instance", - "/en/enterprise/2.13/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.13/admin/installation/setting-up-external-monitoring", - "/enterprise/2.13/admin/installation/setting-up-external-monitoring": "/en/enterprise/2.13/admin/installation/setting-up-external-monitoring", - "/enterprise/2.13/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.13/admin/installation/setting-up-external-monitoring", - "/en/enterprise/2.13/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.13/admin/installation/site-admin-dashboard", - "/enterprise/2.13/admin/installation/site-admin-dashboard": "/en/enterprise/2.13/admin/installation/site-admin-dashboard", - "/enterprise/2.13/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.13/admin/installation/site-admin-dashboard", - "/en/enterprise/2.13/admin/guides/installation/system-overview": "/en/enterprise/2.13/admin/installation/system-overview", - "/enterprise/2.13/admin/installation/system-overview": "/en/enterprise/2.13/admin/installation/system-overview", - "/enterprise/2.13/admin/guides/installation/system-overview": "/en/enterprise/2.13/admin/installation/system-overview", - "/en/enterprise/2.13/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.13/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.13/admin/installation/troubleshooting-ssl-errors": "/en/enterprise/2.13/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.13/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.13/admin/installation/troubleshooting-ssl-errors", - "/en/enterprise/2.13/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.13/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.13/admin/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.13/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.13/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.13/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/en/enterprise/2.13/admin/guides/installation/updating-your-license": "/en/enterprise/2.13/admin/installation/updating-your-license", - "/enterprise/2.13/admin/installation/updating-your-license": "/en/enterprise/2.13/admin/installation/updating-your-license", - "/enterprise/2.13/admin/guides/installation/updating-your-license": "/en/enterprise/2.13/admin/installation/updating-your-license", - "/en/enterprise/2.13/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.13/admin/installation/upgrade-requirements", - "/enterprise/2.13/admin/installation/upgrade-requirements": "/en/enterprise/2.13/admin/installation/upgrade-requirements", - "/enterprise/2.13/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.13/admin/installation/upgrade-requirements", - "/en/enterprise/2.13/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.13/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.13/admin/installation/upgrading-github-enterprise-server": "/en/enterprise/2.13/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.13/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.13/admin/installation/upgrading-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.13/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.13/admin/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.13/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.13/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.13/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/en/enterprise/2.13/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.13/admin/installation/validating-your-domain-settings", - "/enterprise/2.13/admin/installation/validating-your-domain-settings": "/en/enterprise/2.13/admin/installation/validating-your-domain-settings", - "/enterprise/2.13/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.13/admin/installation/validating-your-domain-settings", - "/en/enterprise/2.13/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.13/admin/installation/viewing-push-logs", - "/enterprise/2.13/admin/installation/viewing-push-logs": "/en/enterprise/2.13/admin/installation/viewing-push-logs", - "/enterprise/2.13/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.13/admin/installation/viewing-push-logs", - "/en/enterprise/2.13/admin/guides/migrations/about-migrations": "/en/enterprise/2.13/admin/migrations/about-migrations", - "/enterprise/2.13/admin/migrations/about-migrations": "/en/enterprise/2.13/admin/migrations/about-migrations", - "/enterprise/2.13/admin/guides/migrations/about-migrations": "/en/enterprise/2.13/admin/migrations/about-migrations", - "/en/enterprise/2.13/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.13/admin/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.13/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.13/admin/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.13/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/completing-the-import-on-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.13/admin/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.13/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.13/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.13/admin/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.13/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.13/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.13/admin/migrations/exporting-migration-data-from-githubcom", - "/en/enterprise/2.13/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.13/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.13/admin/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.13/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.13/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.13/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/en/enterprise/2.13/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.13/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.13/admin/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.13/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.13/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.13/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/en/enterprise/2.13/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.13/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.13/admin/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.13/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.13/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.13/admin/migrations/generating-a-list-of-migration-conflicts", - "/en/enterprise/2.13/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.13/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.13/admin/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.13/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.13/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.13/admin/migrations/importing-data-from-third-party-version-control-systems", - "/en/enterprise/2.13/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.13/admin/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.13/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/migrations": "/en/enterprise/2.13/admin/migrations", - "/enterprise/2.13/admin/migrations": "/en/enterprise/2.13/admin/migrations", - "/enterprise/2.13/admin/guides/migrations": "/en/enterprise/2.13/admin/migrations", - "/en/enterprise/2.13/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.13/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.13/admin/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.13/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.13/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.13/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/en/enterprise/2.13/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.13/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.13/admin/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.13/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.13/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.13/admin/migrations/preparing-the-githubcom-source-organization", - "/en/enterprise/2.13/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.13/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.13/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.13/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/en/enterprise/2.13/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.13/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.13/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.13/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.13/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.13/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/en/enterprise/2.13/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.13/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.13/admin/migrations/reviewing-migration-conflicts": "/en/enterprise/2.13/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.13/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.13/admin/migrations/reviewing-migration-conflicts", - "/en/enterprise/2.13/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.13/admin/migrations/reviewing-migration-data", - "/enterprise/2.13/admin/migrations/reviewing-migration-data": "/en/enterprise/2.13/admin/migrations/reviewing-migration-data", - "/enterprise/2.13/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.13/admin/migrations/reviewing-migration-data", - "/en/enterprise/2.13/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.13/admin/user-management/about-global-webhooks", - "/enterprise/2.13/admin/user-management/about-global-webhooks": "/en/enterprise/2.13/admin/user-management/about-global-webhooks", - "/enterprise/2.13/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.13/admin/user-management/about-global-webhooks", - "/en/enterprise/2.13/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.13/admin/user-management/adding-people-to-teams", - "/enterprise/2.13/admin/user-management/adding-people-to-teams": "/en/enterprise/2.13/admin/user-management/adding-people-to-teams", - "/enterprise/2.13/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.13/admin/user-management/adding-people-to-teams", - "/en/enterprise/2.13/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.13/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.13/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.13/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.13/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.13/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/en/enterprise/2.13/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.13/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.13/admin/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.13/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.13/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.13/admin/user-management/archiving-and-unarchiving-repositories", - "/en/enterprise/2.13/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.13/admin/user-management/auditing-ssh-keys", - "/enterprise/2.13/admin/user-management/auditing-ssh-keys": "/en/enterprise/2.13/admin/user-management/auditing-ssh-keys", - "/enterprise/2.13/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.13/admin/user-management/auditing-ssh-keys", - "/en/enterprise/2.13/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.13/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.13/admin/user-management/auditing-users-across-your-instance": "/en/enterprise/2.13/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.13/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.13/admin/user-management/auditing-users-across-your-instance", - "/en/enterprise/2.13/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.13/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.13/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.13/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.13/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.13/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/en/enterprise/2.13/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.13/admin/user-management/basic-account-settings", - "/enterprise/2.13/admin/user-management/basic-account-settings": "/en/enterprise/2.13/admin/user-management/basic-account-settings", - "/enterprise/2.13/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.13/admin/user-management/basic-account-settings", - "/en/enterprise/2.13/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.13/admin/user-management/best-practices-for-user-security", - "/enterprise/2.13/admin/user-management/best-practices-for-user-security": "/en/enterprise/2.13/admin/user-management/best-practices-for-user-security", - "/enterprise/2.13/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.13/admin/user-management/best-practices-for-user-security", - "/en/enterprise/2.13/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.13/admin/user-management/changing-authentication-methods", - "/enterprise/2.13/admin/user-management/changing-authentication-methods": "/en/enterprise/2.13/admin/user-management/changing-authentication-methods", - "/enterprise/2.13/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.13/admin/user-management/changing-authentication-methods", - "/en/enterprise/2.13/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.13/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.13/admin/user-management/configuring-email-for-notifications": "/en/enterprise/2.13/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.13/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.13/admin/user-management/configuring-email-for-notifications", - "/en/enterprise/2.13/admin/guides/user-management/creating-organizations": "/en/enterprise/2.13/admin/user-management/creating-organizations", - "/enterprise/2.13/admin/user-management/creating-organizations": "/en/enterprise/2.13/admin/user-management/creating-organizations", - "/enterprise/2.13/admin/guides/user-management/creating-organizations": "/en/enterprise/2.13/admin/user-management/creating-organizations", - "/en/enterprise/2.13/admin/guides/user-management/creating-teams": "/en/enterprise/2.13/admin/user-management/creating-teams", - "/enterprise/2.13/admin/user-management/creating-teams": "/en/enterprise/2.13/admin/user-management/creating-teams", - "/enterprise/2.13/admin/guides/user-management/creating-teams": "/en/enterprise/2.13/admin/user-management/creating-teams", - "/en/enterprise/2.13/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.13/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.13/admin/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.13/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.13/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.13/admin/user-management/customizing-user-messages-on-your-instance", - "/en/enterprise/2.13/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.13/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.13/admin/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.13/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.13/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.13/admin/user-management/disabling-unauthenticated-sign-ups", - "/en/enterprise/2.13/admin/guides/user-management": "/en/enterprise/2.13/admin/user-management", - "/enterprise/2.13/admin/user-management": "/en/enterprise/2.13/admin/user-management", - "/enterprise/2.13/admin/guides/user-management": "/en/enterprise/2.13/admin/user-management", - "/en/enterprise/2.13/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.13/admin/user-management/managing-dormant-users", - "/enterprise/2.13/admin/user-management/managing-dormant-users": "/en/enterprise/2.13/admin/user-management/managing-dormant-users", - "/enterprise/2.13/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.13/admin/user-management/managing-dormant-users", - "/en/enterprise/2.13/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.13/admin/user-management/managing-global-webhooks", - "/enterprise/2.13/admin/user-management/managing-global-webhooks": "/en/enterprise/2.13/admin/user-management/managing-global-webhooks", - "/enterprise/2.13/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.13/admin/user-management/managing-global-webhooks", - "/en/enterprise/2.13/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.13/admin/user-management/organizations-and-teams", - "/enterprise/2.13/admin/user-management/organizations-and-teams": "/en/enterprise/2.13/admin/user-management/organizations-and-teams", - "/enterprise/2.13/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.13/admin/user-management/organizations-and-teams", - "/en/enterprise/2.13/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.13/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.13/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.13/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.13/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.13/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/en/enterprise/2.13/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.13/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.13/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.13/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.13/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.13/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/en/enterprise/2.13/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.13/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.13/admin/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.13/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.13/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.13/admin/user-management/preventing-users-from-creating-organizations", - "/en/enterprise/2.13/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.13/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.13/admin/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.13/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.13/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.13/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/en/enterprise/2.13/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.13/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.13/admin/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.13/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.13/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.13/admin/user-management/promoting-or-demoting-a-site-administrator", - "/en/enterprise/2.13/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.13/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.13/admin/user-management/rebuilding-contributions-data": "/en/enterprise/2.13/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.13/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.13/admin/user-management/rebuilding-contributions-data", - "/en/enterprise/2.13/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.13/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.13/admin/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.13/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.13/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.13/admin/user-management/removing-users-from-teams-and-organizations", - "/en/enterprise/2.13/admin/guides/user-management/repositories": "/en/enterprise/2.13/admin/user-management/repositories", - "/enterprise/2.13/admin/user-management/repositories": "/en/enterprise/2.13/admin/user-management/repositories", - "/enterprise/2.13/admin/guides/user-management/repositories": "/en/enterprise/2.13/admin/user-management/repositories", - "/en/enterprise/2.13/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.13/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.13/admin/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.13/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.13/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.13/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/en/enterprise/2.13/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.13/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.13/admin/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.13/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.13/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.13/admin/user-management/suspending-and-unsuspending-users", - "/en/enterprise/2.13/admin/guides/user-management/user-security": "/en/enterprise/2.13/admin/user-management/user-security", - "/enterprise/2.13/admin/user-management/user-security": "/en/enterprise/2.13/admin/user-management/user-security", - "/enterprise/2.13/admin/guides/user-management/user-security": "/en/enterprise/2.13/admin/user-management/user-security", - "/en/enterprise/2.13/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.13/admin/user-management/using-built-in-authentication", - "/enterprise/2.13/admin/user-management/using-built-in-authentication": "/en/enterprise/2.13/admin/user-management/using-built-in-authentication", - "/enterprise/2.13/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.13/admin/user-management/using-built-in-authentication", - "/en/enterprise/2.13/admin/guides/user-management/using-cas": "/en/enterprise/2.13/admin/user-management/using-cas", - "/enterprise/2.13/admin/user-management/using-cas": "/en/enterprise/2.13/admin/user-management/using-cas", - "/enterprise/2.13/admin/guides/user-management/using-cas": "/en/enterprise/2.13/admin/user-management/using-cas", - "/en/enterprise/2.13/admin/guides/user-management/using-ldap": "/en/enterprise/2.13/admin/user-management/using-ldap", - "/enterprise/2.13/admin/user-management/using-ldap": "/en/enterprise/2.13/admin/user-management/using-ldap", - "/enterprise/2.13/admin/guides/user-management/using-ldap": "/en/enterprise/2.13/admin/user-management/using-ldap", - "/en/enterprise/2.13/admin/guides/user-management/using-saml": "/en/enterprise/2.13/admin/user-management/using-saml", - "/enterprise/2.13/admin/user-management/using-saml": "/en/enterprise/2.13/admin/user-management/using-saml", - "/enterprise/2.13/admin/guides/user-management/using-saml": "/en/enterprise/2.13/admin/user-management/using-saml", - "/enterprise/2.13": "/en/enterprise/2.13", - "/en/enterprise/2.13/articles/3d-file-viewer": "/en/enterprise/2.13/user/articles/3d-file-viewer", - "/enterprise/2.13/user/articles/3d-file-viewer": "/en/enterprise/2.13/user/articles/3d-file-viewer", - "/enterprise/2.13/articles/3d-file-viewer": "/en/enterprise/2.13/user/articles/3d-file-viewer", - "/en/enterprise/2.13/articles/about-archiving-repositories": "/en/enterprise/2.13/user/articles/about-archiving-repositories", - "/enterprise/2.13/user/articles/about-archiving-repositories": "/en/enterprise/2.13/user/articles/about-archiving-repositories", - "/enterprise/2.13/articles/about-archiving-repositories": "/en/enterprise/2.13/user/articles/about-archiving-repositories", - "/en/enterprise/2.13/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.13/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.13/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.13/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.13/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.13/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.13/articles/about-automation-for-project-boards": "/en/enterprise/2.13/user/articles/about-automation-for-project-boards", - "/enterprise/2.13/user/articles/about-automation-for-project-boards": "/en/enterprise/2.13/user/articles/about-automation-for-project-boards", - "/enterprise/2.13/articles/about-automation-for-project-boards": "/en/enterprise/2.13/user/articles/about-automation-for-project-boards", - "/en/enterprise/2.13/articles/about-branch-restrictions": "/en/enterprise/2.13/user/articles/about-branch-restrictions", - "/enterprise/2.13/user/articles/about-branch-restrictions": "/en/enterprise/2.13/user/articles/about-branch-restrictions", - "/enterprise/2.13/articles/about-branch-restrictions": "/en/enterprise/2.13/user/articles/about-branch-restrictions", - "/en/enterprise/2.13/articles/about-branches": "/en/enterprise/2.13/user/articles/about-branches", - "/enterprise/2.13/user/articles/about-branches": "/en/enterprise/2.13/user/articles/about-branches", - "/enterprise/2.13/articles/about-branches": "/en/enterprise/2.13/user/articles/about-branches", - "/en/enterprise/2.13/articles/about-code-owners": "/en/enterprise/2.13/user/articles/about-code-owners", - "/enterprise/2.13/user/articles/about-code-owners": "/en/enterprise/2.13/user/articles/about-code-owners", - "/enterprise/2.13/articles/about-code-owners": "/en/enterprise/2.13/user/articles/about-code-owners", - "/en/enterprise/2.13/articles/about-collaborative-development-models": "/en/enterprise/2.13/user/articles/about-collaborative-development-models", - "/enterprise/2.13/user/articles/about-collaborative-development-models": "/en/enterprise/2.13/user/articles/about-collaborative-development-models", - "/enterprise/2.13/articles/about-collaborative-development-models": "/en/enterprise/2.13/user/articles/about-collaborative-development-models", - "/en/enterprise/2.13/articles/about-commit-email-addresses": "/en/enterprise/2.13/user/articles/about-commit-email-addresses", - "/enterprise/2.13/user/articles/about-commit-email-addresses": "/en/enterprise/2.13/user/articles/about-commit-email-addresses", - "/enterprise/2.13/articles/about-commit-email-addresses": "/en/enterprise/2.13/user/articles/about-commit-email-addresses", - "/en/enterprise/2.13/articles/about-commit-signature-verification": "/en/enterprise/2.13/user/articles/about-commit-signature-verification", - "/enterprise/2.13/user/articles/about-commit-signature-verification": "/en/enterprise/2.13/user/articles/about-commit-signature-verification", - "/enterprise/2.13/articles/about-commit-signature-verification": "/en/enterprise/2.13/user/articles/about-commit-signature-verification", - "/en/enterprise/2.13/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.13/user/articles/about-comparing-branches-in-pull-requests", - "/enterprise/2.13/user/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.13/user/articles/about-comparing-branches-in-pull-requests", - "/enterprise/2.13/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.13/user/articles/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.13/articles/about-conversations-on-github": "/en/enterprise/2.13/user/articles/about-conversations-on-github", - "/enterprise/2.13/user/articles/about-conversations-on-github": "/en/enterprise/2.13/user/articles/about-conversations-on-github", - "/enterprise/2.13/articles/about-conversations-on-github": "/en/enterprise/2.13/user/articles/about-conversations-on-github", - "/en/enterprise/2.13/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/about-duplicate-issues-and-pull-requests", - "/enterprise/2.13/user/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/about-duplicate-issues-and-pull-requests", - "/enterprise/2.13/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.13/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.13/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.13/user/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.13/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.13/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.13/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.13/articles/about-email-notifications": "/en/enterprise/2.13/user/articles/about-email-notifications", - "/enterprise/2.13/user/articles/about-email-notifications": "/en/enterprise/2.13/user/articles/about-email-notifications", - "/enterprise/2.13/articles/about-email-notifications": "/en/enterprise/2.13/user/articles/about-email-notifications", - "/en/enterprise/2.13/articles/about-forks": "/en/enterprise/2.13/user/articles/about-forks", - "/enterprise/2.13/user/articles/about-forks": "/en/enterprise/2.13/user/articles/about-forks", - "/enterprise/2.13/articles/about-forks": "/en/enterprise/2.13/user/articles/about-forks", - "/en/enterprise/2.13/articles/about-gists": "/en/enterprise/2.13/user/articles/about-gists", - "/enterprise/2.13/user/articles/about-gists": "/en/enterprise/2.13/user/articles/about-gists", - "/enterprise/2.13/articles/about-gists": "/en/enterprise/2.13/user/articles/about-gists", - "/en/enterprise/2.13/articles/about-git-large-file-storage": "/en/enterprise/2.13/user/articles/about-git-large-file-storage", - "/enterprise/2.13/user/articles/about-git-large-file-storage": "/en/enterprise/2.13/user/articles/about-git-large-file-storage", - "/enterprise/2.13/articles/about-git-large-file-storage": "/en/enterprise/2.13/user/articles/about-git-large-file-storage", - "/en/enterprise/2.13/articles/about-git-rebase": "/en/enterprise/2.13/user/articles/about-git-rebase", - "/enterprise/2.13/user/articles/about-git-rebase": "/en/enterprise/2.13/user/articles/about-git-rebase", - "/enterprise/2.13/articles/about-git-rebase": "/en/enterprise/2.13/user/articles/about-git-rebase", - "/en/enterprise/2.13/articles/about-git-subtree-merges": "/en/enterprise/2.13/user/articles/about-git-subtree-merges", - "/enterprise/2.13/user/articles/about-git-subtree-merges": "/en/enterprise/2.13/user/articles/about-git-subtree-merges", - "/enterprise/2.13/articles/about-git-subtree-merges": "/en/enterprise/2.13/user/articles/about-git-subtree-merges", - "/en/enterprise/2.13/articles/about-github-mirrors": "/en/enterprise/2.13/user/articles/about-github-mirrors", - "/enterprise/2.13/user/articles/about-github-mirrors": "/en/enterprise/2.13/user/articles/about-github-mirrors", - "/enterprise/2.13/articles/about-github-mirrors": "/en/enterprise/2.13/user/articles/about-github-mirrors", - "/en/enterprise/2.13/articles/about-github-pages-and-jekyll": "/en/enterprise/2.13/user/articles/about-github-pages-and-jekyll", - "/enterprise/2.13/user/articles/about-github-pages-and-jekyll": "/en/enterprise/2.13/user/articles/about-github-pages-and-jekyll", - "/enterprise/2.13/articles/about-github-pages-and-jekyll": "/en/enterprise/2.13/user/articles/about-github-pages-and-jekyll", - "/en/enterprise/2.13/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.13/user/articles/about-issue-and-pull-request-templates", - "/enterprise/2.13/user/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.13/user/articles/about-issue-and-pull-request-templates", - "/enterprise/2.13/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.13/user/articles/about-issue-and-pull-request-templates", - "/en/enterprise/2.13/articles/about-issues": "/en/enterprise/2.13/user/articles/about-issues", - "/enterprise/2.13/user/articles/about-issues": "/en/enterprise/2.13/user/articles/about-issues", - "/enterprise/2.13/articles/about-issues": "/en/enterprise/2.13/user/articles/about-issues", - "/en/enterprise/2.13/articles/about-jekyll-themes-on-github": "/en/enterprise/2.13/user/articles/about-jekyll-themes-on-github", - "/enterprise/2.13/user/articles/about-jekyll-themes-on-github": "/en/enterprise/2.13/user/articles/about-jekyll-themes-on-github", - "/enterprise/2.13/articles/about-jekyll-themes-on-github": "/en/enterprise/2.13/user/articles/about-jekyll-themes-on-github", - "/en/enterprise/2.13/articles/about-labels": "/en/enterprise/2.13/user/articles/about-labels", - "/enterprise/2.13/user/articles/about-labels": "/en/enterprise/2.13/user/articles/about-labels", - "/enterprise/2.13/articles/about-labels": "/en/enterprise/2.13/user/articles/about-labels", - "/en/enterprise/2.13/articles/about-merge-conflicts": "/en/enterprise/2.13/user/articles/about-merge-conflicts", - "/enterprise/2.13/user/articles/about-merge-conflicts": "/en/enterprise/2.13/user/articles/about-merge-conflicts", - "/enterprise/2.13/articles/about-merge-conflicts": "/en/enterprise/2.13/user/articles/about-merge-conflicts", - "/en/enterprise/2.13/articles/about-merge-methods-on-github": "/en/enterprise/2.13/user/articles/about-merge-methods-on-github", - "/enterprise/2.13/user/articles/about-merge-methods-on-github": "/en/enterprise/2.13/user/articles/about-merge-methods-on-github", - "/enterprise/2.13/articles/about-merge-methods-on-github": "/en/enterprise/2.13/user/articles/about-merge-methods-on-github", - "/en/enterprise/2.13/articles/about-milestones": "/en/enterprise/2.13/user/articles/about-milestones", - "/enterprise/2.13/user/articles/about-milestones": "/en/enterprise/2.13/user/articles/about-milestones", - "/enterprise/2.13/articles/about-milestones": "/en/enterprise/2.13/user/articles/about-milestones", - "/en/enterprise/2.13/articles/about-notifications": "/en/enterprise/2.13/user/articles/about-notifications", - "/enterprise/2.13/user/articles/about-notifications": "/en/enterprise/2.13/user/articles/about-notifications", - "/enterprise/2.13/articles/about-notifications": "/en/enterprise/2.13/user/articles/about-notifications", - "/en/enterprise/2.13/articles/about-organization-membership": "/en/enterprise/2.13/user/articles/about-organization-membership", - "/enterprise/2.13/user/articles/about-organization-membership": "/en/enterprise/2.13/user/articles/about-organization-membership", - "/enterprise/2.13/articles/about-organization-membership": "/en/enterprise/2.13/user/articles/about-organization-membership", - "/en/enterprise/2.13/articles/about-organizations": "/en/enterprise/2.13/user/articles/about-organizations", - "/enterprise/2.13/user/articles/about-organizations": "/en/enterprise/2.13/user/articles/about-organizations", - "/enterprise/2.13/articles/about-organizations": "/en/enterprise/2.13/user/articles/about-organizations", - "/en/enterprise/2.13/articles/about-project-boards": "/en/enterprise/2.13/user/articles/about-project-boards", - "/enterprise/2.13/user/articles/about-project-boards": "/en/enterprise/2.13/user/articles/about-project-boards", - "/enterprise/2.13/articles/about-project-boards": "/en/enterprise/2.13/user/articles/about-project-boards", - "/en/enterprise/2.13/articles/about-protected-branches": "/en/enterprise/2.13/user/articles/about-protected-branches", - "/enterprise/2.13/user/articles/about-protected-branches": "/en/enterprise/2.13/user/articles/about-protected-branches", - "/enterprise/2.13/articles/about-protected-branches": "/en/enterprise/2.13/user/articles/about-protected-branches", - "/en/enterprise/2.13/articles/about-pull-request-merges": "/en/enterprise/2.13/user/articles/about-pull-request-merges", - "/enterprise/2.13/user/articles/about-pull-request-merges": "/en/enterprise/2.13/user/articles/about-pull-request-merges", - "/enterprise/2.13/articles/about-pull-request-merges": "/en/enterprise/2.13/user/articles/about-pull-request-merges", - "/en/enterprise/2.13/articles/about-pull-request-reviews": "/en/enterprise/2.13/user/articles/about-pull-request-reviews", - "/enterprise/2.13/user/articles/about-pull-request-reviews": "/en/enterprise/2.13/user/articles/about-pull-request-reviews", - "/enterprise/2.13/articles/about-pull-request-reviews": "/en/enterprise/2.13/user/articles/about-pull-request-reviews", - "/en/enterprise/2.13/articles/about-pull-requests": "/en/enterprise/2.13/user/articles/about-pull-requests", - "/enterprise/2.13/user/articles/about-pull-requests": "/en/enterprise/2.13/user/articles/about-pull-requests", - "/enterprise/2.13/articles/about-pull-requests": "/en/enterprise/2.13/user/articles/about-pull-requests", - "/en/enterprise/2.13/articles/about-readmes": "/en/enterprise/2.13/user/articles/about-readmes", - "/enterprise/2.13/user/articles/about-readmes": "/en/enterprise/2.13/user/articles/about-readmes", - "/enterprise/2.13/articles/about-readmes": "/en/enterprise/2.13/user/articles/about-readmes", - "/en/enterprise/2.13/articles/about-releases": "/en/enterprise/2.13/user/articles/about-releases", - "/enterprise/2.13/user/articles/about-releases": "/en/enterprise/2.13/user/articles/about-releases", - "/enterprise/2.13/articles/about-releases": "/en/enterprise/2.13/user/articles/about-releases", - "/en/enterprise/2.13/articles/about-remote-repositories": "/en/enterprise/2.13/user/articles/about-remote-repositories", - "/enterprise/2.13/user/articles/about-remote-repositories": "/en/enterprise/2.13/user/articles/about-remote-repositories", - "/enterprise/2.13/articles/about-remote-repositories": "/en/enterprise/2.13/user/articles/about-remote-repositories", - "/en/enterprise/2.13/articles/about-repositories": "/en/enterprise/2.13/user/articles/about-repositories", - "/enterprise/2.13/user/articles/about-repositories": "/en/enterprise/2.13/user/articles/about-repositories", - "/enterprise/2.13/articles/about-repositories": "/en/enterprise/2.13/user/articles/about-repositories", - "/en/enterprise/2.13/articles/about-repository-graphs": "/en/enterprise/2.13/user/articles/about-repository-graphs", - "/enterprise/2.13/user/articles/about-repository-graphs": "/en/enterprise/2.13/user/articles/about-repository-graphs", - "/enterprise/2.13/articles/about-repository-graphs": "/en/enterprise/2.13/user/articles/about-repository-graphs", - "/en/enterprise/2.13/articles/about-repository-languages": "/en/enterprise/2.13/user/articles/about-repository-languages", - "/enterprise/2.13/user/articles/about-repository-languages": "/en/enterprise/2.13/user/articles/about-repository-languages", - "/enterprise/2.13/articles/about-repository-languages": "/en/enterprise/2.13/user/articles/about-repository-languages", - "/en/enterprise/2.13/articles/about-required-commit-signing": "/en/enterprise/2.13/user/articles/about-required-commit-signing", - "/enterprise/2.13/user/articles/about-required-commit-signing": "/en/enterprise/2.13/user/articles/about-required-commit-signing", - "/enterprise/2.13/articles/about-required-commit-signing": "/en/enterprise/2.13/user/articles/about-required-commit-signing", - "/en/enterprise/2.13/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.13/user/articles/about-required-reviews-for-pull-requests", - "/enterprise/2.13/user/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.13/user/articles/about-required-reviews-for-pull-requests", - "/enterprise/2.13/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.13/user/articles/about-required-reviews-for-pull-requests", - "/en/enterprise/2.13/articles/about-required-status-checks": "/en/enterprise/2.13/user/articles/about-required-status-checks", - "/enterprise/2.13/user/articles/about-required-status-checks": "/en/enterprise/2.13/user/articles/about-required-status-checks", - "/enterprise/2.13/articles/about-required-status-checks": "/en/enterprise/2.13/user/articles/about-required-status-checks", - "/en/enterprise/2.13/articles/about-saved-replies": "/en/enterprise/2.13/user/articles/about-saved-replies", - "/enterprise/2.13/user/articles/about-saved-replies": "/en/enterprise/2.13/user/articles/about-saved-replies", - "/enterprise/2.13/articles/about-saved-replies": "/en/enterprise/2.13/user/articles/about-saved-replies", - "/en/enterprise/2.13/articles/about-searching-on-github": "/en/enterprise/2.13/user/articles/about-searching-on-github", - "/enterprise/2.13/user/articles/about-searching-on-github": "/en/enterprise/2.13/user/articles/about-searching-on-github", - "/enterprise/2.13/articles/about-searching-on-github": "/en/enterprise/2.13/user/articles/about-searching-on-github", - "/en/enterprise/2.13/articles/about-ssh": "/en/enterprise/2.13/user/articles/about-ssh", - "/enterprise/2.13/user/articles/about-ssh": "/en/enterprise/2.13/user/articles/about-ssh", - "/enterprise/2.13/articles/about-ssh": "/en/enterprise/2.13/user/articles/about-ssh", - "/en/enterprise/2.13/articles/about-stars": "/en/enterprise/2.13/user/articles/about-stars", - "/enterprise/2.13/user/articles/about-stars": "/en/enterprise/2.13/user/articles/about-stars", - "/enterprise/2.13/articles/about-stars": "/en/enterprise/2.13/user/articles/about-stars", - "/en/enterprise/2.13/articles/about-status-checks": "/en/enterprise/2.13/user/articles/about-status-checks", - "/enterprise/2.13/user/articles/about-status-checks": "/en/enterprise/2.13/user/articles/about-status-checks", - "/enterprise/2.13/articles/about-status-checks": "/en/enterprise/2.13/user/articles/about-status-checks", - "/en/enterprise/2.13/articles/about-task-lists": "/en/enterprise/2.13/user/articles/about-task-lists", - "/enterprise/2.13/user/articles/about-task-lists": "/en/enterprise/2.13/user/articles/about-task-lists", - "/enterprise/2.13/articles/about-task-lists": "/en/enterprise/2.13/user/articles/about-task-lists", - "/en/enterprise/2.13/articles/about-team-discussions": "/en/enterprise/2.13/user/articles/about-team-discussions", - "/enterprise/2.13/user/articles/about-team-discussions": "/en/enterprise/2.13/user/articles/about-team-discussions", - "/enterprise/2.13/articles/about-team-discussions": "/en/enterprise/2.13/user/articles/about-team-discussions", - "/en/enterprise/2.13/articles/about-teams": "/en/enterprise/2.13/user/articles/about-teams", - "/enterprise/2.13/user/articles/about-teams": "/en/enterprise/2.13/user/articles/about-teams", - "/enterprise/2.13/articles/about-teams": "/en/enterprise/2.13/user/articles/about-teams", - "/en/enterprise/2.13/articles/about-topics": "/en/enterprise/2.13/user/articles/about-topics", - "/enterprise/2.13/user/articles/about-topics": "/en/enterprise/2.13/user/articles/about-topics", - "/enterprise/2.13/articles/about-topics": "/en/enterprise/2.13/user/articles/about-topics", - "/en/enterprise/2.13/articles/about-two-factor-authentication": "/en/enterprise/2.13/user/articles/about-two-factor-authentication", - "/enterprise/2.13/user/articles/about-two-factor-authentication": "/en/enterprise/2.13/user/articles/about-two-factor-authentication", - "/enterprise/2.13/articles/about-two-factor-authentication": "/en/enterprise/2.13/user/articles/about-two-factor-authentication", - "/en/enterprise/2.13/articles/about-web-notifications": "/en/enterprise/2.13/user/articles/about-web-notifications", - "/enterprise/2.13/user/articles/about-web-notifications": "/en/enterprise/2.13/user/articles/about-web-notifications", - "/enterprise/2.13/articles/about-web-notifications": "/en/enterprise/2.13/user/articles/about-web-notifications", - "/en/enterprise/2.13/articles/about-webhooks": "/en/enterprise/2.13/user/articles/about-webhooks", - "/enterprise/2.13/user/articles/about-webhooks": "/en/enterprise/2.13/user/articles/about-webhooks", - "/enterprise/2.13/articles/about-webhooks": "/en/enterprise/2.13/user/articles/about-webhooks", - "/en/enterprise/2.13/articles/about-wikis": "/en/enterprise/2.13/user/articles/about-wikis", - "/enterprise/2.13/user/articles/about-wikis": "/en/enterprise/2.13/user/articles/about-wikis", - "/enterprise/2.13/articles/about-wikis": "/en/enterprise/2.13/user/articles/about-wikis", - "/en/enterprise/2.13/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.13/user/articles/about-writing-and-formatting-on-github", - "/enterprise/2.13/user/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.13/user/articles/about-writing-and-formatting-on-github", - "/enterprise/2.13/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.13/user/articles/about-writing-and-formatting-on-github", - "/en/enterprise/2.13/articles/about-your-organizations-news-feed": "/en/enterprise/2.13/user/articles/about-your-organizations-news-feed", - "/enterprise/2.13/user/articles/about-your-organizations-news-feed": "/en/enterprise/2.13/user/articles/about-your-organizations-news-feed", - "/enterprise/2.13/articles/about-your-organizations-news-feed": "/en/enterprise/2.13/user/articles/about-your-organizations-news-feed", - "/en/enterprise/2.13/articles/about-your-organizations-profile": "/en/enterprise/2.13/user/articles/about-your-organizations-profile", - "/enterprise/2.13/user/articles/about-your-organizations-profile": "/en/enterprise/2.13/user/articles/about-your-organizations-profile", - "/enterprise/2.13/articles/about-your-organizations-profile": "/en/enterprise/2.13/user/articles/about-your-organizations-profile", - "/en/enterprise/2.13/articles/about-your-profile": "/en/enterprise/2.13/user/articles/about-your-profile", - "/enterprise/2.13/user/articles/about-your-profile": "/en/enterprise/2.13/user/articles/about-your-profile", - "/enterprise/2.13/articles/about-your-profile": "/en/enterprise/2.13/user/articles/about-your-profile", - "/en/enterprise/2.13/articles/access-permissions-on-github": "/en/enterprise/2.13/user/articles/access-permissions-on-github", - "/enterprise/2.13/user/articles/access-permissions-on-github": "/en/enterprise/2.13/user/articles/access-permissions-on-github", - "/enterprise/2.13/articles/access-permissions-on-github": "/en/enterprise/2.13/user/articles/access-permissions-on-github", - "/en/enterprise/2.13/articles/accessing-an-organization": "/en/enterprise/2.13/user/articles/accessing-an-organization", - "/enterprise/2.13/user/articles/accessing-an-organization": "/en/enterprise/2.13/user/articles/accessing-an-organization", - "/enterprise/2.13/articles/accessing-an-organization": "/en/enterprise/2.13/user/articles/accessing-an-organization", - "/en/enterprise/2.13/articles/accessing-basic-repository-data": "/en/enterprise/2.13/user/articles/accessing-basic-repository-data", - "/enterprise/2.13/user/articles/accessing-basic-repository-data": "/en/enterprise/2.13/user/articles/accessing-basic-repository-data", - "/enterprise/2.13/articles/accessing-basic-repository-data": "/en/enterprise/2.13/user/articles/accessing-basic-repository-data", - "/en/enterprise/2.13/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.13/user/articles/accessing-github-using-two-factor-authentication", - "/enterprise/2.13/user/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.13/user/articles/accessing-github-using-two-factor-authentication", - "/enterprise/2.13/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.13/user/articles/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.13/articles/accessing-your-notifications": "/en/enterprise/2.13/user/articles/accessing-your-notifications", - "/enterprise/2.13/user/articles/accessing-your-notifications": "/en/enterprise/2.13/user/articles/accessing-your-notifications", - "/enterprise/2.13/articles/accessing-your-notifications": "/en/enterprise/2.13/user/articles/accessing-your-notifications", - "/en/enterprise/2.13/articles/accessing-your-organizations-settings": "/en/enterprise/2.13/user/articles/accessing-your-organizations-settings", - "/enterprise/2.13/user/articles/accessing-your-organizations-settings": "/en/enterprise/2.13/user/articles/accessing-your-organizations-settings", - "/enterprise/2.13/articles/accessing-your-organizations-settings": "/en/enterprise/2.13/user/articles/accessing-your-organizations-settings", - "/en/enterprise/2.13/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.13/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.13/user/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.13/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.13/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.13/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.13/articles/adding-a-file-to-a-repository": "/en/enterprise/2.13/user/articles/adding-a-file-to-a-repository", - "/enterprise/2.13/user/articles/adding-a-file-to-a-repository": "/en/enterprise/2.13/user/articles/adding-a-file-to-a-repository", - "/enterprise/2.13/articles/adding-a-file-to-a-repository": "/en/enterprise/2.13/user/articles/adding-a-file-to-a-repository", - "/en/enterprise/2.13/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/en/enterprise/2.13/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/enterprise/2.13/user/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/en/enterprise/2.13/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/enterprise/2.13/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/en/enterprise/2.13/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/en/enterprise/2.13/articles/adding-a-license-to-a-repository": "/en/enterprise/2.13/user/articles/adding-a-license-to-a-repository", - "/enterprise/2.13/user/articles/adding-a-license-to-a-repository": "/en/enterprise/2.13/user/articles/adding-a-license-to-a-repository", - "/enterprise/2.13/articles/adding-a-license-to-a-repository": "/en/enterprise/2.13/user/articles/adding-a-license-to-a-repository", - "/en/enterprise/2.13/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.13/user/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.13/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.13/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.13/user/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.13/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.13/articles/adding-a-remote": "/en/enterprise/2.13/user/articles/adding-a-remote", - "/enterprise/2.13/user/articles/adding-a-remote": "/en/enterprise/2.13/user/articles/adding-a-remote", - "/enterprise/2.13/articles/adding-a-remote": "/en/enterprise/2.13/user/articles/adding-a-remote", - "/en/enterprise/2.13/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-an-email-address-to-your-github-account", - "/enterprise/2.13/user/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-an-email-address-to-your-github-account", - "/enterprise/2.13/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.13/user/articles/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.13/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.13/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.13/user/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.13/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.13/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.13/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.13/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.13/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.13/user/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.13/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.13/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.13/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.13/articles/adding-jekyll-plugins-to-a-github-pages-site": "/en/enterprise/2.13/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/enterprise/2.13/user/articles/adding-jekyll-plugins-to-a-github-pages-site": "/en/enterprise/2.13/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/enterprise/2.13/articles/adding-jekyll-plugins-to-a-github-pages-site": "/en/enterprise/2.13/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/en/enterprise/2.13/articles/adding-notes-to-a-project-board": "/en/enterprise/2.13/user/articles/adding-notes-to-a-project-board", - "/enterprise/2.13/user/articles/adding-notes-to-a-project-board": "/en/enterprise/2.13/user/articles/adding-notes-to-a-project-board", - "/enterprise/2.13/articles/adding-notes-to-a-project-board": "/en/enterprise/2.13/user/articles/adding-notes-to-a-project-board", - "/en/enterprise/2.13/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.13/user/articles/adding-or-editing-wiki-pages", - "/enterprise/2.13/user/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.13/user/articles/adding-or-editing-wiki-pages", - "/enterprise/2.13/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.13/user/articles/adding-or-editing-wiki-pages", - "/en/enterprise/2.13/articles/adding-organization-members-to-a-team": "/en/enterprise/2.13/user/articles/adding-organization-members-to-a-team", - "/enterprise/2.13/user/articles/adding-organization-members-to-a-team": "/en/enterprise/2.13/user/articles/adding-organization-members-to-a-team", - "/enterprise/2.13/articles/adding-organization-members-to-a-team": "/en/enterprise/2.13/user/articles/adding-organization-members-to-a-team", - "/en/enterprise/2.13/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.13/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.13/user/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.13/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.13/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.13/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.13/articles/adding-people-to-your-organization": "/en/enterprise/2.13/user/articles/adding-people-to-your-organization", - "/enterprise/2.13/user/articles/adding-people-to-your-organization": "/en/enterprise/2.13/user/articles/adding-people-to-your-organization", - "/enterprise/2.13/articles/adding-people-to-your-organization": "/en/enterprise/2.13/user/articles/adding-people-to-your-organization", - "/en/enterprise/2.13/articles/adding-support-resources-to-your-project": "/en/enterprise/2.13/user/articles/adding-support-resources-to-your-project", - "/enterprise/2.13/user/articles/adding-support-resources-to-your-project": "/en/enterprise/2.13/user/articles/adding-support-resources-to-your-project", - "/enterprise/2.13/articles/adding-support-resources-to-your-project": "/en/enterprise/2.13/user/articles/adding-support-resources-to-your-project", - "/en/enterprise/2.13/articles/additional-customizations-for-github-pages": "/en/enterprise/2.13/user/articles/additional-customizations-for-github-pages", - "/enterprise/2.13/user/articles/additional-customizations-for-github-pages": "/en/enterprise/2.13/user/articles/additional-customizations-for-github-pages", - "/enterprise/2.13/articles/additional-customizations-for-github-pages": "/en/enterprise/2.13/user/articles/additional-customizations-for-github-pages", - "/en/enterprise/2.13/articles/addressing-merge-conflicts": "/en/enterprise/2.13/user/articles/addressing-merge-conflicts", - "/enterprise/2.13/user/articles/addressing-merge-conflicts": "/en/enterprise/2.13/user/articles/addressing-merge-conflicts", - "/enterprise/2.13/articles/addressing-merge-conflicts": "/en/enterprise/2.13/user/articles/addressing-merge-conflicts", - "/en/enterprise/2.13/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.13/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.13/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.13/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.13/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.13/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.13/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.13/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.13/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.13/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.13/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.13/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/en/enterprise/2.13/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.13/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.13/user/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.13/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.13/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.13/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/en/enterprise/2.13/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.13/user/articles/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.13/user/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.13/user/articles/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.13/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.13/user/articles/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.13/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.13/user/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.13/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.13/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.13/user/articles/approving-a-pull-request-with-required-reviews", - "/enterprise/2.13/user/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.13/user/articles/approving-a-pull-request-with-required-reviews", - "/enterprise/2.13/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.13/user/articles/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.13/articles/archiving-a-github-repository": "/en/enterprise/2.13/user/articles/archiving-a-github-repository", - "/enterprise/2.13/user/articles/archiving-a-github-repository": "/en/enterprise/2.13/user/articles/archiving-a-github-repository", - "/enterprise/2.13/articles/archiving-a-github-repository": "/en/enterprise/2.13/user/articles/archiving-a-github-repository", - "/en/enterprise/2.13/articles/archiving-repositories": "/en/enterprise/2.13/user/articles/archiving-repositories", - "/enterprise/2.13/user/articles/archiving-repositories": "/en/enterprise/2.13/user/articles/archiving-repositories", - "/enterprise/2.13/articles/archiving-repositories": "/en/enterprise/2.13/user/articles/archiving-repositories", - "/en/enterprise/2.13/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.13/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.13/user/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.13/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.13/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.13/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.13/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.13/user/articles/associating-an-email-with-your-gpg-key", - "/enterprise/2.13/user/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.13/user/articles/associating-an-email-with-your-gpg-key", - "/enterprise/2.13/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.13/user/articles/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.13/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.13/user/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.13/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.13/articles/associating-text-editors-with-git": "/en/enterprise/2.13/user/articles/associating-text-editors-with-git", - "/enterprise/2.13/user/articles/associating-text-editors-with-git": "/en/enterprise/2.13/user/articles/associating-text-editors-with-git", - "/enterprise/2.13/articles/associating-text-editors-with-git": "/en/enterprise/2.13/user/articles/associating-text-editors-with-git", - "/en/enterprise/2.13/articles/authorizing-oauth-apps": "/en/enterprise/2.13/user/articles/authorizing-oauth-apps", - "/enterprise/2.13/user/articles/authorizing-oauth-apps": "/en/enterprise/2.13/user/articles/authorizing-oauth-apps", - "/enterprise/2.13/articles/authorizing-oauth-apps": "/en/enterprise/2.13/user/articles/authorizing-oauth-apps", - "/en/enterprise/2.13/articles/autolinked-references-and-urls": "/en/enterprise/2.13/user/articles/autolinked-references-and-urls", - "/enterprise/2.13/user/articles/autolinked-references-and-urls": "/en/enterprise/2.13/user/articles/autolinked-references-and-urls", - "/enterprise/2.13/articles/autolinked-references-and-urls": "/en/enterprise/2.13/user/articles/autolinked-references-and-urls", - "/en/enterprise/2.13/articles/backing-up-a-repository": "/en/enterprise/2.13/user/articles/backing-up-a-repository", - "/enterprise/2.13/user/articles/backing-up-a-repository": "/en/enterprise/2.13/user/articles/backing-up-a-repository", - "/enterprise/2.13/articles/backing-up-a-repository": "/en/enterprise/2.13/user/articles/backing-up-a-repository", - "/en/enterprise/2.13/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.13/user/articles/basic-writing-and-formatting-syntax", - "/enterprise/2.13/user/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.13/user/articles/basic-writing-and-formatting-syntax", - "/enterprise/2.13/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.13/user/articles/basic-writing-and-formatting-syntax", - "/en/enterprise/2.13/articles/be-social": "/en/enterprise/2.13/user/articles/be-social", - "/enterprise/2.13/user/articles/be-social": "/en/enterprise/2.13/user/articles/be-social", - "/enterprise/2.13/articles/be-social": "/en/enterprise/2.13/user/articles/be-social", - "/en/enterprise/2.13/articles/caching-your-github-password-in-git": "/en/enterprise/2.13/user/articles/caching-your-github-password-in-git", - "/enterprise/2.13/user/articles/caching-your-github-password-in-git": "/en/enterprise/2.13/user/articles/caching-your-github-password-in-git", - "/enterprise/2.13/articles/caching-your-github-password-in-git": "/en/enterprise/2.13/user/articles/caching-your-github-password-in-git", - "/en/enterprise/2.13/articles/changing-a-commit-message": "/en/enterprise/2.13/user/articles/changing-a-commit-message", - "/enterprise/2.13/user/articles/changing-a-commit-message": "/en/enterprise/2.13/user/articles/changing-a-commit-message", - "/enterprise/2.13/articles/changing-a-commit-message": "/en/enterprise/2.13/user/articles/changing-a-commit-message", - "/en/enterprise/2.13/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.13/user/articles/changing-a-persons-role-to-owner", - "/enterprise/2.13/user/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.13/user/articles/changing-a-persons-role-to-owner", - "/enterprise/2.13/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.13/user/articles/changing-a-persons-role-to-owner", - "/en/enterprise/2.13/articles/changing-a-remotes-url": "/en/enterprise/2.13/user/articles/changing-a-remotes-url", - "/enterprise/2.13/user/articles/changing-a-remotes-url": "/en/enterprise/2.13/user/articles/changing-a-remotes-url", - "/enterprise/2.13/articles/changing-a-remotes-url": "/en/enterprise/2.13/user/articles/changing-a-remotes-url", - "/en/enterprise/2.13/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.13/user/articles/changing-access-permissions-for-wikis", - "/enterprise/2.13/user/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.13/user/articles/changing-access-permissions-for-wikis", - "/enterprise/2.13/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.13/user/articles/changing-access-permissions-for-wikis", - "/en/enterprise/2.13/articles/changing-author-info": "/en/enterprise/2.13/user/articles/changing-author-info", - "/enterprise/2.13/user/articles/changing-author-info": "/en/enterprise/2.13/user/articles/changing-author-info", - "/enterprise/2.13/articles/changing-author-info": "/en/enterprise/2.13/user/articles/changing-author-info", - "/en/enterprise/2.13/articles/changing-team-visibility": "/en/enterprise/2.13/user/articles/changing-team-visibility", - "/enterprise/2.13/user/articles/changing-team-visibility": "/en/enterprise/2.13/user/articles/changing-team-visibility", - "/enterprise/2.13/articles/changing-team-visibility": "/en/enterprise/2.13/user/articles/changing-team-visibility", - "/en/enterprise/2.13/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.13/user/articles/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.13/user/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.13/user/articles/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.13/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.13/user/articles/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.13/articles/changing-your-github-username": "/en/enterprise/2.13/user/articles/changing-your-github-username", - "/enterprise/2.13/user/articles/changing-your-github-username": "/en/enterprise/2.13/user/articles/changing-your-github-username", - "/enterprise/2.13/articles/changing-your-github-username": "/en/enterprise/2.13/user/articles/changing-your-github-username", - "/en/enterprise/2.13/articles/changing-your-primary-email-address": "/en/enterprise/2.13/user/articles/changing-your-primary-email-address", - "/enterprise/2.13/user/articles/changing-your-primary-email-address": "/en/enterprise/2.13/user/articles/changing-your-primary-email-address", - "/enterprise/2.13/articles/changing-your-primary-email-address": "/en/enterprise/2.13/user/articles/changing-your-primary-email-address", - "/en/enterprise/2.13/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.13/user/articles/checking-for-existing-gpg-keys", - "/enterprise/2.13/user/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.13/user/articles/checking-for-existing-gpg-keys", - "/enterprise/2.13/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.13/user/articles/checking-for-existing-gpg-keys", - "/en/enterprise/2.13/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.13/user/articles/checking-for-existing-ssh-keys", - "/enterprise/2.13/user/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.13/user/articles/checking-for-existing-ssh-keys", - "/enterprise/2.13/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.13/user/articles/checking-for-existing-ssh-keys", - "/en/enterprise/2.13/articles/checking-out-pull-requests-locally": "/en/enterprise/2.13/user/articles/checking-out-pull-requests-locally", - "/enterprise/2.13/user/articles/checking-out-pull-requests-locally": "/en/enterprise/2.13/user/articles/checking-out-pull-requests-locally", - "/enterprise/2.13/articles/checking-out-pull-requests-locally": "/en/enterprise/2.13/user/articles/checking-out-pull-requests-locally", - "/en/enterprise/2.13/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.13/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.13/user/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.13/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.13/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.13/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.13/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.13/user/articles/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.13/user/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.13/user/articles/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.13/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.13/user/articles/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.13/articles/classifying-your-repository-with-topics": "/en/enterprise/2.13/user/articles/classifying-your-repository-with-topics", - "/enterprise/2.13/user/articles/classifying-your-repository-with-topics": "/en/enterprise/2.13/user/articles/classifying-your-repository-with-topics", - "/enterprise/2.13/articles/classifying-your-repository-with-topics": "/en/enterprise/2.13/user/articles/classifying-your-repository-with-topics", - "/en/enterprise/2.13/articles/cloning-a-repository-from-github": "/en/enterprise/2.13/user/articles/cloning-a-repository-from-github", - "/enterprise/2.13/user/articles/cloning-a-repository-from-github": "/en/enterprise/2.13/user/articles/cloning-a-repository-from-github", - "/enterprise/2.13/articles/cloning-a-repository-from-github": "/en/enterprise/2.13/user/articles/cloning-a-repository-from-github", - "/en/enterprise/2.13/articles/cloning-a-repository": "/en/enterprise/2.13/user/articles/cloning-a-repository", - "/enterprise/2.13/user/articles/cloning-a-repository": "/en/enterprise/2.13/user/articles/cloning-a-repository", - "/enterprise/2.13/articles/cloning-a-repository": "/en/enterprise/2.13/user/articles/cloning-a-repository", - "/en/enterprise/2.13/articles/closing-a-project-board": "/en/enterprise/2.13/user/articles/closing-a-project-board", - "/enterprise/2.13/user/articles/closing-a-project-board": "/en/enterprise/2.13/user/articles/closing-a-project-board", - "/enterprise/2.13/articles/closing-a-project-board": "/en/enterprise/2.13/user/articles/closing-a-project-board", - "/en/enterprise/2.13/articles/closing-a-pull-request": "/en/enterprise/2.13/user/articles/closing-a-pull-request", - "/enterprise/2.13/user/articles/closing-a-pull-request": "/en/enterprise/2.13/user/articles/closing-a-pull-request", - "/enterprise/2.13/articles/closing-a-pull-request": "/en/enterprise/2.13/user/articles/closing-a-pull-request", - "/en/enterprise/2.13/articles/closing-issues-using-keywords": "/en/enterprise/2.13/user/articles/closing-issues-using-keywords", - "/enterprise/2.13/user/articles/closing-issues-using-keywords": "/en/enterprise/2.13/user/articles/closing-issues-using-keywords", - "/enterprise/2.13/articles/closing-issues-using-keywords": "/en/enterprise/2.13/user/articles/closing-issues-using-keywords", - "/en/enterprise/2.13/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/en/enterprise/2.13/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/enterprise/2.13/user/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/en/enterprise/2.13/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/enterprise/2.13/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/en/enterprise/2.13/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/en/enterprise/2.13/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.13/user/articles/collaborating-with-groups-in-organizations", - "/enterprise/2.13/user/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.13/user/articles/collaborating-with-groups-in-organizations", - "/enterprise/2.13/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.13/user/articles/collaborating-with-groups-in-organizations", - "/en/enterprise/2.13/articles/collaborating-with-your-team": "/en/enterprise/2.13/user/articles/collaborating-with-your-team", - "/enterprise/2.13/user/articles/collaborating-with-your-team": "/en/enterprise/2.13/user/articles/collaborating-with-your-team", - "/enterprise/2.13/articles/collaborating-with-your-team": "/en/enterprise/2.13/user/articles/collaborating-with-your-team", - "/en/enterprise/2.13/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.13/user/articles/collaboration-with-git-large-file-storage", - "/enterprise/2.13/user/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.13/user/articles/collaboration-with-git-large-file-storage", - "/enterprise/2.13/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.13/user/articles/collaboration-with-git-large-file-storage", - "/en/enterprise/2.13/articles/commenting-on-a-pull-request": "/en/enterprise/2.13/user/articles/commenting-on-a-pull-request", - "/enterprise/2.13/user/articles/commenting-on-a-pull-request": "/en/enterprise/2.13/user/articles/commenting-on-a-pull-request", - "/enterprise/2.13/articles/commenting-on-a-pull-request": "/en/enterprise/2.13/user/articles/commenting-on-a-pull-request", - "/en/enterprise/2.13/articles/commit-branch-and-tag-labels": "/en/enterprise/2.13/user/articles/commit-branch-and-tag-labels", - "/enterprise/2.13/user/articles/commit-branch-and-tag-labels": "/en/enterprise/2.13/user/articles/commit-branch-and-tag-labels", - "/enterprise/2.13/articles/commit-branch-and-tag-labels": "/en/enterprise/2.13/user/articles/commit-branch-and-tag-labels", - "/en/enterprise/2.13/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.13/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.13/user/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.13/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.13/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.13/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.13/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.13/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.13/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.13/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.13/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.13/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.13/articles/comparing-commits-across-time": "/en/enterprise/2.13/user/articles/comparing-commits-across-time", - "/enterprise/2.13/user/articles/comparing-commits-across-time": "/en/enterprise/2.13/user/articles/comparing-commits-across-time", - "/enterprise/2.13/articles/comparing-commits-across-time": "/en/enterprise/2.13/user/articles/comparing-commits-across-time", - "/en/enterprise/2.13/articles/conditions-for-large-files": "/en/enterprise/2.13/user/articles/conditions-for-large-files", - "/enterprise/2.13/user/articles/conditions-for-large-files": "/en/enterprise/2.13/user/articles/conditions-for-large-files", - "/enterprise/2.13/articles/conditions-for-large-files": "/en/enterprise/2.13/user/articles/conditions-for-large-files", - "/en/enterprise/2.13/articles/configuring-a-publishing-source-for-github-pages": "/en/enterprise/2.13/user/articles/configuring-a-publishing-source-for-github-pages", - "/enterprise/2.13/user/articles/configuring-a-publishing-source-for-github-pages": "/en/enterprise/2.13/user/articles/configuring-a-publishing-source-for-github-pages", - "/enterprise/2.13/articles/configuring-a-publishing-source-for-github-pages": "/en/enterprise/2.13/user/articles/configuring-a-publishing-source-for-github-pages", - "/en/enterprise/2.13/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.13/user/articles/configuring-a-remote-for-a-fork", - "/enterprise/2.13/user/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.13/user/articles/configuring-a-remote-for-a-fork", - "/enterprise/2.13/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.13/user/articles/configuring-a-remote-for-a-fork", - "/en/enterprise/2.13/articles/configuring-automation-for-project-boards": "/en/enterprise/2.13/user/articles/configuring-automation-for-project-boards", - "/enterprise/2.13/user/articles/configuring-automation-for-project-boards": "/en/enterprise/2.13/user/articles/configuring-automation-for-project-boards", - "/enterprise/2.13/articles/configuring-automation-for-project-boards": "/en/enterprise/2.13/user/articles/configuring-automation-for-project-boards", - "/en/enterprise/2.13/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.13/user/articles/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.13/user/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.13/user/articles/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.13/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.13/user/articles/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.13/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.13/user/articles/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.13/user/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.13/user/articles/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.13/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.13/user/articles/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.13/articles/configuring-git-large-file-storage": "/en/enterprise/2.13/user/articles/configuring-git-large-file-storage", - "/enterprise/2.13/user/articles/configuring-git-large-file-storage": "/en/enterprise/2.13/user/articles/configuring-git-large-file-storage", - "/enterprise/2.13/articles/configuring-git-large-file-storage": "/en/enterprise/2.13/user/articles/configuring-git-large-file-storage", - "/en/enterprise/2.13/articles/configuring-jekyll-plugins": "/en/enterprise/2.13/user/articles/configuring-jekyll-plugins", - "/enterprise/2.13/user/articles/configuring-jekyll-plugins": "/en/enterprise/2.13/user/articles/configuring-jekyll-plugins", - "/enterprise/2.13/articles/configuring-jekyll-plugins": "/en/enterprise/2.13/user/articles/configuring-jekyll-plugins", - "/en/enterprise/2.13/articles/configuring-jekyll": "/en/enterprise/2.13/user/articles/configuring-jekyll", - "/enterprise/2.13/user/articles/configuring-jekyll": "/en/enterprise/2.13/user/articles/configuring-jekyll", - "/enterprise/2.13/articles/configuring-jekyll": "/en/enterprise/2.13/user/articles/configuring-jekyll", - "/en/enterprise/2.13/articles/configuring-protected-branches": "/en/enterprise/2.13/user/articles/configuring-protected-branches", - "/enterprise/2.13/user/articles/configuring-protected-branches": "/en/enterprise/2.13/user/articles/configuring-protected-branches", - "/enterprise/2.13/articles/configuring-protected-branches": "/en/enterprise/2.13/user/articles/configuring-protected-branches", - "/en/enterprise/2.13/articles/configuring-pull-request-merges": "/en/enterprise/2.13/user/articles/configuring-pull-request-merges", - "/enterprise/2.13/user/articles/configuring-pull-request-merges": "/en/enterprise/2.13/user/articles/configuring-pull-request-merges", - "/enterprise/2.13/articles/configuring-pull-request-merges": "/en/enterprise/2.13/user/articles/configuring-pull-request-merges", - "/en/enterprise/2.13/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.13/user/articles/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.13/user/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.13/user/articles/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.13/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.13/user/articles/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.13/articles/configuring-two-factor-authentication": "/en/enterprise/2.13/user/articles/configuring-two-factor-authentication", - "/enterprise/2.13/user/articles/configuring-two-factor-authentication": "/en/enterprise/2.13/user/articles/configuring-two-factor-authentication", - "/enterprise/2.13/articles/configuring-two-factor-authentication": "/en/enterprise/2.13/user/articles/configuring-two-factor-authentication", - "/en/enterprise/2.13/articles/connecting-to-github-with-ssh": "/en/enterprise/2.13/user/articles/connecting-to-github-with-ssh", - "/enterprise/2.13/user/articles/connecting-to-github-with-ssh": "/en/enterprise/2.13/user/articles/connecting-to-github-with-ssh", - "/enterprise/2.13/articles/connecting-to-github-with-ssh": "/en/enterprise/2.13/user/articles/connecting-to-github-with-ssh", - "/en/enterprise/2.13/articles/connecting-with-third-party-applications": "/en/enterprise/2.13/user/articles/connecting-with-third-party-applications", - "/enterprise/2.13/user/articles/connecting-with-third-party-applications": "/en/enterprise/2.13/user/articles/connecting-with-third-party-applications", - "/enterprise/2.13/articles/connecting-with-third-party-applications": "/en/enterprise/2.13/user/articles/connecting-with-third-party-applications", - "/en/enterprise/2.13/articles/converting-a-user-into-an-organization": "/en/enterprise/2.13/user/articles/converting-a-user-into-an-organization", - "/enterprise/2.13/user/articles/converting-a-user-into-an-organization": "/en/enterprise/2.13/user/articles/converting-a-user-into-an-organization", - "/enterprise/2.13/articles/converting-a-user-into-an-organization": "/en/enterprise/2.13/user/articles/converting-a-user-into-an-organization", - "/en/enterprise/2.13/articles/converting-an-organization-into-a-user": "/en/enterprise/2.13/user/articles/converting-an-organization-into-a-user", - "/enterprise/2.13/user/articles/converting-an-organization-into-a-user": "/en/enterprise/2.13/user/articles/converting-an-organization-into-a-user", - "/enterprise/2.13/articles/converting-an-organization-into-a-user": "/en/enterprise/2.13/user/articles/converting-an-organization-into-a-user", - "/en/enterprise/2.13/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.13/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.13/user/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.13/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.13/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.13/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.13/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.13/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.13/user/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.13/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.13/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.13/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.13/articles/create-a-repo": "/en/enterprise/2.13/user/articles/create-a-repo", - "/enterprise/2.13/user/articles/create-a-repo": "/en/enterprise/2.13/user/articles/create-a-repo", - "/enterprise/2.13/articles/create-a-repo": "/en/enterprise/2.13/user/articles/create-a-repo", - "/en/enterprise/2.13/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.13/user/articles/creating-a-commit-with-multiple-authors", - "/enterprise/2.13/user/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.13/user/articles/creating-a-commit-with-multiple-authors", - "/enterprise/2.13/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.13/user/articles/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.13/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.13/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.13/user/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.13/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.13/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.13/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.13/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.13/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.13/user/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.13/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.13/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.13/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.13/articles/creating-a-label": "/en/enterprise/2.13/user/articles/creating-a-label", - "/enterprise/2.13/user/articles/creating-a-label": "/en/enterprise/2.13/user/articles/creating-a-label", - "/enterprise/2.13/articles/creating-a-label": "/en/enterprise/2.13/user/articles/creating-a-label", - "/en/enterprise/2.13/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.13/user/articles/creating-a-new-organization-from-scratch", - "/enterprise/2.13/user/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.13/user/articles/creating-a-new-organization-from-scratch", - "/enterprise/2.13/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.13/user/articles/creating-a-new-organization-from-scratch", - "/en/enterprise/2.13/articles/creating-a-new-repository": "/en/enterprise/2.13/user/articles/creating-a-new-repository", - "/enterprise/2.13/user/articles/creating-a-new-repository": "/en/enterprise/2.13/user/articles/creating-a-new-repository", - "/enterprise/2.13/articles/creating-a-new-repository": "/en/enterprise/2.13/user/articles/creating-a-new-repository", - "/en/enterprise/2.13/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.13/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.13/user/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.13/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.13/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.13/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.13/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.13/user/articles/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.13/user/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.13/user/articles/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.13/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.13/user/articles/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.13/articles/creating-a-project-board": "/en/enterprise/2.13/user/articles/creating-a-project-board", - "/enterprise/2.13/user/articles/creating-a-project-board": "/en/enterprise/2.13/user/articles/creating-a-project-board", - "/enterprise/2.13/articles/creating-a-project-board": "/en/enterprise/2.13/user/articles/creating-a-project-board", - "/en/enterprise/2.13/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.13/user/articles/creating-a-pull-request-from-a-fork", - "/enterprise/2.13/user/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.13/user/articles/creating-a-pull-request-from-a-fork", - "/enterprise/2.13/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.13/user/articles/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.13/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.13/user/articles/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.13/user/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.13/user/articles/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.13/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.13/user/articles/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.13/articles/creating-a-pull-request": "/en/enterprise/2.13/user/articles/creating-a-pull-request", - "/enterprise/2.13/user/articles/creating-a-pull-request": "/en/enterprise/2.13/user/articles/creating-a-pull-request", - "/enterprise/2.13/articles/creating-a-pull-request": "/en/enterprise/2.13/user/articles/creating-a-pull-request", - "/en/enterprise/2.13/articles/creating-a-repository-on-github": "/en/enterprise/2.13/user/articles/creating-a-repository-on-github", - "/enterprise/2.13/user/articles/creating-a-repository-on-github": "/en/enterprise/2.13/user/articles/creating-a-repository-on-github", - "/enterprise/2.13/articles/creating-a-repository-on-github": "/en/enterprise/2.13/user/articles/creating-a-repository-on-github", - "/en/enterprise/2.13/articles/creating-a-saved-reply": "/en/enterprise/2.13/user/articles/creating-a-saved-reply", - "/enterprise/2.13/user/articles/creating-a-saved-reply": "/en/enterprise/2.13/user/articles/creating-a-saved-reply", - "/enterprise/2.13/articles/creating-a-saved-reply": "/en/enterprise/2.13/user/articles/creating-a-saved-reply", - "/en/enterprise/2.13/articles/creating-a-strong-password": "/en/enterprise/2.13/user/articles/creating-a-strong-password", - "/enterprise/2.13/user/articles/creating-a-strong-password": "/en/enterprise/2.13/user/articles/creating-a-strong-password", - "/enterprise/2.13/articles/creating-a-strong-password": "/en/enterprise/2.13/user/articles/creating-a-strong-password", - "/en/enterprise/2.13/articles/creating-a-team-discussion": "/en/enterprise/2.13/user/articles/creating-a-team-discussion", - "/enterprise/2.13/user/articles/creating-a-team-discussion": "/en/enterprise/2.13/user/articles/creating-a-team-discussion", - "/enterprise/2.13/articles/creating-a-team-discussion": "/en/enterprise/2.13/user/articles/creating-a-team-discussion", - "/en/enterprise/2.13/articles/creating-a-team": "/en/enterprise/2.13/user/articles/creating-a-team", - "/enterprise/2.13/user/articles/creating-a-team": "/en/enterprise/2.13/user/articles/creating-a-team", - "/enterprise/2.13/articles/creating-a-team": "/en/enterprise/2.13/user/articles/creating-a-team", - "/en/enterprise/2.13/articles/creating-an-issue": "/en/enterprise/2.13/user/articles/creating-an-issue", - "/enterprise/2.13/user/articles/creating-an-issue": "/en/enterprise/2.13/user/articles/creating-an-issue", - "/enterprise/2.13/articles/creating-an-issue": "/en/enterprise/2.13/user/articles/creating-an-issue", - "/en/enterprise/2.13/articles/creating-an-issues-only-repository": "/en/enterprise/2.13/user/articles/creating-an-issues-only-repository", - "/enterprise/2.13/user/articles/creating-an-issues-only-repository": "/en/enterprise/2.13/user/articles/creating-an-issues-only-repository", - "/enterprise/2.13/articles/creating-an-issues-only-repository": "/en/enterprise/2.13/user/articles/creating-an-issues-only-repository", - "/en/enterprise/2.13/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.13/user/articles/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.13/user/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.13/user/articles/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.13/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.13/user/articles/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.13/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.13/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.13/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.13/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.13/user/articles/creating-and-highlighting-code-blocks", - "/enterprise/2.13/user/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.13/user/articles/creating-and-highlighting-code-blocks", - "/enterprise/2.13/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.13/user/articles/creating-and-highlighting-code-blocks", - "/en/enterprise/2.13/articles/creating-gists": "/en/enterprise/2.13/user/articles/creating-gists", - "/enterprise/2.13/user/articles/creating-gists": "/en/enterprise/2.13/user/articles/creating-gists", - "/enterprise/2.13/articles/creating-gists": "/en/enterprise/2.13/user/articles/creating-gists", - "/en/enterprise/2.13/articles/creating-new-files": "/en/enterprise/2.13/user/articles/creating-new-files", - "/enterprise/2.13/user/articles/creating-new-files": "/en/enterprise/2.13/user/articles/creating-new-files", - "/enterprise/2.13/articles/creating-new-files": "/en/enterprise/2.13/user/articles/creating-new-files", - "/en/enterprise/2.13/articles/creating-pages-with-the-automatic-generator": "/en/enterprise/2.13/user/articles/creating-pages-with-the-automatic-generator", - "/enterprise/2.13/user/articles/creating-pages-with-the-automatic-generator": "/en/enterprise/2.13/user/articles/creating-pages-with-the-automatic-generator", - "/enterprise/2.13/articles/creating-pages-with-the-automatic-generator": "/en/enterprise/2.13/user/articles/creating-pages-with-the-automatic-generator", - "/en/enterprise/2.13/articles/creating-project-pages-using-the-command-line": "/en/enterprise/2.13/user/articles/creating-project-pages-using-the-command-line", - "/enterprise/2.13/user/articles/creating-project-pages-using-the-command-line": "/en/enterprise/2.13/user/articles/creating-project-pages-using-the-command-line", - "/enterprise/2.13/articles/creating-project-pages-using-the-command-line": "/en/enterprise/2.13/user/articles/creating-project-pages-using-the-command-line", - "/en/enterprise/2.13/articles/creating-releases": "/en/enterprise/2.13/user/articles/creating-releases", - "/enterprise/2.13/user/articles/creating-releases": "/en/enterprise/2.13/user/articles/creating-releases", - "/enterprise/2.13/articles/creating-releases": "/en/enterprise/2.13/user/articles/creating-releases", - "/en/enterprise/2.13/articles/customizing-css-and-html-in-your-jekyll-theme": "/en/enterprise/2.13/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/enterprise/2.13/user/articles/customizing-css-and-html-in-your-jekyll-theme": "/en/enterprise/2.13/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/enterprise/2.13/articles/customizing-css-and-html-in-your-jekyll-theme": "/en/enterprise/2.13/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/en/enterprise/2.13/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.13/user/articles/customizing-how-changed-files-appear-on-github", - "/enterprise/2.13/user/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.13/user/articles/customizing-how-changed-files-appear-on-github", - "/enterprise/2.13/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.13/user/articles/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.13/articles/customizing-your-profile": "/en/enterprise/2.13/user/articles/customizing-your-profile", - "/enterprise/2.13/user/articles/customizing-your-profile": "/en/enterprise/2.13/user/articles/customizing-your-profile", - "/enterprise/2.13/articles/customizing-your-profile": "/en/enterprise/2.13/user/articles/customizing-your-profile", - "/en/enterprise/2.13/articles/dealing-with-line-endings": "/en/enterprise/2.13/user/articles/dealing-with-line-endings", - "/enterprise/2.13/user/articles/dealing-with-line-endings": "/en/enterprise/2.13/user/articles/dealing-with-line-endings", - "/enterprise/2.13/articles/dealing-with-line-endings": "/en/enterprise/2.13/user/articles/dealing-with-line-endings", - "/en/enterprise/2.13/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.13/user/articles/dealing-with-non-fast-forward-errors", - "/enterprise/2.13/user/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.13/user/articles/dealing-with-non-fast-forward-errors", - "/enterprise/2.13/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.13/user/articles/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.13/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.13/user/articles/defining-the-mergeability-of-pull-requests", - "/enterprise/2.13/user/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.13/user/articles/defining-the-mergeability-of-pull-requests", - "/enterprise/2.13/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.13/user/articles/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.13/articles/deleting-a-label": "/en/enterprise/2.13/user/articles/deleting-a-label", - "/enterprise/2.13/user/articles/deleting-a-label": "/en/enterprise/2.13/user/articles/deleting-a-label", - "/enterprise/2.13/articles/deleting-a-label": "/en/enterprise/2.13/user/articles/deleting-a-label", - "/en/enterprise/2.13/articles/deleting-a-project-board": "/en/enterprise/2.13/user/articles/deleting-a-project-board", - "/enterprise/2.13/user/articles/deleting-a-project-board": "/en/enterprise/2.13/user/articles/deleting-a-project-board", - "/enterprise/2.13/articles/deleting-a-project-board": "/en/enterprise/2.13/user/articles/deleting-a-project-board", - "/en/enterprise/2.13/articles/deleting-a-repository": "/en/enterprise/2.13/user/articles/deleting-a-repository", - "/enterprise/2.13/user/articles/deleting-a-repository": "/en/enterprise/2.13/user/articles/deleting-a-repository", - "/enterprise/2.13/articles/deleting-a-repository": "/en/enterprise/2.13/user/articles/deleting-a-repository", - "/en/enterprise/2.13/articles/deleting-a-saved-reply": "/en/enterprise/2.13/user/articles/deleting-a-saved-reply", - "/enterprise/2.13/user/articles/deleting-a-saved-reply": "/en/enterprise/2.13/user/articles/deleting-a-saved-reply", - "/enterprise/2.13/articles/deleting-a-saved-reply": "/en/enterprise/2.13/user/articles/deleting-a-saved-reply", - "/en/enterprise/2.13/articles/deleting-a-team": "/en/enterprise/2.13/user/articles/deleting-a-team", - "/enterprise/2.13/user/articles/deleting-a-team": "/en/enterprise/2.13/user/articles/deleting-a-team", - "/enterprise/2.13/articles/deleting-a-team": "/en/enterprise/2.13/user/articles/deleting-a-team", - "/en/enterprise/2.13/articles/deleting-an-organization-account": "/en/enterprise/2.13/user/articles/deleting-an-organization-account", - "/enterprise/2.13/user/articles/deleting-an-organization-account": "/en/enterprise/2.13/user/articles/deleting-an-organization-account", - "/enterprise/2.13/articles/deleting-an-organization-account": "/en/enterprise/2.13/user/articles/deleting-an-organization-account", - "/en/enterprise/2.13/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.13/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.13/user/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.13/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.13/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.13/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.13/articles/deleting-files": "/en/enterprise/2.13/user/articles/deleting-files", - "/enterprise/2.13/user/articles/deleting-files": "/en/enterprise/2.13/user/articles/deleting-files", - "/enterprise/2.13/articles/deleting-files": "/en/enterprise/2.13/user/articles/deleting-files", - "/en/enterprise/2.13/articles/deleting-your-user-account": "/en/enterprise/2.13/user/articles/deleting-your-user-account", - "/enterprise/2.13/user/articles/deleting-your-user-account": "/en/enterprise/2.13/user/articles/deleting-your-user-account", - "/enterprise/2.13/articles/deleting-your-user-account": "/en/enterprise/2.13/user/articles/deleting-your-user-account", - "/en/enterprise/2.13/articles/differences-between-commit-views": "/en/enterprise/2.13/user/articles/differences-between-commit-views", - "/enterprise/2.13/user/articles/differences-between-commit-views": "/en/enterprise/2.13/user/articles/differences-between-commit-views", - "/enterprise/2.13/articles/differences-between-commit-views": "/en/enterprise/2.13/user/articles/differences-between-commit-views", - "/en/enterprise/2.13/articles/differences-between-user-and-organization-accounts": "/en/enterprise/2.13/user/articles/differences-between-user-and-organization-accounts", - "/enterprise/2.13/user/articles/differences-between-user-and-organization-accounts": "/en/enterprise/2.13/user/articles/differences-between-user-and-organization-accounts", - "/enterprise/2.13/articles/differences-between-user-and-organization-accounts": "/en/enterprise/2.13/user/articles/differences-between-user-and-organization-accounts", - "/en/enterprise/2.13/articles/disabling-issues": "/en/enterprise/2.13/user/articles/disabling-issues", - "/enterprise/2.13/user/articles/disabling-issues": "/en/enterprise/2.13/user/articles/disabling-issues", - "/enterprise/2.13/articles/disabling-issues": "/en/enterprise/2.13/user/articles/disabling-issues", - "/en/enterprise/2.13/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.13/user/articles/disabling-project-boards-in-a-repository", - "/enterprise/2.13/user/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.13/user/articles/disabling-project-boards-in-a-repository", - "/enterprise/2.13/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.13/user/articles/disabling-project-boards-in-a-repository", - "/en/enterprise/2.13/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.13/user/articles/disabling-project-boards-in-your-organization", - "/enterprise/2.13/user/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.13/user/articles/disabling-project-boards-in-your-organization", - "/enterprise/2.13/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.13/user/articles/disabling-project-boards-in-your-organization", - "/en/enterprise/2.13/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.13/user/articles/disabling-team-discussions-for-your-organization", - "/enterprise/2.13/user/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.13/user/articles/disabling-team-discussions-for-your-organization", - "/enterprise/2.13/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.13/user/articles/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.13/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.13/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.13/user/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.13/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.13/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.13/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.13/articles/disabling-wikis": "/en/enterprise/2.13/user/articles/disabling-wikis", - "/enterprise/2.13/user/articles/disabling-wikis": "/en/enterprise/2.13/user/articles/disabling-wikis", - "/enterprise/2.13/articles/disabling-wikis": "/en/enterprise/2.13/user/articles/disabling-wikis", - "/en/enterprise/2.13/articles/dismissing-a-pull-request-review": "/en/enterprise/2.13/user/articles/dismissing-a-pull-request-review", - "/enterprise/2.13/user/articles/dismissing-a-pull-request-review": "/en/enterprise/2.13/user/articles/dismissing-a-pull-request-review", - "/enterprise/2.13/articles/dismissing-a-pull-request-review": "/en/enterprise/2.13/user/articles/dismissing-a-pull-request-review", - "/en/enterprise/2.13/articles/distributing-large-binaries": "/en/enterprise/2.13/user/articles/distributing-large-binaries", - "/enterprise/2.13/user/articles/distributing-large-binaries": "/en/enterprise/2.13/user/articles/distributing-large-binaries", - "/enterprise/2.13/articles/distributing-large-binaries": "/en/enterprise/2.13/user/articles/distributing-large-binaries", - "/en/enterprise/2.13/articles/documenting-your-project-with-wikis": "/en/enterprise/2.13/user/articles/documenting-your-project-with-wikis", - "/enterprise/2.13/user/articles/documenting-your-project-with-wikis": "/en/enterprise/2.13/user/articles/documenting-your-project-with-wikis", - "/enterprise/2.13/articles/documenting-your-project-with-wikis": "/en/enterprise/2.13/user/articles/documenting-your-project-with-wikis", - "/en/enterprise/2.13/articles/duplicating-a-repository": "/en/enterprise/2.13/user/articles/duplicating-a-repository", - "/enterprise/2.13/user/articles/duplicating-a-repository": "/en/enterprise/2.13/user/articles/duplicating-a-repository", - "/enterprise/2.13/articles/duplicating-a-repository": "/en/enterprise/2.13/user/articles/duplicating-a-repository", - "/en/enterprise/2.13/articles/editing-a-label": "/en/enterprise/2.13/user/articles/editing-a-label", - "/enterprise/2.13/user/articles/editing-a-label": "/en/enterprise/2.13/user/articles/editing-a-label", - "/enterprise/2.13/articles/editing-a-label": "/en/enterprise/2.13/user/articles/editing-a-label", - "/en/enterprise/2.13/articles/editing-a-project-board": "/en/enterprise/2.13/user/articles/editing-a-project-board", - "/enterprise/2.13/user/articles/editing-a-project-board": "/en/enterprise/2.13/user/articles/editing-a-project-board", - "/enterprise/2.13/articles/editing-a-project-board": "/en/enterprise/2.13/user/articles/editing-a-project-board", - "/en/enterprise/2.13/articles/editing-a-saved-reply": "/en/enterprise/2.13/user/articles/editing-a-saved-reply", - "/enterprise/2.13/user/articles/editing-a-saved-reply": "/en/enterprise/2.13/user/articles/editing-a-saved-reply", - "/enterprise/2.13/articles/editing-a-saved-reply": "/en/enterprise/2.13/user/articles/editing-a-saved-reply", - "/en/enterprise/2.13/articles/editing-and-deleting-releases": "/en/enterprise/2.13/user/articles/editing-and-deleting-releases", - "/enterprise/2.13/user/articles/editing-and-deleting-releases": "/en/enterprise/2.13/user/articles/editing-and-deleting-releases", - "/enterprise/2.13/articles/editing-and-deleting-releases": "/en/enterprise/2.13/user/articles/editing-and-deleting-releases", - "/en/enterprise/2.13/articles/editing-files-in-another-users-repository": "/en/enterprise/2.13/user/articles/editing-files-in-another-users-repository", - "/enterprise/2.13/user/articles/editing-files-in-another-users-repository": "/en/enterprise/2.13/user/articles/editing-files-in-another-users-repository", - "/enterprise/2.13/articles/editing-files-in-another-users-repository": "/en/enterprise/2.13/user/articles/editing-files-in-another-users-repository", - "/en/enterprise/2.13/articles/editing-files-in-your-repository": "/en/enterprise/2.13/user/articles/editing-files-in-your-repository", - "/enterprise/2.13/user/articles/editing-files-in-your-repository": "/en/enterprise/2.13/user/articles/editing-files-in-your-repository", - "/enterprise/2.13/articles/editing-files-in-your-repository": "/en/enterprise/2.13/user/articles/editing-files-in-your-repository", - "/en/enterprise/2.13/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.13/user/articles/editing-or-deleting-a-team-discussion", - "/enterprise/2.13/user/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.13/user/articles/editing-or-deleting-a-team-discussion", - "/enterprise/2.13/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.13/user/articles/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.13/articles/editing-wiki-content": "/en/enterprise/2.13/user/articles/editing-wiki-content", - "/enterprise/2.13/user/articles/editing-wiki-content": "/en/enterprise/2.13/user/articles/editing-wiki-content", - "/enterprise/2.13/articles/editing-wiki-content": "/en/enterprise/2.13/user/articles/editing-wiki-content", - "/en/enterprise/2.13/articles/emoji-on-github-pages": "/en/enterprise/2.13/user/articles/emoji-on-github-pages", - "/enterprise/2.13/user/articles/emoji-on-github-pages": "/en/enterprise/2.13/user/articles/emoji-on-github-pages", - "/enterprise/2.13/articles/emoji-on-github-pages": "/en/enterprise/2.13/user/articles/emoji-on-github-pages", - "/en/enterprise/2.13/articles/enabling-branch-restrictions": "/en/enterprise/2.13/user/articles/enabling-branch-restrictions", - "/enterprise/2.13/user/articles/enabling-branch-restrictions": "/en/enterprise/2.13/user/articles/enabling-branch-restrictions", - "/enterprise/2.13/articles/enabling-branch-restrictions": "/en/enterprise/2.13/user/articles/enabling-branch-restrictions", - "/en/enterprise/2.13/articles/enabling-required-commit-signing": "/en/enterprise/2.13/user/articles/enabling-required-commit-signing", - "/enterprise/2.13/user/articles/enabling-required-commit-signing": "/en/enterprise/2.13/user/articles/enabling-required-commit-signing", - "/enterprise/2.13/articles/enabling-required-commit-signing": "/en/enterprise/2.13/user/articles/enabling-required-commit-signing", - "/en/enterprise/2.13/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.13/user/articles/enabling-required-reviews-for-pull-requests", - "/enterprise/2.13/user/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.13/user/articles/enabling-required-reviews-for-pull-requests", - "/enterprise/2.13/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.13/user/articles/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.13/articles/enabling-required-status-checks": "/en/enterprise/2.13/user/articles/enabling-required-status-checks", - "/enterprise/2.13/user/articles/enabling-required-status-checks": "/en/enterprise/2.13/user/articles/enabling-required-status-checks", - "/enterprise/2.13/articles/enabling-required-status-checks": "/en/enterprise/2.13/user/articles/enabling-required-status-checks", - "/en/enterprise/2.13/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.13/user/articles/error-agent-admitted-failure-to-sign", - "/enterprise/2.13/user/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.13/user/articles/error-agent-admitted-failure-to-sign", - "/enterprise/2.13/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.13/user/articles/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.13/articles/error-bad-file-number": "/en/enterprise/2.13/user/articles/error-bad-file-number", - "/enterprise/2.13/user/articles/error-bad-file-number": "/en/enterprise/2.13/user/articles/error-bad-file-number", - "/enterprise/2.13/articles/error-bad-file-number": "/en/enterprise/2.13/user/articles/error-bad-file-number", - "/en/enterprise/2.13/articles/error-key-already-in-use": "/en/enterprise/2.13/user/articles/error-key-already-in-use", - "/enterprise/2.13/user/articles/error-key-already-in-use": "/en/enterprise/2.13/user/articles/error-key-already-in-use", - "/enterprise/2.13/articles/error-key-already-in-use": "/en/enterprise/2.13/user/articles/error-key-already-in-use", - "/en/enterprise/2.13/articles/error-permission-denied-publickey": "/en/enterprise/2.13/user/articles/error-permission-denied-publickey", - "/enterprise/2.13/user/articles/error-permission-denied-publickey": "/en/enterprise/2.13/user/articles/error-permission-denied-publickey", - "/enterprise/2.13/articles/error-permission-denied-publickey": "/en/enterprise/2.13/user/articles/error-permission-denied-publickey", - "/en/enterprise/2.13/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.13/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.13/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.13/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.13/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.13/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.13/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.13/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.13/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.13/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.13/articles/error-repository-not-found": "/en/enterprise/2.13/user/articles/error-repository-not-found", - "/enterprise/2.13/user/articles/error-repository-not-found": "/en/enterprise/2.13/user/articles/error-repository-not-found", - "/enterprise/2.13/articles/error-repository-not-found": "/en/enterprise/2.13/user/articles/error-repository-not-found", - "/en/enterprise/2.13/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.13/user/articles/error-ssh-add-illegal-option----k", - "/enterprise/2.13/user/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.13/user/articles/error-ssh-add-illegal-option----k", - "/enterprise/2.13/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.13/user/articles/error-ssh-add-illegal-option----k", - "/en/enterprise/2.13/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.13/user/articles/error-were-doing-an-ssh-key-audit", - "/enterprise/2.13/user/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.13/user/articles/error-were-doing-an-ssh-key-audit", - "/enterprise/2.13/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.13/user/articles/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.13/articles/fetching-a-remote": "/en/enterprise/2.13/user/articles/fetching-a-remote", - "/enterprise/2.13/user/articles/fetching-a-remote": "/en/enterprise/2.13/user/articles/fetching-a-remote", - "/enterprise/2.13/articles/fetching-a-remote": "/en/enterprise/2.13/user/articles/fetching-a-remote", - "/en/enterprise/2.13/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.13/user/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.13/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.13/articles/files-that-start-with-an-underscore-are-missing": "/en/enterprise/2.13/user/articles/files-that-start-with-an-underscore-are-missing", - "/enterprise/2.13/user/articles/files-that-start-with-an-underscore-are-missing": "/en/enterprise/2.13/user/articles/files-that-start-with-an-underscore-are-missing", - "/enterprise/2.13/articles/files-that-start-with-an-underscore-are-missing": "/en/enterprise/2.13/user/articles/files-that-start-with-an-underscore-are-missing", - "/en/enterprise/2.13/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.13/user/articles/filtering-cards-on-a-project-board", - "/enterprise/2.13/user/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.13/user/articles/filtering-cards-on-a-project-board", - "/enterprise/2.13/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.13/user/articles/filtering-cards-on-a-project-board", - "/en/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.13/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests", - "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests", - "/enterprise/2.13/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/filtering-issues-and-pull-requests", - "/en/enterprise/2.13/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.13/user/articles/filtering-pull-requests-by-review-status", - "/enterprise/2.13/user/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.13/user/articles/filtering-pull-requests-by-review-status", - "/enterprise/2.13/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.13/user/articles/filtering-pull-requests-by-review-status", - "/en/enterprise/2.13/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.13/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.13/user/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.13/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.13/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.13/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.13/articles/finding-files-on-github": "/en/enterprise/2.13/user/articles/finding-files-on-github", - "/enterprise/2.13/user/articles/finding-files-on-github": "/en/enterprise/2.13/user/articles/finding-files-on-github", - "/enterprise/2.13/articles/finding-files-on-github": "/en/enterprise/2.13/user/articles/finding-files-on-github", - "/en/enterprise/2.13/articles/finding-information-in-a-repository": "/en/enterprise/2.13/user/articles/finding-information-in-a-repository", - "/enterprise/2.13/user/articles/finding-information-in-a-repository": "/en/enterprise/2.13/user/articles/finding-information-in-a-repository", - "/enterprise/2.13/articles/finding-information-in-a-repository": "/en/enterprise/2.13/user/articles/finding-information-in-a-repository", - "/en/enterprise/2.13/articles/following-people": "/en/enterprise/2.13/user/articles/following-people", - "/enterprise/2.13/user/articles/following-people": "/en/enterprise/2.13/user/articles/following-people", - "/enterprise/2.13/articles/following-people": "/en/enterprise/2.13/user/articles/following-people", - "/en/enterprise/2.13/articles/fork-a-repo": "/en/enterprise/2.13/user/articles/fork-a-repo", - "/enterprise/2.13/user/articles/fork-a-repo": "/en/enterprise/2.13/user/articles/fork-a-repo", - "/enterprise/2.13/articles/fork-a-repo": "/en/enterprise/2.13/user/articles/fork-a-repo", - "/en/enterprise/2.13/articles/forking-and-cloning-gists": "/en/enterprise/2.13/user/articles/forking-and-cloning-gists", - "/enterprise/2.13/user/articles/forking-and-cloning-gists": "/en/enterprise/2.13/user/articles/forking-and-cloning-gists", - "/enterprise/2.13/articles/forking-and-cloning-gists": "/en/enterprise/2.13/user/articles/forking-and-cloning-gists", - "/en/enterprise/2.13/articles/further-reading-on-github-pages": "/en/enterprise/2.13/user/articles/further-reading-on-github-pages", - "/enterprise/2.13/user/articles/further-reading-on-github-pages": "/en/enterprise/2.13/user/articles/further-reading-on-github-pages", - "/enterprise/2.13/articles/further-reading-on-github-pages": "/en/enterprise/2.13/user/articles/further-reading-on-github-pages", - "/en/enterprise/2.13/articles/generating-a-new-gpg-key": "/en/enterprise/2.13/user/articles/generating-a-new-gpg-key", - "/enterprise/2.13/user/articles/generating-a-new-gpg-key": "/en/enterprise/2.13/user/articles/generating-a-new-gpg-key", - "/enterprise/2.13/articles/generating-a-new-gpg-key": "/en/enterprise/2.13/user/articles/generating-a-new-gpg-key", - "/en/enterprise/2.13/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.13/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.13/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.13/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.13/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.13/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.13/articles/generic-jekyll-build-failures": "/en/enterprise/2.13/user/articles/generic-jekyll-build-failures", - "/enterprise/2.13/user/articles/generic-jekyll-build-failures": "/en/enterprise/2.13/user/articles/generic-jekyll-build-failures", - "/enterprise/2.13/articles/generic-jekyll-build-failures": "/en/enterprise/2.13/user/articles/generic-jekyll-build-failures", - "/en/enterprise/2.13/articles/getting-permanent-links-to-files": "/en/enterprise/2.13/user/articles/getting-permanent-links-to-files", - "/enterprise/2.13/user/articles/getting-permanent-links-to-files": "/en/enterprise/2.13/user/articles/getting-permanent-links-to-files", - "/enterprise/2.13/articles/getting-permanent-links-to-files": "/en/enterprise/2.13/user/articles/getting-permanent-links-to-files", - "/en/enterprise/2.13/articles/getting-started-with-notifications": "/en/enterprise/2.13/user/articles/getting-started-with-notifications", - "/enterprise/2.13/user/articles/getting-started-with-notifications": "/en/enterprise/2.13/user/articles/getting-started-with-notifications", - "/enterprise/2.13/articles/getting-started-with-notifications": "/en/enterprise/2.13/user/articles/getting-started-with-notifications", - "/en/enterprise/2.13/articles/getting-started-with-searching-on-github": "/en/enterprise/2.13/user/articles/getting-started-with-searching-on-github", - "/enterprise/2.13/user/articles/getting-started-with-searching-on-github": "/en/enterprise/2.13/user/articles/getting-started-with-searching-on-github", - "/enterprise/2.13/articles/getting-started-with-searching-on-github": "/en/enterprise/2.13/user/articles/getting-started-with-searching-on-github", - "/en/enterprise/2.13/articles/getting-started-with-the-api": "/en/enterprise/2.13/user/articles/getting-started-with-the-api", - "/enterprise/2.13/user/articles/getting-started-with-the-api": "/en/enterprise/2.13/user/articles/getting-started-with-the-api", - "/enterprise/2.13/articles/getting-started-with-the-api": "/en/enterprise/2.13/user/articles/getting-started-with-the-api", - "/en/enterprise/2.13/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.13/user/articles/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.13/user/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.13/user/articles/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.13/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.13/user/articles/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.13/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.13/user/articles/getting-the-download-count-for-your-releases", - "/enterprise/2.13/user/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.13/user/articles/getting-the-download-count-for-your-releases", - "/enterprise/2.13/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.13/user/articles/getting-the-download-count-for-your-releases", - "/en/enterprise/2.13/articles/git-and-github-learning-resources": "/en/enterprise/2.13/user/articles/git-and-github-learning-resources", - "/enterprise/2.13/user/articles/git-and-github-learning-resources": "/en/enterprise/2.13/user/articles/git-and-github-learning-resources", - "/enterprise/2.13/articles/git-and-github-learning-resources": "/en/enterprise/2.13/user/articles/git-and-github-learning-resources", - "/en/enterprise/2.13/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.13/user/articles/git-automation-with-oauth-tokens", - "/enterprise/2.13/user/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.13/user/articles/git-automation-with-oauth-tokens", - "/enterprise/2.13/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.13/user/articles/git-automation-with-oauth-tokens", - "/en/enterprise/2.13/articles/git-cheatsheet": "/en/enterprise/2.13/user/articles/git-cheatsheet", - "/enterprise/2.13/user/articles/git-cheatsheet": "/en/enterprise/2.13/user/articles/git-cheatsheet", - "/enterprise/2.13/articles/git-cheatsheet": "/en/enterprise/2.13/user/articles/git-cheatsheet", - "/en/enterprise/2.13/articles/github-flow": "/en/enterprise/2.13/user/articles/github-flow", - "/enterprise/2.13/user/articles/github-flow": "/en/enterprise/2.13/user/articles/github-flow", - "/enterprise/2.13/articles/github-flow": "/en/enterprise/2.13/user/articles/github-flow", - "/en/enterprise/2.13/articles/github-glossary": "/en/enterprise/2.13/user/articles/github-glossary", - "/enterprise/2.13/user/articles/github-glossary": "/en/enterprise/2.13/user/articles/github-glossary", - "/enterprise/2.13/articles/github-glossary": "/en/enterprise/2.13/user/articles/github-glossary", - "/en/enterprise/2.13/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.13/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.13/user/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.13/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.13/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.13/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.13/articles/https-cloning-errors": "/en/enterprise/2.13/user/articles/https-cloning-errors", - "/enterprise/2.13/user/articles/https-cloning-errors": "/en/enterprise/2.13/user/articles/https-cloning-errors", - "/enterprise/2.13/articles/https-cloning-errors": "/en/enterprise/2.13/user/articles/https-cloning-errors", - "/en/enterprise/2.13/articles/ignoring-files": "/en/enterprise/2.13/user/articles/ignoring-files", - "/enterprise/2.13/user/articles/ignoring-files": "/en/enterprise/2.13/user/articles/ignoring-files", - "/enterprise/2.13/articles/ignoring-files": "/en/enterprise/2.13/user/articles/ignoring-files", - "/en/enterprise/2.13/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.13/user/articles/importing-a-git-repository-using-the-command-line", - "/enterprise/2.13/user/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.13/user/articles/importing-a-git-repository-using-the-command-line", - "/enterprise/2.13/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.13/user/articles/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.13/articles/importing-source-code-to-github": "/en/enterprise/2.13/user/articles/importing-source-code-to-github", - "/enterprise/2.13/user/articles/importing-source-code-to-github": "/en/enterprise/2.13/user/articles/importing-source-code-to-github", - "/enterprise/2.13/articles/importing-source-code-to-github": "/en/enterprise/2.13/user/articles/importing-source-code-to-github", - "/en/enterprise/2.13/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.13/user/articles/incorporating-changes-from-a-pull-request", - "/enterprise/2.13/user/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.13/user/articles/incorporating-changes-from-a-pull-request", - "/enterprise/2.13/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.13/user/articles/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.13/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.13/user/articles/initializing-an-empty-repository-with-a-readme", - "/enterprise/2.13/user/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.13/user/articles/initializing-an-empty-repository-with-a-readme", - "/enterprise/2.13/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.13/user/articles/initializing-an-empty-repository-with-a-readme", - "/en/enterprise/2.13/articles/installing-git-large-file-storage": "/en/enterprise/2.13/user/articles/installing-git-large-file-storage", - "/enterprise/2.13/user/articles/installing-git-large-file-storage": "/en/enterprise/2.13/user/articles/installing-git-large-file-storage", - "/enterprise/2.13/articles/installing-git-large-file-storage": "/en/enterprise/2.13/user/articles/installing-git-large-file-storage", - "/en/enterprise/2.13/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.13/user/articles/integrating-jira-with-your-organization-project-board", - "/enterprise/2.13/user/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.13/user/articles/integrating-jira-with-your-organization-project-board", - "/enterprise/2.13/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.13/user/articles/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.13/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.13/user/articles/integrating-jira-with-your-personal-projects", - "/enterprise/2.13/user/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.13/user/articles/integrating-jira-with-your-personal-projects", - "/enterprise/2.13/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.13/user/articles/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.13/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.13/user/articles/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.13/user/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.13/user/articles/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.13/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.13/user/articles/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.13/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.13/user/articles/keeping-your-account-and-data-secure", - "/enterprise/2.13/user/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.13/user/articles/keeping-your-account-and-data-secure", - "/enterprise/2.13/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.13/user/articles/keeping-your-account-and-data-secure", - "/en/enterprise/2.13/articles/keeping-your-organization-secure": "/en/enterprise/2.13/user/articles/keeping-your-organization-secure", - "/enterprise/2.13/user/articles/keeping-your-organization-secure": "/en/enterprise/2.13/user/articles/keeping-your-organization-secure", - "/enterprise/2.13/articles/keeping-your-organization-secure": "/en/enterprise/2.13/user/articles/keeping-your-organization-secure", - "/en/enterprise/2.13/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/labeling-issues-and-pull-requests", - "/enterprise/2.13/user/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/labeling-issues-and-pull-requests", - "/enterprise/2.13/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/labeling-issues-and-pull-requests", - "/en/enterprise/2.13/articles/licensing-a-repository": "/en/enterprise/2.13/user/articles/licensing-a-repository", - "/enterprise/2.13/user/articles/licensing-a-repository": "/en/enterprise/2.13/user/articles/licensing-a-repository", - "/enterprise/2.13/articles/licensing-a-repository": "/en/enterprise/2.13/user/articles/licensing-a-repository", - "/en/enterprise/2.13/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.13/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.13/user/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.13/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.13/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.13/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.13/articles/linking-to-releases": "/en/enterprise/2.13/user/articles/linking-to-releases", - "/enterprise/2.13/user/articles/linking-to-releases": "/en/enterprise/2.13/user/articles/linking-to-releases", - "/enterprise/2.13/articles/linking-to-releases": "/en/enterprise/2.13/user/articles/linking-to-releases", - "/en/enterprise/2.13/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.13/user/articles/listing-the-forks-of-a-repository", - "/enterprise/2.13/user/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.13/user/articles/listing-the-forks-of-a-repository", - "/enterprise/2.13/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.13/user/articles/listing-the-forks-of-a-repository", - "/en/enterprise/2.13/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.13/user/articles/listing-the-repositories-youre-watching", - "/enterprise/2.13/user/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.13/user/articles/listing-the-repositories-youre-watching", - "/enterprise/2.13/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.13/user/articles/listing-the-repositories-youre-watching", - "/en/enterprise/2.13/articles/locking-conversations": "/en/enterprise/2.13/user/articles/locking-conversations", - "/enterprise/2.13/user/articles/locking-conversations": "/en/enterprise/2.13/user/articles/locking-conversations", - "/enterprise/2.13/articles/locking-conversations": "/en/enterprise/2.13/user/articles/locking-conversations", - "/en/enterprise/2.13/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.13/user/articles/managing-access-to-your-organizations-repositories", - "/enterprise/2.13/user/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.13/user/articles/managing-access-to-your-organizations-repositories", - "/enterprise/2.13/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.13/user/articles/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.13/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.13/user/articles/managing-access-to-your-personal-repositories", - "/enterprise/2.13/user/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.13/user/articles/managing-access-to-your-personal-repositories", - "/enterprise/2.13/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.13/user/articles/managing-access-to-your-personal-repositories", - "/en/enterprise/2.13/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.13/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.13/user/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.13/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.13/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.13/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.13/articles/managing-branches-in-your-repository": "/en/enterprise/2.13/user/articles/managing-branches-in-your-repository", - "/enterprise/2.13/user/articles/managing-branches-in-your-repository": "/en/enterprise/2.13/user/articles/managing-branches-in-your-repository", - "/enterprise/2.13/articles/managing-branches-in-your-repository": "/en/enterprise/2.13/user/articles/managing-branches-in-your-repository", - "/en/enterprise/2.13/articles/managing-commit-signature-verification": "/en/enterprise/2.13/user/articles/managing-commit-signature-verification", - "/enterprise/2.13/user/articles/managing-commit-signature-verification": "/en/enterprise/2.13/user/articles/managing-commit-signature-verification", - "/enterprise/2.13/articles/managing-commit-signature-verification": "/en/enterprise/2.13/user/articles/managing-commit-signature-verification", - "/en/enterprise/2.13/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.13/user/articles/managing-contribution-graphs-on-your-profile", - "/enterprise/2.13/user/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.13/user/articles/managing-contribution-graphs-on-your-profile", - "/enterprise/2.13/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.13/user/articles/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.13/articles/managing-disruptive-comments": "/en/enterprise/2.13/user/articles/managing-disruptive-comments", - "/enterprise/2.13/user/articles/managing-disruptive-comments": "/en/enterprise/2.13/user/articles/managing-disruptive-comments", - "/enterprise/2.13/articles/managing-disruptive-comments": "/en/enterprise/2.13/user/articles/managing-disruptive-comments", - "/en/enterprise/2.13/articles/managing-email-preferences": "/en/enterprise/2.13/user/articles/managing-email-preferences", - "/enterprise/2.13/user/articles/managing-email-preferences": "/en/enterprise/2.13/user/articles/managing-email-preferences", - "/enterprise/2.13/articles/managing-email-preferences": "/en/enterprise/2.13/user/articles/managing-email-preferences", - "/en/enterprise/2.13/articles/managing-files-on-github": "/en/enterprise/2.13/user/articles/managing-files-on-github", - "/enterprise/2.13/user/articles/managing-files-on-github": "/en/enterprise/2.13/user/articles/managing-files-on-github", - "/enterprise/2.13/articles/managing-files-on-github": "/en/enterprise/2.13/user/articles/managing-files-on-github", - "/en/enterprise/2.13/articles/managing-files-using-the-command-line": "/en/enterprise/2.13/user/articles/managing-files-using-the-command-line", - "/enterprise/2.13/user/articles/managing-files-using-the-command-line": "/en/enterprise/2.13/user/articles/managing-files-using-the-command-line", - "/enterprise/2.13/articles/managing-files-using-the-command-line": "/en/enterprise/2.13/user/articles/managing-files-using-the-command-line", - "/en/enterprise/2.13/articles/managing-membership-in-your-organization": "/en/enterprise/2.13/user/articles/managing-membership-in-your-organization", - "/enterprise/2.13/user/articles/managing-membership-in-your-organization": "/en/enterprise/2.13/user/articles/managing-membership-in-your-organization", - "/enterprise/2.13/articles/managing-membership-in-your-organization": "/en/enterprise/2.13/user/articles/managing-membership-in-your-organization", - "/en/enterprise/2.13/articles/managing-organization-settings": "/en/enterprise/2.13/user/articles/managing-organization-settings", - "/enterprise/2.13/user/articles/managing-organization-settings": "/en/enterprise/2.13/user/articles/managing-organization-settings", - "/enterprise/2.13/articles/managing-organization-settings": "/en/enterprise/2.13/user/articles/managing-organization-settings", - "/en/enterprise/2.13/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.13/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.13/user/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.13/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.13/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.13/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.13/articles/managing-project-boards": "/en/enterprise/2.13/user/articles/managing-project-boards", - "/enterprise/2.13/user/articles/managing-project-boards": "/en/enterprise/2.13/user/articles/managing-project-boards", - "/enterprise/2.13/articles/managing-project-boards": "/en/enterprise/2.13/user/articles/managing-project-boards", - "/en/enterprise/2.13/articles/managing-repository-settings": "/en/enterprise/2.13/user/articles/managing-repository-settings", - "/enterprise/2.13/user/articles/managing-repository-settings": "/en/enterprise/2.13/user/articles/managing-repository-settings", - "/enterprise/2.13/articles/managing-repository-settings": "/en/enterprise/2.13/user/articles/managing-repository-settings", - "/en/enterprise/2.13/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.13/user/articles/managing-team-access-to-an-organization-repository", - "/enterprise/2.13/user/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.13/user/articles/managing-team-access-to-an-organization-repository", - "/enterprise/2.13/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.13/user/articles/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.13/articles/managing-user-account-settings": "/en/enterprise/2.13/user/articles/managing-user-account-settings", - "/enterprise/2.13/user/articles/managing-user-account-settings": "/en/enterprise/2.13/user/articles/managing-user-account-settings", - "/enterprise/2.13/articles/managing-user-account-settings": "/en/enterprise/2.13/user/articles/managing-user-account-settings", - "/en/enterprise/2.13/articles/managing-your-membership-in-organizations": "/en/enterprise/2.13/user/articles/managing-your-membership-in-organizations", - "/enterprise/2.13/user/articles/managing-your-membership-in-organizations": "/en/enterprise/2.13/user/articles/managing-your-membership-in-organizations", - "/enterprise/2.13/articles/managing-your-membership-in-organizations": "/en/enterprise/2.13/user/articles/managing-your-membership-in-organizations", - "/en/enterprise/2.13/articles/managing-your-notifications": "/en/enterprise/2.13/user/articles/managing-your-notifications", - "/enterprise/2.13/user/articles/managing-your-notifications": "/en/enterprise/2.13/user/articles/managing-your-notifications", - "/enterprise/2.13/articles/managing-your-notifications": "/en/enterprise/2.13/user/articles/managing-your-notifications", - "/en/enterprise/2.13/articles/managing-your-stars": "/en/enterprise/2.13/user/articles/managing-your-stars", - "/enterprise/2.13/user/articles/managing-your-stars": "/en/enterprise/2.13/user/articles/managing-your-stars", - "/enterprise/2.13/articles/managing-your-stars": "/en/enterprise/2.13/user/articles/managing-your-stars", - "/en/enterprise/2.13/articles/managing-your-work-with-issues": "/en/enterprise/2.13/user/articles/managing-your-work-with-issues", - "/enterprise/2.13/user/articles/managing-your-work-with-issues": "/en/enterprise/2.13/user/articles/managing-your-work-with-issues", - "/enterprise/2.13/articles/managing-your-work-with-issues": "/en/enterprise/2.13/user/articles/managing-your-work-with-issues", - "/en/enterprise/2.13/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.13/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.13/user/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.13/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.13/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.13/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.13/articles/mapping-geojson-files-on-github": "/en/enterprise/2.13/user/articles/mapping-geojson-files-on-github", - "/enterprise/2.13/user/articles/mapping-geojson-files-on-github": "/en/enterprise/2.13/user/articles/mapping-geojson-files-on-github", - "/enterprise/2.13/articles/mapping-geojson-files-on-github": "/en/enterprise/2.13/user/articles/mapping-geojson-files-on-github", - "/en/enterprise/2.13/articles/marking-notifications-as-read": "/en/enterprise/2.13/user/articles/marking-notifications-as-read", - "/enterprise/2.13/user/articles/marking-notifications-as-read": "/en/enterprise/2.13/user/articles/marking-notifications-as-read", - "/enterprise/2.13/articles/marking-notifications-as-read": "/en/enterprise/2.13/user/articles/marking-notifications-as-read", - "/en/enterprise/2.13/articles/mentions-on-github-pages": "/en/enterprise/2.13/user/articles/mentions-on-github-pages", - "/enterprise/2.13/user/articles/mentions-on-github-pages": "/en/enterprise/2.13/user/articles/mentions-on-github-pages", - "/enterprise/2.13/articles/mentions-on-github-pages": "/en/enterprise/2.13/user/articles/mentions-on-github-pages", - "/en/enterprise/2.13/articles/merging-a-pull-request": "/en/enterprise/2.13/user/articles/merging-a-pull-request", - "/enterprise/2.13/user/articles/merging-a-pull-request": "/en/enterprise/2.13/user/articles/merging-a-pull-request", - "/enterprise/2.13/articles/merging-a-pull-request": "/en/enterprise/2.13/user/articles/merging-a-pull-request", - "/en/enterprise/2.13/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.13/user/articles/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.13/user/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.13/user/articles/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.13/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.13/user/articles/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.13/articles/mime-types-on-github-pages": "/en/enterprise/2.13/user/articles/mime-types-on-github-pages", - "/enterprise/2.13/user/articles/mime-types-on-github-pages": "/en/enterprise/2.13/user/articles/mime-types-on-github-pages", - "/enterprise/2.13/articles/mime-types-on-github-pages": "/en/enterprise/2.13/user/articles/mime-types-on-github-pages", - "/en/enterprise/2.13/articles/moderating-comments-and-conversations": "/en/enterprise/2.13/user/articles/moderating-comments-and-conversations", - "/enterprise/2.13/user/articles/moderating-comments-and-conversations": "/en/enterprise/2.13/user/articles/moderating-comments-and-conversations", - "/enterprise/2.13/articles/moderating-comments-and-conversations": "/en/enterprise/2.13/user/articles/moderating-comments-and-conversations", - "/en/enterprise/2.13/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.13/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.13/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.13/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.13/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.13/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.13/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.13/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.13/user/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.13/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.13/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.13/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.13/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.13/user/articles/moving-a-file-to-a-new-location", - "/enterprise/2.13/user/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.13/user/articles/moving-a-file-to-a-new-location", - "/enterprise/2.13/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.13/user/articles/moving-a-file-to-a-new-location", - "/en/enterprise/2.13/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.13/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.13/user/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.13/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.13/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.13/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.13/articles/opening-an-issue-from-code": "/en/enterprise/2.13/user/articles/opening-an-issue-from-code", - "/enterprise/2.13/user/articles/opening-an-issue-from-code": "/en/enterprise/2.13/user/articles/opening-an-issue-from-code", - "/enterprise/2.13/articles/opening-an-issue-from-code": "/en/enterprise/2.13/user/articles/opening-an-issue-from-code", - "/en/enterprise/2.13/articles/organizing-information-with-tables": "/en/enterprise/2.13/user/articles/organizing-information-with-tables", - "/enterprise/2.13/user/articles/organizing-information-with-tables": "/en/enterprise/2.13/user/articles/organizing-information-with-tables", - "/enterprise/2.13/articles/organizing-information-with-tables": "/en/enterprise/2.13/user/articles/organizing-information-with-tables", - "/en/enterprise/2.13/articles/organizing-members-into-teams": "/en/enterprise/2.13/user/articles/organizing-members-into-teams", - "/enterprise/2.13/user/articles/organizing-members-into-teams": "/en/enterprise/2.13/user/articles/organizing-members-into-teams", - "/enterprise/2.13/articles/organizing-members-into-teams": "/en/enterprise/2.13/user/articles/organizing-members-into-teams", - "/en/enterprise/2.13/articles/page-build-failed-config-file-error": "/en/enterprise/2.13/user/articles/page-build-failed-config-file-error", - "/enterprise/2.13/user/articles/page-build-failed-config-file-error": "/en/enterprise/2.13/user/articles/page-build-failed-config-file-error", - "/enterprise/2.13/articles/page-build-failed-config-file-error": "/en/enterprise/2.13/user/articles/page-build-failed-config-file-error", - "/en/enterprise/2.13/articles/page-build-failed-date-is-not-a-valid-datetime": "/en/enterprise/2.13/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/enterprise/2.13/user/articles/page-build-failed-date-is-not-a-valid-datetime": "/en/enterprise/2.13/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/enterprise/2.13/articles/page-build-failed-date-is-not-a-valid-datetime": "/en/enterprise/2.13/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/en/enterprise/2.13/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/en/enterprise/2.13/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/enterprise/2.13/user/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/en/enterprise/2.13/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/enterprise/2.13/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/en/enterprise/2.13/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/en/enterprise/2.13/articles/page-build-failed-file-is-a-symlink": "/en/enterprise/2.13/user/articles/page-build-failed-file-is-a-symlink", - "/enterprise/2.13/user/articles/page-build-failed-file-is-a-symlink": "/en/enterprise/2.13/user/articles/page-build-failed-file-is-a-symlink", - "/enterprise/2.13/articles/page-build-failed-file-is-a-symlink": "/en/enterprise/2.13/user/articles/page-build-failed-file-is-a-symlink", - "/en/enterprise/2.13/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/en/enterprise/2.13/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/enterprise/2.13/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/en/enterprise/2.13/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/enterprise/2.13/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/en/enterprise/2.13/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/en/enterprise/2.13/articles/page-build-failed-invalid-highlighter-language": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-highlighter-language", - "/enterprise/2.13/user/articles/page-build-failed-invalid-highlighter-language": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-highlighter-language", - "/enterprise/2.13/articles/page-build-failed-invalid-highlighter-language": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-highlighter-language", - "/en/enterprise/2.13/articles/page-build-failed-invalid-post-date": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-post-date", - "/enterprise/2.13/user/articles/page-build-failed-invalid-post-date": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-post-date", - "/enterprise/2.13/articles/page-build-failed-invalid-post-date": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-post-date", - "/en/enterprise/2.13/articles/page-build-failed-invalid-sass-or-scss": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-sass-or-scss", - "/enterprise/2.13/user/articles/page-build-failed-invalid-sass-or-scss": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-sass-or-scss", - "/enterprise/2.13/articles/page-build-failed-invalid-sass-or-scss": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-sass-or-scss", - "/en/enterprise/2.13/articles/page-build-failed-invalid-submodule": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-submodule", - "/enterprise/2.13/user/articles/page-build-failed-invalid-submodule": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-submodule", - "/enterprise/2.13/articles/page-build-failed-invalid-submodule": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-submodule", - "/en/enterprise/2.13/articles/page-build-failed-invalid-yaml-in-data-file": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/enterprise/2.13/user/articles/page-build-failed-invalid-yaml-in-data-file": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/enterprise/2.13/articles/page-build-failed-invalid-yaml-in-data-file": "/en/enterprise/2.13/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/en/enterprise/2.13/articles/page-build-failed-markdown-errors": "/en/enterprise/2.13/user/articles/page-build-failed-markdown-errors", - "/enterprise/2.13/user/articles/page-build-failed-markdown-errors": "/en/enterprise/2.13/user/articles/page-build-failed-markdown-errors", - "/enterprise/2.13/articles/page-build-failed-markdown-errors": "/en/enterprise/2.13/user/articles/page-build-failed-markdown-errors", - "/en/enterprise/2.13/articles/page-build-failed-missing-docs-folder": "/en/enterprise/2.13/user/articles/page-build-failed-missing-docs-folder", - "/enterprise/2.13/user/articles/page-build-failed-missing-docs-folder": "/en/enterprise/2.13/user/articles/page-build-failed-missing-docs-folder", - "/enterprise/2.13/articles/page-build-failed-missing-docs-folder": "/en/enterprise/2.13/user/articles/page-build-failed-missing-docs-folder", - "/en/enterprise/2.13/articles/page-build-failed-missing-submodule": "/en/enterprise/2.13/user/articles/page-build-failed-missing-submodule", - "/enterprise/2.13/user/articles/page-build-failed-missing-submodule": "/en/enterprise/2.13/user/articles/page-build-failed-missing-submodule", - "/enterprise/2.13/articles/page-build-failed-missing-submodule": "/en/enterprise/2.13/user/articles/page-build-failed-missing-submodule", - "/en/enterprise/2.13/articles/page-build-failed-relative-permalinks-configured": "/en/enterprise/2.13/user/articles/page-build-failed-relative-permalinks-configured", - "/enterprise/2.13/user/articles/page-build-failed-relative-permalinks-configured": "/en/enterprise/2.13/user/articles/page-build-failed-relative-permalinks-configured", - "/enterprise/2.13/articles/page-build-failed-relative-permalinks-configured": "/en/enterprise/2.13/user/articles/page-build-failed-relative-permalinks-configured", - "/en/enterprise/2.13/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/en/enterprise/2.13/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/enterprise/2.13/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/en/enterprise/2.13/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/enterprise/2.13/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/en/enterprise/2.13/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/en/enterprise/2.13/articles/page-build-failed-syntax-error-in-for-loop": "/en/enterprise/2.13/user/articles/page-build-failed-syntax-error-in-for-loop", - "/enterprise/2.13/user/articles/page-build-failed-syntax-error-in-for-loop": "/en/enterprise/2.13/user/articles/page-build-failed-syntax-error-in-for-loop", - "/enterprise/2.13/articles/page-build-failed-syntax-error-in-for-loop": "/en/enterprise/2.13/user/articles/page-build-failed-syntax-error-in-for-loop", - "/en/enterprise/2.13/articles/page-build-failed-tag-not-properly-closed": "/en/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-closed", - "/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-closed": "/en/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-closed", - "/enterprise/2.13/articles/page-build-failed-tag-not-properly-closed": "/en/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-closed", - "/en/enterprise/2.13/articles/page-build-failed-tag-not-properly-terminated": "/en/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-terminated", - "/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-terminated": "/en/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-terminated", - "/enterprise/2.13/articles/page-build-failed-tag-not-properly-terminated": "/en/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-terminated", - "/en/enterprise/2.13/articles/page-build-failed-unknown-tag-error": "/en/enterprise/2.13/user/articles/page-build-failed-unknown-tag-error", - "/enterprise/2.13/user/articles/page-build-failed-unknown-tag-error": "/en/enterprise/2.13/user/articles/page-build-failed-unknown-tag-error", - "/enterprise/2.13/articles/page-build-failed-unknown-tag-error": "/en/enterprise/2.13/user/articles/page-build-failed-unknown-tag-error", - "/en/enterprise/2.13/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.13/user/articles/permission-levels-for-a-user-account-repository", - "/enterprise/2.13/user/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.13/user/articles/permission-levels-for-a-user-account-repository", - "/enterprise/2.13/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.13/user/articles/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.13/articles/permission-levels-for-an-organization": "/en/enterprise/2.13/user/articles/permission-levels-for-an-organization", - "/enterprise/2.13/user/articles/permission-levels-for-an-organization": "/en/enterprise/2.13/user/articles/permission-levels-for-an-organization", - "/enterprise/2.13/articles/permission-levels-for-an-organization": "/en/enterprise/2.13/user/articles/permission-levels-for-an-organization", - "/en/enterprise/2.13/articles/personalizing-your-profile": "/en/enterprise/2.13/user/articles/personalizing-your-profile", - "/enterprise/2.13/user/articles/personalizing-your-profile": "/en/enterprise/2.13/user/articles/personalizing-your-profile", - "/enterprise/2.13/articles/personalizing-your-profile": "/en/enterprise/2.13/user/articles/personalizing-your-profile", - "/en/enterprise/2.13/articles/pinning-a-team-discussion": "/en/enterprise/2.13/user/articles/pinning-a-team-discussion", - "/enterprise/2.13/user/articles/pinning-a-team-discussion": "/en/enterprise/2.13/user/articles/pinning-a-team-discussion", - "/enterprise/2.13/articles/pinning-a-team-discussion": "/en/enterprise/2.13/user/articles/pinning-a-team-discussion", - "/en/enterprise/2.13/articles/pinning-items-to-your-profile": "/en/enterprise/2.13/user/articles/pinning-items-to-your-profile", - "/enterprise/2.13/user/articles/pinning-items-to-your-profile": "/en/enterprise/2.13/user/articles/pinning-items-to-your-profile", - "/enterprise/2.13/articles/pinning-items-to-your-profile": "/en/enterprise/2.13/user/articles/pinning-items-to-your-profile", - "/en/enterprise/2.13/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.13/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.13/user/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.13/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.13/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.13/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.13/articles/preventing-unauthorized-access": "/en/enterprise/2.13/user/articles/preventing-unauthorized-access", - "/enterprise/2.13/user/articles/preventing-unauthorized-access": "/en/enterprise/2.13/user/articles/preventing-unauthorized-access", - "/enterprise/2.13/articles/preventing-unauthorized-access": "/en/enterprise/2.13/user/articles/preventing-unauthorized-access", - "/en/enterprise/2.13/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.13/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.13/user/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.13/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.13/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.13/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.13/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.13/user/articles/publicizing-or-hiding-organization-membership", - "/enterprise/2.13/user/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.13/user/articles/publicizing-or-hiding-organization-membership", - "/enterprise/2.13/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.13/user/articles/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.13/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.13/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.13/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.13/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.13/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.13/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.13/articles/pushing-to-a-remote": "/en/enterprise/2.13/user/articles/pushing-to-a-remote", - "/enterprise/2.13/user/articles/pushing-to-a-remote": "/en/enterprise/2.13/user/articles/pushing-to-a-remote", - "/enterprise/2.13/articles/pushing-to-a-remote": "/en/enterprise/2.13/user/articles/pushing-to-a-remote", - "/en/enterprise/2.13/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.13/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.13/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.13/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.13/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.13/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.13/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.13/user/articles/recovering-your-ssh-key-passphrase", - "/enterprise/2.13/user/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.13/user/articles/recovering-your-ssh-key-passphrase", - "/enterprise/2.13/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.13/user/articles/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.13/articles/redirects-on-github-pages": "/en/enterprise/2.13/user/articles/redirects-on-github-pages", - "/enterprise/2.13/user/articles/redirects-on-github-pages": "/en/enterprise/2.13/user/articles/redirects-on-github-pages", - "/enterprise/2.13/articles/redirects-on-github-pages": "/en/enterprise/2.13/user/articles/redirects-on-github-pages", - "/en/enterprise/2.13/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.13/user/articles/reinstating-a-former-member-of-your-organization", - "/enterprise/2.13/user/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.13/user/articles/reinstating-a-former-member-of-your-organization", - "/enterprise/2.13/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.13/user/articles/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.13/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.13/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.13/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.13/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.13/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.13/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.13/articles/remembering-your-github-username-or-email": "/en/enterprise/2.13/user/articles/remembering-your-github-username-or-email", - "/enterprise/2.13/user/articles/remembering-your-github-username-or-email": "/en/enterprise/2.13/user/articles/remembering-your-github-username-or-email", - "/enterprise/2.13/articles/remembering-your-github-username-or-email": "/en/enterprise/2.13/user/articles/remembering-your-github-username-or-email", - "/en/enterprise/2.13/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.13/user/articles/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.13/user/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.13/user/articles/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.13/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.13/user/articles/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.13/articles/removing-a-member-from-your-organization": "/en/enterprise/2.13/user/articles/removing-a-member-from-your-organization", - "/enterprise/2.13/user/articles/removing-a-member-from-your-organization": "/en/enterprise/2.13/user/articles/removing-a-member-from-your-organization", - "/enterprise/2.13/articles/removing-a-member-from-your-organization": "/en/enterprise/2.13/user/articles/removing-a-member-from-your-organization", - "/en/enterprise/2.13/articles/removing-a-remote": "/en/enterprise/2.13/user/articles/removing-a-remote", - "/enterprise/2.13/user/articles/removing-a-remote": "/en/enterprise/2.13/user/articles/removing-a-remote", - "/enterprise/2.13/articles/removing-a-remote": "/en/enterprise/2.13/user/articles/removing-a-remote", - "/en/enterprise/2.13/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.13/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.13/user/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.13/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.13/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.13/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.13/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.13/user/articles/removing-files-from-a-repositorys-history", - "/enterprise/2.13/user/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.13/user/articles/removing-files-from-a-repositorys-history", - "/enterprise/2.13/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.13/user/articles/removing-files-from-a-repositorys-history", - "/en/enterprise/2.13/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.13/user/articles/removing-files-from-git-large-file-storage", - "/enterprise/2.13/user/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.13/user/articles/removing-files-from-git-large-file-storage", - "/enterprise/2.13/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.13/user/articles/removing-files-from-git-large-file-storage", - "/en/enterprise/2.13/articles/removing-organization-members-from-a-team": "/en/enterprise/2.13/user/articles/removing-organization-members-from-a-team", - "/enterprise/2.13/user/articles/removing-organization-members-from-a-team": "/en/enterprise/2.13/user/articles/removing-organization-members-from-a-team", - "/enterprise/2.13/articles/removing-organization-members-from-a-team": "/en/enterprise/2.13/user/articles/removing-organization-members-from-a-team", - "/en/enterprise/2.13/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.13/user/articles/removing-sensitive-data-from-a-repository", - "/enterprise/2.13/user/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.13/user/articles/removing-sensitive-data-from-a-repository", - "/enterprise/2.13/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.13/user/articles/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.13/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.13/user/articles/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.13/user/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.13/user/articles/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.13/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.13/user/articles/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.13/articles/removing-yourself-from-an-organization": "/en/enterprise/2.13/user/articles/removing-yourself-from-an-organization", - "/enterprise/2.13/user/articles/removing-yourself-from-an-organization": "/en/enterprise/2.13/user/articles/removing-yourself-from-an-organization", - "/enterprise/2.13/articles/removing-yourself-from-an-organization": "/en/enterprise/2.13/user/articles/removing-yourself-from-an-organization", - "/en/enterprise/2.13/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.13/user/articles/renaming-a-file-using-the-command-line", - "/enterprise/2.13/user/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.13/user/articles/renaming-a-file-using-the-command-line", - "/enterprise/2.13/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.13/user/articles/renaming-a-file-using-the-command-line", - "/en/enterprise/2.13/articles/renaming-a-file": "/en/enterprise/2.13/user/articles/renaming-a-file", - "/enterprise/2.13/user/articles/renaming-a-file": "/en/enterprise/2.13/user/articles/renaming-a-file", - "/enterprise/2.13/articles/renaming-a-file": "/en/enterprise/2.13/user/articles/renaming-a-file", - "/en/enterprise/2.13/articles/renaming-a-remote": "/en/enterprise/2.13/user/articles/renaming-a-remote", - "/enterprise/2.13/user/articles/renaming-a-remote": "/en/enterprise/2.13/user/articles/renaming-a-remote", - "/enterprise/2.13/articles/renaming-a-remote": "/en/enterprise/2.13/user/articles/renaming-a-remote", - "/en/enterprise/2.13/articles/renaming-a-repository": "/en/enterprise/2.13/user/articles/renaming-a-repository", - "/enterprise/2.13/user/articles/renaming-a-repository": "/en/enterprise/2.13/user/articles/renaming-a-repository", - "/enterprise/2.13/articles/renaming-a-repository": "/en/enterprise/2.13/user/articles/renaming-a-repository", - "/en/enterprise/2.13/articles/renaming-a-team": "/en/enterprise/2.13/user/articles/renaming-a-team", - "/enterprise/2.13/user/articles/renaming-a-team": "/en/enterprise/2.13/user/articles/renaming-a-team", - "/enterprise/2.13/articles/renaming-a-team": "/en/enterprise/2.13/user/articles/renaming-a-team", - "/en/enterprise/2.13/articles/renaming-an-organization": "/en/enterprise/2.13/user/articles/renaming-an-organization", - "/enterprise/2.13/user/articles/renaming-an-organization": "/en/enterprise/2.13/user/articles/renaming-an-organization", - "/enterprise/2.13/articles/renaming-an-organization": "/en/enterprise/2.13/user/articles/renaming-an-organization", - "/en/enterprise/2.13/articles/rendering-and-diffing-images": "/en/enterprise/2.13/user/articles/rendering-and-diffing-images", - "/enterprise/2.13/user/articles/rendering-and-diffing-images": "/en/enterprise/2.13/user/articles/rendering-and-diffing-images", - "/enterprise/2.13/articles/rendering-and-diffing-images": "/en/enterprise/2.13/user/articles/rendering-and-diffing-images", - "/en/enterprise/2.13/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.13/user/articles/rendering-csv-and-tsv-data", - "/enterprise/2.13/user/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.13/user/articles/rendering-csv-and-tsv-data", - "/enterprise/2.13/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.13/user/articles/rendering-csv-and-tsv-data", - "/en/enterprise/2.13/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.13/user/articles/rendering-differences-in-prose-documents", - "/enterprise/2.13/user/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.13/user/articles/rendering-differences-in-prose-documents", - "/enterprise/2.13/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.13/user/articles/rendering-differences-in-prose-documents", - "/en/enterprise/2.13/articles/rendering-pdf-documents": "/en/enterprise/2.13/user/articles/rendering-pdf-documents", - "/enterprise/2.13/user/articles/rendering-pdf-documents": "/en/enterprise/2.13/user/articles/rendering-pdf-documents", - "/enterprise/2.13/articles/rendering-pdf-documents": "/en/enterprise/2.13/user/articles/rendering-pdf-documents", - "/en/enterprise/2.13/articles/repository-metadata-on-github-pages": "/en/enterprise/2.13/user/articles/repository-metadata-on-github-pages", - "/enterprise/2.13/user/articles/repository-metadata-on-github-pages": "/en/enterprise/2.13/user/articles/repository-metadata-on-github-pages", - "/enterprise/2.13/articles/repository-metadata-on-github-pages": "/en/enterprise/2.13/user/articles/repository-metadata-on-github-pages", - "/en/enterprise/2.13/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.13/user/articles/repository-permission-levels-for-an-organization", - "/enterprise/2.13/user/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.13/user/articles/repository-permission-levels-for-an-organization", - "/enterprise/2.13/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.13/user/articles/repository-permission-levels-for-an-organization", - "/en/enterprise/2.13/articles/requesting-a-pull-request-review": "/en/enterprise/2.13/user/articles/requesting-a-pull-request-review", - "/enterprise/2.13/user/articles/requesting-a-pull-request-review": "/en/enterprise/2.13/user/articles/requesting-a-pull-request-review", - "/enterprise/2.13/articles/requesting-a-pull-request-review": "/en/enterprise/2.13/user/articles/requesting-a-pull-request-review", - "/en/enterprise/2.13/articles/requesting-to-add-a-child-team": "/en/enterprise/2.13/user/articles/requesting-to-add-a-child-team", - "/enterprise/2.13/user/articles/requesting-to-add-a-child-team": "/en/enterprise/2.13/user/articles/requesting-to-add-a-child-team", - "/enterprise/2.13/articles/requesting-to-add-a-child-team": "/en/enterprise/2.13/user/articles/requesting-to-add-a-child-team", - "/en/enterprise/2.13/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.13/user/articles/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.13/user/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.13/user/articles/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.13/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.13/user/articles/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.13/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.13/user/articles/resolving-a-merge-conflict-on-github", - "/enterprise/2.13/user/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.13/user/articles/resolving-a-merge-conflict-on-github", - "/enterprise/2.13/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.13/user/articles/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.13/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.13/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.13/user/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.13/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.13/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.13/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.13/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.13/user/articles/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.13/user/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.13/user/articles/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.13/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.13/user/articles/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.13/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.13/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.13/user/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.13/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.13/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.13/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.13/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.13/user/articles/restricting-repository-creation-in-your-organization", - "/enterprise/2.13/user/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.13/user/articles/restricting-repository-creation-in-your-organization", - "/enterprise/2.13/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.13/user/articles/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.13/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.13/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.13/user/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.13/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.13/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.13/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.13/articles/reverting-a-pull-request": "/en/enterprise/2.13/user/articles/reverting-a-pull-request", - "/enterprise/2.13/user/articles/reverting-a-pull-request": "/en/enterprise/2.13/user/articles/reverting-a-pull-request", - "/enterprise/2.13/articles/reverting-a-pull-request": "/en/enterprise/2.13/user/articles/reverting-a-pull-request", - "/en/enterprise/2.13/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.13/user/articles/reviewing-changes-in-pull-requests", - "/enterprise/2.13/user/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.13/user/articles/reviewing-changes-in-pull-requests", - "/enterprise/2.13/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.13/user/articles/reviewing-changes-in-pull-requests", - "/en/enterprise/2.13/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.13/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.13/user/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.13/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.13/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.13/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.13/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.13/user/articles/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.13/user/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.13/user/articles/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.13/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.13/user/articles/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.13/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.13/user/articles/reviewing-your-authorized-applications-oauth", - "/enterprise/2.13/user/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.13/user/articles/reviewing-your-authorized-applications-oauth", - "/enterprise/2.13/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.13/user/articles/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.13/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.13/user/articles/reviewing-your-authorized-integrations", - "/enterprise/2.13/user/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.13/user/articles/reviewing-your-authorized-integrations", - "/enterprise/2.13/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.13/user/articles/reviewing-your-authorized-integrations", - "/en/enterprise/2.13/articles/reviewing-your-deploy-keys": "/en/enterprise/2.13/user/articles/reviewing-your-deploy-keys", - "/enterprise/2.13/user/articles/reviewing-your-deploy-keys": "/en/enterprise/2.13/user/articles/reviewing-your-deploy-keys", - "/enterprise/2.13/articles/reviewing-your-deploy-keys": "/en/enterprise/2.13/user/articles/reviewing-your-deploy-keys", - "/en/enterprise/2.13/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.13/user/articles/reviewing-your-organizations-installed-integrations", - "/enterprise/2.13/user/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.13/user/articles/reviewing-your-organizations-installed-integrations", - "/enterprise/2.13/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.13/user/articles/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.13/articles/reviewing-your-security-log": "/en/enterprise/2.13/user/articles/reviewing-your-security-log", - "/enterprise/2.13/user/articles/reviewing-your-security-log": "/en/enterprise/2.13/user/articles/reviewing-your-security-log", - "/enterprise/2.13/articles/reviewing-your-security-log": "/en/enterprise/2.13/user/articles/reviewing-your-security-log", - "/en/enterprise/2.13/articles/reviewing-your-ssh-keys": "/en/enterprise/2.13/user/articles/reviewing-your-ssh-keys", - "/enterprise/2.13/user/articles/reviewing-your-ssh-keys": "/en/enterprise/2.13/user/articles/reviewing-your-ssh-keys", - "/enterprise/2.13/articles/reviewing-your-ssh-keys": "/en/enterprise/2.13/user/articles/reviewing-your-ssh-keys", - "/en/enterprise/2.13/articles/searching-code": "/en/enterprise/2.13/user/articles/searching-code", - "/enterprise/2.13/user/articles/searching-code": "/en/enterprise/2.13/user/articles/searching-code", - "/enterprise/2.13/articles/searching-code": "/en/enterprise/2.13/user/articles/searching-code", - "/en/enterprise/2.13/articles/searching-commits": "/en/enterprise/2.13/user/articles/searching-commits", - "/enterprise/2.13/user/articles/searching-commits": "/en/enterprise/2.13/user/articles/searching-commits", - "/enterprise/2.13/articles/searching-commits": "/en/enterprise/2.13/user/articles/searching-commits", - "/en/enterprise/2.13/articles/searching-for-repositories": "/en/enterprise/2.13/user/articles/searching-for-repositories", - "/enterprise/2.13/user/articles/searching-for-repositories": "/en/enterprise/2.13/user/articles/searching-for-repositories", - "/enterprise/2.13/articles/searching-for-repositories": "/en/enterprise/2.13/user/articles/searching-for-repositories", - "/en/enterprise/2.13/articles/searching-in-forks": "/en/enterprise/2.13/user/articles/searching-in-forks", - "/enterprise/2.13/user/articles/searching-in-forks": "/en/enterprise/2.13/user/articles/searching-in-forks", - "/enterprise/2.13/articles/searching-in-forks": "/en/enterprise/2.13/user/articles/searching-in-forks", - "/en/enterprise/2.13/articles/searching-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/searching-issues-and-pull-requests", - "/enterprise/2.13/user/articles/searching-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/searching-issues-and-pull-requests", - "/enterprise/2.13/articles/searching-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/searching-issues-and-pull-requests", - "/en/enterprise/2.13/articles/searching-on-github": "/en/enterprise/2.13/user/articles/searching-on-github", - "/enterprise/2.13/user/articles/searching-on-github": "/en/enterprise/2.13/user/articles/searching-on-github", - "/enterprise/2.13/articles/searching-on-github": "/en/enterprise/2.13/user/articles/searching-on-github", - "/en/enterprise/2.13/articles/searching-topics": "/en/enterprise/2.13/user/articles/searching-topics", - "/enterprise/2.13/user/articles/searching-topics": "/en/enterprise/2.13/user/articles/searching-topics", - "/enterprise/2.13/articles/searching-topics": "/en/enterprise/2.13/user/articles/searching-topics", - "/en/enterprise/2.13/articles/searching-users": "/en/enterprise/2.13/user/articles/searching-users", - "/enterprise/2.13/user/articles/searching-users": "/en/enterprise/2.13/user/articles/searching-users", - "/enterprise/2.13/articles/searching-users": "/en/enterprise/2.13/user/articles/searching-users", - "/en/enterprise/2.13/articles/searching-wikis": "/en/enterprise/2.13/user/articles/searching-wikis", - "/enterprise/2.13/user/articles/searching-wikis": "/en/enterprise/2.13/user/articles/searching-wikis", - "/enterprise/2.13/articles/searching-wikis": "/en/enterprise/2.13/user/articles/searching-wikis", - "/en/enterprise/2.13/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.13/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.13/user/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.13/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.13/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.13/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.13/articles/set-up-git": "/en/enterprise/2.13/user/articles/set-up-git", - "/enterprise/2.13/user/articles/set-up-git": "/en/enterprise/2.13/user/articles/set-up-git", - "/enterprise/2.13/articles/set-up-git": "/en/enterprise/2.13/user/articles/set-up-git", - "/en/enterprise/2.13/articles/setting-a-backup-email-address": "/en/enterprise/2.13/user/articles/setting-a-backup-email-address", - "/enterprise/2.13/user/articles/setting-a-backup-email-address": "/en/enterprise/2.13/user/articles/setting-a-backup-email-address", - "/enterprise/2.13/articles/setting-a-backup-email-address": "/en/enterprise/2.13/user/articles/setting-a-backup-email-address", - "/en/enterprise/2.13/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.13/user/articles/setting-guidelines-for-repository-contributors", - "/enterprise/2.13/user/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.13/user/articles/setting-guidelines-for-repository-contributors", - "/enterprise/2.13/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.13/user/articles/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.13/articles/setting-repository-visibility": "/en/enterprise/2.13/user/articles/setting-repository-visibility", - "/enterprise/2.13/user/articles/setting-repository-visibility": "/en/enterprise/2.13/user/articles/setting-repository-visibility", - "/enterprise/2.13/articles/setting-repository-visibility": "/en/enterprise/2.13/user/articles/setting-repository-visibility", - "/en/enterprise/2.13/articles/setting-the-default-branch": "/en/enterprise/2.13/user/articles/setting-the-default-branch", - "/enterprise/2.13/user/articles/setting-the-default-branch": "/en/enterprise/2.13/user/articles/setting-the-default-branch", - "/enterprise/2.13/articles/setting-the-default-branch": "/en/enterprise/2.13/user/articles/setting-the-default-branch", - "/en/enterprise/2.13/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.13/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.13/user/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.13/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.13/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.13/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.13/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.13/user/articles/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.13/user/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.13/user/articles/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.13/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.13/user/articles/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.13/articles/setting-your-commit-email-address-in-git": "/en/enterprise/2.13/user/articles/setting-your-commit-email-address-in-git", - "/enterprise/2.13/user/articles/setting-your-commit-email-address-in-git": "/en/enterprise/2.13/user/articles/setting-your-commit-email-address-in-git", - "/enterprise/2.13/articles/setting-your-commit-email-address-in-git": "/en/enterprise/2.13/user/articles/setting-your-commit-email-address-in-git", - "/en/enterprise/2.13/articles/setting-your-commit-email-address-on-github": "/en/enterprise/2.13/user/articles/setting-your-commit-email-address-on-github", - "/enterprise/2.13/user/articles/setting-your-commit-email-address-on-github": "/en/enterprise/2.13/user/articles/setting-your-commit-email-address-on-github", - "/enterprise/2.13/articles/setting-your-commit-email-address-on-github": "/en/enterprise/2.13/user/articles/setting-your-commit-email-address-on-github", - "/en/enterprise/2.13/articles/setting-your-teams-profile-picture": "/en/enterprise/2.13/user/articles/setting-your-teams-profile-picture", - "/enterprise/2.13/user/articles/setting-your-teams-profile-picture": "/en/enterprise/2.13/user/articles/setting-your-teams-profile-picture", - "/enterprise/2.13/articles/setting-your-teams-profile-picture": "/en/enterprise/2.13/user/articles/setting-your-teams-profile-picture", - "/en/enterprise/2.13/articles/setting-your-username-in-git": "/en/enterprise/2.13/user/articles/setting-your-username-in-git", - "/enterprise/2.13/user/articles/setting-your-username-in-git": "/en/enterprise/2.13/user/articles/setting-your-username-in-git", - "/enterprise/2.13/articles/setting-your-username-in-git": "/en/enterprise/2.13/user/articles/setting-your-username-in-git", - "/en/enterprise/2.13/articles/sharing-filters": "/en/enterprise/2.13/user/articles/sharing-filters", - "/enterprise/2.13/user/articles/sharing-filters": "/en/enterprise/2.13/user/articles/sharing-filters", - "/enterprise/2.13/articles/sharing-filters": "/en/enterprise/2.13/user/articles/sharing-filters", - "/en/enterprise/2.13/articles/signing-commits": "/en/enterprise/2.13/user/articles/signing-commits", - "/enterprise/2.13/user/articles/signing-commits": "/en/enterprise/2.13/user/articles/signing-commits", - "/enterprise/2.13/articles/signing-commits": "/en/enterprise/2.13/user/articles/signing-commits", - "/en/enterprise/2.13/articles/signing-tags": "/en/enterprise/2.13/user/articles/signing-tags", - "/enterprise/2.13/user/articles/signing-tags": "/en/enterprise/2.13/user/articles/signing-tags", - "/enterprise/2.13/articles/signing-tags": "/en/enterprise/2.13/user/articles/signing-tags", - "/en/enterprise/2.13/articles/sitemaps-for-github-pages": "/en/enterprise/2.13/user/articles/sitemaps-for-github-pages", - "/enterprise/2.13/user/articles/sitemaps-for-github-pages": "/en/enterprise/2.13/user/articles/sitemaps-for-github-pages", - "/enterprise/2.13/articles/sitemaps-for-github-pages": "/en/enterprise/2.13/user/articles/sitemaps-for-github-pages", - "/en/enterprise/2.13/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/sorting-issues-and-pull-requests", - "/enterprise/2.13/user/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/sorting-issues-and-pull-requests", - "/enterprise/2.13/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/sorting-issues-and-pull-requests", - "/en/enterprise/2.13/articles/sorting-search-results": "/en/enterprise/2.13/user/articles/sorting-search-results", - "/enterprise/2.13/user/articles/sorting-search-results": "/en/enterprise/2.13/user/articles/sorting-search-results", - "/enterprise/2.13/articles/sorting-search-results": "/en/enterprise/2.13/user/articles/sorting-search-results", - "/en/enterprise/2.13/articles/source-code-migration-tools": "/en/enterprise/2.13/user/articles/source-code-migration-tools", - "/enterprise/2.13/user/articles/source-code-migration-tools": "/en/enterprise/2.13/user/articles/source-code-migration-tools", - "/enterprise/2.13/articles/source-code-migration-tools": "/en/enterprise/2.13/user/articles/source-code-migration-tools", - "/en/enterprise/2.13/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.13/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.13/user/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.13/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.13/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.13/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.13/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.13/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.13/user/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.13/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.13/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.13/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.13/articles/subversion-properties-supported-by-github": "/en/enterprise/2.13/user/articles/subversion-properties-supported-by-github", - "/enterprise/2.13/user/articles/subversion-properties-supported-by-github": "/en/enterprise/2.13/user/articles/subversion-properties-supported-by-github", - "/enterprise/2.13/articles/subversion-properties-supported-by-github": "/en/enterprise/2.13/user/articles/subversion-properties-supported-by-github", - "/en/enterprise/2.13/articles/sudo-mode": "/en/enterprise/2.13/user/articles/sudo-mode", - "/enterprise/2.13/user/articles/sudo-mode": "/en/enterprise/2.13/user/articles/sudo-mode", - "/enterprise/2.13/articles/sudo-mode": "/en/enterprise/2.13/user/articles/sudo-mode", - "/en/enterprise/2.13/articles/support-for-subversion-clients": "/en/enterprise/2.13/user/articles/support-for-subversion-clients", - "/enterprise/2.13/user/articles/support-for-subversion-clients": "/en/enterprise/2.13/user/articles/support-for-subversion-clients", - "/enterprise/2.13/articles/support-for-subversion-clients": "/en/enterprise/2.13/user/articles/support-for-subversion-clients", - "/en/enterprise/2.13/articles/supported-browsers": "/en/enterprise/2.13/user/articles/supported-browsers", - "/enterprise/2.13/user/articles/supported-browsers": "/en/enterprise/2.13/user/articles/supported-browsers", - "/enterprise/2.13/articles/supported-browsers": "/en/enterprise/2.13/user/articles/supported-browsers", - "/en/enterprise/2.13/articles/syncing-a-fork": "/en/enterprise/2.13/user/articles/syncing-a-fork", - "/enterprise/2.13/user/articles/syncing-a-fork": "/en/enterprise/2.13/user/articles/syncing-a-fork", - "/enterprise/2.13/articles/syncing-a-fork": "/en/enterprise/2.13/user/articles/syncing-a-fork", - "/en/enterprise/2.13/articles/telling-git-about-your-signing-key": "/en/enterprise/2.13/user/articles/telling-git-about-your-signing-key", - "/enterprise/2.13/user/articles/telling-git-about-your-signing-key": "/en/enterprise/2.13/user/articles/telling-git-about-your-signing-key", - "/enterprise/2.13/articles/telling-git-about-your-signing-key": "/en/enterprise/2.13/user/articles/telling-git-about-your-signing-key", - "/en/enterprise/2.13/articles/testing-your-ssh-connection": "/en/enterprise/2.13/user/articles/testing-your-ssh-connection", - "/enterprise/2.13/user/articles/testing-your-ssh-connection": "/en/enterprise/2.13/user/articles/testing-your-ssh-connection", - "/enterprise/2.13/articles/testing-your-ssh-connection": "/en/enterprise/2.13/user/articles/testing-your-ssh-connection", - "/en/enterprise/2.13/articles/tracking-changes-in-a-file": "/en/enterprise/2.13/user/articles/tracking-changes-in-a-file", - "/enterprise/2.13/user/articles/tracking-changes-in-a-file": "/en/enterprise/2.13/user/articles/tracking-changes-in-a-file", - "/enterprise/2.13/articles/tracking-changes-in-a-file": "/en/enterprise/2.13/user/articles/tracking-changes-in-a-file", - "/en/enterprise/2.13/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.13/user/articles/tracking-progress-on-your-project-board", - "/enterprise/2.13/user/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.13/user/articles/tracking-progress-on-your-project-board", - "/enterprise/2.13/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.13/user/articles/tracking-progress-on-your-project-board", - "/en/enterprise/2.13/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.13/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.13/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.13/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.13/articles/transferring-a-repository": "/en/enterprise/2.13/user/articles/transferring-a-repository", - "/enterprise/2.13/user/articles/transferring-a-repository": "/en/enterprise/2.13/user/articles/transferring-a-repository", - "/enterprise/2.13/articles/transferring-a-repository": "/en/enterprise/2.13/user/articles/transferring-a-repository", - "/en/enterprise/2.13/articles/transferring-organization-ownership": "/en/enterprise/2.13/user/articles/transferring-organization-ownership", - "/enterprise/2.13/user/articles/transferring-organization-ownership": "/en/enterprise/2.13/user/articles/transferring-organization-ownership", - "/enterprise/2.13/articles/transferring-organization-ownership": "/en/enterprise/2.13/user/articles/transferring-organization-ownership", - "/en/enterprise/2.13/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.13/user/articles/troubleshooting-commit-signature-verification", - "/enterprise/2.13/user/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.13/user/articles/troubleshooting-commit-signature-verification", - "/enterprise/2.13/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.13/user/articles/troubleshooting-commit-signature-verification", - "/en/enterprise/2.13/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.13/user/articles/troubleshooting-commits-on-your-timeline", - "/enterprise/2.13/user/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.13/user/articles/troubleshooting-commits-on-your-timeline", - "/enterprise/2.13/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.13/user/articles/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.13/articles/troubleshooting-github-pages-builds": "/en/enterprise/2.13/user/articles/troubleshooting-github-pages-builds", - "/enterprise/2.13/user/articles/troubleshooting-github-pages-builds": "/en/enterprise/2.13/user/articles/troubleshooting-github-pages-builds", - "/enterprise/2.13/articles/troubleshooting-github-pages-builds": "/en/enterprise/2.13/user/articles/troubleshooting-github-pages-builds", - "/en/enterprise/2.13/articles/troubleshooting-search-queries": "/en/enterprise/2.13/user/articles/troubleshooting-search-queries", - "/enterprise/2.13/user/articles/troubleshooting-search-queries": "/en/enterprise/2.13/user/articles/troubleshooting-search-queries", - "/enterprise/2.13/articles/troubleshooting-search-queries": "/en/enterprise/2.13/user/articles/troubleshooting-search-queries", - "/en/enterprise/2.13/articles/troubleshooting-ssh": "/en/enterprise/2.13/user/articles/troubleshooting-ssh", - "/enterprise/2.13/user/articles/troubleshooting-ssh": "/en/enterprise/2.13/user/articles/troubleshooting-ssh", - "/enterprise/2.13/articles/troubleshooting-ssh": "/en/enterprise/2.13/user/articles/troubleshooting-ssh", - "/en/enterprise/2.13/articles/types-of-required-status-checks": "/en/enterprise/2.13/user/articles/types-of-required-status-checks", - "/enterprise/2.13/user/articles/types-of-required-status-checks": "/en/enterprise/2.13/user/articles/types-of-required-status-checks", - "/enterprise/2.13/articles/types-of-required-status-checks": "/en/enterprise/2.13/user/articles/types-of-required-status-checks", - "/en/enterprise/2.13/articles/understanding-connections-between-repositories": "/en/enterprise/2.13/user/articles/understanding-connections-between-repositories", - "/enterprise/2.13/user/articles/understanding-connections-between-repositories": "/en/enterprise/2.13/user/articles/understanding-connections-between-repositories", - "/enterprise/2.13/articles/understanding-connections-between-repositories": "/en/enterprise/2.13/user/articles/understanding-connections-between-repositories", - "/en/enterprise/2.13/articles/understanding-the-search-syntax": "/en/enterprise/2.13/user/articles/understanding-the-search-syntax", - "/enterprise/2.13/user/articles/understanding-the-search-syntax": "/en/enterprise/2.13/user/articles/understanding-the-search-syntax", - "/enterprise/2.13/articles/understanding-the-search-syntax": "/en/enterprise/2.13/user/articles/understanding-the-search-syntax", - "/en/enterprise/2.13/articles/unpublishing-a-project-pages-site": "/en/enterprise/2.13/user/articles/unpublishing-a-project-pages-site", - "/enterprise/2.13/user/articles/unpublishing-a-project-pages-site": "/en/enterprise/2.13/user/articles/unpublishing-a-project-pages-site", - "/enterprise/2.13/articles/unpublishing-a-project-pages-site": "/en/enterprise/2.13/user/articles/unpublishing-a-project-pages-site", - "/en/enterprise/2.13/articles/unpublishing-a-user-pages-site": "/en/enterprise/2.13/user/articles/unpublishing-a-user-pages-site", - "/enterprise/2.13/user/articles/unpublishing-a-user-pages-site": "/en/enterprise/2.13/user/articles/unpublishing-a-user-pages-site", - "/enterprise/2.13/articles/unpublishing-a-user-pages-site": "/en/enterprise/2.13/user/articles/unpublishing-a-user-pages-site", - "/en/enterprise/2.13/articles/updating-an-expired-gpg-key": "/en/enterprise/2.13/user/articles/updating-an-expired-gpg-key", - "/enterprise/2.13/user/articles/updating-an-expired-gpg-key": "/en/enterprise/2.13/user/articles/updating-an-expired-gpg-key", - "/enterprise/2.13/articles/updating-an-expired-gpg-key": "/en/enterprise/2.13/user/articles/updating-an-expired-gpg-key", - "/en/enterprise/2.13/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.13/user/articles/updating-credentials-from-the-osx-keychain", - "/enterprise/2.13/user/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.13/user/articles/updating-credentials-from-the-osx-keychain", - "/enterprise/2.13/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.13/user/articles/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.13/articles/updating-your-github-access-credentials": "/en/enterprise/2.13/user/articles/updating-your-github-access-credentials", - "/enterprise/2.13/user/articles/updating-your-github-access-credentials": "/en/enterprise/2.13/user/articles/updating-your-github-access-credentials", - "/enterprise/2.13/articles/updating-your-github-access-credentials": "/en/enterprise/2.13/user/articles/updating-your-github-access-credentials", - "/en/enterprise/2.13/articles/updating-your-markdown-processor-to-kramdown": "/en/enterprise/2.13/user/articles/updating-your-markdown-processor-to-kramdown", - "/enterprise/2.13/user/articles/updating-your-markdown-processor-to-kramdown": "/en/enterprise/2.13/user/articles/updating-your-markdown-processor-to-kramdown", - "/enterprise/2.13/articles/updating-your-markdown-processor-to-kramdown": "/en/enterprise/2.13/user/articles/updating-your-markdown-processor-to-kramdown", - "/en/enterprise/2.13/articles/user-organization-and-project-pages": "/en/enterprise/2.13/user/articles/user-organization-and-project-pages", - "/enterprise/2.13/user/articles/user-organization-and-project-pages": "/en/enterprise/2.13/user/articles/user-organization-and-project-pages", - "/enterprise/2.13/articles/user-organization-and-project-pages": "/en/enterprise/2.13/user/articles/user-organization-and-project-pages", - "/en/enterprise/2.13/articles/using-a-static-site-generator-other-than-jekyll": "/en/enterprise/2.13/user/articles/using-a-static-site-generator-other-than-jekyll", - "/enterprise/2.13/user/articles/using-a-static-site-generator-other-than-jekyll": "/en/enterprise/2.13/user/articles/using-a-static-site-generator-other-than-jekyll", - "/enterprise/2.13/articles/using-a-static-site-generator-other-than-jekyll": "/en/enterprise/2.13/user/articles/using-a-static-site-generator-other-than-jekyll", - "/en/enterprise/2.13/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.13/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.13/user/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.13/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.13/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.13/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.13/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.13/user/articles/using-git-rebase-on-the-command-line", - "/enterprise/2.13/user/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.13/user/articles/using-git-rebase-on-the-command-line", - "/enterprise/2.13/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.13/user/articles/using-git-rebase-on-the-command-line", - "/en/enterprise/2.13/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/en/enterprise/2.13/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/enterprise/2.13/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/en/enterprise/2.13/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/enterprise/2.13/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/en/enterprise/2.13/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/en/enterprise/2.13/articles/using-keyboard-shortcuts": "/en/enterprise/2.13/user/articles/using-keyboard-shortcuts", - "/enterprise/2.13/user/articles/using-keyboard-shortcuts": "/en/enterprise/2.13/user/articles/using-keyboard-shortcuts", - "/enterprise/2.13/articles/using-keyboard-shortcuts": "/en/enterprise/2.13/user/articles/using-keyboard-shortcuts", - "/en/enterprise/2.13/articles/using-saved-replies": "/en/enterprise/2.13/user/articles/using-saved-replies", - "/enterprise/2.13/user/articles/using-saved-replies": "/en/enterprise/2.13/user/articles/using-saved-replies", - "/enterprise/2.13/articles/using-saved-replies": "/en/enterprise/2.13/user/articles/using-saved-replies", - "/en/enterprise/2.13/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.13/user/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.13/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.13/articles/using-syntax-highlighting-on-github-pages": "/en/enterprise/2.13/user/articles/using-syntax-highlighting-on-github-pages", - "/enterprise/2.13/user/articles/using-syntax-highlighting-on-github-pages": "/en/enterprise/2.13/user/articles/using-syntax-highlighting-on-github-pages", - "/enterprise/2.13/articles/using-syntax-highlighting-on-github-pages": "/en/enterprise/2.13/user/articles/using-syntax-highlighting-on-github-pages", - "/en/enterprise/2.13/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/en/enterprise/2.13/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/enterprise/2.13/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/en/enterprise/2.13/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/enterprise/2.13/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/en/enterprise/2.13/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/en/enterprise/2.13/articles/versioning-large-files": "/en/enterprise/2.13/user/articles/versioning-large-files", - "/enterprise/2.13/user/articles/versioning-large-files": "/en/enterprise/2.13/user/articles/versioning-large-files", - "/enterprise/2.13/articles/versioning-large-files": "/en/enterprise/2.13/user/articles/versioning-large-files", - "/en/enterprise/2.13/articles/viewing-a-pull-request-review": "/en/enterprise/2.13/user/articles/viewing-a-pull-request-review", - "/enterprise/2.13/user/articles/viewing-a-pull-request-review": "/en/enterprise/2.13/user/articles/viewing-a-pull-request-review", - "/enterprise/2.13/articles/viewing-a-pull-request-review": "/en/enterprise/2.13/user/articles/viewing-a-pull-request-review", - "/en/enterprise/2.13/articles/viewing-a-repositorys-network": "/en/enterprise/2.13/user/articles/viewing-a-repositorys-network", - "/enterprise/2.13/user/articles/viewing-a-repositorys-network": "/en/enterprise/2.13/user/articles/viewing-a-repositorys-network", - "/enterprise/2.13/articles/viewing-a-repositorys-network": "/en/enterprise/2.13/user/articles/viewing-a-repositorys-network", - "/en/enterprise/2.13/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.13/user/articles/viewing-a-summary-of-repository-activity", - "/enterprise/2.13/user/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.13/user/articles/viewing-a-summary-of-repository-activity", - "/enterprise/2.13/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.13/user/articles/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.13/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.13/user/articles/viewing-a-wikis-history-of-changes", - "/enterprise/2.13/user/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.13/user/articles/viewing-a-wikis-history-of-changes", - "/enterprise/2.13/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.13/user/articles/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.13/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.13/user/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.13/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.13/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.13/articles/viewing-branches-in-your-repository": "/en/enterprise/2.13/user/articles/viewing-branches-in-your-repository", - "/enterprise/2.13/user/articles/viewing-branches-in-your-repository": "/en/enterprise/2.13/user/articles/viewing-branches-in-your-repository", - "/enterprise/2.13/articles/viewing-branches-in-your-repository": "/en/enterprise/2.13/user/articles/viewing-branches-in-your-repository", - "/en/enterprise/2.13/articles/viewing-contribution-activity-in-a-repository": "/en/enterprise/2.13/user/articles/viewing-contribution-activity-in-a-repository", - "/enterprise/2.13/user/articles/viewing-contribution-activity-in-a-repository": "/en/enterprise/2.13/user/articles/viewing-contribution-activity-in-a-repository", - "/enterprise/2.13/articles/viewing-contribution-activity-in-a-repository": "/en/enterprise/2.13/user/articles/viewing-contribution-activity-in-a-repository", - "/en/enterprise/2.13/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.13/user/articles/viewing-contributions-on-your-profile", - "/enterprise/2.13/user/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.13/user/articles/viewing-contributions-on-your-profile", - "/enterprise/2.13/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.13/user/articles/viewing-contributions-on-your-profile", - "/en/enterprise/2.13/articles/viewing-jekyll-build-error-messages": "/en/enterprise/2.13/user/articles/viewing-jekyll-build-error-messages", - "/enterprise/2.13/user/articles/viewing-jekyll-build-error-messages": "/en/enterprise/2.13/user/articles/viewing-jekyll-build-error-messages", - "/enterprise/2.13/articles/viewing-jekyll-build-error-messages": "/en/enterprise/2.13/user/articles/viewing-jekyll-build-error-messages", - "/en/enterprise/2.13/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.13/user/articles/viewing-peoples-roles-in-an-organization", - "/enterprise/2.13/user/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.13/user/articles/viewing-peoples-roles-in-an-organization", - "/enterprise/2.13/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.13/user/articles/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.13/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.13/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.13/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.13/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.13/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.13/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.13/articles/viewing-your-milestones-progress": "/en/enterprise/2.13/user/articles/viewing-your-milestones-progress", - "/enterprise/2.13/user/articles/viewing-your-milestones-progress": "/en/enterprise/2.13/user/articles/viewing-your-milestones-progress", - "/enterprise/2.13/articles/viewing-your-milestones-progress": "/en/enterprise/2.13/user/articles/viewing-your-milestones-progress", - "/en/enterprise/2.13/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.13/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.13/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.13/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.13/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.13/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.13/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.13/user/articles/visualizing-commits-in-a-repository", - "/enterprise/2.13/user/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.13/user/articles/visualizing-commits-in-a-repository", - "/enterprise/2.13/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.13/user/articles/visualizing-commits-in-a-repository", - "/en/enterprise/2.13/articles/watching-and-unwatching-repositories": "/en/enterprise/2.13/user/articles/watching-and-unwatching-repositories", - "/enterprise/2.13/user/articles/watching-and-unwatching-repositories": "/en/enterprise/2.13/user/articles/watching-and-unwatching-repositories", - "/enterprise/2.13/articles/watching-and-unwatching-repositories": "/en/enterprise/2.13/user/articles/watching-and-unwatching-repositories", - "/en/enterprise/2.13/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.13/user/articles/watching-and-unwatching-team-discussions", - "/enterprise/2.13/user/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.13/user/articles/watching-and-unwatching-team-discussions", - "/enterprise/2.13/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.13/user/articles/watching-and-unwatching-team-discussions", - "/en/enterprise/2.13/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.13/user/articles/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.13/user/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.13/user/articles/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.13/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.13/user/articles/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.13/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.13/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.13/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.13/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.13/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.13/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.13/articles/what-happens-when-i-change-my-username": "/en/enterprise/2.13/user/articles/what-happens-when-i-change-my-username", - "/enterprise/2.13/user/articles/what-happens-when-i-change-my-username": "/en/enterprise/2.13/user/articles/what-happens-when-i-change-my-username", - "/enterprise/2.13/articles/what-happens-when-i-change-my-username": "/en/enterprise/2.13/user/articles/what-happens-when-i-change-my-username", - "/en/enterprise/2.13/articles/what-is-a-good-git-workflow": "/en/enterprise/2.13/user/articles/what-is-a-good-git-workflow", - "/enterprise/2.13/user/articles/what-is-a-good-git-workflow": "/en/enterprise/2.13/user/articles/what-is-a-good-git-workflow", - "/enterprise/2.13/articles/what-is-a-good-git-workflow": "/en/enterprise/2.13/user/articles/what-is-a-good-git-workflow", - "/en/enterprise/2.13/articles/what-is-github-pages": "/en/enterprise/2.13/user/articles/what-is-github-pages", - "/enterprise/2.13/user/articles/what-is-github-pages": "/en/enterprise/2.13/user/articles/what-is-github-pages", - "/enterprise/2.13/articles/what-is-github-pages": "/en/enterprise/2.13/user/articles/what-is-github-pages", - "/en/enterprise/2.13/articles/which-remote-url-should-i-use": "/en/enterprise/2.13/user/articles/which-remote-url-should-i-use", - "/enterprise/2.13/user/articles/which-remote-url-should-i-use": "/en/enterprise/2.13/user/articles/which-remote-url-should-i-use", - "/enterprise/2.13/articles/which-remote-url-should-i-use": "/en/enterprise/2.13/user/articles/which-remote-url-should-i-use", - "/en/enterprise/2.13/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.13/user/articles/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.13/user/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.13/user/articles/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.13/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.13/user/articles/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.13/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.13/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.13/user/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.13/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.13/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.13/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.13/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.13/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.13/user/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.13/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.13/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.13/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.13/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.13/user/articles/why-is-git-always-asking-for-my-password", - "/enterprise/2.13/user/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.13/user/articles/why-is-git-always-asking-for-my-password", - "/enterprise/2.13/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.13/user/articles/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.13/articles/working-with-advanced-formatting": "/en/enterprise/2.13/user/articles/working-with-advanced-formatting", - "/enterprise/2.13/user/articles/working-with-advanced-formatting": "/en/enterprise/2.13/user/articles/working-with-advanced-formatting", - "/enterprise/2.13/articles/working-with-advanced-formatting": "/en/enterprise/2.13/user/articles/working-with-advanced-formatting", - "/en/enterprise/2.13/articles/working-with-forks": "/en/enterprise/2.13/user/articles/working-with-forks", - "/enterprise/2.13/user/articles/working-with-forks": "/en/enterprise/2.13/user/articles/working-with-forks", - "/enterprise/2.13/articles/working-with-forks": "/en/enterprise/2.13/user/articles/working-with-forks", - "/en/enterprise/2.13/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.13/user/articles/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.13/user/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.13/user/articles/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.13/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.13/user/articles/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.13/articles/working-with-large-files": "/en/enterprise/2.13/user/articles/working-with-large-files", - "/enterprise/2.13/user/articles/working-with-large-files": "/en/enterprise/2.13/user/articles/working-with-large-files", - "/enterprise/2.13/articles/working-with-large-files": "/en/enterprise/2.13/user/articles/working-with-large-files", - "/en/enterprise/2.13/articles/working-with-pre-receive-hooks": "/en/enterprise/2.13/user/articles/working-with-pre-receive-hooks", - "/enterprise/2.13/user/articles/working-with-pre-receive-hooks": "/en/enterprise/2.13/user/articles/working-with-pre-receive-hooks", - "/enterprise/2.13/articles/working-with-pre-receive-hooks": "/en/enterprise/2.13/user/articles/working-with-pre-receive-hooks", - "/en/enterprise/2.13/articles/working-with-saved-replies": "/en/enterprise/2.13/user/articles/working-with-saved-replies", - "/enterprise/2.13/user/articles/working-with-saved-replies": "/en/enterprise/2.13/user/articles/working-with-saved-replies", - "/enterprise/2.13/articles/working-with-saved-replies": "/en/enterprise/2.13/user/articles/working-with-saved-replies", - "/en/enterprise/2.13/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.13/user/articles/working-with-ssh-key-passphrases", - "/enterprise/2.13/user/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.13/user/articles/working-with-ssh-key-passphrases", - "/enterprise/2.13/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.13/user/articles/working-with-ssh-key-passphrases", - "/en/enterprise/2.13/articles/working-with-subversion-on-github": "/en/enterprise/2.13/user/articles/working-with-subversion-on-github", - "/enterprise/2.13/user/articles/working-with-subversion-on-github": "/en/enterprise/2.13/user/articles/working-with-subversion-on-github", - "/enterprise/2.13/articles/working-with-subversion-on-github": "/en/enterprise/2.13/user/articles/working-with-subversion-on-github", - "/en/enterprise/2.13/articles/working-with-tags": "/en/enterprise/2.13/user/articles/working-with-tags", - "/enterprise/2.13/user/articles/working-with-tags": "/en/enterprise/2.13/user/articles/working-with-tags", - "/enterprise/2.13/articles/working-with-tags": "/en/enterprise/2.13/user/articles/working-with-tags", - "/en/enterprise/2.13/categories/about-github": "/en/enterprise/2.13/user/categories/about-github", - "/enterprise/2.13/user/categories/about-github": "/en/enterprise/2.13/user/categories/about-github", - "/enterprise/2.13/categories/about-github": "/en/enterprise/2.13/user/categories/about-github", - "/en/enterprise/2.13/user/categories/admin/guidesistering-a-repository": "/en/enterprise/2.13/user/categories/administering-a-repository", - "/en/enterprise/2.13/categories/administering-a-repository": "/en/enterprise/2.13/user/categories/administering-a-repository", - "/enterprise/2.13/user/categories/administering-a-repository": "/en/enterprise/2.13/user/categories/administering-a-repository", - "/enterprise/2.13/user/categories/admin/guidesistering-a-repository": "/en/enterprise/2.13/user/categories/administering-a-repository", - "/enterprise/2.13/categories/administering-a-repository": "/en/enterprise/2.13/user/categories/administering-a-repository", - "/en/enterprise/2.13/categories/advanced-git": "/en/enterprise/2.13/user/categories/advanced-git", - "/enterprise/2.13/user/categories/advanced-git": "/en/enterprise/2.13/user/categories/advanced-git", - "/enterprise/2.13/categories/advanced-git": "/en/enterprise/2.13/user/categories/advanced-git", - "/en/enterprise/2.13/categories/authenticating-to-github": "/en/enterprise/2.13/user/categories/authenticating-to-github", - "/enterprise/2.13/user/categories/authenticating-to-github": "/en/enterprise/2.13/user/categories/authenticating-to-github", - "/enterprise/2.13/categories/authenticating-to-github": "/en/enterprise/2.13/user/categories/authenticating-to-github", - "/en/enterprise/2.13/categories/automation": "/en/enterprise/2.13/user/categories/automation", - "/enterprise/2.13/user/categories/automation": "/en/enterprise/2.13/user/categories/automation", - "/enterprise/2.13/categories/automation": "/en/enterprise/2.13/user/categories/automation", - "/en/enterprise/2.13/categories/bootcamp": "/en/enterprise/2.13/user/categories/bootcamp", - "/enterprise/2.13/user/categories/bootcamp": "/en/enterprise/2.13/user/categories/bootcamp", - "/enterprise/2.13/categories/bootcamp": "/en/enterprise/2.13/user/categories/bootcamp", - "/en/enterprise/2.13/categories/building-a-strong-community": "/en/enterprise/2.13/user/categories/building-a-strong-community", - "/enterprise/2.13/user/categories/building-a-strong-community": "/en/enterprise/2.13/user/categories/building-a-strong-community", - "/enterprise/2.13/categories/building-a-strong-community": "/en/enterprise/2.13/user/categories/building-a-strong-community", - "/en/enterprise/2.13/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.13/user/categories/collaborating-with-issues-and-pull-requests", - "/enterprise/2.13/user/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.13/user/categories/collaborating-with-issues-and-pull-requests", - "/enterprise/2.13/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.13/user/categories/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.13/categories/commits": "/en/enterprise/2.13/user/categories/commits", - "/enterprise/2.13/user/categories/commits": "/en/enterprise/2.13/user/categories/commits", - "/enterprise/2.13/categories/commits": "/en/enterprise/2.13/user/categories/commits", - "/en/enterprise/2.13/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.13/user/categories/creating-cloning-and-archiving-repositories", - "/enterprise/2.13/user/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.13/user/categories/creating-cloning-and-archiving-repositories", - "/enterprise/2.13/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.13/user/categories/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.13/categories/customizing-github-pages": "/en/enterprise/2.13/user/categories/customizing-github-pages", - "/enterprise/2.13/user/categories/customizing-github-pages": "/en/enterprise/2.13/user/categories/customizing-github-pages", - "/enterprise/2.13/categories/customizing-github-pages": "/en/enterprise/2.13/user/categories/customizing-github-pages", - "/en/enterprise/2.13/categories/exploring-projects-on-github": "/en/enterprise/2.13/user/categories/exploring-projects-on-github", - "/enterprise/2.13/user/categories/exploring-projects-on-github": "/en/enterprise/2.13/user/categories/exploring-projects-on-github", - "/enterprise/2.13/categories/exploring-projects-on-github": "/en/enterprise/2.13/user/categories/exploring-projects-on-github", - "/en/enterprise/2.13/categories/gists": "/en/enterprise/2.13/user/categories/gists", - "/enterprise/2.13/user/categories/gists": "/en/enterprise/2.13/user/categories/gists", - "/enterprise/2.13/categories/gists": "/en/enterprise/2.13/user/categories/gists", - "/en/enterprise/2.13/categories/github-pages-basics": "/en/enterprise/2.13/user/categories/github-pages-basics", - "/enterprise/2.13/user/categories/github-pages-basics": "/en/enterprise/2.13/user/categories/github-pages-basics", - "/enterprise/2.13/categories/github-pages-basics": "/en/enterprise/2.13/user/categories/github-pages-basics", - "/en/enterprise/2.13/categories/importing-your-projects-to-github": "/en/enterprise/2.13/user/categories/importing-your-projects-to-github", - "/enterprise/2.13/user/categories/importing-your-projects-to-github": "/en/enterprise/2.13/user/categories/importing-your-projects-to-github", - "/enterprise/2.13/categories/importing-your-projects-to-github": "/en/enterprise/2.13/user/categories/importing-your-projects-to-github", - "/en/enterprise/2.13/categories/keyboard-shortcuts": "/en/enterprise/2.13/user/categories/keyboard-shortcuts", - "/enterprise/2.13/user/categories/keyboard-shortcuts": "/en/enterprise/2.13/user/categories/keyboard-shortcuts", - "/enterprise/2.13/categories/keyboard-shortcuts": "/en/enterprise/2.13/user/categories/keyboard-shortcuts", - "/en/enterprise/2.13/categories/managing-files-in-a-repository": "/en/enterprise/2.13/user/categories/managing-files-in-a-repository", - "/enterprise/2.13/user/categories/managing-files-in-a-repository": "/en/enterprise/2.13/user/categories/managing-files-in-a-repository", - "/enterprise/2.13/categories/managing-files-in-a-repository": "/en/enterprise/2.13/user/categories/managing-files-in-a-repository", - "/en/enterprise/2.13/categories/managing-large-files": "/en/enterprise/2.13/user/categories/managing-large-files", - "/enterprise/2.13/user/categories/managing-large-files": "/en/enterprise/2.13/user/categories/managing-large-files", - "/enterprise/2.13/categories/managing-large-files": "/en/enterprise/2.13/user/categories/managing-large-files", - "/en/enterprise/2.13/categories/managing-remotes": "/en/enterprise/2.13/user/categories/managing-remotes", - "/enterprise/2.13/user/categories/managing-remotes": "/en/enterprise/2.13/user/categories/managing-remotes", - "/enterprise/2.13/categories/managing-remotes": "/en/enterprise/2.13/user/categories/managing-remotes", - "/en/enterprise/2.13/categories/managing-your-work-on-github": "/en/enterprise/2.13/user/categories/managing-your-work-on-github", - "/enterprise/2.13/user/categories/managing-your-work-on-github": "/en/enterprise/2.13/user/categories/managing-your-work-on-github", - "/enterprise/2.13/categories/managing-your-work-on-github": "/en/enterprise/2.13/user/categories/managing-your-work-on-github", - "/en/enterprise/2.13/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.13/user/categories/receiving-notifications-about-activity-on-github", - "/enterprise/2.13/user/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.13/user/categories/receiving-notifications-about-activity-on-github", - "/enterprise/2.13/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.13/user/categories/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.13/categories/releases": "/en/enterprise/2.13/user/categories/releases", - "/enterprise/2.13/user/categories/releases": "/en/enterprise/2.13/user/categories/releases", - "/enterprise/2.13/categories/releases": "/en/enterprise/2.13/user/categories/releases", - "/en/enterprise/2.13/categories/searching-for-information-on-github": "/en/enterprise/2.13/user/categories/searching-for-information-on-github", - "/enterprise/2.13/user/categories/searching-for-information-on-github": "/en/enterprise/2.13/user/categories/searching-for-information-on-github", - "/enterprise/2.13/categories/searching-for-information-on-github": "/en/enterprise/2.13/user/categories/searching-for-information-on-github", - "/en/enterprise/2.13/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.13/user/categories/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.13/user/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.13/user/categories/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.13/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.13/user/categories/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.13/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.13/user/categories/setting-up-and-managing-your-github-profile", - "/enterprise/2.13/user/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.13/user/categories/setting-up-and-managing-your-github-profile", - "/enterprise/2.13/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.13/user/categories/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.13/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.13/user/categories/setting-up-and-managing-your-github-user-account", - "/enterprise/2.13/user/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.13/user/categories/setting-up-and-managing-your-github-user-account", - "/enterprise/2.13/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.13/user/categories/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.13/categories/setup": "/en/enterprise/2.13/user/categories/setup", - "/enterprise/2.13/user/categories/setup": "/en/enterprise/2.13/user/categories/setup", - "/enterprise/2.13/categories/setup": "/en/enterprise/2.13/user/categories/setup", - "/en/enterprise/2.13/categories/using-git": "/en/enterprise/2.13/user/categories/using-git", - "/enterprise/2.13/user/categories/using-git": "/en/enterprise/2.13/user/categories/using-git", - "/enterprise/2.13/categories/using-git": "/en/enterprise/2.13/user/categories/using-git", - "/en/enterprise/2.13/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.13/user/categories/visualizing-repository-data-with-graphs", - "/enterprise/2.13/user/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.13/user/categories/visualizing-repository-data-with-graphs", - "/enterprise/2.13/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.13/user/categories/visualizing-repository-data-with-graphs", - "/en/enterprise/2.13/categories/working-with-non-code-files": "/en/enterprise/2.13/user/categories/working-with-non-code-files", - "/enterprise/2.13/user/categories/working-with-non-code-files": "/en/enterprise/2.13/user/categories/working-with-non-code-files", - "/enterprise/2.13/categories/working-with-non-code-files": "/en/enterprise/2.13/user/categories/working-with-non-code-files", - "/en/enterprise/2.13/categories/writing-on-github": "/en/enterprise/2.13/user/categories/writing-on-github", - "/enterprise/2.13/user/categories/writing-on-github": "/en/enterprise/2.13/user/categories/writing-on-github", - "/enterprise/2.13/categories/writing-on-github": "/en/enterprise/2.13/user/categories/writing-on-github", - "/enterprise/2.13/user": "/en/enterprise/2.13/user", - "/cn/enterprise/2.14/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/cn/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/cn/enterprise/2.14/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/cn/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/cn/enterprise/2.14/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/cn/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/cn/enterprise/2.14/admin/guides/articles/using-github-task-runner": "/cn/enterprise/2.14/admin/articles/using-github-task-runner", - "/cn/enterprise/2.14/admin/guides/clustering/about-cluster-nodes": "/cn/enterprise/2.14/admin/clustering/about-cluster-nodes", - "/cn/enterprise/2.14/admin/guides/clustering/clustering-overview": "/cn/enterprise/2.14/admin/clustering/clustering-overview", - "/cn/enterprise/2.14/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/cn/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/cn/enterprise/2.14/admin/guides/clustering/evacuating-a-cluster-node": "/cn/enterprise/2.14/admin/clustering/evacuating-a-cluster-node", - "/cn/enterprise/2.14/admin/guides/clustering": "/cn/enterprise/2.14/admin/clustering", - "/cn/enterprise/2.14/admin/guides/clustering/initializing-the-cluster": "/cn/enterprise/2.14/admin/clustering/initializing-the-cluster", - "/cn/enterprise/2.14/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/cn/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster", - "/cn/enterprise/2.14/admin/guides/clustering/monitoring-cluster-nodes": "/cn/enterprise/2.14/admin/clustering/monitoring-cluster-nodes", - "/cn/enterprise/2.14/admin/guides/clustering/network-configuration": "/cn/enterprise/2.14/admin/clustering/network-configuration", - "/cn/enterprise/2.14/admin/guides/clustering/replacing-a-cluster-node": "/cn/enterprise/2.14/admin/clustering/replacing-a-cluster-node", - "/cn/enterprise/2.14/admin/guides/clustering/setting-up-the-cluster-instances": "/cn/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances", - "/cn/enterprise/2.14/admin/guides/clustering/upgrading-a-cluster": "/cn/enterprise/2.14/admin/clustering/upgrading-a-cluster", - "/cn/enterprise/2.14/admin/guides/developer-workflow/about-pre-receive-hooks": "/cn/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks", - "/cn/enterprise/2.14/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/cn/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/cn/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/cn/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/cn/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/cn/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/cn/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/cn/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/cn/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes": "/cn/enterprise/2.14/admin/developer-workflow/blocking-force-pushes", - "/cn/enterprise/2.14/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/cn/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/cn/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/cn/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins", - "/cn/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/cn/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci", - "/cn/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/cn/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/cn/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/cn/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/cn/enterprise/2.14/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/cn/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations", - "/cn/enterprise/2.14/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/cn/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/cn/enterprise/2.14/admin/guides/developer-workflow": "/cn/enterprise/2.14/admin/developer-workflow", - "/cn/enterprise/2.14/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/cn/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/cn/enterprise/2.14/admin/guides/developer-workflow/managing-projects-using-jira": "/cn/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira", - "/cn/enterprise/2.14/admin/guides/developer-workflow/troubleshooting-service-hooks": "/cn/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks", - "/cn/enterprise/2.14/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/cn/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/cn/enterprise/2.14/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/cn/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/cn/enterprise/2.14/admin/guides/enterprise-support/about-github-enterprise-support": "/cn/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support", - "/cn/enterprise/2.14/admin/guides/enterprise-support": "/cn/enterprise/2.14/admin/enterprise-support", - "/cn/enterprise/2.14/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/cn/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket", - "/cn/enterprise/2.14/admin/guides/enterprise-support/providing-data-to-github-support": "/cn/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support", - "/cn/enterprise/2.14/admin/guides/enterprise-support/reaching-github-support": "/cn/enterprise/2.14/admin/enterprise-support/reaching-github-support", - "/cn/enterprise/2.14/admin/guides/enterprise-support/receiving-help-from-github-support": "/cn/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support", - "/cn/enterprise/2.14/admin/guides/enterprise-support/submitting-a-ticket": "/cn/enterprise/2.14/admin/enterprise-support/submitting-a-ticket", - "/cn/enterprise/2.14/admin/guides": "/cn/enterprise/2.14/admin", - "/cn/enterprise/2.14/admin/guides/installation/about-geo-replication": "/cn/enterprise/2.14/admin/installation/about-geo-replication", - "/cn/enterprise/2.14/admin/guides/installation/about-high-availability-configuration": "/cn/enterprise/2.14/admin/installation/about-high-availability-configuration", - "/cn/enterprise/2.14/admin/guides/installation/about-the-github-enterprise-server-api": "/cn/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api", - "/cn/enterprise/2.14/admin/guides/installation/accessing-the-administrative-shell-ssh": "/cn/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh", - "/cn/enterprise/2.14/admin/guides/installation/accessing-the-management-console": "/cn/enterprise/2.14/admin/installation/accessing-the-management-console", - "/cn/enterprise/2.14/admin/guides/installation/accessing-the-monitor-dashboard": "/cn/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard", - "/cn/enterprise/2.14/admin/guides/installation/activity-dashboard": "/cn/enterprise/2.14/admin/installation/activity-dashboard", - "/cn/enterprise/2.14/admin/guides/installation/audit-logging": "/cn/enterprise/2.14/admin/installation/audit-logging", - "/cn/enterprise/2.14/admin/guides/installation/audited-actions": "/cn/enterprise/2.14/admin/installation/audited-actions", - "/cn/enterprise/2.14/admin/guides/installation/command-line-utilities": "/cn/enterprise/2.14/admin/installation/command-line-utilities", - "/cn/enterprise/2.14/admin/guides/installation/configuring-a-hostname": "/cn/enterprise/2.14/admin/installation/configuring-a-hostname", - "/cn/enterprise/2.14/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/cn/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server", - "/cn/enterprise/2.14/admin/guides/installation/configuring-backups-on-your-appliance": "/cn/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance", - "/cn/enterprise/2.14/admin/guides/installation/configuring-built-in-firewall-rules": "/cn/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules", - "/cn/enterprise/2.14/admin/guides/installation/configuring-collectd": "/cn/enterprise/2.14/admin/installation/configuring-collectd", - "/cn/enterprise/2.14/admin/guides/installation/configuring-dns-nameservers": "/cn/enterprise/2.14/admin/installation/configuring-dns-nameservers", - "/cn/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/cn/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/cn/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/cn/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage": "/cn/enterprise/2.14/admin/installation/configuring-git-large-file-storage", - "/cn/enterprise/2.14/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/cn/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/cn/enterprise/2.14/admin/guides/installation/configuring-github-pages-on-your-appliance": "/cn/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance", - "/cn/enterprise/2.14/admin/guides/installation/configuring-rate-limits": "/cn/enterprise/2.14/admin/installation/configuring-rate-limits", - "/cn/enterprise/2.14/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/cn/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/cn/enterprise/2.14/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/cn/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance", - "/cn/enterprise/2.14/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/cn/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/cn/enterprise/2.14/admin/guides/installation/configuring-time-synchronization": "/cn/enterprise/2.14/admin/installation/configuring-time-synchronization", - "/cn/enterprise/2.14/admin/guides/installation/configuring-tls": "/cn/enterprise/2.14/admin/installation/configuring-tls", - "/cn/enterprise/2.14/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/cn/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/cn/enterprise/2.14/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/cn/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/cn/enterprise/2.14/admin/guides/installation/creating-a-high-availability-replica": "/cn/enterprise/2.14/admin/installation/creating-a-high-availability-replica", - "/cn/enterprise/2.14/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/cn/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/cn/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/cn/enterprise/2.14/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/cn/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode", - "/cn/enterprise/2.14/admin/guides/installation/enabling-automatic-update-checks": "/cn/enterprise/2.14/admin/installation/enabling-automatic-update-checks", - "/cn/enterprise/2.14/admin/guides/installation/enabling-private-mode": "/cn/enterprise/2.14/admin/installation/enabling-private-mode", - "/cn/enterprise/2.14/admin/guides/installation/enabling-subdomain-isolation": "/cn/enterprise/2.14/admin/installation/enabling-subdomain-isolation", - "/cn/enterprise/2.14/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.14/admin/guides/installation/increasing-cpu-or-memory-resources": "/cn/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources", - "/cn/enterprise/2.14/admin/guides/installation/increasing-storage-capacity": "/cn/enterprise/2.14/admin/installation/increasing-storage-capacity", - "/cn/enterprise/2.14/admin/guides/installation": "/cn/enterprise/2.14/admin/installation", - "/cn/enterprise/2.14/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/cn/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-aws": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-azure": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware", - "/cn/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/cn/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver", - "/cn/enterprise/2.14/admin/guides/installation/log-forwarding": "/cn/enterprise/2.14/admin/installation/log-forwarding", - "/cn/enterprise/2.14/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/cn/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/cn/enterprise/2.14/admin/guides/installation/managing-your-github-enterprise-server-license": "/cn/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license", - "/cn/enterprise/2.14/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/cn/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/cn/enterprise/2.14/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/cn/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/cn/enterprise/2.14/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/cn/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/cn/enterprise/2.14/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/cn/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/cn/enterprise/2.14/admin/guides/installation/monitoring-using-snmp": "/cn/enterprise/2.14/admin/installation/monitoring-using-snmp", - "/cn/enterprise/2.14/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/cn/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/cn/enterprise/2.14/admin/guides/installation/network-ports": "/cn/enterprise/2.14/admin/installation/network-ports", - "/cn/enterprise/2.14/admin/guides/installation/recommended-alert-thresholds": "/cn/enterprise/2.14/admin/installation/recommended-alert-thresholds", - "/cn/enterprise/2.14/admin/guides/installation/recovering-a-high-availability-configuration": "/cn/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration", - "/cn/enterprise/2.14/admin/guides/installation/removing-a-high-availability-replica": "/cn/enterprise/2.14/admin/installation/removing-a-high-availability-replica", - "/cn/enterprise/2.14/admin/guides/installation/searching-the-audit-log": "/cn/enterprise/2.14/admin/installation/searching-the-audit-log", - "/cn/enterprise/2.14/admin/guides/installation/setting-git-push-limits": "/cn/enterprise/2.14/admin/installation/setting-git-push-limits", - "/cn/enterprise/2.14/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/cn/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance", - "/cn/enterprise/2.14/admin/guides/installation/setting-up-a-staging-instance": "/cn/enterprise/2.14/admin/installation/setting-up-a-staging-instance", - "/cn/enterprise/2.14/admin/guides/installation/setting-up-external-monitoring": "/cn/enterprise/2.14/admin/installation/setting-up-external-monitoring", - "/cn/enterprise/2.14/admin/guides/installation/site-admin-dashboard": "/cn/enterprise/2.14/admin/installation/site-admin-dashboard", - "/cn/enterprise/2.14/admin/guides/installation/system-overview": "/cn/enterprise/2.14/admin/installation/system-overview", - "/cn/enterprise/2.14/admin/guides/installation/troubleshooting-ssl-errors": "/cn/enterprise/2.14/admin/installation/troubleshooting-ssl-errors", - "/cn/enterprise/2.14/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/cn/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/cn/enterprise/2.14/admin/guides/installation/upgrade-requirements": "/cn/enterprise/2.14/admin/installation/upgrade-requirements", - "/cn/enterprise/2.14/admin/guides/installation/upgrading-github-enterprise-server": "/cn/enterprise/2.14/admin/installation/upgrading-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/cn/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/cn/enterprise/2.14/admin/guides/installation/validating-your-domain-settings": "/cn/enterprise/2.14/admin/installation/validating-your-domain-settings", - "/cn/enterprise/2.14/admin/guides/installation/viewing-push-logs": "/cn/enterprise/2.14/admin/installation/viewing-push-logs", - "/cn/enterprise/2.14/admin/guides/migrations/about-migrations": "/cn/enterprise/2.14/admin/migrations/about-migrations", - "/cn/enterprise/2.14/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/cn/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/cn/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/cn/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-githubcom": "/cn/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom", - "/cn/enterprise/2.14/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/cn/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/cn/enterprise/2.14/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/cn/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/cn/enterprise/2.14/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/cn/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts", - "/cn/enterprise/2.14/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/cn/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems", - "/cn/enterprise/2.14/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/cn/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/migrations": "/cn/enterprise/2.14/admin/migrations", - "/cn/enterprise/2.14/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/cn/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/cn/enterprise/2.14/admin/guides/migrations/preparing-the-githubcom-source-organization": "/cn/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization", - "/cn/enterprise/2.14/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/cn/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/cn/enterprise/2.14/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/cn/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/cn/enterprise/2.14/admin/guides/migrations/reviewing-migration-conflicts": "/cn/enterprise/2.14/admin/migrations/reviewing-migration-conflicts", - "/cn/enterprise/2.14/admin/guides/migrations/reviewing-migration-data": "/cn/enterprise/2.14/admin/migrations/reviewing-migration-data", - "/cn/enterprise/2.14/admin/guides/user-management/about-global-webhooks": "/cn/enterprise/2.14/admin/user-management/about-global-webhooks", - "/cn/enterprise/2.14/admin/guides/user-management/adding-people-to-teams": "/cn/enterprise/2.14/admin/user-management/adding-people-to-teams", - "/cn/enterprise/2.14/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/cn/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/cn/enterprise/2.14/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/cn/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/cn/enterprise/2.14/admin/guides/user-management/archiving-and-unarchiving-repositories": "/cn/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories", - "/cn/enterprise/2.14/admin/guides/user-management/auditing-ssh-keys": "/cn/enterprise/2.14/admin/user-management/auditing-ssh-keys", - "/cn/enterprise/2.14/admin/guides/user-management/auditing-users-across-your-instance": "/cn/enterprise/2.14/admin/user-management/auditing-users-across-your-instance", - "/cn/enterprise/2.14/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/cn/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/cn/enterprise/2.14/admin/guides/user-management/basic-account-settings": "/cn/enterprise/2.14/admin/user-management/basic-account-settings", - "/cn/enterprise/2.14/admin/guides/user-management/best-practices-for-user-security": "/cn/enterprise/2.14/admin/user-management/best-practices-for-user-security", - "/cn/enterprise/2.14/admin/guides/user-management/changing-authentication-methods": "/cn/enterprise/2.14/admin/user-management/changing-authentication-methods", - "/cn/enterprise/2.14/admin/guides/user-management/configuring-email-for-notifications": "/cn/enterprise/2.14/admin/user-management/configuring-email-for-notifications", - "/cn/enterprise/2.14/admin/guides/user-management/configuring-visibility-for-organization-membership": "/cn/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership", - "/cn/enterprise/2.14/admin/guides/user-management/creating-organizations": "/cn/enterprise/2.14/admin/user-management/creating-organizations", - "/cn/enterprise/2.14/admin/guides/user-management/creating-teams": "/cn/enterprise/2.14/admin/user-management/creating-teams", - "/cn/enterprise/2.14/admin/guides/user-management/customizing-user-messages-on-your-instance": "/cn/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance", - "/cn/enterprise/2.14/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/cn/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups", - "/cn/enterprise/2.14/admin/guides/user-management": "/cn/enterprise/2.14/admin/user-management", - "/cn/enterprise/2.14/admin/guides/user-management/managing-dormant-users": "/cn/enterprise/2.14/admin/user-management/managing-dormant-users", - "/cn/enterprise/2.14/admin/guides/user-management/managing-global-webhooks": "/cn/enterprise/2.14/admin/user-management/managing-global-webhooks", - "/cn/enterprise/2.14/admin/guides/user-management/organizations-and-teams": "/cn/enterprise/2.14/admin/user-management/organizations-and-teams", - "/cn/enterprise/2.14/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/cn/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/cn/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/cn/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/cn/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/cn/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/cn/enterprise/2.14/admin/guides/user-management/preventing-users-from-creating-organizations": "/cn/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations", - "/cn/enterprise/2.14/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/cn/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/cn/enterprise/2.14/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/cn/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator", - "/cn/enterprise/2.14/admin/guides/user-management/rebuilding-contributions-data": "/cn/enterprise/2.14/admin/user-management/rebuilding-contributions-data", - "/cn/enterprise/2.14/admin/guides/user-management/removing-users-from-teams-and-organizations": "/cn/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations", - "/cn/enterprise/2.14/admin/guides/user-management/repositories": "/cn/enterprise/2.14/admin/user-management/repositories", - "/cn/enterprise/2.14/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/cn/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/cn/enterprise/2.14/admin/guides/user-management/suspending-and-unsuspending-users": "/cn/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users", - "/cn/enterprise/2.14/admin/guides/user-management/user-security": "/cn/enterprise/2.14/admin/user-management/user-security", - "/cn/enterprise/2.14/admin/guides/user-management/using-built-in-authentication": "/cn/enterprise/2.14/admin/user-management/using-built-in-authentication", - "/cn/enterprise/2.14/admin/guides/user-management/using-cas": "/cn/enterprise/2.14/admin/user-management/using-cas", - "/cn/enterprise/2.14/admin/guides/user-management/using-ldap": "/cn/enterprise/2.14/admin/user-management/using-ldap", - "/cn/enterprise/2.14/admin/guides/user-management/using-saml": "/cn/enterprise/2.14/admin/user-management/using-saml", - "/cn/enterprise/2.14/articles/3d-file-viewer": "/cn/enterprise/2.14/user/articles/3d-file-viewer", - "/cn/enterprise/2.14/articles/about-archiving-repositories": "/cn/enterprise/2.14/user/articles/about-archiving-repositories", - "/cn/enterprise/2.14/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/cn/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/cn/enterprise/2.14/articles/about-automation-for-project-boards": "/cn/enterprise/2.14/user/articles/about-automation-for-project-boards", - "/cn/enterprise/2.14/articles/about-branch-restrictions": "/cn/enterprise/2.14/user/articles/about-branch-restrictions", - "/cn/enterprise/2.14/articles/about-branches": "/cn/enterprise/2.14/user/articles/about-branches", - "/cn/enterprise/2.14/articles/about-code-owners": "/cn/enterprise/2.14/user/articles/about-code-owners", - "/cn/enterprise/2.14/articles/about-collaborative-development-models": "/cn/enterprise/2.14/user/articles/about-collaborative-development-models", - "/cn/enterprise/2.14/articles/about-commit-signature-verification": "/cn/enterprise/2.14/user/articles/about-commit-signature-verification", - "/cn/enterprise/2.14/articles/about-comparing-branches-in-pull-requests": "/cn/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests", - "/cn/enterprise/2.14/articles/about-conversations-on-github": "/cn/enterprise/2.14/user/articles/about-conversations-on-github", - "/cn/enterprise/2.14/articles/about-duplicate-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.14/articles/about-email-notifications": "/cn/enterprise/2.14/user/articles/about-email-notifications", - "/cn/enterprise/2.14/articles/about-forks": "/cn/enterprise/2.14/user/articles/about-forks", - "/cn/enterprise/2.14/articles/about-git-large-file-storage": "/cn/enterprise/2.14/user/articles/about-git-large-file-storage", - "/cn/enterprise/2.14/articles/about-git-rebase": "/cn/enterprise/2.14/user/articles/about-git-rebase", - "/cn/enterprise/2.14/articles/about-git-subtree-merges": "/cn/enterprise/2.14/user/articles/about-git-subtree-merges", - "/cn/enterprise/2.14/articles/about-github-pages-and-jekyll": "/cn/enterprise/2.14/user/articles/about-github-pages-and-jekyll", - "/cn/enterprise/2.14/articles/about-issue-and-pull-request-templates": "/cn/enterprise/2.14/user/articles/about-issue-and-pull-request-templates", - "/cn/enterprise/2.14/articles/about-issues": "/cn/enterprise/2.14/user/articles/about-issues", - "/cn/enterprise/2.14/articles/about-jekyll-themes-on-github": "/cn/enterprise/2.14/user/articles/about-jekyll-themes-on-github", - "/cn/enterprise/2.14/articles/about-labels": "/cn/enterprise/2.14/user/articles/about-labels", - "/cn/enterprise/2.14/articles/about-merge-conflicts": "/cn/enterprise/2.14/user/articles/about-merge-conflicts", - "/cn/enterprise/2.14/articles/about-merge-methods-on-github": "/cn/enterprise/2.14/user/articles/about-merge-methods-on-github", - "/cn/enterprise/2.14/articles/about-milestones": "/cn/enterprise/2.14/user/articles/about-milestones", - "/cn/enterprise/2.14/articles/about-notifications": "/cn/enterprise/2.14/user/articles/about-notifications", - "/cn/enterprise/2.14/articles/about-organization-membership": "/cn/enterprise/2.14/user/articles/about-organization-membership", - "/cn/enterprise/2.14/articles/about-organizations": "/cn/enterprise/2.14/user/articles/about-organizations", - "/cn/enterprise/2.14/articles/about-project-boards": "/cn/enterprise/2.14/user/articles/about-project-boards", - "/cn/enterprise/2.14/articles/about-protected-branches": "/cn/enterprise/2.14/user/articles/about-protected-branches", - "/cn/enterprise/2.14/articles/about-pull-request-merges": "/cn/enterprise/2.14/user/articles/about-pull-request-merges", - "/cn/enterprise/2.14/articles/about-pull-request-reviews": "/cn/enterprise/2.14/user/articles/about-pull-request-reviews", - "/cn/enterprise/2.14/articles/about-pull-requests": "/cn/enterprise/2.14/user/articles/about-pull-requests", - "/cn/enterprise/2.14/articles/about-readmes": "/cn/enterprise/2.14/user/articles/about-readmes", - "/cn/enterprise/2.14/articles/about-releases": "/cn/enterprise/2.14/user/articles/about-releases", - "/cn/enterprise/2.14/articles/about-remote-repositories": "/cn/enterprise/2.14/user/articles/about-remote-repositories", - "/cn/enterprise/2.14/articles/about-repositories": "/cn/enterprise/2.14/user/articles/about-repositories", - "/cn/enterprise/2.14/articles/about-repository-graphs": "/cn/enterprise/2.14/user/articles/about-repository-graphs", - "/cn/enterprise/2.14/articles/about-repository-languages": "/cn/enterprise/2.14/user/articles/about-repository-languages", - "/cn/enterprise/2.14/articles/about-required-commit-signing": "/cn/enterprise/2.14/user/articles/about-required-commit-signing", - "/cn/enterprise/2.14/articles/about-required-reviews-for-pull-requests": "/cn/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.14/articles/about-required-status-checks": "/cn/enterprise/2.14/user/articles/about-required-status-checks", - "/cn/enterprise/2.14/articles/about-saved-replies": "/cn/enterprise/2.14/user/articles/about-saved-replies", - "/cn/enterprise/2.14/articles/about-searching-on-github": "/cn/enterprise/2.14/user/articles/about-searching-on-github", - "/cn/enterprise/2.14/articles/about-ssh": "/cn/enterprise/2.14/user/articles/about-ssh", - "/cn/enterprise/2.14/articles/about-status-checks": "/cn/enterprise/2.14/user/articles/about-status-checks", - "/cn/enterprise/2.14/articles/about-task-lists": "/cn/enterprise/2.14/user/articles/about-task-lists", - "/cn/enterprise/2.14/articles/about-team-discussions": "/cn/enterprise/2.14/user/articles/about-team-discussions", - "/cn/enterprise/2.14/articles/about-teams": "/cn/enterprise/2.14/user/articles/about-teams", - "/cn/enterprise/2.14/articles/about-two-factor-authentication": "/cn/enterprise/2.14/user/articles/about-two-factor-authentication", - "/cn/enterprise/2.14/articles/about-web-notifications": "/cn/enterprise/2.14/user/articles/about-web-notifications", - "/cn/enterprise/2.14/articles/about-webhooks": "/cn/enterprise/2.14/user/articles/about-webhooks", - "/cn/enterprise/2.14/articles/about-wikis": "/cn/enterprise/2.14/user/articles/about-wikis", - "/cn/enterprise/2.14/articles/about-writing-and-formatting-on-github": "/cn/enterprise/2.14/user/articles/about-writing-and-formatting-on-github", - "/cn/enterprise/2.14/articles/about-your-organization-dashboard": "/cn/enterprise/2.14/user/articles/about-your-organization-dashboard", - "/cn/enterprise/2.14/articles/about-your-organizations-news-feed": "/cn/enterprise/2.14/user/articles/about-your-organizations-news-feed", - "/cn/enterprise/2.14/articles/about-your-organizations-profile": "/cn/enterprise/2.14/user/articles/about-your-organizations-profile", - "/cn/enterprise/2.14/articles/about-your-personal-dashboard": "/cn/enterprise/2.14/user/articles/about-your-personal-dashboard", - "/cn/enterprise/2.14/articles/about-your-profile": "/cn/enterprise/2.14/user/articles/about-your-profile", - "/cn/enterprise/2.14/articles/access-permissions-on-github": "/cn/enterprise/2.14/user/articles/access-permissions-on-github", - "/cn/enterprise/2.14/articles/accessing-an-organization": "/cn/enterprise/2.14/user/articles/accessing-an-organization", - "/cn/enterprise/2.14/articles/accessing-basic-repository-data": "/cn/enterprise/2.14/user/articles/accessing-basic-repository-data", - "/cn/enterprise/2.14/articles/accessing-github-using-two-factor-authentication": "/cn/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication", - "/cn/enterprise/2.14/articles/accessing-your-notifications": "/cn/enterprise/2.14/user/articles/accessing-your-notifications", - "/cn/enterprise/2.14/articles/accessing-your-organizations-settings": "/cn/enterprise/2.14/user/articles/accessing-your-organizations-settings", - "/cn/enterprise/2.14/articles/adding-a-file-to-a-repository-using-the-command-line": "/cn/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/cn/enterprise/2.14/articles/adding-a-file-to-a-repository": "/cn/enterprise/2.14/user/articles/adding-a-file-to-a-repository", - "/cn/enterprise/2.14/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/cn/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/cn/enterprise/2.14/articles/adding-a-license-to-a-repository": "/cn/enterprise/2.14/user/articles/adding-a-license-to-a-repository", - "/cn/enterprise/2.14/articles/adding-a-new-gpg-key-to-your-github-account": "/cn/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/cn/enterprise/2.14/articles/adding-a-new-ssh-key-to-your-github-account": "/cn/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/cn/enterprise/2.14/articles/adding-a-remote": "/cn/enterprise/2.14/user/articles/adding-a-remote", - "/cn/enterprise/2.14/articles/adding-an-email-address-to-your-github-account": "/cn/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account", - "/cn/enterprise/2.14/articles/adding-an-existing-project-to-github-using-the-command-line": "/cn/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/cn/enterprise/2.14/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/cn/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/cn/enterprise/2.14/articles/adding-issues-and-pull-requests-to-a-project-board": "/cn/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/cn/enterprise/2.14/articles/adding-jekyll-plugins-to-a-github-pages-site": "/cn/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/cn/enterprise/2.14/articles/adding-notes-to-a-project-board": "/cn/enterprise/2.14/user/articles/adding-notes-to-a-project-board", - "/cn/enterprise/2.14/articles/adding-or-editing-wiki-pages": "/cn/enterprise/2.14/user/articles/adding-or-editing-wiki-pages", - "/cn/enterprise/2.14/articles/adding-organization-members-to-a-team": "/cn/enterprise/2.14/user/articles/adding-organization-members-to-a-team", - "/cn/enterprise/2.14/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/cn/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/cn/enterprise/2.14/articles/adding-people-to-your-organization": "/cn/enterprise/2.14/user/articles/adding-people-to-your-organization", - "/cn/enterprise/2.14/articles/adding-support-resources-to-your-project": "/cn/enterprise/2.14/user/articles/adding-support-resources-to-your-project", - "/cn/enterprise/2.14/articles/additional-customizations-for-github-pages": "/cn/enterprise/2.14/user/articles/additional-customizations-for-github-pages", - "/cn/enterprise/2.14/articles/addressing-merge-conflicts": "/cn/enterprise/2.14/user/articles/addressing-merge-conflicts", - "/cn/enterprise/2.14/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.14/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/cn/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/cn/enterprise/2.14/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/cn/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/cn/enterprise/2.14/articles/analyzing-changes-to-a-repositorys-content": "/cn/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content", - "/cn/enterprise/2.14/articles/applying-labels-to-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/approving-a-pull-request-with-required-reviews": "/cn/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews", - "/cn/enterprise/2.14/articles/archiving-a-github-repository": "/cn/enterprise/2.14/user/articles/archiving-a-github-repository", - "/cn/enterprise/2.14/articles/archiving-repositories": "/cn/enterprise/2.14/user/articles/archiving-repositories", - "/cn/enterprise/2.14/articles/assigning-issues-and-pull-requests-to-other-github-users": "/cn/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/cn/enterprise/2.14/articles/associating-an-email-with-your-gpg-key": "/cn/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key", - "/cn/enterprise/2.14/articles/associating-milestones-with-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/associating-text-editors-with-git": "/cn/enterprise/2.14/user/articles/associating-text-editors-with-git", - "/cn/enterprise/2.14/articles/authorizing-oauth-apps": "/cn/enterprise/2.14/user/articles/authorizing-oauth-apps", - "/cn/enterprise/2.14/articles/autolinked-references-and-urls": "/cn/enterprise/2.14/user/articles/autolinked-references-and-urls", - "/cn/enterprise/2.14/articles/backing-up-a-repository": "/cn/enterprise/2.14/user/articles/backing-up-a-repository", - "/cn/enterprise/2.14/articles/basic-writing-and-formatting-syntax": "/cn/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax", - "/cn/enterprise/2.14/articles/be-social": "/cn/enterprise/2.14/user/articles/be-social", - "/cn/enterprise/2.14/articles/caching-your-github-password-in-git": "/cn/enterprise/2.14/user/articles/caching-your-github-password-in-git", - "/cn/enterprise/2.14/articles/changing-a-commit-message": "/cn/enterprise/2.14/user/articles/changing-a-commit-message", - "/cn/enterprise/2.14/articles/changing-a-persons-role-to-owner": "/cn/enterprise/2.14/user/articles/changing-a-persons-role-to-owner", - "/cn/enterprise/2.14/articles/changing-a-remotes-url": "/cn/enterprise/2.14/user/articles/changing-a-remotes-url", - "/cn/enterprise/2.14/articles/changing-access-permissions-for-wikis": "/cn/enterprise/2.14/user/articles/changing-access-permissions-for-wikis", - "/cn/enterprise/2.14/articles/changing-author-info": "/cn/enterprise/2.14/user/articles/changing-author-info", - "/cn/enterprise/2.14/articles/changing-project-board-visibility": "/cn/enterprise/2.14/user/articles/changing-project-board-visibility", - "/cn/enterprise/2.14/articles/changing-team-visibility": "/cn/enterprise/2.14/user/articles/changing-team-visibility", - "/cn/enterprise/2.14/articles/changing-the-base-branch-of-a-pull-request": "/cn/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request", - "/cn/enterprise/2.14/articles/changing-your-github-username": "/cn/enterprise/2.14/user/articles/changing-your-github-username", - "/cn/enterprise/2.14/articles/changing-your-primary-email-address": "/cn/enterprise/2.14/user/articles/changing-your-primary-email-address", - "/cn/enterprise/2.14/articles/checking-for-existing-gpg-keys": "/cn/enterprise/2.14/user/articles/checking-for-existing-gpg-keys", - "/cn/enterprise/2.14/articles/checking-for-existing-ssh-keys": "/cn/enterprise/2.14/user/articles/checking-for-existing-ssh-keys", - "/cn/enterprise/2.14/articles/checking-out-pull-requests-locally": "/cn/enterprise/2.14/user/articles/checking-out-pull-requests-locally", - "/cn/enterprise/2.14/articles/checking-your-commit-and-tag-signature-verification-status": "/cn/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/cn/enterprise/2.14/articles/choosing-the-delivery-method-for-your-notifications": "/cn/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications", - "/cn/enterprise/2.14/articles/classifying-your-repository-with-topics": "/cn/enterprise/2.14/user/articles/classifying-your-repository-with-topics", - "/cn/enterprise/2.14/articles/cloning-a-repository-from-github": "/cn/enterprise/2.14/user/articles/cloning-a-repository-from-github", - "/cn/enterprise/2.14/articles/cloning-a-repository": "/cn/enterprise/2.14/user/articles/cloning-a-repository", - "/cn/enterprise/2.14/articles/closing-a-project-board": "/cn/enterprise/2.14/user/articles/closing-a-project-board", - "/cn/enterprise/2.14/articles/closing-a-pull-request": "/cn/enterprise/2.14/user/articles/closing-a-pull-request", - "/cn/enterprise/2.14/articles/closing-issues-using-keywords": "/cn/enterprise/2.14/user/articles/closing-issues-using-keywords", - "/cn/enterprise/2.14/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/cn/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/cn/enterprise/2.14/articles/collaborating-with-groups-in-organizations": "/cn/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations", - "/cn/enterprise/2.14/articles/collaborating-with-your-team": "/cn/enterprise/2.14/user/articles/collaborating-with-your-team", - "/cn/enterprise/2.14/articles/collaboration-with-git-large-file-storage": "/cn/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage", - "/cn/enterprise/2.14/articles/commenting-on-a-pull-request": "/cn/enterprise/2.14/user/articles/commenting-on-a-pull-request", - "/cn/enterprise/2.14/articles/commit-branch-and-tag-labels": "/cn/enterprise/2.14/user/articles/commit-branch-and-tag-labels", - "/cn/enterprise/2.14/articles/commit-exists-on-github-but-not-in-my-local-clone": "/cn/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/cn/enterprise/2.14/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.14/articles/comparing-commits-across-time": "/cn/enterprise/2.14/user/articles/comparing-commits-across-time", - "/cn/enterprise/2.14/articles/conditions-for-large-files": "/cn/enterprise/2.14/user/articles/conditions-for-large-files", - "/cn/enterprise/2.14/articles/configuring-a-publishing-source-for-github-pages": "/cn/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages", - "/cn/enterprise/2.14/articles/configuring-a-remote-for-a-fork": "/cn/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork", - "/cn/enterprise/2.14/articles/configuring-automation-for-project-boards": "/cn/enterprise/2.14/user/articles/configuring-automation-for-project-boards", - "/cn/enterprise/2.14/articles/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.14/articles/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.14/articles/configuring-git-large-file-storage": "/cn/enterprise/2.14/user/articles/configuring-git-large-file-storage", - "/cn/enterprise/2.14/articles/configuring-git-to-handle-line-endings": "/cn/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings", - "/cn/enterprise/2.14/articles/configuring-jekyll-plugins": "/cn/enterprise/2.14/user/articles/configuring-jekyll-plugins", - "/cn/enterprise/2.14/articles/configuring-jekyll": "/cn/enterprise/2.14/user/articles/configuring-jekyll", - "/cn/enterprise/2.14/articles/configuring-protected-branches": "/cn/enterprise/2.14/user/articles/configuring-protected-branches", - "/cn/enterprise/2.14/articles/configuring-pull-request-merges": "/cn/enterprise/2.14/user/articles/configuring-pull-request-merges", - "/cn/enterprise/2.14/articles/configuring-two-factor-authentication-recovery-methods": "/cn/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods", - "/cn/enterprise/2.14/articles/configuring-two-factor-authentication": "/cn/enterprise/2.14/user/articles/configuring-two-factor-authentication", - "/cn/enterprise/2.14/articles/connecting-to-github-with-ssh": "/cn/enterprise/2.14/user/articles/connecting-to-github-with-ssh", - "/cn/enterprise/2.14/articles/connecting-with-third-party-applications": "/cn/enterprise/2.14/user/articles/connecting-with-third-party-applications", - "/cn/enterprise/2.14/articles/converting-a-user-into-an-organization": "/cn/enterprise/2.14/user/articles/converting-a-user-into-an-organization", - "/cn/enterprise/2.14/articles/converting-an-organization-into-a-user": "/cn/enterprise/2.14/user/articles/converting-an-organization-into-a-user", - "/cn/enterprise/2.14/articles/converting-an-organization-member-to-an-outside-collaborator": "/cn/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/cn/enterprise/2.14/articles/converting-an-outside-collaborator-to-an-organization-member": "/cn/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/cn/enterprise/2.14/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": "/cn/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions", - "/cn/enterprise/2.14/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": "/cn/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions", - "/cn/enterprise/2.14/articles/create-a-repo": "/cn/enterprise/2.14/user/articles/create-a-repo", - "/cn/enterprise/2.14/articles/creating-a-commit-with-multiple-authors": "/cn/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors", - "/cn/enterprise/2.14/articles/creating-a-custom-404-page-for-your-github-pages-site": "/cn/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/cn/enterprise/2.14/articles/creating-a-footer-or-sidebar-for-your-wiki": "/cn/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/cn/enterprise/2.14/articles/creating-a-label": "/cn/enterprise/2.14/user/articles/creating-a-label", - "/cn/enterprise/2.14/articles/creating-a-new-organization-from-scratch": "/cn/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch", - "/cn/enterprise/2.14/articles/creating-a-new-repository": "/cn/enterprise/2.14/user/articles/creating-a-new-repository", - "/cn/enterprise/2.14/articles/creating-a-permanent-link-to-a-code-snippet": "/cn/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/cn/enterprise/2.14/articles/creating-a-personal-access-token-for-the-command-line": "/cn/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line", - "/cn/enterprise/2.14/articles/creating-a-project-board": "/cn/enterprise/2.14/user/articles/creating-a-project-board", - "/cn/enterprise/2.14/articles/creating-a-pull-request-from-a-fork": "/cn/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork", - "/cn/enterprise/2.14/articles/creating-a-pull-request-template-for-your-repository": "/cn/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository", - "/cn/enterprise/2.14/articles/creating-a-pull-request": "/cn/enterprise/2.14/user/articles/creating-a-pull-request", - "/cn/enterprise/2.14/articles/creating-a-repository-on-github": "/cn/enterprise/2.14/user/articles/creating-a-repository-on-github", - "/cn/enterprise/2.14/articles/creating-a-saved-reply": "/cn/enterprise/2.14/user/articles/creating-a-saved-reply", - "/cn/enterprise/2.14/articles/creating-a-strong-password": "/cn/enterprise/2.14/user/articles/creating-a-strong-password", - "/cn/enterprise/2.14/articles/creating-a-team-discussion": "/cn/enterprise/2.14/user/articles/creating-a-team-discussion", - "/cn/enterprise/2.14/articles/creating-a-team": "/cn/enterprise/2.14/user/articles/creating-a-team", - "/cn/enterprise/2.14/articles/creating-an-issue": "/cn/enterprise/2.14/user/articles/creating-an-issue", - "/cn/enterprise/2.14/articles/creating-an-issues-only-repository": "/cn/enterprise/2.14/user/articles/creating-an-issues-only-repository", - "/cn/enterprise/2.14/articles/creating-and-deleting-branches-within-your-repository": "/cn/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository", - "/cn/enterprise/2.14/articles/creating-and-editing-commits": "/cn/enterprise/2.14/user/articles/creating-and-editing-commits", - "/cn/enterprise/2.14/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/creating-and-highlighting-code-blocks": "/cn/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks", - "/cn/enterprise/2.14/articles/creating-gists": "/cn/enterprise/2.14/user/articles/creating-gists", - "/cn/enterprise/2.14/articles/creating-issue-templates-for-your-repository": "/cn/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository", - "/cn/enterprise/2.14/articles/creating-new-files": "/cn/enterprise/2.14/user/articles/creating-new-files", - "/cn/enterprise/2.14/articles/creating-pages-with-the-automatic-generator": "/cn/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator", - "/cn/enterprise/2.14/articles/creating-project-pages-using-the-command-line": "/cn/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line", - "/cn/enterprise/2.14/articles/creating-releases": "/cn/enterprise/2.14/user/articles/creating-releases", - "/cn/enterprise/2.14/articles/customizing-css-and-html-in-your-jekyll-theme": "/cn/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/cn/enterprise/2.14/articles/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.14/articles/customizing-your-profile": "/cn/enterprise/2.14/user/articles/customizing-your-profile", - "/cn/enterprise/2.14/articles/dealing-with-non-fast-forward-errors": "/cn/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors", - "/cn/enterprise/2.14/articles/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.14/articles/deleting-a-label": "/cn/enterprise/2.14/user/articles/deleting-a-label", - "/cn/enterprise/2.14/articles/deleting-a-project-board": "/cn/enterprise/2.14/user/articles/deleting-a-project-board", - "/cn/enterprise/2.14/articles/deleting-a-repository": "/cn/enterprise/2.14/user/articles/deleting-a-repository", - "/cn/enterprise/2.14/articles/deleting-a-saved-reply": "/cn/enterprise/2.14/user/articles/deleting-a-saved-reply", - "/cn/enterprise/2.14/articles/deleting-a-team": "/cn/enterprise/2.14/user/articles/deleting-a-team", - "/cn/enterprise/2.14/articles/deleting-an-organization-account": "/cn/enterprise/2.14/user/articles/deleting-an-organization-account", - "/cn/enterprise/2.14/articles/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.14/articles/deleting-files": "/cn/enterprise/2.14/user/articles/deleting-files", - "/cn/enterprise/2.14/articles/deleting-your-user-account": "/cn/enterprise/2.14/user/articles/deleting-your-user-account", - "/cn/enterprise/2.14/articles/differences-between-commit-views": "/cn/enterprise/2.14/user/articles/differences-between-commit-views", - "/cn/enterprise/2.14/articles/disabling-issues": "/cn/enterprise/2.14/user/articles/disabling-issues", - "/cn/enterprise/2.14/articles/disabling-project-boards-in-a-repository": "/cn/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository", - "/cn/enterprise/2.14/articles/disabling-project-boards-in-your-organization": "/cn/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization", - "/cn/enterprise/2.14/articles/disabling-team-discussions-for-your-organization": "/cn/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization", - "/cn/enterprise/2.14/articles/disabling-two-factor-authentication-for-your-personal-account": "/cn/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/cn/enterprise/2.14/articles/disabling-wikis": "/cn/enterprise/2.14/user/articles/disabling-wikis", - "/cn/enterprise/2.14/articles/dismissing-a-pull-request-review": "/cn/enterprise/2.14/user/articles/dismissing-a-pull-request-review", - "/cn/enterprise/2.14/articles/distributing-large-binaries": "/cn/enterprise/2.14/user/articles/distributing-large-binaries", - "/cn/enterprise/2.14/articles/documenting-your-project-with-wikis": "/cn/enterprise/2.14/user/articles/documenting-your-project-with-wikis", - "/cn/enterprise/2.14/articles/duplicating-a-repository": "/cn/enterprise/2.14/user/articles/duplicating-a-repository", - "/cn/enterprise/2.14/articles/editing-a-label": "/cn/enterprise/2.14/user/articles/editing-a-label", - "/cn/enterprise/2.14/articles/editing-a-project-board": "/cn/enterprise/2.14/user/articles/editing-a-project-board", - "/cn/enterprise/2.14/articles/editing-a-saved-reply": "/cn/enterprise/2.14/user/articles/editing-a-saved-reply", - "/cn/enterprise/2.14/articles/editing-and-deleting-releases": "/cn/enterprise/2.14/user/articles/editing-and-deleting-releases", - "/cn/enterprise/2.14/articles/editing-and-sharing-content-with-gists": "/cn/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists", - "/cn/enterprise/2.14/articles/editing-files-in-another-users-repository": "/cn/enterprise/2.14/user/articles/editing-files-in-another-users-repository", - "/cn/enterprise/2.14/articles/editing-files-in-your-repository": "/cn/enterprise/2.14/user/articles/editing-files-in-your-repository", - "/cn/enterprise/2.14/articles/editing-or-deleting-a-team-discussion": "/cn/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion", - "/cn/enterprise/2.14/articles/editing-wiki-content": "/cn/enterprise/2.14/user/articles/editing-wiki-content", - "/cn/enterprise/2.14/articles/emoji-on-github-pages": "/cn/enterprise/2.14/user/articles/emoji-on-github-pages", - "/cn/enterprise/2.14/articles/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.14/articles/enabling-branch-restrictions": "/cn/enterprise/2.14/user/articles/enabling-branch-restrictions", - "/cn/enterprise/2.14/articles/enabling-required-commit-signing": "/cn/enterprise/2.14/user/articles/enabling-required-commit-signing", - "/cn/enterprise/2.14/articles/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.14/articles/enabling-required-status-checks": "/cn/enterprise/2.14/user/articles/enabling-required-status-checks", - "/cn/enterprise/2.14/articles/error-agent-admitted-failure-to-sign": "/cn/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign", - "/cn/enterprise/2.14/articles/error-bad-file-number": "/cn/enterprise/2.14/user/articles/error-bad-file-number", - "/cn/enterprise/2.14/articles/error-key-already-in-use": "/cn/enterprise/2.14/user/articles/error-key-already-in-use", - "/cn/enterprise/2.14/articles/error-permission-denied-publickey": "/cn/enterprise/2.14/user/articles/error-permission-denied-publickey", - "/cn/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-other-user": "/cn/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/cn/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-userother-repo": "/cn/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/cn/enterprise/2.14/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/cn/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/cn/enterprise/2.14/articles/error-repository-not-found": "/cn/enterprise/2.14/user/articles/error-repository-not-found", - "/cn/enterprise/2.14/articles/error-ssh-add-illegal-option----k": "/cn/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k", - "/cn/enterprise/2.14/articles/error-were-doing-an-ssh-key-audit": "/cn/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit", - "/cn/enterprise/2.14/articles/exploring-projects-on-github": "/cn/enterprise/2.14/user/articles/exploring-projects-on-github", - "/cn/enterprise/2.14/articles/file-attachments-on-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/files-that-start-with-an-underscore-are-missing": "/cn/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing", - "/cn/enterprise/2.14/articles/filtering-cards-on-a-project-board": "/cn/enterprise/2.14/user/articles/filtering-cards-on-a-project-board", - "/cn/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-assignees": "/cn/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/cn/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-labels": "/cn/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels", - "/cn/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-milestone": "/cn/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/cn/enterprise/2.14/articles/filtering-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/filtering-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/filtering-pull-requests-by-review-status": "/cn/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status", - "/cn/enterprise/2.14/articles/finding-changed-methods-and-functions-in-a-pull-request": "/cn/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/cn/enterprise/2.14/articles/finding-files-on-github": "/cn/enterprise/2.14/user/articles/finding-files-on-github", - "/cn/enterprise/2.14/articles/finding-information-in-a-repository": "/cn/enterprise/2.14/user/articles/finding-information-in-a-repository", - "/cn/enterprise/2.14/articles/following-people": "/cn/enterprise/2.14/user/articles/following-people", - "/cn/enterprise/2.14/articles/fork-a-repo": "/cn/enterprise/2.14/user/articles/fork-a-repo", - "/cn/enterprise/2.14/articles/forking-and-cloning-gists": "/cn/enterprise/2.14/user/articles/forking-and-cloning-gists", - "/cn/enterprise/2.14/articles/further-reading-on-github-pages": "/cn/enterprise/2.14/user/articles/further-reading-on-github-pages", - "/cn/enterprise/2.14/articles/generating-a-new-gpg-key": "/cn/enterprise/2.14/user/articles/generating-a-new-gpg-key", - "/cn/enterprise/2.14/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/cn/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/cn/enterprise/2.14/articles/generic-jekyll-build-failures": "/cn/enterprise/2.14/user/articles/generic-jekyll-build-failures", - "/cn/enterprise/2.14/articles/getting-changes-from-a-remote-repository": "/cn/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository", - "/cn/enterprise/2.14/articles/getting-permanent-links-to-files": "/cn/enterprise/2.14/user/articles/getting-permanent-links-to-files", - "/cn/enterprise/2.14/articles/getting-started-with-git-and-github": "/cn/enterprise/2.14/user/articles/getting-started-with-git-and-github", - "/cn/enterprise/2.14/articles/getting-started-with-notifications": "/cn/enterprise/2.14/user/articles/getting-started-with-notifications", - "/cn/enterprise/2.14/articles/getting-started-with-searching-on-github": "/cn/enterprise/2.14/user/articles/getting-started-with-searching-on-github", - "/cn/enterprise/2.14/articles/getting-started-with-the-api": "/cn/enterprise/2.14/user/articles/getting-started-with-the-api", - "/cn/enterprise/2.14/articles/getting-started-with-writing-and-formatting-on-github": "/cn/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github", - "/cn/enterprise/2.14/articles/getting-the-download-count-for-your-releases": "/cn/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases", - "/cn/enterprise/2.14/articles/git-and-github-learning-resources": "/cn/enterprise/2.14/user/articles/git-and-github-learning-resources", - "/cn/enterprise/2.14/articles/git-automation-with-oauth-tokens": "/cn/enterprise/2.14/user/articles/git-automation-with-oauth-tokens", - "/cn/enterprise/2.14/articles/git-cheatsheet": "/cn/enterprise/2.14/user/articles/git-cheatsheet", - "/cn/enterprise/2.14/articles/git-workflows": "/cn/enterprise/2.14/user/articles/git-workflows", - "/cn/enterprise/2.14/articles/github-flow": "/cn/enterprise/2.14/user/articles/github-flow", - "/cn/enterprise/2.14/articles/github-glossary": "/cn/enterprise/2.14/user/articles/github-glossary", - "/cn/enterprise/2.14/articles/giving-team-maintainer-permissions-to-an-organization-member": "/cn/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/cn/enterprise/2.14/articles/https-cloning-errors": "/cn/enterprise/2.14/user/articles/https-cloning-errors", - "/cn/enterprise/2.14/articles/ignoring-files": "/cn/enterprise/2.14/user/articles/ignoring-files", - "/cn/enterprise/2.14/articles/importing-a-git-repository-using-the-command-line": "/cn/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line", - "/cn/enterprise/2.14/articles/importing-source-code-to-github": "/cn/enterprise/2.14/user/articles/importing-source-code-to-github", - "/cn/enterprise/2.14/articles/incorporating-changes-from-a-pull-request": "/cn/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request", - "/cn/enterprise/2.14/articles/initializing-an-empty-repository-with-a-readme": "/cn/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme", - "/cn/enterprise/2.14/articles/installing-git-large-file-storage": "/cn/enterprise/2.14/user/articles/installing-git-large-file-storage", - "/cn/enterprise/2.14/articles/integrating-jira-with-your-organization-project-board": "/cn/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board", - "/cn/enterprise/2.14/articles/integrating-jira-with-your-personal-projects": "/cn/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects", - "/cn/enterprise/2.14/articles/inviting-collaborators-to-a-personal-repository": "/cn/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository", - "/cn/enterprise/2.14/articles/keeping-your-account-and-data-secure": "/cn/enterprise/2.14/user/articles/keeping-your-account-and-data-secure", - "/cn/enterprise/2.14/articles/keeping-your-organization-secure": "/cn/enterprise/2.14/user/articles/keeping-your-organization-secure", - "/cn/enterprise/2.14/articles/keyboard-shortcuts": "/cn/enterprise/2.14/user/articles/keyboard-shortcuts", - "/cn/enterprise/2.14/articles/labeling-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/labeling-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/learning-about-git": "/cn/enterprise/2.14/user/articles/learning-about-git", - "/cn/enterprise/2.14/articles/learning-about-github": "/cn/enterprise/2.14/user/articles/learning-about-github", - "/cn/enterprise/2.14/articles/licensing-a-repository": "/cn/enterprise/2.14/user/articles/licensing-a-repository", - "/cn/enterprise/2.14/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/cn/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/cn/enterprise/2.14/articles/linking-to-releases": "/cn/enterprise/2.14/user/articles/linking-to-releases", - "/cn/enterprise/2.14/articles/listing-the-forks-of-a-repository": "/cn/enterprise/2.14/user/articles/listing-the-forks-of-a-repository", - "/cn/enterprise/2.14/articles/listing-the-repositories-youre-watching": "/cn/enterprise/2.14/user/articles/listing-the-repositories-youre-watching", - "/cn/enterprise/2.14/articles/locking-conversations": "/cn/enterprise/2.14/user/articles/locking-conversations", - "/cn/enterprise/2.14/articles/managing-access-to-a-project-board-for-organization-members": "/cn/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members", - "/cn/enterprise/2.14/articles/managing-access-to-your-organizations-project-boards": "/cn/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards", - "/cn/enterprise/2.14/articles/managing-access-to-your-organizations-repositories": "/cn/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories", - "/cn/enterprise/2.14/articles/managing-access-to-your-personal-repositories": "/cn/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories", - "/cn/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-project-board": "/cn/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/cn/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-repository": "/cn/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/cn/enterprise/2.14/articles/managing-branches-in-your-repository": "/cn/enterprise/2.14/user/articles/managing-branches-in-your-repository", - "/cn/enterprise/2.14/articles/managing-commit-signature-verification": "/cn/enterprise/2.14/user/articles/managing-commit-signature-verification", - "/cn/enterprise/2.14/articles/managing-contribution-graphs-on-your-profile": "/cn/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile", - "/cn/enterprise/2.14/articles/managing-disruptive-comments": "/cn/enterprise/2.14/user/articles/managing-disruptive-comments", - "/cn/enterprise/2.14/articles/managing-email-preferences": "/cn/enterprise/2.14/user/articles/managing-email-preferences", - "/cn/enterprise/2.14/articles/managing-files-on-github": "/cn/enterprise/2.14/user/articles/managing-files-on-github", - "/cn/enterprise/2.14/articles/managing-files-using-the-command-line": "/cn/enterprise/2.14/user/articles/managing-files-using-the-command-line", - "/cn/enterprise/2.14/articles/managing-membership-in-your-organization": "/cn/enterprise/2.14/user/articles/managing-membership-in-your-organization", - "/cn/enterprise/2.14/articles/managing-organization-settings": "/cn/enterprise/2.14/user/articles/managing-organization-settings", - "/cn/enterprise/2.14/articles/managing-peoples-access-to-your-organization-with-roles": "/cn/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/cn/enterprise/2.14/articles/managing-project-boards": "/cn/enterprise/2.14/user/articles/managing-project-boards", - "/cn/enterprise/2.14/articles/managing-releases-in-a-repository": "/cn/enterprise/2.14/user/articles/managing-releases-in-a-repository", - "/cn/enterprise/2.14/articles/managing-remote-repositories": "/cn/enterprise/2.14/user/articles/managing-remote-repositories", - "/cn/enterprise/2.14/articles/managing-repository-settings": "/cn/enterprise/2.14/user/articles/managing-repository-settings", - "/cn/enterprise/2.14/articles/managing-team-access-to-an-organization-project-board": "/cn/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board", - "/cn/enterprise/2.14/articles/managing-team-access-to-an-organization-repository": "/cn/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository", - "/cn/enterprise/2.14/articles/managing-user-account-settings": "/cn/enterprise/2.14/user/articles/managing-user-account-settings", - "/cn/enterprise/2.14/articles/managing-your-membership-in-organizations": "/cn/enterprise/2.14/user/articles/managing-your-membership-in-organizations", - "/cn/enterprise/2.14/articles/managing-your-notifications": "/cn/enterprise/2.14/user/articles/managing-your-notifications", - "/cn/enterprise/2.14/articles/managing-your-work-with-issues": "/cn/enterprise/2.14/user/articles/managing-your-work-with-issues", - "/cn/enterprise/2.14/articles/manually-creating-a-single-issue-template-for-your-repository": "/cn/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/cn/enterprise/2.14/articles/mapping-geojson-files-on-github": "/cn/enterprise/2.14/user/articles/mapping-geojson-files-on-github", - "/cn/enterprise/2.14/articles/marking-notifications-as-read": "/cn/enterprise/2.14/user/articles/marking-notifications-as-read", - "/cn/enterprise/2.14/articles/mentions-on-github-pages": "/cn/enterprise/2.14/user/articles/mentions-on-github-pages", - "/cn/enterprise/2.14/articles/merging-a-pull-request": "/cn/enterprise/2.14/user/articles/merging-a-pull-request", - "/cn/enterprise/2.14/articles/merging-an-upstream-repository-into-your-fork": "/cn/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork", - "/cn/enterprise/2.14/articles/migrating-your-organization-to-improved-organization-permissions": "/cn/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions", - "/cn/enterprise/2.14/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": "/cn/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions", - "/cn/enterprise/2.14/articles/mime-types-on-github-pages": "/cn/enterprise/2.14/user/articles/mime-types-on-github-pages", - "/cn/enterprise/2.14/articles/moderating-comments-and-conversations": "/cn/enterprise/2.14/user/articles/moderating-comments-and-conversations", - "/cn/enterprise/2.14/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/cn/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/cn/enterprise/2.14/articles/moving-a-file-to-a-new-location-using-the-command-line": "/cn/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/cn/enterprise/2.14/articles/moving-a-file-to-a-new-location": "/cn/enterprise/2.14/user/articles/moving-a-file-to-a-new-location", - "/cn/enterprise/2.14/articles/moving-a-team-in-your-organizations-hierarchy": "/cn/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/cn/enterprise/2.14/articles/opening-an-issue-from-code": "/cn/enterprise/2.14/user/articles/opening-an-issue-from-code", - "/cn/enterprise/2.14/articles/organizing-information-with-tables": "/cn/enterprise/2.14/user/articles/organizing-information-with-tables", - "/cn/enterprise/2.14/articles/organizing-members-into-teams": "/cn/enterprise/2.14/user/articles/organizing-members-into-teams", - "/cn/enterprise/2.14/articles/page-build-failed-config-file-error": "/cn/enterprise/2.14/user/articles/page-build-failed-config-file-error", - "/cn/enterprise/2.14/articles/page-build-failed-date-is-not-a-valid-datetime": "/cn/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/cn/enterprise/2.14/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/cn/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/cn/enterprise/2.14/articles/page-build-failed-file-is-a-symlink": "/cn/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink", - "/cn/enterprise/2.14/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/cn/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/cn/enterprise/2.14/articles/page-build-failed-invalid-highlighter-language": "/cn/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language", - "/cn/enterprise/2.14/articles/page-build-failed-invalid-post-date": "/cn/enterprise/2.14/user/articles/page-build-failed-invalid-post-date", - "/cn/enterprise/2.14/articles/page-build-failed-invalid-sass-or-scss": "/cn/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss", - "/cn/enterprise/2.14/articles/page-build-failed-invalid-submodule": "/cn/enterprise/2.14/user/articles/page-build-failed-invalid-submodule", - "/cn/enterprise/2.14/articles/page-build-failed-invalid-yaml-in-data-file": "/cn/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/cn/enterprise/2.14/articles/page-build-failed-markdown-errors": "/cn/enterprise/2.14/user/articles/page-build-failed-markdown-errors", - "/cn/enterprise/2.14/articles/page-build-failed-missing-docs-folder": "/cn/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder", - "/cn/enterprise/2.14/articles/page-build-failed-missing-submodule": "/cn/enterprise/2.14/user/articles/page-build-failed-missing-submodule", - "/cn/enterprise/2.14/articles/page-build-failed-relative-permalinks-configured": "/cn/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured", - "/cn/enterprise/2.14/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/cn/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/cn/enterprise/2.14/articles/page-build-failed-syntax-error-in-for-loop": "/cn/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop", - "/cn/enterprise/2.14/articles/page-build-failed-tag-not-properly-closed": "/cn/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed", - "/cn/enterprise/2.14/articles/page-build-failed-tag-not-properly-terminated": "/cn/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated", - "/cn/enterprise/2.14/articles/page-build-failed-unknown-tag-error": "/cn/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error", - "/cn/enterprise/2.14/articles/permission-levels-for-a-user-account-repository": "/cn/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository", - "/cn/enterprise/2.14/articles/permission-levels-for-an-organization": "/cn/enterprise/2.14/user/articles/permission-levels-for-an-organization", - "/cn/enterprise/2.14/articles/personalizing-your-profile": "/cn/enterprise/2.14/user/articles/personalizing-your-profile", - "/cn/enterprise/2.14/articles/pinning-a-team-discussion": "/cn/enterprise/2.14/user/articles/pinning-a-team-discussion", - "/cn/enterprise/2.14/articles/pinning-items-to-your-profile": "/cn/enterprise/2.14/user/articles/pinning-items-to-your-profile", - "/cn/enterprise/2.14/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/cn/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.14/articles/preventing-unauthorized-access": "/cn/enterprise/2.14/user/articles/preventing-unauthorized-access", - "/cn/enterprise/2.14/articles/project-board-permissions-for-an-organization": "/cn/enterprise/2.14/user/articles/project-board-permissions-for-an-organization", - "/cn/enterprise/2.14/articles/proposing-changes-to-your-work-with-pull-requests": "/cn/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/cn/enterprise/2.14/articles/publicizing-or-hiding-organization-membership": "/cn/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership", - "/cn/enterprise/2.14/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/cn/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/cn/enterprise/2.14/articles/pushing-commits-to-a-remote-repository": "/cn/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository", - "/cn/enterprise/2.14/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/cn/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/cn/enterprise/2.14/articles/recovering-your-ssh-key-passphrase": "/cn/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase", - "/cn/enterprise/2.14/articles/redirects-on-github-pages": "/cn/enterprise/2.14/user/articles/redirects-on-github-pages", - "/cn/enterprise/2.14/articles/reinstating-a-former-member-of-your-organization": "/cn/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization", - "/cn/enterprise/2.14/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/cn/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/cn/enterprise/2.14/articles/remembering-your-github-username-or-email": "/cn/enterprise/2.14/user/articles/remembering-your-github-username-or-email", - "/cn/enterprise/2.14/articles/removing-a-collaborator-from-a-personal-repository": "/cn/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository", - "/cn/enterprise/2.14/articles/removing-a-member-from-your-organization": "/cn/enterprise/2.14/user/articles/removing-a-member-from-your-organization", - "/cn/enterprise/2.14/articles/removing-a-remote": "/cn/enterprise/2.14/user/articles/removing-a-remote", - "/cn/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/cn/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/cn/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-repository": "/cn/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/cn/enterprise/2.14/articles/removing-files-from-a-repositorys-history": "/cn/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history", - "/cn/enterprise/2.14/articles/removing-files-from-git-large-file-storage": "/cn/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage", - "/cn/enterprise/2.14/articles/removing-organization-members-from-a-team": "/cn/enterprise/2.14/user/articles/removing-organization-members-from-a-team", - "/cn/enterprise/2.14/articles/removing-sensitive-data-from-a-repository": "/cn/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository", - "/cn/enterprise/2.14/articles/removing-yourself-from-a-collaborators-repository": "/cn/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository", - "/cn/enterprise/2.14/articles/removing-yourself-from-an-organization": "/cn/enterprise/2.14/user/articles/removing-yourself-from-an-organization", - "/cn/enterprise/2.14/articles/renaming-a-file-using-the-command-line": "/cn/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line", - "/cn/enterprise/2.14/articles/renaming-a-file": "/cn/enterprise/2.14/user/articles/renaming-a-file", - "/cn/enterprise/2.14/articles/renaming-a-remote": "/cn/enterprise/2.14/user/articles/renaming-a-remote", - "/cn/enterprise/2.14/articles/renaming-a-repository": "/cn/enterprise/2.14/user/articles/renaming-a-repository", - "/cn/enterprise/2.14/articles/renaming-a-team": "/cn/enterprise/2.14/user/articles/renaming-a-team", - "/cn/enterprise/2.14/articles/renaming-an-organization": "/cn/enterprise/2.14/user/articles/renaming-an-organization", - "/cn/enterprise/2.14/articles/rendering-and-diffing-images": "/cn/enterprise/2.14/user/articles/rendering-and-diffing-images", - "/cn/enterprise/2.14/articles/rendering-csv-and-tsv-data": "/cn/enterprise/2.14/user/articles/rendering-csv-and-tsv-data", - "/cn/enterprise/2.14/articles/rendering-differences-in-prose-documents": "/cn/enterprise/2.14/user/articles/rendering-differences-in-prose-documents", - "/cn/enterprise/2.14/articles/rendering-pdf-documents": "/cn/enterprise/2.14/user/articles/rendering-pdf-documents", - "/cn/enterprise/2.14/articles/reopening-a-closed-project-board": "/cn/enterprise/2.14/user/articles/reopening-a-closed-project-board", - "/cn/enterprise/2.14/articles/repository-metadata-on-github-pages": "/cn/enterprise/2.14/user/articles/repository-metadata-on-github-pages", - "/cn/enterprise/2.14/articles/repository-permission-levels-for-an-organization": "/cn/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization", - "/cn/enterprise/2.14/articles/requesting-a-pull-request-review": "/cn/enterprise/2.14/user/articles/requesting-a-pull-request-review", - "/cn/enterprise/2.14/articles/requesting-a-trial-of-github-enterprise": "/cn/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise", - "/cn/enterprise/2.14/articles/requesting-to-add-a-child-team": "/cn/enterprise/2.14/user/articles/requesting-to-add-a-child-team", - "/cn/enterprise/2.14/articles/requesting-to-add-or-change-a-parent-team": "/cn/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team", - "/cn/enterprise/2.14/articles/requiring-two-factor-authentication-in-your-organization": "/cn/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.14/articles/resolving-a-merge-conflict-on-github": "/cn/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github", - "/cn/enterprise/2.14/articles/resolving-a-merge-conflict-using-the-command-line": "/cn/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/cn/enterprise/2.14/articles/resolving-git-large-file-storage-upload-failures": "/cn/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures", - "/cn/enterprise/2.14/articles/resolving-merge-conflicts-after-a-git-rebase": "/cn/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/cn/enterprise/2.14/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.14/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.14/articles/reverting-a-pull-request": "/cn/enterprise/2.14/user/articles/reverting-a-pull-request", - "/cn/enterprise/2.14/articles/reviewing-changes-in-pull-requests": "/cn/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests", - "/cn/enterprise/2.14/articles/reviewing-proposed-changes-in-a-pull-request": "/cn/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/cn/enterprise/2.14/articles/reviewing-the-audit-log-for-your-organization": "/cn/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization", - "/cn/enterprise/2.14/articles/reviewing-your-authorized-applications-oauth": "/cn/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth", - "/cn/enterprise/2.14/articles/reviewing-your-authorized-integrations": "/cn/enterprise/2.14/user/articles/reviewing-your-authorized-integrations", - "/cn/enterprise/2.14/articles/reviewing-your-deploy-keys": "/cn/enterprise/2.14/user/articles/reviewing-your-deploy-keys", - "/cn/enterprise/2.14/articles/reviewing-your-organizations-installed-integrations": "/cn/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations", - "/cn/enterprise/2.14/articles/reviewing-your-security-log": "/cn/enterprise/2.14/user/articles/reviewing-your-security-log", - "/cn/enterprise/2.14/articles/reviewing-your-ssh-keys": "/cn/enterprise/2.14/user/articles/reviewing-your-ssh-keys", - "/cn/enterprise/2.14/articles/saving-repositories-with-stars": "/cn/enterprise/2.14/user/articles/saving-repositories-with-stars", - "/cn/enterprise/2.14/articles/searching-code": "/cn/enterprise/2.14/user/articles/searching-code", - "/cn/enterprise/2.14/articles/searching-commits": "/cn/enterprise/2.14/user/articles/searching-commits", - "/cn/enterprise/2.14/articles/searching-for-repositories": "/cn/enterprise/2.14/user/articles/searching-for-repositories", - "/cn/enterprise/2.14/articles/searching-in-forks": "/cn/enterprise/2.14/user/articles/searching-in-forks", - "/cn/enterprise/2.14/articles/searching-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/searching-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/searching-on-github": "/cn/enterprise/2.14/user/articles/searching-on-github", - "/cn/enterprise/2.14/articles/searching-topics": "/cn/enterprise/2.14/user/articles/searching-topics", - "/cn/enterprise/2.14/articles/searching-users": "/cn/enterprise/2.14/user/articles/searching-users", - "/cn/enterprise/2.14/articles/searching-wikis": "/cn/enterprise/2.14/user/articles/searching-wikis", - "/cn/enterprise/2.14/articles/securing-your-account-with-two-factor-authentication-2fa": "/cn/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/cn/enterprise/2.14/articles/set-up-git": "/cn/enterprise/2.14/user/articles/set-up-git", - "/cn/enterprise/2.14/articles/setting-a-backup-email-address": "/cn/enterprise/2.14/user/articles/setting-a-backup-email-address", - "/cn/enterprise/2.14/articles/setting-guidelines-for-repository-contributors": "/cn/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors", - "/cn/enterprise/2.14/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": "/cn/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization", - "/cn/enterprise/2.14/articles/setting-repository-visibility": "/cn/enterprise/2.14/user/articles/setting-repository-visibility", - "/cn/enterprise/2.14/articles/setting-the-default-branch": "/cn/enterprise/2.14/user/articles/setting-the-default-branch", - "/cn/enterprise/2.14/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/cn/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/cn/enterprise/2.14/articles/setting-up-your-project-for-healthy-contributions": "/cn/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions", - "/cn/enterprise/2.14/articles/setting-your-commit-email-address": "/cn/enterprise/2.14/user/articles/setting-your-commit-email-address", - "/cn/enterprise/2.14/articles/setting-your-teams-profile-picture": "/cn/enterprise/2.14/user/articles/setting-your-teams-profile-picture", - "/cn/enterprise/2.14/articles/setting-your-username-in-git": "/cn/enterprise/2.14/user/articles/setting-your-username-in-git", - "/cn/enterprise/2.14/articles/sharing-filters": "/cn/enterprise/2.14/user/articles/sharing-filters", - "/cn/enterprise/2.14/articles/signing-commits": "/cn/enterprise/2.14/user/articles/signing-commits", - "/cn/enterprise/2.14/articles/signing-tags": "/cn/enterprise/2.14/user/articles/signing-tags", - "/cn/enterprise/2.14/articles/signing-up-for-github": "/cn/enterprise/2.14/user/articles/signing-up-for-github", - "/cn/enterprise/2.14/articles/sitemaps-for-github-pages": "/cn/enterprise/2.14/user/articles/sitemaps-for-github-pages", - "/cn/enterprise/2.14/articles/sorting-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/sorting-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/sorting-search-results": "/cn/enterprise/2.14/user/articles/sorting-search-results", - "/cn/enterprise/2.14/articles/source-code-migration-tools": "/cn/enterprise/2.14/user/articles/source-code-migration-tools", - "/cn/enterprise/2.14/articles/splitting-a-subfolder-out-into-a-new-repository": "/cn/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/cn/enterprise/2.14/articles/subscribing-to-and-unsubscribing-from-notifications": "/cn/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/cn/enterprise/2.14/articles/subversion-properties-supported-by-github": "/cn/enterprise/2.14/user/articles/subversion-properties-supported-by-github", - "/cn/enterprise/2.14/articles/sudo-mode": "/cn/enterprise/2.14/user/articles/sudo-mode", - "/cn/enterprise/2.14/articles/support-for-subversion-clients": "/cn/enterprise/2.14/user/articles/support-for-subversion-clients", - "/cn/enterprise/2.14/articles/supported-browsers": "/cn/enterprise/2.14/user/articles/supported-browsers", - "/cn/enterprise/2.14/articles/syncing-a-fork": "/cn/enterprise/2.14/user/articles/syncing-a-fork", - "/cn/enterprise/2.14/articles/telling-git-about-your-signing-key": "/cn/enterprise/2.14/user/articles/telling-git-about-your-signing-key", - "/cn/enterprise/2.14/articles/testing-your-ssh-connection": "/cn/enterprise/2.14/user/articles/testing-your-ssh-connection", - "/cn/enterprise/2.14/articles/tracking-changes-in-a-comment": "/cn/enterprise/2.14/user/articles/tracking-changes-in-a-comment", - "/cn/enterprise/2.14/articles/tracking-changes-in-a-file": "/cn/enterprise/2.14/user/articles/tracking-changes-in-a-file", - "/cn/enterprise/2.14/articles/tracking-progress-on-your-project-board": "/cn/enterprise/2.14/user/articles/tracking-progress-on-your-project-board", - "/cn/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-milestones": "/cn/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/cn/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-project-boards": "/cn/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/cn/enterprise/2.14/articles/transferring-a-repository": "/cn/enterprise/2.14/user/articles/transferring-a-repository", - "/cn/enterprise/2.14/articles/transferring-organization-ownership": "/cn/enterprise/2.14/user/articles/transferring-organization-ownership", - "/cn/enterprise/2.14/articles/troubleshooting-commit-signature-verification": "/cn/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification", - "/cn/enterprise/2.14/articles/troubleshooting-commits-on-your-timeline": "/cn/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline", - "/cn/enterprise/2.14/articles/troubleshooting-commits": "/cn/enterprise/2.14/user/articles/troubleshooting-commits", - "/cn/enterprise/2.14/articles/troubleshooting-github-pages-builds": "/cn/enterprise/2.14/user/articles/troubleshooting-github-pages-builds", - "/cn/enterprise/2.14/articles/troubleshooting-search-queries": "/cn/enterprise/2.14/user/articles/troubleshooting-search-queries", - "/cn/enterprise/2.14/articles/troubleshooting-ssh": "/cn/enterprise/2.14/user/articles/troubleshooting-ssh", - "/cn/enterprise/2.14/articles/types-of-github-accounts": "/cn/enterprise/2.14/user/articles/types-of-github-accounts", - "/cn/enterprise/2.14/articles/types-of-required-status-checks": "/cn/enterprise/2.14/user/articles/types-of-required-status-checks", - "/cn/enterprise/2.14/articles/understanding-connections-between-repositories": "/cn/enterprise/2.14/user/articles/understanding-connections-between-repositories", - "/cn/enterprise/2.14/articles/understanding-the-search-syntax": "/cn/enterprise/2.14/user/articles/understanding-the-search-syntax", - "/cn/enterprise/2.14/articles/unpublishing-a-project-pages-site": "/cn/enterprise/2.14/user/articles/unpublishing-a-project-pages-site", - "/cn/enterprise/2.14/articles/unpublishing-a-user-pages-site": "/cn/enterprise/2.14/user/articles/unpublishing-a-user-pages-site", - "/cn/enterprise/2.14/articles/updating-an-expired-gpg-key": "/cn/enterprise/2.14/user/articles/updating-an-expired-gpg-key", - "/cn/enterprise/2.14/articles/updating-credentials-from-the-osx-keychain": "/cn/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain", - "/cn/enterprise/2.14/articles/updating-your-github-access-credentials": "/cn/enterprise/2.14/user/articles/updating-your-github-access-credentials", - "/cn/enterprise/2.14/articles/updating-your-markdown-processor-to-kramdown": "/cn/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown", - "/cn/enterprise/2.14/articles/user-organization-and-project-pages": "/cn/enterprise/2.14/user/articles/user-organization-and-project-pages", - "/cn/enterprise/2.14/articles/using-a-static-site-generator-other-than-jekyll": "/cn/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll", - "/cn/enterprise/2.14/articles/using-a-verified-email-address-in-your-gpg-key": "/cn/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/cn/enterprise/2.14/articles/using-advanced-git-commands": "/cn/enterprise/2.14/user/articles/using-advanced-git-commands", - "/cn/enterprise/2.14/articles/using-common-git-commands": "/cn/enterprise/2.14/user/articles/using-common-git-commands", - "/cn/enterprise/2.14/articles/using-git-rebase-on-the-command-line": "/cn/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line", - "/cn/enterprise/2.14/articles/using-github": "/cn/enterprise/2.14/user/articles/using-github", - "/cn/enterprise/2.14/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/cn/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/cn/enterprise/2.14/articles/using-saved-replies": "/cn/enterprise/2.14/user/articles/using-saved-replies", - "/cn/enterprise/2.14/articles/using-search-to-filter-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/using-syntax-highlighting-on-github-pages": "/cn/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages", - "/cn/enterprise/2.14/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/cn/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/cn/enterprise/2.14/articles/versioning-large-files": "/cn/enterprise/2.14/user/articles/versioning-large-files", - "/cn/enterprise/2.14/articles/viewing-a-projects-contributors": "/cn/enterprise/2.14/user/articles/viewing-a-projects-contributors", - "/cn/enterprise/2.14/articles/viewing-a-pull-request-review": "/cn/enterprise/2.14/user/articles/viewing-a-pull-request-review", - "/cn/enterprise/2.14/articles/viewing-a-repositorys-network": "/cn/enterprise/2.14/user/articles/viewing-a-repositorys-network", - "/cn/enterprise/2.14/articles/viewing-a-summary-of-repository-activity": "/cn/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity", - "/cn/enterprise/2.14/articles/viewing-a-wikis-history-of-changes": "/cn/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes", - "/cn/enterprise/2.14/articles/viewing-all-of-your-issues-and-pull-requests": "/cn/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/cn/enterprise/2.14/articles/viewing-and-comparing-commits": "/cn/enterprise/2.14/user/articles/viewing-and-comparing-commits", - "/cn/enterprise/2.14/articles/viewing-branches-in-your-repository": "/cn/enterprise/2.14/user/articles/viewing-branches-in-your-repository", - "/cn/enterprise/2.14/articles/viewing-contributions-on-your-profile": "/cn/enterprise/2.14/user/articles/viewing-contributions-on-your-profile", - "/cn/enterprise/2.14/articles/viewing-jekyll-build-error-messages": "/cn/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages", - "/cn/enterprise/2.14/articles/viewing-peoples-roles-in-an-organization": "/cn/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization", - "/cn/enterprise/2.14/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/cn/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/cn/enterprise/2.14/articles/viewing-your-milestones-progress": "/cn/enterprise/2.14/user/articles/viewing-your-milestones-progress", - "/cn/enterprise/2.14/articles/viewing-your-repositorys-tags": "/cn/enterprise/2.14/user/articles/viewing-your-repositorys-tags", - "/cn/enterprise/2.14/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/cn/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/cn/enterprise/2.14/articles/visualizing-commits-in-a-repository": "/cn/enterprise/2.14/user/articles/visualizing-commits-in-a-repository", - "/cn/enterprise/2.14/articles/watching-and-unwatching-repositories": "/cn/enterprise/2.14/user/articles/watching-and-unwatching-repositories", - "/cn/enterprise/2.14/articles/watching-and-unwatching-team-discussions": "/cn/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions", - "/cn/enterprise/2.14/articles/what-are-the-differences-between-subversion-and-git": "/cn/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git", - "/cn/enterprise/2.14/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/cn/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/cn/enterprise/2.14/articles/what-is-github-pages": "/cn/enterprise/2.14/user/articles/what-is-github-pages", - "/cn/enterprise/2.14/articles/which-remote-url-should-i-use": "/cn/enterprise/2.14/user/articles/which-remote-url-should-i-use", - "/cn/enterprise/2.14/articles/why-are-my-commits-in-the-wrong-order": "/cn/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order", - "/cn/enterprise/2.14/articles/why-are-my-commits-linked-to-the-wrong-user": "/cn/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/cn/enterprise/2.14/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/cn/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/cn/enterprise/2.14/articles/why-is-git-always-asking-for-my-password": "/cn/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password", - "/cn/enterprise/2.14/articles/working-with-advanced-formatting": "/cn/enterprise/2.14/user/articles/working-with-advanced-formatting", - "/cn/enterprise/2.14/articles/working-with-forks": "/cn/enterprise/2.14/user/articles/working-with-forks", - "/cn/enterprise/2.14/articles/working-with-jupyter-notebook-files-on-github": "/cn/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github", - "/cn/enterprise/2.14/articles/working-with-large-files": "/cn/enterprise/2.14/user/articles/working-with-large-files", - "/cn/enterprise/2.14/articles/working-with-non-code-files": "/cn/enterprise/2.14/user/articles/working-with-non-code-files", - "/cn/enterprise/2.14/articles/working-with-pre-receive-hooks": "/cn/enterprise/2.14/user/articles/working-with-pre-receive-hooks", - "/cn/enterprise/2.14/articles/working-with-saved-replies": "/cn/enterprise/2.14/user/articles/working-with-saved-replies", - "/cn/enterprise/2.14/articles/working-with-ssh-key-passphrases": "/cn/enterprise/2.14/user/articles/working-with-ssh-key-passphrases", - "/cn/enterprise/2.14/articles/working-with-subversion-on-github": "/cn/enterprise/2.14/user/articles/working-with-subversion-on-github", - "/cn/enterprise/2.14/user/categories/admin/guidesistering-a-repository": "/cn/enterprise/2.14/user/categories/administering-a-repository", - "/cn/enterprise/2.14/categories/administering-a-repository": "/cn/enterprise/2.14/user/categories/administering-a-repository", - "/cn/enterprise/2.14/categories/authenticating-to-github": "/cn/enterprise/2.14/user/categories/authenticating-to-github", - "/cn/enterprise/2.14/categories/building-a-strong-community": "/cn/enterprise/2.14/user/categories/building-a-strong-community", - "/cn/enterprise/2.14/categories/collaborating-with-issues-and-pull-requests": "/cn/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests", - "/cn/enterprise/2.14/categories/committing-changes-to-your-project": "/cn/enterprise/2.14/user/categories/committing-changes-to-your-project", - "/cn/enterprise/2.14/categories/creating-cloning-and-archiving-repositories": "/cn/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories", - "/cn/enterprise/2.14/categories/customizing-github-pages": "/cn/enterprise/2.14/user/categories/customizing-github-pages", - "/cn/enterprise/2.14/categories/extending-github": "/cn/enterprise/2.14/user/categories/extending-github", - "/cn/enterprise/2.14/categories/getting-started-with-github": "/cn/enterprise/2.14/user/categories/getting-started-with-github", - "/cn/enterprise/2.14/categories/github-pages-basics": "/cn/enterprise/2.14/user/categories/github-pages-basics", - "/cn/enterprise/2.14/categories/importing-your-projects-to-github": "/cn/enterprise/2.14/user/categories/importing-your-projects-to-github", - "/cn/enterprise/2.14/categories/managing-files-in-a-repository": "/cn/enterprise/2.14/user/categories/managing-files-in-a-repository", - "/cn/enterprise/2.14/categories/managing-large-files": "/cn/enterprise/2.14/user/categories/managing-large-files", - "/cn/enterprise/2.14/categories/managing-your-work-on-github": "/cn/enterprise/2.14/user/categories/managing-your-work-on-github", - "/cn/enterprise/2.14/categories/receiving-notifications-about-activity-on-github": "/cn/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github", - "/cn/enterprise/2.14/categories/searching-for-information-on-github": "/cn/enterprise/2.14/user/categories/searching-for-information-on-github", - "/cn/enterprise/2.14/categories/setting-up-and-managing-organizations-and-teams": "/cn/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams", - "/cn/enterprise/2.14/categories/setting-up-and-managing-your-github-profile": "/cn/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile", - "/cn/enterprise/2.14/categories/setting-up-and-managing-your-github-user-account": "/cn/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account", - "/cn/enterprise/2.14/categories/using-git": "/cn/enterprise/2.14/user/categories/using-git", - "/cn/enterprise/2.14/categories/visualizing-repository-data-with-graphs": "/cn/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs", - "/cn/enterprise/2.14/categories/writing-on-github": "/cn/enterprise/2.14/user/categories/writing-on-github", - "/en/enterprise/2.14/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.14/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/en/enterprise/2.14/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.14/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/en/enterprise/2.14/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.14/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/en/enterprise/2.14/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.14/admin/articles/using-github-task-runner", - "/enterprise/2.14/admin/articles/using-github-task-runner": "/en/enterprise/2.14/admin/articles/using-github-task-runner", - "/enterprise/2.14/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.14/admin/articles/using-github-task-runner", - "/en/enterprise/2.14/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.14/admin/clustering/about-cluster-nodes", - "/enterprise/2.14/admin/clustering/about-cluster-nodes": "/en/enterprise/2.14/admin/clustering/about-cluster-nodes", - "/enterprise/2.14/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.14/admin/clustering/about-cluster-nodes", - "/en/enterprise/2.14/admin/guides/clustering/clustering-overview": "/en/enterprise/2.14/admin/clustering/clustering-overview", - "/enterprise/2.14/admin/clustering/clustering-overview": "/en/enterprise/2.14/admin/clustering/clustering-overview", - "/enterprise/2.14/admin/guides/clustering/clustering-overview": "/en/enterprise/2.14/admin/clustering/clustering-overview", - "/en/enterprise/2.14/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.14/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/en/enterprise/2.14/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.14/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.14/admin/clustering/evacuating-a-cluster-node": "/en/enterprise/2.14/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.14/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.14/admin/clustering/evacuating-a-cluster-node", - "/en/enterprise/2.14/admin/guides/clustering": "/en/enterprise/2.14/admin/clustering", - "/enterprise/2.14/admin/clustering": "/en/enterprise/2.14/admin/clustering", - "/enterprise/2.14/admin/guides/clustering": "/en/enterprise/2.14/admin/clustering", - "/en/enterprise/2.14/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.14/admin/clustering/initializing-the-cluster", - "/enterprise/2.14/admin/clustering/initializing-the-cluster": "/en/enterprise/2.14/admin/clustering/initializing-the-cluster", - "/enterprise/2.14/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.14/admin/clustering/initializing-the-cluster", - "/en/enterprise/2.14/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.14/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster", - "/en/enterprise/2.14/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.14/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.14/admin/clustering/monitoring-cluster-nodes": "/en/enterprise/2.14/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.14/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.14/admin/clustering/monitoring-cluster-nodes", - "/en/enterprise/2.14/admin/guides/clustering/network-configuration": "/en/enterprise/2.14/admin/clustering/network-configuration", - "/enterprise/2.14/admin/clustering/network-configuration": "/en/enterprise/2.14/admin/clustering/network-configuration", - "/enterprise/2.14/admin/guides/clustering/network-configuration": "/en/enterprise/2.14/admin/clustering/network-configuration", - "/en/enterprise/2.14/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.14/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.14/admin/clustering/replacing-a-cluster-node": "/en/enterprise/2.14/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.14/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.14/admin/clustering/replacing-a-cluster-node", - "/en/enterprise/2.14/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.14/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances", - "/en/enterprise/2.14/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.14/admin/clustering/upgrading-a-cluster", - "/enterprise/2.14/admin/clustering/upgrading-a-cluster": "/en/enterprise/2.14/admin/clustering/upgrading-a-cluster", - "/enterprise/2.14/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.14/admin/clustering/upgrading-a-cluster", - "/en/enterprise/2.14/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.14/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks", - "/en/enterprise/2.14/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.14/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/en/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/en/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/en/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/en/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.14/admin/developer-workflow/blocking-force-pushes", - "/en/enterprise/2.14/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.14/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/en/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins", - "/en/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci", - "/en/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/en/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/en/enterprise/2.14/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.14/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations", - "/en/enterprise/2.14/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.14/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/en/enterprise/2.14/admin/guides/developer-workflow": "/en/enterprise/2.14/admin/developer-workflow", - "/enterprise/2.14/admin/developer-workflow": "/en/enterprise/2.14/admin/developer-workflow", - "/enterprise/2.14/admin/guides/developer-workflow": "/en/enterprise/2.14/admin/developer-workflow", - "/en/enterprise/2.14/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.14/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/en/enterprise/2.14/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.14/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira", - "/en/enterprise/2.14/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.14/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks", - "/en/enterprise/2.14/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.14/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/en/enterprise/2.14/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.14/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/en/enterprise/2.14/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.14/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support", - "/en/enterprise/2.14/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.14/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.14/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/en/enterprise/2.14/admin/guides/enterprise-support": "/en/enterprise/2.14/admin/enterprise-support", - "/enterprise/2.14/admin/enterprise-support": "/en/enterprise/2.14/admin/enterprise-support", - "/enterprise/2.14/admin/guides/enterprise-support": "/en/enterprise/2.14/admin/enterprise-support", - "/en/enterprise/2.14/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.14/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket", - "/en/enterprise/2.14/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.14/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support", - "/en/enterprise/2.14/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.14/admin/enterprise-support/reaching-github-support", - "/enterprise/2.14/admin/enterprise-support/reaching-github-support": "/en/enterprise/2.14/admin/enterprise-support/reaching-github-support", - "/enterprise/2.14/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.14/admin/enterprise-support/reaching-github-support", - "/en/enterprise/2.14/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.14/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support", - "/en/enterprise/2.14/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.14/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.14/admin/enterprise-support/submitting-a-ticket": "/en/enterprise/2.14/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.14/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.14/admin/enterprise-support/submitting-a-ticket", - "/en/enterprise/2.14/admin/guides": "/en/enterprise/2.14/admin", - "/enterprise/2.14/admin": "/en/enterprise/2.14/admin", - "/enterprise/2.14/admin/guides": "/en/enterprise/2.14/admin", - "/en/enterprise/2.14/admin/guides/installation/about-geo-replication": "/en/enterprise/2.14/admin/installation/about-geo-replication", - "/enterprise/2.14/admin/installation/about-geo-replication": "/en/enterprise/2.14/admin/installation/about-geo-replication", - "/enterprise/2.14/admin/guides/installation/about-geo-replication": "/en/enterprise/2.14/admin/installation/about-geo-replication", - "/en/enterprise/2.14/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.14/admin/installation/about-high-availability-configuration", - "/enterprise/2.14/admin/installation/about-high-availability-configuration": "/en/enterprise/2.14/admin/installation/about-high-availability-configuration", - "/enterprise/2.14/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.14/admin/installation/about-high-availability-configuration", - "/en/enterprise/2.14/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.14/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api", - "/en/enterprise/2.14/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.14/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh", - "/en/enterprise/2.14/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.14/admin/installation/accessing-the-management-console", - "/enterprise/2.14/admin/installation/accessing-the-management-console": "/en/enterprise/2.14/admin/installation/accessing-the-management-console", - "/enterprise/2.14/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.14/admin/installation/accessing-the-management-console", - "/en/enterprise/2.14/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.14/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard", - "/en/enterprise/2.14/admin/guides/installation/activity-dashboard": "/en/enterprise/2.14/admin/installation/activity-dashboard", - "/enterprise/2.14/admin/installation/activity-dashboard": "/en/enterprise/2.14/admin/installation/activity-dashboard", - "/enterprise/2.14/admin/guides/installation/activity-dashboard": "/en/enterprise/2.14/admin/installation/activity-dashboard", - "/en/enterprise/2.14/admin/guides/installation/audit-logging": "/en/enterprise/2.14/admin/installation/audit-logging", - "/enterprise/2.14/admin/installation/audit-logging": "/en/enterprise/2.14/admin/installation/audit-logging", - "/enterprise/2.14/admin/guides/installation/audit-logging": "/en/enterprise/2.14/admin/installation/audit-logging", - "/en/enterprise/2.14/admin/guides/installation/audited-actions": "/en/enterprise/2.14/admin/installation/audited-actions", - "/enterprise/2.14/admin/installation/audited-actions": "/en/enterprise/2.14/admin/installation/audited-actions", - "/enterprise/2.14/admin/guides/installation/audited-actions": "/en/enterprise/2.14/admin/installation/audited-actions", - "/en/enterprise/2.14/admin/guides/installation/command-line-utilities": "/en/enterprise/2.14/admin/installation/command-line-utilities", - "/enterprise/2.14/admin/installation/command-line-utilities": "/en/enterprise/2.14/admin/installation/command-line-utilities", - "/enterprise/2.14/admin/guides/installation/command-line-utilities": "/en/enterprise/2.14/admin/installation/command-line-utilities", - "/en/enterprise/2.14/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.14/admin/installation/configuring-a-hostname", - "/enterprise/2.14/admin/installation/configuring-a-hostname": "/en/enterprise/2.14/admin/installation/configuring-a-hostname", - "/enterprise/2.14/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.14/admin/installation/configuring-a-hostname", - "/en/enterprise/2.14/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.14/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server", - "/en/enterprise/2.14/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.14/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance", - "/en/enterprise/2.14/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.14/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules", - "/en/enterprise/2.14/admin/guides/installation/configuring-collectd": "/en/enterprise/2.14/admin/installation/configuring-collectd", - "/enterprise/2.14/admin/installation/configuring-collectd": "/en/enterprise/2.14/admin/installation/configuring-collectd", - "/enterprise/2.14/admin/guides/installation/configuring-collectd": "/en/enterprise/2.14/admin/installation/configuring-collectd", - "/en/enterprise/2.14/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.14/admin/installation/configuring-dns-nameservers", - "/enterprise/2.14/admin/installation/configuring-dns-nameservers": "/en/enterprise/2.14/admin/installation/configuring-dns-nameservers", - "/enterprise/2.14/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.14/admin/installation/configuring-dns-nameservers", - "/en/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/en/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.14/admin/installation/configuring-git-large-file-storage": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.14/admin/installation/configuring-git-large-file-storage", - "/en/enterprise/2.14/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.14/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/en/enterprise/2.14/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.14/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance", - "/en/enterprise/2.14/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.14/admin/installation/configuring-rate-limits", - "/enterprise/2.14/admin/installation/configuring-rate-limits": "/en/enterprise/2.14/admin/installation/configuring-rate-limits", - "/enterprise/2.14/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.14/admin/installation/configuring-rate-limits", - "/en/enterprise/2.14/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.14/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/en/enterprise/2.14/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.14/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance", - "/en/enterprise/2.14/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.14/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/en/enterprise/2.14/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.14/admin/installation/configuring-time-synchronization", - "/enterprise/2.14/admin/installation/configuring-time-synchronization": "/en/enterprise/2.14/admin/installation/configuring-time-synchronization", - "/enterprise/2.14/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.14/admin/installation/configuring-time-synchronization", - "/en/enterprise/2.14/admin/guides/installation/configuring-tls": "/en/enterprise/2.14/admin/installation/configuring-tls", - "/enterprise/2.14/admin/installation/configuring-tls": "/en/enterprise/2.14/admin/installation/configuring-tls", - "/enterprise/2.14/admin/guides/installation/configuring-tls": "/en/enterprise/2.14/admin/installation/configuring-tls", - "/en/enterprise/2.14/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.14/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/en/enterprise/2.14/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.14/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/en/enterprise/2.14/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.14/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.14/admin/installation/creating-a-high-availability-replica": "/en/enterprise/2.14/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.14/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.14/admin/installation/creating-a-high-availability-replica", - "/en/enterprise/2.14/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.14/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.14/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/en/enterprise/2.14/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.14/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode", - "/en/enterprise/2.14/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.14/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.14/admin/installation/enabling-automatic-update-checks": "/en/enterprise/2.14/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.14/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.14/admin/installation/enabling-automatic-update-checks", - "/en/enterprise/2.14/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.14/admin/installation/enabling-private-mode", - "/enterprise/2.14/admin/installation/enabling-private-mode": "/en/enterprise/2.14/admin/installation/enabling-private-mode", - "/enterprise/2.14/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.14/admin/installation/enabling-private-mode", - "/en/enterprise/2.14/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.14/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.14/admin/installation/enabling-subdomain-isolation": "/en/enterprise/2.14/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.14/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.14/admin/installation/enabling-subdomain-isolation", - "/en/enterprise/2.14/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.14/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.14/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.14/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources", - "/en/enterprise/2.14/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.14/admin/installation/increasing-storage-capacity", - "/enterprise/2.14/admin/installation/increasing-storage-capacity": "/en/enterprise/2.14/admin/installation/increasing-storage-capacity", - "/enterprise/2.14/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.14/admin/installation/increasing-storage-capacity", - "/en/enterprise/2.14/admin/guides/installation": "/en/enterprise/2.14/admin/installation", - "/enterprise/2.14/admin/installation": "/en/enterprise/2.14/admin/installation", - "/enterprise/2.14/admin/guides/installation": "/en/enterprise/2.14/admin/installation", - "/en/enterprise/2.14/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.14/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware", - "/en/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver", - "/en/enterprise/2.14/admin/guides/installation/log-forwarding": "/en/enterprise/2.14/admin/installation/log-forwarding", - "/enterprise/2.14/admin/installation/log-forwarding": "/en/enterprise/2.14/admin/installation/log-forwarding", - "/enterprise/2.14/admin/guides/installation/log-forwarding": "/en/enterprise/2.14/admin/installation/log-forwarding", - "/en/enterprise/2.14/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.14/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/en/enterprise/2.14/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.14/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license", - "/en/enterprise/2.14/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.14/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/en/enterprise/2.14/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.14/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/en/enterprise/2.14/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.14/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/en/enterprise/2.14/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.14/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/en/enterprise/2.14/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.14/admin/installation/monitoring-using-snmp", - "/enterprise/2.14/admin/installation/monitoring-using-snmp": "/en/enterprise/2.14/admin/installation/monitoring-using-snmp", - "/enterprise/2.14/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.14/admin/installation/monitoring-using-snmp", - "/en/enterprise/2.14/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.14/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/en/enterprise/2.14/admin/guides/installation/network-ports": "/en/enterprise/2.14/admin/installation/network-ports", - "/enterprise/2.14/admin/installation/network-ports": "/en/enterprise/2.14/admin/installation/network-ports", - "/enterprise/2.14/admin/guides/installation/network-ports": "/en/enterprise/2.14/admin/installation/network-ports", - "/en/enterprise/2.14/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.14/admin/installation/recommended-alert-thresholds", - "/enterprise/2.14/admin/installation/recommended-alert-thresholds": "/en/enterprise/2.14/admin/installation/recommended-alert-thresholds", - "/enterprise/2.14/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.14/admin/installation/recommended-alert-thresholds", - "/en/enterprise/2.14/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.14/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration", - "/en/enterprise/2.14/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.14/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.14/admin/installation/removing-a-high-availability-replica": "/en/enterprise/2.14/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.14/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.14/admin/installation/removing-a-high-availability-replica", - "/en/enterprise/2.14/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.14/admin/installation/searching-the-audit-log", - "/enterprise/2.14/admin/installation/searching-the-audit-log": "/en/enterprise/2.14/admin/installation/searching-the-audit-log", - "/enterprise/2.14/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.14/admin/installation/searching-the-audit-log", - "/en/enterprise/2.14/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.14/admin/installation/setting-git-push-limits", - "/enterprise/2.14/admin/installation/setting-git-push-limits": "/en/enterprise/2.14/admin/installation/setting-git-push-limits", - "/enterprise/2.14/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.14/admin/installation/setting-git-push-limits", - "/en/enterprise/2.14/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.14/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance", - "/en/enterprise/2.14/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.14/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.14/admin/installation/setting-up-a-staging-instance": "/en/enterprise/2.14/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.14/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.14/admin/installation/setting-up-a-staging-instance", - "/en/enterprise/2.14/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.14/admin/installation/setting-up-external-monitoring", - "/enterprise/2.14/admin/installation/setting-up-external-monitoring": "/en/enterprise/2.14/admin/installation/setting-up-external-monitoring", - "/enterprise/2.14/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.14/admin/installation/setting-up-external-monitoring", - "/en/enterprise/2.14/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.14/admin/installation/site-admin-dashboard", - "/enterprise/2.14/admin/installation/site-admin-dashboard": "/en/enterprise/2.14/admin/installation/site-admin-dashboard", - "/enterprise/2.14/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.14/admin/installation/site-admin-dashboard", - "/en/enterprise/2.14/admin/guides/installation/system-overview": "/en/enterprise/2.14/admin/installation/system-overview", - "/enterprise/2.14/admin/installation/system-overview": "/en/enterprise/2.14/admin/installation/system-overview", - "/enterprise/2.14/admin/guides/installation/system-overview": "/en/enterprise/2.14/admin/installation/system-overview", - "/en/enterprise/2.14/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.14/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.14/admin/installation/troubleshooting-ssl-errors": "/en/enterprise/2.14/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.14/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.14/admin/installation/troubleshooting-ssl-errors", - "/en/enterprise/2.14/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.14/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/en/enterprise/2.14/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.14/admin/installation/upgrade-requirements", - "/enterprise/2.14/admin/installation/upgrade-requirements": "/en/enterprise/2.14/admin/installation/upgrade-requirements", - "/enterprise/2.14/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.14/admin/installation/upgrade-requirements", - "/en/enterprise/2.14/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.14/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.14/admin/installation/upgrading-github-enterprise-server": "/en/enterprise/2.14/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.14/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.14/admin/installation/upgrading-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.14/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/en/enterprise/2.14/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.14/admin/installation/validating-your-domain-settings", - "/enterprise/2.14/admin/installation/validating-your-domain-settings": "/en/enterprise/2.14/admin/installation/validating-your-domain-settings", - "/enterprise/2.14/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.14/admin/installation/validating-your-domain-settings", - "/en/enterprise/2.14/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.14/admin/installation/viewing-push-logs", - "/enterprise/2.14/admin/installation/viewing-push-logs": "/en/enterprise/2.14/admin/installation/viewing-push-logs", - "/enterprise/2.14/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.14/admin/installation/viewing-push-logs", - "/en/enterprise/2.14/admin/guides/migrations/about-migrations": "/en/enterprise/2.14/admin/migrations/about-migrations", - "/enterprise/2.14/admin/migrations/about-migrations": "/en/enterprise/2.14/admin/migrations/about-migrations", - "/enterprise/2.14/admin/guides/migrations/about-migrations": "/en/enterprise/2.14/admin/migrations/about-migrations", - "/en/enterprise/2.14/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.14/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.14/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom", - "/en/enterprise/2.14/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.14/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/en/enterprise/2.14/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.14/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/en/enterprise/2.14/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.14/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts", - "/en/enterprise/2.14/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.14/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems", - "/en/enterprise/2.14/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.14/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/migrations": "/en/enterprise/2.14/admin/migrations", - "/enterprise/2.14/admin/migrations": "/en/enterprise/2.14/admin/migrations", - "/enterprise/2.14/admin/guides/migrations": "/en/enterprise/2.14/admin/migrations", - "/en/enterprise/2.14/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.14/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/en/enterprise/2.14/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.14/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization", - "/en/enterprise/2.14/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.14/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/en/enterprise/2.14/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.14/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/en/enterprise/2.14/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.14/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.14/admin/migrations/reviewing-migration-conflicts": "/en/enterprise/2.14/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.14/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.14/admin/migrations/reviewing-migration-conflicts", - "/en/enterprise/2.14/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.14/admin/migrations/reviewing-migration-data", - "/enterprise/2.14/admin/migrations/reviewing-migration-data": "/en/enterprise/2.14/admin/migrations/reviewing-migration-data", - "/enterprise/2.14/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.14/admin/migrations/reviewing-migration-data", - "/en/enterprise/2.14/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.14/admin/user-management/about-global-webhooks", - "/enterprise/2.14/admin/user-management/about-global-webhooks": "/en/enterprise/2.14/admin/user-management/about-global-webhooks", - "/enterprise/2.14/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.14/admin/user-management/about-global-webhooks", - "/en/enterprise/2.14/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.14/admin/user-management/adding-people-to-teams", - "/enterprise/2.14/admin/user-management/adding-people-to-teams": "/en/enterprise/2.14/admin/user-management/adding-people-to-teams", - "/enterprise/2.14/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.14/admin/user-management/adding-people-to-teams", - "/en/enterprise/2.14/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.14/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/en/enterprise/2.14/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.14/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/en/enterprise/2.14/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.14/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories", - "/en/enterprise/2.14/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.14/admin/user-management/auditing-ssh-keys", - "/enterprise/2.14/admin/user-management/auditing-ssh-keys": "/en/enterprise/2.14/admin/user-management/auditing-ssh-keys", - "/enterprise/2.14/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.14/admin/user-management/auditing-ssh-keys", - "/en/enterprise/2.14/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.14/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.14/admin/user-management/auditing-users-across-your-instance": "/en/enterprise/2.14/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.14/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.14/admin/user-management/auditing-users-across-your-instance", - "/en/enterprise/2.14/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.14/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/en/enterprise/2.14/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.14/admin/user-management/basic-account-settings", - "/enterprise/2.14/admin/user-management/basic-account-settings": "/en/enterprise/2.14/admin/user-management/basic-account-settings", - "/enterprise/2.14/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.14/admin/user-management/basic-account-settings", - "/en/enterprise/2.14/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.14/admin/user-management/best-practices-for-user-security", - "/enterprise/2.14/admin/user-management/best-practices-for-user-security": "/en/enterprise/2.14/admin/user-management/best-practices-for-user-security", - "/enterprise/2.14/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.14/admin/user-management/best-practices-for-user-security", - "/en/enterprise/2.14/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.14/admin/user-management/changing-authentication-methods", - "/enterprise/2.14/admin/user-management/changing-authentication-methods": "/en/enterprise/2.14/admin/user-management/changing-authentication-methods", - "/enterprise/2.14/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.14/admin/user-management/changing-authentication-methods", - "/en/enterprise/2.14/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.14/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.14/admin/user-management/configuring-email-for-notifications": "/en/enterprise/2.14/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.14/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.14/admin/user-management/configuring-email-for-notifications", - "/en/enterprise/2.14/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.14/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership", - "/en/enterprise/2.14/admin/guides/user-management/creating-organizations": "/en/enterprise/2.14/admin/user-management/creating-organizations", - "/enterprise/2.14/admin/user-management/creating-organizations": "/en/enterprise/2.14/admin/user-management/creating-organizations", - "/enterprise/2.14/admin/guides/user-management/creating-organizations": "/en/enterprise/2.14/admin/user-management/creating-organizations", - "/en/enterprise/2.14/admin/guides/user-management/creating-teams": "/en/enterprise/2.14/admin/user-management/creating-teams", - "/enterprise/2.14/admin/user-management/creating-teams": "/en/enterprise/2.14/admin/user-management/creating-teams", - "/enterprise/2.14/admin/guides/user-management/creating-teams": "/en/enterprise/2.14/admin/user-management/creating-teams", - "/en/enterprise/2.14/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.14/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance", - "/en/enterprise/2.14/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.14/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups", - "/en/enterprise/2.14/admin/guides/user-management": "/en/enterprise/2.14/admin/user-management", - "/enterprise/2.14/admin/user-management": "/en/enterprise/2.14/admin/user-management", - "/enterprise/2.14/admin/guides/user-management": "/en/enterprise/2.14/admin/user-management", - "/en/enterprise/2.14/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.14/admin/user-management/managing-dormant-users", - "/enterprise/2.14/admin/user-management/managing-dormant-users": "/en/enterprise/2.14/admin/user-management/managing-dormant-users", - "/enterprise/2.14/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.14/admin/user-management/managing-dormant-users", - "/en/enterprise/2.14/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.14/admin/user-management/managing-global-webhooks", - "/enterprise/2.14/admin/user-management/managing-global-webhooks": "/en/enterprise/2.14/admin/user-management/managing-global-webhooks", - "/enterprise/2.14/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.14/admin/user-management/managing-global-webhooks", - "/en/enterprise/2.14/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.14/admin/user-management/organizations-and-teams", - "/enterprise/2.14/admin/user-management/organizations-and-teams": "/en/enterprise/2.14/admin/user-management/organizations-and-teams", - "/enterprise/2.14/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.14/admin/user-management/organizations-and-teams", - "/en/enterprise/2.14/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.14/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/en/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/en/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/en/enterprise/2.14/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.14/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations", - "/en/enterprise/2.14/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.14/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/en/enterprise/2.14/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.14/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator", - "/en/enterprise/2.14/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.14/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.14/admin/user-management/rebuilding-contributions-data": "/en/enterprise/2.14/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.14/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.14/admin/user-management/rebuilding-contributions-data", - "/en/enterprise/2.14/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.14/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations", - "/en/enterprise/2.14/admin/guides/user-management/repositories": "/en/enterprise/2.14/admin/user-management/repositories", - "/enterprise/2.14/admin/user-management/repositories": "/en/enterprise/2.14/admin/user-management/repositories", - "/enterprise/2.14/admin/guides/user-management/repositories": "/en/enterprise/2.14/admin/user-management/repositories", - "/en/enterprise/2.14/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.14/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/en/enterprise/2.14/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.14/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users", - "/en/enterprise/2.14/admin/guides/user-management/user-security": "/en/enterprise/2.14/admin/user-management/user-security", - "/enterprise/2.14/admin/user-management/user-security": "/en/enterprise/2.14/admin/user-management/user-security", - "/enterprise/2.14/admin/guides/user-management/user-security": "/en/enterprise/2.14/admin/user-management/user-security", - "/en/enterprise/2.14/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.14/admin/user-management/using-built-in-authentication", - "/enterprise/2.14/admin/user-management/using-built-in-authentication": "/en/enterprise/2.14/admin/user-management/using-built-in-authentication", - "/enterprise/2.14/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.14/admin/user-management/using-built-in-authentication", - "/en/enterprise/2.14/admin/guides/user-management/using-cas": "/en/enterprise/2.14/admin/user-management/using-cas", - "/enterprise/2.14/admin/user-management/using-cas": "/en/enterprise/2.14/admin/user-management/using-cas", - "/enterprise/2.14/admin/guides/user-management/using-cas": "/en/enterprise/2.14/admin/user-management/using-cas", - "/en/enterprise/2.14/admin/guides/user-management/using-ldap": "/en/enterprise/2.14/admin/user-management/using-ldap", - "/enterprise/2.14/admin/user-management/using-ldap": "/en/enterprise/2.14/admin/user-management/using-ldap", - "/enterprise/2.14/admin/guides/user-management/using-ldap": "/en/enterprise/2.14/admin/user-management/using-ldap", - "/en/enterprise/2.14/admin/guides/user-management/using-saml": "/en/enterprise/2.14/admin/user-management/using-saml", - "/enterprise/2.14/admin/user-management/using-saml": "/en/enterprise/2.14/admin/user-management/using-saml", - "/enterprise/2.14/admin/guides/user-management/using-saml": "/en/enterprise/2.14/admin/user-management/using-saml", - "/enterprise/2.14": "/en/enterprise/2.14", - "/en/enterprise/2.14/articles/3d-file-viewer": "/en/enterprise/2.14/user/articles/3d-file-viewer", - "/enterprise/2.14/user/articles/3d-file-viewer": "/en/enterprise/2.14/user/articles/3d-file-viewer", - "/enterprise/2.14/articles/3d-file-viewer": "/en/enterprise/2.14/user/articles/3d-file-viewer", - "/en/enterprise/2.14/articles/about-archiving-repositories": "/en/enterprise/2.14/user/articles/about-archiving-repositories", - "/enterprise/2.14/user/articles/about-archiving-repositories": "/en/enterprise/2.14/user/articles/about-archiving-repositories", - "/enterprise/2.14/articles/about-archiving-repositories": "/en/enterprise/2.14/user/articles/about-archiving-repositories", - "/en/enterprise/2.14/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.14/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.14/articles/about-automation-for-project-boards": "/en/enterprise/2.14/user/articles/about-automation-for-project-boards", - "/enterprise/2.14/user/articles/about-automation-for-project-boards": "/en/enterprise/2.14/user/articles/about-automation-for-project-boards", - "/enterprise/2.14/articles/about-automation-for-project-boards": "/en/enterprise/2.14/user/articles/about-automation-for-project-boards", - "/en/enterprise/2.14/articles/about-branch-restrictions": "/en/enterprise/2.14/user/articles/about-branch-restrictions", - "/enterprise/2.14/user/articles/about-branch-restrictions": "/en/enterprise/2.14/user/articles/about-branch-restrictions", - "/enterprise/2.14/articles/about-branch-restrictions": "/en/enterprise/2.14/user/articles/about-branch-restrictions", - "/en/enterprise/2.14/articles/about-branches": "/en/enterprise/2.14/user/articles/about-branches", - "/enterprise/2.14/user/articles/about-branches": "/en/enterprise/2.14/user/articles/about-branches", - "/enterprise/2.14/articles/about-branches": "/en/enterprise/2.14/user/articles/about-branches", - "/en/enterprise/2.14/articles/about-code-owners": "/en/enterprise/2.14/user/articles/about-code-owners", - "/enterprise/2.14/user/articles/about-code-owners": "/en/enterprise/2.14/user/articles/about-code-owners", - "/enterprise/2.14/articles/about-code-owners": "/en/enterprise/2.14/user/articles/about-code-owners", - "/en/enterprise/2.14/articles/about-collaborative-development-models": "/en/enterprise/2.14/user/articles/about-collaborative-development-models", - "/enterprise/2.14/user/articles/about-collaborative-development-models": "/en/enterprise/2.14/user/articles/about-collaborative-development-models", - "/enterprise/2.14/articles/about-collaborative-development-models": "/en/enterprise/2.14/user/articles/about-collaborative-development-models", - "/en/enterprise/2.14/articles/about-commit-signature-verification": "/en/enterprise/2.14/user/articles/about-commit-signature-verification", - "/enterprise/2.14/user/articles/about-commit-signature-verification": "/en/enterprise/2.14/user/articles/about-commit-signature-verification", - "/enterprise/2.14/articles/about-commit-signature-verification": "/en/enterprise/2.14/user/articles/about-commit-signature-verification", - "/en/enterprise/2.14/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests", - "/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests", - "/enterprise/2.14/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.14/articles/about-conversations-on-github": "/en/enterprise/2.14/user/articles/about-conversations-on-github", - "/enterprise/2.14/user/articles/about-conversations-on-github": "/en/enterprise/2.14/user/articles/about-conversations-on-github", - "/enterprise/2.14/articles/about-conversations-on-github": "/en/enterprise/2.14/user/articles/about-conversations-on-github", - "/en/enterprise/2.14/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests", - "/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests", - "/enterprise/2.14/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.14/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.14/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.14/articles/about-email-notifications": "/en/enterprise/2.14/user/articles/about-email-notifications", - "/enterprise/2.14/user/articles/about-email-notifications": "/en/enterprise/2.14/user/articles/about-email-notifications", - "/enterprise/2.14/articles/about-email-notifications": "/en/enterprise/2.14/user/articles/about-email-notifications", - "/en/enterprise/2.14/articles/about-forks": "/en/enterprise/2.14/user/articles/about-forks", - "/enterprise/2.14/user/articles/about-forks": "/en/enterprise/2.14/user/articles/about-forks", - "/enterprise/2.14/articles/about-forks": "/en/enterprise/2.14/user/articles/about-forks", - "/en/enterprise/2.14/articles/about-git-large-file-storage": "/en/enterprise/2.14/user/articles/about-git-large-file-storage", - "/enterprise/2.14/user/articles/about-git-large-file-storage": "/en/enterprise/2.14/user/articles/about-git-large-file-storage", - "/enterprise/2.14/articles/about-git-large-file-storage": "/en/enterprise/2.14/user/articles/about-git-large-file-storage", - "/en/enterprise/2.14/articles/about-git-rebase": "/en/enterprise/2.14/user/articles/about-git-rebase", - "/enterprise/2.14/user/articles/about-git-rebase": "/en/enterprise/2.14/user/articles/about-git-rebase", - "/enterprise/2.14/articles/about-git-rebase": "/en/enterprise/2.14/user/articles/about-git-rebase", - "/en/enterprise/2.14/articles/about-git-subtree-merges": "/en/enterprise/2.14/user/articles/about-git-subtree-merges", - "/enterprise/2.14/user/articles/about-git-subtree-merges": "/en/enterprise/2.14/user/articles/about-git-subtree-merges", - "/enterprise/2.14/articles/about-git-subtree-merges": "/en/enterprise/2.14/user/articles/about-git-subtree-merges", - "/en/enterprise/2.14/articles/about-github-pages-and-jekyll": "/en/enterprise/2.14/user/articles/about-github-pages-and-jekyll", - "/enterprise/2.14/user/articles/about-github-pages-and-jekyll": "/en/enterprise/2.14/user/articles/about-github-pages-and-jekyll", - "/enterprise/2.14/articles/about-github-pages-and-jekyll": "/en/enterprise/2.14/user/articles/about-github-pages-and-jekyll", - "/en/enterprise/2.14/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.14/user/articles/about-issue-and-pull-request-templates", - "/enterprise/2.14/user/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.14/user/articles/about-issue-and-pull-request-templates", - "/enterprise/2.14/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.14/user/articles/about-issue-and-pull-request-templates", - "/en/enterprise/2.14/articles/about-issues": "/en/enterprise/2.14/user/articles/about-issues", - "/enterprise/2.14/user/articles/about-issues": "/en/enterprise/2.14/user/articles/about-issues", - "/enterprise/2.14/articles/about-issues": "/en/enterprise/2.14/user/articles/about-issues", - "/en/enterprise/2.14/articles/about-jekyll-themes-on-github": "/en/enterprise/2.14/user/articles/about-jekyll-themes-on-github", - "/enterprise/2.14/user/articles/about-jekyll-themes-on-github": "/en/enterprise/2.14/user/articles/about-jekyll-themes-on-github", - "/enterprise/2.14/articles/about-jekyll-themes-on-github": "/en/enterprise/2.14/user/articles/about-jekyll-themes-on-github", - "/en/enterprise/2.14/articles/about-labels": "/en/enterprise/2.14/user/articles/about-labels", - "/enterprise/2.14/user/articles/about-labels": "/en/enterprise/2.14/user/articles/about-labels", - "/enterprise/2.14/articles/about-labels": "/en/enterprise/2.14/user/articles/about-labels", - "/en/enterprise/2.14/articles/about-merge-conflicts": "/en/enterprise/2.14/user/articles/about-merge-conflicts", - "/enterprise/2.14/user/articles/about-merge-conflicts": "/en/enterprise/2.14/user/articles/about-merge-conflicts", - "/enterprise/2.14/articles/about-merge-conflicts": "/en/enterprise/2.14/user/articles/about-merge-conflicts", - "/en/enterprise/2.14/articles/about-merge-methods-on-github": "/en/enterprise/2.14/user/articles/about-merge-methods-on-github", - "/enterprise/2.14/user/articles/about-merge-methods-on-github": "/en/enterprise/2.14/user/articles/about-merge-methods-on-github", - "/enterprise/2.14/articles/about-merge-methods-on-github": "/en/enterprise/2.14/user/articles/about-merge-methods-on-github", - "/en/enterprise/2.14/articles/about-milestones": "/en/enterprise/2.14/user/articles/about-milestones", - "/enterprise/2.14/user/articles/about-milestones": "/en/enterprise/2.14/user/articles/about-milestones", - "/enterprise/2.14/articles/about-milestones": "/en/enterprise/2.14/user/articles/about-milestones", - "/en/enterprise/2.14/articles/about-notifications": "/en/enterprise/2.14/user/articles/about-notifications", - "/enterprise/2.14/user/articles/about-notifications": "/en/enterprise/2.14/user/articles/about-notifications", - "/enterprise/2.14/articles/about-notifications": "/en/enterprise/2.14/user/articles/about-notifications", - "/en/enterprise/2.14/articles/about-organization-membership": "/en/enterprise/2.14/user/articles/about-organization-membership", - "/enterprise/2.14/user/articles/about-organization-membership": "/en/enterprise/2.14/user/articles/about-organization-membership", - "/enterprise/2.14/articles/about-organization-membership": "/en/enterprise/2.14/user/articles/about-organization-membership", - "/en/enterprise/2.14/articles/about-organizations": "/en/enterprise/2.14/user/articles/about-organizations", - "/enterprise/2.14/user/articles/about-organizations": "/en/enterprise/2.14/user/articles/about-organizations", - "/enterprise/2.14/articles/about-organizations": "/en/enterprise/2.14/user/articles/about-organizations", - "/en/enterprise/2.14/articles/about-project-boards": "/en/enterprise/2.14/user/articles/about-project-boards", - "/enterprise/2.14/user/articles/about-project-boards": "/en/enterprise/2.14/user/articles/about-project-boards", - "/enterprise/2.14/articles/about-project-boards": "/en/enterprise/2.14/user/articles/about-project-boards", - "/en/enterprise/2.14/articles/about-protected-branches": "/en/enterprise/2.14/user/articles/about-protected-branches", - "/enterprise/2.14/user/articles/about-protected-branches": "/en/enterprise/2.14/user/articles/about-protected-branches", - "/enterprise/2.14/articles/about-protected-branches": "/en/enterprise/2.14/user/articles/about-protected-branches", - "/en/enterprise/2.14/articles/about-pull-request-merges": "/en/enterprise/2.14/user/articles/about-pull-request-merges", - "/enterprise/2.14/user/articles/about-pull-request-merges": "/en/enterprise/2.14/user/articles/about-pull-request-merges", - "/enterprise/2.14/articles/about-pull-request-merges": "/en/enterprise/2.14/user/articles/about-pull-request-merges", - "/en/enterprise/2.14/articles/about-pull-request-reviews": "/en/enterprise/2.14/user/articles/about-pull-request-reviews", - "/enterprise/2.14/user/articles/about-pull-request-reviews": "/en/enterprise/2.14/user/articles/about-pull-request-reviews", - "/enterprise/2.14/articles/about-pull-request-reviews": "/en/enterprise/2.14/user/articles/about-pull-request-reviews", - "/en/enterprise/2.14/articles/about-pull-requests": "/en/enterprise/2.14/user/articles/about-pull-requests", - "/enterprise/2.14/user/articles/about-pull-requests": "/en/enterprise/2.14/user/articles/about-pull-requests", - "/enterprise/2.14/articles/about-pull-requests": "/en/enterprise/2.14/user/articles/about-pull-requests", - "/en/enterprise/2.14/articles/about-readmes": "/en/enterprise/2.14/user/articles/about-readmes", - "/enterprise/2.14/user/articles/about-readmes": "/en/enterprise/2.14/user/articles/about-readmes", - "/enterprise/2.14/articles/about-readmes": "/en/enterprise/2.14/user/articles/about-readmes", - "/en/enterprise/2.14/articles/about-releases": "/en/enterprise/2.14/user/articles/about-releases", - "/enterprise/2.14/user/articles/about-releases": "/en/enterprise/2.14/user/articles/about-releases", - "/enterprise/2.14/articles/about-releases": "/en/enterprise/2.14/user/articles/about-releases", - "/en/enterprise/2.14/articles/about-remote-repositories": "/en/enterprise/2.14/user/articles/about-remote-repositories", - "/enterprise/2.14/user/articles/about-remote-repositories": "/en/enterprise/2.14/user/articles/about-remote-repositories", - "/enterprise/2.14/articles/about-remote-repositories": "/en/enterprise/2.14/user/articles/about-remote-repositories", - "/en/enterprise/2.14/articles/about-repositories": "/en/enterprise/2.14/user/articles/about-repositories", - "/enterprise/2.14/user/articles/about-repositories": "/en/enterprise/2.14/user/articles/about-repositories", - "/enterprise/2.14/articles/about-repositories": "/en/enterprise/2.14/user/articles/about-repositories", - "/en/enterprise/2.14/articles/about-repository-graphs": "/en/enterprise/2.14/user/articles/about-repository-graphs", - "/enterprise/2.14/user/articles/about-repository-graphs": "/en/enterprise/2.14/user/articles/about-repository-graphs", - "/enterprise/2.14/articles/about-repository-graphs": "/en/enterprise/2.14/user/articles/about-repository-graphs", - "/en/enterprise/2.14/articles/about-repository-languages": "/en/enterprise/2.14/user/articles/about-repository-languages", - "/enterprise/2.14/user/articles/about-repository-languages": "/en/enterprise/2.14/user/articles/about-repository-languages", - "/enterprise/2.14/articles/about-repository-languages": "/en/enterprise/2.14/user/articles/about-repository-languages", - "/en/enterprise/2.14/articles/about-required-commit-signing": "/en/enterprise/2.14/user/articles/about-required-commit-signing", - "/enterprise/2.14/user/articles/about-required-commit-signing": "/en/enterprise/2.14/user/articles/about-required-commit-signing", - "/enterprise/2.14/articles/about-required-commit-signing": "/en/enterprise/2.14/user/articles/about-required-commit-signing", - "/en/enterprise/2.14/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests", - "/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests", - "/enterprise/2.14/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests", - "/en/enterprise/2.14/articles/about-required-status-checks": "/en/enterprise/2.14/user/articles/about-required-status-checks", - "/enterprise/2.14/user/articles/about-required-status-checks": "/en/enterprise/2.14/user/articles/about-required-status-checks", - "/enterprise/2.14/articles/about-required-status-checks": "/en/enterprise/2.14/user/articles/about-required-status-checks", - "/en/enterprise/2.14/articles/about-saved-replies": "/en/enterprise/2.14/user/articles/about-saved-replies", - "/enterprise/2.14/user/articles/about-saved-replies": "/en/enterprise/2.14/user/articles/about-saved-replies", - "/enterprise/2.14/articles/about-saved-replies": "/en/enterprise/2.14/user/articles/about-saved-replies", - "/en/enterprise/2.14/articles/about-searching-on-github": "/en/enterprise/2.14/user/articles/about-searching-on-github", - "/enterprise/2.14/user/articles/about-searching-on-github": "/en/enterprise/2.14/user/articles/about-searching-on-github", - "/enterprise/2.14/articles/about-searching-on-github": "/en/enterprise/2.14/user/articles/about-searching-on-github", - "/en/enterprise/2.14/articles/about-ssh": "/en/enterprise/2.14/user/articles/about-ssh", - "/enterprise/2.14/user/articles/about-ssh": "/en/enterprise/2.14/user/articles/about-ssh", - "/enterprise/2.14/articles/about-ssh": "/en/enterprise/2.14/user/articles/about-ssh", - "/en/enterprise/2.14/articles/about-status-checks": "/en/enterprise/2.14/user/articles/about-status-checks", - "/enterprise/2.14/user/articles/about-status-checks": "/en/enterprise/2.14/user/articles/about-status-checks", - "/enterprise/2.14/articles/about-status-checks": "/en/enterprise/2.14/user/articles/about-status-checks", - "/en/enterprise/2.14/articles/about-task-lists": "/en/enterprise/2.14/user/articles/about-task-lists", - "/enterprise/2.14/user/articles/about-task-lists": "/en/enterprise/2.14/user/articles/about-task-lists", - "/enterprise/2.14/articles/about-task-lists": "/en/enterprise/2.14/user/articles/about-task-lists", - "/en/enterprise/2.14/articles/about-team-discussions": "/en/enterprise/2.14/user/articles/about-team-discussions", - "/enterprise/2.14/user/articles/about-team-discussions": "/en/enterprise/2.14/user/articles/about-team-discussions", - "/enterprise/2.14/articles/about-team-discussions": "/en/enterprise/2.14/user/articles/about-team-discussions", - "/en/enterprise/2.14/articles/about-teams": "/en/enterprise/2.14/user/articles/about-teams", - "/enterprise/2.14/user/articles/about-teams": "/en/enterprise/2.14/user/articles/about-teams", - "/enterprise/2.14/articles/about-teams": "/en/enterprise/2.14/user/articles/about-teams", - "/en/enterprise/2.14/articles/about-two-factor-authentication": "/en/enterprise/2.14/user/articles/about-two-factor-authentication", - "/enterprise/2.14/user/articles/about-two-factor-authentication": "/en/enterprise/2.14/user/articles/about-two-factor-authentication", - "/enterprise/2.14/articles/about-two-factor-authentication": "/en/enterprise/2.14/user/articles/about-two-factor-authentication", - "/en/enterprise/2.14/articles/about-web-notifications": "/en/enterprise/2.14/user/articles/about-web-notifications", - "/enterprise/2.14/user/articles/about-web-notifications": "/en/enterprise/2.14/user/articles/about-web-notifications", - "/enterprise/2.14/articles/about-web-notifications": "/en/enterprise/2.14/user/articles/about-web-notifications", - "/en/enterprise/2.14/articles/about-webhooks": "/en/enterprise/2.14/user/articles/about-webhooks", - "/enterprise/2.14/user/articles/about-webhooks": "/en/enterprise/2.14/user/articles/about-webhooks", - "/enterprise/2.14/articles/about-webhooks": "/en/enterprise/2.14/user/articles/about-webhooks", - "/en/enterprise/2.14/articles/about-wikis": "/en/enterprise/2.14/user/articles/about-wikis", - "/enterprise/2.14/user/articles/about-wikis": "/en/enterprise/2.14/user/articles/about-wikis", - "/enterprise/2.14/articles/about-wikis": "/en/enterprise/2.14/user/articles/about-wikis", - "/en/enterprise/2.14/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.14/user/articles/about-writing-and-formatting-on-github", - "/enterprise/2.14/user/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.14/user/articles/about-writing-and-formatting-on-github", - "/enterprise/2.14/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.14/user/articles/about-writing-and-formatting-on-github", - "/en/enterprise/2.14/articles/about-your-organization-dashboard": "/en/enterprise/2.14/user/articles/about-your-organization-dashboard", - "/enterprise/2.14/user/articles/about-your-organization-dashboard": "/en/enterprise/2.14/user/articles/about-your-organization-dashboard", - "/enterprise/2.14/articles/about-your-organization-dashboard": "/en/enterprise/2.14/user/articles/about-your-organization-dashboard", - "/en/enterprise/2.14/articles/about-your-organizations-news-feed": "/en/enterprise/2.14/user/articles/about-your-organizations-news-feed", - "/enterprise/2.14/user/articles/about-your-organizations-news-feed": "/en/enterprise/2.14/user/articles/about-your-organizations-news-feed", - "/enterprise/2.14/articles/about-your-organizations-news-feed": "/en/enterprise/2.14/user/articles/about-your-organizations-news-feed", - "/en/enterprise/2.14/articles/about-your-organizations-profile": "/en/enterprise/2.14/user/articles/about-your-organizations-profile", - "/enterprise/2.14/user/articles/about-your-organizations-profile": "/en/enterprise/2.14/user/articles/about-your-organizations-profile", - "/enterprise/2.14/articles/about-your-organizations-profile": "/en/enterprise/2.14/user/articles/about-your-organizations-profile", - "/en/enterprise/2.14/articles/about-your-personal-dashboard": "/en/enterprise/2.14/user/articles/about-your-personal-dashboard", - "/enterprise/2.14/user/articles/about-your-personal-dashboard": "/en/enterprise/2.14/user/articles/about-your-personal-dashboard", - "/enterprise/2.14/articles/about-your-personal-dashboard": "/en/enterprise/2.14/user/articles/about-your-personal-dashboard", - "/en/enterprise/2.14/articles/about-your-profile": "/en/enterprise/2.14/user/articles/about-your-profile", - "/enterprise/2.14/user/articles/about-your-profile": "/en/enterprise/2.14/user/articles/about-your-profile", - "/enterprise/2.14/articles/about-your-profile": "/en/enterprise/2.14/user/articles/about-your-profile", - "/en/enterprise/2.14/articles/access-permissions-on-github": "/en/enterprise/2.14/user/articles/access-permissions-on-github", - "/enterprise/2.14/user/articles/access-permissions-on-github": "/en/enterprise/2.14/user/articles/access-permissions-on-github", - "/enterprise/2.14/articles/access-permissions-on-github": "/en/enterprise/2.14/user/articles/access-permissions-on-github", - "/en/enterprise/2.14/articles/accessing-an-organization": "/en/enterprise/2.14/user/articles/accessing-an-organization", - "/enterprise/2.14/user/articles/accessing-an-organization": "/en/enterprise/2.14/user/articles/accessing-an-organization", - "/enterprise/2.14/articles/accessing-an-organization": "/en/enterprise/2.14/user/articles/accessing-an-organization", - "/en/enterprise/2.14/articles/accessing-basic-repository-data": "/en/enterprise/2.14/user/articles/accessing-basic-repository-data", - "/enterprise/2.14/user/articles/accessing-basic-repository-data": "/en/enterprise/2.14/user/articles/accessing-basic-repository-data", - "/enterprise/2.14/articles/accessing-basic-repository-data": "/en/enterprise/2.14/user/articles/accessing-basic-repository-data", - "/en/enterprise/2.14/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication", - "/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication", - "/enterprise/2.14/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.14/articles/accessing-your-notifications": "/en/enterprise/2.14/user/articles/accessing-your-notifications", - "/enterprise/2.14/user/articles/accessing-your-notifications": "/en/enterprise/2.14/user/articles/accessing-your-notifications", - "/enterprise/2.14/articles/accessing-your-notifications": "/en/enterprise/2.14/user/articles/accessing-your-notifications", - "/en/enterprise/2.14/articles/accessing-your-organizations-settings": "/en/enterprise/2.14/user/articles/accessing-your-organizations-settings", - "/enterprise/2.14/user/articles/accessing-your-organizations-settings": "/en/enterprise/2.14/user/articles/accessing-your-organizations-settings", - "/enterprise/2.14/articles/accessing-your-organizations-settings": "/en/enterprise/2.14/user/articles/accessing-your-organizations-settings", - "/en/enterprise/2.14/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.14/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.14/articles/adding-a-file-to-a-repository": "/en/enterprise/2.14/user/articles/adding-a-file-to-a-repository", - "/enterprise/2.14/user/articles/adding-a-file-to-a-repository": "/en/enterprise/2.14/user/articles/adding-a-file-to-a-repository", - "/enterprise/2.14/articles/adding-a-file-to-a-repository": "/en/enterprise/2.14/user/articles/adding-a-file-to-a-repository", - "/en/enterprise/2.14/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/en/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/en/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/enterprise/2.14/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/en/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/en/enterprise/2.14/articles/adding-a-license-to-a-repository": "/en/enterprise/2.14/user/articles/adding-a-license-to-a-repository", - "/enterprise/2.14/user/articles/adding-a-license-to-a-repository": "/en/enterprise/2.14/user/articles/adding-a-license-to-a-repository", - "/enterprise/2.14/articles/adding-a-license-to-a-repository": "/en/enterprise/2.14/user/articles/adding-a-license-to-a-repository", - "/en/enterprise/2.14/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.14/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.14/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.14/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.14/articles/adding-a-remote": "/en/enterprise/2.14/user/articles/adding-a-remote", - "/enterprise/2.14/user/articles/adding-a-remote": "/en/enterprise/2.14/user/articles/adding-a-remote", - "/enterprise/2.14/articles/adding-a-remote": "/en/enterprise/2.14/user/articles/adding-a-remote", - "/en/enterprise/2.14/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account", - "/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account", - "/enterprise/2.14/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.14/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.14/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.14/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.14/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/en/enterprise/2.14/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.14/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.14/articles/adding-jekyll-plugins-to-a-github-pages-site": "/en/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site": "/en/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/enterprise/2.14/articles/adding-jekyll-plugins-to-a-github-pages-site": "/en/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/en/enterprise/2.14/articles/adding-notes-to-a-project-board": "/en/enterprise/2.14/user/articles/adding-notes-to-a-project-board", - "/enterprise/2.14/user/articles/adding-notes-to-a-project-board": "/en/enterprise/2.14/user/articles/adding-notes-to-a-project-board", - "/enterprise/2.14/articles/adding-notes-to-a-project-board": "/en/enterprise/2.14/user/articles/adding-notes-to-a-project-board", - "/en/enterprise/2.14/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.14/user/articles/adding-or-editing-wiki-pages", - "/enterprise/2.14/user/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.14/user/articles/adding-or-editing-wiki-pages", - "/enterprise/2.14/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.14/user/articles/adding-or-editing-wiki-pages", - "/en/enterprise/2.14/articles/adding-organization-members-to-a-team": "/en/enterprise/2.14/user/articles/adding-organization-members-to-a-team", - "/enterprise/2.14/user/articles/adding-organization-members-to-a-team": "/en/enterprise/2.14/user/articles/adding-organization-members-to-a-team", - "/enterprise/2.14/articles/adding-organization-members-to-a-team": "/en/enterprise/2.14/user/articles/adding-organization-members-to-a-team", - "/en/enterprise/2.14/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.14/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.14/articles/adding-people-to-your-organization": "/en/enterprise/2.14/user/articles/adding-people-to-your-organization", - "/enterprise/2.14/user/articles/adding-people-to-your-organization": "/en/enterprise/2.14/user/articles/adding-people-to-your-organization", - "/enterprise/2.14/articles/adding-people-to-your-organization": "/en/enterprise/2.14/user/articles/adding-people-to-your-organization", - "/en/enterprise/2.14/articles/adding-support-resources-to-your-project": "/en/enterprise/2.14/user/articles/adding-support-resources-to-your-project", - "/enterprise/2.14/user/articles/adding-support-resources-to-your-project": "/en/enterprise/2.14/user/articles/adding-support-resources-to-your-project", - "/enterprise/2.14/articles/adding-support-resources-to-your-project": "/en/enterprise/2.14/user/articles/adding-support-resources-to-your-project", - "/en/enterprise/2.14/articles/additional-customizations-for-github-pages": "/en/enterprise/2.14/user/articles/additional-customizations-for-github-pages", - "/enterprise/2.14/user/articles/additional-customizations-for-github-pages": "/en/enterprise/2.14/user/articles/additional-customizations-for-github-pages", - "/enterprise/2.14/articles/additional-customizations-for-github-pages": "/en/enterprise/2.14/user/articles/additional-customizations-for-github-pages", - "/en/enterprise/2.14/articles/addressing-merge-conflicts": "/en/enterprise/2.14/user/articles/addressing-merge-conflicts", - "/enterprise/2.14/user/articles/addressing-merge-conflicts": "/en/enterprise/2.14/user/articles/addressing-merge-conflicts", - "/enterprise/2.14/articles/addressing-merge-conflicts": "/en/enterprise/2.14/user/articles/addressing-merge-conflicts", - "/en/enterprise/2.14/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.14/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.14/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.14/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/en/enterprise/2.14/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.14/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/en/enterprise/2.14/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.14/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.14/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.14/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.14/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews", - "/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews", - "/enterprise/2.14/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.14/articles/archiving-a-github-repository": "/en/enterprise/2.14/user/articles/archiving-a-github-repository", - "/enterprise/2.14/user/articles/archiving-a-github-repository": "/en/enterprise/2.14/user/articles/archiving-a-github-repository", - "/enterprise/2.14/articles/archiving-a-github-repository": "/en/enterprise/2.14/user/articles/archiving-a-github-repository", - "/en/enterprise/2.14/articles/archiving-repositories": "/en/enterprise/2.14/user/articles/archiving-repositories", - "/enterprise/2.14/user/articles/archiving-repositories": "/en/enterprise/2.14/user/articles/archiving-repositories", - "/enterprise/2.14/articles/archiving-repositories": "/en/enterprise/2.14/user/articles/archiving-repositories", - "/en/enterprise/2.14/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.14/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.14/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key", - "/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key", - "/enterprise/2.14/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.14/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.14/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.14/articles/associating-text-editors-with-git": "/en/enterprise/2.14/user/articles/associating-text-editors-with-git", - "/enterprise/2.14/user/articles/associating-text-editors-with-git": "/en/enterprise/2.14/user/articles/associating-text-editors-with-git", - "/enterprise/2.14/articles/associating-text-editors-with-git": "/en/enterprise/2.14/user/articles/associating-text-editors-with-git", - "/en/enterprise/2.14/articles/authorizing-oauth-apps": "/en/enterprise/2.14/user/articles/authorizing-oauth-apps", - "/enterprise/2.14/user/articles/authorizing-oauth-apps": "/en/enterprise/2.14/user/articles/authorizing-oauth-apps", - "/enterprise/2.14/articles/authorizing-oauth-apps": "/en/enterprise/2.14/user/articles/authorizing-oauth-apps", - "/en/enterprise/2.14/articles/autolinked-references-and-urls": "/en/enterprise/2.14/user/articles/autolinked-references-and-urls", - "/enterprise/2.14/user/articles/autolinked-references-and-urls": "/en/enterprise/2.14/user/articles/autolinked-references-and-urls", - "/enterprise/2.14/articles/autolinked-references-and-urls": "/en/enterprise/2.14/user/articles/autolinked-references-and-urls", - "/en/enterprise/2.14/articles/backing-up-a-repository": "/en/enterprise/2.14/user/articles/backing-up-a-repository", - "/enterprise/2.14/user/articles/backing-up-a-repository": "/en/enterprise/2.14/user/articles/backing-up-a-repository", - "/enterprise/2.14/articles/backing-up-a-repository": "/en/enterprise/2.14/user/articles/backing-up-a-repository", - "/en/enterprise/2.14/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax", - "/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax", - "/enterprise/2.14/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax", - "/en/enterprise/2.14/articles/be-social": "/en/enterprise/2.14/user/articles/be-social", - "/enterprise/2.14/user/articles/be-social": "/en/enterprise/2.14/user/articles/be-social", - "/enterprise/2.14/articles/be-social": "/en/enterprise/2.14/user/articles/be-social", - "/en/enterprise/2.14/articles/caching-your-github-password-in-git": "/en/enterprise/2.14/user/articles/caching-your-github-password-in-git", - "/enterprise/2.14/user/articles/caching-your-github-password-in-git": "/en/enterprise/2.14/user/articles/caching-your-github-password-in-git", - "/enterprise/2.14/articles/caching-your-github-password-in-git": "/en/enterprise/2.14/user/articles/caching-your-github-password-in-git", - "/en/enterprise/2.14/articles/changing-a-commit-message": "/en/enterprise/2.14/user/articles/changing-a-commit-message", - "/enterprise/2.14/user/articles/changing-a-commit-message": "/en/enterprise/2.14/user/articles/changing-a-commit-message", - "/enterprise/2.14/articles/changing-a-commit-message": "/en/enterprise/2.14/user/articles/changing-a-commit-message", - "/en/enterprise/2.14/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.14/user/articles/changing-a-persons-role-to-owner", - "/enterprise/2.14/user/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.14/user/articles/changing-a-persons-role-to-owner", - "/enterprise/2.14/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.14/user/articles/changing-a-persons-role-to-owner", - "/en/enterprise/2.14/articles/changing-a-remotes-url": "/en/enterprise/2.14/user/articles/changing-a-remotes-url", - "/enterprise/2.14/user/articles/changing-a-remotes-url": "/en/enterprise/2.14/user/articles/changing-a-remotes-url", - "/enterprise/2.14/articles/changing-a-remotes-url": "/en/enterprise/2.14/user/articles/changing-a-remotes-url", - "/en/enterprise/2.14/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.14/user/articles/changing-access-permissions-for-wikis", - "/enterprise/2.14/user/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.14/user/articles/changing-access-permissions-for-wikis", - "/enterprise/2.14/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.14/user/articles/changing-access-permissions-for-wikis", - "/en/enterprise/2.14/articles/changing-author-info": "/en/enterprise/2.14/user/articles/changing-author-info", - "/enterprise/2.14/user/articles/changing-author-info": "/en/enterprise/2.14/user/articles/changing-author-info", - "/enterprise/2.14/articles/changing-author-info": "/en/enterprise/2.14/user/articles/changing-author-info", - "/en/enterprise/2.14/articles/changing-project-board-visibility": "/en/enterprise/2.14/user/articles/changing-project-board-visibility", - "/enterprise/2.14/user/articles/changing-project-board-visibility": "/en/enterprise/2.14/user/articles/changing-project-board-visibility", - "/enterprise/2.14/articles/changing-project-board-visibility": "/en/enterprise/2.14/user/articles/changing-project-board-visibility", - "/en/enterprise/2.14/articles/changing-team-visibility": "/en/enterprise/2.14/user/articles/changing-team-visibility", - "/enterprise/2.14/user/articles/changing-team-visibility": "/en/enterprise/2.14/user/articles/changing-team-visibility", - "/enterprise/2.14/articles/changing-team-visibility": "/en/enterprise/2.14/user/articles/changing-team-visibility", - "/en/enterprise/2.14/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.14/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.14/articles/changing-your-github-username": "/en/enterprise/2.14/user/articles/changing-your-github-username", - "/enterprise/2.14/user/articles/changing-your-github-username": "/en/enterprise/2.14/user/articles/changing-your-github-username", - "/enterprise/2.14/articles/changing-your-github-username": "/en/enterprise/2.14/user/articles/changing-your-github-username", - "/en/enterprise/2.14/articles/changing-your-primary-email-address": "/en/enterprise/2.14/user/articles/changing-your-primary-email-address", - "/enterprise/2.14/user/articles/changing-your-primary-email-address": "/en/enterprise/2.14/user/articles/changing-your-primary-email-address", - "/enterprise/2.14/articles/changing-your-primary-email-address": "/en/enterprise/2.14/user/articles/changing-your-primary-email-address", - "/en/enterprise/2.14/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.14/user/articles/checking-for-existing-gpg-keys", - "/enterprise/2.14/user/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.14/user/articles/checking-for-existing-gpg-keys", - "/enterprise/2.14/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.14/user/articles/checking-for-existing-gpg-keys", - "/en/enterprise/2.14/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.14/user/articles/checking-for-existing-ssh-keys", - "/enterprise/2.14/user/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.14/user/articles/checking-for-existing-ssh-keys", - "/enterprise/2.14/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.14/user/articles/checking-for-existing-ssh-keys", - "/en/enterprise/2.14/articles/checking-out-pull-requests-locally": "/en/enterprise/2.14/user/articles/checking-out-pull-requests-locally", - "/enterprise/2.14/user/articles/checking-out-pull-requests-locally": "/en/enterprise/2.14/user/articles/checking-out-pull-requests-locally", - "/enterprise/2.14/articles/checking-out-pull-requests-locally": "/en/enterprise/2.14/user/articles/checking-out-pull-requests-locally", - "/en/enterprise/2.14/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.14/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.14/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.14/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.14/articles/classifying-your-repository-with-topics": "/en/enterprise/2.14/user/articles/classifying-your-repository-with-topics", - "/enterprise/2.14/user/articles/classifying-your-repository-with-topics": "/en/enterprise/2.14/user/articles/classifying-your-repository-with-topics", - "/enterprise/2.14/articles/classifying-your-repository-with-topics": "/en/enterprise/2.14/user/articles/classifying-your-repository-with-topics", - "/en/enterprise/2.14/articles/cloning-a-repository-from-github": "/en/enterprise/2.14/user/articles/cloning-a-repository-from-github", - "/enterprise/2.14/user/articles/cloning-a-repository-from-github": "/en/enterprise/2.14/user/articles/cloning-a-repository-from-github", - "/enterprise/2.14/articles/cloning-a-repository-from-github": "/en/enterprise/2.14/user/articles/cloning-a-repository-from-github", - "/en/enterprise/2.14/articles/cloning-a-repository": "/en/enterprise/2.14/user/articles/cloning-a-repository", - "/enterprise/2.14/user/articles/cloning-a-repository": "/en/enterprise/2.14/user/articles/cloning-a-repository", - "/enterprise/2.14/articles/cloning-a-repository": "/en/enterprise/2.14/user/articles/cloning-a-repository", - "/en/enterprise/2.14/articles/closing-a-project-board": "/en/enterprise/2.14/user/articles/closing-a-project-board", - "/enterprise/2.14/user/articles/closing-a-project-board": "/en/enterprise/2.14/user/articles/closing-a-project-board", - "/enterprise/2.14/articles/closing-a-project-board": "/en/enterprise/2.14/user/articles/closing-a-project-board", - "/en/enterprise/2.14/articles/closing-a-pull-request": "/en/enterprise/2.14/user/articles/closing-a-pull-request", - "/enterprise/2.14/user/articles/closing-a-pull-request": "/en/enterprise/2.14/user/articles/closing-a-pull-request", - "/enterprise/2.14/articles/closing-a-pull-request": "/en/enterprise/2.14/user/articles/closing-a-pull-request", - "/en/enterprise/2.14/articles/closing-issues-using-keywords": "/en/enterprise/2.14/user/articles/closing-issues-using-keywords", - "/enterprise/2.14/user/articles/closing-issues-using-keywords": "/en/enterprise/2.14/user/articles/closing-issues-using-keywords", - "/enterprise/2.14/articles/closing-issues-using-keywords": "/en/enterprise/2.14/user/articles/closing-issues-using-keywords", - "/en/enterprise/2.14/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/en/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/en/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/enterprise/2.14/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/en/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/en/enterprise/2.14/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations", - "/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations", - "/enterprise/2.14/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations", - "/en/enterprise/2.14/articles/collaborating-with-your-team": "/en/enterprise/2.14/user/articles/collaborating-with-your-team", - "/enterprise/2.14/user/articles/collaborating-with-your-team": "/en/enterprise/2.14/user/articles/collaborating-with-your-team", - "/enterprise/2.14/articles/collaborating-with-your-team": "/en/enterprise/2.14/user/articles/collaborating-with-your-team", - "/en/enterprise/2.14/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage", - "/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage", - "/enterprise/2.14/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage", - "/en/enterprise/2.14/articles/commenting-on-a-pull-request": "/en/enterprise/2.14/user/articles/commenting-on-a-pull-request", - "/enterprise/2.14/user/articles/commenting-on-a-pull-request": "/en/enterprise/2.14/user/articles/commenting-on-a-pull-request", - "/enterprise/2.14/articles/commenting-on-a-pull-request": "/en/enterprise/2.14/user/articles/commenting-on-a-pull-request", - "/en/enterprise/2.14/articles/commit-branch-and-tag-labels": "/en/enterprise/2.14/user/articles/commit-branch-and-tag-labels", - "/enterprise/2.14/user/articles/commit-branch-and-tag-labels": "/en/enterprise/2.14/user/articles/commit-branch-and-tag-labels", - "/enterprise/2.14/articles/commit-branch-and-tag-labels": "/en/enterprise/2.14/user/articles/commit-branch-and-tag-labels", - "/en/enterprise/2.14/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.14/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.14/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.14/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.14/articles/comparing-commits-across-time": "/en/enterprise/2.14/user/articles/comparing-commits-across-time", - "/enterprise/2.14/user/articles/comparing-commits-across-time": "/en/enterprise/2.14/user/articles/comparing-commits-across-time", - "/enterprise/2.14/articles/comparing-commits-across-time": "/en/enterprise/2.14/user/articles/comparing-commits-across-time", - "/en/enterprise/2.14/articles/conditions-for-large-files": "/en/enterprise/2.14/user/articles/conditions-for-large-files", - "/enterprise/2.14/user/articles/conditions-for-large-files": "/en/enterprise/2.14/user/articles/conditions-for-large-files", - "/enterprise/2.14/articles/conditions-for-large-files": "/en/enterprise/2.14/user/articles/conditions-for-large-files", - "/en/enterprise/2.14/articles/configuring-a-publishing-source-for-github-pages": "/en/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages", - "/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages": "/en/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages", - "/enterprise/2.14/articles/configuring-a-publishing-source-for-github-pages": "/en/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages", - "/en/enterprise/2.14/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork", - "/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork", - "/enterprise/2.14/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork", - "/en/enterprise/2.14/articles/configuring-automation-for-project-boards": "/en/enterprise/2.14/user/articles/configuring-automation-for-project-boards", - "/enterprise/2.14/user/articles/configuring-automation-for-project-boards": "/en/enterprise/2.14/user/articles/configuring-automation-for-project-boards", - "/enterprise/2.14/articles/configuring-automation-for-project-boards": "/en/enterprise/2.14/user/articles/configuring-automation-for-project-boards", - "/en/enterprise/2.14/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.14/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.14/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.14/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.14/articles/configuring-git-large-file-storage": "/en/enterprise/2.14/user/articles/configuring-git-large-file-storage", - "/enterprise/2.14/user/articles/configuring-git-large-file-storage": "/en/enterprise/2.14/user/articles/configuring-git-large-file-storage", - "/enterprise/2.14/articles/configuring-git-large-file-storage": "/en/enterprise/2.14/user/articles/configuring-git-large-file-storage", - "/en/enterprise/2.14/articles/configuring-git-to-handle-line-endings": "/en/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings", - "/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings": "/en/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings", - "/enterprise/2.14/articles/configuring-git-to-handle-line-endings": "/en/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings", - "/en/enterprise/2.14/articles/configuring-jekyll-plugins": "/en/enterprise/2.14/user/articles/configuring-jekyll-plugins", - "/enterprise/2.14/user/articles/configuring-jekyll-plugins": "/en/enterprise/2.14/user/articles/configuring-jekyll-plugins", - "/enterprise/2.14/articles/configuring-jekyll-plugins": "/en/enterprise/2.14/user/articles/configuring-jekyll-plugins", - "/en/enterprise/2.14/articles/configuring-jekyll": "/en/enterprise/2.14/user/articles/configuring-jekyll", - "/enterprise/2.14/user/articles/configuring-jekyll": "/en/enterprise/2.14/user/articles/configuring-jekyll", - "/enterprise/2.14/articles/configuring-jekyll": "/en/enterprise/2.14/user/articles/configuring-jekyll", - "/en/enterprise/2.14/articles/configuring-protected-branches": "/en/enterprise/2.14/user/articles/configuring-protected-branches", - "/enterprise/2.14/user/articles/configuring-protected-branches": "/en/enterprise/2.14/user/articles/configuring-protected-branches", - "/enterprise/2.14/articles/configuring-protected-branches": "/en/enterprise/2.14/user/articles/configuring-protected-branches", - "/en/enterprise/2.14/articles/configuring-pull-request-merges": "/en/enterprise/2.14/user/articles/configuring-pull-request-merges", - "/enterprise/2.14/user/articles/configuring-pull-request-merges": "/en/enterprise/2.14/user/articles/configuring-pull-request-merges", - "/enterprise/2.14/articles/configuring-pull-request-merges": "/en/enterprise/2.14/user/articles/configuring-pull-request-merges", - "/en/enterprise/2.14/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.14/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.14/articles/configuring-two-factor-authentication": "/en/enterprise/2.14/user/articles/configuring-two-factor-authentication", - "/enterprise/2.14/user/articles/configuring-two-factor-authentication": "/en/enterprise/2.14/user/articles/configuring-two-factor-authentication", - "/enterprise/2.14/articles/configuring-two-factor-authentication": "/en/enterprise/2.14/user/articles/configuring-two-factor-authentication", - "/en/enterprise/2.14/articles/connecting-to-github-with-ssh": "/en/enterprise/2.14/user/articles/connecting-to-github-with-ssh", - "/enterprise/2.14/user/articles/connecting-to-github-with-ssh": "/en/enterprise/2.14/user/articles/connecting-to-github-with-ssh", - "/enterprise/2.14/articles/connecting-to-github-with-ssh": "/en/enterprise/2.14/user/articles/connecting-to-github-with-ssh", - "/en/enterprise/2.14/articles/connecting-with-third-party-applications": "/en/enterprise/2.14/user/articles/connecting-with-third-party-applications", - "/enterprise/2.14/user/articles/connecting-with-third-party-applications": "/en/enterprise/2.14/user/articles/connecting-with-third-party-applications", - "/enterprise/2.14/articles/connecting-with-third-party-applications": "/en/enterprise/2.14/user/articles/connecting-with-third-party-applications", - "/en/enterprise/2.14/articles/converting-a-user-into-an-organization": "/en/enterprise/2.14/user/articles/converting-a-user-into-an-organization", - "/enterprise/2.14/user/articles/converting-a-user-into-an-organization": "/en/enterprise/2.14/user/articles/converting-a-user-into-an-organization", - "/enterprise/2.14/articles/converting-a-user-into-an-organization": "/en/enterprise/2.14/user/articles/converting-a-user-into-an-organization", - "/en/enterprise/2.14/articles/converting-an-organization-into-a-user": "/en/enterprise/2.14/user/articles/converting-an-organization-into-a-user", - "/enterprise/2.14/user/articles/converting-an-organization-into-a-user": "/en/enterprise/2.14/user/articles/converting-an-organization-into-a-user", - "/enterprise/2.14/articles/converting-an-organization-into-a-user": "/en/enterprise/2.14/user/articles/converting-an-organization-into-a-user", - "/en/enterprise/2.14/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.14/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.14/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.14/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.14/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions", - "/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions", - "/enterprise/2.14/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions", - "/en/enterprise/2.14/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions", - "/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions", - "/enterprise/2.14/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions", - "/en/enterprise/2.14/articles/create-a-repo": "/en/enterprise/2.14/user/articles/create-a-repo", - "/enterprise/2.14/user/articles/create-a-repo": "/en/enterprise/2.14/user/articles/create-a-repo", - "/enterprise/2.14/articles/create-a-repo": "/en/enterprise/2.14/user/articles/create-a-repo", - "/en/enterprise/2.14/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors", - "/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors", - "/enterprise/2.14/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.14/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.14/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.14/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.14/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.14/articles/creating-a-label": "/en/enterprise/2.14/user/articles/creating-a-label", - "/enterprise/2.14/user/articles/creating-a-label": "/en/enterprise/2.14/user/articles/creating-a-label", - "/enterprise/2.14/articles/creating-a-label": "/en/enterprise/2.14/user/articles/creating-a-label", - "/en/enterprise/2.14/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch", - "/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch", - "/enterprise/2.14/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch", - "/en/enterprise/2.14/articles/creating-a-new-repository": "/en/enterprise/2.14/user/articles/creating-a-new-repository", - "/enterprise/2.14/user/articles/creating-a-new-repository": "/en/enterprise/2.14/user/articles/creating-a-new-repository", - "/enterprise/2.14/articles/creating-a-new-repository": "/en/enterprise/2.14/user/articles/creating-a-new-repository", - "/en/enterprise/2.14/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.14/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.14/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.14/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.14/articles/creating-a-project-board": "/en/enterprise/2.14/user/articles/creating-a-project-board", - "/enterprise/2.14/user/articles/creating-a-project-board": "/en/enterprise/2.14/user/articles/creating-a-project-board", - "/enterprise/2.14/articles/creating-a-project-board": "/en/enterprise/2.14/user/articles/creating-a-project-board", - "/en/enterprise/2.14/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork", - "/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork", - "/enterprise/2.14/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.14/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.14/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.14/articles/creating-a-pull-request": "/en/enterprise/2.14/user/articles/creating-a-pull-request", - "/enterprise/2.14/user/articles/creating-a-pull-request": "/en/enterprise/2.14/user/articles/creating-a-pull-request", - "/enterprise/2.14/articles/creating-a-pull-request": "/en/enterprise/2.14/user/articles/creating-a-pull-request", - "/en/enterprise/2.14/articles/creating-a-repository-on-github": "/en/enterprise/2.14/user/articles/creating-a-repository-on-github", - "/enterprise/2.14/user/articles/creating-a-repository-on-github": "/en/enterprise/2.14/user/articles/creating-a-repository-on-github", - "/enterprise/2.14/articles/creating-a-repository-on-github": "/en/enterprise/2.14/user/articles/creating-a-repository-on-github", - "/en/enterprise/2.14/articles/creating-a-saved-reply": "/en/enterprise/2.14/user/articles/creating-a-saved-reply", - "/enterprise/2.14/user/articles/creating-a-saved-reply": "/en/enterprise/2.14/user/articles/creating-a-saved-reply", - "/enterprise/2.14/articles/creating-a-saved-reply": "/en/enterprise/2.14/user/articles/creating-a-saved-reply", - "/en/enterprise/2.14/articles/creating-a-strong-password": "/en/enterprise/2.14/user/articles/creating-a-strong-password", - "/enterprise/2.14/user/articles/creating-a-strong-password": "/en/enterprise/2.14/user/articles/creating-a-strong-password", - "/enterprise/2.14/articles/creating-a-strong-password": "/en/enterprise/2.14/user/articles/creating-a-strong-password", - "/en/enterprise/2.14/articles/creating-a-team-discussion": "/en/enterprise/2.14/user/articles/creating-a-team-discussion", - "/enterprise/2.14/user/articles/creating-a-team-discussion": "/en/enterprise/2.14/user/articles/creating-a-team-discussion", - "/enterprise/2.14/articles/creating-a-team-discussion": "/en/enterprise/2.14/user/articles/creating-a-team-discussion", - "/en/enterprise/2.14/articles/creating-a-team": "/en/enterprise/2.14/user/articles/creating-a-team", - "/enterprise/2.14/user/articles/creating-a-team": "/en/enterprise/2.14/user/articles/creating-a-team", - "/enterprise/2.14/articles/creating-a-team": "/en/enterprise/2.14/user/articles/creating-a-team", - "/en/enterprise/2.14/articles/creating-an-issue": "/en/enterprise/2.14/user/articles/creating-an-issue", - "/enterprise/2.14/user/articles/creating-an-issue": "/en/enterprise/2.14/user/articles/creating-an-issue", - "/enterprise/2.14/articles/creating-an-issue": "/en/enterprise/2.14/user/articles/creating-an-issue", - "/en/enterprise/2.14/articles/creating-an-issues-only-repository": "/en/enterprise/2.14/user/articles/creating-an-issues-only-repository", - "/enterprise/2.14/user/articles/creating-an-issues-only-repository": "/en/enterprise/2.14/user/articles/creating-an-issues-only-repository", - "/enterprise/2.14/articles/creating-an-issues-only-repository": "/en/enterprise/2.14/user/articles/creating-an-issues-only-repository", - "/en/enterprise/2.14/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.14/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.14/articles/creating-and-editing-commits": "/en/enterprise/2.14/user/articles/creating-and-editing-commits", - "/enterprise/2.14/user/articles/creating-and-editing-commits": "/en/enterprise/2.14/user/articles/creating-and-editing-commits", - "/enterprise/2.14/articles/creating-and-editing-commits": "/en/enterprise/2.14/user/articles/creating-and-editing-commits", - "/en/enterprise/2.14/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.14/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.14/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks", - "/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks", - "/enterprise/2.14/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks", - "/en/enterprise/2.14/articles/creating-gists": "/en/enterprise/2.14/user/articles/creating-gists", - "/enterprise/2.14/user/articles/creating-gists": "/en/enterprise/2.14/user/articles/creating-gists", - "/enterprise/2.14/articles/creating-gists": "/en/enterprise/2.14/user/articles/creating-gists", - "/en/enterprise/2.14/articles/creating-issue-templates-for-your-repository": "/en/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository", - "/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository": "/en/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository", - "/enterprise/2.14/articles/creating-issue-templates-for-your-repository": "/en/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository", - "/en/enterprise/2.14/articles/creating-new-files": "/en/enterprise/2.14/user/articles/creating-new-files", - "/enterprise/2.14/user/articles/creating-new-files": "/en/enterprise/2.14/user/articles/creating-new-files", - "/enterprise/2.14/articles/creating-new-files": "/en/enterprise/2.14/user/articles/creating-new-files", - "/en/enterprise/2.14/articles/creating-pages-with-the-automatic-generator": "/en/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator", - "/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator": "/en/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator", - "/enterprise/2.14/articles/creating-pages-with-the-automatic-generator": "/en/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator", - "/en/enterprise/2.14/articles/creating-project-pages-using-the-command-line": "/en/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line", - "/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line": "/en/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line", - "/enterprise/2.14/articles/creating-project-pages-using-the-command-line": "/en/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line", - "/en/enterprise/2.14/articles/creating-releases": "/en/enterprise/2.14/user/articles/creating-releases", - "/enterprise/2.14/user/articles/creating-releases": "/en/enterprise/2.14/user/articles/creating-releases", - "/enterprise/2.14/articles/creating-releases": "/en/enterprise/2.14/user/articles/creating-releases", - "/en/enterprise/2.14/articles/customizing-css-and-html-in-your-jekyll-theme": "/en/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme": "/en/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/enterprise/2.14/articles/customizing-css-and-html-in-your-jekyll-theme": "/en/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/en/enterprise/2.14/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github", - "/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github", - "/enterprise/2.14/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.14/articles/customizing-your-profile": "/en/enterprise/2.14/user/articles/customizing-your-profile", - "/enterprise/2.14/user/articles/customizing-your-profile": "/en/enterprise/2.14/user/articles/customizing-your-profile", - "/enterprise/2.14/articles/customizing-your-profile": "/en/enterprise/2.14/user/articles/customizing-your-profile", - "/en/enterprise/2.14/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors", - "/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors", - "/enterprise/2.14/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.14/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests", - "/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests", - "/enterprise/2.14/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.14/articles/deleting-a-label": "/en/enterprise/2.14/user/articles/deleting-a-label", - "/enterprise/2.14/user/articles/deleting-a-label": "/en/enterprise/2.14/user/articles/deleting-a-label", - "/enterprise/2.14/articles/deleting-a-label": "/en/enterprise/2.14/user/articles/deleting-a-label", - "/en/enterprise/2.14/articles/deleting-a-project-board": "/en/enterprise/2.14/user/articles/deleting-a-project-board", - "/enterprise/2.14/user/articles/deleting-a-project-board": "/en/enterprise/2.14/user/articles/deleting-a-project-board", - "/enterprise/2.14/articles/deleting-a-project-board": "/en/enterprise/2.14/user/articles/deleting-a-project-board", - "/en/enterprise/2.14/articles/deleting-a-repository": "/en/enterprise/2.14/user/articles/deleting-a-repository", - "/enterprise/2.14/user/articles/deleting-a-repository": "/en/enterprise/2.14/user/articles/deleting-a-repository", - "/enterprise/2.14/articles/deleting-a-repository": "/en/enterprise/2.14/user/articles/deleting-a-repository", - "/en/enterprise/2.14/articles/deleting-a-saved-reply": "/en/enterprise/2.14/user/articles/deleting-a-saved-reply", - "/enterprise/2.14/user/articles/deleting-a-saved-reply": "/en/enterprise/2.14/user/articles/deleting-a-saved-reply", - "/enterprise/2.14/articles/deleting-a-saved-reply": "/en/enterprise/2.14/user/articles/deleting-a-saved-reply", - "/en/enterprise/2.14/articles/deleting-a-team": "/en/enterprise/2.14/user/articles/deleting-a-team", - "/enterprise/2.14/user/articles/deleting-a-team": "/en/enterprise/2.14/user/articles/deleting-a-team", - "/enterprise/2.14/articles/deleting-a-team": "/en/enterprise/2.14/user/articles/deleting-a-team", - "/en/enterprise/2.14/articles/deleting-an-organization-account": "/en/enterprise/2.14/user/articles/deleting-an-organization-account", - "/enterprise/2.14/user/articles/deleting-an-organization-account": "/en/enterprise/2.14/user/articles/deleting-an-organization-account", - "/enterprise/2.14/articles/deleting-an-organization-account": "/en/enterprise/2.14/user/articles/deleting-an-organization-account", - "/en/enterprise/2.14/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.14/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.14/articles/deleting-files": "/en/enterprise/2.14/user/articles/deleting-files", - "/enterprise/2.14/user/articles/deleting-files": "/en/enterprise/2.14/user/articles/deleting-files", - "/enterprise/2.14/articles/deleting-files": "/en/enterprise/2.14/user/articles/deleting-files", - "/en/enterprise/2.14/articles/deleting-your-user-account": "/en/enterprise/2.14/user/articles/deleting-your-user-account", - "/enterprise/2.14/user/articles/deleting-your-user-account": "/en/enterprise/2.14/user/articles/deleting-your-user-account", - "/enterprise/2.14/articles/deleting-your-user-account": "/en/enterprise/2.14/user/articles/deleting-your-user-account", - "/en/enterprise/2.14/articles/differences-between-commit-views": "/en/enterprise/2.14/user/articles/differences-between-commit-views", - "/enterprise/2.14/user/articles/differences-between-commit-views": "/en/enterprise/2.14/user/articles/differences-between-commit-views", - "/enterprise/2.14/articles/differences-between-commit-views": "/en/enterprise/2.14/user/articles/differences-between-commit-views", - "/en/enterprise/2.14/articles/disabling-issues": "/en/enterprise/2.14/user/articles/disabling-issues", - "/enterprise/2.14/user/articles/disabling-issues": "/en/enterprise/2.14/user/articles/disabling-issues", - "/enterprise/2.14/articles/disabling-issues": "/en/enterprise/2.14/user/articles/disabling-issues", - "/en/enterprise/2.14/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository", - "/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository", - "/enterprise/2.14/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository", - "/en/enterprise/2.14/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization", - "/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization", - "/enterprise/2.14/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization", - "/en/enterprise/2.14/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization", - "/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization", - "/enterprise/2.14/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.14/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.14/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.14/articles/disabling-wikis": "/en/enterprise/2.14/user/articles/disabling-wikis", - "/enterprise/2.14/user/articles/disabling-wikis": "/en/enterprise/2.14/user/articles/disabling-wikis", - "/enterprise/2.14/articles/disabling-wikis": "/en/enterprise/2.14/user/articles/disabling-wikis", - "/en/enterprise/2.14/articles/dismissing-a-pull-request-review": "/en/enterprise/2.14/user/articles/dismissing-a-pull-request-review", - "/enterprise/2.14/user/articles/dismissing-a-pull-request-review": "/en/enterprise/2.14/user/articles/dismissing-a-pull-request-review", - "/enterprise/2.14/articles/dismissing-a-pull-request-review": "/en/enterprise/2.14/user/articles/dismissing-a-pull-request-review", - "/en/enterprise/2.14/articles/distributing-large-binaries": "/en/enterprise/2.14/user/articles/distributing-large-binaries", - "/enterprise/2.14/user/articles/distributing-large-binaries": "/en/enterprise/2.14/user/articles/distributing-large-binaries", - "/enterprise/2.14/articles/distributing-large-binaries": "/en/enterprise/2.14/user/articles/distributing-large-binaries", - "/en/enterprise/2.14/articles/documenting-your-project-with-wikis": "/en/enterprise/2.14/user/articles/documenting-your-project-with-wikis", - "/enterprise/2.14/user/articles/documenting-your-project-with-wikis": "/en/enterprise/2.14/user/articles/documenting-your-project-with-wikis", - "/enterprise/2.14/articles/documenting-your-project-with-wikis": "/en/enterprise/2.14/user/articles/documenting-your-project-with-wikis", - "/en/enterprise/2.14/articles/duplicating-a-repository": "/en/enterprise/2.14/user/articles/duplicating-a-repository", - "/enterprise/2.14/user/articles/duplicating-a-repository": "/en/enterprise/2.14/user/articles/duplicating-a-repository", - "/enterprise/2.14/articles/duplicating-a-repository": "/en/enterprise/2.14/user/articles/duplicating-a-repository", - "/en/enterprise/2.14/articles/editing-a-label": "/en/enterprise/2.14/user/articles/editing-a-label", - "/enterprise/2.14/user/articles/editing-a-label": "/en/enterprise/2.14/user/articles/editing-a-label", - "/enterprise/2.14/articles/editing-a-label": "/en/enterprise/2.14/user/articles/editing-a-label", - "/en/enterprise/2.14/articles/editing-a-project-board": "/en/enterprise/2.14/user/articles/editing-a-project-board", - "/enterprise/2.14/user/articles/editing-a-project-board": "/en/enterprise/2.14/user/articles/editing-a-project-board", - "/enterprise/2.14/articles/editing-a-project-board": "/en/enterprise/2.14/user/articles/editing-a-project-board", - "/en/enterprise/2.14/articles/editing-a-saved-reply": "/en/enterprise/2.14/user/articles/editing-a-saved-reply", - "/enterprise/2.14/user/articles/editing-a-saved-reply": "/en/enterprise/2.14/user/articles/editing-a-saved-reply", - "/enterprise/2.14/articles/editing-a-saved-reply": "/en/enterprise/2.14/user/articles/editing-a-saved-reply", - "/en/enterprise/2.14/articles/editing-and-deleting-releases": "/en/enterprise/2.14/user/articles/editing-and-deleting-releases", - "/enterprise/2.14/user/articles/editing-and-deleting-releases": "/en/enterprise/2.14/user/articles/editing-and-deleting-releases", - "/enterprise/2.14/articles/editing-and-deleting-releases": "/en/enterprise/2.14/user/articles/editing-and-deleting-releases", - "/en/enterprise/2.14/articles/editing-and-sharing-content-with-gists": "/en/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists", - "/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists": "/en/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists", - "/enterprise/2.14/articles/editing-and-sharing-content-with-gists": "/en/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists", - "/en/enterprise/2.14/articles/editing-files-in-another-users-repository": "/en/enterprise/2.14/user/articles/editing-files-in-another-users-repository", - "/enterprise/2.14/user/articles/editing-files-in-another-users-repository": "/en/enterprise/2.14/user/articles/editing-files-in-another-users-repository", - "/enterprise/2.14/articles/editing-files-in-another-users-repository": "/en/enterprise/2.14/user/articles/editing-files-in-another-users-repository", - "/en/enterprise/2.14/articles/editing-files-in-your-repository": "/en/enterprise/2.14/user/articles/editing-files-in-your-repository", - "/enterprise/2.14/user/articles/editing-files-in-your-repository": "/en/enterprise/2.14/user/articles/editing-files-in-your-repository", - "/enterprise/2.14/articles/editing-files-in-your-repository": "/en/enterprise/2.14/user/articles/editing-files-in-your-repository", - "/en/enterprise/2.14/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion", - "/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion", - "/enterprise/2.14/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.14/articles/editing-wiki-content": "/en/enterprise/2.14/user/articles/editing-wiki-content", - "/enterprise/2.14/user/articles/editing-wiki-content": "/en/enterprise/2.14/user/articles/editing-wiki-content", - "/enterprise/2.14/articles/editing-wiki-content": "/en/enterprise/2.14/user/articles/editing-wiki-content", - "/en/enterprise/2.14/articles/emoji-on-github-pages": "/en/enterprise/2.14/user/articles/emoji-on-github-pages", - "/enterprise/2.14/user/articles/emoji-on-github-pages": "/en/enterprise/2.14/user/articles/emoji-on-github-pages", - "/enterprise/2.14/articles/emoji-on-github-pages": "/en/enterprise/2.14/user/articles/emoji-on-github-pages", - "/en/enterprise/2.14/articles/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.14/articles/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.14/articles/enabling-branch-restrictions": "/en/enterprise/2.14/user/articles/enabling-branch-restrictions", - "/enterprise/2.14/user/articles/enabling-branch-restrictions": "/en/enterprise/2.14/user/articles/enabling-branch-restrictions", - "/enterprise/2.14/articles/enabling-branch-restrictions": "/en/enterprise/2.14/user/articles/enabling-branch-restrictions", - "/en/enterprise/2.14/articles/enabling-required-commit-signing": "/en/enterprise/2.14/user/articles/enabling-required-commit-signing", - "/enterprise/2.14/user/articles/enabling-required-commit-signing": "/en/enterprise/2.14/user/articles/enabling-required-commit-signing", - "/enterprise/2.14/articles/enabling-required-commit-signing": "/en/enterprise/2.14/user/articles/enabling-required-commit-signing", - "/en/enterprise/2.14/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests", - "/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests", - "/enterprise/2.14/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.14/articles/enabling-required-status-checks": "/en/enterprise/2.14/user/articles/enabling-required-status-checks", - "/enterprise/2.14/user/articles/enabling-required-status-checks": "/en/enterprise/2.14/user/articles/enabling-required-status-checks", - "/enterprise/2.14/articles/enabling-required-status-checks": "/en/enterprise/2.14/user/articles/enabling-required-status-checks", - "/en/enterprise/2.14/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign", - "/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign", - "/enterprise/2.14/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.14/articles/error-bad-file-number": "/en/enterprise/2.14/user/articles/error-bad-file-number", - "/enterprise/2.14/user/articles/error-bad-file-number": "/en/enterprise/2.14/user/articles/error-bad-file-number", - "/enterprise/2.14/articles/error-bad-file-number": "/en/enterprise/2.14/user/articles/error-bad-file-number", - "/en/enterprise/2.14/articles/error-key-already-in-use": "/en/enterprise/2.14/user/articles/error-key-already-in-use", - "/enterprise/2.14/user/articles/error-key-already-in-use": "/en/enterprise/2.14/user/articles/error-key-already-in-use", - "/enterprise/2.14/articles/error-key-already-in-use": "/en/enterprise/2.14/user/articles/error-key-already-in-use", - "/en/enterprise/2.14/articles/error-permission-denied-publickey": "/en/enterprise/2.14/user/articles/error-permission-denied-publickey", - "/enterprise/2.14/user/articles/error-permission-denied-publickey": "/en/enterprise/2.14/user/articles/error-permission-denied-publickey", - "/enterprise/2.14/articles/error-permission-denied-publickey": "/en/enterprise/2.14/user/articles/error-permission-denied-publickey", - "/en/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.14/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.14/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.14/articles/error-repository-not-found": "/en/enterprise/2.14/user/articles/error-repository-not-found", - "/enterprise/2.14/user/articles/error-repository-not-found": "/en/enterprise/2.14/user/articles/error-repository-not-found", - "/enterprise/2.14/articles/error-repository-not-found": "/en/enterprise/2.14/user/articles/error-repository-not-found", - "/en/enterprise/2.14/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k", - "/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k", - "/enterprise/2.14/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k", - "/en/enterprise/2.14/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit", - "/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit", - "/enterprise/2.14/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.14/articles/exploring-projects-on-github": "/en/enterprise/2.14/user/articles/exploring-projects-on-github", - "/enterprise/2.14/user/articles/exploring-projects-on-github": "/en/enterprise/2.14/user/articles/exploring-projects-on-github", - "/enterprise/2.14/articles/exploring-projects-on-github": "/en/enterprise/2.14/user/articles/exploring-projects-on-github", - "/en/enterprise/2.14/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.14/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.14/articles/files-that-start-with-an-underscore-are-missing": "/en/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing", - "/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing": "/en/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing", - "/enterprise/2.14/articles/files-that-start-with-an-underscore-are-missing": "/en/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing", - "/en/enterprise/2.14/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.14/user/articles/filtering-cards-on-a-project-board", - "/enterprise/2.14/user/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.14/user/articles/filtering-cards-on-a-project-board", - "/enterprise/2.14/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.14/user/articles/filtering-cards-on-a-project-board", - "/en/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.14/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests", - "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests", - "/enterprise/2.14/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/filtering-issues-and-pull-requests", - "/en/enterprise/2.14/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status", - "/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status", - "/enterprise/2.14/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status", - "/en/enterprise/2.14/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.14/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.14/articles/finding-files-on-github": "/en/enterprise/2.14/user/articles/finding-files-on-github", - "/enterprise/2.14/user/articles/finding-files-on-github": "/en/enterprise/2.14/user/articles/finding-files-on-github", - "/enterprise/2.14/articles/finding-files-on-github": "/en/enterprise/2.14/user/articles/finding-files-on-github", - "/en/enterprise/2.14/articles/finding-information-in-a-repository": "/en/enterprise/2.14/user/articles/finding-information-in-a-repository", - "/enterprise/2.14/user/articles/finding-information-in-a-repository": "/en/enterprise/2.14/user/articles/finding-information-in-a-repository", - "/enterprise/2.14/articles/finding-information-in-a-repository": "/en/enterprise/2.14/user/articles/finding-information-in-a-repository", - "/en/enterprise/2.14/articles/following-people": "/en/enterprise/2.14/user/articles/following-people", - "/enterprise/2.14/user/articles/following-people": "/en/enterprise/2.14/user/articles/following-people", - "/enterprise/2.14/articles/following-people": "/en/enterprise/2.14/user/articles/following-people", - "/en/enterprise/2.14/articles/fork-a-repo": "/en/enterprise/2.14/user/articles/fork-a-repo", - "/enterprise/2.14/user/articles/fork-a-repo": "/en/enterprise/2.14/user/articles/fork-a-repo", - "/enterprise/2.14/articles/fork-a-repo": "/en/enterprise/2.14/user/articles/fork-a-repo", - "/en/enterprise/2.14/articles/forking-and-cloning-gists": "/en/enterprise/2.14/user/articles/forking-and-cloning-gists", - "/enterprise/2.14/user/articles/forking-and-cloning-gists": "/en/enterprise/2.14/user/articles/forking-and-cloning-gists", - "/enterprise/2.14/articles/forking-and-cloning-gists": "/en/enterprise/2.14/user/articles/forking-and-cloning-gists", - "/en/enterprise/2.14/articles/further-reading-on-github-pages": "/en/enterprise/2.14/user/articles/further-reading-on-github-pages", - "/enterprise/2.14/user/articles/further-reading-on-github-pages": "/en/enterprise/2.14/user/articles/further-reading-on-github-pages", - "/enterprise/2.14/articles/further-reading-on-github-pages": "/en/enterprise/2.14/user/articles/further-reading-on-github-pages", - "/en/enterprise/2.14/articles/generating-a-new-gpg-key": "/en/enterprise/2.14/user/articles/generating-a-new-gpg-key", - "/enterprise/2.14/user/articles/generating-a-new-gpg-key": "/en/enterprise/2.14/user/articles/generating-a-new-gpg-key", - "/enterprise/2.14/articles/generating-a-new-gpg-key": "/en/enterprise/2.14/user/articles/generating-a-new-gpg-key", - "/en/enterprise/2.14/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.14/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.14/articles/generic-jekyll-build-failures": "/en/enterprise/2.14/user/articles/generic-jekyll-build-failures", - "/enterprise/2.14/user/articles/generic-jekyll-build-failures": "/en/enterprise/2.14/user/articles/generic-jekyll-build-failures", - "/enterprise/2.14/articles/generic-jekyll-build-failures": "/en/enterprise/2.14/user/articles/generic-jekyll-build-failures", - "/en/enterprise/2.14/articles/getting-changes-from-a-remote-repository": "/en/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository", - "/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository": "/en/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository", - "/enterprise/2.14/articles/getting-changes-from-a-remote-repository": "/en/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository", - "/en/enterprise/2.14/articles/getting-permanent-links-to-files": "/en/enterprise/2.14/user/articles/getting-permanent-links-to-files", - "/enterprise/2.14/user/articles/getting-permanent-links-to-files": "/en/enterprise/2.14/user/articles/getting-permanent-links-to-files", - "/enterprise/2.14/articles/getting-permanent-links-to-files": "/en/enterprise/2.14/user/articles/getting-permanent-links-to-files", - "/en/enterprise/2.14/articles/getting-started-with-git-and-github": "/en/enterprise/2.14/user/articles/getting-started-with-git-and-github", - "/enterprise/2.14/user/articles/getting-started-with-git-and-github": "/en/enterprise/2.14/user/articles/getting-started-with-git-and-github", - "/enterprise/2.14/articles/getting-started-with-git-and-github": "/en/enterprise/2.14/user/articles/getting-started-with-git-and-github", - "/en/enterprise/2.14/articles/getting-started-with-notifications": "/en/enterprise/2.14/user/articles/getting-started-with-notifications", - "/enterprise/2.14/user/articles/getting-started-with-notifications": "/en/enterprise/2.14/user/articles/getting-started-with-notifications", - "/enterprise/2.14/articles/getting-started-with-notifications": "/en/enterprise/2.14/user/articles/getting-started-with-notifications", - "/en/enterprise/2.14/articles/getting-started-with-searching-on-github": "/en/enterprise/2.14/user/articles/getting-started-with-searching-on-github", - "/enterprise/2.14/user/articles/getting-started-with-searching-on-github": "/en/enterprise/2.14/user/articles/getting-started-with-searching-on-github", - "/enterprise/2.14/articles/getting-started-with-searching-on-github": "/en/enterprise/2.14/user/articles/getting-started-with-searching-on-github", - "/en/enterprise/2.14/articles/getting-started-with-the-api": "/en/enterprise/2.14/user/articles/getting-started-with-the-api", - "/enterprise/2.14/user/articles/getting-started-with-the-api": "/en/enterprise/2.14/user/articles/getting-started-with-the-api", - "/enterprise/2.14/articles/getting-started-with-the-api": "/en/enterprise/2.14/user/articles/getting-started-with-the-api", - "/en/enterprise/2.14/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.14/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.14/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases", - "/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases", - "/enterprise/2.14/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases", - "/en/enterprise/2.14/articles/git-and-github-learning-resources": "/en/enterprise/2.14/user/articles/git-and-github-learning-resources", - "/enterprise/2.14/user/articles/git-and-github-learning-resources": "/en/enterprise/2.14/user/articles/git-and-github-learning-resources", - "/enterprise/2.14/articles/git-and-github-learning-resources": "/en/enterprise/2.14/user/articles/git-and-github-learning-resources", - "/en/enterprise/2.14/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.14/user/articles/git-automation-with-oauth-tokens", - "/enterprise/2.14/user/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.14/user/articles/git-automation-with-oauth-tokens", - "/enterprise/2.14/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.14/user/articles/git-automation-with-oauth-tokens", - "/en/enterprise/2.14/articles/git-cheatsheet": "/en/enterprise/2.14/user/articles/git-cheatsheet", - "/enterprise/2.14/user/articles/git-cheatsheet": "/en/enterprise/2.14/user/articles/git-cheatsheet", - "/enterprise/2.14/articles/git-cheatsheet": "/en/enterprise/2.14/user/articles/git-cheatsheet", - "/en/enterprise/2.14/articles/git-workflows": "/en/enterprise/2.14/user/articles/git-workflows", - "/enterprise/2.14/user/articles/git-workflows": "/en/enterprise/2.14/user/articles/git-workflows", - "/enterprise/2.14/articles/git-workflows": "/en/enterprise/2.14/user/articles/git-workflows", - "/en/enterprise/2.14/articles/github-flow": "/en/enterprise/2.14/user/articles/github-flow", - "/enterprise/2.14/user/articles/github-flow": "/en/enterprise/2.14/user/articles/github-flow", - "/enterprise/2.14/articles/github-flow": "/en/enterprise/2.14/user/articles/github-flow", - "/en/enterprise/2.14/articles/github-glossary": "/en/enterprise/2.14/user/articles/github-glossary", - "/enterprise/2.14/user/articles/github-glossary": "/en/enterprise/2.14/user/articles/github-glossary", - "/enterprise/2.14/articles/github-glossary": "/en/enterprise/2.14/user/articles/github-glossary", - "/en/enterprise/2.14/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.14/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.14/articles/https-cloning-errors": "/en/enterprise/2.14/user/articles/https-cloning-errors", - "/enterprise/2.14/user/articles/https-cloning-errors": "/en/enterprise/2.14/user/articles/https-cloning-errors", - "/enterprise/2.14/articles/https-cloning-errors": "/en/enterprise/2.14/user/articles/https-cloning-errors", - "/en/enterprise/2.14/articles/ignoring-files": "/en/enterprise/2.14/user/articles/ignoring-files", - "/enterprise/2.14/user/articles/ignoring-files": "/en/enterprise/2.14/user/articles/ignoring-files", - "/enterprise/2.14/articles/ignoring-files": "/en/enterprise/2.14/user/articles/ignoring-files", - "/en/enterprise/2.14/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line", - "/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line", - "/enterprise/2.14/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.14/articles/importing-source-code-to-github": "/en/enterprise/2.14/user/articles/importing-source-code-to-github", - "/enterprise/2.14/user/articles/importing-source-code-to-github": "/en/enterprise/2.14/user/articles/importing-source-code-to-github", - "/enterprise/2.14/articles/importing-source-code-to-github": "/en/enterprise/2.14/user/articles/importing-source-code-to-github", - "/en/enterprise/2.14/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request", - "/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request", - "/enterprise/2.14/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.14/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme", - "/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme", - "/enterprise/2.14/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme", - "/en/enterprise/2.14/articles/installing-git-large-file-storage": "/en/enterprise/2.14/user/articles/installing-git-large-file-storage", - "/enterprise/2.14/user/articles/installing-git-large-file-storage": "/en/enterprise/2.14/user/articles/installing-git-large-file-storage", - "/enterprise/2.14/articles/installing-git-large-file-storage": "/en/enterprise/2.14/user/articles/installing-git-large-file-storage", - "/en/enterprise/2.14/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board", - "/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board", - "/enterprise/2.14/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.14/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects", - "/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects", - "/enterprise/2.14/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.14/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.14/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.14/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.14/user/articles/keeping-your-account-and-data-secure", - "/enterprise/2.14/user/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.14/user/articles/keeping-your-account-and-data-secure", - "/enterprise/2.14/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.14/user/articles/keeping-your-account-and-data-secure", - "/en/enterprise/2.14/articles/keeping-your-organization-secure": "/en/enterprise/2.14/user/articles/keeping-your-organization-secure", - "/enterprise/2.14/user/articles/keeping-your-organization-secure": "/en/enterprise/2.14/user/articles/keeping-your-organization-secure", - "/enterprise/2.14/articles/keeping-your-organization-secure": "/en/enterprise/2.14/user/articles/keeping-your-organization-secure", - "/en/enterprise/2.14/articles/keyboard-shortcuts": "/en/enterprise/2.14/user/articles/keyboard-shortcuts", - "/enterprise/2.14/user/articles/keyboard-shortcuts": "/en/enterprise/2.14/user/articles/keyboard-shortcuts", - "/enterprise/2.14/articles/keyboard-shortcuts": "/en/enterprise/2.14/user/articles/keyboard-shortcuts", - "/en/enterprise/2.14/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/labeling-issues-and-pull-requests", - "/enterprise/2.14/user/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/labeling-issues-and-pull-requests", - "/enterprise/2.14/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/labeling-issues-and-pull-requests", - "/en/enterprise/2.14/articles/learning-about-git": "/en/enterprise/2.14/user/articles/learning-about-git", - "/enterprise/2.14/user/articles/learning-about-git": "/en/enterprise/2.14/user/articles/learning-about-git", - "/enterprise/2.14/articles/learning-about-git": "/en/enterprise/2.14/user/articles/learning-about-git", - "/en/enterprise/2.14/articles/learning-about-github": "/en/enterprise/2.14/user/articles/learning-about-github", - "/enterprise/2.14/user/articles/learning-about-github": "/en/enterprise/2.14/user/articles/learning-about-github", - "/enterprise/2.14/articles/learning-about-github": "/en/enterprise/2.14/user/articles/learning-about-github", - "/en/enterprise/2.14/articles/licensing-a-repository": "/en/enterprise/2.14/user/articles/licensing-a-repository", - "/enterprise/2.14/user/articles/licensing-a-repository": "/en/enterprise/2.14/user/articles/licensing-a-repository", - "/enterprise/2.14/articles/licensing-a-repository": "/en/enterprise/2.14/user/articles/licensing-a-repository", - "/en/enterprise/2.14/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.14/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.14/articles/linking-to-releases": "/en/enterprise/2.14/user/articles/linking-to-releases", - "/enterprise/2.14/user/articles/linking-to-releases": "/en/enterprise/2.14/user/articles/linking-to-releases", - "/enterprise/2.14/articles/linking-to-releases": "/en/enterprise/2.14/user/articles/linking-to-releases", - "/en/enterprise/2.14/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.14/user/articles/listing-the-forks-of-a-repository", - "/enterprise/2.14/user/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.14/user/articles/listing-the-forks-of-a-repository", - "/enterprise/2.14/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.14/user/articles/listing-the-forks-of-a-repository", - "/en/enterprise/2.14/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.14/user/articles/listing-the-repositories-youre-watching", - "/enterprise/2.14/user/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.14/user/articles/listing-the-repositories-youre-watching", - "/enterprise/2.14/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.14/user/articles/listing-the-repositories-youre-watching", - "/en/enterprise/2.14/articles/locking-conversations": "/en/enterprise/2.14/user/articles/locking-conversations", - "/enterprise/2.14/user/articles/locking-conversations": "/en/enterprise/2.14/user/articles/locking-conversations", - "/enterprise/2.14/articles/locking-conversations": "/en/enterprise/2.14/user/articles/locking-conversations", - "/en/enterprise/2.14/articles/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.14/articles/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members", - "/en/enterprise/2.14/articles/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards", - "/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards", - "/enterprise/2.14/articles/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards", - "/en/enterprise/2.14/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories", - "/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories", - "/enterprise/2.14/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.14/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories", - "/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories", - "/enterprise/2.14/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories", - "/en/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/en/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.14/articles/managing-branches-in-your-repository": "/en/enterprise/2.14/user/articles/managing-branches-in-your-repository", - "/enterprise/2.14/user/articles/managing-branches-in-your-repository": "/en/enterprise/2.14/user/articles/managing-branches-in-your-repository", - "/enterprise/2.14/articles/managing-branches-in-your-repository": "/en/enterprise/2.14/user/articles/managing-branches-in-your-repository", - "/en/enterprise/2.14/articles/managing-commit-signature-verification": "/en/enterprise/2.14/user/articles/managing-commit-signature-verification", - "/enterprise/2.14/user/articles/managing-commit-signature-verification": "/en/enterprise/2.14/user/articles/managing-commit-signature-verification", - "/enterprise/2.14/articles/managing-commit-signature-verification": "/en/enterprise/2.14/user/articles/managing-commit-signature-verification", - "/en/enterprise/2.14/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile", - "/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile", - "/enterprise/2.14/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.14/articles/managing-disruptive-comments": "/en/enterprise/2.14/user/articles/managing-disruptive-comments", - "/enterprise/2.14/user/articles/managing-disruptive-comments": "/en/enterprise/2.14/user/articles/managing-disruptive-comments", - "/enterprise/2.14/articles/managing-disruptive-comments": "/en/enterprise/2.14/user/articles/managing-disruptive-comments", - "/en/enterprise/2.14/articles/managing-email-preferences": "/en/enterprise/2.14/user/articles/managing-email-preferences", - "/enterprise/2.14/user/articles/managing-email-preferences": "/en/enterprise/2.14/user/articles/managing-email-preferences", - "/enterprise/2.14/articles/managing-email-preferences": "/en/enterprise/2.14/user/articles/managing-email-preferences", - "/en/enterprise/2.14/articles/managing-files-on-github": "/en/enterprise/2.14/user/articles/managing-files-on-github", - "/enterprise/2.14/user/articles/managing-files-on-github": "/en/enterprise/2.14/user/articles/managing-files-on-github", - "/enterprise/2.14/articles/managing-files-on-github": "/en/enterprise/2.14/user/articles/managing-files-on-github", - "/en/enterprise/2.14/articles/managing-files-using-the-command-line": "/en/enterprise/2.14/user/articles/managing-files-using-the-command-line", - "/enterprise/2.14/user/articles/managing-files-using-the-command-line": "/en/enterprise/2.14/user/articles/managing-files-using-the-command-line", - "/enterprise/2.14/articles/managing-files-using-the-command-line": "/en/enterprise/2.14/user/articles/managing-files-using-the-command-line", - "/en/enterprise/2.14/articles/managing-membership-in-your-organization": "/en/enterprise/2.14/user/articles/managing-membership-in-your-organization", - "/enterprise/2.14/user/articles/managing-membership-in-your-organization": "/en/enterprise/2.14/user/articles/managing-membership-in-your-organization", - "/enterprise/2.14/articles/managing-membership-in-your-organization": "/en/enterprise/2.14/user/articles/managing-membership-in-your-organization", - "/en/enterprise/2.14/articles/managing-organization-settings": "/en/enterprise/2.14/user/articles/managing-organization-settings", - "/enterprise/2.14/user/articles/managing-organization-settings": "/en/enterprise/2.14/user/articles/managing-organization-settings", - "/enterprise/2.14/articles/managing-organization-settings": "/en/enterprise/2.14/user/articles/managing-organization-settings", - "/en/enterprise/2.14/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.14/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.14/articles/managing-project-boards": "/en/enterprise/2.14/user/articles/managing-project-boards", - "/enterprise/2.14/user/articles/managing-project-boards": "/en/enterprise/2.14/user/articles/managing-project-boards", - "/enterprise/2.14/articles/managing-project-boards": "/en/enterprise/2.14/user/articles/managing-project-boards", - "/en/enterprise/2.14/articles/managing-releases-in-a-repository": "/en/enterprise/2.14/user/articles/managing-releases-in-a-repository", - "/enterprise/2.14/user/articles/managing-releases-in-a-repository": "/en/enterprise/2.14/user/articles/managing-releases-in-a-repository", - "/enterprise/2.14/articles/managing-releases-in-a-repository": "/en/enterprise/2.14/user/articles/managing-releases-in-a-repository", - "/en/enterprise/2.14/articles/managing-remote-repositories": "/en/enterprise/2.14/user/articles/managing-remote-repositories", - "/enterprise/2.14/user/articles/managing-remote-repositories": "/en/enterprise/2.14/user/articles/managing-remote-repositories", - "/enterprise/2.14/articles/managing-remote-repositories": "/en/enterprise/2.14/user/articles/managing-remote-repositories", - "/en/enterprise/2.14/articles/managing-repository-settings": "/en/enterprise/2.14/user/articles/managing-repository-settings", - "/enterprise/2.14/user/articles/managing-repository-settings": "/en/enterprise/2.14/user/articles/managing-repository-settings", - "/enterprise/2.14/articles/managing-repository-settings": "/en/enterprise/2.14/user/articles/managing-repository-settings", - "/en/enterprise/2.14/articles/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board", - "/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board", - "/enterprise/2.14/articles/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board", - "/en/enterprise/2.14/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository", - "/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository", - "/enterprise/2.14/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.14/articles/managing-user-account-settings": "/en/enterprise/2.14/user/articles/managing-user-account-settings", - "/enterprise/2.14/user/articles/managing-user-account-settings": "/en/enterprise/2.14/user/articles/managing-user-account-settings", - "/enterprise/2.14/articles/managing-user-account-settings": "/en/enterprise/2.14/user/articles/managing-user-account-settings", - "/en/enterprise/2.14/articles/managing-your-membership-in-organizations": "/en/enterprise/2.14/user/articles/managing-your-membership-in-organizations", - "/enterprise/2.14/user/articles/managing-your-membership-in-organizations": "/en/enterprise/2.14/user/articles/managing-your-membership-in-organizations", - "/enterprise/2.14/articles/managing-your-membership-in-organizations": "/en/enterprise/2.14/user/articles/managing-your-membership-in-organizations", - "/en/enterprise/2.14/articles/managing-your-notifications": "/en/enterprise/2.14/user/articles/managing-your-notifications", - "/enterprise/2.14/user/articles/managing-your-notifications": "/en/enterprise/2.14/user/articles/managing-your-notifications", - "/enterprise/2.14/articles/managing-your-notifications": "/en/enterprise/2.14/user/articles/managing-your-notifications", - "/en/enterprise/2.14/articles/managing-your-work-with-issues": "/en/enterprise/2.14/user/articles/managing-your-work-with-issues", - "/enterprise/2.14/user/articles/managing-your-work-with-issues": "/en/enterprise/2.14/user/articles/managing-your-work-with-issues", - "/enterprise/2.14/articles/managing-your-work-with-issues": "/en/enterprise/2.14/user/articles/managing-your-work-with-issues", - "/en/enterprise/2.14/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.14/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.14/articles/mapping-geojson-files-on-github": "/en/enterprise/2.14/user/articles/mapping-geojson-files-on-github", - "/enterprise/2.14/user/articles/mapping-geojson-files-on-github": "/en/enterprise/2.14/user/articles/mapping-geojson-files-on-github", - "/enterprise/2.14/articles/mapping-geojson-files-on-github": "/en/enterprise/2.14/user/articles/mapping-geojson-files-on-github", - "/en/enterprise/2.14/articles/marking-notifications-as-read": "/en/enterprise/2.14/user/articles/marking-notifications-as-read", - "/enterprise/2.14/user/articles/marking-notifications-as-read": "/en/enterprise/2.14/user/articles/marking-notifications-as-read", - "/enterprise/2.14/articles/marking-notifications-as-read": "/en/enterprise/2.14/user/articles/marking-notifications-as-read", - "/en/enterprise/2.14/articles/mentions-on-github-pages": "/en/enterprise/2.14/user/articles/mentions-on-github-pages", - "/enterprise/2.14/user/articles/mentions-on-github-pages": "/en/enterprise/2.14/user/articles/mentions-on-github-pages", - "/enterprise/2.14/articles/mentions-on-github-pages": "/en/enterprise/2.14/user/articles/mentions-on-github-pages", - "/en/enterprise/2.14/articles/merging-a-pull-request": "/en/enterprise/2.14/user/articles/merging-a-pull-request", - "/enterprise/2.14/user/articles/merging-a-pull-request": "/en/enterprise/2.14/user/articles/merging-a-pull-request", - "/enterprise/2.14/articles/merging-a-pull-request": "/en/enterprise/2.14/user/articles/merging-a-pull-request", - "/en/enterprise/2.14/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.14/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.14/articles/migrating-your-organization-to-improved-organization-permissions": "/en/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions", - "/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions": "/en/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions", - "/enterprise/2.14/articles/migrating-your-organization-to-improved-organization-permissions": "/en/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions", - "/en/enterprise/2.14/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions", - "/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions", - "/enterprise/2.14/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": "/en/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions", - "/en/enterprise/2.14/articles/mime-types-on-github-pages": "/en/enterprise/2.14/user/articles/mime-types-on-github-pages", - "/enterprise/2.14/user/articles/mime-types-on-github-pages": "/en/enterprise/2.14/user/articles/mime-types-on-github-pages", - "/enterprise/2.14/articles/mime-types-on-github-pages": "/en/enterprise/2.14/user/articles/mime-types-on-github-pages", - "/en/enterprise/2.14/articles/moderating-comments-and-conversations": "/en/enterprise/2.14/user/articles/moderating-comments-and-conversations", - "/enterprise/2.14/user/articles/moderating-comments-and-conversations": "/en/enterprise/2.14/user/articles/moderating-comments-and-conversations", - "/enterprise/2.14/articles/moderating-comments-and-conversations": "/en/enterprise/2.14/user/articles/moderating-comments-and-conversations", - "/en/enterprise/2.14/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.14/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.14/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.14/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.14/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.14/user/articles/moving-a-file-to-a-new-location", - "/enterprise/2.14/user/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.14/user/articles/moving-a-file-to-a-new-location", - "/enterprise/2.14/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.14/user/articles/moving-a-file-to-a-new-location", - "/en/enterprise/2.14/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.14/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.14/articles/opening-an-issue-from-code": "/en/enterprise/2.14/user/articles/opening-an-issue-from-code", - "/enterprise/2.14/user/articles/opening-an-issue-from-code": "/en/enterprise/2.14/user/articles/opening-an-issue-from-code", - "/enterprise/2.14/articles/opening-an-issue-from-code": "/en/enterprise/2.14/user/articles/opening-an-issue-from-code", - "/en/enterprise/2.14/articles/organizing-information-with-tables": "/en/enterprise/2.14/user/articles/organizing-information-with-tables", - "/enterprise/2.14/user/articles/organizing-information-with-tables": "/en/enterprise/2.14/user/articles/organizing-information-with-tables", - "/enterprise/2.14/articles/organizing-information-with-tables": "/en/enterprise/2.14/user/articles/organizing-information-with-tables", - "/en/enterprise/2.14/articles/organizing-members-into-teams": "/en/enterprise/2.14/user/articles/organizing-members-into-teams", - "/enterprise/2.14/user/articles/organizing-members-into-teams": "/en/enterprise/2.14/user/articles/organizing-members-into-teams", - "/enterprise/2.14/articles/organizing-members-into-teams": "/en/enterprise/2.14/user/articles/organizing-members-into-teams", - "/en/enterprise/2.14/articles/page-build-failed-config-file-error": "/en/enterprise/2.14/user/articles/page-build-failed-config-file-error", - "/enterprise/2.14/user/articles/page-build-failed-config-file-error": "/en/enterprise/2.14/user/articles/page-build-failed-config-file-error", - "/enterprise/2.14/articles/page-build-failed-config-file-error": "/en/enterprise/2.14/user/articles/page-build-failed-config-file-error", - "/en/enterprise/2.14/articles/page-build-failed-date-is-not-a-valid-datetime": "/en/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime": "/en/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/enterprise/2.14/articles/page-build-failed-date-is-not-a-valid-datetime": "/en/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/en/enterprise/2.14/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/en/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/en/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/enterprise/2.14/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/en/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/en/enterprise/2.14/articles/page-build-failed-file-is-a-symlink": "/en/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink", - "/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink": "/en/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink", - "/enterprise/2.14/articles/page-build-failed-file-is-a-symlink": "/en/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink", - "/en/enterprise/2.14/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/en/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/en/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/enterprise/2.14/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/en/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/en/enterprise/2.14/articles/page-build-failed-invalid-highlighter-language": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language", - "/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language", - "/enterprise/2.14/articles/page-build-failed-invalid-highlighter-language": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language", - "/en/enterprise/2.14/articles/page-build-failed-invalid-post-date": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-post-date", - "/enterprise/2.14/user/articles/page-build-failed-invalid-post-date": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-post-date", - "/enterprise/2.14/articles/page-build-failed-invalid-post-date": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-post-date", - "/en/enterprise/2.14/articles/page-build-failed-invalid-sass-or-scss": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss", - "/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss", - "/enterprise/2.14/articles/page-build-failed-invalid-sass-or-scss": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss", - "/en/enterprise/2.14/articles/page-build-failed-invalid-submodule": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-submodule", - "/enterprise/2.14/user/articles/page-build-failed-invalid-submodule": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-submodule", - "/enterprise/2.14/articles/page-build-failed-invalid-submodule": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-submodule", - "/en/enterprise/2.14/articles/page-build-failed-invalid-yaml-in-data-file": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/enterprise/2.14/articles/page-build-failed-invalid-yaml-in-data-file": "/en/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/en/enterprise/2.14/articles/page-build-failed-markdown-errors": "/en/enterprise/2.14/user/articles/page-build-failed-markdown-errors", - "/enterprise/2.14/user/articles/page-build-failed-markdown-errors": "/en/enterprise/2.14/user/articles/page-build-failed-markdown-errors", - "/enterprise/2.14/articles/page-build-failed-markdown-errors": "/en/enterprise/2.14/user/articles/page-build-failed-markdown-errors", - "/en/enterprise/2.14/articles/page-build-failed-missing-docs-folder": "/en/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder", - "/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder": "/en/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder", - "/enterprise/2.14/articles/page-build-failed-missing-docs-folder": "/en/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder", - "/en/enterprise/2.14/articles/page-build-failed-missing-submodule": "/en/enterprise/2.14/user/articles/page-build-failed-missing-submodule", - "/enterprise/2.14/user/articles/page-build-failed-missing-submodule": "/en/enterprise/2.14/user/articles/page-build-failed-missing-submodule", - "/enterprise/2.14/articles/page-build-failed-missing-submodule": "/en/enterprise/2.14/user/articles/page-build-failed-missing-submodule", - "/en/enterprise/2.14/articles/page-build-failed-relative-permalinks-configured": "/en/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured", - "/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured": "/en/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured", - "/enterprise/2.14/articles/page-build-failed-relative-permalinks-configured": "/en/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured", - "/en/enterprise/2.14/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/en/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/en/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/enterprise/2.14/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/en/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/en/enterprise/2.14/articles/page-build-failed-syntax-error-in-for-loop": "/en/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop", - "/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop": "/en/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop", - "/enterprise/2.14/articles/page-build-failed-syntax-error-in-for-loop": "/en/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop", - "/en/enterprise/2.14/articles/page-build-failed-tag-not-properly-closed": "/en/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed", - "/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed": "/en/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed", - "/enterprise/2.14/articles/page-build-failed-tag-not-properly-closed": "/en/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed", - "/en/enterprise/2.14/articles/page-build-failed-tag-not-properly-terminated": "/en/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated", - "/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated": "/en/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated", - "/enterprise/2.14/articles/page-build-failed-tag-not-properly-terminated": "/en/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated", - "/en/enterprise/2.14/articles/page-build-failed-unknown-tag-error": "/en/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error", - "/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error": "/en/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error", - "/enterprise/2.14/articles/page-build-failed-unknown-tag-error": "/en/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error", - "/en/enterprise/2.14/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository", - "/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository", - "/enterprise/2.14/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.14/articles/permission-levels-for-an-organization": "/en/enterprise/2.14/user/articles/permission-levels-for-an-organization", - "/enterprise/2.14/user/articles/permission-levels-for-an-organization": "/en/enterprise/2.14/user/articles/permission-levels-for-an-organization", - "/enterprise/2.14/articles/permission-levels-for-an-organization": "/en/enterprise/2.14/user/articles/permission-levels-for-an-organization", - "/en/enterprise/2.14/articles/personalizing-your-profile": "/en/enterprise/2.14/user/articles/personalizing-your-profile", - "/enterprise/2.14/user/articles/personalizing-your-profile": "/en/enterprise/2.14/user/articles/personalizing-your-profile", - "/enterprise/2.14/articles/personalizing-your-profile": "/en/enterprise/2.14/user/articles/personalizing-your-profile", - "/en/enterprise/2.14/articles/pinning-a-team-discussion": "/en/enterprise/2.14/user/articles/pinning-a-team-discussion", - "/enterprise/2.14/user/articles/pinning-a-team-discussion": "/en/enterprise/2.14/user/articles/pinning-a-team-discussion", - "/enterprise/2.14/articles/pinning-a-team-discussion": "/en/enterprise/2.14/user/articles/pinning-a-team-discussion", - "/en/enterprise/2.14/articles/pinning-items-to-your-profile": "/en/enterprise/2.14/user/articles/pinning-items-to-your-profile", - "/enterprise/2.14/user/articles/pinning-items-to-your-profile": "/en/enterprise/2.14/user/articles/pinning-items-to-your-profile", - "/enterprise/2.14/articles/pinning-items-to-your-profile": "/en/enterprise/2.14/user/articles/pinning-items-to-your-profile", - "/en/enterprise/2.14/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.14/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.14/articles/preventing-unauthorized-access": "/en/enterprise/2.14/user/articles/preventing-unauthorized-access", - "/enterprise/2.14/user/articles/preventing-unauthorized-access": "/en/enterprise/2.14/user/articles/preventing-unauthorized-access", - "/enterprise/2.14/articles/preventing-unauthorized-access": "/en/enterprise/2.14/user/articles/preventing-unauthorized-access", - "/en/enterprise/2.14/articles/project-board-permissions-for-an-organization": "/en/enterprise/2.14/user/articles/project-board-permissions-for-an-organization", - "/enterprise/2.14/user/articles/project-board-permissions-for-an-organization": "/en/enterprise/2.14/user/articles/project-board-permissions-for-an-organization", - "/enterprise/2.14/articles/project-board-permissions-for-an-organization": "/en/enterprise/2.14/user/articles/project-board-permissions-for-an-organization", - "/en/enterprise/2.14/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.14/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.14/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership", - "/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership", - "/enterprise/2.14/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.14/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.14/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.14/articles/pushing-commits-to-a-remote-repository": "/en/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository", - "/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository": "/en/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository", - "/enterprise/2.14/articles/pushing-commits-to-a-remote-repository": "/en/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository", - "/en/enterprise/2.14/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.14/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.14/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase", - "/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase", - "/enterprise/2.14/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.14/articles/redirects-on-github-pages": "/en/enterprise/2.14/user/articles/redirects-on-github-pages", - "/enterprise/2.14/user/articles/redirects-on-github-pages": "/en/enterprise/2.14/user/articles/redirects-on-github-pages", - "/enterprise/2.14/articles/redirects-on-github-pages": "/en/enterprise/2.14/user/articles/redirects-on-github-pages", - "/en/enterprise/2.14/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization", - "/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization", - "/enterprise/2.14/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.14/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.14/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.14/articles/remembering-your-github-username-or-email": "/en/enterprise/2.14/user/articles/remembering-your-github-username-or-email", - "/enterprise/2.14/user/articles/remembering-your-github-username-or-email": "/en/enterprise/2.14/user/articles/remembering-your-github-username-or-email", - "/enterprise/2.14/articles/remembering-your-github-username-or-email": "/en/enterprise/2.14/user/articles/remembering-your-github-username-or-email", - "/en/enterprise/2.14/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.14/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.14/articles/removing-a-member-from-your-organization": "/en/enterprise/2.14/user/articles/removing-a-member-from-your-organization", - "/enterprise/2.14/user/articles/removing-a-member-from-your-organization": "/en/enterprise/2.14/user/articles/removing-a-member-from-your-organization", - "/enterprise/2.14/articles/removing-a-member-from-your-organization": "/en/enterprise/2.14/user/articles/removing-a-member-from-your-organization", - "/en/enterprise/2.14/articles/removing-a-remote": "/en/enterprise/2.14/user/articles/removing-a-remote", - "/enterprise/2.14/user/articles/removing-a-remote": "/en/enterprise/2.14/user/articles/removing-a-remote", - "/enterprise/2.14/articles/removing-a-remote": "/en/enterprise/2.14/user/articles/removing-a-remote", - "/en/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/en/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.14/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history", - "/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history", - "/enterprise/2.14/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history", - "/en/enterprise/2.14/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage", - "/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage", - "/enterprise/2.14/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage", - "/en/enterprise/2.14/articles/removing-organization-members-from-a-team": "/en/enterprise/2.14/user/articles/removing-organization-members-from-a-team", - "/enterprise/2.14/user/articles/removing-organization-members-from-a-team": "/en/enterprise/2.14/user/articles/removing-organization-members-from-a-team", - "/enterprise/2.14/articles/removing-organization-members-from-a-team": "/en/enterprise/2.14/user/articles/removing-organization-members-from-a-team", - "/en/enterprise/2.14/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository", - "/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository", - "/enterprise/2.14/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.14/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.14/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.14/articles/removing-yourself-from-an-organization": "/en/enterprise/2.14/user/articles/removing-yourself-from-an-organization", - "/enterprise/2.14/user/articles/removing-yourself-from-an-organization": "/en/enterprise/2.14/user/articles/removing-yourself-from-an-organization", - "/enterprise/2.14/articles/removing-yourself-from-an-organization": "/en/enterprise/2.14/user/articles/removing-yourself-from-an-organization", - "/en/enterprise/2.14/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line", - "/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line", - "/enterprise/2.14/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line", - "/en/enterprise/2.14/articles/renaming-a-file": "/en/enterprise/2.14/user/articles/renaming-a-file", - "/enterprise/2.14/user/articles/renaming-a-file": "/en/enterprise/2.14/user/articles/renaming-a-file", - "/enterprise/2.14/articles/renaming-a-file": "/en/enterprise/2.14/user/articles/renaming-a-file", - "/en/enterprise/2.14/articles/renaming-a-remote": "/en/enterprise/2.14/user/articles/renaming-a-remote", - "/enterprise/2.14/user/articles/renaming-a-remote": "/en/enterprise/2.14/user/articles/renaming-a-remote", - "/enterprise/2.14/articles/renaming-a-remote": "/en/enterprise/2.14/user/articles/renaming-a-remote", - "/en/enterprise/2.14/articles/renaming-a-repository": "/en/enterprise/2.14/user/articles/renaming-a-repository", - "/enterprise/2.14/user/articles/renaming-a-repository": "/en/enterprise/2.14/user/articles/renaming-a-repository", - "/enterprise/2.14/articles/renaming-a-repository": "/en/enterprise/2.14/user/articles/renaming-a-repository", - "/en/enterprise/2.14/articles/renaming-a-team": "/en/enterprise/2.14/user/articles/renaming-a-team", - "/enterprise/2.14/user/articles/renaming-a-team": "/en/enterprise/2.14/user/articles/renaming-a-team", - "/enterprise/2.14/articles/renaming-a-team": "/en/enterprise/2.14/user/articles/renaming-a-team", - "/en/enterprise/2.14/articles/renaming-an-organization": "/en/enterprise/2.14/user/articles/renaming-an-organization", - "/enterprise/2.14/user/articles/renaming-an-organization": "/en/enterprise/2.14/user/articles/renaming-an-organization", - "/enterprise/2.14/articles/renaming-an-organization": "/en/enterprise/2.14/user/articles/renaming-an-organization", - "/en/enterprise/2.14/articles/rendering-and-diffing-images": "/en/enterprise/2.14/user/articles/rendering-and-diffing-images", - "/enterprise/2.14/user/articles/rendering-and-diffing-images": "/en/enterprise/2.14/user/articles/rendering-and-diffing-images", - "/enterprise/2.14/articles/rendering-and-diffing-images": "/en/enterprise/2.14/user/articles/rendering-and-diffing-images", - "/en/enterprise/2.14/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.14/user/articles/rendering-csv-and-tsv-data", - "/enterprise/2.14/user/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.14/user/articles/rendering-csv-and-tsv-data", - "/enterprise/2.14/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.14/user/articles/rendering-csv-and-tsv-data", - "/en/enterprise/2.14/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.14/user/articles/rendering-differences-in-prose-documents", - "/enterprise/2.14/user/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.14/user/articles/rendering-differences-in-prose-documents", - "/enterprise/2.14/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.14/user/articles/rendering-differences-in-prose-documents", - "/en/enterprise/2.14/articles/rendering-pdf-documents": "/en/enterprise/2.14/user/articles/rendering-pdf-documents", - "/enterprise/2.14/user/articles/rendering-pdf-documents": "/en/enterprise/2.14/user/articles/rendering-pdf-documents", - "/enterprise/2.14/articles/rendering-pdf-documents": "/en/enterprise/2.14/user/articles/rendering-pdf-documents", - "/en/enterprise/2.14/articles/reopening-a-closed-project-board": "/en/enterprise/2.14/user/articles/reopening-a-closed-project-board", - "/enterprise/2.14/user/articles/reopening-a-closed-project-board": "/en/enterprise/2.14/user/articles/reopening-a-closed-project-board", - "/enterprise/2.14/articles/reopening-a-closed-project-board": "/en/enterprise/2.14/user/articles/reopening-a-closed-project-board", - "/en/enterprise/2.14/articles/repository-metadata-on-github-pages": "/en/enterprise/2.14/user/articles/repository-metadata-on-github-pages", - "/enterprise/2.14/user/articles/repository-metadata-on-github-pages": "/en/enterprise/2.14/user/articles/repository-metadata-on-github-pages", - "/enterprise/2.14/articles/repository-metadata-on-github-pages": "/en/enterprise/2.14/user/articles/repository-metadata-on-github-pages", - "/en/enterprise/2.14/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization", - "/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization", - "/enterprise/2.14/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization", - "/en/enterprise/2.14/articles/requesting-a-pull-request-review": "/en/enterprise/2.14/user/articles/requesting-a-pull-request-review", - "/enterprise/2.14/user/articles/requesting-a-pull-request-review": "/en/enterprise/2.14/user/articles/requesting-a-pull-request-review", - "/enterprise/2.14/articles/requesting-a-pull-request-review": "/en/enterprise/2.14/user/articles/requesting-a-pull-request-review", - "/en/enterprise/2.14/articles/requesting-a-trial-of-github-enterprise": "/en/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise", - "/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise": "/en/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise", - "/enterprise/2.14/articles/requesting-a-trial-of-github-enterprise": "/en/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise", - "/en/enterprise/2.14/articles/requesting-to-add-a-child-team": "/en/enterprise/2.14/user/articles/requesting-to-add-a-child-team", - "/enterprise/2.14/user/articles/requesting-to-add-a-child-team": "/en/enterprise/2.14/user/articles/requesting-to-add-a-child-team", - "/enterprise/2.14/articles/requesting-to-add-a-child-team": "/en/enterprise/2.14/user/articles/requesting-to-add-a-child-team", - "/en/enterprise/2.14/articles/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.14/articles/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team", - "/en/enterprise/2.14/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.14/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.14/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github", - "/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github", - "/enterprise/2.14/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.14/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.14/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.14/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.14/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.14/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.14/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.14/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization", - "/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization", - "/enterprise/2.14/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.14/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.14/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.14/articles/reverting-a-pull-request": "/en/enterprise/2.14/user/articles/reverting-a-pull-request", - "/enterprise/2.14/user/articles/reverting-a-pull-request": "/en/enterprise/2.14/user/articles/reverting-a-pull-request", - "/enterprise/2.14/articles/reverting-a-pull-request": "/en/enterprise/2.14/user/articles/reverting-a-pull-request", - "/en/enterprise/2.14/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests", - "/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests", - "/enterprise/2.14/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests", - "/en/enterprise/2.14/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.14/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.14/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.14/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.14/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth", - "/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth", - "/enterprise/2.14/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.14/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.14/user/articles/reviewing-your-authorized-integrations", - "/enterprise/2.14/user/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.14/user/articles/reviewing-your-authorized-integrations", - "/enterprise/2.14/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.14/user/articles/reviewing-your-authorized-integrations", - "/en/enterprise/2.14/articles/reviewing-your-deploy-keys": "/en/enterprise/2.14/user/articles/reviewing-your-deploy-keys", - "/enterprise/2.14/user/articles/reviewing-your-deploy-keys": "/en/enterprise/2.14/user/articles/reviewing-your-deploy-keys", - "/enterprise/2.14/articles/reviewing-your-deploy-keys": "/en/enterprise/2.14/user/articles/reviewing-your-deploy-keys", - "/en/enterprise/2.14/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations", - "/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations", - "/enterprise/2.14/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.14/articles/reviewing-your-security-log": "/en/enterprise/2.14/user/articles/reviewing-your-security-log", - "/enterprise/2.14/user/articles/reviewing-your-security-log": "/en/enterprise/2.14/user/articles/reviewing-your-security-log", - "/enterprise/2.14/articles/reviewing-your-security-log": "/en/enterprise/2.14/user/articles/reviewing-your-security-log", - "/en/enterprise/2.14/articles/reviewing-your-ssh-keys": "/en/enterprise/2.14/user/articles/reviewing-your-ssh-keys", - "/enterprise/2.14/user/articles/reviewing-your-ssh-keys": "/en/enterprise/2.14/user/articles/reviewing-your-ssh-keys", - "/enterprise/2.14/articles/reviewing-your-ssh-keys": "/en/enterprise/2.14/user/articles/reviewing-your-ssh-keys", - "/en/enterprise/2.14/articles/saving-repositories-with-stars": "/en/enterprise/2.14/user/articles/saving-repositories-with-stars", - "/enterprise/2.14/user/articles/saving-repositories-with-stars": "/en/enterprise/2.14/user/articles/saving-repositories-with-stars", - "/enterprise/2.14/articles/saving-repositories-with-stars": "/en/enterprise/2.14/user/articles/saving-repositories-with-stars", - "/en/enterprise/2.14/articles/searching-code": "/en/enterprise/2.14/user/articles/searching-code", - "/enterprise/2.14/user/articles/searching-code": "/en/enterprise/2.14/user/articles/searching-code", - "/enterprise/2.14/articles/searching-code": "/en/enterprise/2.14/user/articles/searching-code", - "/en/enterprise/2.14/articles/searching-commits": "/en/enterprise/2.14/user/articles/searching-commits", - "/enterprise/2.14/user/articles/searching-commits": "/en/enterprise/2.14/user/articles/searching-commits", - "/enterprise/2.14/articles/searching-commits": "/en/enterprise/2.14/user/articles/searching-commits", - "/en/enterprise/2.14/articles/searching-for-repositories": "/en/enterprise/2.14/user/articles/searching-for-repositories", - "/enterprise/2.14/user/articles/searching-for-repositories": "/en/enterprise/2.14/user/articles/searching-for-repositories", - "/enterprise/2.14/articles/searching-for-repositories": "/en/enterprise/2.14/user/articles/searching-for-repositories", - "/en/enterprise/2.14/articles/searching-in-forks": "/en/enterprise/2.14/user/articles/searching-in-forks", - "/enterprise/2.14/user/articles/searching-in-forks": "/en/enterprise/2.14/user/articles/searching-in-forks", - "/enterprise/2.14/articles/searching-in-forks": "/en/enterprise/2.14/user/articles/searching-in-forks", - "/en/enterprise/2.14/articles/searching-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/searching-issues-and-pull-requests", - "/enterprise/2.14/user/articles/searching-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/searching-issues-and-pull-requests", - "/enterprise/2.14/articles/searching-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/searching-issues-and-pull-requests", - "/en/enterprise/2.14/articles/searching-on-github": "/en/enterprise/2.14/user/articles/searching-on-github", - "/enterprise/2.14/user/articles/searching-on-github": "/en/enterprise/2.14/user/articles/searching-on-github", - "/enterprise/2.14/articles/searching-on-github": "/en/enterprise/2.14/user/articles/searching-on-github", - "/en/enterprise/2.14/articles/searching-topics": "/en/enterprise/2.14/user/articles/searching-topics", - "/enterprise/2.14/user/articles/searching-topics": "/en/enterprise/2.14/user/articles/searching-topics", - "/enterprise/2.14/articles/searching-topics": "/en/enterprise/2.14/user/articles/searching-topics", - "/en/enterprise/2.14/articles/searching-users": "/en/enterprise/2.14/user/articles/searching-users", - "/enterprise/2.14/user/articles/searching-users": "/en/enterprise/2.14/user/articles/searching-users", - "/enterprise/2.14/articles/searching-users": "/en/enterprise/2.14/user/articles/searching-users", - "/en/enterprise/2.14/articles/searching-wikis": "/en/enterprise/2.14/user/articles/searching-wikis", - "/enterprise/2.14/user/articles/searching-wikis": "/en/enterprise/2.14/user/articles/searching-wikis", - "/enterprise/2.14/articles/searching-wikis": "/en/enterprise/2.14/user/articles/searching-wikis", - "/en/enterprise/2.14/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.14/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.14/articles/set-up-git": "/en/enterprise/2.14/user/articles/set-up-git", - "/enterprise/2.14/user/articles/set-up-git": "/en/enterprise/2.14/user/articles/set-up-git", - "/enterprise/2.14/articles/set-up-git": "/en/enterprise/2.14/user/articles/set-up-git", - "/en/enterprise/2.14/articles/setting-a-backup-email-address": "/en/enterprise/2.14/user/articles/setting-a-backup-email-address", - "/enterprise/2.14/user/articles/setting-a-backup-email-address": "/en/enterprise/2.14/user/articles/setting-a-backup-email-address", - "/enterprise/2.14/articles/setting-a-backup-email-address": "/en/enterprise/2.14/user/articles/setting-a-backup-email-address", - "/en/enterprise/2.14/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors", - "/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors", - "/enterprise/2.14/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.14/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization", - "/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization", - "/enterprise/2.14/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": "/en/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization", - "/en/enterprise/2.14/articles/setting-repository-visibility": "/en/enterprise/2.14/user/articles/setting-repository-visibility", - "/enterprise/2.14/user/articles/setting-repository-visibility": "/en/enterprise/2.14/user/articles/setting-repository-visibility", - "/enterprise/2.14/articles/setting-repository-visibility": "/en/enterprise/2.14/user/articles/setting-repository-visibility", - "/en/enterprise/2.14/articles/setting-the-default-branch": "/en/enterprise/2.14/user/articles/setting-the-default-branch", - "/enterprise/2.14/user/articles/setting-the-default-branch": "/en/enterprise/2.14/user/articles/setting-the-default-branch", - "/enterprise/2.14/articles/setting-the-default-branch": "/en/enterprise/2.14/user/articles/setting-the-default-branch", - "/en/enterprise/2.14/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.14/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.14/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.14/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.14/articles/setting-your-commit-email-address": "/en/enterprise/2.14/user/articles/setting-your-commit-email-address", - "/enterprise/2.14/user/articles/setting-your-commit-email-address": "/en/enterprise/2.14/user/articles/setting-your-commit-email-address", - "/enterprise/2.14/articles/setting-your-commit-email-address": "/en/enterprise/2.14/user/articles/setting-your-commit-email-address", - "/en/enterprise/2.14/articles/setting-your-teams-profile-picture": "/en/enterprise/2.14/user/articles/setting-your-teams-profile-picture", - "/enterprise/2.14/user/articles/setting-your-teams-profile-picture": "/en/enterprise/2.14/user/articles/setting-your-teams-profile-picture", - "/enterprise/2.14/articles/setting-your-teams-profile-picture": "/en/enterprise/2.14/user/articles/setting-your-teams-profile-picture", - "/en/enterprise/2.14/articles/setting-your-username-in-git": "/en/enterprise/2.14/user/articles/setting-your-username-in-git", - "/enterprise/2.14/user/articles/setting-your-username-in-git": "/en/enterprise/2.14/user/articles/setting-your-username-in-git", - "/enterprise/2.14/articles/setting-your-username-in-git": "/en/enterprise/2.14/user/articles/setting-your-username-in-git", - "/en/enterprise/2.14/articles/sharing-filters": "/en/enterprise/2.14/user/articles/sharing-filters", - "/enterprise/2.14/user/articles/sharing-filters": "/en/enterprise/2.14/user/articles/sharing-filters", - "/enterprise/2.14/articles/sharing-filters": "/en/enterprise/2.14/user/articles/sharing-filters", - "/en/enterprise/2.14/articles/signing-commits": "/en/enterprise/2.14/user/articles/signing-commits", - "/enterprise/2.14/user/articles/signing-commits": "/en/enterprise/2.14/user/articles/signing-commits", - "/enterprise/2.14/articles/signing-commits": "/en/enterprise/2.14/user/articles/signing-commits", - "/en/enterprise/2.14/articles/signing-tags": "/en/enterprise/2.14/user/articles/signing-tags", - "/enterprise/2.14/user/articles/signing-tags": "/en/enterprise/2.14/user/articles/signing-tags", - "/enterprise/2.14/articles/signing-tags": "/en/enterprise/2.14/user/articles/signing-tags", - "/en/enterprise/2.14/articles/signing-up-for-github": "/en/enterprise/2.14/user/articles/signing-up-for-github", - "/enterprise/2.14/user/articles/signing-up-for-github": "/en/enterprise/2.14/user/articles/signing-up-for-github", - "/enterprise/2.14/articles/signing-up-for-github": "/en/enterprise/2.14/user/articles/signing-up-for-github", - "/en/enterprise/2.14/articles/sitemaps-for-github-pages": "/en/enterprise/2.14/user/articles/sitemaps-for-github-pages", - "/enterprise/2.14/user/articles/sitemaps-for-github-pages": "/en/enterprise/2.14/user/articles/sitemaps-for-github-pages", - "/enterprise/2.14/articles/sitemaps-for-github-pages": "/en/enterprise/2.14/user/articles/sitemaps-for-github-pages", - "/en/enterprise/2.14/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/sorting-issues-and-pull-requests", - "/enterprise/2.14/user/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/sorting-issues-and-pull-requests", - "/enterprise/2.14/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/sorting-issues-and-pull-requests", - "/en/enterprise/2.14/articles/sorting-search-results": "/en/enterprise/2.14/user/articles/sorting-search-results", - "/enterprise/2.14/user/articles/sorting-search-results": "/en/enterprise/2.14/user/articles/sorting-search-results", - "/enterprise/2.14/articles/sorting-search-results": "/en/enterprise/2.14/user/articles/sorting-search-results", - "/en/enterprise/2.14/articles/source-code-migration-tools": "/en/enterprise/2.14/user/articles/source-code-migration-tools", - "/enterprise/2.14/user/articles/source-code-migration-tools": "/en/enterprise/2.14/user/articles/source-code-migration-tools", - "/enterprise/2.14/articles/source-code-migration-tools": "/en/enterprise/2.14/user/articles/source-code-migration-tools", - "/en/enterprise/2.14/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.14/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.14/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.14/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.14/articles/subversion-properties-supported-by-github": "/en/enterprise/2.14/user/articles/subversion-properties-supported-by-github", - "/enterprise/2.14/user/articles/subversion-properties-supported-by-github": "/en/enterprise/2.14/user/articles/subversion-properties-supported-by-github", - "/enterprise/2.14/articles/subversion-properties-supported-by-github": "/en/enterprise/2.14/user/articles/subversion-properties-supported-by-github", - "/en/enterprise/2.14/articles/sudo-mode": "/en/enterprise/2.14/user/articles/sudo-mode", - "/enterprise/2.14/user/articles/sudo-mode": "/en/enterprise/2.14/user/articles/sudo-mode", - "/enterprise/2.14/articles/sudo-mode": "/en/enterprise/2.14/user/articles/sudo-mode", - "/en/enterprise/2.14/articles/support-for-subversion-clients": "/en/enterprise/2.14/user/articles/support-for-subversion-clients", - "/enterprise/2.14/user/articles/support-for-subversion-clients": "/en/enterprise/2.14/user/articles/support-for-subversion-clients", - "/enterprise/2.14/articles/support-for-subversion-clients": "/en/enterprise/2.14/user/articles/support-for-subversion-clients", - "/en/enterprise/2.14/articles/supported-browsers": "/en/enterprise/2.14/user/articles/supported-browsers", - "/enterprise/2.14/user/articles/supported-browsers": "/en/enterprise/2.14/user/articles/supported-browsers", - "/enterprise/2.14/articles/supported-browsers": "/en/enterprise/2.14/user/articles/supported-browsers", - "/en/enterprise/2.14/articles/syncing-a-fork": "/en/enterprise/2.14/user/articles/syncing-a-fork", - "/enterprise/2.14/user/articles/syncing-a-fork": "/en/enterprise/2.14/user/articles/syncing-a-fork", - "/enterprise/2.14/articles/syncing-a-fork": "/en/enterprise/2.14/user/articles/syncing-a-fork", - "/en/enterprise/2.14/articles/telling-git-about-your-signing-key": "/en/enterprise/2.14/user/articles/telling-git-about-your-signing-key", - "/enterprise/2.14/user/articles/telling-git-about-your-signing-key": "/en/enterprise/2.14/user/articles/telling-git-about-your-signing-key", - "/enterprise/2.14/articles/telling-git-about-your-signing-key": "/en/enterprise/2.14/user/articles/telling-git-about-your-signing-key", - "/en/enterprise/2.14/articles/testing-your-ssh-connection": "/en/enterprise/2.14/user/articles/testing-your-ssh-connection", - "/enterprise/2.14/user/articles/testing-your-ssh-connection": "/en/enterprise/2.14/user/articles/testing-your-ssh-connection", - "/enterprise/2.14/articles/testing-your-ssh-connection": "/en/enterprise/2.14/user/articles/testing-your-ssh-connection", - "/en/enterprise/2.14/articles/tracking-changes-in-a-comment": "/en/enterprise/2.14/user/articles/tracking-changes-in-a-comment", - "/enterprise/2.14/user/articles/tracking-changes-in-a-comment": "/en/enterprise/2.14/user/articles/tracking-changes-in-a-comment", - "/enterprise/2.14/articles/tracking-changes-in-a-comment": "/en/enterprise/2.14/user/articles/tracking-changes-in-a-comment", - "/en/enterprise/2.14/articles/tracking-changes-in-a-file": "/en/enterprise/2.14/user/articles/tracking-changes-in-a-file", - "/enterprise/2.14/user/articles/tracking-changes-in-a-file": "/en/enterprise/2.14/user/articles/tracking-changes-in-a-file", - "/enterprise/2.14/articles/tracking-changes-in-a-file": "/en/enterprise/2.14/user/articles/tracking-changes-in-a-file", - "/en/enterprise/2.14/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.14/user/articles/tracking-progress-on-your-project-board", - "/enterprise/2.14/user/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.14/user/articles/tracking-progress-on-your-project-board", - "/enterprise/2.14/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.14/user/articles/tracking-progress-on-your-project-board", - "/en/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.14/articles/transferring-a-repository": "/en/enterprise/2.14/user/articles/transferring-a-repository", - "/enterprise/2.14/user/articles/transferring-a-repository": "/en/enterprise/2.14/user/articles/transferring-a-repository", - "/enterprise/2.14/articles/transferring-a-repository": "/en/enterprise/2.14/user/articles/transferring-a-repository", - "/en/enterprise/2.14/articles/transferring-organization-ownership": "/en/enterprise/2.14/user/articles/transferring-organization-ownership", - "/enterprise/2.14/user/articles/transferring-organization-ownership": "/en/enterprise/2.14/user/articles/transferring-organization-ownership", - "/enterprise/2.14/articles/transferring-organization-ownership": "/en/enterprise/2.14/user/articles/transferring-organization-ownership", - "/en/enterprise/2.14/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification", - "/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification", - "/enterprise/2.14/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification", - "/en/enterprise/2.14/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline", - "/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline", - "/enterprise/2.14/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.14/articles/troubleshooting-commits": "/en/enterprise/2.14/user/articles/troubleshooting-commits", - "/enterprise/2.14/user/articles/troubleshooting-commits": "/en/enterprise/2.14/user/articles/troubleshooting-commits", - "/enterprise/2.14/articles/troubleshooting-commits": "/en/enterprise/2.14/user/articles/troubleshooting-commits", - "/en/enterprise/2.14/articles/troubleshooting-github-pages-builds": "/en/enterprise/2.14/user/articles/troubleshooting-github-pages-builds", - "/enterprise/2.14/user/articles/troubleshooting-github-pages-builds": "/en/enterprise/2.14/user/articles/troubleshooting-github-pages-builds", - "/enterprise/2.14/articles/troubleshooting-github-pages-builds": "/en/enterprise/2.14/user/articles/troubleshooting-github-pages-builds", - "/en/enterprise/2.14/articles/troubleshooting-search-queries": "/en/enterprise/2.14/user/articles/troubleshooting-search-queries", - "/enterprise/2.14/user/articles/troubleshooting-search-queries": "/en/enterprise/2.14/user/articles/troubleshooting-search-queries", - "/enterprise/2.14/articles/troubleshooting-search-queries": "/en/enterprise/2.14/user/articles/troubleshooting-search-queries", - "/en/enterprise/2.14/articles/troubleshooting-ssh": "/en/enterprise/2.14/user/articles/troubleshooting-ssh", - "/enterprise/2.14/user/articles/troubleshooting-ssh": "/en/enterprise/2.14/user/articles/troubleshooting-ssh", - "/enterprise/2.14/articles/troubleshooting-ssh": "/en/enterprise/2.14/user/articles/troubleshooting-ssh", - "/en/enterprise/2.14/articles/types-of-github-accounts": "/en/enterprise/2.14/user/articles/types-of-github-accounts", - "/enterprise/2.14/user/articles/types-of-github-accounts": "/en/enterprise/2.14/user/articles/types-of-github-accounts", - "/enterprise/2.14/articles/types-of-github-accounts": "/en/enterprise/2.14/user/articles/types-of-github-accounts", - "/en/enterprise/2.14/articles/types-of-required-status-checks": "/en/enterprise/2.14/user/articles/types-of-required-status-checks", - "/enterprise/2.14/user/articles/types-of-required-status-checks": "/en/enterprise/2.14/user/articles/types-of-required-status-checks", - "/enterprise/2.14/articles/types-of-required-status-checks": "/en/enterprise/2.14/user/articles/types-of-required-status-checks", - "/en/enterprise/2.14/articles/understanding-connections-between-repositories": "/en/enterprise/2.14/user/articles/understanding-connections-between-repositories", - "/enterprise/2.14/user/articles/understanding-connections-between-repositories": "/en/enterprise/2.14/user/articles/understanding-connections-between-repositories", - "/enterprise/2.14/articles/understanding-connections-between-repositories": "/en/enterprise/2.14/user/articles/understanding-connections-between-repositories", - "/en/enterprise/2.14/articles/understanding-the-search-syntax": "/en/enterprise/2.14/user/articles/understanding-the-search-syntax", - "/enterprise/2.14/user/articles/understanding-the-search-syntax": "/en/enterprise/2.14/user/articles/understanding-the-search-syntax", - "/enterprise/2.14/articles/understanding-the-search-syntax": "/en/enterprise/2.14/user/articles/understanding-the-search-syntax", - "/en/enterprise/2.14/articles/unpublishing-a-project-pages-site": "/en/enterprise/2.14/user/articles/unpublishing-a-project-pages-site", - "/enterprise/2.14/user/articles/unpublishing-a-project-pages-site": "/en/enterprise/2.14/user/articles/unpublishing-a-project-pages-site", - "/enterprise/2.14/articles/unpublishing-a-project-pages-site": "/en/enterprise/2.14/user/articles/unpublishing-a-project-pages-site", - "/en/enterprise/2.14/articles/unpublishing-a-user-pages-site": "/en/enterprise/2.14/user/articles/unpublishing-a-user-pages-site", - "/enterprise/2.14/user/articles/unpublishing-a-user-pages-site": "/en/enterprise/2.14/user/articles/unpublishing-a-user-pages-site", - "/enterprise/2.14/articles/unpublishing-a-user-pages-site": "/en/enterprise/2.14/user/articles/unpublishing-a-user-pages-site", - "/en/enterprise/2.14/articles/updating-an-expired-gpg-key": "/en/enterprise/2.14/user/articles/updating-an-expired-gpg-key", - "/enterprise/2.14/user/articles/updating-an-expired-gpg-key": "/en/enterprise/2.14/user/articles/updating-an-expired-gpg-key", - "/enterprise/2.14/articles/updating-an-expired-gpg-key": "/en/enterprise/2.14/user/articles/updating-an-expired-gpg-key", - "/en/enterprise/2.14/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain", - "/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain", - "/enterprise/2.14/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.14/articles/updating-your-github-access-credentials": "/en/enterprise/2.14/user/articles/updating-your-github-access-credentials", - "/enterprise/2.14/user/articles/updating-your-github-access-credentials": "/en/enterprise/2.14/user/articles/updating-your-github-access-credentials", - "/enterprise/2.14/articles/updating-your-github-access-credentials": "/en/enterprise/2.14/user/articles/updating-your-github-access-credentials", - "/en/enterprise/2.14/articles/updating-your-markdown-processor-to-kramdown": "/en/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown", - "/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown": "/en/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown", - "/enterprise/2.14/articles/updating-your-markdown-processor-to-kramdown": "/en/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown", - "/en/enterprise/2.14/articles/user-organization-and-project-pages": "/en/enterprise/2.14/user/articles/user-organization-and-project-pages", - "/enterprise/2.14/user/articles/user-organization-and-project-pages": "/en/enterprise/2.14/user/articles/user-organization-and-project-pages", - "/enterprise/2.14/articles/user-organization-and-project-pages": "/en/enterprise/2.14/user/articles/user-organization-and-project-pages", - "/en/enterprise/2.14/articles/using-a-static-site-generator-other-than-jekyll": "/en/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll", - "/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll": "/en/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll", - "/enterprise/2.14/articles/using-a-static-site-generator-other-than-jekyll": "/en/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll", - "/en/enterprise/2.14/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.14/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.14/articles/using-advanced-git-commands": "/en/enterprise/2.14/user/articles/using-advanced-git-commands", - "/enterprise/2.14/user/articles/using-advanced-git-commands": "/en/enterprise/2.14/user/articles/using-advanced-git-commands", - "/enterprise/2.14/articles/using-advanced-git-commands": "/en/enterprise/2.14/user/articles/using-advanced-git-commands", - "/en/enterprise/2.14/articles/using-common-git-commands": "/en/enterprise/2.14/user/articles/using-common-git-commands", - "/enterprise/2.14/user/articles/using-common-git-commands": "/en/enterprise/2.14/user/articles/using-common-git-commands", - "/enterprise/2.14/articles/using-common-git-commands": "/en/enterprise/2.14/user/articles/using-common-git-commands", - "/en/enterprise/2.14/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line", - "/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line", - "/enterprise/2.14/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line", - "/en/enterprise/2.14/articles/using-github": "/en/enterprise/2.14/user/articles/using-github", - "/enterprise/2.14/user/articles/using-github": "/en/enterprise/2.14/user/articles/using-github", - "/enterprise/2.14/articles/using-github": "/en/enterprise/2.14/user/articles/using-github", - "/en/enterprise/2.14/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/en/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/en/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/enterprise/2.14/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/en/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/en/enterprise/2.14/articles/using-saved-replies": "/en/enterprise/2.14/user/articles/using-saved-replies", - "/enterprise/2.14/user/articles/using-saved-replies": "/en/enterprise/2.14/user/articles/using-saved-replies", - "/enterprise/2.14/articles/using-saved-replies": "/en/enterprise/2.14/user/articles/using-saved-replies", - "/en/enterprise/2.14/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.14/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.14/articles/using-syntax-highlighting-on-github-pages": "/en/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages", - "/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages": "/en/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages", - "/enterprise/2.14/articles/using-syntax-highlighting-on-github-pages": "/en/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages", - "/en/enterprise/2.14/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/en/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/en/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/enterprise/2.14/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/en/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/en/enterprise/2.14/articles/versioning-large-files": "/en/enterprise/2.14/user/articles/versioning-large-files", - "/enterprise/2.14/user/articles/versioning-large-files": "/en/enterprise/2.14/user/articles/versioning-large-files", - "/enterprise/2.14/articles/versioning-large-files": "/en/enterprise/2.14/user/articles/versioning-large-files", - "/en/enterprise/2.14/articles/viewing-a-projects-contributors": "/en/enterprise/2.14/user/articles/viewing-a-projects-contributors", - "/enterprise/2.14/user/articles/viewing-a-projects-contributors": "/en/enterprise/2.14/user/articles/viewing-a-projects-contributors", - "/enterprise/2.14/articles/viewing-a-projects-contributors": "/en/enterprise/2.14/user/articles/viewing-a-projects-contributors", - "/en/enterprise/2.14/articles/viewing-a-pull-request-review": "/en/enterprise/2.14/user/articles/viewing-a-pull-request-review", - "/enterprise/2.14/user/articles/viewing-a-pull-request-review": "/en/enterprise/2.14/user/articles/viewing-a-pull-request-review", - "/enterprise/2.14/articles/viewing-a-pull-request-review": "/en/enterprise/2.14/user/articles/viewing-a-pull-request-review", - "/en/enterprise/2.14/articles/viewing-a-repositorys-network": "/en/enterprise/2.14/user/articles/viewing-a-repositorys-network", - "/enterprise/2.14/user/articles/viewing-a-repositorys-network": "/en/enterprise/2.14/user/articles/viewing-a-repositorys-network", - "/enterprise/2.14/articles/viewing-a-repositorys-network": "/en/enterprise/2.14/user/articles/viewing-a-repositorys-network", - "/en/enterprise/2.14/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity", - "/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity", - "/enterprise/2.14/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.14/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes", - "/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes", - "/enterprise/2.14/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.14/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.14/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.14/articles/viewing-and-comparing-commits": "/en/enterprise/2.14/user/articles/viewing-and-comparing-commits", - "/enterprise/2.14/user/articles/viewing-and-comparing-commits": "/en/enterprise/2.14/user/articles/viewing-and-comparing-commits", - "/enterprise/2.14/articles/viewing-and-comparing-commits": "/en/enterprise/2.14/user/articles/viewing-and-comparing-commits", - "/en/enterprise/2.14/articles/viewing-branches-in-your-repository": "/en/enterprise/2.14/user/articles/viewing-branches-in-your-repository", - "/enterprise/2.14/user/articles/viewing-branches-in-your-repository": "/en/enterprise/2.14/user/articles/viewing-branches-in-your-repository", - "/enterprise/2.14/articles/viewing-branches-in-your-repository": "/en/enterprise/2.14/user/articles/viewing-branches-in-your-repository", - "/en/enterprise/2.14/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.14/user/articles/viewing-contributions-on-your-profile", - "/enterprise/2.14/user/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.14/user/articles/viewing-contributions-on-your-profile", - "/enterprise/2.14/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.14/user/articles/viewing-contributions-on-your-profile", - "/en/enterprise/2.14/articles/viewing-jekyll-build-error-messages": "/en/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages", - "/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages": "/en/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages", - "/enterprise/2.14/articles/viewing-jekyll-build-error-messages": "/en/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages", - "/en/enterprise/2.14/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization", - "/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization", - "/enterprise/2.14/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.14/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.14/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.14/articles/viewing-your-milestones-progress": "/en/enterprise/2.14/user/articles/viewing-your-milestones-progress", - "/enterprise/2.14/user/articles/viewing-your-milestones-progress": "/en/enterprise/2.14/user/articles/viewing-your-milestones-progress", - "/enterprise/2.14/articles/viewing-your-milestones-progress": "/en/enterprise/2.14/user/articles/viewing-your-milestones-progress", - "/en/enterprise/2.14/articles/viewing-your-repositorys-tags": "/en/enterprise/2.14/user/articles/viewing-your-repositorys-tags", - "/enterprise/2.14/user/articles/viewing-your-repositorys-tags": "/en/enterprise/2.14/user/articles/viewing-your-repositorys-tags", - "/enterprise/2.14/articles/viewing-your-repositorys-tags": "/en/enterprise/2.14/user/articles/viewing-your-repositorys-tags", - "/en/enterprise/2.14/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.14/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.14/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.14/user/articles/visualizing-commits-in-a-repository", - "/enterprise/2.14/user/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.14/user/articles/visualizing-commits-in-a-repository", - "/enterprise/2.14/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.14/user/articles/visualizing-commits-in-a-repository", - "/en/enterprise/2.14/articles/watching-and-unwatching-repositories": "/en/enterprise/2.14/user/articles/watching-and-unwatching-repositories", - "/enterprise/2.14/user/articles/watching-and-unwatching-repositories": "/en/enterprise/2.14/user/articles/watching-and-unwatching-repositories", - "/enterprise/2.14/articles/watching-and-unwatching-repositories": "/en/enterprise/2.14/user/articles/watching-and-unwatching-repositories", - "/en/enterprise/2.14/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions", - "/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions", - "/enterprise/2.14/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions", - "/en/enterprise/2.14/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.14/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.14/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.14/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.14/articles/what-is-github-pages": "/en/enterprise/2.14/user/articles/what-is-github-pages", - "/enterprise/2.14/user/articles/what-is-github-pages": "/en/enterprise/2.14/user/articles/what-is-github-pages", - "/enterprise/2.14/articles/what-is-github-pages": "/en/enterprise/2.14/user/articles/what-is-github-pages", - "/en/enterprise/2.14/articles/which-remote-url-should-i-use": "/en/enterprise/2.14/user/articles/which-remote-url-should-i-use", - "/enterprise/2.14/user/articles/which-remote-url-should-i-use": "/en/enterprise/2.14/user/articles/which-remote-url-should-i-use", - "/enterprise/2.14/articles/which-remote-url-should-i-use": "/en/enterprise/2.14/user/articles/which-remote-url-should-i-use", - "/en/enterprise/2.14/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.14/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.14/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.14/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.14/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.14/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.14/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password", - "/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password", - "/enterprise/2.14/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.14/articles/working-with-advanced-formatting": "/en/enterprise/2.14/user/articles/working-with-advanced-formatting", - "/enterprise/2.14/user/articles/working-with-advanced-formatting": "/en/enterprise/2.14/user/articles/working-with-advanced-formatting", - "/enterprise/2.14/articles/working-with-advanced-formatting": "/en/enterprise/2.14/user/articles/working-with-advanced-formatting", - "/en/enterprise/2.14/articles/working-with-forks": "/en/enterprise/2.14/user/articles/working-with-forks", - "/enterprise/2.14/user/articles/working-with-forks": "/en/enterprise/2.14/user/articles/working-with-forks", - "/enterprise/2.14/articles/working-with-forks": "/en/enterprise/2.14/user/articles/working-with-forks", - "/en/enterprise/2.14/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.14/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.14/articles/working-with-large-files": "/en/enterprise/2.14/user/articles/working-with-large-files", - "/enterprise/2.14/user/articles/working-with-large-files": "/en/enterprise/2.14/user/articles/working-with-large-files", - "/enterprise/2.14/articles/working-with-large-files": "/en/enterprise/2.14/user/articles/working-with-large-files", - "/en/enterprise/2.14/articles/working-with-non-code-files": "/en/enterprise/2.14/user/articles/working-with-non-code-files", - "/enterprise/2.14/user/articles/working-with-non-code-files": "/en/enterprise/2.14/user/articles/working-with-non-code-files", - "/enterprise/2.14/articles/working-with-non-code-files": "/en/enterprise/2.14/user/articles/working-with-non-code-files", - "/en/enterprise/2.14/articles/working-with-pre-receive-hooks": "/en/enterprise/2.14/user/articles/working-with-pre-receive-hooks", - "/enterprise/2.14/user/articles/working-with-pre-receive-hooks": "/en/enterprise/2.14/user/articles/working-with-pre-receive-hooks", - "/enterprise/2.14/articles/working-with-pre-receive-hooks": "/en/enterprise/2.14/user/articles/working-with-pre-receive-hooks", - "/en/enterprise/2.14/articles/working-with-saved-replies": "/en/enterprise/2.14/user/articles/working-with-saved-replies", - "/enterprise/2.14/user/articles/working-with-saved-replies": "/en/enterprise/2.14/user/articles/working-with-saved-replies", - "/enterprise/2.14/articles/working-with-saved-replies": "/en/enterprise/2.14/user/articles/working-with-saved-replies", - "/en/enterprise/2.14/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.14/user/articles/working-with-ssh-key-passphrases", - "/enterprise/2.14/user/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.14/user/articles/working-with-ssh-key-passphrases", - "/enterprise/2.14/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.14/user/articles/working-with-ssh-key-passphrases", - "/en/enterprise/2.14/articles/working-with-subversion-on-github": "/en/enterprise/2.14/user/articles/working-with-subversion-on-github", - "/enterprise/2.14/user/articles/working-with-subversion-on-github": "/en/enterprise/2.14/user/articles/working-with-subversion-on-github", - "/enterprise/2.14/articles/working-with-subversion-on-github": "/en/enterprise/2.14/user/articles/working-with-subversion-on-github", - "/en/enterprise/2.14/user/categories/admin/guidesistering-a-repository": "/en/enterprise/2.14/user/categories/administering-a-repository", - "/en/enterprise/2.14/categories/administering-a-repository": "/en/enterprise/2.14/user/categories/administering-a-repository", - "/enterprise/2.14/user/categories/administering-a-repository": "/en/enterprise/2.14/user/categories/administering-a-repository", - "/enterprise/2.14/user/categories/admin/guidesistering-a-repository": "/en/enterprise/2.14/user/categories/administering-a-repository", - "/enterprise/2.14/categories/administering-a-repository": "/en/enterprise/2.14/user/categories/administering-a-repository", - "/en/enterprise/2.14/categories/authenticating-to-github": "/en/enterprise/2.14/user/categories/authenticating-to-github", - "/enterprise/2.14/user/categories/authenticating-to-github": "/en/enterprise/2.14/user/categories/authenticating-to-github", - "/enterprise/2.14/categories/authenticating-to-github": "/en/enterprise/2.14/user/categories/authenticating-to-github", - "/en/enterprise/2.14/categories/building-a-strong-community": "/en/enterprise/2.14/user/categories/building-a-strong-community", - "/enterprise/2.14/user/categories/building-a-strong-community": "/en/enterprise/2.14/user/categories/building-a-strong-community", - "/enterprise/2.14/categories/building-a-strong-community": "/en/enterprise/2.14/user/categories/building-a-strong-community", - "/en/enterprise/2.14/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests", - "/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests", - "/enterprise/2.14/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.14/categories/committing-changes-to-your-project": "/en/enterprise/2.14/user/categories/committing-changes-to-your-project", - "/enterprise/2.14/user/categories/committing-changes-to-your-project": "/en/enterprise/2.14/user/categories/committing-changes-to-your-project", - "/enterprise/2.14/categories/committing-changes-to-your-project": "/en/enterprise/2.14/user/categories/committing-changes-to-your-project", - "/en/enterprise/2.14/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories", - "/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories", - "/enterprise/2.14/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.14/categories/customizing-github-pages": "/en/enterprise/2.14/user/categories/customizing-github-pages", - "/enterprise/2.14/user/categories/customizing-github-pages": "/en/enterprise/2.14/user/categories/customizing-github-pages", - "/enterprise/2.14/categories/customizing-github-pages": "/en/enterprise/2.14/user/categories/customizing-github-pages", - "/en/enterprise/2.14/categories/extending-github": "/en/enterprise/2.14/user/categories/extending-github", - "/enterprise/2.14/user/categories/extending-github": "/en/enterprise/2.14/user/categories/extending-github", - "/enterprise/2.14/categories/extending-github": "/en/enterprise/2.14/user/categories/extending-github", - "/en/enterprise/2.14/categories/getting-started-with-github": "/en/enterprise/2.14/user/categories/getting-started-with-github", - "/enterprise/2.14/user/categories/getting-started-with-github": "/en/enterprise/2.14/user/categories/getting-started-with-github", - "/enterprise/2.14/categories/getting-started-with-github": "/en/enterprise/2.14/user/categories/getting-started-with-github", - "/en/enterprise/2.14/categories/github-pages-basics": "/en/enterprise/2.14/user/categories/github-pages-basics", - "/enterprise/2.14/user/categories/github-pages-basics": "/en/enterprise/2.14/user/categories/github-pages-basics", - "/enterprise/2.14/categories/github-pages-basics": "/en/enterprise/2.14/user/categories/github-pages-basics", - "/en/enterprise/2.14/categories/importing-your-projects-to-github": "/en/enterprise/2.14/user/categories/importing-your-projects-to-github", - "/enterprise/2.14/user/categories/importing-your-projects-to-github": "/en/enterprise/2.14/user/categories/importing-your-projects-to-github", - "/enterprise/2.14/categories/importing-your-projects-to-github": "/en/enterprise/2.14/user/categories/importing-your-projects-to-github", - "/en/enterprise/2.14/categories/managing-files-in-a-repository": "/en/enterprise/2.14/user/categories/managing-files-in-a-repository", - "/enterprise/2.14/user/categories/managing-files-in-a-repository": "/en/enterprise/2.14/user/categories/managing-files-in-a-repository", - "/enterprise/2.14/categories/managing-files-in-a-repository": "/en/enterprise/2.14/user/categories/managing-files-in-a-repository", - "/en/enterprise/2.14/categories/managing-large-files": "/en/enterprise/2.14/user/categories/managing-large-files", - "/enterprise/2.14/user/categories/managing-large-files": "/en/enterprise/2.14/user/categories/managing-large-files", - "/enterprise/2.14/categories/managing-large-files": "/en/enterprise/2.14/user/categories/managing-large-files", - "/en/enterprise/2.14/categories/managing-your-work-on-github": "/en/enterprise/2.14/user/categories/managing-your-work-on-github", - "/enterprise/2.14/user/categories/managing-your-work-on-github": "/en/enterprise/2.14/user/categories/managing-your-work-on-github", - "/enterprise/2.14/categories/managing-your-work-on-github": "/en/enterprise/2.14/user/categories/managing-your-work-on-github", - "/en/enterprise/2.14/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github", - "/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github", - "/enterprise/2.14/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.14/categories/searching-for-information-on-github": "/en/enterprise/2.14/user/categories/searching-for-information-on-github", - "/enterprise/2.14/user/categories/searching-for-information-on-github": "/en/enterprise/2.14/user/categories/searching-for-information-on-github", - "/enterprise/2.14/categories/searching-for-information-on-github": "/en/enterprise/2.14/user/categories/searching-for-information-on-github", - "/en/enterprise/2.14/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.14/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.14/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile", - "/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile", - "/enterprise/2.14/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.14/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account", - "/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account", - "/enterprise/2.14/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.14/categories/using-git": "/en/enterprise/2.14/user/categories/using-git", - "/enterprise/2.14/user/categories/using-git": "/en/enterprise/2.14/user/categories/using-git", - "/enterprise/2.14/categories/using-git": "/en/enterprise/2.14/user/categories/using-git", - "/en/enterprise/2.14/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs", - "/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs", - "/enterprise/2.14/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs", - "/en/enterprise/2.14/categories/writing-on-github": "/en/enterprise/2.14/user/categories/writing-on-github", - "/enterprise/2.14/user/categories/writing-on-github": "/en/enterprise/2.14/user/categories/writing-on-github", - "/enterprise/2.14/categories/writing-on-github": "/en/enterprise/2.14/user/categories/writing-on-github", - "/enterprise/2.14/user": "/en/enterprise/2.14/user", - "/ja/enterprise/2.14/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/ja/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/ja/enterprise/2.14/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/ja/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/ja/enterprise/2.14/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/ja/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/ja/enterprise/2.14/admin/guides/articles/using-github-task-runner": "/ja/enterprise/2.14/admin/articles/using-github-task-runner", - "/ja/enterprise/2.14/admin/guides/clustering/about-cluster-nodes": "/ja/enterprise/2.14/admin/clustering/about-cluster-nodes", - "/ja/enterprise/2.14/admin/guides/clustering/clustering-overview": "/ja/enterprise/2.14/admin/clustering/clustering-overview", - "/ja/enterprise/2.14/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/ja/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/ja/enterprise/2.14/admin/guides/clustering/evacuating-a-cluster-node": "/ja/enterprise/2.14/admin/clustering/evacuating-a-cluster-node", - "/ja/enterprise/2.14/admin/guides/clustering": "/ja/enterprise/2.14/admin/clustering", - "/ja/enterprise/2.14/admin/guides/clustering/initializing-the-cluster": "/ja/enterprise/2.14/admin/clustering/initializing-the-cluster", - "/ja/enterprise/2.14/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/ja/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster", - "/ja/enterprise/2.14/admin/guides/clustering/monitoring-cluster-nodes": "/ja/enterprise/2.14/admin/clustering/monitoring-cluster-nodes", - "/ja/enterprise/2.14/admin/guides/clustering/network-configuration": "/ja/enterprise/2.14/admin/clustering/network-configuration", - "/ja/enterprise/2.14/admin/guides/clustering/replacing-a-cluster-node": "/ja/enterprise/2.14/admin/clustering/replacing-a-cluster-node", - "/ja/enterprise/2.14/admin/guides/clustering/setting-up-the-cluster-instances": "/ja/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances", - "/ja/enterprise/2.14/admin/guides/clustering/upgrading-a-cluster": "/ja/enterprise/2.14/admin/clustering/upgrading-a-cluster", - "/ja/enterprise/2.14/admin/guides/developer-workflow/about-pre-receive-hooks": "/ja/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks", - "/ja/enterprise/2.14/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/ja/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/ja/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/ja/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/ja/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/ja/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/ja/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/ja/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/ja/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes": "/ja/enterprise/2.14/admin/developer-workflow/blocking-force-pushes", - "/ja/enterprise/2.14/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/ja/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/ja/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/ja/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins", - "/ja/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/ja/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci", - "/ja/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/ja/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/ja/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/ja/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/ja/enterprise/2.14/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/ja/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations", - "/ja/enterprise/2.14/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/ja/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/ja/enterprise/2.14/admin/guides/developer-workflow": "/ja/enterprise/2.14/admin/developer-workflow", - "/ja/enterprise/2.14/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/ja/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/ja/enterprise/2.14/admin/guides/developer-workflow/managing-projects-using-jira": "/ja/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira", - "/ja/enterprise/2.14/admin/guides/developer-workflow/troubleshooting-service-hooks": "/ja/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks", - "/ja/enterprise/2.14/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/ja/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/ja/enterprise/2.14/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/ja/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/ja/enterprise/2.14/admin/guides/enterprise-support/about-github-enterprise-support": "/ja/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support", - "/ja/enterprise/2.14/admin/guides/enterprise-support": "/ja/enterprise/2.14/admin/enterprise-support", - "/ja/enterprise/2.14/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/ja/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket", - "/ja/enterprise/2.14/admin/guides/enterprise-support/providing-data-to-github-support": "/ja/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support", - "/ja/enterprise/2.14/admin/guides/enterprise-support/reaching-github-support": "/ja/enterprise/2.14/admin/enterprise-support/reaching-github-support", - "/ja/enterprise/2.14/admin/guides/enterprise-support/receiving-help-from-github-support": "/ja/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support", - "/ja/enterprise/2.14/admin/guides/enterprise-support/submitting-a-ticket": "/ja/enterprise/2.14/admin/enterprise-support/submitting-a-ticket", - "/ja/enterprise/2.14/admin/guides": "/ja/enterprise/2.14/admin", - "/ja/enterprise/2.14/admin/guides/installation/about-geo-replication": "/ja/enterprise/2.14/admin/installation/about-geo-replication", - "/ja/enterprise/2.14/admin/guides/installation/about-high-availability-configuration": "/ja/enterprise/2.14/admin/installation/about-high-availability-configuration", - "/ja/enterprise/2.14/admin/guides/installation/about-the-github-enterprise-server-api": "/ja/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api", - "/ja/enterprise/2.14/admin/guides/installation/accessing-the-administrative-shell-ssh": "/ja/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh", - "/ja/enterprise/2.14/admin/guides/installation/accessing-the-management-console": "/ja/enterprise/2.14/admin/installation/accessing-the-management-console", - "/ja/enterprise/2.14/admin/guides/installation/accessing-the-monitor-dashboard": "/ja/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard", - "/ja/enterprise/2.14/admin/guides/installation/activity-dashboard": "/ja/enterprise/2.14/admin/installation/activity-dashboard", - "/ja/enterprise/2.14/admin/guides/installation/audit-logging": "/ja/enterprise/2.14/admin/installation/audit-logging", - "/ja/enterprise/2.14/admin/guides/installation/audited-actions": "/ja/enterprise/2.14/admin/installation/audited-actions", - "/ja/enterprise/2.14/admin/guides/installation/command-line-utilities": "/ja/enterprise/2.14/admin/installation/command-line-utilities", - "/ja/enterprise/2.14/admin/guides/installation/configuring-a-hostname": "/ja/enterprise/2.14/admin/installation/configuring-a-hostname", - "/ja/enterprise/2.14/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/ja/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server", - "/ja/enterprise/2.14/admin/guides/installation/configuring-backups-on-your-appliance": "/ja/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance", - "/ja/enterprise/2.14/admin/guides/installation/configuring-built-in-firewall-rules": "/ja/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules", - "/ja/enterprise/2.14/admin/guides/installation/configuring-collectd": "/ja/enterprise/2.14/admin/installation/configuring-collectd", - "/ja/enterprise/2.14/admin/guides/installation/configuring-dns-nameservers": "/ja/enterprise/2.14/admin/installation/configuring-dns-nameservers", - "/ja/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/ja/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/ja/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/ja/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage": "/ja/enterprise/2.14/admin/installation/configuring-git-large-file-storage", - "/ja/enterprise/2.14/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/ja/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/ja/enterprise/2.14/admin/guides/installation/configuring-github-pages-on-your-appliance": "/ja/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance", - "/ja/enterprise/2.14/admin/guides/installation/configuring-rate-limits": "/ja/enterprise/2.14/admin/installation/configuring-rate-limits", - "/ja/enterprise/2.14/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/ja/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/ja/enterprise/2.14/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/ja/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance", - "/ja/enterprise/2.14/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/ja/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/ja/enterprise/2.14/admin/guides/installation/configuring-time-synchronization": "/ja/enterprise/2.14/admin/installation/configuring-time-synchronization", - "/ja/enterprise/2.14/admin/guides/installation/configuring-tls": "/ja/enterprise/2.14/admin/installation/configuring-tls", - "/ja/enterprise/2.14/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/ja/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/ja/enterprise/2.14/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/ja/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/ja/enterprise/2.14/admin/guides/installation/creating-a-high-availability-replica": "/ja/enterprise/2.14/admin/installation/creating-a-high-availability-replica", - "/ja/enterprise/2.14/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/ja/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/ja/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/ja/enterprise/2.14/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/ja/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode", - "/ja/enterprise/2.14/admin/guides/installation/enabling-automatic-update-checks": "/ja/enterprise/2.14/admin/installation/enabling-automatic-update-checks", - "/ja/enterprise/2.14/admin/guides/installation/enabling-private-mode": "/ja/enterprise/2.14/admin/installation/enabling-private-mode", - "/ja/enterprise/2.14/admin/guides/installation/enabling-subdomain-isolation": "/ja/enterprise/2.14/admin/installation/enabling-subdomain-isolation", - "/ja/enterprise/2.14/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.14/admin/guides/installation/increasing-cpu-or-memory-resources": "/ja/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources", - "/ja/enterprise/2.14/admin/guides/installation/increasing-storage-capacity": "/ja/enterprise/2.14/admin/installation/increasing-storage-capacity", - "/ja/enterprise/2.14/admin/guides/installation": "/ja/enterprise/2.14/admin/installation", - "/ja/enterprise/2.14/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/ja/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-aws": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-azure": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware", - "/ja/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/ja/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver", - "/ja/enterprise/2.14/admin/guides/installation/log-forwarding": "/ja/enterprise/2.14/admin/installation/log-forwarding", - "/ja/enterprise/2.14/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/ja/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/ja/enterprise/2.14/admin/guides/installation/managing-your-github-enterprise-server-license": "/ja/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license", - "/ja/enterprise/2.14/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/ja/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/ja/enterprise/2.14/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/ja/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/ja/enterprise/2.14/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/ja/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/ja/enterprise/2.14/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/ja/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/ja/enterprise/2.14/admin/guides/installation/monitoring-using-snmp": "/ja/enterprise/2.14/admin/installation/monitoring-using-snmp", - "/ja/enterprise/2.14/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/ja/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/ja/enterprise/2.14/admin/guides/installation/network-ports": "/ja/enterprise/2.14/admin/installation/network-ports", - "/ja/enterprise/2.14/admin/guides/installation/recommended-alert-thresholds": "/ja/enterprise/2.14/admin/installation/recommended-alert-thresholds", - "/ja/enterprise/2.14/admin/guides/installation/recovering-a-high-availability-configuration": "/ja/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration", - "/ja/enterprise/2.14/admin/guides/installation/removing-a-high-availability-replica": "/ja/enterprise/2.14/admin/installation/removing-a-high-availability-replica", - "/ja/enterprise/2.14/admin/guides/installation/searching-the-audit-log": "/ja/enterprise/2.14/admin/installation/searching-the-audit-log", - "/ja/enterprise/2.14/admin/guides/installation/setting-git-push-limits": "/ja/enterprise/2.14/admin/installation/setting-git-push-limits", - "/ja/enterprise/2.14/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/ja/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance", - "/ja/enterprise/2.14/admin/guides/installation/setting-up-a-staging-instance": "/ja/enterprise/2.14/admin/installation/setting-up-a-staging-instance", - "/ja/enterprise/2.14/admin/guides/installation/setting-up-external-monitoring": "/ja/enterprise/2.14/admin/installation/setting-up-external-monitoring", - "/ja/enterprise/2.14/admin/guides/installation/site-admin-dashboard": "/ja/enterprise/2.14/admin/installation/site-admin-dashboard", - "/ja/enterprise/2.14/admin/guides/installation/system-overview": "/ja/enterprise/2.14/admin/installation/system-overview", - "/ja/enterprise/2.14/admin/guides/installation/troubleshooting-ssl-errors": "/ja/enterprise/2.14/admin/installation/troubleshooting-ssl-errors", - "/ja/enterprise/2.14/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/ja/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/ja/enterprise/2.14/admin/guides/installation/upgrade-requirements": "/ja/enterprise/2.14/admin/installation/upgrade-requirements", - "/ja/enterprise/2.14/admin/guides/installation/upgrading-github-enterprise-server": "/ja/enterprise/2.14/admin/installation/upgrading-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/ja/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/ja/enterprise/2.14/admin/guides/installation/validating-your-domain-settings": "/ja/enterprise/2.14/admin/installation/validating-your-domain-settings", - "/ja/enterprise/2.14/admin/guides/installation/viewing-push-logs": "/ja/enterprise/2.14/admin/installation/viewing-push-logs", - "/ja/enterprise/2.14/admin/guides/migrations/about-migrations": "/ja/enterprise/2.14/admin/migrations/about-migrations", - "/ja/enterprise/2.14/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/ja/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/ja/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/ja/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-githubcom": "/ja/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom", - "/ja/enterprise/2.14/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/ja/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/ja/enterprise/2.14/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/ja/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/ja/enterprise/2.14/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/ja/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts", - "/ja/enterprise/2.14/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/ja/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems", - "/ja/enterprise/2.14/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/ja/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/migrations": "/ja/enterprise/2.14/admin/migrations", - "/ja/enterprise/2.14/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/ja/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/ja/enterprise/2.14/admin/guides/migrations/preparing-the-githubcom-source-organization": "/ja/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization", - "/ja/enterprise/2.14/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/ja/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/ja/enterprise/2.14/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/ja/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/ja/enterprise/2.14/admin/guides/migrations/reviewing-migration-conflicts": "/ja/enterprise/2.14/admin/migrations/reviewing-migration-conflicts", - "/ja/enterprise/2.14/admin/guides/migrations/reviewing-migration-data": "/ja/enterprise/2.14/admin/migrations/reviewing-migration-data", - "/ja/enterprise/2.14/admin/guides/user-management/about-global-webhooks": "/ja/enterprise/2.14/admin/user-management/about-global-webhooks", - "/ja/enterprise/2.14/admin/guides/user-management/adding-people-to-teams": "/ja/enterprise/2.14/admin/user-management/adding-people-to-teams", - "/ja/enterprise/2.14/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/ja/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/ja/enterprise/2.14/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/ja/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/ja/enterprise/2.14/admin/guides/user-management/archiving-and-unarchiving-repositories": "/ja/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories", - "/ja/enterprise/2.14/admin/guides/user-management/auditing-ssh-keys": "/ja/enterprise/2.14/admin/user-management/auditing-ssh-keys", - "/ja/enterprise/2.14/admin/guides/user-management/auditing-users-across-your-instance": "/ja/enterprise/2.14/admin/user-management/auditing-users-across-your-instance", - "/ja/enterprise/2.14/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/ja/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/ja/enterprise/2.14/admin/guides/user-management/basic-account-settings": "/ja/enterprise/2.14/admin/user-management/basic-account-settings", - "/ja/enterprise/2.14/admin/guides/user-management/best-practices-for-user-security": "/ja/enterprise/2.14/admin/user-management/best-practices-for-user-security", - "/ja/enterprise/2.14/admin/guides/user-management/changing-authentication-methods": "/ja/enterprise/2.14/admin/user-management/changing-authentication-methods", - "/ja/enterprise/2.14/admin/guides/user-management/configuring-email-for-notifications": "/ja/enterprise/2.14/admin/user-management/configuring-email-for-notifications", - "/ja/enterprise/2.14/admin/guides/user-management/configuring-visibility-for-organization-membership": "/ja/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership", - "/ja/enterprise/2.14/admin/guides/user-management/creating-organizations": "/ja/enterprise/2.14/admin/user-management/creating-organizations", - "/ja/enterprise/2.14/admin/guides/user-management/creating-teams": "/ja/enterprise/2.14/admin/user-management/creating-teams", - "/ja/enterprise/2.14/admin/guides/user-management/customizing-user-messages-on-your-instance": "/ja/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance", - "/ja/enterprise/2.14/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/ja/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups", - "/ja/enterprise/2.14/admin/guides/user-management": "/ja/enterprise/2.14/admin/user-management", - "/ja/enterprise/2.14/admin/guides/user-management/managing-dormant-users": "/ja/enterprise/2.14/admin/user-management/managing-dormant-users", - "/ja/enterprise/2.14/admin/guides/user-management/managing-global-webhooks": "/ja/enterprise/2.14/admin/user-management/managing-global-webhooks", - "/ja/enterprise/2.14/admin/guides/user-management/organizations-and-teams": "/ja/enterprise/2.14/admin/user-management/organizations-and-teams", - "/ja/enterprise/2.14/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/ja/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/ja/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/ja/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/ja/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/ja/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/ja/enterprise/2.14/admin/guides/user-management/preventing-users-from-creating-organizations": "/ja/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations", - "/ja/enterprise/2.14/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/ja/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/ja/enterprise/2.14/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/ja/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator", - "/ja/enterprise/2.14/admin/guides/user-management/rebuilding-contributions-data": "/ja/enterprise/2.14/admin/user-management/rebuilding-contributions-data", - "/ja/enterprise/2.14/admin/guides/user-management/removing-users-from-teams-and-organizations": "/ja/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations", - "/ja/enterprise/2.14/admin/guides/user-management/repositories": "/ja/enterprise/2.14/admin/user-management/repositories", - "/ja/enterprise/2.14/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/ja/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/ja/enterprise/2.14/admin/guides/user-management/suspending-and-unsuspending-users": "/ja/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users", - "/ja/enterprise/2.14/admin/guides/user-management/user-security": "/ja/enterprise/2.14/admin/user-management/user-security", - "/ja/enterprise/2.14/admin/guides/user-management/using-built-in-authentication": "/ja/enterprise/2.14/admin/user-management/using-built-in-authentication", - "/ja/enterprise/2.14/admin/guides/user-management/using-cas": "/ja/enterprise/2.14/admin/user-management/using-cas", - "/ja/enterprise/2.14/admin/guides/user-management/using-ldap": "/ja/enterprise/2.14/admin/user-management/using-ldap", - "/ja/enterprise/2.14/admin/guides/user-management/using-saml": "/ja/enterprise/2.14/admin/user-management/using-saml", - "/ja/enterprise/2.14/articles/3d-file-viewer": "/ja/enterprise/2.14/user/articles/3d-file-viewer", - "/ja/enterprise/2.14/articles/about-archiving-repositories": "/ja/enterprise/2.14/user/articles/about-archiving-repositories", - "/ja/enterprise/2.14/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/ja/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/ja/enterprise/2.14/articles/about-automation-for-project-boards": "/ja/enterprise/2.14/user/articles/about-automation-for-project-boards", - "/ja/enterprise/2.14/articles/about-branch-restrictions": "/ja/enterprise/2.14/user/articles/about-branch-restrictions", - "/ja/enterprise/2.14/articles/about-branches": "/ja/enterprise/2.14/user/articles/about-branches", - "/ja/enterprise/2.14/articles/about-code-owners": "/ja/enterprise/2.14/user/articles/about-code-owners", - "/ja/enterprise/2.14/articles/about-collaborative-development-models": "/ja/enterprise/2.14/user/articles/about-collaborative-development-models", - "/ja/enterprise/2.14/articles/about-commit-signature-verification": "/ja/enterprise/2.14/user/articles/about-commit-signature-verification", - "/ja/enterprise/2.14/articles/about-comparing-branches-in-pull-requests": "/ja/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests", - "/ja/enterprise/2.14/articles/about-conversations-on-github": "/ja/enterprise/2.14/user/articles/about-conversations-on-github", - "/ja/enterprise/2.14/articles/about-duplicate-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.14/articles/about-email-notifications": "/ja/enterprise/2.14/user/articles/about-email-notifications", - "/ja/enterprise/2.14/articles/about-forks": "/ja/enterprise/2.14/user/articles/about-forks", - "/ja/enterprise/2.14/articles/about-git-large-file-storage": "/ja/enterprise/2.14/user/articles/about-git-large-file-storage", - "/ja/enterprise/2.14/articles/about-git-rebase": "/ja/enterprise/2.14/user/articles/about-git-rebase", - "/ja/enterprise/2.14/articles/about-git-subtree-merges": "/ja/enterprise/2.14/user/articles/about-git-subtree-merges", - "/ja/enterprise/2.14/articles/about-github-pages-and-jekyll": "/ja/enterprise/2.14/user/articles/about-github-pages-and-jekyll", - "/ja/enterprise/2.14/articles/about-issue-and-pull-request-templates": "/ja/enterprise/2.14/user/articles/about-issue-and-pull-request-templates", - "/ja/enterprise/2.14/articles/about-issues": "/ja/enterprise/2.14/user/articles/about-issues", - "/ja/enterprise/2.14/articles/about-jekyll-themes-on-github": "/ja/enterprise/2.14/user/articles/about-jekyll-themes-on-github", - "/ja/enterprise/2.14/articles/about-labels": "/ja/enterprise/2.14/user/articles/about-labels", - "/ja/enterprise/2.14/articles/about-merge-conflicts": "/ja/enterprise/2.14/user/articles/about-merge-conflicts", - "/ja/enterprise/2.14/articles/about-merge-methods-on-github": "/ja/enterprise/2.14/user/articles/about-merge-methods-on-github", - "/ja/enterprise/2.14/articles/about-milestones": "/ja/enterprise/2.14/user/articles/about-milestones", - "/ja/enterprise/2.14/articles/about-notifications": "/ja/enterprise/2.14/user/articles/about-notifications", - "/ja/enterprise/2.14/articles/about-organization-membership": "/ja/enterprise/2.14/user/articles/about-organization-membership", - "/ja/enterprise/2.14/articles/about-organizations": "/ja/enterprise/2.14/user/articles/about-organizations", - "/ja/enterprise/2.14/articles/about-project-boards": "/ja/enterprise/2.14/user/articles/about-project-boards", - "/ja/enterprise/2.14/articles/about-protected-branches": "/ja/enterprise/2.14/user/articles/about-protected-branches", - "/ja/enterprise/2.14/articles/about-pull-request-merges": "/ja/enterprise/2.14/user/articles/about-pull-request-merges", - "/ja/enterprise/2.14/articles/about-pull-request-reviews": "/ja/enterprise/2.14/user/articles/about-pull-request-reviews", - "/ja/enterprise/2.14/articles/about-pull-requests": "/ja/enterprise/2.14/user/articles/about-pull-requests", - "/ja/enterprise/2.14/articles/about-readmes": "/ja/enterprise/2.14/user/articles/about-readmes", - "/ja/enterprise/2.14/articles/about-releases": "/ja/enterprise/2.14/user/articles/about-releases", - "/ja/enterprise/2.14/articles/about-remote-repositories": "/ja/enterprise/2.14/user/articles/about-remote-repositories", - "/ja/enterprise/2.14/articles/about-repositories": "/ja/enterprise/2.14/user/articles/about-repositories", - "/ja/enterprise/2.14/articles/about-repository-graphs": "/ja/enterprise/2.14/user/articles/about-repository-graphs", - "/ja/enterprise/2.14/articles/about-repository-languages": "/ja/enterprise/2.14/user/articles/about-repository-languages", - "/ja/enterprise/2.14/articles/about-required-commit-signing": "/ja/enterprise/2.14/user/articles/about-required-commit-signing", - "/ja/enterprise/2.14/articles/about-required-reviews-for-pull-requests": "/ja/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.14/articles/about-required-status-checks": "/ja/enterprise/2.14/user/articles/about-required-status-checks", - "/ja/enterprise/2.14/articles/about-saved-replies": "/ja/enterprise/2.14/user/articles/about-saved-replies", - "/ja/enterprise/2.14/articles/about-searching-on-github": "/ja/enterprise/2.14/user/articles/about-searching-on-github", - "/ja/enterprise/2.14/articles/about-ssh": "/ja/enterprise/2.14/user/articles/about-ssh", - "/ja/enterprise/2.14/articles/about-status-checks": "/ja/enterprise/2.14/user/articles/about-status-checks", - "/ja/enterprise/2.14/articles/about-task-lists": "/ja/enterprise/2.14/user/articles/about-task-lists", - "/ja/enterprise/2.14/articles/about-team-discussions": "/ja/enterprise/2.14/user/articles/about-team-discussions", - "/ja/enterprise/2.14/articles/about-teams": "/ja/enterprise/2.14/user/articles/about-teams", - "/ja/enterprise/2.14/articles/about-two-factor-authentication": "/ja/enterprise/2.14/user/articles/about-two-factor-authentication", - "/ja/enterprise/2.14/articles/about-web-notifications": "/ja/enterprise/2.14/user/articles/about-web-notifications", - "/ja/enterprise/2.14/articles/about-webhooks": "/ja/enterprise/2.14/user/articles/about-webhooks", - "/ja/enterprise/2.14/articles/about-wikis": "/ja/enterprise/2.14/user/articles/about-wikis", - "/ja/enterprise/2.14/articles/about-writing-and-formatting-on-github": "/ja/enterprise/2.14/user/articles/about-writing-and-formatting-on-github", - "/ja/enterprise/2.14/articles/about-your-organization-dashboard": "/ja/enterprise/2.14/user/articles/about-your-organization-dashboard", - "/ja/enterprise/2.14/articles/about-your-organizations-news-feed": "/ja/enterprise/2.14/user/articles/about-your-organizations-news-feed", - "/ja/enterprise/2.14/articles/about-your-organizations-profile": "/ja/enterprise/2.14/user/articles/about-your-organizations-profile", - "/ja/enterprise/2.14/articles/about-your-personal-dashboard": "/ja/enterprise/2.14/user/articles/about-your-personal-dashboard", - "/ja/enterprise/2.14/articles/about-your-profile": "/ja/enterprise/2.14/user/articles/about-your-profile", - "/ja/enterprise/2.14/articles/access-permissions-on-github": "/ja/enterprise/2.14/user/articles/access-permissions-on-github", - "/ja/enterprise/2.14/articles/accessing-an-organization": "/ja/enterprise/2.14/user/articles/accessing-an-organization", - "/ja/enterprise/2.14/articles/accessing-basic-repository-data": "/ja/enterprise/2.14/user/articles/accessing-basic-repository-data", - "/ja/enterprise/2.14/articles/accessing-github-using-two-factor-authentication": "/ja/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication", - "/ja/enterprise/2.14/articles/accessing-your-notifications": "/ja/enterprise/2.14/user/articles/accessing-your-notifications", - "/ja/enterprise/2.14/articles/accessing-your-organizations-settings": "/ja/enterprise/2.14/user/articles/accessing-your-organizations-settings", - "/ja/enterprise/2.14/articles/adding-a-file-to-a-repository-using-the-command-line": "/ja/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/ja/enterprise/2.14/articles/adding-a-file-to-a-repository": "/ja/enterprise/2.14/user/articles/adding-a-file-to-a-repository", - "/ja/enterprise/2.14/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/ja/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", - "/ja/enterprise/2.14/articles/adding-a-license-to-a-repository": "/ja/enterprise/2.14/user/articles/adding-a-license-to-a-repository", - "/ja/enterprise/2.14/articles/adding-a-new-gpg-key-to-your-github-account": "/ja/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/ja/enterprise/2.14/articles/adding-a-new-ssh-key-to-your-github-account": "/ja/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/ja/enterprise/2.14/articles/adding-a-remote": "/ja/enterprise/2.14/user/articles/adding-a-remote", - "/ja/enterprise/2.14/articles/adding-an-email-address-to-your-github-account": "/ja/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account", - "/ja/enterprise/2.14/articles/adding-an-existing-project-to-github-using-the-command-line": "/ja/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/ja/enterprise/2.14/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/ja/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/ja/enterprise/2.14/articles/adding-issues-and-pull-requests-to-a-project-board": "/ja/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/ja/enterprise/2.14/articles/adding-jekyll-plugins-to-a-github-pages-site": "/ja/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site", - "/ja/enterprise/2.14/articles/adding-notes-to-a-project-board": "/ja/enterprise/2.14/user/articles/adding-notes-to-a-project-board", - "/ja/enterprise/2.14/articles/adding-or-editing-wiki-pages": "/ja/enterprise/2.14/user/articles/adding-or-editing-wiki-pages", - "/ja/enterprise/2.14/articles/adding-organization-members-to-a-team": "/ja/enterprise/2.14/user/articles/adding-organization-members-to-a-team", - "/ja/enterprise/2.14/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/ja/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/ja/enterprise/2.14/articles/adding-people-to-your-organization": "/ja/enterprise/2.14/user/articles/adding-people-to-your-organization", - "/ja/enterprise/2.14/articles/adding-support-resources-to-your-project": "/ja/enterprise/2.14/user/articles/adding-support-resources-to-your-project", - "/ja/enterprise/2.14/articles/additional-customizations-for-github-pages": "/ja/enterprise/2.14/user/articles/additional-customizations-for-github-pages", - "/ja/enterprise/2.14/articles/addressing-merge-conflicts": "/ja/enterprise/2.14/user/articles/addressing-merge-conflicts", - "/ja/enterprise/2.14/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.14/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/ja/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/ja/enterprise/2.14/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/ja/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/ja/enterprise/2.14/articles/analyzing-changes-to-a-repositorys-content": "/ja/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content", - "/ja/enterprise/2.14/articles/applying-labels-to-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/approving-a-pull-request-with-required-reviews": "/ja/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews", - "/ja/enterprise/2.14/articles/archiving-a-github-repository": "/ja/enterprise/2.14/user/articles/archiving-a-github-repository", - "/ja/enterprise/2.14/articles/archiving-repositories": "/ja/enterprise/2.14/user/articles/archiving-repositories", - "/ja/enterprise/2.14/articles/assigning-issues-and-pull-requests-to-other-github-users": "/ja/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/ja/enterprise/2.14/articles/associating-an-email-with-your-gpg-key": "/ja/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key", - "/ja/enterprise/2.14/articles/associating-milestones-with-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/associating-text-editors-with-git": "/ja/enterprise/2.14/user/articles/associating-text-editors-with-git", - "/ja/enterprise/2.14/articles/authorizing-oauth-apps": "/ja/enterprise/2.14/user/articles/authorizing-oauth-apps", - "/ja/enterprise/2.14/articles/autolinked-references-and-urls": "/ja/enterprise/2.14/user/articles/autolinked-references-and-urls", - "/ja/enterprise/2.14/articles/backing-up-a-repository": "/ja/enterprise/2.14/user/articles/backing-up-a-repository", - "/ja/enterprise/2.14/articles/basic-writing-and-formatting-syntax": "/ja/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax", - "/ja/enterprise/2.14/articles/be-social": "/ja/enterprise/2.14/user/articles/be-social", - "/ja/enterprise/2.14/articles/caching-your-github-password-in-git": "/ja/enterprise/2.14/user/articles/caching-your-github-password-in-git", - "/ja/enterprise/2.14/articles/changing-a-commit-message": "/ja/enterprise/2.14/user/articles/changing-a-commit-message", - "/ja/enterprise/2.14/articles/changing-a-persons-role-to-owner": "/ja/enterprise/2.14/user/articles/changing-a-persons-role-to-owner", - "/ja/enterprise/2.14/articles/changing-a-remotes-url": "/ja/enterprise/2.14/user/articles/changing-a-remotes-url", - "/ja/enterprise/2.14/articles/changing-access-permissions-for-wikis": "/ja/enterprise/2.14/user/articles/changing-access-permissions-for-wikis", - "/ja/enterprise/2.14/articles/changing-author-info": "/ja/enterprise/2.14/user/articles/changing-author-info", - "/ja/enterprise/2.14/articles/changing-project-board-visibility": "/ja/enterprise/2.14/user/articles/changing-project-board-visibility", - "/ja/enterprise/2.14/articles/changing-team-visibility": "/ja/enterprise/2.14/user/articles/changing-team-visibility", - "/ja/enterprise/2.14/articles/changing-the-base-branch-of-a-pull-request": "/ja/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request", - "/ja/enterprise/2.14/articles/changing-your-github-username": "/ja/enterprise/2.14/user/articles/changing-your-github-username", - "/ja/enterprise/2.14/articles/changing-your-primary-email-address": "/ja/enterprise/2.14/user/articles/changing-your-primary-email-address", - "/ja/enterprise/2.14/articles/checking-for-existing-gpg-keys": "/ja/enterprise/2.14/user/articles/checking-for-existing-gpg-keys", - "/ja/enterprise/2.14/articles/checking-for-existing-ssh-keys": "/ja/enterprise/2.14/user/articles/checking-for-existing-ssh-keys", - "/ja/enterprise/2.14/articles/checking-out-pull-requests-locally": "/ja/enterprise/2.14/user/articles/checking-out-pull-requests-locally", - "/ja/enterprise/2.14/articles/checking-your-commit-and-tag-signature-verification-status": "/ja/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/ja/enterprise/2.14/articles/choosing-the-delivery-method-for-your-notifications": "/ja/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications", - "/ja/enterprise/2.14/articles/classifying-your-repository-with-topics": "/ja/enterprise/2.14/user/articles/classifying-your-repository-with-topics", - "/ja/enterprise/2.14/articles/cloning-a-repository-from-github": "/ja/enterprise/2.14/user/articles/cloning-a-repository-from-github", - "/ja/enterprise/2.14/articles/cloning-a-repository": "/ja/enterprise/2.14/user/articles/cloning-a-repository", - "/ja/enterprise/2.14/articles/closing-a-project-board": "/ja/enterprise/2.14/user/articles/closing-a-project-board", - "/ja/enterprise/2.14/articles/closing-a-pull-request": "/ja/enterprise/2.14/user/articles/closing-a-pull-request", - "/ja/enterprise/2.14/articles/closing-issues-using-keywords": "/ja/enterprise/2.14/user/articles/closing-issues-using-keywords", - "/ja/enterprise/2.14/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/ja/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", - "/ja/enterprise/2.14/articles/collaborating-with-groups-in-organizations": "/ja/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations", - "/ja/enterprise/2.14/articles/collaborating-with-your-team": "/ja/enterprise/2.14/user/articles/collaborating-with-your-team", - "/ja/enterprise/2.14/articles/collaboration-with-git-large-file-storage": "/ja/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage", - "/ja/enterprise/2.14/articles/commenting-on-a-pull-request": "/ja/enterprise/2.14/user/articles/commenting-on-a-pull-request", - "/ja/enterprise/2.14/articles/commit-branch-and-tag-labels": "/ja/enterprise/2.14/user/articles/commit-branch-and-tag-labels", - "/ja/enterprise/2.14/articles/commit-exists-on-github-but-not-in-my-local-clone": "/ja/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/ja/enterprise/2.14/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.14/articles/comparing-commits-across-time": "/ja/enterprise/2.14/user/articles/comparing-commits-across-time", - "/ja/enterprise/2.14/articles/conditions-for-large-files": "/ja/enterprise/2.14/user/articles/conditions-for-large-files", - "/ja/enterprise/2.14/articles/configuring-a-publishing-source-for-github-pages": "/ja/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages", - "/ja/enterprise/2.14/articles/configuring-a-remote-for-a-fork": "/ja/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork", - "/ja/enterprise/2.14/articles/configuring-automation-for-project-boards": "/ja/enterprise/2.14/user/articles/configuring-automation-for-project-boards", - "/ja/enterprise/2.14/articles/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.14/articles/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.14/articles/configuring-git-large-file-storage": "/ja/enterprise/2.14/user/articles/configuring-git-large-file-storage", - "/ja/enterprise/2.14/articles/configuring-git-to-handle-line-endings": "/ja/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings", - "/ja/enterprise/2.14/articles/configuring-jekyll-plugins": "/ja/enterprise/2.14/user/articles/configuring-jekyll-plugins", - "/ja/enterprise/2.14/articles/configuring-jekyll": "/ja/enterprise/2.14/user/articles/configuring-jekyll", - "/ja/enterprise/2.14/articles/configuring-protected-branches": "/ja/enterprise/2.14/user/articles/configuring-protected-branches", - "/ja/enterprise/2.14/articles/configuring-pull-request-merges": "/ja/enterprise/2.14/user/articles/configuring-pull-request-merges", - "/ja/enterprise/2.14/articles/configuring-two-factor-authentication-recovery-methods": "/ja/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods", - "/ja/enterprise/2.14/articles/configuring-two-factor-authentication": "/ja/enterprise/2.14/user/articles/configuring-two-factor-authentication", - "/ja/enterprise/2.14/articles/connecting-to-github-with-ssh": "/ja/enterprise/2.14/user/articles/connecting-to-github-with-ssh", - "/ja/enterprise/2.14/articles/connecting-with-third-party-applications": "/ja/enterprise/2.14/user/articles/connecting-with-third-party-applications", - "/ja/enterprise/2.14/articles/converting-a-user-into-an-organization": "/ja/enterprise/2.14/user/articles/converting-a-user-into-an-organization", - "/ja/enterprise/2.14/articles/converting-an-organization-into-a-user": "/ja/enterprise/2.14/user/articles/converting-an-organization-into-a-user", - "/ja/enterprise/2.14/articles/converting-an-organization-member-to-an-outside-collaborator": "/ja/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/ja/enterprise/2.14/articles/converting-an-outside-collaborator-to-an-organization-member": "/ja/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/ja/enterprise/2.14/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": "/ja/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions", - "/ja/enterprise/2.14/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": "/ja/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions", - "/ja/enterprise/2.14/articles/create-a-repo": "/ja/enterprise/2.14/user/articles/create-a-repo", - "/ja/enterprise/2.14/articles/creating-a-commit-with-multiple-authors": "/ja/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors", - "/ja/enterprise/2.14/articles/creating-a-custom-404-page-for-your-github-pages-site": "/ja/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/ja/enterprise/2.14/articles/creating-a-footer-or-sidebar-for-your-wiki": "/ja/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/ja/enterprise/2.14/articles/creating-a-label": "/ja/enterprise/2.14/user/articles/creating-a-label", - "/ja/enterprise/2.14/articles/creating-a-new-organization-from-scratch": "/ja/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch", - "/ja/enterprise/2.14/articles/creating-a-new-repository": "/ja/enterprise/2.14/user/articles/creating-a-new-repository", - "/ja/enterprise/2.14/articles/creating-a-permanent-link-to-a-code-snippet": "/ja/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/ja/enterprise/2.14/articles/creating-a-personal-access-token-for-the-command-line": "/ja/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line", - "/ja/enterprise/2.14/articles/creating-a-project-board": "/ja/enterprise/2.14/user/articles/creating-a-project-board", - "/ja/enterprise/2.14/articles/creating-a-pull-request-from-a-fork": "/ja/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork", - "/ja/enterprise/2.14/articles/creating-a-pull-request-template-for-your-repository": "/ja/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository", - "/ja/enterprise/2.14/articles/creating-a-pull-request": "/ja/enterprise/2.14/user/articles/creating-a-pull-request", - "/ja/enterprise/2.14/articles/creating-a-repository-on-github": "/ja/enterprise/2.14/user/articles/creating-a-repository-on-github", - "/ja/enterprise/2.14/articles/creating-a-saved-reply": "/ja/enterprise/2.14/user/articles/creating-a-saved-reply", - "/ja/enterprise/2.14/articles/creating-a-strong-password": "/ja/enterprise/2.14/user/articles/creating-a-strong-password", - "/ja/enterprise/2.14/articles/creating-a-team-discussion": "/ja/enterprise/2.14/user/articles/creating-a-team-discussion", - "/ja/enterprise/2.14/articles/creating-a-team": "/ja/enterprise/2.14/user/articles/creating-a-team", - "/ja/enterprise/2.14/articles/creating-an-issue": "/ja/enterprise/2.14/user/articles/creating-an-issue", - "/ja/enterprise/2.14/articles/creating-an-issues-only-repository": "/ja/enterprise/2.14/user/articles/creating-an-issues-only-repository", - "/ja/enterprise/2.14/articles/creating-and-deleting-branches-within-your-repository": "/ja/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository", - "/ja/enterprise/2.14/articles/creating-and-editing-commits": "/ja/enterprise/2.14/user/articles/creating-and-editing-commits", - "/ja/enterprise/2.14/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/creating-and-highlighting-code-blocks": "/ja/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks", - "/ja/enterprise/2.14/articles/creating-gists": "/ja/enterprise/2.14/user/articles/creating-gists", - "/ja/enterprise/2.14/articles/creating-issue-templates-for-your-repository": "/ja/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository", - "/ja/enterprise/2.14/articles/creating-new-files": "/ja/enterprise/2.14/user/articles/creating-new-files", - "/ja/enterprise/2.14/articles/creating-pages-with-the-automatic-generator": "/ja/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator", - "/ja/enterprise/2.14/articles/creating-project-pages-using-the-command-line": "/ja/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line", - "/ja/enterprise/2.14/articles/creating-releases": "/ja/enterprise/2.14/user/articles/creating-releases", - "/ja/enterprise/2.14/articles/customizing-css-and-html-in-your-jekyll-theme": "/ja/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme", - "/ja/enterprise/2.14/articles/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.14/articles/customizing-your-profile": "/ja/enterprise/2.14/user/articles/customizing-your-profile", - "/ja/enterprise/2.14/articles/dealing-with-non-fast-forward-errors": "/ja/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors", - "/ja/enterprise/2.14/articles/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.14/articles/deleting-a-label": "/ja/enterprise/2.14/user/articles/deleting-a-label", - "/ja/enterprise/2.14/articles/deleting-a-project-board": "/ja/enterprise/2.14/user/articles/deleting-a-project-board", - "/ja/enterprise/2.14/articles/deleting-a-repository": "/ja/enterprise/2.14/user/articles/deleting-a-repository", - "/ja/enterprise/2.14/articles/deleting-a-saved-reply": "/ja/enterprise/2.14/user/articles/deleting-a-saved-reply", - "/ja/enterprise/2.14/articles/deleting-a-team": "/ja/enterprise/2.14/user/articles/deleting-a-team", - "/ja/enterprise/2.14/articles/deleting-an-organization-account": "/ja/enterprise/2.14/user/articles/deleting-an-organization-account", - "/ja/enterprise/2.14/articles/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.14/articles/deleting-files": "/ja/enterprise/2.14/user/articles/deleting-files", - "/ja/enterprise/2.14/articles/deleting-your-user-account": "/ja/enterprise/2.14/user/articles/deleting-your-user-account", - "/ja/enterprise/2.14/articles/differences-between-commit-views": "/ja/enterprise/2.14/user/articles/differences-between-commit-views", - "/ja/enterprise/2.14/articles/disabling-issues": "/ja/enterprise/2.14/user/articles/disabling-issues", - "/ja/enterprise/2.14/articles/disabling-project-boards-in-a-repository": "/ja/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository", - "/ja/enterprise/2.14/articles/disabling-project-boards-in-your-organization": "/ja/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization", - "/ja/enterprise/2.14/articles/disabling-team-discussions-for-your-organization": "/ja/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization", - "/ja/enterprise/2.14/articles/disabling-two-factor-authentication-for-your-personal-account": "/ja/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/ja/enterprise/2.14/articles/disabling-wikis": "/ja/enterprise/2.14/user/articles/disabling-wikis", - "/ja/enterprise/2.14/articles/dismissing-a-pull-request-review": "/ja/enterprise/2.14/user/articles/dismissing-a-pull-request-review", - "/ja/enterprise/2.14/articles/distributing-large-binaries": "/ja/enterprise/2.14/user/articles/distributing-large-binaries", - "/ja/enterprise/2.14/articles/documenting-your-project-with-wikis": "/ja/enterprise/2.14/user/articles/documenting-your-project-with-wikis", - "/ja/enterprise/2.14/articles/duplicating-a-repository": "/ja/enterprise/2.14/user/articles/duplicating-a-repository", - "/ja/enterprise/2.14/articles/editing-a-label": "/ja/enterprise/2.14/user/articles/editing-a-label", - "/ja/enterprise/2.14/articles/editing-a-project-board": "/ja/enterprise/2.14/user/articles/editing-a-project-board", - "/ja/enterprise/2.14/articles/editing-a-saved-reply": "/ja/enterprise/2.14/user/articles/editing-a-saved-reply", - "/ja/enterprise/2.14/articles/editing-and-deleting-releases": "/ja/enterprise/2.14/user/articles/editing-and-deleting-releases", - "/ja/enterprise/2.14/articles/editing-and-sharing-content-with-gists": "/ja/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists", - "/ja/enterprise/2.14/articles/editing-files-in-another-users-repository": "/ja/enterprise/2.14/user/articles/editing-files-in-another-users-repository", - "/ja/enterprise/2.14/articles/editing-files-in-your-repository": "/ja/enterprise/2.14/user/articles/editing-files-in-your-repository", - "/ja/enterprise/2.14/articles/editing-or-deleting-a-team-discussion": "/ja/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion", - "/ja/enterprise/2.14/articles/editing-wiki-content": "/ja/enterprise/2.14/user/articles/editing-wiki-content", - "/ja/enterprise/2.14/articles/emoji-on-github-pages": "/ja/enterprise/2.14/user/articles/emoji-on-github-pages", - "/ja/enterprise/2.14/articles/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.14/articles/enabling-branch-restrictions": "/ja/enterprise/2.14/user/articles/enabling-branch-restrictions", - "/ja/enterprise/2.14/articles/enabling-required-commit-signing": "/ja/enterprise/2.14/user/articles/enabling-required-commit-signing", - "/ja/enterprise/2.14/articles/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.14/articles/enabling-required-status-checks": "/ja/enterprise/2.14/user/articles/enabling-required-status-checks", - "/ja/enterprise/2.14/articles/error-agent-admitted-failure-to-sign": "/ja/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign", - "/ja/enterprise/2.14/articles/error-bad-file-number": "/ja/enterprise/2.14/user/articles/error-bad-file-number", - "/ja/enterprise/2.14/articles/error-key-already-in-use": "/ja/enterprise/2.14/user/articles/error-key-already-in-use", - "/ja/enterprise/2.14/articles/error-permission-denied-publickey": "/ja/enterprise/2.14/user/articles/error-permission-denied-publickey", - "/ja/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-other-user": "/ja/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/ja/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-userother-repo": "/ja/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/ja/enterprise/2.14/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/ja/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/ja/enterprise/2.14/articles/error-repository-not-found": "/ja/enterprise/2.14/user/articles/error-repository-not-found", - "/ja/enterprise/2.14/articles/error-ssh-add-illegal-option----k": "/ja/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k", - "/ja/enterprise/2.14/articles/error-were-doing-an-ssh-key-audit": "/ja/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit", - "/ja/enterprise/2.14/articles/exploring-projects-on-github": "/ja/enterprise/2.14/user/articles/exploring-projects-on-github", - "/ja/enterprise/2.14/articles/file-attachments-on-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/files-that-start-with-an-underscore-are-missing": "/ja/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing", - "/ja/enterprise/2.14/articles/filtering-cards-on-a-project-board": "/ja/enterprise/2.14/user/articles/filtering-cards-on-a-project-board", - "/ja/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-assignees": "/ja/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/ja/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-labels": "/ja/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels", - "/ja/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-milestone": "/ja/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/ja/enterprise/2.14/articles/filtering-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/filtering-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/filtering-pull-requests-by-review-status": "/ja/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status", - "/ja/enterprise/2.14/articles/finding-changed-methods-and-functions-in-a-pull-request": "/ja/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/ja/enterprise/2.14/articles/finding-files-on-github": "/ja/enterprise/2.14/user/articles/finding-files-on-github", - "/ja/enterprise/2.14/articles/finding-information-in-a-repository": "/ja/enterprise/2.14/user/articles/finding-information-in-a-repository", - "/ja/enterprise/2.14/articles/following-people": "/ja/enterprise/2.14/user/articles/following-people", - "/ja/enterprise/2.14/articles/fork-a-repo": "/ja/enterprise/2.14/user/articles/fork-a-repo", - "/ja/enterprise/2.14/articles/forking-and-cloning-gists": "/ja/enterprise/2.14/user/articles/forking-and-cloning-gists", - "/ja/enterprise/2.14/articles/further-reading-on-github-pages": "/ja/enterprise/2.14/user/articles/further-reading-on-github-pages", - "/ja/enterprise/2.14/articles/generating-a-new-gpg-key": "/ja/enterprise/2.14/user/articles/generating-a-new-gpg-key", - "/ja/enterprise/2.14/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/ja/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/ja/enterprise/2.14/articles/generic-jekyll-build-failures": "/ja/enterprise/2.14/user/articles/generic-jekyll-build-failures", - "/ja/enterprise/2.14/articles/getting-changes-from-a-remote-repository": "/ja/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository", - "/ja/enterprise/2.14/articles/getting-permanent-links-to-files": "/ja/enterprise/2.14/user/articles/getting-permanent-links-to-files", - "/ja/enterprise/2.14/articles/getting-started-with-git-and-github": "/ja/enterprise/2.14/user/articles/getting-started-with-git-and-github", - "/ja/enterprise/2.14/articles/getting-started-with-notifications": "/ja/enterprise/2.14/user/articles/getting-started-with-notifications", - "/ja/enterprise/2.14/articles/getting-started-with-searching-on-github": "/ja/enterprise/2.14/user/articles/getting-started-with-searching-on-github", - "/ja/enterprise/2.14/articles/getting-started-with-the-api": "/ja/enterprise/2.14/user/articles/getting-started-with-the-api", - "/ja/enterprise/2.14/articles/getting-started-with-writing-and-formatting-on-github": "/ja/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github", - "/ja/enterprise/2.14/articles/getting-the-download-count-for-your-releases": "/ja/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases", - "/ja/enterprise/2.14/articles/git-and-github-learning-resources": "/ja/enterprise/2.14/user/articles/git-and-github-learning-resources", - "/ja/enterprise/2.14/articles/git-automation-with-oauth-tokens": "/ja/enterprise/2.14/user/articles/git-automation-with-oauth-tokens", - "/ja/enterprise/2.14/articles/git-cheatsheet": "/ja/enterprise/2.14/user/articles/git-cheatsheet", - "/ja/enterprise/2.14/articles/git-workflows": "/ja/enterprise/2.14/user/articles/git-workflows", - "/ja/enterprise/2.14/articles/github-flow": "/ja/enterprise/2.14/user/articles/github-flow", - "/ja/enterprise/2.14/articles/github-glossary": "/ja/enterprise/2.14/user/articles/github-glossary", - "/ja/enterprise/2.14/articles/giving-team-maintainer-permissions-to-an-organization-member": "/ja/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/ja/enterprise/2.14/articles/https-cloning-errors": "/ja/enterprise/2.14/user/articles/https-cloning-errors", - "/ja/enterprise/2.14/articles/ignoring-files": "/ja/enterprise/2.14/user/articles/ignoring-files", - "/ja/enterprise/2.14/articles/importing-a-git-repository-using-the-command-line": "/ja/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line", - "/ja/enterprise/2.14/articles/importing-source-code-to-github": "/ja/enterprise/2.14/user/articles/importing-source-code-to-github", - "/ja/enterprise/2.14/articles/incorporating-changes-from-a-pull-request": "/ja/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request", - "/ja/enterprise/2.14/articles/initializing-an-empty-repository-with-a-readme": "/ja/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme", - "/ja/enterprise/2.14/articles/installing-git-large-file-storage": "/ja/enterprise/2.14/user/articles/installing-git-large-file-storage", - "/ja/enterprise/2.14/articles/integrating-jira-with-your-organization-project-board": "/ja/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board", - "/ja/enterprise/2.14/articles/integrating-jira-with-your-personal-projects": "/ja/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects", - "/ja/enterprise/2.14/articles/inviting-collaborators-to-a-personal-repository": "/ja/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository", - "/ja/enterprise/2.14/articles/keeping-your-account-and-data-secure": "/ja/enterprise/2.14/user/articles/keeping-your-account-and-data-secure", - "/ja/enterprise/2.14/articles/keeping-your-organization-secure": "/ja/enterprise/2.14/user/articles/keeping-your-organization-secure", - "/ja/enterprise/2.14/articles/keyboard-shortcuts": "/ja/enterprise/2.14/user/articles/keyboard-shortcuts", - "/ja/enterprise/2.14/articles/labeling-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/labeling-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/learning-about-git": "/ja/enterprise/2.14/user/articles/learning-about-git", - "/ja/enterprise/2.14/articles/learning-about-github": "/ja/enterprise/2.14/user/articles/learning-about-github", - "/ja/enterprise/2.14/articles/licensing-a-repository": "/ja/enterprise/2.14/user/articles/licensing-a-repository", - "/ja/enterprise/2.14/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/ja/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/ja/enterprise/2.14/articles/linking-to-releases": "/ja/enterprise/2.14/user/articles/linking-to-releases", - "/ja/enterprise/2.14/articles/listing-the-forks-of-a-repository": "/ja/enterprise/2.14/user/articles/listing-the-forks-of-a-repository", - "/ja/enterprise/2.14/articles/listing-the-repositories-youre-watching": "/ja/enterprise/2.14/user/articles/listing-the-repositories-youre-watching", - "/ja/enterprise/2.14/articles/locking-conversations": "/ja/enterprise/2.14/user/articles/locking-conversations", - "/ja/enterprise/2.14/articles/managing-access-to-a-project-board-for-organization-members": "/ja/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members", - "/ja/enterprise/2.14/articles/managing-access-to-your-organizations-project-boards": "/ja/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards", - "/ja/enterprise/2.14/articles/managing-access-to-your-organizations-repositories": "/ja/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories", - "/ja/enterprise/2.14/articles/managing-access-to-your-personal-repositories": "/ja/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories", - "/ja/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-project-board": "/ja/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/ja/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-repository": "/ja/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/ja/enterprise/2.14/articles/managing-branches-in-your-repository": "/ja/enterprise/2.14/user/articles/managing-branches-in-your-repository", - "/ja/enterprise/2.14/articles/managing-commit-signature-verification": "/ja/enterprise/2.14/user/articles/managing-commit-signature-verification", - "/ja/enterprise/2.14/articles/managing-contribution-graphs-on-your-profile": "/ja/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile", - "/ja/enterprise/2.14/articles/managing-disruptive-comments": "/ja/enterprise/2.14/user/articles/managing-disruptive-comments", - "/ja/enterprise/2.14/articles/managing-email-preferences": "/ja/enterprise/2.14/user/articles/managing-email-preferences", - "/ja/enterprise/2.14/articles/managing-files-on-github": "/ja/enterprise/2.14/user/articles/managing-files-on-github", - "/ja/enterprise/2.14/articles/managing-files-using-the-command-line": "/ja/enterprise/2.14/user/articles/managing-files-using-the-command-line", - "/ja/enterprise/2.14/articles/managing-membership-in-your-organization": "/ja/enterprise/2.14/user/articles/managing-membership-in-your-organization", - "/ja/enterprise/2.14/articles/managing-organization-settings": "/ja/enterprise/2.14/user/articles/managing-organization-settings", - "/ja/enterprise/2.14/articles/managing-peoples-access-to-your-organization-with-roles": "/ja/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/ja/enterprise/2.14/articles/managing-project-boards": "/ja/enterprise/2.14/user/articles/managing-project-boards", - "/ja/enterprise/2.14/articles/managing-releases-in-a-repository": "/ja/enterprise/2.14/user/articles/managing-releases-in-a-repository", - "/ja/enterprise/2.14/articles/managing-remote-repositories": "/ja/enterprise/2.14/user/articles/managing-remote-repositories", - "/ja/enterprise/2.14/articles/managing-repository-settings": "/ja/enterprise/2.14/user/articles/managing-repository-settings", - "/ja/enterprise/2.14/articles/managing-team-access-to-an-organization-project-board": "/ja/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board", - "/ja/enterprise/2.14/articles/managing-team-access-to-an-organization-repository": "/ja/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository", - "/ja/enterprise/2.14/articles/managing-user-account-settings": "/ja/enterprise/2.14/user/articles/managing-user-account-settings", - "/ja/enterprise/2.14/articles/managing-your-membership-in-organizations": "/ja/enterprise/2.14/user/articles/managing-your-membership-in-organizations", - "/ja/enterprise/2.14/articles/managing-your-notifications": "/ja/enterprise/2.14/user/articles/managing-your-notifications", - "/ja/enterprise/2.14/articles/managing-your-work-with-issues": "/ja/enterprise/2.14/user/articles/managing-your-work-with-issues", - "/ja/enterprise/2.14/articles/manually-creating-a-single-issue-template-for-your-repository": "/ja/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/ja/enterprise/2.14/articles/mapping-geojson-files-on-github": "/ja/enterprise/2.14/user/articles/mapping-geojson-files-on-github", - "/ja/enterprise/2.14/articles/marking-notifications-as-read": "/ja/enterprise/2.14/user/articles/marking-notifications-as-read", - "/ja/enterprise/2.14/articles/mentions-on-github-pages": "/ja/enterprise/2.14/user/articles/mentions-on-github-pages", - "/ja/enterprise/2.14/articles/merging-a-pull-request": "/ja/enterprise/2.14/user/articles/merging-a-pull-request", - "/ja/enterprise/2.14/articles/merging-an-upstream-repository-into-your-fork": "/ja/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork", - "/ja/enterprise/2.14/articles/migrating-your-organization-to-improved-organization-permissions": "/ja/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions", - "/ja/enterprise/2.14/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": "/ja/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions", - "/ja/enterprise/2.14/articles/mime-types-on-github-pages": "/ja/enterprise/2.14/user/articles/mime-types-on-github-pages", - "/ja/enterprise/2.14/articles/moderating-comments-and-conversations": "/ja/enterprise/2.14/user/articles/moderating-comments-and-conversations", - "/ja/enterprise/2.14/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/ja/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/ja/enterprise/2.14/articles/moving-a-file-to-a-new-location-using-the-command-line": "/ja/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/ja/enterprise/2.14/articles/moving-a-file-to-a-new-location": "/ja/enterprise/2.14/user/articles/moving-a-file-to-a-new-location", - "/ja/enterprise/2.14/articles/moving-a-team-in-your-organizations-hierarchy": "/ja/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/ja/enterprise/2.14/articles/opening-an-issue-from-code": "/ja/enterprise/2.14/user/articles/opening-an-issue-from-code", - "/ja/enterprise/2.14/articles/organizing-information-with-tables": "/ja/enterprise/2.14/user/articles/organizing-information-with-tables", - "/ja/enterprise/2.14/articles/organizing-members-into-teams": "/ja/enterprise/2.14/user/articles/organizing-members-into-teams", - "/ja/enterprise/2.14/articles/page-build-failed-config-file-error": "/ja/enterprise/2.14/user/articles/page-build-failed-config-file-error", - "/ja/enterprise/2.14/articles/page-build-failed-date-is-not-a-valid-datetime": "/ja/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime", - "/ja/enterprise/2.14/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/ja/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", - "/ja/enterprise/2.14/articles/page-build-failed-file-is-a-symlink": "/ja/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink", - "/ja/enterprise/2.14/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/ja/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", - "/ja/enterprise/2.14/articles/page-build-failed-invalid-highlighter-language": "/ja/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language", - "/ja/enterprise/2.14/articles/page-build-failed-invalid-post-date": "/ja/enterprise/2.14/user/articles/page-build-failed-invalid-post-date", - "/ja/enterprise/2.14/articles/page-build-failed-invalid-sass-or-scss": "/ja/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss", - "/ja/enterprise/2.14/articles/page-build-failed-invalid-submodule": "/ja/enterprise/2.14/user/articles/page-build-failed-invalid-submodule", - "/ja/enterprise/2.14/articles/page-build-failed-invalid-yaml-in-data-file": "/ja/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file", - "/ja/enterprise/2.14/articles/page-build-failed-markdown-errors": "/ja/enterprise/2.14/user/articles/page-build-failed-markdown-errors", - "/ja/enterprise/2.14/articles/page-build-failed-missing-docs-folder": "/ja/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder", - "/ja/enterprise/2.14/articles/page-build-failed-missing-submodule": "/ja/enterprise/2.14/user/articles/page-build-failed-missing-submodule", - "/ja/enterprise/2.14/articles/page-build-failed-relative-permalinks-configured": "/ja/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured", - "/ja/enterprise/2.14/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/ja/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", - "/ja/enterprise/2.14/articles/page-build-failed-syntax-error-in-for-loop": "/ja/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop", - "/ja/enterprise/2.14/articles/page-build-failed-tag-not-properly-closed": "/ja/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed", - "/ja/enterprise/2.14/articles/page-build-failed-tag-not-properly-terminated": "/ja/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated", - "/ja/enterprise/2.14/articles/page-build-failed-unknown-tag-error": "/ja/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error", - "/ja/enterprise/2.14/articles/permission-levels-for-a-user-account-repository": "/ja/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository", - "/ja/enterprise/2.14/articles/permission-levels-for-an-organization": "/ja/enterprise/2.14/user/articles/permission-levels-for-an-organization", - "/ja/enterprise/2.14/articles/personalizing-your-profile": "/ja/enterprise/2.14/user/articles/personalizing-your-profile", - "/ja/enterprise/2.14/articles/pinning-a-team-discussion": "/ja/enterprise/2.14/user/articles/pinning-a-team-discussion", - "/ja/enterprise/2.14/articles/pinning-items-to-your-profile": "/ja/enterprise/2.14/user/articles/pinning-items-to-your-profile", - "/ja/enterprise/2.14/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/ja/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.14/articles/preventing-unauthorized-access": "/ja/enterprise/2.14/user/articles/preventing-unauthorized-access", - "/ja/enterprise/2.14/articles/project-board-permissions-for-an-organization": "/ja/enterprise/2.14/user/articles/project-board-permissions-for-an-organization", - "/ja/enterprise/2.14/articles/proposing-changes-to-your-work-with-pull-requests": "/ja/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/ja/enterprise/2.14/articles/publicizing-or-hiding-organization-membership": "/ja/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership", - "/ja/enterprise/2.14/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/ja/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/ja/enterprise/2.14/articles/pushing-commits-to-a-remote-repository": "/ja/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository", - "/ja/enterprise/2.14/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/ja/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/ja/enterprise/2.14/articles/recovering-your-ssh-key-passphrase": "/ja/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase", - "/ja/enterprise/2.14/articles/redirects-on-github-pages": "/ja/enterprise/2.14/user/articles/redirects-on-github-pages", - "/ja/enterprise/2.14/articles/reinstating-a-former-member-of-your-organization": "/ja/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization", - "/ja/enterprise/2.14/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/ja/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/ja/enterprise/2.14/articles/remembering-your-github-username-or-email": "/ja/enterprise/2.14/user/articles/remembering-your-github-username-or-email", - "/ja/enterprise/2.14/articles/removing-a-collaborator-from-a-personal-repository": "/ja/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository", - "/ja/enterprise/2.14/articles/removing-a-member-from-your-organization": "/ja/enterprise/2.14/user/articles/removing-a-member-from-your-organization", - "/ja/enterprise/2.14/articles/removing-a-remote": "/ja/enterprise/2.14/user/articles/removing-a-remote", - "/ja/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/ja/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/ja/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-repository": "/ja/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/ja/enterprise/2.14/articles/removing-files-from-a-repositorys-history": "/ja/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history", - "/ja/enterprise/2.14/articles/removing-files-from-git-large-file-storage": "/ja/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage", - "/ja/enterprise/2.14/articles/removing-organization-members-from-a-team": "/ja/enterprise/2.14/user/articles/removing-organization-members-from-a-team", - "/ja/enterprise/2.14/articles/removing-sensitive-data-from-a-repository": "/ja/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository", - "/ja/enterprise/2.14/articles/removing-yourself-from-a-collaborators-repository": "/ja/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository", - "/ja/enterprise/2.14/articles/removing-yourself-from-an-organization": "/ja/enterprise/2.14/user/articles/removing-yourself-from-an-organization", - "/ja/enterprise/2.14/articles/renaming-a-file-using-the-command-line": "/ja/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line", - "/ja/enterprise/2.14/articles/renaming-a-file": "/ja/enterprise/2.14/user/articles/renaming-a-file", - "/ja/enterprise/2.14/articles/renaming-a-remote": "/ja/enterprise/2.14/user/articles/renaming-a-remote", - "/ja/enterprise/2.14/articles/renaming-a-repository": "/ja/enterprise/2.14/user/articles/renaming-a-repository", - "/ja/enterprise/2.14/articles/renaming-a-team": "/ja/enterprise/2.14/user/articles/renaming-a-team", - "/ja/enterprise/2.14/articles/renaming-an-organization": "/ja/enterprise/2.14/user/articles/renaming-an-organization", - "/ja/enterprise/2.14/articles/rendering-and-diffing-images": "/ja/enterprise/2.14/user/articles/rendering-and-diffing-images", - "/ja/enterprise/2.14/articles/rendering-csv-and-tsv-data": "/ja/enterprise/2.14/user/articles/rendering-csv-and-tsv-data", - "/ja/enterprise/2.14/articles/rendering-differences-in-prose-documents": "/ja/enterprise/2.14/user/articles/rendering-differences-in-prose-documents", - "/ja/enterprise/2.14/articles/rendering-pdf-documents": "/ja/enterprise/2.14/user/articles/rendering-pdf-documents", - "/ja/enterprise/2.14/articles/reopening-a-closed-project-board": "/ja/enterprise/2.14/user/articles/reopening-a-closed-project-board", - "/ja/enterprise/2.14/articles/repository-metadata-on-github-pages": "/ja/enterprise/2.14/user/articles/repository-metadata-on-github-pages", - "/ja/enterprise/2.14/articles/repository-permission-levels-for-an-organization": "/ja/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization", - "/ja/enterprise/2.14/articles/requesting-a-pull-request-review": "/ja/enterprise/2.14/user/articles/requesting-a-pull-request-review", - "/ja/enterprise/2.14/articles/requesting-a-trial-of-github-enterprise": "/ja/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise", - "/ja/enterprise/2.14/articles/requesting-to-add-a-child-team": "/ja/enterprise/2.14/user/articles/requesting-to-add-a-child-team", - "/ja/enterprise/2.14/articles/requesting-to-add-or-change-a-parent-team": "/ja/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team", - "/ja/enterprise/2.14/articles/requiring-two-factor-authentication-in-your-organization": "/ja/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.14/articles/resolving-a-merge-conflict-on-github": "/ja/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github", - "/ja/enterprise/2.14/articles/resolving-a-merge-conflict-using-the-command-line": "/ja/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/ja/enterprise/2.14/articles/resolving-git-large-file-storage-upload-failures": "/ja/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures", - "/ja/enterprise/2.14/articles/resolving-merge-conflicts-after-a-git-rebase": "/ja/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/ja/enterprise/2.14/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.14/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.14/articles/reverting-a-pull-request": "/ja/enterprise/2.14/user/articles/reverting-a-pull-request", - "/ja/enterprise/2.14/articles/reviewing-changes-in-pull-requests": "/ja/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests", - "/ja/enterprise/2.14/articles/reviewing-proposed-changes-in-a-pull-request": "/ja/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/ja/enterprise/2.14/articles/reviewing-the-audit-log-for-your-organization": "/ja/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization", - "/ja/enterprise/2.14/articles/reviewing-your-authorized-applications-oauth": "/ja/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth", - "/ja/enterprise/2.14/articles/reviewing-your-authorized-integrations": "/ja/enterprise/2.14/user/articles/reviewing-your-authorized-integrations", - "/ja/enterprise/2.14/articles/reviewing-your-deploy-keys": "/ja/enterprise/2.14/user/articles/reviewing-your-deploy-keys", - "/ja/enterprise/2.14/articles/reviewing-your-organizations-installed-integrations": "/ja/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations", - "/ja/enterprise/2.14/articles/reviewing-your-security-log": "/ja/enterprise/2.14/user/articles/reviewing-your-security-log", - "/ja/enterprise/2.14/articles/reviewing-your-ssh-keys": "/ja/enterprise/2.14/user/articles/reviewing-your-ssh-keys", - "/ja/enterprise/2.14/articles/saving-repositories-with-stars": "/ja/enterprise/2.14/user/articles/saving-repositories-with-stars", - "/ja/enterprise/2.14/articles/searching-code": "/ja/enterprise/2.14/user/articles/searching-code", - "/ja/enterprise/2.14/articles/searching-commits": "/ja/enterprise/2.14/user/articles/searching-commits", - "/ja/enterprise/2.14/articles/searching-for-repositories": "/ja/enterprise/2.14/user/articles/searching-for-repositories", - "/ja/enterprise/2.14/articles/searching-in-forks": "/ja/enterprise/2.14/user/articles/searching-in-forks", - "/ja/enterprise/2.14/articles/searching-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/searching-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/searching-on-github": "/ja/enterprise/2.14/user/articles/searching-on-github", - "/ja/enterprise/2.14/articles/searching-topics": "/ja/enterprise/2.14/user/articles/searching-topics", - "/ja/enterprise/2.14/articles/searching-users": "/ja/enterprise/2.14/user/articles/searching-users", - "/ja/enterprise/2.14/articles/searching-wikis": "/ja/enterprise/2.14/user/articles/searching-wikis", - "/ja/enterprise/2.14/articles/securing-your-account-with-two-factor-authentication-2fa": "/ja/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/ja/enterprise/2.14/articles/set-up-git": "/ja/enterprise/2.14/user/articles/set-up-git", - "/ja/enterprise/2.14/articles/setting-a-backup-email-address": "/ja/enterprise/2.14/user/articles/setting-a-backup-email-address", - "/ja/enterprise/2.14/articles/setting-guidelines-for-repository-contributors": "/ja/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors", - "/ja/enterprise/2.14/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": "/ja/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization", - "/ja/enterprise/2.14/articles/setting-repository-visibility": "/ja/enterprise/2.14/user/articles/setting-repository-visibility", - "/ja/enterprise/2.14/articles/setting-the-default-branch": "/ja/enterprise/2.14/user/articles/setting-the-default-branch", - "/ja/enterprise/2.14/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/ja/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", - "/ja/enterprise/2.14/articles/setting-up-your-project-for-healthy-contributions": "/ja/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions", - "/ja/enterprise/2.14/articles/setting-your-commit-email-address": "/ja/enterprise/2.14/user/articles/setting-your-commit-email-address", - "/ja/enterprise/2.14/articles/setting-your-teams-profile-picture": "/ja/enterprise/2.14/user/articles/setting-your-teams-profile-picture", - "/ja/enterprise/2.14/articles/setting-your-username-in-git": "/ja/enterprise/2.14/user/articles/setting-your-username-in-git", - "/ja/enterprise/2.14/articles/sharing-filters": "/ja/enterprise/2.14/user/articles/sharing-filters", - "/ja/enterprise/2.14/articles/signing-commits": "/ja/enterprise/2.14/user/articles/signing-commits", - "/ja/enterprise/2.14/articles/signing-tags": "/ja/enterprise/2.14/user/articles/signing-tags", - "/ja/enterprise/2.14/articles/signing-up-for-github": "/ja/enterprise/2.14/user/articles/signing-up-for-github", - "/ja/enterprise/2.14/articles/sitemaps-for-github-pages": "/ja/enterprise/2.14/user/articles/sitemaps-for-github-pages", - "/ja/enterprise/2.14/articles/sorting-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/sorting-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/sorting-search-results": "/ja/enterprise/2.14/user/articles/sorting-search-results", - "/ja/enterprise/2.14/articles/source-code-migration-tools": "/ja/enterprise/2.14/user/articles/source-code-migration-tools", - "/ja/enterprise/2.14/articles/splitting-a-subfolder-out-into-a-new-repository": "/ja/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/ja/enterprise/2.14/articles/subscribing-to-and-unsubscribing-from-notifications": "/ja/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/ja/enterprise/2.14/articles/subversion-properties-supported-by-github": "/ja/enterprise/2.14/user/articles/subversion-properties-supported-by-github", - "/ja/enterprise/2.14/articles/sudo-mode": "/ja/enterprise/2.14/user/articles/sudo-mode", - "/ja/enterprise/2.14/articles/support-for-subversion-clients": "/ja/enterprise/2.14/user/articles/support-for-subversion-clients", - "/ja/enterprise/2.14/articles/supported-browsers": "/ja/enterprise/2.14/user/articles/supported-browsers", - "/ja/enterprise/2.14/articles/syncing-a-fork": "/ja/enterprise/2.14/user/articles/syncing-a-fork", - "/ja/enterprise/2.14/articles/telling-git-about-your-signing-key": "/ja/enterprise/2.14/user/articles/telling-git-about-your-signing-key", - "/ja/enterprise/2.14/articles/testing-your-ssh-connection": "/ja/enterprise/2.14/user/articles/testing-your-ssh-connection", - "/ja/enterprise/2.14/articles/tracking-changes-in-a-comment": "/ja/enterprise/2.14/user/articles/tracking-changes-in-a-comment", - "/ja/enterprise/2.14/articles/tracking-changes-in-a-file": "/ja/enterprise/2.14/user/articles/tracking-changes-in-a-file", - "/ja/enterprise/2.14/articles/tracking-progress-on-your-project-board": "/ja/enterprise/2.14/user/articles/tracking-progress-on-your-project-board", - "/ja/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-milestones": "/ja/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/ja/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-project-boards": "/ja/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/ja/enterprise/2.14/articles/transferring-a-repository": "/ja/enterprise/2.14/user/articles/transferring-a-repository", - "/ja/enterprise/2.14/articles/transferring-organization-ownership": "/ja/enterprise/2.14/user/articles/transferring-organization-ownership", - "/ja/enterprise/2.14/articles/troubleshooting-commit-signature-verification": "/ja/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification", - "/ja/enterprise/2.14/articles/troubleshooting-commits-on-your-timeline": "/ja/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline", - "/ja/enterprise/2.14/articles/troubleshooting-commits": "/ja/enterprise/2.14/user/articles/troubleshooting-commits", - "/ja/enterprise/2.14/articles/troubleshooting-github-pages-builds": "/ja/enterprise/2.14/user/articles/troubleshooting-github-pages-builds", - "/ja/enterprise/2.14/articles/troubleshooting-search-queries": "/ja/enterprise/2.14/user/articles/troubleshooting-search-queries", - "/ja/enterprise/2.14/articles/troubleshooting-ssh": "/ja/enterprise/2.14/user/articles/troubleshooting-ssh", - "/ja/enterprise/2.14/articles/types-of-github-accounts": "/ja/enterprise/2.14/user/articles/types-of-github-accounts", - "/ja/enterprise/2.14/articles/types-of-required-status-checks": "/ja/enterprise/2.14/user/articles/types-of-required-status-checks", - "/ja/enterprise/2.14/articles/understanding-connections-between-repositories": "/ja/enterprise/2.14/user/articles/understanding-connections-between-repositories", - "/ja/enterprise/2.14/articles/understanding-the-search-syntax": "/ja/enterprise/2.14/user/articles/understanding-the-search-syntax", - "/ja/enterprise/2.14/articles/unpublishing-a-project-pages-site": "/ja/enterprise/2.14/user/articles/unpublishing-a-project-pages-site", - "/ja/enterprise/2.14/articles/unpublishing-a-user-pages-site": "/ja/enterprise/2.14/user/articles/unpublishing-a-user-pages-site", - "/ja/enterprise/2.14/articles/updating-an-expired-gpg-key": "/ja/enterprise/2.14/user/articles/updating-an-expired-gpg-key", - "/ja/enterprise/2.14/articles/updating-credentials-from-the-osx-keychain": "/ja/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain", - "/ja/enterprise/2.14/articles/updating-your-github-access-credentials": "/ja/enterprise/2.14/user/articles/updating-your-github-access-credentials", - "/ja/enterprise/2.14/articles/updating-your-markdown-processor-to-kramdown": "/ja/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown", - "/ja/enterprise/2.14/articles/user-organization-and-project-pages": "/ja/enterprise/2.14/user/articles/user-organization-and-project-pages", - "/ja/enterprise/2.14/articles/using-a-static-site-generator-other-than-jekyll": "/ja/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll", - "/ja/enterprise/2.14/articles/using-a-verified-email-address-in-your-gpg-key": "/ja/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/ja/enterprise/2.14/articles/using-advanced-git-commands": "/ja/enterprise/2.14/user/articles/using-advanced-git-commands", - "/ja/enterprise/2.14/articles/using-common-git-commands": "/ja/enterprise/2.14/user/articles/using-common-git-commands", - "/ja/enterprise/2.14/articles/using-git-rebase-on-the-command-line": "/ja/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line", - "/ja/enterprise/2.14/articles/using-github": "/ja/enterprise/2.14/user/articles/using-github", - "/ja/enterprise/2.14/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/ja/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", - "/ja/enterprise/2.14/articles/using-saved-replies": "/ja/enterprise/2.14/user/articles/using-saved-replies", - "/ja/enterprise/2.14/articles/using-search-to-filter-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/using-syntax-highlighting-on-github-pages": "/ja/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages", - "/ja/enterprise/2.14/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/ja/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", - "/ja/enterprise/2.14/articles/versioning-large-files": "/ja/enterprise/2.14/user/articles/versioning-large-files", - "/ja/enterprise/2.14/articles/viewing-a-projects-contributors": "/ja/enterprise/2.14/user/articles/viewing-a-projects-contributors", - "/ja/enterprise/2.14/articles/viewing-a-pull-request-review": "/ja/enterprise/2.14/user/articles/viewing-a-pull-request-review", - "/ja/enterprise/2.14/articles/viewing-a-repositorys-network": "/ja/enterprise/2.14/user/articles/viewing-a-repositorys-network", - "/ja/enterprise/2.14/articles/viewing-a-summary-of-repository-activity": "/ja/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity", - "/ja/enterprise/2.14/articles/viewing-a-wikis-history-of-changes": "/ja/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes", - "/ja/enterprise/2.14/articles/viewing-all-of-your-issues-and-pull-requests": "/ja/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/ja/enterprise/2.14/articles/viewing-and-comparing-commits": "/ja/enterprise/2.14/user/articles/viewing-and-comparing-commits", - "/ja/enterprise/2.14/articles/viewing-branches-in-your-repository": "/ja/enterprise/2.14/user/articles/viewing-branches-in-your-repository", - "/ja/enterprise/2.14/articles/viewing-contributions-on-your-profile": "/ja/enterprise/2.14/user/articles/viewing-contributions-on-your-profile", - "/ja/enterprise/2.14/articles/viewing-jekyll-build-error-messages": "/ja/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages", - "/ja/enterprise/2.14/articles/viewing-peoples-roles-in-an-organization": "/ja/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization", - "/ja/enterprise/2.14/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/ja/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/ja/enterprise/2.14/articles/viewing-your-milestones-progress": "/ja/enterprise/2.14/user/articles/viewing-your-milestones-progress", - "/ja/enterprise/2.14/articles/viewing-your-repositorys-tags": "/ja/enterprise/2.14/user/articles/viewing-your-repositorys-tags", - "/ja/enterprise/2.14/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/ja/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/ja/enterprise/2.14/articles/visualizing-commits-in-a-repository": "/ja/enterprise/2.14/user/articles/visualizing-commits-in-a-repository", - "/ja/enterprise/2.14/articles/watching-and-unwatching-repositories": "/ja/enterprise/2.14/user/articles/watching-and-unwatching-repositories", - "/ja/enterprise/2.14/articles/watching-and-unwatching-team-discussions": "/ja/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions", - "/ja/enterprise/2.14/articles/what-are-the-differences-between-subversion-and-git": "/ja/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git", - "/ja/enterprise/2.14/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/ja/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/ja/enterprise/2.14/articles/what-is-github-pages": "/ja/enterprise/2.14/user/articles/what-is-github-pages", - "/ja/enterprise/2.14/articles/which-remote-url-should-i-use": "/ja/enterprise/2.14/user/articles/which-remote-url-should-i-use", - "/ja/enterprise/2.14/articles/why-are-my-commits-in-the-wrong-order": "/ja/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order", - "/ja/enterprise/2.14/articles/why-are-my-commits-linked-to-the-wrong-user": "/ja/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/ja/enterprise/2.14/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/ja/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/ja/enterprise/2.14/articles/why-is-git-always-asking-for-my-password": "/ja/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password", - "/ja/enterprise/2.14/articles/working-with-advanced-formatting": "/ja/enterprise/2.14/user/articles/working-with-advanced-formatting", - "/ja/enterprise/2.14/articles/working-with-forks": "/ja/enterprise/2.14/user/articles/working-with-forks", - "/ja/enterprise/2.14/articles/working-with-jupyter-notebook-files-on-github": "/ja/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github", - "/ja/enterprise/2.14/articles/working-with-large-files": "/ja/enterprise/2.14/user/articles/working-with-large-files", - "/ja/enterprise/2.14/articles/working-with-non-code-files": "/ja/enterprise/2.14/user/articles/working-with-non-code-files", - "/ja/enterprise/2.14/articles/working-with-pre-receive-hooks": "/ja/enterprise/2.14/user/articles/working-with-pre-receive-hooks", - "/ja/enterprise/2.14/articles/working-with-saved-replies": "/ja/enterprise/2.14/user/articles/working-with-saved-replies", - "/ja/enterprise/2.14/articles/working-with-ssh-key-passphrases": "/ja/enterprise/2.14/user/articles/working-with-ssh-key-passphrases", - "/ja/enterprise/2.14/articles/working-with-subversion-on-github": "/ja/enterprise/2.14/user/articles/working-with-subversion-on-github", - "/ja/enterprise/2.14/user/categories/admin/guidesistering-a-repository": "/ja/enterprise/2.14/user/categories/administering-a-repository", - "/ja/enterprise/2.14/categories/administering-a-repository": "/ja/enterprise/2.14/user/categories/administering-a-repository", - "/ja/enterprise/2.14/categories/authenticating-to-github": "/ja/enterprise/2.14/user/categories/authenticating-to-github", - "/ja/enterprise/2.14/categories/building-a-strong-community": "/ja/enterprise/2.14/user/categories/building-a-strong-community", - "/ja/enterprise/2.14/categories/collaborating-with-issues-and-pull-requests": "/ja/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests", - "/ja/enterprise/2.14/categories/committing-changes-to-your-project": "/ja/enterprise/2.14/user/categories/committing-changes-to-your-project", - "/ja/enterprise/2.14/categories/creating-cloning-and-archiving-repositories": "/ja/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories", - "/ja/enterprise/2.14/categories/customizing-github-pages": "/ja/enterprise/2.14/user/categories/customizing-github-pages", - "/ja/enterprise/2.14/categories/extending-github": "/ja/enterprise/2.14/user/categories/extending-github", - "/ja/enterprise/2.14/categories/getting-started-with-github": "/ja/enterprise/2.14/user/categories/getting-started-with-github", - "/ja/enterprise/2.14/categories/github-pages-basics": "/ja/enterprise/2.14/user/categories/github-pages-basics", - "/ja/enterprise/2.14/categories/importing-your-projects-to-github": "/ja/enterprise/2.14/user/categories/importing-your-projects-to-github", - "/ja/enterprise/2.14/categories/managing-files-in-a-repository": "/ja/enterprise/2.14/user/categories/managing-files-in-a-repository", - "/ja/enterprise/2.14/categories/managing-large-files": "/ja/enterprise/2.14/user/categories/managing-large-files", - "/ja/enterprise/2.14/categories/managing-your-work-on-github": "/ja/enterprise/2.14/user/categories/managing-your-work-on-github", - "/ja/enterprise/2.14/categories/receiving-notifications-about-activity-on-github": "/ja/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github", - "/ja/enterprise/2.14/categories/searching-for-information-on-github": "/ja/enterprise/2.14/user/categories/searching-for-information-on-github", - "/ja/enterprise/2.14/categories/setting-up-and-managing-organizations-and-teams": "/ja/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams", - "/ja/enterprise/2.14/categories/setting-up-and-managing-your-github-profile": "/ja/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile", - "/ja/enterprise/2.14/categories/setting-up-and-managing-your-github-user-account": "/ja/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account", - "/ja/enterprise/2.14/categories/using-git": "/ja/enterprise/2.14/user/categories/using-git", - "/ja/enterprise/2.14/categories/visualizing-repository-data-with-graphs": "/ja/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs", - "/ja/enterprise/2.14/categories/writing-on-github": "/ja/enterprise/2.14/user/categories/writing-on-github", - "/cn/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/cn/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/cn/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/cn/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/cn/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/cn/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/cn/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/cn/enterprise/2.15/admin/articles/using-github-task-runner", - "/cn/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/cn/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/cn/enterprise/2.15/admin/guides/clustering/clustering-overview": "/cn/enterprise/2.15/admin/clustering/clustering-overview", - "/cn/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/cn/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/cn/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/cn/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/cn/enterprise/2.15/admin/guides/clustering": "/cn/enterprise/2.15/admin/clustering", - "/cn/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/cn/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/cn/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/cn/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/cn/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/cn/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/cn/enterprise/2.15/admin/guides/clustering/network-configuration": "/cn/enterprise/2.15/admin/clustering/network-configuration", - "/cn/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/cn/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/cn/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/cn/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/cn/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/cn/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/cn/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/cn/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/cn/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/cn/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/cn/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/cn/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/cn/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/cn/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/cn/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/cn/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/cn/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/cn/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/cn/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/cn/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/cn/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/cn/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/cn/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/cn/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/cn/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/cn/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/cn/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/cn/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/cn/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/cn/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/cn/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/cn/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/cn/enterprise/2.15/admin/guides/developer-workflow": "/cn/enterprise/2.15/admin/developer-workflow", - "/cn/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/cn/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/cn/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/cn/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/cn/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/cn/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/cn/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/cn/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/cn/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/cn/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/cn/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/cn/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/cn/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/cn/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/cn/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/cn/enterprise/2.15/admin/guides/enterprise-support": "/cn/enterprise/2.15/admin/enterprise-support", - "/cn/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/cn/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/cn/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/cn/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/cn/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/cn/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/cn/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/cn/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/cn/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/cn/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/cn/enterprise/2.15/admin/guides": "/cn/enterprise/2.15/admin", - "/cn/enterprise/2.15/admin/guides/installation/about-geo-replication": "/cn/enterprise/2.15/admin/installation/about-geo-replication", - "/cn/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/cn/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/cn/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/cn/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/cn/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/cn/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/cn/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/cn/enterprise/2.15/admin/installation/accessing-the-management-console", - "/cn/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/cn/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/cn/enterprise/2.15/admin/guides/installation/activity-dashboard": "/cn/enterprise/2.15/admin/installation/activity-dashboard", - "/cn/enterprise/2.15/admin/guides/installation/audit-logging": "/cn/enterprise/2.15/admin/installation/audit-logging", - "/cn/enterprise/2.15/admin/guides/installation/audited-actions": "/cn/enterprise/2.15/admin/installation/audited-actions", - "/cn/enterprise/2.15/admin/guides/installation/command-line-utilities": "/cn/enterprise/2.15/admin/installation/command-line-utilities", - "/cn/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/cn/enterprise/2.15/admin/installation/configuring-a-hostname", - "/cn/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/cn/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/cn/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/cn/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/cn/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/cn/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/cn/enterprise/2.15/admin/guides/installation/configuring-collectd": "/cn/enterprise/2.15/admin/installation/configuring-collectd", - "/cn/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/cn/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/cn/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/cn/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/cn/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/cn/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/cn/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/cn/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/cn/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/cn/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/cn/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/cn/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/cn/enterprise/2.15/admin/installation/configuring-rate-limits", - "/cn/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/cn/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/cn/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/cn/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/cn/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/cn/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/cn/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/cn/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/cn/enterprise/2.15/admin/guides/installation/configuring-tls": "/cn/enterprise/2.15/admin/installation/configuring-tls", - "/cn/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/cn/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/cn/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/cn/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/cn/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/cn/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/cn/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/cn/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/cn/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/cn/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/cn/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/cn/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/cn/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/cn/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/cn/enterprise/2.15/admin/installation/enabling-private-mode", - "/cn/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/cn/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/cn/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/cn/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/cn/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/cn/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/cn/enterprise/2.15/admin/guides/installation": "/cn/enterprise/2.15/admin/installation", - "/cn/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/cn/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/cn/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/cn/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/cn/enterprise/2.15/admin/guides/installation/log-forwarding": "/cn/enterprise/2.15/admin/installation/log-forwarding", - "/cn/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/cn/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/cn/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/cn/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/cn/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/cn/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/cn/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/cn/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/cn/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/cn/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/cn/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/cn/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/cn/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/cn/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/cn/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/cn/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/cn/enterprise/2.15/admin/guides/installation/network-ports": "/cn/enterprise/2.15/admin/installation/network-ports", - "/cn/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/cn/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/cn/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/cn/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/cn/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/cn/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/cn/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/cn/enterprise/2.15/admin/installation/searching-the-audit-log", - "/cn/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/cn/enterprise/2.15/admin/installation/setting-git-push-limits", - "/cn/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/cn/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/cn/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/cn/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/cn/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/cn/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/cn/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/cn/enterprise/2.15/admin/installation/site-admin-dashboard", - "/cn/enterprise/2.15/admin/guides/installation/system-overview": "/cn/enterprise/2.15/admin/installation/system-overview", - "/cn/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/cn/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/cn/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/cn/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/cn/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/cn/enterprise/2.15/admin/installation/upgrade-requirements", - "/cn/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/cn/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/cn/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/cn/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/cn/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/cn/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/cn/enterprise/2.15/admin/installation/viewing-push-logs", - "/cn/enterprise/2.15/admin/guides/migrations/about-migrations": "/cn/enterprise/2.15/admin/migrations/about-migrations", - "/cn/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/cn/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/cn/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/cn/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/cn/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/cn/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/cn/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/cn/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/cn/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/cn/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/cn/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/cn/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/cn/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/cn/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/cn/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/migrations": "/cn/enterprise/2.15/admin/migrations", - "/cn/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/cn/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/cn/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/cn/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/cn/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/cn/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/cn/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/cn/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/cn/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/cn/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/cn/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/cn/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/cn/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/cn/enterprise/2.15/admin/user-management/about-global-webhooks", - "/cn/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/cn/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/cn/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/cn/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/cn/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/cn/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/cn/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/cn/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/cn/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/cn/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/cn/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/cn/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/cn/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/cn/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/cn/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/cn/enterprise/2.15/admin/user-management/basic-account-settings", - "/cn/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/cn/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/cn/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/cn/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/cn/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/cn/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/cn/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/cn/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/cn/enterprise/2.15/admin/guides/user-management/creating-organizations": "/cn/enterprise/2.15/admin/user-management/creating-organizations", - "/cn/enterprise/2.15/admin/guides/user-management/creating-teams": "/cn/enterprise/2.15/admin/user-management/creating-teams", - "/cn/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/cn/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/cn/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/cn/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/cn/enterprise/2.15/admin/guides/user-management": "/cn/enterprise/2.15/admin/user-management", - "/cn/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/cn/enterprise/2.15/admin/user-management/managing-dormant-users", - "/cn/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/cn/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/cn/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/cn/enterprise/2.15/admin/user-management/organizations-and-teams", - "/cn/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/cn/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/cn/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/cn/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/cn/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/cn/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/cn/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/cn/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/cn/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/cn/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/cn/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/cn/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/cn/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/cn/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/cn/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/cn/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/cn/enterprise/2.15/admin/guides/user-management/repositories": "/cn/enterprise/2.15/admin/user-management/repositories", - "/cn/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/cn/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/cn/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/cn/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/cn/enterprise/2.15/admin/guides/user-management/user-security": "/cn/enterprise/2.15/admin/user-management/user-security", - "/cn/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/cn/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/cn/enterprise/2.15/admin/guides/user-management/using-cas": "/cn/enterprise/2.15/admin/user-management/using-cas", - "/cn/enterprise/2.15/admin/guides/user-management/using-ldap": "/cn/enterprise/2.15/admin/user-management/using-ldap", - "/cn/enterprise/2.15/admin/guides/user-management/using-saml": "/cn/enterprise/2.15/admin/user-management/using-saml", - "/cn/enterprise/2.15/articles/3d-file-viewer": "/cn/enterprise/2.15/user/articles/3d-file-viewer", - "/cn/enterprise/2.15/articles/about-archiving-repositories": "/cn/enterprise/2.15/user/articles/about-archiving-repositories", - "/cn/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/cn/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/cn/enterprise/2.15/articles/about-automation-for-project-boards": "/cn/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/cn/enterprise/2.15/articles/about-branch-restrictions": "/cn/enterprise/2.15/user/articles/about-branch-restrictions", - "/cn/enterprise/2.15/articles/about-branches": "/cn/enterprise/2.15/user/articles/about-branches", - "/cn/enterprise/2.15/articles/about-code-owners": "/cn/enterprise/2.15/user/articles/about-code-owners", - "/cn/enterprise/2.15/articles/about-collaborative-development-models": "/cn/enterprise/2.15/user/articles/about-collaborative-development-models", - "/cn/enterprise/2.15/articles/about-commit-signature-verification": "/cn/enterprise/2.15/user/articles/about-commit-signature-verification", - "/cn/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/cn/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/cn/enterprise/2.15/articles/about-conversations-on-github": "/cn/enterprise/2.15/user/articles/about-conversations-on-github", - "/cn/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.15/articles/about-email-notifications": "/cn/enterprise/2.15/user/articles/about-email-notifications", - "/cn/enterprise/2.15/articles/about-forks": "/cn/enterprise/2.15/user/articles/about-forks", - "/cn/enterprise/2.15/articles/about-git-large-file-storage": "/cn/enterprise/2.15/user/articles/about-git-large-file-storage", - "/cn/enterprise/2.15/articles/about-git-rebase": "/cn/enterprise/2.15/user/articles/about-git-rebase", - "/cn/enterprise/2.15/articles/about-git-subtree-merges": "/cn/enterprise/2.15/user/articles/about-git-subtree-merges", - "/cn/enterprise/2.15/articles/about-github-pages-and-jekyll": "/cn/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/cn/enterprise/2.15/articles/about-github-pages": "/cn/enterprise/2.15/user/articles/about-github-pages", - "/cn/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/cn/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/cn/enterprise/2.15/articles/about-issues": "/cn/enterprise/2.15/user/articles/about-issues", - "/cn/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.15/articles/about-labels": "/cn/enterprise/2.15/user/articles/about-labels", - "/cn/enterprise/2.15/articles/about-merge-conflicts": "/cn/enterprise/2.15/user/articles/about-merge-conflicts", - "/cn/enterprise/2.15/articles/about-merge-methods-on-github": "/cn/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/cn/enterprise/2.15/articles/about-milestones": "/cn/enterprise/2.15/user/articles/about-milestones", - "/cn/enterprise/2.15/articles/about-notifications": "/cn/enterprise/2.15/user/articles/about-notifications", - "/cn/enterprise/2.15/articles/about-organization-membership": "/cn/enterprise/2.15/user/articles/about-organization-membership", - "/cn/enterprise/2.15/articles/about-organizations": "/cn/enterprise/2.15/user/articles/about-organizations", - "/cn/enterprise/2.15/articles/about-project-boards": "/cn/enterprise/2.15/user/articles/about-project-boards", - "/cn/enterprise/2.15/articles/about-protected-branches": "/cn/enterprise/2.15/user/articles/about-protected-branches", - "/cn/enterprise/2.15/articles/about-pull-request-merges": "/cn/enterprise/2.15/user/articles/about-pull-request-merges", - "/cn/enterprise/2.15/articles/about-pull-request-reviews": "/cn/enterprise/2.15/user/articles/about-pull-request-reviews", - "/cn/enterprise/2.15/articles/about-pull-requests": "/cn/enterprise/2.15/user/articles/about-pull-requests", - "/cn/enterprise/2.15/articles/about-readmes": "/cn/enterprise/2.15/user/articles/about-readmes", - "/cn/enterprise/2.15/articles/about-releases": "/cn/enterprise/2.15/user/articles/about-releases", - "/cn/enterprise/2.15/articles/about-remote-repositories": "/cn/enterprise/2.15/user/articles/about-remote-repositories", - "/cn/enterprise/2.15/articles/about-repositories": "/cn/enterprise/2.15/user/articles/about-repositories", - "/cn/enterprise/2.15/articles/about-repository-graphs": "/cn/enterprise/2.15/user/articles/about-repository-graphs", - "/cn/enterprise/2.15/articles/about-repository-languages": "/cn/enterprise/2.15/user/articles/about-repository-languages", - "/cn/enterprise/2.15/articles/about-required-commit-signing": "/cn/enterprise/2.15/user/articles/about-required-commit-signing", - "/cn/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/cn/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.15/articles/about-required-status-checks": "/cn/enterprise/2.15/user/articles/about-required-status-checks", - "/cn/enterprise/2.15/articles/about-saved-replies": "/cn/enterprise/2.15/user/articles/about-saved-replies", - "/cn/enterprise/2.15/articles/about-searching-on-github": "/cn/enterprise/2.15/user/articles/about-searching-on-github", - "/cn/enterprise/2.15/articles/about-ssh": "/cn/enterprise/2.15/user/articles/about-ssh", - "/cn/enterprise/2.15/articles/about-status-checks": "/cn/enterprise/2.15/user/articles/about-status-checks", - "/cn/enterprise/2.15/articles/about-task-lists": "/cn/enterprise/2.15/user/articles/about-task-lists", - "/cn/enterprise/2.15/articles/about-team-discussions": "/cn/enterprise/2.15/user/articles/about-team-discussions", - "/cn/enterprise/2.15/articles/about-teams": "/cn/enterprise/2.15/user/articles/about-teams", - "/cn/enterprise/2.15/articles/about-two-factor-authentication": "/cn/enterprise/2.15/user/articles/about-two-factor-authentication", - "/cn/enterprise/2.15/articles/about-web-notifications": "/cn/enterprise/2.15/user/articles/about-web-notifications", - "/cn/enterprise/2.15/articles/about-webhooks": "/cn/enterprise/2.15/user/articles/about-webhooks", - "/cn/enterprise/2.15/articles/about-wikis": "/cn/enterprise/2.15/user/articles/about-wikis", - "/cn/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/cn/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/cn/enterprise/2.15/articles/about-your-organization-dashboard": "/cn/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/cn/enterprise/2.15/articles/about-your-organizations-news-feed": "/cn/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/cn/enterprise/2.15/articles/about-your-organizations-profile": "/cn/enterprise/2.15/user/articles/about-your-organizations-profile", - "/cn/enterprise/2.15/articles/about-your-personal-dashboard": "/cn/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/cn/enterprise/2.15/articles/about-your-profile": "/cn/enterprise/2.15/user/articles/about-your-profile", - "/cn/enterprise/2.15/articles/access-permissions-on-github": "/cn/enterprise/2.15/user/articles/access-permissions-on-github", - "/cn/enterprise/2.15/articles/accessing-an-organization": "/cn/enterprise/2.15/user/articles/accessing-an-organization", - "/cn/enterprise/2.15/articles/accessing-basic-repository-data": "/cn/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/cn/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/cn/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/cn/enterprise/2.15/articles/accessing-your-notifications": "/cn/enterprise/2.15/user/articles/accessing-your-notifications", - "/cn/enterprise/2.15/articles/accessing-your-organizations-settings": "/cn/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/cn/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/cn/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/cn/enterprise/2.15/articles/adding-a-file-to-a-repository": "/cn/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/cn/enterprise/2.15/articles/adding-a-license-to-a-repository": "/cn/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/cn/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/cn/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/cn/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/cn/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/cn/enterprise/2.15/articles/adding-a-remote": "/cn/enterprise/2.15/user/articles/adding-a-remote", - "/cn/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/cn/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/cn/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/cn/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/cn/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/cn/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/cn/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/cn/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/cn/enterprise/2.15/articles/adding-notes-to-a-project-board": "/cn/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/cn/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/cn/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/cn/enterprise/2.15/articles/adding-organization-members-to-a-team": "/cn/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/cn/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/cn/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/cn/enterprise/2.15/articles/adding-people-to-your-organization": "/cn/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/cn/enterprise/2.15/articles/adding-support-resources-to-your-project": "/cn/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/cn/enterprise/2.15/articles/addressing-merge-conflicts": "/cn/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/cn/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/cn/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/cn/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/cn/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/cn/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/cn/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/cn/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/cn/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/cn/enterprise/2.15/articles/archiving-a-github-repository": "/cn/enterprise/2.15/user/articles/archiving-a-github-repository", - "/cn/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/cn/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/cn/enterprise/2.15/articles/archiving-repositories": "/cn/enterprise/2.15/user/articles/archiving-repositories", - "/cn/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/cn/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/cn/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/cn/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/cn/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/associating-text-editors-with-git": "/cn/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/cn/enterprise/2.15/articles/authorizing-oauth-apps": "/cn/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/cn/enterprise/2.15/articles/autolinked-references-and-urls": "/cn/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/cn/enterprise/2.15/articles/backing-up-a-repository": "/cn/enterprise/2.15/user/articles/backing-up-a-repository", - "/cn/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/cn/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/cn/enterprise/2.15/articles/be-social": "/cn/enterprise/2.15/user/articles/be-social", - "/cn/enterprise/2.15/articles/caching-your-github-password-in-git": "/cn/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/cn/enterprise/2.15/articles/changing-a-commit-message": "/cn/enterprise/2.15/user/articles/changing-a-commit-message", - "/cn/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/cn/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/cn/enterprise/2.15/articles/changing-a-remotes-url": "/cn/enterprise/2.15/user/articles/changing-a-remotes-url", - "/cn/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/cn/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/cn/enterprise/2.15/articles/changing-author-info": "/cn/enterprise/2.15/user/articles/changing-author-info", - "/cn/enterprise/2.15/articles/changing-project-board-visibility": "/cn/enterprise/2.15/user/articles/changing-project-board-visibility", - "/cn/enterprise/2.15/articles/changing-team-visibility": "/cn/enterprise/2.15/user/articles/changing-team-visibility", - "/cn/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/cn/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/cn/enterprise/2.15/articles/changing-your-github-username": "/cn/enterprise/2.15/user/articles/changing-your-github-username", - "/cn/enterprise/2.15/articles/changing-your-primary-email-address": "/cn/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/cn/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/cn/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/cn/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/cn/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/cn/enterprise/2.15/articles/checking-out-pull-requests-locally": "/cn/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/cn/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/cn/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/cn/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/cn/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/cn/enterprise/2.15/articles/classifying-your-repository-with-topics": "/cn/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/cn/enterprise/2.15/articles/cloning-a-repository-from-github": "/cn/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/cn/enterprise/2.15/articles/cloning-a-repository": "/cn/enterprise/2.15/user/articles/cloning-a-repository", - "/cn/enterprise/2.15/articles/closing-a-project-board": "/cn/enterprise/2.15/user/articles/closing-a-project-board", - "/cn/enterprise/2.15/articles/closing-a-pull-request": "/cn/enterprise/2.15/user/articles/closing-a-pull-request", - "/cn/enterprise/2.15/articles/closing-issues-using-keywords": "/cn/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/cn/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/cn/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/cn/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/cn/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/cn/enterprise/2.15/articles/collaborating-with-your-team": "/cn/enterprise/2.15/user/articles/collaborating-with-your-team", - "/cn/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/cn/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/cn/enterprise/2.15/articles/commenting-on-a-pull-request": "/cn/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/cn/enterprise/2.15/articles/commit-branch-and-tag-labels": "/cn/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/cn/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/cn/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/cn/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.15/articles/comparing-commits-across-time": "/cn/enterprise/2.15/user/articles/comparing-commits-across-time", - "/cn/enterprise/2.15/articles/conditions-for-large-files": "/cn/enterprise/2.15/user/articles/conditions-for-large-files", - "/cn/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/cn/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/cn/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/cn/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/cn/enterprise/2.15/articles/configuring-automation-for-project-boards": "/cn/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/cn/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.15/articles/configuring-git-large-file-storage": "/cn/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/cn/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/cn/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/cn/enterprise/2.15/articles/configuring-protected-branches": "/cn/enterprise/2.15/user/articles/configuring-protected-branches", - "/cn/enterprise/2.15/articles/configuring-pull-request-merges": "/cn/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/cn/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/cn/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/cn/enterprise/2.15/articles/configuring-two-factor-authentication": "/cn/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/cn/enterprise/2.15/articles/connecting-to-github-with-ssh": "/cn/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/cn/enterprise/2.15/articles/connecting-with-third-party-applications": "/cn/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/cn/enterprise/2.15/articles/converting-a-user-into-an-organization": "/cn/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/cn/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/cn/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/cn/enterprise/2.15/articles/converting-an-organization-into-a-user": "/cn/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/cn/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/cn/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/cn/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/cn/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/cn/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/cn/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/cn/enterprise/2.15/articles/create-a-repo": "/cn/enterprise/2.15/user/articles/create-a-repo", - "/cn/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/cn/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/cn/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/cn/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/cn/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/cn/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/cn/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/cn/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.15/articles/creating-a-github-pages-site": "/cn/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/cn/enterprise/2.15/articles/creating-a-label": "/cn/enterprise/2.15/user/articles/creating-a-label", - "/cn/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/cn/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/cn/enterprise/2.15/articles/creating-a-new-repository": "/cn/enterprise/2.15/user/articles/creating-a-new-repository", - "/cn/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/cn/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/cn/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/cn/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/cn/enterprise/2.15/articles/creating-a-project-board": "/cn/enterprise/2.15/user/articles/creating-a-project-board", - "/cn/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/cn/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/cn/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/cn/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/cn/enterprise/2.15/articles/creating-a-pull-request": "/cn/enterprise/2.15/user/articles/creating-a-pull-request", - "/cn/enterprise/2.15/articles/creating-a-repository-on-github": "/cn/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/cn/enterprise/2.15/articles/creating-a-saved-reply": "/cn/enterprise/2.15/user/articles/creating-a-saved-reply", - "/cn/enterprise/2.15/articles/creating-a-strong-password": "/cn/enterprise/2.15/user/articles/creating-a-strong-password", - "/cn/enterprise/2.15/articles/creating-a-team-discussion": "/cn/enterprise/2.15/user/articles/creating-a-team-discussion", - "/cn/enterprise/2.15/articles/creating-a-team": "/cn/enterprise/2.15/user/articles/creating-a-team", - "/cn/enterprise/2.15/articles/creating-an-issue": "/cn/enterprise/2.15/user/articles/creating-an-issue", - "/cn/enterprise/2.15/articles/creating-an-issues-only-repository": "/cn/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/cn/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/cn/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/cn/enterprise/2.15/articles/creating-and-editing-commits": "/cn/enterprise/2.15/user/articles/creating-and-editing-commits", - "/cn/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/cn/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/cn/enterprise/2.15/articles/creating-gists": "/cn/enterprise/2.15/user/articles/creating-gists", - "/cn/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/cn/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/cn/enterprise/2.15/articles/creating-new-files": "/cn/enterprise/2.15/user/articles/creating-new-files", - "/cn/enterprise/2.15/articles/creating-releases": "/cn/enterprise/2.15/user/articles/creating-releases", - "/cn/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.15/articles/customizing-your-profile": "/cn/enterprise/2.15/user/articles/customizing-your-profile", - "/cn/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/cn/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/cn/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.15/articles/deleting-a-label": "/cn/enterprise/2.15/user/articles/deleting-a-label", - "/cn/enterprise/2.15/articles/deleting-a-project-board": "/cn/enterprise/2.15/user/articles/deleting-a-project-board", - "/cn/enterprise/2.15/articles/deleting-a-repository": "/cn/enterprise/2.15/user/articles/deleting-a-repository", - "/cn/enterprise/2.15/articles/deleting-a-saved-reply": "/cn/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/cn/enterprise/2.15/articles/deleting-a-team": "/cn/enterprise/2.15/user/articles/deleting-a-team", - "/cn/enterprise/2.15/articles/deleting-an-organization-account": "/cn/enterprise/2.15/user/articles/deleting-an-organization-account", - "/cn/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.15/articles/deleting-files": "/cn/enterprise/2.15/user/articles/deleting-files", - "/cn/enterprise/2.15/articles/deleting-your-user-account": "/cn/enterprise/2.15/user/articles/deleting-your-user-account", - "/cn/enterprise/2.15/articles/differences-between-commit-views": "/cn/enterprise/2.15/user/articles/differences-between-commit-views", - "/cn/enterprise/2.15/articles/disabling-issues": "/cn/enterprise/2.15/user/articles/disabling-issues", - "/cn/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/cn/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/cn/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/cn/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/cn/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/cn/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/cn/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/cn/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/cn/enterprise/2.15/articles/disabling-wikis": "/cn/enterprise/2.15/user/articles/disabling-wikis", - "/cn/enterprise/2.15/articles/dismissing-a-pull-request-review": "/cn/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/cn/enterprise/2.15/articles/distributing-large-binaries": "/cn/enterprise/2.15/user/articles/distributing-large-binaries", - "/cn/enterprise/2.15/articles/documenting-your-project-with-wikis": "/cn/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/cn/enterprise/2.15/articles/duplicating-a-repository": "/cn/enterprise/2.15/user/articles/duplicating-a-repository", - "/cn/enterprise/2.15/articles/editing-a-label": "/cn/enterprise/2.15/user/articles/editing-a-label", - "/cn/enterprise/2.15/articles/editing-a-project-board": "/cn/enterprise/2.15/user/articles/editing-a-project-board", - "/cn/enterprise/2.15/articles/editing-a-saved-reply": "/cn/enterprise/2.15/user/articles/editing-a-saved-reply", - "/cn/enterprise/2.15/articles/editing-and-deleting-releases": "/cn/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/cn/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/cn/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/cn/enterprise/2.15/articles/editing-files-in-another-users-repository": "/cn/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/cn/enterprise/2.15/articles/editing-files-in-your-repository": "/cn/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/cn/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/cn/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/cn/enterprise/2.15/articles/editing-wiki-content": "/cn/enterprise/2.15/user/articles/editing-wiki-content", - "/cn/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.15/articles/enabling-branch-restrictions": "/cn/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/cn/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/cn/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/cn/enterprise/2.15/articles/enabling-required-commit-signing": "/cn/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/cn/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.15/articles/enabling-required-status-checks": "/cn/enterprise/2.15/user/articles/enabling-required-status-checks", - "/cn/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/cn/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/cn/enterprise/2.15/articles/error-bad-file-number": "/cn/enterprise/2.15/user/articles/error-bad-file-number", - "/cn/enterprise/2.15/articles/error-key-already-in-use": "/cn/enterprise/2.15/user/articles/error-key-already-in-use", - "/cn/enterprise/2.15/articles/error-permission-denied-publickey": "/cn/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/cn/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/cn/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/cn/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/cn/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/cn/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/cn/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/cn/enterprise/2.15/articles/error-repository-not-found": "/cn/enterprise/2.15/user/articles/error-repository-not-found", - "/cn/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/cn/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/cn/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/cn/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/cn/enterprise/2.15/articles/exploring-projects-on-github": "/cn/enterprise/2.15/user/articles/exploring-projects-on-github", - "/cn/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/cn/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/cn/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/cn/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/cn/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/cn/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/cn/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/cn/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/cn/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/cn/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/cn/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/cn/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/cn/enterprise/2.15/articles/finding-files-on-github": "/cn/enterprise/2.15/user/articles/finding-files-on-github", - "/cn/enterprise/2.15/articles/finding-information-in-a-repository": "/cn/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/cn/enterprise/2.15/articles/following-people": "/cn/enterprise/2.15/user/articles/following-people", - "/cn/enterprise/2.15/articles/fork-a-repo": "/cn/enterprise/2.15/user/articles/fork-a-repo", - "/cn/enterprise/2.15/articles/forking-and-cloning-gists": "/cn/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/cn/enterprise/2.15/articles/generating-a-new-gpg-key": "/cn/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/cn/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/cn/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/cn/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/cn/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/cn/enterprise/2.15/articles/getting-permanent-links-to-files": "/cn/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/cn/enterprise/2.15/articles/getting-started-with-git-and-github": "/cn/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/cn/enterprise/2.15/articles/getting-started-with-github-pages": "/cn/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/cn/enterprise/2.15/articles/getting-started-with-notifications": "/cn/enterprise/2.15/user/articles/getting-started-with-notifications", - "/cn/enterprise/2.15/articles/getting-started-with-searching-on-github": "/cn/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/cn/enterprise/2.15/articles/getting-started-with-the-api": "/cn/enterprise/2.15/user/articles/getting-started-with-the-api", - "/cn/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/cn/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/cn/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/cn/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/cn/enterprise/2.15/articles/git-and-github-learning-resources": "/cn/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/cn/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/cn/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/cn/enterprise/2.15/articles/git-cheatsheet": "/cn/enterprise/2.15/user/articles/git-cheatsheet", - "/cn/enterprise/2.15/articles/git-workflows": "/cn/enterprise/2.15/user/articles/git-workflows", - "/cn/enterprise/2.15/articles/github-flow": "/cn/enterprise/2.15/user/articles/github-flow", - "/cn/enterprise/2.15/articles/github-glossary": "/cn/enterprise/2.15/user/articles/github-glossary", - "/cn/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/cn/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/cn/enterprise/2.15/articles/https-cloning-errors": "/cn/enterprise/2.15/user/articles/https-cloning-errors", - "/cn/enterprise/2.15/articles/ignoring-files": "/cn/enterprise/2.15/user/articles/ignoring-files", - "/cn/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/cn/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/cn/enterprise/2.15/articles/importing-source-code-to-github": "/cn/enterprise/2.15/user/articles/importing-source-code-to-github", - "/cn/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/cn/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/cn/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/cn/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/cn/enterprise/2.15/articles/installing-git-large-file-storage": "/cn/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/cn/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/cn/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/cn/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/cn/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/cn/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/cn/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/cn/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/cn/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/cn/enterprise/2.15/articles/keeping-your-organization-secure": "/cn/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/cn/enterprise/2.15/articles/keyboard-shortcuts": "/cn/enterprise/2.15/user/articles/keyboard-shortcuts", - "/cn/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/learning-about-git": "/cn/enterprise/2.15/user/articles/learning-about-git", - "/cn/enterprise/2.15/articles/learning-about-github": "/cn/enterprise/2.15/user/articles/learning-about-github", - "/cn/enterprise/2.15/articles/licensing-a-repository": "/cn/enterprise/2.15/user/articles/licensing-a-repository", - "/cn/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/cn/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/cn/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/cn/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/cn/enterprise/2.15/articles/linking-to-releases": "/cn/enterprise/2.15/user/articles/linking-to-releases", - "/cn/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/cn/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/cn/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/cn/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/cn/enterprise/2.15/articles/locking-conversations": "/cn/enterprise/2.15/user/articles/locking-conversations", - "/cn/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/cn/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/cn/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/cn/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/cn/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/cn/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/cn/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/cn/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/cn/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/cn/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/cn/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/cn/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/cn/enterprise/2.15/articles/managing-branches-in-your-repository": "/cn/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/cn/enterprise/2.15/articles/managing-commit-signature-verification": "/cn/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/cn/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/cn/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/cn/enterprise/2.15/articles/managing-disruptive-comments": "/cn/enterprise/2.15/user/articles/managing-disruptive-comments", - "/cn/enterprise/2.15/articles/managing-email-preferences": "/cn/enterprise/2.15/user/articles/managing-email-preferences", - "/cn/enterprise/2.15/articles/managing-files-on-github": "/cn/enterprise/2.15/user/articles/managing-files-on-github", - "/cn/enterprise/2.15/articles/managing-files-using-the-command-line": "/cn/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/cn/enterprise/2.15/articles/managing-membership-in-your-organization": "/cn/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/cn/enterprise/2.15/articles/managing-organization-settings": "/cn/enterprise/2.15/user/articles/managing-organization-settings", - "/cn/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/cn/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/cn/enterprise/2.15/articles/managing-project-boards": "/cn/enterprise/2.15/user/articles/managing-project-boards", - "/cn/enterprise/2.15/articles/managing-releases-in-a-repository": "/cn/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/cn/enterprise/2.15/articles/managing-remote-repositories": "/cn/enterprise/2.15/user/articles/managing-remote-repositories", - "/cn/enterprise/2.15/articles/managing-repository-settings": "/cn/enterprise/2.15/user/articles/managing-repository-settings", - "/cn/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/cn/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/cn/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/cn/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/cn/enterprise/2.15/articles/managing-user-account-settings": "/cn/enterprise/2.15/user/articles/managing-user-account-settings", - "/cn/enterprise/2.15/articles/managing-your-membership-in-organizations": "/cn/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/cn/enterprise/2.15/articles/managing-your-notifications": "/cn/enterprise/2.15/user/articles/managing-your-notifications", - "/cn/enterprise/2.15/articles/managing-your-work-with-issues": "/cn/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/cn/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/cn/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/cn/enterprise/2.15/articles/mapping-geojson-files-on-github": "/cn/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/cn/enterprise/2.15/articles/marking-notifications-as-read": "/cn/enterprise/2.15/user/articles/marking-notifications-as-read", - "/cn/enterprise/2.15/articles/merging-a-pull-request": "/cn/enterprise/2.15/user/articles/merging-a-pull-request", - "/cn/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/cn/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/cn/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/cn/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/cn/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/cn/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/cn/enterprise/2.15/articles/moderating-comments-and-conversations": "/cn/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/cn/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/cn/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/cn/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/cn/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/cn/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/cn/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/cn/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/cn/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/cn/enterprise/2.15/articles/opening-an-issue-from-code": "/cn/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/cn/enterprise/2.15/articles/organizing-information-with-tables": "/cn/enterprise/2.15/user/articles/organizing-information-with-tables", - "/cn/enterprise/2.15/articles/organizing-members-into-teams": "/cn/enterprise/2.15/user/articles/organizing-members-into-teams", - "/cn/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/cn/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/cn/enterprise/2.15/articles/permission-levels-for-an-organization": "/cn/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/cn/enterprise/2.15/articles/personalizing-your-profile": "/cn/enterprise/2.15/user/articles/personalizing-your-profile", - "/cn/enterprise/2.15/articles/pinning-a-team-discussion": "/cn/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/cn/enterprise/2.15/articles/pinning-items-to-your-profile": "/cn/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/cn/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/cn/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.15/articles/preventing-unauthorized-access": "/cn/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/cn/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/cn/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/cn/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/cn/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/cn/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/cn/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/cn/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/cn/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/cn/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/cn/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/cn/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/cn/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/cn/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/cn/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/cn/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/cn/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/cn/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/cn/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/cn/enterprise/2.15/articles/remembering-your-github-username-or-email": "/cn/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/cn/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/cn/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/cn/enterprise/2.15/articles/removing-a-member-from-your-organization": "/cn/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/cn/enterprise/2.15/articles/removing-a-remote": "/cn/enterprise/2.15/user/articles/removing-a-remote", - "/cn/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/cn/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/cn/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/cn/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/cn/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/cn/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/cn/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/cn/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/cn/enterprise/2.15/articles/removing-organization-members-from-a-team": "/cn/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/cn/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/cn/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/cn/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/cn/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/cn/enterprise/2.15/articles/removing-yourself-from-an-organization": "/cn/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/cn/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/cn/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/cn/enterprise/2.15/articles/renaming-a-file": "/cn/enterprise/2.15/user/articles/renaming-a-file", - "/cn/enterprise/2.15/articles/renaming-a-remote": "/cn/enterprise/2.15/user/articles/renaming-a-remote", - "/cn/enterprise/2.15/articles/renaming-a-repository": "/cn/enterprise/2.15/user/articles/renaming-a-repository", - "/cn/enterprise/2.15/articles/renaming-a-team": "/cn/enterprise/2.15/user/articles/renaming-a-team", - "/cn/enterprise/2.15/articles/renaming-an-organization": "/cn/enterprise/2.15/user/articles/renaming-an-organization", - "/cn/enterprise/2.15/articles/rendering-and-diffing-images": "/cn/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/cn/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/cn/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/cn/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/cn/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/cn/enterprise/2.15/articles/rendering-pdf-documents": "/cn/enterprise/2.15/user/articles/rendering-pdf-documents", - "/cn/enterprise/2.15/articles/reopening-a-closed-project-board": "/cn/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/cn/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/cn/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/cn/enterprise/2.15/articles/requesting-a-pull-request-review": "/cn/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/cn/enterprise/2.15/articles/requesting-to-add-a-child-team": "/cn/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/cn/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/cn/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/cn/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/cn/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/cn/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/cn/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/cn/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/cn/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/cn/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/cn/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/cn/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/cn/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.15/articles/reverting-a-pull-request": "/cn/enterprise/2.15/user/articles/reverting-a-pull-request", - "/cn/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/cn/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/cn/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/cn/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/cn/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/cn/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/cn/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/cn/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/cn/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/cn/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/cn/enterprise/2.15/articles/reviewing-your-deploy-keys": "/cn/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/cn/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/cn/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/cn/enterprise/2.15/articles/reviewing-your-security-log": "/cn/enterprise/2.15/user/articles/reviewing-your-security-log", - "/cn/enterprise/2.15/articles/reviewing-your-ssh-keys": "/cn/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/cn/enterprise/2.15/articles/saving-repositories-with-stars": "/cn/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/cn/enterprise/2.15/articles/searching-code": "/cn/enterprise/2.15/user/articles/searching-code", - "/cn/enterprise/2.15/articles/searching-commits": "/cn/enterprise/2.15/user/articles/searching-commits", - "/cn/enterprise/2.15/articles/searching-for-repositories": "/cn/enterprise/2.15/user/articles/searching-for-repositories", - "/cn/enterprise/2.15/articles/searching-in-forks": "/cn/enterprise/2.15/user/articles/searching-in-forks", - "/cn/enterprise/2.15/articles/searching-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/searching-on-github": "/cn/enterprise/2.15/user/articles/searching-on-github", - "/cn/enterprise/2.15/articles/searching-topics": "/cn/enterprise/2.15/user/articles/searching-topics", - "/cn/enterprise/2.15/articles/searching-users": "/cn/enterprise/2.15/user/articles/searching-users", - "/cn/enterprise/2.15/articles/searching-wikis": "/cn/enterprise/2.15/user/articles/searching-wikis", - "/cn/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/cn/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/cn/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/cn/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/cn/enterprise/2.15/articles/set-up-git": "/cn/enterprise/2.15/user/articles/set-up-git", - "/cn/enterprise/2.15/articles/setting-a-backup-email-address": "/cn/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/cn/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/cn/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/cn/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/cn/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/cn/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/cn/enterprise/2.15/articles/setting-repository-visibility": "/cn/enterprise/2.15/user/articles/setting-repository-visibility", - "/cn/enterprise/2.15/articles/setting-the-default-branch": "/cn/enterprise/2.15/user/articles/setting-the-default-branch", - "/cn/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/cn/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/cn/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/cn/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/cn/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/cn/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/cn/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/cn/enterprise/2.15/articles/setting-your-commit-email-address": "/cn/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/cn/enterprise/2.15/articles/setting-your-teams-profile-picture": "/cn/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/cn/enterprise/2.15/articles/setting-your-username-in-git": "/cn/enterprise/2.15/user/articles/setting-your-username-in-git", - "/cn/enterprise/2.15/articles/sharing-filters": "/cn/enterprise/2.15/user/articles/sharing-filters", - "/cn/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/cn/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/cn/enterprise/2.15/articles/signing-commits": "/cn/enterprise/2.15/user/articles/signing-commits", - "/cn/enterprise/2.15/articles/signing-tags": "/cn/enterprise/2.15/user/articles/signing-tags", - "/cn/enterprise/2.15/articles/signing-up-for-github": "/cn/enterprise/2.15/user/articles/signing-up-for-github", - "/cn/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/sorting-search-results": "/cn/enterprise/2.15/user/articles/sorting-search-results", - "/cn/enterprise/2.15/articles/source-code-migration-tools": "/cn/enterprise/2.15/user/articles/source-code-migration-tools", - "/cn/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/cn/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/cn/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/cn/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/cn/enterprise/2.15/articles/subversion-properties-supported-by-github": "/cn/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/cn/enterprise/2.15/articles/sudo-mode": "/cn/enterprise/2.15/user/articles/sudo-mode", - "/cn/enterprise/2.15/articles/support-for-subversion-clients": "/cn/enterprise/2.15/user/articles/support-for-subversion-clients", - "/cn/enterprise/2.15/articles/supported-browsers": "/cn/enterprise/2.15/user/articles/supported-browsers", - "/cn/enterprise/2.15/articles/syncing-a-fork": "/cn/enterprise/2.15/user/articles/syncing-a-fork", - "/cn/enterprise/2.15/articles/telling-git-about-your-signing-key": "/cn/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/cn/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/cn/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/cn/enterprise/2.15/articles/testing-your-ssh-connection": "/cn/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/cn/enterprise/2.15/articles/tracking-changes-in-a-comment": "/cn/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/cn/enterprise/2.15/articles/tracking-changes-in-a-file": "/cn/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/cn/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/cn/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/cn/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/cn/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/cn/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/cn/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/cn/enterprise/2.15/articles/transferring-a-repository": "/cn/enterprise/2.15/user/articles/transferring-a-repository", - "/cn/enterprise/2.15/articles/transferring-organization-ownership": "/cn/enterprise/2.15/user/articles/transferring-organization-ownership", - "/cn/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/cn/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/cn/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/cn/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/cn/enterprise/2.15/articles/troubleshooting-commits": "/cn/enterprise/2.15/user/articles/troubleshooting-commits", - "/cn/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.15/articles/troubleshooting-search-queries": "/cn/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/cn/enterprise/2.15/articles/troubleshooting-ssh": "/cn/enterprise/2.15/user/articles/troubleshooting-ssh", - "/cn/enterprise/2.15/articles/types-of-github-accounts": "/cn/enterprise/2.15/user/articles/types-of-github-accounts", - "/cn/enterprise/2.15/articles/types-of-required-status-checks": "/cn/enterprise/2.15/user/articles/types-of-required-status-checks", - "/cn/enterprise/2.15/articles/understanding-connections-between-repositories": "/cn/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/cn/enterprise/2.15/articles/understanding-the-search-syntax": "/cn/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/cn/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/cn/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/cn/enterprise/2.15/articles/updating-an-expired-gpg-key": "/cn/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/cn/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/cn/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/cn/enterprise/2.15/articles/updating-your-github-access-credentials": "/cn/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/cn/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/cn/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/cn/enterprise/2.15/articles/using-advanced-git-commands": "/cn/enterprise/2.15/user/articles/using-advanced-git-commands", - "/cn/enterprise/2.15/articles/using-common-git-commands": "/cn/enterprise/2.15/user/articles/using-common-git-commands", - "/cn/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/cn/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/cn/enterprise/2.15/articles/using-github": "/cn/enterprise/2.15/user/articles/using-github", - "/cn/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/cn/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/cn/enterprise/2.15/articles/using-saved-replies": "/cn/enterprise/2.15/user/articles/using-saved-replies", - "/cn/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/versioning-large-files": "/cn/enterprise/2.15/user/articles/versioning-large-files", - "/cn/enterprise/2.15/articles/viewing-a-projects-contributors": "/cn/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/cn/enterprise/2.15/articles/viewing-a-pull-request-review": "/cn/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/cn/enterprise/2.15/articles/viewing-a-repositorys-network": "/cn/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/cn/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/cn/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/cn/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/cn/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/cn/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/cn/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/cn/enterprise/2.15/articles/viewing-and-comparing-commits": "/cn/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/cn/enterprise/2.15/articles/viewing-branches-in-your-repository": "/cn/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/cn/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/cn/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/cn/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/cn/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/cn/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/cn/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/cn/enterprise/2.15/articles/viewing-your-milestones-progress": "/cn/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/cn/enterprise/2.15/articles/viewing-your-repositorys-tags": "/cn/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/cn/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/cn/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/cn/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/cn/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/cn/enterprise/2.15/articles/watching-and-unwatching-repositories": "/cn/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/cn/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/cn/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/cn/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/cn/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/cn/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/cn/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/cn/enterprise/2.15/articles/which-remote-url-should-i-use": "/cn/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/cn/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/cn/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/cn/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/cn/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/cn/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/cn/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/cn/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/cn/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/cn/enterprise/2.15/articles/working-with-advanced-formatting": "/cn/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/cn/enterprise/2.15/articles/working-with-forks": "/cn/enterprise/2.15/user/articles/working-with-forks", - "/cn/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/cn/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/cn/enterprise/2.15/articles/working-with-large-files": "/cn/enterprise/2.15/user/articles/working-with-large-files", - "/cn/enterprise/2.15/articles/working-with-non-code-files": "/cn/enterprise/2.15/user/articles/working-with-non-code-files", - "/cn/enterprise/2.15/articles/working-with-pre-receive-hooks": "/cn/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/cn/enterprise/2.15/articles/working-with-saved-replies": "/cn/enterprise/2.15/user/articles/working-with-saved-replies", - "/cn/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/cn/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/cn/enterprise/2.15/articles/working-with-subversion-on-github": "/cn/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/cn/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/cn/enterprise/2.15/user/categories/administering-a-repository", - "/cn/enterprise/2.15/categories/administering-a-repository": "/cn/enterprise/2.15/user/categories/administering-a-repository", - "/cn/enterprise/2.15/categories/authenticating-to-github": "/cn/enterprise/2.15/user/categories/authenticating-to-github", - "/cn/enterprise/2.15/categories/building-a-strong-community": "/cn/enterprise/2.15/user/categories/building-a-strong-community", - "/cn/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/cn/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/cn/enterprise/2.15/categories/committing-changes-to-your-project": "/cn/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/cn/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/cn/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/cn/enterprise/2.15/categories/extending-github": "/cn/enterprise/2.15/user/categories/extending-github", - "/cn/enterprise/2.15/categories/getting-started-with-github": "/cn/enterprise/2.15/user/categories/getting-started-with-github", - "/cn/enterprise/2.15/categories/importing-your-projects-to-github": "/cn/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/cn/enterprise/2.15/categories/managing-files-in-a-repository": "/cn/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/cn/enterprise/2.15/categories/managing-large-files": "/cn/enterprise/2.15/user/categories/managing-large-files", - "/cn/enterprise/2.15/categories/managing-your-work-on-github": "/cn/enterprise/2.15/user/categories/managing-your-work-on-github", - "/cn/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/cn/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/cn/enterprise/2.15/categories/searching-for-information-on-github": "/cn/enterprise/2.15/user/categories/searching-for-information-on-github", - "/cn/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/cn/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/cn/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/cn/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/cn/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/cn/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/cn/enterprise/2.15/categories/using-git": "/cn/enterprise/2.15/user/categories/using-git", - "/cn/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/cn/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/cn/enterprise/2.15/categories/working-with-github-pages": "/cn/enterprise/2.15/user/categories/working-with-github-pages", - "/cn/enterprise/2.15/categories/writing-on-github": "/cn/enterprise/2.15/user/categories/writing-on-github", - "/en/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/en/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/en/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/en/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.15/admin/articles/using-github-task-runner", - "/enterprise/2.15/admin/articles/using-github-task-runner": "/en/enterprise/2.15/admin/articles/using-github-task-runner", - "/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.15/admin/articles/using-github-task-runner", - "/en/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/enterprise/2.15/admin/clustering/about-cluster-nodes": "/en/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/en/enterprise/2.15/admin/guides/clustering/clustering-overview": "/en/enterprise/2.15/admin/clustering/clustering-overview", - "/enterprise/2.15/admin/clustering/clustering-overview": "/en/enterprise/2.15/admin/clustering/clustering-overview", - "/enterprise/2.15/admin/guides/clustering/clustering-overview": "/en/enterprise/2.15/admin/clustering/clustering-overview", - "/en/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/en/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.15/admin/clustering/evacuating-a-cluster-node": "/en/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/en/enterprise/2.15/admin/guides/clustering": "/en/enterprise/2.15/admin/clustering", - "/enterprise/2.15/admin/clustering": "/en/enterprise/2.15/admin/clustering", - "/enterprise/2.15/admin/guides/clustering": "/en/enterprise/2.15/admin/clustering", - "/en/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/enterprise/2.15/admin/clustering/initializing-the-cluster": "/en/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/en/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/en/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.15/admin/clustering/monitoring-cluster-nodes": "/en/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/en/enterprise/2.15/admin/guides/clustering/network-configuration": "/en/enterprise/2.15/admin/clustering/network-configuration", - "/enterprise/2.15/admin/clustering/network-configuration": "/en/enterprise/2.15/admin/clustering/network-configuration", - "/enterprise/2.15/admin/guides/clustering/network-configuration": "/en/enterprise/2.15/admin/clustering/network-configuration", - "/en/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.15/admin/clustering/replacing-a-cluster-node": "/en/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/en/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/en/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/enterprise/2.15/admin/clustering/upgrading-a-cluster": "/en/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/en/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/en/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/en/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/en/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/en/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/en/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/en/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/en/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/en/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/en/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/en/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/en/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/en/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/en/enterprise/2.15/admin/guides/developer-workflow": "/en/enterprise/2.15/admin/developer-workflow", - "/enterprise/2.15/admin/developer-workflow": "/en/enterprise/2.15/admin/developer-workflow", - "/enterprise/2.15/admin/guides/developer-workflow": "/en/enterprise/2.15/admin/developer-workflow", - "/en/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/en/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/en/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/en/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/en/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/en/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/en/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/en/enterprise/2.15/admin/guides/enterprise-support": "/en/enterprise/2.15/admin/enterprise-support", - "/enterprise/2.15/admin/enterprise-support": "/en/enterprise/2.15/admin/enterprise-support", - "/enterprise/2.15/admin/guides/enterprise-support": "/en/enterprise/2.15/admin/enterprise-support", - "/en/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/en/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/en/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/enterprise/2.15/admin/enterprise-support/reaching-github-support": "/en/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/en/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/en/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.15/admin/enterprise-support/submitting-a-ticket": "/en/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/en/enterprise/2.15/admin/guides": "/en/enterprise/2.15/admin", - "/enterprise/2.15/admin": "/en/enterprise/2.15/admin", - "/enterprise/2.15/admin/guides": "/en/enterprise/2.15/admin", - "/en/enterprise/2.15/admin/guides/installation/about-geo-replication": "/en/enterprise/2.15/admin/installation/about-geo-replication", - "/enterprise/2.15/admin/installation/about-geo-replication": "/en/enterprise/2.15/admin/installation/about-geo-replication", - "/enterprise/2.15/admin/guides/installation/about-geo-replication": "/en/enterprise/2.15/admin/installation/about-geo-replication", - "/en/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/enterprise/2.15/admin/installation/about-high-availability-configuration": "/en/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/en/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/en/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/en/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.15/admin/installation/accessing-the-management-console", - "/enterprise/2.15/admin/installation/accessing-the-management-console": "/en/enterprise/2.15/admin/installation/accessing-the-management-console", - "/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.15/admin/installation/accessing-the-management-console", - "/en/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/en/enterprise/2.15/admin/guides/installation/activity-dashboard": "/en/enterprise/2.15/admin/installation/activity-dashboard", - "/enterprise/2.15/admin/installation/activity-dashboard": "/en/enterprise/2.15/admin/installation/activity-dashboard", - "/enterprise/2.15/admin/guides/installation/activity-dashboard": "/en/enterprise/2.15/admin/installation/activity-dashboard", - "/en/enterprise/2.15/admin/guides/installation/audit-logging": "/en/enterprise/2.15/admin/installation/audit-logging", - "/enterprise/2.15/admin/installation/audit-logging": "/en/enterprise/2.15/admin/installation/audit-logging", - "/enterprise/2.15/admin/guides/installation/audit-logging": "/en/enterprise/2.15/admin/installation/audit-logging", - "/en/enterprise/2.15/admin/guides/installation/audited-actions": "/en/enterprise/2.15/admin/installation/audited-actions", - "/enterprise/2.15/admin/installation/audited-actions": "/en/enterprise/2.15/admin/installation/audited-actions", - "/enterprise/2.15/admin/guides/installation/audited-actions": "/en/enterprise/2.15/admin/installation/audited-actions", - "/en/enterprise/2.15/admin/guides/installation/command-line-utilities": "/en/enterprise/2.15/admin/installation/command-line-utilities", - "/enterprise/2.15/admin/installation/command-line-utilities": "/en/enterprise/2.15/admin/installation/command-line-utilities", - "/enterprise/2.15/admin/guides/installation/command-line-utilities": "/en/enterprise/2.15/admin/installation/command-line-utilities", - "/en/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.15/admin/installation/configuring-a-hostname", - "/enterprise/2.15/admin/installation/configuring-a-hostname": "/en/enterprise/2.15/admin/installation/configuring-a-hostname", - "/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.15/admin/installation/configuring-a-hostname", - "/en/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/en/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/en/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/en/enterprise/2.15/admin/guides/installation/configuring-collectd": "/en/enterprise/2.15/admin/installation/configuring-collectd", - "/enterprise/2.15/admin/installation/configuring-collectd": "/en/enterprise/2.15/admin/installation/configuring-collectd", - "/enterprise/2.15/admin/guides/installation/configuring-collectd": "/en/enterprise/2.15/admin/installation/configuring-collectd", - "/en/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/enterprise/2.15/admin/installation/configuring-dns-nameservers": "/en/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/en/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/en/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.15/admin/installation/configuring-git-large-file-storage": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/en/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/en/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/en/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.15/admin/installation/configuring-rate-limits", - "/enterprise/2.15/admin/installation/configuring-rate-limits": "/en/enterprise/2.15/admin/installation/configuring-rate-limits", - "/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.15/admin/installation/configuring-rate-limits", - "/en/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/en/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/en/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/en/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/enterprise/2.15/admin/installation/configuring-time-synchronization": "/en/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/en/enterprise/2.15/admin/guides/installation/configuring-tls": "/en/enterprise/2.15/admin/installation/configuring-tls", - "/enterprise/2.15/admin/installation/configuring-tls": "/en/enterprise/2.15/admin/installation/configuring-tls", - "/enterprise/2.15/admin/guides/installation/configuring-tls": "/en/enterprise/2.15/admin/installation/configuring-tls", - "/en/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/en/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/en/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.15/admin/installation/creating-a-high-availability-replica": "/en/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/en/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/en/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/en/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.15/admin/installation/enabling-automatic-update-checks": "/en/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/en/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.15/admin/installation/enabling-private-mode", - "/enterprise/2.15/admin/installation/enabling-private-mode": "/en/enterprise/2.15/admin/installation/enabling-private-mode", - "/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.15/admin/installation/enabling-private-mode", - "/en/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.15/admin/installation/enabling-subdomain-isolation": "/en/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/en/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/en/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/enterprise/2.15/admin/installation/increasing-storage-capacity": "/en/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/en/enterprise/2.15/admin/guides/installation": "/en/enterprise/2.15/admin/installation", - "/enterprise/2.15/admin/installation": "/en/enterprise/2.15/admin/installation", - "/enterprise/2.15/admin/guides/installation": "/en/enterprise/2.15/admin/installation", - "/en/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/en/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/en/enterprise/2.15/admin/guides/installation/log-forwarding": "/en/enterprise/2.15/admin/installation/log-forwarding", - "/enterprise/2.15/admin/installation/log-forwarding": "/en/enterprise/2.15/admin/installation/log-forwarding", - "/enterprise/2.15/admin/guides/installation/log-forwarding": "/en/enterprise/2.15/admin/installation/log-forwarding", - "/en/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/en/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/en/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/en/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/en/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/en/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/en/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/enterprise/2.15/admin/installation/monitoring-using-snmp": "/en/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/en/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/en/enterprise/2.15/admin/guides/installation/network-ports": "/en/enterprise/2.15/admin/installation/network-ports", - "/enterprise/2.15/admin/installation/network-ports": "/en/enterprise/2.15/admin/installation/network-ports", - "/enterprise/2.15/admin/guides/installation/network-ports": "/en/enterprise/2.15/admin/installation/network-ports", - "/en/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/enterprise/2.15/admin/installation/recommended-alert-thresholds": "/en/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/en/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/en/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.15/admin/installation/removing-a-high-availability-replica": "/en/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/en/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.15/admin/installation/searching-the-audit-log", - "/enterprise/2.15/admin/installation/searching-the-audit-log": "/en/enterprise/2.15/admin/installation/searching-the-audit-log", - "/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.15/admin/installation/searching-the-audit-log", - "/en/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.15/admin/installation/setting-git-push-limits", - "/enterprise/2.15/admin/installation/setting-git-push-limits": "/en/enterprise/2.15/admin/installation/setting-git-push-limits", - "/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.15/admin/installation/setting-git-push-limits", - "/en/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/en/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.15/admin/installation/setting-up-a-staging-instance": "/en/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/en/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/enterprise/2.15/admin/installation/setting-up-external-monitoring": "/en/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/en/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.15/admin/installation/site-admin-dashboard", - "/enterprise/2.15/admin/installation/site-admin-dashboard": "/en/enterprise/2.15/admin/installation/site-admin-dashboard", - "/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.15/admin/installation/site-admin-dashboard", - "/en/enterprise/2.15/admin/guides/installation/system-overview": "/en/enterprise/2.15/admin/installation/system-overview", - "/enterprise/2.15/admin/installation/system-overview": "/en/enterprise/2.15/admin/installation/system-overview", - "/enterprise/2.15/admin/guides/installation/system-overview": "/en/enterprise/2.15/admin/installation/system-overview", - "/en/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.15/admin/installation/troubleshooting-ssl-errors": "/en/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/en/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/en/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.15/admin/installation/upgrade-requirements", - "/enterprise/2.15/admin/installation/upgrade-requirements": "/en/enterprise/2.15/admin/installation/upgrade-requirements", - "/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.15/admin/installation/upgrade-requirements", - "/en/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.15/admin/installation/upgrading-github-enterprise-server": "/en/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/en/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/enterprise/2.15/admin/installation/validating-your-domain-settings": "/en/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/en/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.15/admin/installation/viewing-push-logs", - "/enterprise/2.15/admin/installation/viewing-push-logs": "/en/enterprise/2.15/admin/installation/viewing-push-logs", - "/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.15/admin/installation/viewing-push-logs", - "/en/enterprise/2.15/admin/guides/migrations/about-migrations": "/en/enterprise/2.15/admin/migrations/about-migrations", - "/enterprise/2.15/admin/migrations/about-migrations": "/en/enterprise/2.15/admin/migrations/about-migrations", - "/enterprise/2.15/admin/guides/migrations/about-migrations": "/en/enterprise/2.15/admin/migrations/about-migrations", - "/en/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/en/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/en/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/en/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/en/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/en/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/migrations": "/en/enterprise/2.15/admin/migrations", - "/enterprise/2.15/admin/migrations": "/en/enterprise/2.15/admin/migrations", - "/enterprise/2.15/admin/guides/migrations": "/en/enterprise/2.15/admin/migrations", - "/en/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/en/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/en/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/en/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/en/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.15/admin/migrations/reviewing-migration-conflicts": "/en/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/en/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/enterprise/2.15/admin/migrations/reviewing-migration-data": "/en/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/en/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.15/admin/user-management/about-global-webhooks", - "/enterprise/2.15/admin/user-management/about-global-webhooks": "/en/enterprise/2.15/admin/user-management/about-global-webhooks", - "/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.15/admin/user-management/about-global-webhooks", - "/en/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/enterprise/2.15/admin/user-management/adding-people-to-teams": "/en/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/en/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/en/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/en/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/en/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/enterprise/2.15/admin/user-management/auditing-ssh-keys": "/en/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/en/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.15/admin/user-management/auditing-users-across-your-instance": "/en/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/en/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/en/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.15/admin/user-management/basic-account-settings", - "/enterprise/2.15/admin/user-management/basic-account-settings": "/en/enterprise/2.15/admin/user-management/basic-account-settings", - "/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.15/admin/user-management/basic-account-settings", - "/en/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/enterprise/2.15/admin/user-management/best-practices-for-user-security": "/en/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/en/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/enterprise/2.15/admin/user-management/changing-authentication-methods": "/en/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/en/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.15/admin/user-management/configuring-email-for-notifications": "/en/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/en/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/en/enterprise/2.15/admin/guides/user-management/creating-organizations": "/en/enterprise/2.15/admin/user-management/creating-organizations", - "/enterprise/2.15/admin/user-management/creating-organizations": "/en/enterprise/2.15/admin/user-management/creating-organizations", - "/enterprise/2.15/admin/guides/user-management/creating-organizations": "/en/enterprise/2.15/admin/user-management/creating-organizations", - "/en/enterprise/2.15/admin/guides/user-management/creating-teams": "/en/enterprise/2.15/admin/user-management/creating-teams", - "/enterprise/2.15/admin/user-management/creating-teams": "/en/enterprise/2.15/admin/user-management/creating-teams", - "/enterprise/2.15/admin/guides/user-management/creating-teams": "/en/enterprise/2.15/admin/user-management/creating-teams", - "/en/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/en/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/en/enterprise/2.15/admin/guides/user-management": "/en/enterprise/2.15/admin/user-management", - "/enterprise/2.15/admin/user-management": "/en/enterprise/2.15/admin/user-management", - "/enterprise/2.15/admin/guides/user-management": "/en/enterprise/2.15/admin/user-management", - "/en/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.15/admin/user-management/managing-dormant-users", - "/enterprise/2.15/admin/user-management/managing-dormant-users": "/en/enterprise/2.15/admin/user-management/managing-dormant-users", - "/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.15/admin/user-management/managing-dormant-users", - "/en/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/enterprise/2.15/admin/user-management/managing-global-webhooks": "/en/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/en/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.15/admin/user-management/organizations-and-teams", - "/enterprise/2.15/admin/user-management/organizations-and-teams": "/en/enterprise/2.15/admin/user-management/organizations-and-teams", - "/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.15/admin/user-management/organizations-and-teams", - "/en/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/en/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/en/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/en/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/en/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/en/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/en/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.15/admin/user-management/rebuilding-contributions-data": "/en/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/en/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/en/enterprise/2.15/admin/guides/user-management/repositories": "/en/enterprise/2.15/admin/user-management/repositories", - "/enterprise/2.15/admin/user-management/repositories": "/en/enterprise/2.15/admin/user-management/repositories", - "/enterprise/2.15/admin/guides/user-management/repositories": "/en/enterprise/2.15/admin/user-management/repositories", - "/en/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/en/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/en/enterprise/2.15/admin/guides/user-management/user-security": "/en/enterprise/2.15/admin/user-management/user-security", - "/enterprise/2.15/admin/user-management/user-security": "/en/enterprise/2.15/admin/user-management/user-security", - "/enterprise/2.15/admin/guides/user-management/user-security": "/en/enterprise/2.15/admin/user-management/user-security", - "/en/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/enterprise/2.15/admin/user-management/using-built-in-authentication": "/en/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/en/enterprise/2.15/admin/guides/user-management/using-cas": "/en/enterprise/2.15/admin/user-management/using-cas", - "/enterprise/2.15/admin/user-management/using-cas": "/en/enterprise/2.15/admin/user-management/using-cas", - "/enterprise/2.15/admin/guides/user-management/using-cas": "/en/enterprise/2.15/admin/user-management/using-cas", - "/en/enterprise/2.15/admin/guides/user-management/using-ldap": "/en/enterprise/2.15/admin/user-management/using-ldap", - "/enterprise/2.15/admin/user-management/using-ldap": "/en/enterprise/2.15/admin/user-management/using-ldap", - "/enterprise/2.15/admin/guides/user-management/using-ldap": "/en/enterprise/2.15/admin/user-management/using-ldap", - "/en/enterprise/2.15/admin/guides/user-management/using-saml": "/en/enterprise/2.15/admin/user-management/using-saml", - "/enterprise/2.15/admin/user-management/using-saml": "/en/enterprise/2.15/admin/user-management/using-saml", - "/enterprise/2.15/admin/guides/user-management/using-saml": "/en/enterprise/2.15/admin/user-management/using-saml", - "/enterprise/2.15": "/en/enterprise/2.15", - "/en/enterprise/2.15/articles/3d-file-viewer": "/en/enterprise/2.15/user/articles/3d-file-viewer", - "/enterprise/2.15/user/articles/3d-file-viewer": "/en/enterprise/2.15/user/articles/3d-file-viewer", - "/enterprise/2.15/articles/3d-file-viewer": "/en/enterprise/2.15/user/articles/3d-file-viewer", - "/en/enterprise/2.15/articles/about-archiving-repositories": "/en/enterprise/2.15/user/articles/about-archiving-repositories", - "/enterprise/2.15/user/articles/about-archiving-repositories": "/en/enterprise/2.15/user/articles/about-archiving-repositories", - "/enterprise/2.15/articles/about-archiving-repositories": "/en/enterprise/2.15/user/articles/about-archiving-repositories", - "/en/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.15/articles/about-automation-for-project-boards": "/en/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/enterprise/2.15/user/articles/about-automation-for-project-boards": "/en/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/enterprise/2.15/articles/about-automation-for-project-boards": "/en/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/en/enterprise/2.15/articles/about-branch-restrictions": "/en/enterprise/2.15/user/articles/about-branch-restrictions", - "/enterprise/2.15/user/articles/about-branch-restrictions": "/en/enterprise/2.15/user/articles/about-branch-restrictions", - "/enterprise/2.15/articles/about-branch-restrictions": "/en/enterprise/2.15/user/articles/about-branch-restrictions", - "/en/enterprise/2.15/articles/about-branches": "/en/enterprise/2.15/user/articles/about-branches", - "/enterprise/2.15/user/articles/about-branches": "/en/enterprise/2.15/user/articles/about-branches", - "/enterprise/2.15/articles/about-branches": "/en/enterprise/2.15/user/articles/about-branches", - "/en/enterprise/2.15/articles/about-code-owners": "/en/enterprise/2.15/user/articles/about-code-owners", - "/enterprise/2.15/user/articles/about-code-owners": "/en/enterprise/2.15/user/articles/about-code-owners", - "/enterprise/2.15/articles/about-code-owners": "/en/enterprise/2.15/user/articles/about-code-owners", - "/en/enterprise/2.15/articles/about-collaborative-development-models": "/en/enterprise/2.15/user/articles/about-collaborative-development-models", - "/enterprise/2.15/user/articles/about-collaborative-development-models": "/en/enterprise/2.15/user/articles/about-collaborative-development-models", - "/enterprise/2.15/articles/about-collaborative-development-models": "/en/enterprise/2.15/user/articles/about-collaborative-development-models", - "/en/enterprise/2.15/articles/about-commit-signature-verification": "/en/enterprise/2.15/user/articles/about-commit-signature-verification", - "/enterprise/2.15/user/articles/about-commit-signature-verification": "/en/enterprise/2.15/user/articles/about-commit-signature-verification", - "/enterprise/2.15/articles/about-commit-signature-verification": "/en/enterprise/2.15/user/articles/about-commit-signature-verification", - "/en/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/en/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.15/articles/about-conversations-on-github": "/en/enterprise/2.15/user/articles/about-conversations-on-github", - "/enterprise/2.15/user/articles/about-conversations-on-github": "/en/enterprise/2.15/user/articles/about-conversations-on-github", - "/enterprise/2.15/articles/about-conversations-on-github": "/en/enterprise/2.15/user/articles/about-conversations-on-github", - "/en/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.15/articles/about-email-notifications": "/en/enterprise/2.15/user/articles/about-email-notifications", - "/enterprise/2.15/user/articles/about-email-notifications": "/en/enterprise/2.15/user/articles/about-email-notifications", - "/enterprise/2.15/articles/about-email-notifications": "/en/enterprise/2.15/user/articles/about-email-notifications", - "/en/enterprise/2.15/articles/about-forks": "/en/enterprise/2.15/user/articles/about-forks", - "/enterprise/2.15/user/articles/about-forks": "/en/enterprise/2.15/user/articles/about-forks", - "/enterprise/2.15/articles/about-forks": "/en/enterprise/2.15/user/articles/about-forks", - "/en/enterprise/2.15/articles/about-git-large-file-storage": "/en/enterprise/2.15/user/articles/about-git-large-file-storage", - "/enterprise/2.15/user/articles/about-git-large-file-storage": "/en/enterprise/2.15/user/articles/about-git-large-file-storage", - "/enterprise/2.15/articles/about-git-large-file-storage": "/en/enterprise/2.15/user/articles/about-git-large-file-storage", - "/en/enterprise/2.15/articles/about-git-rebase": "/en/enterprise/2.15/user/articles/about-git-rebase", - "/enterprise/2.15/user/articles/about-git-rebase": "/en/enterprise/2.15/user/articles/about-git-rebase", - "/enterprise/2.15/articles/about-git-rebase": "/en/enterprise/2.15/user/articles/about-git-rebase", - "/en/enterprise/2.15/articles/about-git-subtree-merges": "/en/enterprise/2.15/user/articles/about-git-subtree-merges", - "/enterprise/2.15/user/articles/about-git-subtree-merges": "/en/enterprise/2.15/user/articles/about-git-subtree-merges", - "/enterprise/2.15/articles/about-git-subtree-merges": "/en/enterprise/2.15/user/articles/about-git-subtree-merges", - "/en/enterprise/2.15/articles/about-github-pages-and-jekyll": "/en/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/enterprise/2.15/user/articles/about-github-pages-and-jekyll": "/en/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/enterprise/2.15/articles/about-github-pages-and-jekyll": "/en/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/en/enterprise/2.15/articles/about-github-pages": "/en/enterprise/2.15/user/articles/about-github-pages", - "/enterprise/2.15/user/articles/about-github-pages": "/en/enterprise/2.15/user/articles/about-github-pages", - "/enterprise/2.15/articles/about-github-pages": "/en/enterprise/2.15/user/articles/about-github-pages", - "/en/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/enterprise/2.15/user/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/en/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/en/enterprise/2.15/articles/about-issues": "/en/enterprise/2.15/user/articles/about-issues", - "/enterprise/2.15/user/articles/about-issues": "/en/enterprise/2.15/user/articles/about-issues", - "/enterprise/2.15/articles/about-issues": "/en/enterprise/2.15/user/articles/about-issues", - "/en/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.15/articles/about-labels": "/en/enterprise/2.15/user/articles/about-labels", - "/enterprise/2.15/user/articles/about-labels": "/en/enterprise/2.15/user/articles/about-labels", - "/enterprise/2.15/articles/about-labels": "/en/enterprise/2.15/user/articles/about-labels", - "/en/enterprise/2.15/articles/about-merge-conflicts": "/en/enterprise/2.15/user/articles/about-merge-conflicts", - "/enterprise/2.15/user/articles/about-merge-conflicts": "/en/enterprise/2.15/user/articles/about-merge-conflicts", - "/enterprise/2.15/articles/about-merge-conflicts": "/en/enterprise/2.15/user/articles/about-merge-conflicts", - "/en/enterprise/2.15/articles/about-merge-methods-on-github": "/en/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/enterprise/2.15/user/articles/about-merge-methods-on-github": "/en/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/enterprise/2.15/articles/about-merge-methods-on-github": "/en/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/en/enterprise/2.15/articles/about-milestones": "/en/enterprise/2.15/user/articles/about-milestones", - "/enterprise/2.15/user/articles/about-milestones": "/en/enterprise/2.15/user/articles/about-milestones", - "/enterprise/2.15/articles/about-milestones": "/en/enterprise/2.15/user/articles/about-milestones", - "/en/enterprise/2.15/articles/about-notifications": "/en/enterprise/2.15/user/articles/about-notifications", - "/enterprise/2.15/user/articles/about-notifications": "/en/enterprise/2.15/user/articles/about-notifications", - "/enterprise/2.15/articles/about-notifications": "/en/enterprise/2.15/user/articles/about-notifications", - "/en/enterprise/2.15/articles/about-organization-membership": "/en/enterprise/2.15/user/articles/about-organization-membership", - "/enterprise/2.15/user/articles/about-organization-membership": "/en/enterprise/2.15/user/articles/about-organization-membership", - "/enterprise/2.15/articles/about-organization-membership": "/en/enterprise/2.15/user/articles/about-organization-membership", - "/en/enterprise/2.15/articles/about-organizations": "/en/enterprise/2.15/user/articles/about-organizations", - "/enterprise/2.15/user/articles/about-organizations": "/en/enterprise/2.15/user/articles/about-organizations", - "/enterprise/2.15/articles/about-organizations": "/en/enterprise/2.15/user/articles/about-organizations", - "/en/enterprise/2.15/articles/about-project-boards": "/en/enterprise/2.15/user/articles/about-project-boards", - "/enterprise/2.15/user/articles/about-project-boards": "/en/enterprise/2.15/user/articles/about-project-boards", - "/enterprise/2.15/articles/about-project-boards": "/en/enterprise/2.15/user/articles/about-project-boards", - "/en/enterprise/2.15/articles/about-protected-branches": "/en/enterprise/2.15/user/articles/about-protected-branches", - "/enterprise/2.15/user/articles/about-protected-branches": "/en/enterprise/2.15/user/articles/about-protected-branches", - "/enterprise/2.15/articles/about-protected-branches": "/en/enterprise/2.15/user/articles/about-protected-branches", - "/en/enterprise/2.15/articles/about-pull-request-merges": "/en/enterprise/2.15/user/articles/about-pull-request-merges", - "/enterprise/2.15/user/articles/about-pull-request-merges": "/en/enterprise/2.15/user/articles/about-pull-request-merges", - "/enterprise/2.15/articles/about-pull-request-merges": "/en/enterprise/2.15/user/articles/about-pull-request-merges", - "/en/enterprise/2.15/articles/about-pull-request-reviews": "/en/enterprise/2.15/user/articles/about-pull-request-reviews", - "/enterprise/2.15/user/articles/about-pull-request-reviews": "/en/enterprise/2.15/user/articles/about-pull-request-reviews", - "/enterprise/2.15/articles/about-pull-request-reviews": "/en/enterprise/2.15/user/articles/about-pull-request-reviews", - "/en/enterprise/2.15/articles/about-pull-requests": "/en/enterprise/2.15/user/articles/about-pull-requests", - "/enterprise/2.15/user/articles/about-pull-requests": "/en/enterprise/2.15/user/articles/about-pull-requests", - "/enterprise/2.15/articles/about-pull-requests": "/en/enterprise/2.15/user/articles/about-pull-requests", - "/en/enterprise/2.15/articles/about-readmes": "/en/enterprise/2.15/user/articles/about-readmes", - "/enterprise/2.15/user/articles/about-readmes": "/en/enterprise/2.15/user/articles/about-readmes", - "/enterprise/2.15/articles/about-readmes": "/en/enterprise/2.15/user/articles/about-readmes", - "/en/enterprise/2.15/articles/about-releases": "/en/enterprise/2.15/user/articles/about-releases", - "/enterprise/2.15/user/articles/about-releases": "/en/enterprise/2.15/user/articles/about-releases", - "/enterprise/2.15/articles/about-releases": "/en/enterprise/2.15/user/articles/about-releases", - "/en/enterprise/2.15/articles/about-remote-repositories": "/en/enterprise/2.15/user/articles/about-remote-repositories", - "/enterprise/2.15/user/articles/about-remote-repositories": "/en/enterprise/2.15/user/articles/about-remote-repositories", - "/enterprise/2.15/articles/about-remote-repositories": "/en/enterprise/2.15/user/articles/about-remote-repositories", - "/en/enterprise/2.15/articles/about-repositories": "/en/enterprise/2.15/user/articles/about-repositories", - "/enterprise/2.15/user/articles/about-repositories": "/en/enterprise/2.15/user/articles/about-repositories", - "/enterprise/2.15/articles/about-repositories": "/en/enterprise/2.15/user/articles/about-repositories", - "/en/enterprise/2.15/articles/about-repository-graphs": "/en/enterprise/2.15/user/articles/about-repository-graphs", - "/enterprise/2.15/user/articles/about-repository-graphs": "/en/enterprise/2.15/user/articles/about-repository-graphs", - "/enterprise/2.15/articles/about-repository-graphs": "/en/enterprise/2.15/user/articles/about-repository-graphs", - "/en/enterprise/2.15/articles/about-repository-languages": "/en/enterprise/2.15/user/articles/about-repository-languages", - "/enterprise/2.15/user/articles/about-repository-languages": "/en/enterprise/2.15/user/articles/about-repository-languages", - "/enterprise/2.15/articles/about-repository-languages": "/en/enterprise/2.15/user/articles/about-repository-languages", - "/en/enterprise/2.15/articles/about-required-commit-signing": "/en/enterprise/2.15/user/articles/about-required-commit-signing", - "/enterprise/2.15/user/articles/about-required-commit-signing": "/en/enterprise/2.15/user/articles/about-required-commit-signing", - "/enterprise/2.15/articles/about-required-commit-signing": "/en/enterprise/2.15/user/articles/about-required-commit-signing", - "/en/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/en/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/en/enterprise/2.15/articles/about-required-status-checks": "/en/enterprise/2.15/user/articles/about-required-status-checks", - "/enterprise/2.15/user/articles/about-required-status-checks": "/en/enterprise/2.15/user/articles/about-required-status-checks", - "/enterprise/2.15/articles/about-required-status-checks": "/en/enterprise/2.15/user/articles/about-required-status-checks", - "/en/enterprise/2.15/articles/about-saved-replies": "/en/enterprise/2.15/user/articles/about-saved-replies", - "/enterprise/2.15/user/articles/about-saved-replies": "/en/enterprise/2.15/user/articles/about-saved-replies", - "/enterprise/2.15/articles/about-saved-replies": "/en/enterprise/2.15/user/articles/about-saved-replies", - "/en/enterprise/2.15/articles/about-searching-on-github": "/en/enterprise/2.15/user/articles/about-searching-on-github", - "/enterprise/2.15/user/articles/about-searching-on-github": "/en/enterprise/2.15/user/articles/about-searching-on-github", - "/enterprise/2.15/articles/about-searching-on-github": "/en/enterprise/2.15/user/articles/about-searching-on-github", - "/en/enterprise/2.15/articles/about-ssh": "/en/enterprise/2.15/user/articles/about-ssh", - "/enterprise/2.15/user/articles/about-ssh": "/en/enterprise/2.15/user/articles/about-ssh", - "/enterprise/2.15/articles/about-ssh": "/en/enterprise/2.15/user/articles/about-ssh", - "/en/enterprise/2.15/articles/about-status-checks": "/en/enterprise/2.15/user/articles/about-status-checks", - "/enterprise/2.15/user/articles/about-status-checks": "/en/enterprise/2.15/user/articles/about-status-checks", - "/enterprise/2.15/articles/about-status-checks": "/en/enterprise/2.15/user/articles/about-status-checks", - "/en/enterprise/2.15/articles/about-task-lists": "/en/enterprise/2.15/user/articles/about-task-lists", - "/enterprise/2.15/user/articles/about-task-lists": "/en/enterprise/2.15/user/articles/about-task-lists", - "/enterprise/2.15/articles/about-task-lists": "/en/enterprise/2.15/user/articles/about-task-lists", - "/en/enterprise/2.15/articles/about-team-discussions": "/en/enterprise/2.15/user/articles/about-team-discussions", - "/enterprise/2.15/user/articles/about-team-discussions": "/en/enterprise/2.15/user/articles/about-team-discussions", - "/enterprise/2.15/articles/about-team-discussions": "/en/enterprise/2.15/user/articles/about-team-discussions", - "/en/enterprise/2.15/articles/about-teams": "/en/enterprise/2.15/user/articles/about-teams", - "/enterprise/2.15/user/articles/about-teams": "/en/enterprise/2.15/user/articles/about-teams", - "/enterprise/2.15/articles/about-teams": "/en/enterprise/2.15/user/articles/about-teams", - "/en/enterprise/2.15/articles/about-two-factor-authentication": "/en/enterprise/2.15/user/articles/about-two-factor-authentication", - "/enterprise/2.15/user/articles/about-two-factor-authentication": "/en/enterprise/2.15/user/articles/about-two-factor-authentication", - "/enterprise/2.15/articles/about-two-factor-authentication": "/en/enterprise/2.15/user/articles/about-two-factor-authentication", - "/en/enterprise/2.15/articles/about-web-notifications": "/en/enterprise/2.15/user/articles/about-web-notifications", - "/enterprise/2.15/user/articles/about-web-notifications": "/en/enterprise/2.15/user/articles/about-web-notifications", - "/enterprise/2.15/articles/about-web-notifications": "/en/enterprise/2.15/user/articles/about-web-notifications", - "/en/enterprise/2.15/articles/about-webhooks": "/en/enterprise/2.15/user/articles/about-webhooks", - "/enterprise/2.15/user/articles/about-webhooks": "/en/enterprise/2.15/user/articles/about-webhooks", - "/enterprise/2.15/articles/about-webhooks": "/en/enterprise/2.15/user/articles/about-webhooks", - "/en/enterprise/2.15/articles/about-wikis": "/en/enterprise/2.15/user/articles/about-wikis", - "/enterprise/2.15/user/articles/about-wikis": "/en/enterprise/2.15/user/articles/about-wikis", - "/enterprise/2.15/articles/about-wikis": "/en/enterprise/2.15/user/articles/about-wikis", - "/en/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/enterprise/2.15/user/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/en/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/en/enterprise/2.15/articles/about-your-organization-dashboard": "/en/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/enterprise/2.15/user/articles/about-your-organization-dashboard": "/en/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/enterprise/2.15/articles/about-your-organization-dashboard": "/en/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/en/enterprise/2.15/articles/about-your-organizations-news-feed": "/en/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/enterprise/2.15/user/articles/about-your-organizations-news-feed": "/en/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/enterprise/2.15/articles/about-your-organizations-news-feed": "/en/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/en/enterprise/2.15/articles/about-your-organizations-profile": "/en/enterprise/2.15/user/articles/about-your-organizations-profile", - "/enterprise/2.15/user/articles/about-your-organizations-profile": "/en/enterprise/2.15/user/articles/about-your-organizations-profile", - "/enterprise/2.15/articles/about-your-organizations-profile": "/en/enterprise/2.15/user/articles/about-your-organizations-profile", - "/en/enterprise/2.15/articles/about-your-personal-dashboard": "/en/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/enterprise/2.15/user/articles/about-your-personal-dashboard": "/en/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/enterprise/2.15/articles/about-your-personal-dashboard": "/en/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/en/enterprise/2.15/articles/about-your-profile": "/en/enterprise/2.15/user/articles/about-your-profile", - "/enterprise/2.15/user/articles/about-your-profile": "/en/enterprise/2.15/user/articles/about-your-profile", - "/enterprise/2.15/articles/about-your-profile": "/en/enterprise/2.15/user/articles/about-your-profile", - "/en/enterprise/2.15/articles/access-permissions-on-github": "/en/enterprise/2.15/user/articles/access-permissions-on-github", - "/enterprise/2.15/user/articles/access-permissions-on-github": "/en/enterprise/2.15/user/articles/access-permissions-on-github", - "/enterprise/2.15/articles/access-permissions-on-github": "/en/enterprise/2.15/user/articles/access-permissions-on-github", - "/en/enterprise/2.15/articles/accessing-an-organization": "/en/enterprise/2.15/user/articles/accessing-an-organization", - "/enterprise/2.15/user/articles/accessing-an-organization": "/en/enterprise/2.15/user/articles/accessing-an-organization", - "/enterprise/2.15/articles/accessing-an-organization": "/en/enterprise/2.15/user/articles/accessing-an-organization", - "/en/enterprise/2.15/articles/accessing-basic-repository-data": "/en/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/enterprise/2.15/user/articles/accessing-basic-repository-data": "/en/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/enterprise/2.15/articles/accessing-basic-repository-data": "/en/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/en/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/en/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.15/articles/accessing-your-notifications": "/en/enterprise/2.15/user/articles/accessing-your-notifications", - "/enterprise/2.15/user/articles/accessing-your-notifications": "/en/enterprise/2.15/user/articles/accessing-your-notifications", - "/enterprise/2.15/articles/accessing-your-notifications": "/en/enterprise/2.15/user/articles/accessing-your-notifications", - "/en/enterprise/2.15/articles/accessing-your-organizations-settings": "/en/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/enterprise/2.15/user/articles/accessing-your-organizations-settings": "/en/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/enterprise/2.15/articles/accessing-your-organizations-settings": "/en/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/en/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.15/articles/adding-a-file-to-a-repository": "/en/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/enterprise/2.15/user/articles/adding-a-file-to-a-repository": "/en/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/enterprise/2.15/articles/adding-a-file-to-a-repository": "/en/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/en/enterprise/2.15/articles/adding-a-license-to-a-repository": "/en/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/enterprise/2.15/user/articles/adding-a-license-to-a-repository": "/en/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/enterprise/2.15/articles/adding-a-license-to-a-repository": "/en/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/en/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.15/articles/adding-a-remote": "/en/enterprise/2.15/user/articles/adding-a-remote", - "/enterprise/2.15/user/articles/adding-a-remote": "/en/enterprise/2.15/user/articles/adding-a-remote", - "/enterprise/2.15/articles/adding-a-remote": "/en/enterprise/2.15/user/articles/adding-a-remote", - "/en/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/en/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/en/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.15/articles/adding-notes-to-a-project-board": "/en/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/enterprise/2.15/user/articles/adding-notes-to-a-project-board": "/en/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/enterprise/2.15/articles/adding-notes-to-a-project-board": "/en/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/en/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/enterprise/2.15/user/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/en/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/en/enterprise/2.15/articles/adding-organization-members-to-a-team": "/en/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/enterprise/2.15/user/articles/adding-organization-members-to-a-team": "/en/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/enterprise/2.15/articles/adding-organization-members-to-a-team": "/en/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/en/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.15/articles/adding-people-to-your-organization": "/en/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/enterprise/2.15/user/articles/adding-people-to-your-organization": "/en/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/enterprise/2.15/articles/adding-people-to-your-organization": "/en/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/en/enterprise/2.15/articles/adding-support-resources-to-your-project": "/en/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/enterprise/2.15/user/articles/adding-support-resources-to-your-project": "/en/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/enterprise/2.15/articles/adding-support-resources-to-your-project": "/en/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/en/enterprise/2.15/articles/addressing-merge-conflicts": "/en/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/enterprise/2.15/user/articles/addressing-merge-conflicts": "/en/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/enterprise/2.15/articles/addressing-merge-conflicts": "/en/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/en/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/en/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/en/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.15/articles/archiving-a-github-repository": "/en/enterprise/2.15/user/articles/archiving-a-github-repository", - "/enterprise/2.15/user/articles/archiving-a-github-repository": "/en/enterprise/2.15/user/articles/archiving-a-github-repository", - "/enterprise/2.15/articles/archiving-a-github-repository": "/en/enterprise/2.15/user/articles/archiving-a-github-repository", - "/en/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/en/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/enterprise/2.15/user/articles/archiving-cards-on-a-project-board": "/en/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/en/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/en/enterprise/2.15/articles/archiving-repositories": "/en/enterprise/2.15/user/articles/archiving-repositories", - "/enterprise/2.15/user/articles/archiving-repositories": "/en/enterprise/2.15/user/articles/archiving-repositories", - "/enterprise/2.15/articles/archiving-repositories": "/en/enterprise/2.15/user/articles/archiving-repositories", - "/en/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/en/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.15/articles/associating-text-editors-with-git": "/en/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/enterprise/2.15/user/articles/associating-text-editors-with-git": "/en/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/enterprise/2.15/articles/associating-text-editors-with-git": "/en/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/en/enterprise/2.15/articles/authorizing-oauth-apps": "/en/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/enterprise/2.15/user/articles/authorizing-oauth-apps": "/en/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/enterprise/2.15/articles/authorizing-oauth-apps": "/en/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/en/enterprise/2.15/articles/autolinked-references-and-urls": "/en/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/enterprise/2.15/user/articles/autolinked-references-and-urls": "/en/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/enterprise/2.15/articles/autolinked-references-and-urls": "/en/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/en/enterprise/2.15/articles/backing-up-a-repository": "/en/enterprise/2.15/user/articles/backing-up-a-repository", - "/enterprise/2.15/user/articles/backing-up-a-repository": "/en/enterprise/2.15/user/articles/backing-up-a-repository", - "/enterprise/2.15/articles/backing-up-a-repository": "/en/enterprise/2.15/user/articles/backing-up-a-repository", - "/en/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/en/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/en/enterprise/2.15/articles/be-social": "/en/enterprise/2.15/user/articles/be-social", - "/enterprise/2.15/user/articles/be-social": "/en/enterprise/2.15/user/articles/be-social", - "/enterprise/2.15/articles/be-social": "/en/enterprise/2.15/user/articles/be-social", - "/en/enterprise/2.15/articles/caching-your-github-password-in-git": "/en/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/enterprise/2.15/user/articles/caching-your-github-password-in-git": "/en/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/enterprise/2.15/articles/caching-your-github-password-in-git": "/en/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/en/enterprise/2.15/articles/changing-a-commit-message": "/en/enterprise/2.15/user/articles/changing-a-commit-message", - "/enterprise/2.15/user/articles/changing-a-commit-message": "/en/enterprise/2.15/user/articles/changing-a-commit-message", - "/enterprise/2.15/articles/changing-a-commit-message": "/en/enterprise/2.15/user/articles/changing-a-commit-message", - "/en/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/enterprise/2.15/user/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/en/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/en/enterprise/2.15/articles/changing-a-remotes-url": "/en/enterprise/2.15/user/articles/changing-a-remotes-url", - "/enterprise/2.15/user/articles/changing-a-remotes-url": "/en/enterprise/2.15/user/articles/changing-a-remotes-url", - "/enterprise/2.15/articles/changing-a-remotes-url": "/en/enterprise/2.15/user/articles/changing-a-remotes-url", - "/en/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/enterprise/2.15/user/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/en/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/en/enterprise/2.15/articles/changing-author-info": "/en/enterprise/2.15/user/articles/changing-author-info", - "/enterprise/2.15/user/articles/changing-author-info": "/en/enterprise/2.15/user/articles/changing-author-info", - "/enterprise/2.15/articles/changing-author-info": "/en/enterprise/2.15/user/articles/changing-author-info", - "/en/enterprise/2.15/articles/changing-project-board-visibility": "/en/enterprise/2.15/user/articles/changing-project-board-visibility", - "/enterprise/2.15/user/articles/changing-project-board-visibility": "/en/enterprise/2.15/user/articles/changing-project-board-visibility", - "/enterprise/2.15/articles/changing-project-board-visibility": "/en/enterprise/2.15/user/articles/changing-project-board-visibility", - "/en/enterprise/2.15/articles/changing-team-visibility": "/en/enterprise/2.15/user/articles/changing-team-visibility", - "/enterprise/2.15/user/articles/changing-team-visibility": "/en/enterprise/2.15/user/articles/changing-team-visibility", - "/enterprise/2.15/articles/changing-team-visibility": "/en/enterprise/2.15/user/articles/changing-team-visibility", - "/en/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.15/articles/changing-your-github-username": "/en/enterprise/2.15/user/articles/changing-your-github-username", - "/enterprise/2.15/user/articles/changing-your-github-username": "/en/enterprise/2.15/user/articles/changing-your-github-username", - "/enterprise/2.15/articles/changing-your-github-username": "/en/enterprise/2.15/user/articles/changing-your-github-username", - "/en/enterprise/2.15/articles/changing-your-primary-email-address": "/en/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/enterprise/2.15/user/articles/changing-your-primary-email-address": "/en/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/enterprise/2.15/articles/changing-your-primary-email-address": "/en/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/en/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/enterprise/2.15/user/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/en/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/en/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/enterprise/2.15/user/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/en/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/en/enterprise/2.15/articles/checking-out-pull-requests-locally": "/en/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/enterprise/2.15/user/articles/checking-out-pull-requests-locally": "/en/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/enterprise/2.15/articles/checking-out-pull-requests-locally": "/en/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/en/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.15/articles/classifying-your-repository-with-topics": "/en/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/enterprise/2.15/user/articles/classifying-your-repository-with-topics": "/en/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/enterprise/2.15/articles/classifying-your-repository-with-topics": "/en/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/en/enterprise/2.15/articles/cloning-a-repository-from-github": "/en/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/enterprise/2.15/user/articles/cloning-a-repository-from-github": "/en/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/enterprise/2.15/articles/cloning-a-repository-from-github": "/en/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/en/enterprise/2.15/articles/cloning-a-repository": "/en/enterprise/2.15/user/articles/cloning-a-repository", - "/enterprise/2.15/user/articles/cloning-a-repository": "/en/enterprise/2.15/user/articles/cloning-a-repository", - "/enterprise/2.15/articles/cloning-a-repository": "/en/enterprise/2.15/user/articles/cloning-a-repository", - "/en/enterprise/2.15/articles/closing-a-project-board": "/en/enterprise/2.15/user/articles/closing-a-project-board", - "/enterprise/2.15/user/articles/closing-a-project-board": "/en/enterprise/2.15/user/articles/closing-a-project-board", - "/enterprise/2.15/articles/closing-a-project-board": "/en/enterprise/2.15/user/articles/closing-a-project-board", - "/en/enterprise/2.15/articles/closing-a-pull-request": "/en/enterprise/2.15/user/articles/closing-a-pull-request", - "/enterprise/2.15/user/articles/closing-a-pull-request": "/en/enterprise/2.15/user/articles/closing-a-pull-request", - "/enterprise/2.15/articles/closing-a-pull-request": "/en/enterprise/2.15/user/articles/closing-a-pull-request", - "/en/enterprise/2.15/articles/closing-issues-using-keywords": "/en/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/enterprise/2.15/user/articles/closing-issues-using-keywords": "/en/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/enterprise/2.15/articles/closing-issues-using-keywords": "/en/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/en/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/en/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/en/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/en/enterprise/2.15/articles/collaborating-with-your-team": "/en/enterprise/2.15/user/articles/collaborating-with-your-team", - "/enterprise/2.15/user/articles/collaborating-with-your-team": "/en/enterprise/2.15/user/articles/collaborating-with-your-team", - "/enterprise/2.15/articles/collaborating-with-your-team": "/en/enterprise/2.15/user/articles/collaborating-with-your-team", - "/en/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/en/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/en/enterprise/2.15/articles/commenting-on-a-pull-request": "/en/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/enterprise/2.15/user/articles/commenting-on-a-pull-request": "/en/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/enterprise/2.15/articles/commenting-on-a-pull-request": "/en/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/en/enterprise/2.15/articles/commit-branch-and-tag-labels": "/en/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/enterprise/2.15/user/articles/commit-branch-and-tag-labels": "/en/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/enterprise/2.15/articles/commit-branch-and-tag-labels": "/en/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/en/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.15/articles/comparing-commits-across-time": "/en/enterprise/2.15/user/articles/comparing-commits-across-time", - "/enterprise/2.15/user/articles/comparing-commits-across-time": "/en/enterprise/2.15/user/articles/comparing-commits-across-time", - "/enterprise/2.15/articles/comparing-commits-across-time": "/en/enterprise/2.15/user/articles/comparing-commits-across-time", - "/en/enterprise/2.15/articles/conditions-for-large-files": "/en/enterprise/2.15/user/articles/conditions-for-large-files", - "/enterprise/2.15/user/articles/conditions-for-large-files": "/en/enterprise/2.15/user/articles/conditions-for-large-files", - "/enterprise/2.15/articles/conditions-for-large-files": "/en/enterprise/2.15/user/articles/conditions-for-large-files", - "/en/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/en/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/en/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/en/enterprise/2.15/articles/configuring-automation-for-project-boards": "/en/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/enterprise/2.15/user/articles/configuring-automation-for-project-boards": "/en/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/enterprise/2.15/articles/configuring-automation-for-project-boards": "/en/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/en/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.15/articles/configuring-git-large-file-storage": "/en/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/enterprise/2.15/user/articles/configuring-git-large-file-storage": "/en/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/enterprise/2.15/articles/configuring-git-large-file-storage": "/en/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/en/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/en/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings": "/en/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/en/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/en/enterprise/2.15/articles/configuring-protected-branches": "/en/enterprise/2.15/user/articles/configuring-protected-branches", - "/enterprise/2.15/user/articles/configuring-protected-branches": "/en/enterprise/2.15/user/articles/configuring-protected-branches", - "/enterprise/2.15/articles/configuring-protected-branches": "/en/enterprise/2.15/user/articles/configuring-protected-branches", - "/en/enterprise/2.15/articles/configuring-pull-request-merges": "/en/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/enterprise/2.15/user/articles/configuring-pull-request-merges": "/en/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/enterprise/2.15/articles/configuring-pull-request-merges": "/en/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/en/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.15/articles/configuring-two-factor-authentication": "/en/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/enterprise/2.15/user/articles/configuring-two-factor-authentication": "/en/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/enterprise/2.15/articles/configuring-two-factor-authentication": "/en/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/en/enterprise/2.15/articles/connecting-to-github-with-ssh": "/en/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/enterprise/2.15/user/articles/connecting-to-github-with-ssh": "/en/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/enterprise/2.15/articles/connecting-to-github-with-ssh": "/en/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/en/enterprise/2.15/articles/connecting-with-third-party-applications": "/en/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/enterprise/2.15/user/articles/connecting-with-third-party-applications": "/en/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/enterprise/2.15/articles/connecting-with-third-party-applications": "/en/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/en/enterprise/2.15/articles/converting-a-user-into-an-organization": "/en/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/enterprise/2.15/user/articles/converting-a-user-into-an-organization": "/en/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/enterprise/2.15/articles/converting-a-user-into-an-organization": "/en/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/en/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/en/enterprise/2.15/articles/converting-an-organization-into-a-user": "/en/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/enterprise/2.15/user/articles/converting-an-organization-into-a-user": "/en/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/enterprise/2.15/articles/converting-an-organization-into-a-user": "/en/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/en/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/en/enterprise/2.15/articles/create-a-repo": "/en/enterprise/2.15/user/articles/create-a-repo", - "/enterprise/2.15/user/articles/create-a-repo": "/en/enterprise/2.15/user/articles/create-a-repo", - "/enterprise/2.15/articles/create-a-repo": "/en/enterprise/2.15/user/articles/create-a-repo", - "/en/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/en/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/en/enterprise/2.15/articles/creating-a-github-pages-site": "/en/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/enterprise/2.15/user/articles/creating-a-github-pages-site": "/en/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/enterprise/2.15/articles/creating-a-github-pages-site": "/en/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/en/enterprise/2.15/articles/creating-a-label": "/en/enterprise/2.15/user/articles/creating-a-label", - "/enterprise/2.15/user/articles/creating-a-label": "/en/enterprise/2.15/user/articles/creating-a-label", - "/enterprise/2.15/articles/creating-a-label": "/en/enterprise/2.15/user/articles/creating-a-label", - "/en/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/en/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/en/enterprise/2.15/articles/creating-a-new-repository": "/en/enterprise/2.15/user/articles/creating-a-new-repository", - "/enterprise/2.15/user/articles/creating-a-new-repository": "/en/enterprise/2.15/user/articles/creating-a-new-repository", - "/enterprise/2.15/articles/creating-a-new-repository": "/en/enterprise/2.15/user/articles/creating-a-new-repository", - "/en/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.15/articles/creating-a-project-board": "/en/enterprise/2.15/user/articles/creating-a-project-board", - "/enterprise/2.15/user/articles/creating-a-project-board": "/en/enterprise/2.15/user/articles/creating-a-project-board", - "/enterprise/2.15/articles/creating-a-project-board": "/en/enterprise/2.15/user/articles/creating-a-project-board", - "/en/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/en/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.15/articles/creating-a-pull-request": "/en/enterprise/2.15/user/articles/creating-a-pull-request", - "/enterprise/2.15/user/articles/creating-a-pull-request": "/en/enterprise/2.15/user/articles/creating-a-pull-request", - "/enterprise/2.15/articles/creating-a-pull-request": "/en/enterprise/2.15/user/articles/creating-a-pull-request", - "/en/enterprise/2.15/articles/creating-a-repository-on-github": "/en/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/enterprise/2.15/user/articles/creating-a-repository-on-github": "/en/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/enterprise/2.15/articles/creating-a-repository-on-github": "/en/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/en/enterprise/2.15/articles/creating-a-saved-reply": "/en/enterprise/2.15/user/articles/creating-a-saved-reply", - "/enterprise/2.15/user/articles/creating-a-saved-reply": "/en/enterprise/2.15/user/articles/creating-a-saved-reply", - "/enterprise/2.15/articles/creating-a-saved-reply": "/en/enterprise/2.15/user/articles/creating-a-saved-reply", - "/en/enterprise/2.15/articles/creating-a-strong-password": "/en/enterprise/2.15/user/articles/creating-a-strong-password", - "/enterprise/2.15/user/articles/creating-a-strong-password": "/en/enterprise/2.15/user/articles/creating-a-strong-password", - "/enterprise/2.15/articles/creating-a-strong-password": "/en/enterprise/2.15/user/articles/creating-a-strong-password", - "/en/enterprise/2.15/articles/creating-a-team-discussion": "/en/enterprise/2.15/user/articles/creating-a-team-discussion", - "/enterprise/2.15/user/articles/creating-a-team-discussion": "/en/enterprise/2.15/user/articles/creating-a-team-discussion", - "/enterprise/2.15/articles/creating-a-team-discussion": "/en/enterprise/2.15/user/articles/creating-a-team-discussion", - "/en/enterprise/2.15/articles/creating-a-team": "/en/enterprise/2.15/user/articles/creating-a-team", - "/enterprise/2.15/user/articles/creating-a-team": "/en/enterprise/2.15/user/articles/creating-a-team", - "/enterprise/2.15/articles/creating-a-team": "/en/enterprise/2.15/user/articles/creating-a-team", - "/en/enterprise/2.15/articles/creating-an-issue": "/en/enterprise/2.15/user/articles/creating-an-issue", - "/enterprise/2.15/user/articles/creating-an-issue": "/en/enterprise/2.15/user/articles/creating-an-issue", - "/enterprise/2.15/articles/creating-an-issue": "/en/enterprise/2.15/user/articles/creating-an-issue", - "/en/enterprise/2.15/articles/creating-an-issues-only-repository": "/en/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/enterprise/2.15/user/articles/creating-an-issues-only-repository": "/en/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/enterprise/2.15/articles/creating-an-issues-only-repository": "/en/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/en/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.15/articles/creating-and-editing-commits": "/en/enterprise/2.15/user/articles/creating-and-editing-commits", - "/enterprise/2.15/user/articles/creating-and-editing-commits": "/en/enterprise/2.15/user/articles/creating-and-editing-commits", - "/enterprise/2.15/articles/creating-and-editing-commits": "/en/enterprise/2.15/user/articles/creating-and-editing-commits", - "/en/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/en/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/en/enterprise/2.15/articles/creating-gists": "/en/enterprise/2.15/user/articles/creating-gists", - "/enterprise/2.15/user/articles/creating-gists": "/en/enterprise/2.15/user/articles/creating-gists", - "/enterprise/2.15/articles/creating-gists": "/en/enterprise/2.15/user/articles/creating-gists", - "/en/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/en/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository": "/en/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/en/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/en/enterprise/2.15/articles/creating-new-files": "/en/enterprise/2.15/user/articles/creating-new-files", - "/enterprise/2.15/user/articles/creating-new-files": "/en/enterprise/2.15/user/articles/creating-new-files", - "/enterprise/2.15/articles/creating-new-files": "/en/enterprise/2.15/user/articles/creating-new-files", - "/en/enterprise/2.15/articles/creating-releases": "/en/enterprise/2.15/user/articles/creating-releases", - "/enterprise/2.15/user/articles/creating-releases": "/en/enterprise/2.15/user/articles/creating-releases", - "/enterprise/2.15/articles/creating-releases": "/en/enterprise/2.15/user/articles/creating-releases", - "/en/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.15/articles/customizing-your-profile": "/en/enterprise/2.15/user/articles/customizing-your-profile", - "/enterprise/2.15/user/articles/customizing-your-profile": "/en/enterprise/2.15/user/articles/customizing-your-profile", - "/enterprise/2.15/articles/customizing-your-profile": "/en/enterprise/2.15/user/articles/customizing-your-profile", - "/en/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/en/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.15/articles/deleting-a-label": "/en/enterprise/2.15/user/articles/deleting-a-label", - "/enterprise/2.15/user/articles/deleting-a-label": "/en/enterprise/2.15/user/articles/deleting-a-label", - "/enterprise/2.15/articles/deleting-a-label": "/en/enterprise/2.15/user/articles/deleting-a-label", - "/en/enterprise/2.15/articles/deleting-a-project-board": "/en/enterprise/2.15/user/articles/deleting-a-project-board", - "/enterprise/2.15/user/articles/deleting-a-project-board": "/en/enterprise/2.15/user/articles/deleting-a-project-board", - "/enterprise/2.15/articles/deleting-a-project-board": "/en/enterprise/2.15/user/articles/deleting-a-project-board", - "/en/enterprise/2.15/articles/deleting-a-repository": "/en/enterprise/2.15/user/articles/deleting-a-repository", - "/enterprise/2.15/user/articles/deleting-a-repository": "/en/enterprise/2.15/user/articles/deleting-a-repository", - "/enterprise/2.15/articles/deleting-a-repository": "/en/enterprise/2.15/user/articles/deleting-a-repository", - "/en/enterprise/2.15/articles/deleting-a-saved-reply": "/en/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/enterprise/2.15/user/articles/deleting-a-saved-reply": "/en/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/enterprise/2.15/articles/deleting-a-saved-reply": "/en/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/en/enterprise/2.15/articles/deleting-a-team": "/en/enterprise/2.15/user/articles/deleting-a-team", - "/enterprise/2.15/user/articles/deleting-a-team": "/en/enterprise/2.15/user/articles/deleting-a-team", - "/enterprise/2.15/articles/deleting-a-team": "/en/enterprise/2.15/user/articles/deleting-a-team", - "/en/enterprise/2.15/articles/deleting-an-organization-account": "/en/enterprise/2.15/user/articles/deleting-an-organization-account", - "/enterprise/2.15/user/articles/deleting-an-organization-account": "/en/enterprise/2.15/user/articles/deleting-an-organization-account", - "/enterprise/2.15/articles/deleting-an-organization-account": "/en/enterprise/2.15/user/articles/deleting-an-organization-account", - "/en/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.15/articles/deleting-files": "/en/enterprise/2.15/user/articles/deleting-files", - "/enterprise/2.15/user/articles/deleting-files": "/en/enterprise/2.15/user/articles/deleting-files", - "/enterprise/2.15/articles/deleting-files": "/en/enterprise/2.15/user/articles/deleting-files", - "/en/enterprise/2.15/articles/deleting-your-user-account": "/en/enterprise/2.15/user/articles/deleting-your-user-account", - "/enterprise/2.15/user/articles/deleting-your-user-account": "/en/enterprise/2.15/user/articles/deleting-your-user-account", - "/enterprise/2.15/articles/deleting-your-user-account": "/en/enterprise/2.15/user/articles/deleting-your-user-account", - "/en/enterprise/2.15/articles/differences-between-commit-views": "/en/enterprise/2.15/user/articles/differences-between-commit-views", - "/enterprise/2.15/user/articles/differences-between-commit-views": "/en/enterprise/2.15/user/articles/differences-between-commit-views", - "/enterprise/2.15/articles/differences-between-commit-views": "/en/enterprise/2.15/user/articles/differences-between-commit-views", - "/en/enterprise/2.15/articles/disabling-issues": "/en/enterprise/2.15/user/articles/disabling-issues", - "/enterprise/2.15/user/articles/disabling-issues": "/en/enterprise/2.15/user/articles/disabling-issues", - "/enterprise/2.15/articles/disabling-issues": "/en/enterprise/2.15/user/articles/disabling-issues", - "/en/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/en/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/en/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/en/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/en/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/en/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.15/articles/disabling-wikis": "/en/enterprise/2.15/user/articles/disabling-wikis", - "/enterprise/2.15/user/articles/disabling-wikis": "/en/enterprise/2.15/user/articles/disabling-wikis", - "/enterprise/2.15/articles/disabling-wikis": "/en/enterprise/2.15/user/articles/disabling-wikis", - "/en/enterprise/2.15/articles/dismissing-a-pull-request-review": "/en/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/enterprise/2.15/user/articles/dismissing-a-pull-request-review": "/en/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/enterprise/2.15/articles/dismissing-a-pull-request-review": "/en/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/en/enterprise/2.15/articles/distributing-large-binaries": "/en/enterprise/2.15/user/articles/distributing-large-binaries", - "/enterprise/2.15/user/articles/distributing-large-binaries": "/en/enterprise/2.15/user/articles/distributing-large-binaries", - "/enterprise/2.15/articles/distributing-large-binaries": "/en/enterprise/2.15/user/articles/distributing-large-binaries", - "/en/enterprise/2.15/articles/documenting-your-project-with-wikis": "/en/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/enterprise/2.15/user/articles/documenting-your-project-with-wikis": "/en/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/enterprise/2.15/articles/documenting-your-project-with-wikis": "/en/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/en/enterprise/2.15/articles/duplicating-a-repository": "/en/enterprise/2.15/user/articles/duplicating-a-repository", - "/enterprise/2.15/user/articles/duplicating-a-repository": "/en/enterprise/2.15/user/articles/duplicating-a-repository", - "/enterprise/2.15/articles/duplicating-a-repository": "/en/enterprise/2.15/user/articles/duplicating-a-repository", - "/en/enterprise/2.15/articles/editing-a-label": "/en/enterprise/2.15/user/articles/editing-a-label", - "/enterprise/2.15/user/articles/editing-a-label": "/en/enterprise/2.15/user/articles/editing-a-label", - "/enterprise/2.15/articles/editing-a-label": "/en/enterprise/2.15/user/articles/editing-a-label", - "/en/enterprise/2.15/articles/editing-a-project-board": "/en/enterprise/2.15/user/articles/editing-a-project-board", - "/enterprise/2.15/user/articles/editing-a-project-board": "/en/enterprise/2.15/user/articles/editing-a-project-board", - "/enterprise/2.15/articles/editing-a-project-board": "/en/enterprise/2.15/user/articles/editing-a-project-board", - "/en/enterprise/2.15/articles/editing-a-saved-reply": "/en/enterprise/2.15/user/articles/editing-a-saved-reply", - "/enterprise/2.15/user/articles/editing-a-saved-reply": "/en/enterprise/2.15/user/articles/editing-a-saved-reply", - "/enterprise/2.15/articles/editing-a-saved-reply": "/en/enterprise/2.15/user/articles/editing-a-saved-reply", - "/en/enterprise/2.15/articles/editing-and-deleting-releases": "/en/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/enterprise/2.15/user/articles/editing-and-deleting-releases": "/en/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/enterprise/2.15/articles/editing-and-deleting-releases": "/en/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/en/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/en/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists": "/en/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/en/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/en/enterprise/2.15/articles/editing-files-in-another-users-repository": "/en/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/enterprise/2.15/user/articles/editing-files-in-another-users-repository": "/en/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/enterprise/2.15/articles/editing-files-in-another-users-repository": "/en/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/en/enterprise/2.15/articles/editing-files-in-your-repository": "/en/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/enterprise/2.15/user/articles/editing-files-in-your-repository": "/en/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/enterprise/2.15/articles/editing-files-in-your-repository": "/en/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/en/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/en/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.15/articles/editing-wiki-content": "/en/enterprise/2.15/user/articles/editing-wiki-content", - "/enterprise/2.15/user/articles/editing-wiki-content": "/en/enterprise/2.15/user/articles/editing-wiki-content", - "/enterprise/2.15/articles/editing-wiki-content": "/en/enterprise/2.15/user/articles/editing-wiki-content", - "/en/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.15/articles/enabling-branch-restrictions": "/en/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/enterprise/2.15/user/articles/enabling-branch-restrictions": "/en/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/enterprise/2.15/articles/enabling-branch-restrictions": "/en/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/en/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/en/enterprise/2.15/articles/enabling-required-commit-signing": "/en/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/enterprise/2.15/user/articles/enabling-required-commit-signing": "/en/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/enterprise/2.15/articles/enabling-required-commit-signing": "/en/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/en/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.15/articles/enabling-required-status-checks": "/en/enterprise/2.15/user/articles/enabling-required-status-checks", - "/enterprise/2.15/user/articles/enabling-required-status-checks": "/en/enterprise/2.15/user/articles/enabling-required-status-checks", - "/enterprise/2.15/articles/enabling-required-status-checks": "/en/enterprise/2.15/user/articles/enabling-required-status-checks", - "/en/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/en/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.15/articles/error-bad-file-number": "/en/enterprise/2.15/user/articles/error-bad-file-number", - "/enterprise/2.15/user/articles/error-bad-file-number": "/en/enterprise/2.15/user/articles/error-bad-file-number", - "/enterprise/2.15/articles/error-bad-file-number": "/en/enterprise/2.15/user/articles/error-bad-file-number", - "/en/enterprise/2.15/articles/error-key-already-in-use": "/en/enterprise/2.15/user/articles/error-key-already-in-use", - "/enterprise/2.15/user/articles/error-key-already-in-use": "/en/enterprise/2.15/user/articles/error-key-already-in-use", - "/enterprise/2.15/articles/error-key-already-in-use": "/en/enterprise/2.15/user/articles/error-key-already-in-use", - "/en/enterprise/2.15/articles/error-permission-denied-publickey": "/en/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/enterprise/2.15/user/articles/error-permission-denied-publickey": "/en/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/enterprise/2.15/articles/error-permission-denied-publickey": "/en/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/en/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.15/articles/error-repository-not-found": "/en/enterprise/2.15/user/articles/error-repository-not-found", - "/enterprise/2.15/user/articles/error-repository-not-found": "/en/enterprise/2.15/user/articles/error-repository-not-found", - "/enterprise/2.15/articles/error-repository-not-found": "/en/enterprise/2.15/user/articles/error-repository-not-found", - "/en/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/en/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/en/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.15/articles/exploring-projects-on-github": "/en/enterprise/2.15/user/articles/exploring-projects-on-github", - "/enterprise/2.15/user/articles/exploring-projects-on-github": "/en/enterprise/2.15/user/articles/exploring-projects-on-github", - "/enterprise/2.15/articles/exploring-projects-on-github": "/en/enterprise/2.15/user/articles/exploring-projects-on-github", - "/en/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/enterprise/2.15/user/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/en/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/en/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/en/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/en/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/en/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.15/articles/finding-files-on-github": "/en/enterprise/2.15/user/articles/finding-files-on-github", - "/enterprise/2.15/user/articles/finding-files-on-github": "/en/enterprise/2.15/user/articles/finding-files-on-github", - "/enterprise/2.15/articles/finding-files-on-github": "/en/enterprise/2.15/user/articles/finding-files-on-github", - "/en/enterprise/2.15/articles/finding-information-in-a-repository": "/en/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/enterprise/2.15/user/articles/finding-information-in-a-repository": "/en/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/enterprise/2.15/articles/finding-information-in-a-repository": "/en/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/en/enterprise/2.15/articles/following-people": "/en/enterprise/2.15/user/articles/following-people", - "/enterprise/2.15/user/articles/following-people": "/en/enterprise/2.15/user/articles/following-people", - "/enterprise/2.15/articles/following-people": "/en/enterprise/2.15/user/articles/following-people", - "/en/enterprise/2.15/articles/fork-a-repo": "/en/enterprise/2.15/user/articles/fork-a-repo", - "/enterprise/2.15/user/articles/fork-a-repo": "/en/enterprise/2.15/user/articles/fork-a-repo", - "/enterprise/2.15/articles/fork-a-repo": "/en/enterprise/2.15/user/articles/fork-a-repo", - "/en/enterprise/2.15/articles/forking-and-cloning-gists": "/en/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/enterprise/2.15/user/articles/forking-and-cloning-gists": "/en/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/enterprise/2.15/articles/forking-and-cloning-gists": "/en/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/en/enterprise/2.15/articles/generating-a-new-gpg-key": "/en/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/enterprise/2.15/user/articles/generating-a-new-gpg-key": "/en/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/enterprise/2.15/articles/generating-a-new-gpg-key": "/en/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/en/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/en/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository": "/en/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/en/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/en/enterprise/2.15/articles/getting-permanent-links-to-files": "/en/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/enterprise/2.15/user/articles/getting-permanent-links-to-files": "/en/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/enterprise/2.15/articles/getting-permanent-links-to-files": "/en/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/en/enterprise/2.15/articles/getting-started-with-git-and-github": "/en/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/enterprise/2.15/user/articles/getting-started-with-git-and-github": "/en/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/enterprise/2.15/articles/getting-started-with-git-and-github": "/en/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/en/enterprise/2.15/articles/getting-started-with-github-pages": "/en/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/enterprise/2.15/user/articles/getting-started-with-github-pages": "/en/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/enterprise/2.15/articles/getting-started-with-github-pages": "/en/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/en/enterprise/2.15/articles/getting-started-with-notifications": "/en/enterprise/2.15/user/articles/getting-started-with-notifications", - "/enterprise/2.15/user/articles/getting-started-with-notifications": "/en/enterprise/2.15/user/articles/getting-started-with-notifications", - "/enterprise/2.15/articles/getting-started-with-notifications": "/en/enterprise/2.15/user/articles/getting-started-with-notifications", - "/en/enterprise/2.15/articles/getting-started-with-searching-on-github": "/en/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/enterprise/2.15/user/articles/getting-started-with-searching-on-github": "/en/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/enterprise/2.15/articles/getting-started-with-searching-on-github": "/en/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/en/enterprise/2.15/articles/getting-started-with-the-api": "/en/enterprise/2.15/user/articles/getting-started-with-the-api", - "/enterprise/2.15/user/articles/getting-started-with-the-api": "/en/enterprise/2.15/user/articles/getting-started-with-the-api", - "/enterprise/2.15/articles/getting-started-with-the-api": "/en/enterprise/2.15/user/articles/getting-started-with-the-api", - "/en/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/en/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/en/enterprise/2.15/articles/git-and-github-learning-resources": "/en/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/enterprise/2.15/user/articles/git-and-github-learning-resources": "/en/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/enterprise/2.15/articles/git-and-github-learning-resources": "/en/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/en/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/enterprise/2.15/user/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/en/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/en/enterprise/2.15/articles/git-cheatsheet": "/en/enterprise/2.15/user/articles/git-cheatsheet", - "/enterprise/2.15/user/articles/git-cheatsheet": "/en/enterprise/2.15/user/articles/git-cheatsheet", - "/enterprise/2.15/articles/git-cheatsheet": "/en/enterprise/2.15/user/articles/git-cheatsheet", - "/en/enterprise/2.15/articles/git-workflows": "/en/enterprise/2.15/user/articles/git-workflows", - "/enterprise/2.15/user/articles/git-workflows": "/en/enterprise/2.15/user/articles/git-workflows", - "/enterprise/2.15/articles/git-workflows": "/en/enterprise/2.15/user/articles/git-workflows", - "/en/enterprise/2.15/articles/github-flow": "/en/enterprise/2.15/user/articles/github-flow", - "/enterprise/2.15/user/articles/github-flow": "/en/enterprise/2.15/user/articles/github-flow", - "/enterprise/2.15/articles/github-flow": "/en/enterprise/2.15/user/articles/github-flow", - "/en/enterprise/2.15/articles/github-glossary": "/en/enterprise/2.15/user/articles/github-glossary", - "/enterprise/2.15/user/articles/github-glossary": "/en/enterprise/2.15/user/articles/github-glossary", - "/enterprise/2.15/articles/github-glossary": "/en/enterprise/2.15/user/articles/github-glossary", - "/en/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.15/articles/https-cloning-errors": "/en/enterprise/2.15/user/articles/https-cloning-errors", - "/enterprise/2.15/user/articles/https-cloning-errors": "/en/enterprise/2.15/user/articles/https-cloning-errors", - "/enterprise/2.15/articles/https-cloning-errors": "/en/enterprise/2.15/user/articles/https-cloning-errors", - "/en/enterprise/2.15/articles/ignoring-files": "/en/enterprise/2.15/user/articles/ignoring-files", - "/enterprise/2.15/user/articles/ignoring-files": "/en/enterprise/2.15/user/articles/ignoring-files", - "/enterprise/2.15/articles/ignoring-files": "/en/enterprise/2.15/user/articles/ignoring-files", - "/en/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.15/articles/importing-source-code-to-github": "/en/enterprise/2.15/user/articles/importing-source-code-to-github", - "/enterprise/2.15/user/articles/importing-source-code-to-github": "/en/enterprise/2.15/user/articles/importing-source-code-to-github", - "/enterprise/2.15/articles/importing-source-code-to-github": "/en/enterprise/2.15/user/articles/importing-source-code-to-github", - "/en/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/en/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/en/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/en/enterprise/2.15/articles/installing-git-large-file-storage": "/en/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/enterprise/2.15/user/articles/installing-git-large-file-storage": "/en/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/enterprise/2.15/articles/installing-git-large-file-storage": "/en/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/en/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/en/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/enterprise/2.15/user/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/en/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/en/enterprise/2.15/articles/keeping-your-organization-secure": "/en/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/enterprise/2.15/user/articles/keeping-your-organization-secure": "/en/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/enterprise/2.15/articles/keeping-your-organization-secure": "/en/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/en/enterprise/2.15/articles/keyboard-shortcuts": "/en/enterprise/2.15/user/articles/keyboard-shortcuts", - "/enterprise/2.15/user/articles/keyboard-shortcuts": "/en/enterprise/2.15/user/articles/keyboard-shortcuts", - "/enterprise/2.15/articles/keyboard-shortcuts": "/en/enterprise/2.15/user/articles/keyboard-shortcuts", - "/en/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/enterprise/2.15/user/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/en/enterprise/2.15/articles/learning-about-git": "/en/enterprise/2.15/user/articles/learning-about-git", - "/enterprise/2.15/user/articles/learning-about-git": "/en/enterprise/2.15/user/articles/learning-about-git", - "/enterprise/2.15/articles/learning-about-git": "/en/enterprise/2.15/user/articles/learning-about-git", - "/en/enterprise/2.15/articles/learning-about-github": "/en/enterprise/2.15/user/articles/learning-about-github", - "/enterprise/2.15/user/articles/learning-about-github": "/en/enterprise/2.15/user/articles/learning-about-github", - "/enterprise/2.15/articles/learning-about-github": "/en/enterprise/2.15/user/articles/learning-about-github", - "/en/enterprise/2.15/articles/licensing-a-repository": "/en/enterprise/2.15/user/articles/licensing-a-repository", - "/enterprise/2.15/user/articles/licensing-a-repository": "/en/enterprise/2.15/user/articles/licensing-a-repository", - "/enterprise/2.15/articles/licensing-a-repository": "/en/enterprise/2.15/user/articles/licensing-a-repository", - "/en/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/en/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board": "/en/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/en/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/en/enterprise/2.15/articles/linking-to-releases": "/en/enterprise/2.15/user/articles/linking-to-releases", - "/enterprise/2.15/user/articles/linking-to-releases": "/en/enterprise/2.15/user/articles/linking-to-releases", - "/enterprise/2.15/articles/linking-to-releases": "/en/enterprise/2.15/user/articles/linking-to-releases", - "/en/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/enterprise/2.15/user/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/en/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/en/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/enterprise/2.15/user/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/en/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/en/enterprise/2.15/articles/locking-conversations": "/en/enterprise/2.15/user/articles/locking-conversations", - "/enterprise/2.15/user/articles/locking-conversations": "/en/enterprise/2.15/user/articles/locking-conversations", - "/enterprise/2.15/articles/locking-conversations": "/en/enterprise/2.15/user/articles/locking-conversations", - "/en/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/en/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/en/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/en/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/en/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/en/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/en/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.15/articles/managing-branches-in-your-repository": "/en/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/enterprise/2.15/user/articles/managing-branches-in-your-repository": "/en/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/enterprise/2.15/articles/managing-branches-in-your-repository": "/en/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/en/enterprise/2.15/articles/managing-commit-signature-verification": "/en/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/enterprise/2.15/user/articles/managing-commit-signature-verification": "/en/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/enterprise/2.15/articles/managing-commit-signature-verification": "/en/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/en/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.15/articles/managing-disruptive-comments": "/en/enterprise/2.15/user/articles/managing-disruptive-comments", - "/enterprise/2.15/user/articles/managing-disruptive-comments": "/en/enterprise/2.15/user/articles/managing-disruptive-comments", - "/enterprise/2.15/articles/managing-disruptive-comments": "/en/enterprise/2.15/user/articles/managing-disruptive-comments", - "/en/enterprise/2.15/articles/managing-email-preferences": "/en/enterprise/2.15/user/articles/managing-email-preferences", - "/enterprise/2.15/user/articles/managing-email-preferences": "/en/enterprise/2.15/user/articles/managing-email-preferences", - "/enterprise/2.15/articles/managing-email-preferences": "/en/enterprise/2.15/user/articles/managing-email-preferences", - "/en/enterprise/2.15/articles/managing-files-on-github": "/en/enterprise/2.15/user/articles/managing-files-on-github", - "/enterprise/2.15/user/articles/managing-files-on-github": "/en/enterprise/2.15/user/articles/managing-files-on-github", - "/enterprise/2.15/articles/managing-files-on-github": "/en/enterprise/2.15/user/articles/managing-files-on-github", - "/en/enterprise/2.15/articles/managing-files-using-the-command-line": "/en/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/enterprise/2.15/user/articles/managing-files-using-the-command-line": "/en/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/enterprise/2.15/articles/managing-files-using-the-command-line": "/en/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/en/enterprise/2.15/articles/managing-membership-in-your-organization": "/en/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/enterprise/2.15/user/articles/managing-membership-in-your-organization": "/en/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/enterprise/2.15/articles/managing-membership-in-your-organization": "/en/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/en/enterprise/2.15/articles/managing-organization-settings": "/en/enterprise/2.15/user/articles/managing-organization-settings", - "/enterprise/2.15/user/articles/managing-organization-settings": "/en/enterprise/2.15/user/articles/managing-organization-settings", - "/enterprise/2.15/articles/managing-organization-settings": "/en/enterprise/2.15/user/articles/managing-organization-settings", - "/en/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.15/articles/managing-project-boards": "/en/enterprise/2.15/user/articles/managing-project-boards", - "/enterprise/2.15/user/articles/managing-project-boards": "/en/enterprise/2.15/user/articles/managing-project-boards", - "/enterprise/2.15/articles/managing-project-boards": "/en/enterprise/2.15/user/articles/managing-project-boards", - "/en/enterprise/2.15/articles/managing-releases-in-a-repository": "/en/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/enterprise/2.15/user/articles/managing-releases-in-a-repository": "/en/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/enterprise/2.15/articles/managing-releases-in-a-repository": "/en/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/en/enterprise/2.15/articles/managing-remote-repositories": "/en/enterprise/2.15/user/articles/managing-remote-repositories", - "/enterprise/2.15/user/articles/managing-remote-repositories": "/en/enterprise/2.15/user/articles/managing-remote-repositories", - "/enterprise/2.15/articles/managing-remote-repositories": "/en/enterprise/2.15/user/articles/managing-remote-repositories", - "/en/enterprise/2.15/articles/managing-repository-settings": "/en/enterprise/2.15/user/articles/managing-repository-settings", - "/enterprise/2.15/user/articles/managing-repository-settings": "/en/enterprise/2.15/user/articles/managing-repository-settings", - "/enterprise/2.15/articles/managing-repository-settings": "/en/enterprise/2.15/user/articles/managing-repository-settings", - "/en/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/en/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/en/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.15/articles/managing-user-account-settings": "/en/enterprise/2.15/user/articles/managing-user-account-settings", - "/enterprise/2.15/user/articles/managing-user-account-settings": "/en/enterprise/2.15/user/articles/managing-user-account-settings", - "/enterprise/2.15/articles/managing-user-account-settings": "/en/enterprise/2.15/user/articles/managing-user-account-settings", - "/en/enterprise/2.15/articles/managing-your-membership-in-organizations": "/en/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/enterprise/2.15/user/articles/managing-your-membership-in-organizations": "/en/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/enterprise/2.15/articles/managing-your-membership-in-organizations": "/en/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/en/enterprise/2.15/articles/managing-your-notifications": "/en/enterprise/2.15/user/articles/managing-your-notifications", - "/enterprise/2.15/user/articles/managing-your-notifications": "/en/enterprise/2.15/user/articles/managing-your-notifications", - "/enterprise/2.15/articles/managing-your-notifications": "/en/enterprise/2.15/user/articles/managing-your-notifications", - "/en/enterprise/2.15/articles/managing-your-work-with-issues": "/en/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/enterprise/2.15/user/articles/managing-your-work-with-issues": "/en/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/enterprise/2.15/articles/managing-your-work-with-issues": "/en/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/en/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.15/articles/mapping-geojson-files-on-github": "/en/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/enterprise/2.15/user/articles/mapping-geojson-files-on-github": "/en/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/enterprise/2.15/articles/mapping-geojson-files-on-github": "/en/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/en/enterprise/2.15/articles/marking-notifications-as-read": "/en/enterprise/2.15/user/articles/marking-notifications-as-read", - "/enterprise/2.15/user/articles/marking-notifications-as-read": "/en/enterprise/2.15/user/articles/marking-notifications-as-read", - "/enterprise/2.15/articles/marking-notifications-as-read": "/en/enterprise/2.15/user/articles/marking-notifications-as-read", - "/en/enterprise/2.15/articles/merging-a-pull-request": "/en/enterprise/2.15/user/articles/merging-a-pull-request", - "/enterprise/2.15/user/articles/merging-a-pull-request": "/en/enterprise/2.15/user/articles/merging-a-pull-request", - "/enterprise/2.15/articles/merging-a-pull-request": "/en/enterprise/2.15/user/articles/merging-a-pull-request", - "/en/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/en/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/en/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/en/enterprise/2.15/articles/moderating-comments-and-conversations": "/en/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/enterprise/2.15/user/articles/moderating-comments-and-conversations": "/en/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/enterprise/2.15/articles/moderating-comments-and-conversations": "/en/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/en/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/enterprise/2.15/user/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/en/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/en/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.15/articles/opening-an-issue-from-code": "/en/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/enterprise/2.15/user/articles/opening-an-issue-from-code": "/en/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/enterprise/2.15/articles/opening-an-issue-from-code": "/en/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/en/enterprise/2.15/articles/organizing-information-with-tables": "/en/enterprise/2.15/user/articles/organizing-information-with-tables", - "/enterprise/2.15/user/articles/organizing-information-with-tables": "/en/enterprise/2.15/user/articles/organizing-information-with-tables", - "/enterprise/2.15/articles/organizing-information-with-tables": "/en/enterprise/2.15/user/articles/organizing-information-with-tables", - "/en/enterprise/2.15/articles/organizing-members-into-teams": "/en/enterprise/2.15/user/articles/organizing-members-into-teams", - "/enterprise/2.15/user/articles/organizing-members-into-teams": "/en/enterprise/2.15/user/articles/organizing-members-into-teams", - "/enterprise/2.15/articles/organizing-members-into-teams": "/en/enterprise/2.15/user/articles/organizing-members-into-teams", - "/en/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/en/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.15/articles/permission-levels-for-an-organization": "/en/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/enterprise/2.15/user/articles/permission-levels-for-an-organization": "/en/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/enterprise/2.15/articles/permission-levels-for-an-organization": "/en/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/en/enterprise/2.15/articles/personalizing-your-profile": "/en/enterprise/2.15/user/articles/personalizing-your-profile", - "/enterprise/2.15/user/articles/personalizing-your-profile": "/en/enterprise/2.15/user/articles/personalizing-your-profile", - "/enterprise/2.15/articles/personalizing-your-profile": "/en/enterprise/2.15/user/articles/personalizing-your-profile", - "/en/enterprise/2.15/articles/pinning-a-team-discussion": "/en/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/enterprise/2.15/user/articles/pinning-a-team-discussion": "/en/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/enterprise/2.15/articles/pinning-a-team-discussion": "/en/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/en/enterprise/2.15/articles/pinning-items-to-your-profile": "/en/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/enterprise/2.15/user/articles/pinning-items-to-your-profile": "/en/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/enterprise/2.15/articles/pinning-items-to-your-profile": "/en/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/en/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.15/articles/preventing-unauthorized-access": "/en/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/enterprise/2.15/user/articles/preventing-unauthorized-access": "/en/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/enterprise/2.15/articles/preventing-unauthorized-access": "/en/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/en/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/en/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/enterprise/2.15/user/articles/project-board-permissions-for-an-organization": "/en/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/en/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/en/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/en/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/en/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository": "/en/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/en/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/en/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/en/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.15/articles/remembering-your-github-username-or-email": "/en/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/enterprise/2.15/user/articles/remembering-your-github-username-or-email": "/en/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/enterprise/2.15/articles/remembering-your-github-username-or-email": "/en/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/en/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.15/articles/removing-a-member-from-your-organization": "/en/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/enterprise/2.15/user/articles/removing-a-member-from-your-organization": "/en/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/enterprise/2.15/articles/removing-a-member-from-your-organization": "/en/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/en/enterprise/2.15/articles/removing-a-remote": "/en/enterprise/2.15/user/articles/removing-a-remote", - "/enterprise/2.15/user/articles/removing-a-remote": "/en/enterprise/2.15/user/articles/removing-a-remote", - "/enterprise/2.15/articles/removing-a-remote": "/en/enterprise/2.15/user/articles/removing-a-remote", - "/en/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/en/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/en/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/en/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/en/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/en/enterprise/2.15/articles/removing-organization-members-from-a-team": "/en/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/enterprise/2.15/user/articles/removing-organization-members-from-a-team": "/en/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/enterprise/2.15/articles/removing-organization-members-from-a-team": "/en/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/en/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/en/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.15/articles/removing-yourself-from-an-organization": "/en/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/enterprise/2.15/user/articles/removing-yourself-from-an-organization": "/en/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/enterprise/2.15/articles/removing-yourself-from-an-organization": "/en/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/en/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/en/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/en/enterprise/2.15/articles/renaming-a-file": "/en/enterprise/2.15/user/articles/renaming-a-file", - "/enterprise/2.15/user/articles/renaming-a-file": "/en/enterprise/2.15/user/articles/renaming-a-file", - "/enterprise/2.15/articles/renaming-a-file": "/en/enterprise/2.15/user/articles/renaming-a-file", - "/en/enterprise/2.15/articles/renaming-a-remote": "/en/enterprise/2.15/user/articles/renaming-a-remote", - "/enterprise/2.15/user/articles/renaming-a-remote": "/en/enterprise/2.15/user/articles/renaming-a-remote", - "/enterprise/2.15/articles/renaming-a-remote": "/en/enterprise/2.15/user/articles/renaming-a-remote", - "/en/enterprise/2.15/articles/renaming-a-repository": "/en/enterprise/2.15/user/articles/renaming-a-repository", - "/enterprise/2.15/user/articles/renaming-a-repository": "/en/enterprise/2.15/user/articles/renaming-a-repository", - "/enterprise/2.15/articles/renaming-a-repository": "/en/enterprise/2.15/user/articles/renaming-a-repository", - "/en/enterprise/2.15/articles/renaming-a-team": "/en/enterprise/2.15/user/articles/renaming-a-team", - "/enterprise/2.15/user/articles/renaming-a-team": "/en/enterprise/2.15/user/articles/renaming-a-team", - "/enterprise/2.15/articles/renaming-a-team": "/en/enterprise/2.15/user/articles/renaming-a-team", - "/en/enterprise/2.15/articles/renaming-an-organization": "/en/enterprise/2.15/user/articles/renaming-an-organization", - "/enterprise/2.15/user/articles/renaming-an-organization": "/en/enterprise/2.15/user/articles/renaming-an-organization", - "/enterprise/2.15/articles/renaming-an-organization": "/en/enterprise/2.15/user/articles/renaming-an-organization", - "/en/enterprise/2.15/articles/rendering-and-diffing-images": "/en/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/enterprise/2.15/user/articles/rendering-and-diffing-images": "/en/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/enterprise/2.15/articles/rendering-and-diffing-images": "/en/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/en/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/enterprise/2.15/user/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/en/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/en/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/enterprise/2.15/user/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/en/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/en/enterprise/2.15/articles/rendering-pdf-documents": "/en/enterprise/2.15/user/articles/rendering-pdf-documents", - "/enterprise/2.15/user/articles/rendering-pdf-documents": "/en/enterprise/2.15/user/articles/rendering-pdf-documents", - "/enterprise/2.15/articles/rendering-pdf-documents": "/en/enterprise/2.15/user/articles/rendering-pdf-documents", - "/en/enterprise/2.15/articles/reopening-a-closed-project-board": "/en/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/enterprise/2.15/user/articles/reopening-a-closed-project-board": "/en/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/enterprise/2.15/articles/reopening-a-closed-project-board": "/en/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/en/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/en/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/en/enterprise/2.15/articles/requesting-a-pull-request-review": "/en/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/enterprise/2.15/user/articles/requesting-a-pull-request-review": "/en/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/enterprise/2.15/articles/requesting-a-pull-request-review": "/en/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/en/enterprise/2.15/articles/requesting-to-add-a-child-team": "/en/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/enterprise/2.15/user/articles/requesting-to-add-a-child-team": "/en/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/enterprise/2.15/articles/requesting-to-add-a-child-team": "/en/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/en/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/en/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/en/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/en/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.15/articles/reverting-a-pull-request": "/en/enterprise/2.15/user/articles/reverting-a-pull-request", - "/enterprise/2.15/user/articles/reverting-a-pull-request": "/en/enterprise/2.15/user/articles/reverting-a-pull-request", - "/enterprise/2.15/articles/reverting-a-pull-request": "/en/enterprise/2.15/user/articles/reverting-a-pull-request", - "/en/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/en/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/en/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/enterprise/2.15/user/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/en/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/en/enterprise/2.15/articles/reviewing-your-deploy-keys": "/en/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/enterprise/2.15/user/articles/reviewing-your-deploy-keys": "/en/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/enterprise/2.15/articles/reviewing-your-deploy-keys": "/en/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/en/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.15/articles/reviewing-your-security-log": "/en/enterprise/2.15/user/articles/reviewing-your-security-log", - "/enterprise/2.15/user/articles/reviewing-your-security-log": "/en/enterprise/2.15/user/articles/reviewing-your-security-log", - "/enterprise/2.15/articles/reviewing-your-security-log": "/en/enterprise/2.15/user/articles/reviewing-your-security-log", - "/en/enterprise/2.15/articles/reviewing-your-ssh-keys": "/en/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/enterprise/2.15/user/articles/reviewing-your-ssh-keys": "/en/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/enterprise/2.15/articles/reviewing-your-ssh-keys": "/en/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/en/enterprise/2.15/articles/saving-repositories-with-stars": "/en/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/enterprise/2.15/user/articles/saving-repositories-with-stars": "/en/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/enterprise/2.15/articles/saving-repositories-with-stars": "/en/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/en/enterprise/2.15/articles/searching-code": "/en/enterprise/2.15/user/articles/searching-code", - "/enterprise/2.15/user/articles/searching-code": "/en/enterprise/2.15/user/articles/searching-code", - "/enterprise/2.15/articles/searching-code": "/en/enterprise/2.15/user/articles/searching-code", - "/en/enterprise/2.15/articles/searching-commits": "/en/enterprise/2.15/user/articles/searching-commits", - "/enterprise/2.15/user/articles/searching-commits": "/en/enterprise/2.15/user/articles/searching-commits", - "/enterprise/2.15/articles/searching-commits": "/en/enterprise/2.15/user/articles/searching-commits", - "/en/enterprise/2.15/articles/searching-for-repositories": "/en/enterprise/2.15/user/articles/searching-for-repositories", - "/enterprise/2.15/user/articles/searching-for-repositories": "/en/enterprise/2.15/user/articles/searching-for-repositories", - "/enterprise/2.15/articles/searching-for-repositories": "/en/enterprise/2.15/user/articles/searching-for-repositories", - "/en/enterprise/2.15/articles/searching-in-forks": "/en/enterprise/2.15/user/articles/searching-in-forks", - "/enterprise/2.15/user/articles/searching-in-forks": "/en/enterprise/2.15/user/articles/searching-in-forks", - "/enterprise/2.15/articles/searching-in-forks": "/en/enterprise/2.15/user/articles/searching-in-forks", - "/en/enterprise/2.15/articles/searching-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/enterprise/2.15/user/articles/searching-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/enterprise/2.15/articles/searching-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/en/enterprise/2.15/articles/searching-on-github": "/en/enterprise/2.15/user/articles/searching-on-github", - "/enterprise/2.15/user/articles/searching-on-github": "/en/enterprise/2.15/user/articles/searching-on-github", - "/enterprise/2.15/articles/searching-on-github": "/en/enterprise/2.15/user/articles/searching-on-github", - "/en/enterprise/2.15/articles/searching-topics": "/en/enterprise/2.15/user/articles/searching-topics", - "/enterprise/2.15/user/articles/searching-topics": "/en/enterprise/2.15/user/articles/searching-topics", - "/enterprise/2.15/articles/searching-topics": "/en/enterprise/2.15/user/articles/searching-topics", - "/en/enterprise/2.15/articles/searching-users": "/en/enterprise/2.15/user/articles/searching-users", - "/enterprise/2.15/user/articles/searching-users": "/en/enterprise/2.15/user/articles/searching-users", - "/enterprise/2.15/articles/searching-users": "/en/enterprise/2.15/user/articles/searching-users", - "/en/enterprise/2.15/articles/searching-wikis": "/en/enterprise/2.15/user/articles/searching-wikis", - "/enterprise/2.15/user/articles/searching-wikis": "/en/enterprise/2.15/user/articles/searching-wikis", - "/enterprise/2.15/articles/searching-wikis": "/en/enterprise/2.15/user/articles/searching-wikis", - "/en/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/en/enterprise/2.15/articles/set-up-git": "/en/enterprise/2.15/user/articles/set-up-git", - "/enterprise/2.15/user/articles/set-up-git": "/en/enterprise/2.15/user/articles/set-up-git", - "/enterprise/2.15/articles/set-up-git": "/en/enterprise/2.15/user/articles/set-up-git", - "/en/enterprise/2.15/articles/setting-a-backup-email-address": "/en/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/enterprise/2.15/user/articles/setting-a-backup-email-address": "/en/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/enterprise/2.15/articles/setting-a-backup-email-address": "/en/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/en/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/en/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/en/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/en/enterprise/2.15/articles/setting-repository-visibility": "/en/enterprise/2.15/user/articles/setting-repository-visibility", - "/enterprise/2.15/user/articles/setting-repository-visibility": "/en/enterprise/2.15/user/articles/setting-repository-visibility", - "/enterprise/2.15/articles/setting-repository-visibility": "/en/enterprise/2.15/user/articles/setting-repository-visibility", - "/en/enterprise/2.15/articles/setting-the-default-branch": "/en/enterprise/2.15/user/articles/setting-the-default-branch", - "/enterprise/2.15/user/articles/setting-the-default-branch": "/en/enterprise/2.15/user/articles/setting-the-default-branch", - "/enterprise/2.15/articles/setting-the-default-branch": "/en/enterprise/2.15/user/articles/setting-the-default-branch", - "/en/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/en/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/en/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/en/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.15/articles/setting-your-commit-email-address": "/en/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/enterprise/2.15/user/articles/setting-your-commit-email-address": "/en/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/enterprise/2.15/articles/setting-your-commit-email-address": "/en/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/en/enterprise/2.15/articles/setting-your-teams-profile-picture": "/en/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/enterprise/2.15/user/articles/setting-your-teams-profile-picture": "/en/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/enterprise/2.15/articles/setting-your-teams-profile-picture": "/en/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/en/enterprise/2.15/articles/setting-your-username-in-git": "/en/enterprise/2.15/user/articles/setting-your-username-in-git", - "/enterprise/2.15/user/articles/setting-your-username-in-git": "/en/enterprise/2.15/user/articles/setting-your-username-in-git", - "/enterprise/2.15/articles/setting-your-username-in-git": "/en/enterprise/2.15/user/articles/setting-your-username-in-git", - "/en/enterprise/2.15/articles/sharing-filters": "/en/enterprise/2.15/user/articles/sharing-filters", - "/enterprise/2.15/user/articles/sharing-filters": "/en/enterprise/2.15/user/articles/sharing-filters", - "/enterprise/2.15/articles/sharing-filters": "/en/enterprise/2.15/user/articles/sharing-filters", - "/en/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/en/enterprise/2.15/articles/signing-commits": "/en/enterprise/2.15/user/articles/signing-commits", - "/enterprise/2.15/user/articles/signing-commits": "/en/enterprise/2.15/user/articles/signing-commits", - "/enterprise/2.15/articles/signing-commits": "/en/enterprise/2.15/user/articles/signing-commits", - "/en/enterprise/2.15/articles/signing-tags": "/en/enterprise/2.15/user/articles/signing-tags", - "/enterprise/2.15/user/articles/signing-tags": "/en/enterprise/2.15/user/articles/signing-tags", - "/enterprise/2.15/articles/signing-tags": "/en/enterprise/2.15/user/articles/signing-tags", - "/en/enterprise/2.15/articles/signing-up-for-github": "/en/enterprise/2.15/user/articles/signing-up-for-github", - "/enterprise/2.15/user/articles/signing-up-for-github": "/en/enterprise/2.15/user/articles/signing-up-for-github", - "/enterprise/2.15/articles/signing-up-for-github": "/en/enterprise/2.15/user/articles/signing-up-for-github", - "/en/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/enterprise/2.15/user/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/en/enterprise/2.15/articles/sorting-search-results": "/en/enterprise/2.15/user/articles/sorting-search-results", - "/enterprise/2.15/user/articles/sorting-search-results": "/en/enterprise/2.15/user/articles/sorting-search-results", - "/enterprise/2.15/articles/sorting-search-results": "/en/enterprise/2.15/user/articles/sorting-search-results", - "/en/enterprise/2.15/articles/source-code-migration-tools": "/en/enterprise/2.15/user/articles/source-code-migration-tools", - "/enterprise/2.15/user/articles/source-code-migration-tools": "/en/enterprise/2.15/user/articles/source-code-migration-tools", - "/enterprise/2.15/articles/source-code-migration-tools": "/en/enterprise/2.15/user/articles/source-code-migration-tools", - "/en/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.15/articles/subversion-properties-supported-by-github": "/en/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/enterprise/2.15/user/articles/subversion-properties-supported-by-github": "/en/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/enterprise/2.15/articles/subversion-properties-supported-by-github": "/en/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/en/enterprise/2.15/articles/sudo-mode": "/en/enterprise/2.15/user/articles/sudo-mode", - "/enterprise/2.15/user/articles/sudo-mode": "/en/enterprise/2.15/user/articles/sudo-mode", - "/enterprise/2.15/articles/sudo-mode": "/en/enterprise/2.15/user/articles/sudo-mode", - "/en/enterprise/2.15/articles/support-for-subversion-clients": "/en/enterprise/2.15/user/articles/support-for-subversion-clients", - "/enterprise/2.15/user/articles/support-for-subversion-clients": "/en/enterprise/2.15/user/articles/support-for-subversion-clients", - "/enterprise/2.15/articles/support-for-subversion-clients": "/en/enterprise/2.15/user/articles/support-for-subversion-clients", - "/en/enterprise/2.15/articles/supported-browsers": "/en/enterprise/2.15/user/articles/supported-browsers", - "/enterprise/2.15/user/articles/supported-browsers": "/en/enterprise/2.15/user/articles/supported-browsers", - "/enterprise/2.15/articles/supported-browsers": "/en/enterprise/2.15/user/articles/supported-browsers", - "/en/enterprise/2.15/articles/syncing-a-fork": "/en/enterprise/2.15/user/articles/syncing-a-fork", - "/enterprise/2.15/user/articles/syncing-a-fork": "/en/enterprise/2.15/user/articles/syncing-a-fork", - "/enterprise/2.15/articles/syncing-a-fork": "/en/enterprise/2.15/user/articles/syncing-a-fork", - "/en/enterprise/2.15/articles/telling-git-about-your-signing-key": "/en/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/enterprise/2.15/user/articles/telling-git-about-your-signing-key": "/en/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/enterprise/2.15/articles/telling-git-about-your-signing-key": "/en/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/en/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.15/articles/testing-your-ssh-connection": "/en/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/enterprise/2.15/user/articles/testing-your-ssh-connection": "/en/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/enterprise/2.15/articles/testing-your-ssh-connection": "/en/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/en/enterprise/2.15/articles/tracking-changes-in-a-comment": "/en/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/enterprise/2.15/user/articles/tracking-changes-in-a-comment": "/en/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/enterprise/2.15/articles/tracking-changes-in-a-comment": "/en/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/en/enterprise/2.15/articles/tracking-changes-in-a-file": "/en/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/enterprise/2.15/user/articles/tracking-changes-in-a-file": "/en/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/enterprise/2.15/articles/tracking-changes-in-a-file": "/en/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/en/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/enterprise/2.15/user/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/en/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/en/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.15/articles/transferring-a-repository": "/en/enterprise/2.15/user/articles/transferring-a-repository", - "/enterprise/2.15/user/articles/transferring-a-repository": "/en/enterprise/2.15/user/articles/transferring-a-repository", - "/enterprise/2.15/articles/transferring-a-repository": "/en/enterprise/2.15/user/articles/transferring-a-repository", - "/en/enterprise/2.15/articles/transferring-organization-ownership": "/en/enterprise/2.15/user/articles/transferring-organization-ownership", - "/enterprise/2.15/user/articles/transferring-organization-ownership": "/en/enterprise/2.15/user/articles/transferring-organization-ownership", - "/enterprise/2.15/articles/transferring-organization-ownership": "/en/enterprise/2.15/user/articles/transferring-organization-ownership", - "/en/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/en/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/en/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.15/articles/troubleshooting-commits": "/en/enterprise/2.15/user/articles/troubleshooting-commits", - "/enterprise/2.15/user/articles/troubleshooting-commits": "/en/enterprise/2.15/user/articles/troubleshooting-commits", - "/enterprise/2.15/articles/troubleshooting-commits": "/en/enterprise/2.15/user/articles/troubleshooting-commits", - "/en/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.15/articles/troubleshooting-search-queries": "/en/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/enterprise/2.15/user/articles/troubleshooting-search-queries": "/en/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/enterprise/2.15/articles/troubleshooting-search-queries": "/en/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/en/enterprise/2.15/articles/troubleshooting-ssh": "/en/enterprise/2.15/user/articles/troubleshooting-ssh", - "/enterprise/2.15/user/articles/troubleshooting-ssh": "/en/enterprise/2.15/user/articles/troubleshooting-ssh", - "/enterprise/2.15/articles/troubleshooting-ssh": "/en/enterprise/2.15/user/articles/troubleshooting-ssh", - "/en/enterprise/2.15/articles/types-of-github-accounts": "/en/enterprise/2.15/user/articles/types-of-github-accounts", - "/enterprise/2.15/user/articles/types-of-github-accounts": "/en/enterprise/2.15/user/articles/types-of-github-accounts", - "/enterprise/2.15/articles/types-of-github-accounts": "/en/enterprise/2.15/user/articles/types-of-github-accounts", - "/en/enterprise/2.15/articles/types-of-required-status-checks": "/en/enterprise/2.15/user/articles/types-of-required-status-checks", - "/enterprise/2.15/user/articles/types-of-required-status-checks": "/en/enterprise/2.15/user/articles/types-of-required-status-checks", - "/enterprise/2.15/articles/types-of-required-status-checks": "/en/enterprise/2.15/user/articles/types-of-required-status-checks", - "/en/enterprise/2.15/articles/understanding-connections-between-repositories": "/en/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/enterprise/2.15/user/articles/understanding-connections-between-repositories": "/en/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/enterprise/2.15/articles/understanding-connections-between-repositories": "/en/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/en/enterprise/2.15/articles/understanding-the-search-syntax": "/en/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/enterprise/2.15/user/articles/understanding-the-search-syntax": "/en/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/enterprise/2.15/articles/understanding-the-search-syntax": "/en/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/en/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/en/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/enterprise/2.15/user/articles/unpublishing-a-github-pages-site": "/en/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/en/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/en/enterprise/2.15/articles/updating-an-expired-gpg-key": "/en/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/enterprise/2.15/user/articles/updating-an-expired-gpg-key": "/en/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/enterprise/2.15/articles/updating-an-expired-gpg-key": "/en/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/en/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.15/articles/updating-your-github-access-credentials": "/en/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/enterprise/2.15/user/articles/updating-your-github-access-credentials": "/en/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/enterprise/2.15/articles/updating-your-github-access-credentials": "/en/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/en/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.15/articles/using-advanced-git-commands": "/en/enterprise/2.15/user/articles/using-advanced-git-commands", - "/enterprise/2.15/user/articles/using-advanced-git-commands": "/en/enterprise/2.15/user/articles/using-advanced-git-commands", - "/enterprise/2.15/articles/using-advanced-git-commands": "/en/enterprise/2.15/user/articles/using-advanced-git-commands", - "/en/enterprise/2.15/articles/using-common-git-commands": "/en/enterprise/2.15/user/articles/using-common-git-commands", - "/enterprise/2.15/user/articles/using-common-git-commands": "/en/enterprise/2.15/user/articles/using-common-git-commands", - "/enterprise/2.15/articles/using-common-git-commands": "/en/enterprise/2.15/user/articles/using-common-git-commands", - "/en/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/en/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/en/enterprise/2.15/articles/using-github": "/en/enterprise/2.15/user/articles/using-github", - "/enterprise/2.15/user/articles/using-github": "/en/enterprise/2.15/user/articles/using-github", - "/enterprise/2.15/articles/using-github": "/en/enterprise/2.15/user/articles/using-github", - "/en/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/en/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/enterprise/2.15/user/articles/using-issue-and-pull-request-templates": "/en/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/en/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/en/enterprise/2.15/articles/using-saved-replies": "/en/enterprise/2.15/user/articles/using-saved-replies", - "/enterprise/2.15/user/articles/using-saved-replies": "/en/enterprise/2.15/user/articles/using-saved-replies", - "/enterprise/2.15/articles/using-saved-replies": "/en/enterprise/2.15/user/articles/using-saved-replies", - "/en/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.15/articles/versioning-large-files": "/en/enterprise/2.15/user/articles/versioning-large-files", - "/enterprise/2.15/user/articles/versioning-large-files": "/en/enterprise/2.15/user/articles/versioning-large-files", - "/enterprise/2.15/articles/versioning-large-files": "/en/enterprise/2.15/user/articles/versioning-large-files", - "/en/enterprise/2.15/articles/viewing-a-projects-contributors": "/en/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/enterprise/2.15/user/articles/viewing-a-projects-contributors": "/en/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/enterprise/2.15/articles/viewing-a-projects-contributors": "/en/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/en/enterprise/2.15/articles/viewing-a-pull-request-review": "/en/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/enterprise/2.15/user/articles/viewing-a-pull-request-review": "/en/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/enterprise/2.15/articles/viewing-a-pull-request-review": "/en/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/en/enterprise/2.15/articles/viewing-a-repositorys-network": "/en/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/enterprise/2.15/user/articles/viewing-a-repositorys-network": "/en/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/enterprise/2.15/articles/viewing-a-repositorys-network": "/en/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/en/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/en/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/en/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.15/articles/viewing-and-comparing-commits": "/en/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/enterprise/2.15/user/articles/viewing-and-comparing-commits": "/en/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/enterprise/2.15/articles/viewing-and-comparing-commits": "/en/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/en/enterprise/2.15/articles/viewing-branches-in-your-repository": "/en/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/enterprise/2.15/user/articles/viewing-branches-in-your-repository": "/en/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/enterprise/2.15/articles/viewing-branches-in-your-repository": "/en/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/en/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/enterprise/2.15/user/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/en/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/en/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.15/articles/viewing-your-milestones-progress": "/en/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/enterprise/2.15/user/articles/viewing-your-milestones-progress": "/en/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/enterprise/2.15/articles/viewing-your-milestones-progress": "/en/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/en/enterprise/2.15/articles/viewing-your-repositorys-tags": "/en/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/enterprise/2.15/user/articles/viewing-your-repositorys-tags": "/en/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/enterprise/2.15/articles/viewing-your-repositorys-tags": "/en/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/en/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/enterprise/2.15/user/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/en/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/en/enterprise/2.15/articles/watching-and-unwatching-repositories": "/en/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/enterprise/2.15/user/articles/watching-and-unwatching-repositories": "/en/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/enterprise/2.15/articles/watching-and-unwatching-repositories": "/en/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/en/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/en/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/en/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.15/articles/which-remote-url-should-i-use": "/en/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/enterprise/2.15/user/articles/which-remote-url-should-i-use": "/en/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/enterprise/2.15/articles/which-remote-url-should-i-use": "/en/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/en/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/en/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.15/articles/working-with-advanced-formatting": "/en/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/enterprise/2.15/user/articles/working-with-advanced-formatting": "/en/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/enterprise/2.15/articles/working-with-advanced-formatting": "/en/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/en/enterprise/2.15/articles/working-with-forks": "/en/enterprise/2.15/user/articles/working-with-forks", - "/enterprise/2.15/user/articles/working-with-forks": "/en/enterprise/2.15/user/articles/working-with-forks", - "/enterprise/2.15/articles/working-with-forks": "/en/enterprise/2.15/user/articles/working-with-forks", - "/en/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.15/articles/working-with-large-files": "/en/enterprise/2.15/user/articles/working-with-large-files", - "/enterprise/2.15/user/articles/working-with-large-files": "/en/enterprise/2.15/user/articles/working-with-large-files", - "/enterprise/2.15/articles/working-with-large-files": "/en/enterprise/2.15/user/articles/working-with-large-files", - "/en/enterprise/2.15/articles/working-with-non-code-files": "/en/enterprise/2.15/user/articles/working-with-non-code-files", - "/enterprise/2.15/user/articles/working-with-non-code-files": "/en/enterprise/2.15/user/articles/working-with-non-code-files", - "/enterprise/2.15/articles/working-with-non-code-files": "/en/enterprise/2.15/user/articles/working-with-non-code-files", - "/en/enterprise/2.15/articles/working-with-pre-receive-hooks": "/en/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/enterprise/2.15/user/articles/working-with-pre-receive-hooks": "/en/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/enterprise/2.15/articles/working-with-pre-receive-hooks": "/en/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/en/enterprise/2.15/articles/working-with-saved-replies": "/en/enterprise/2.15/user/articles/working-with-saved-replies", - "/enterprise/2.15/user/articles/working-with-saved-replies": "/en/enterprise/2.15/user/articles/working-with-saved-replies", - "/enterprise/2.15/articles/working-with-saved-replies": "/en/enterprise/2.15/user/articles/working-with-saved-replies", - "/en/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/enterprise/2.15/user/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/en/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/en/enterprise/2.15/articles/working-with-subversion-on-github": "/en/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/enterprise/2.15/user/articles/working-with-subversion-on-github": "/en/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/enterprise/2.15/articles/working-with-subversion-on-github": "/en/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/en/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/en/enterprise/2.15/user/categories/administering-a-repository", - "/en/enterprise/2.15/categories/administering-a-repository": "/en/enterprise/2.15/user/categories/administering-a-repository", - "/enterprise/2.15/user/categories/administering-a-repository": "/en/enterprise/2.15/user/categories/administering-a-repository", - "/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/en/enterprise/2.15/user/categories/administering-a-repository", - "/enterprise/2.15/categories/administering-a-repository": "/en/enterprise/2.15/user/categories/administering-a-repository", - "/en/enterprise/2.15/categories/authenticating-to-github": "/en/enterprise/2.15/user/categories/authenticating-to-github", - "/enterprise/2.15/user/categories/authenticating-to-github": "/en/enterprise/2.15/user/categories/authenticating-to-github", - "/enterprise/2.15/categories/authenticating-to-github": "/en/enterprise/2.15/user/categories/authenticating-to-github", - "/en/enterprise/2.15/categories/building-a-strong-community": "/en/enterprise/2.15/user/categories/building-a-strong-community", - "/enterprise/2.15/user/categories/building-a-strong-community": "/en/enterprise/2.15/user/categories/building-a-strong-community", - "/enterprise/2.15/categories/building-a-strong-community": "/en/enterprise/2.15/user/categories/building-a-strong-community", - "/en/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.15/categories/committing-changes-to-your-project": "/en/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/enterprise/2.15/user/categories/committing-changes-to-your-project": "/en/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/enterprise/2.15/categories/committing-changes-to-your-project": "/en/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/en/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/en/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.15/categories/extending-github": "/en/enterprise/2.15/user/categories/extending-github", - "/enterprise/2.15/user/categories/extending-github": "/en/enterprise/2.15/user/categories/extending-github", - "/enterprise/2.15/categories/extending-github": "/en/enterprise/2.15/user/categories/extending-github", - "/en/enterprise/2.15/categories/getting-started-with-github": "/en/enterprise/2.15/user/categories/getting-started-with-github", - "/enterprise/2.15/user/categories/getting-started-with-github": "/en/enterprise/2.15/user/categories/getting-started-with-github", - "/enterprise/2.15/categories/getting-started-with-github": "/en/enterprise/2.15/user/categories/getting-started-with-github", - "/en/enterprise/2.15/categories/importing-your-projects-to-github": "/en/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/enterprise/2.15/user/categories/importing-your-projects-to-github": "/en/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/enterprise/2.15/categories/importing-your-projects-to-github": "/en/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/en/enterprise/2.15/categories/managing-files-in-a-repository": "/en/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/enterprise/2.15/user/categories/managing-files-in-a-repository": "/en/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/enterprise/2.15/categories/managing-files-in-a-repository": "/en/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/en/enterprise/2.15/categories/managing-large-files": "/en/enterprise/2.15/user/categories/managing-large-files", - "/enterprise/2.15/user/categories/managing-large-files": "/en/enterprise/2.15/user/categories/managing-large-files", - "/enterprise/2.15/categories/managing-large-files": "/en/enterprise/2.15/user/categories/managing-large-files", - "/en/enterprise/2.15/categories/managing-your-work-on-github": "/en/enterprise/2.15/user/categories/managing-your-work-on-github", - "/enterprise/2.15/user/categories/managing-your-work-on-github": "/en/enterprise/2.15/user/categories/managing-your-work-on-github", - "/enterprise/2.15/categories/managing-your-work-on-github": "/en/enterprise/2.15/user/categories/managing-your-work-on-github", - "/en/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/en/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.15/categories/searching-for-information-on-github": "/en/enterprise/2.15/user/categories/searching-for-information-on-github", - "/enterprise/2.15/user/categories/searching-for-information-on-github": "/en/enterprise/2.15/user/categories/searching-for-information-on-github", - "/enterprise/2.15/categories/searching-for-information-on-github": "/en/enterprise/2.15/user/categories/searching-for-information-on-github", - "/en/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/en/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.15/categories/using-git": "/en/enterprise/2.15/user/categories/using-git", - "/enterprise/2.15/user/categories/using-git": "/en/enterprise/2.15/user/categories/using-git", - "/enterprise/2.15/categories/using-git": "/en/enterprise/2.15/user/categories/using-git", - "/en/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/en/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/en/enterprise/2.15/categories/working-with-github-pages": "/en/enterprise/2.15/user/categories/working-with-github-pages", - "/enterprise/2.15/user/categories/working-with-github-pages": "/en/enterprise/2.15/user/categories/working-with-github-pages", - "/enterprise/2.15/categories/working-with-github-pages": "/en/enterprise/2.15/user/categories/working-with-github-pages", - "/en/enterprise/2.15/categories/writing-on-github": "/en/enterprise/2.15/user/categories/writing-on-github", - "/enterprise/2.15/user/categories/writing-on-github": "/en/enterprise/2.15/user/categories/writing-on-github", - "/enterprise/2.15/categories/writing-on-github": "/en/enterprise/2.15/user/categories/writing-on-github", - "/enterprise/2.15/user": "/en/enterprise/2.15/user", - "/es/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/es/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/es/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/es/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/es/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/es/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/es/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/es/enterprise/2.15/admin/articles/using-github-task-runner", - "/es/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/es/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/es/enterprise/2.15/admin/guides/clustering/clustering-overview": "/es/enterprise/2.15/admin/clustering/clustering-overview", - "/es/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/es/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/es/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/es/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/es/enterprise/2.15/admin/guides/clustering": "/es/enterprise/2.15/admin/clustering", - "/es/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/es/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/es/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/es/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/es/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/es/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/es/enterprise/2.15/admin/guides/clustering/network-configuration": "/es/enterprise/2.15/admin/clustering/network-configuration", - "/es/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/es/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/es/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/es/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/es/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/es/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/es/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/es/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/es/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/es/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/es/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/es/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/es/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/es/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/es/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/es/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/es/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/es/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/es/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/es/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/es/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/es/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/es/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/es/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/es/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/es/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/es/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/es/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/es/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/es/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/es/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/es/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/es/enterprise/2.15/admin/guides/developer-workflow": "/es/enterprise/2.15/admin/developer-workflow", - "/es/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/es/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/es/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/es/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/es/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/es/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/es/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/es/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/es/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/es/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/es/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/es/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/es/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/es/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/es/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/es/enterprise/2.15/admin/guides/enterprise-support": "/es/enterprise/2.15/admin/enterprise-support", - "/es/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/es/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/es/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/es/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/es/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/es/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/es/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/es/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/es/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/es/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/es/enterprise/2.15/admin/guides": "/es/enterprise/2.15/admin", - "/es/enterprise/2.15/admin/guides/installation/about-geo-replication": "/es/enterprise/2.15/admin/installation/about-geo-replication", - "/es/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/es/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/es/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/es/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/es/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/es/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/es/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/es/enterprise/2.15/admin/installation/accessing-the-management-console", - "/es/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/es/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/es/enterprise/2.15/admin/guides/installation/activity-dashboard": "/es/enterprise/2.15/admin/installation/activity-dashboard", - "/es/enterprise/2.15/admin/guides/installation/audit-logging": "/es/enterprise/2.15/admin/installation/audit-logging", - "/es/enterprise/2.15/admin/guides/installation/audited-actions": "/es/enterprise/2.15/admin/installation/audited-actions", - "/es/enterprise/2.15/admin/guides/installation/command-line-utilities": "/es/enterprise/2.15/admin/installation/command-line-utilities", - "/es/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/es/enterprise/2.15/admin/installation/configuring-a-hostname", - "/es/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/es/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/es/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/es/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/es/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/es/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/es/enterprise/2.15/admin/guides/installation/configuring-collectd": "/es/enterprise/2.15/admin/installation/configuring-collectd", - "/es/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/es/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/es/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/es/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/es/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/es/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/es/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/es/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/es/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/es/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/es/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/es/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/es/enterprise/2.15/admin/installation/configuring-rate-limits", - "/es/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/es/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/es/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/es/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/es/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/es/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/es/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/es/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/es/enterprise/2.15/admin/guides/installation/configuring-tls": "/es/enterprise/2.15/admin/installation/configuring-tls", - "/es/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/es/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/es/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/es/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/es/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/es/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/es/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/es/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/es/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/es/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/es/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/es/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/es/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/es/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/es/enterprise/2.15/admin/installation/enabling-private-mode", - "/es/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/es/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/es/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/es/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/es/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/es/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/es/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/es/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/es/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/es/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/es/enterprise/2.15/admin/guides/installation": "/es/enterprise/2.15/admin/installation", - "/es/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/es/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/es/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/es/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/es/enterprise/2.15/admin/guides/installation/log-forwarding": "/es/enterprise/2.15/admin/installation/log-forwarding", - "/es/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/es/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/es/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/es/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/es/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/es/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/es/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/es/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/es/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/es/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/es/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/es/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/es/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/es/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/es/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/es/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/es/enterprise/2.15/admin/guides/installation/network-ports": "/es/enterprise/2.15/admin/installation/network-ports", - "/es/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/es/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/es/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/es/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/es/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/es/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/es/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/es/enterprise/2.15/admin/installation/searching-the-audit-log", - "/es/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/es/enterprise/2.15/admin/installation/setting-git-push-limits", - "/es/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/es/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/es/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/es/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/es/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/es/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/es/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/es/enterprise/2.15/admin/installation/site-admin-dashboard", - "/es/enterprise/2.15/admin/guides/installation/system-overview": "/es/enterprise/2.15/admin/installation/system-overview", - "/es/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/es/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/es/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/es/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/es/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/es/enterprise/2.15/admin/installation/upgrade-requirements", - "/es/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/es/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/es/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/es/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/es/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/es/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/es/enterprise/2.15/admin/installation/viewing-push-logs", - "/es/enterprise/2.15/admin/guides/migrations/about-migrations": "/es/enterprise/2.15/admin/migrations/about-migrations", - "/es/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/es/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/es/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/es/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/es/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/es/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/es/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/es/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/es/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/es/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/es/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/es/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/es/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/es/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/es/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/migrations": "/es/enterprise/2.15/admin/migrations", - "/es/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/es/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/es/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/es/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/es/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/es/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/es/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/es/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/es/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/es/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/es/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/es/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/es/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/es/enterprise/2.15/admin/user-management/about-global-webhooks", - "/es/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/es/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/es/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/es/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/es/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/es/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/es/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/es/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/es/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/es/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/es/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/es/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/es/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/es/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/es/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/es/enterprise/2.15/admin/user-management/basic-account-settings", - "/es/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/es/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/es/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/es/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/es/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/es/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/es/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/es/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/es/enterprise/2.15/admin/guides/user-management/creating-organizations": "/es/enterprise/2.15/admin/user-management/creating-organizations", - "/es/enterprise/2.15/admin/guides/user-management/creating-teams": "/es/enterprise/2.15/admin/user-management/creating-teams", - "/es/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/es/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/es/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/es/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/es/enterprise/2.15/admin/guides/user-management": "/es/enterprise/2.15/admin/user-management", - "/es/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/es/enterprise/2.15/admin/user-management/managing-dormant-users", - "/es/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/es/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/es/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/es/enterprise/2.15/admin/user-management/organizations-and-teams", - "/es/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/es/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/es/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/es/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/es/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/es/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/es/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/es/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/es/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/es/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/es/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/es/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/es/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/es/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/es/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/es/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/es/enterprise/2.15/admin/guides/user-management/repositories": "/es/enterprise/2.15/admin/user-management/repositories", - "/es/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/es/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/es/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/es/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/es/enterprise/2.15/admin/guides/user-management/user-security": "/es/enterprise/2.15/admin/user-management/user-security", - "/es/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/es/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/es/enterprise/2.15/admin/guides/user-management/using-cas": "/es/enterprise/2.15/admin/user-management/using-cas", - "/es/enterprise/2.15/admin/guides/user-management/using-ldap": "/es/enterprise/2.15/admin/user-management/using-ldap", - "/es/enterprise/2.15/admin/guides/user-management/using-saml": "/es/enterprise/2.15/admin/user-management/using-saml", - "/es/enterprise/2.15/articles/3d-file-viewer": "/es/enterprise/2.15/user/articles/3d-file-viewer", - "/es/enterprise/2.15/articles/about-archiving-repositories": "/es/enterprise/2.15/user/articles/about-archiving-repositories", - "/es/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/es/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/es/enterprise/2.15/articles/about-automation-for-project-boards": "/es/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/es/enterprise/2.15/articles/about-branch-restrictions": "/es/enterprise/2.15/user/articles/about-branch-restrictions", - "/es/enterprise/2.15/articles/about-branches": "/es/enterprise/2.15/user/articles/about-branches", - "/es/enterprise/2.15/articles/about-code-owners": "/es/enterprise/2.15/user/articles/about-code-owners", - "/es/enterprise/2.15/articles/about-collaborative-development-models": "/es/enterprise/2.15/user/articles/about-collaborative-development-models", - "/es/enterprise/2.15/articles/about-commit-signature-verification": "/es/enterprise/2.15/user/articles/about-commit-signature-verification", - "/es/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/es/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/es/enterprise/2.15/articles/about-conversations-on-github": "/es/enterprise/2.15/user/articles/about-conversations-on-github", - "/es/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/es/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/es/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/es/enterprise/2.15/articles/about-email-notifications": "/es/enterprise/2.15/user/articles/about-email-notifications", - "/es/enterprise/2.15/articles/about-forks": "/es/enterprise/2.15/user/articles/about-forks", - "/es/enterprise/2.15/articles/about-git-large-file-storage": "/es/enterprise/2.15/user/articles/about-git-large-file-storage", - "/es/enterprise/2.15/articles/about-git-rebase": "/es/enterprise/2.15/user/articles/about-git-rebase", - "/es/enterprise/2.15/articles/about-git-subtree-merges": "/es/enterprise/2.15/user/articles/about-git-subtree-merges", - "/es/enterprise/2.15/articles/about-github-pages-and-jekyll": "/es/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/es/enterprise/2.15/articles/about-github-pages": "/es/enterprise/2.15/user/articles/about-github-pages", - "/es/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/es/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/es/enterprise/2.15/articles/about-issues": "/es/enterprise/2.15/user/articles/about-issues", - "/es/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.15/articles/about-labels": "/es/enterprise/2.15/user/articles/about-labels", - "/es/enterprise/2.15/articles/about-merge-conflicts": "/es/enterprise/2.15/user/articles/about-merge-conflicts", - "/es/enterprise/2.15/articles/about-merge-methods-on-github": "/es/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/es/enterprise/2.15/articles/about-milestones": "/es/enterprise/2.15/user/articles/about-milestones", - "/es/enterprise/2.15/articles/about-notifications": "/es/enterprise/2.15/user/articles/about-notifications", - "/es/enterprise/2.15/articles/about-organization-membership": "/es/enterprise/2.15/user/articles/about-organization-membership", - "/es/enterprise/2.15/articles/about-organizations": "/es/enterprise/2.15/user/articles/about-organizations", - "/es/enterprise/2.15/articles/about-project-boards": "/es/enterprise/2.15/user/articles/about-project-boards", - "/es/enterprise/2.15/articles/about-protected-branches": "/es/enterprise/2.15/user/articles/about-protected-branches", - "/es/enterprise/2.15/articles/about-pull-request-merges": "/es/enterprise/2.15/user/articles/about-pull-request-merges", - "/es/enterprise/2.15/articles/about-pull-request-reviews": "/es/enterprise/2.15/user/articles/about-pull-request-reviews", - "/es/enterprise/2.15/articles/about-pull-requests": "/es/enterprise/2.15/user/articles/about-pull-requests", - "/es/enterprise/2.15/articles/about-readmes": "/es/enterprise/2.15/user/articles/about-readmes", - "/es/enterprise/2.15/articles/about-releases": "/es/enterprise/2.15/user/articles/about-releases", - "/es/enterprise/2.15/articles/about-remote-repositories": "/es/enterprise/2.15/user/articles/about-remote-repositories", - "/es/enterprise/2.15/articles/about-repositories": "/es/enterprise/2.15/user/articles/about-repositories", - "/es/enterprise/2.15/articles/about-repository-graphs": "/es/enterprise/2.15/user/articles/about-repository-graphs", - "/es/enterprise/2.15/articles/about-repository-languages": "/es/enterprise/2.15/user/articles/about-repository-languages", - "/es/enterprise/2.15/articles/about-required-commit-signing": "/es/enterprise/2.15/user/articles/about-required-commit-signing", - "/es/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/es/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/es/enterprise/2.15/articles/about-required-status-checks": "/es/enterprise/2.15/user/articles/about-required-status-checks", - "/es/enterprise/2.15/articles/about-saved-replies": "/es/enterprise/2.15/user/articles/about-saved-replies", - "/es/enterprise/2.15/articles/about-searching-on-github": "/es/enterprise/2.15/user/articles/about-searching-on-github", - "/es/enterprise/2.15/articles/about-ssh": "/es/enterprise/2.15/user/articles/about-ssh", - "/es/enterprise/2.15/articles/about-status-checks": "/es/enterprise/2.15/user/articles/about-status-checks", - "/es/enterprise/2.15/articles/about-task-lists": "/es/enterprise/2.15/user/articles/about-task-lists", - "/es/enterprise/2.15/articles/about-team-discussions": "/es/enterprise/2.15/user/articles/about-team-discussions", - "/es/enterprise/2.15/articles/about-teams": "/es/enterprise/2.15/user/articles/about-teams", - "/es/enterprise/2.15/articles/about-two-factor-authentication": "/es/enterprise/2.15/user/articles/about-two-factor-authentication", - "/es/enterprise/2.15/articles/about-web-notifications": "/es/enterprise/2.15/user/articles/about-web-notifications", - "/es/enterprise/2.15/articles/about-webhooks": "/es/enterprise/2.15/user/articles/about-webhooks", - "/es/enterprise/2.15/articles/about-wikis": "/es/enterprise/2.15/user/articles/about-wikis", - "/es/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/es/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/es/enterprise/2.15/articles/about-your-organization-dashboard": "/es/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/es/enterprise/2.15/articles/about-your-organizations-news-feed": "/es/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/es/enterprise/2.15/articles/about-your-organizations-profile": "/es/enterprise/2.15/user/articles/about-your-organizations-profile", - "/es/enterprise/2.15/articles/about-your-personal-dashboard": "/es/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/es/enterprise/2.15/articles/about-your-profile": "/es/enterprise/2.15/user/articles/about-your-profile", - "/es/enterprise/2.15/articles/access-permissions-on-github": "/es/enterprise/2.15/user/articles/access-permissions-on-github", - "/es/enterprise/2.15/articles/accessing-an-organization": "/es/enterprise/2.15/user/articles/accessing-an-organization", - "/es/enterprise/2.15/articles/accessing-basic-repository-data": "/es/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/es/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/es/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/es/enterprise/2.15/articles/accessing-your-notifications": "/es/enterprise/2.15/user/articles/accessing-your-notifications", - "/es/enterprise/2.15/articles/accessing-your-organizations-settings": "/es/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/es/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/es/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/es/enterprise/2.15/articles/adding-a-file-to-a-repository": "/es/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/es/enterprise/2.15/articles/adding-a-license-to-a-repository": "/es/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/es/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/es/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/es/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/es/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/es/enterprise/2.15/articles/adding-a-remote": "/es/enterprise/2.15/user/articles/adding-a-remote", - "/es/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/es/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/es/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/es/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/es/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/es/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/es/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/es/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/es/enterprise/2.15/articles/adding-notes-to-a-project-board": "/es/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/es/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/es/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/es/enterprise/2.15/articles/adding-organization-members-to-a-team": "/es/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/es/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/es/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/es/enterprise/2.15/articles/adding-people-to-your-organization": "/es/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/es/enterprise/2.15/articles/adding-support-resources-to-your-project": "/es/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/es/enterprise/2.15/articles/addressing-merge-conflicts": "/es/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/es/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/es/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/es/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/es/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/es/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/es/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/es/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/es/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/es/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/es/enterprise/2.15/articles/archiving-a-github-repository": "/es/enterprise/2.15/user/articles/archiving-a-github-repository", - "/es/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/es/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/es/enterprise/2.15/articles/archiving-repositories": "/es/enterprise/2.15/user/articles/archiving-repositories", - "/es/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/es/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/es/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/es/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/es/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/es/enterprise/2.15/articles/associating-text-editors-with-git": "/es/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/es/enterprise/2.15/articles/authorizing-oauth-apps": "/es/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/es/enterprise/2.15/articles/autolinked-references-and-urls": "/es/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/es/enterprise/2.15/articles/backing-up-a-repository": "/es/enterprise/2.15/user/articles/backing-up-a-repository", - "/es/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/es/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/es/enterprise/2.15/articles/be-social": "/es/enterprise/2.15/user/articles/be-social", - "/es/enterprise/2.15/articles/caching-your-github-password-in-git": "/es/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/es/enterprise/2.15/articles/changing-a-commit-message": "/es/enterprise/2.15/user/articles/changing-a-commit-message", - "/es/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/es/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/es/enterprise/2.15/articles/changing-a-remotes-url": "/es/enterprise/2.15/user/articles/changing-a-remotes-url", - "/es/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/es/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/es/enterprise/2.15/articles/changing-author-info": "/es/enterprise/2.15/user/articles/changing-author-info", - "/es/enterprise/2.15/articles/changing-project-board-visibility": "/es/enterprise/2.15/user/articles/changing-project-board-visibility", - "/es/enterprise/2.15/articles/changing-team-visibility": "/es/enterprise/2.15/user/articles/changing-team-visibility", - "/es/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/es/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/es/enterprise/2.15/articles/changing-your-github-username": "/es/enterprise/2.15/user/articles/changing-your-github-username", - "/es/enterprise/2.15/articles/changing-your-primary-email-address": "/es/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/es/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/es/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/es/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/es/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/es/enterprise/2.15/articles/checking-out-pull-requests-locally": "/es/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/es/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/es/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/es/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/es/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/es/enterprise/2.15/articles/classifying-your-repository-with-topics": "/es/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/es/enterprise/2.15/articles/cloning-a-repository-from-github": "/es/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/es/enterprise/2.15/articles/cloning-a-repository": "/es/enterprise/2.15/user/articles/cloning-a-repository", - "/es/enterprise/2.15/articles/closing-a-project-board": "/es/enterprise/2.15/user/articles/closing-a-project-board", - "/es/enterprise/2.15/articles/closing-a-pull-request": "/es/enterprise/2.15/user/articles/closing-a-pull-request", - "/es/enterprise/2.15/articles/closing-issues-using-keywords": "/es/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/es/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/es/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/es/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/es/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/es/enterprise/2.15/articles/collaborating-with-your-team": "/es/enterprise/2.15/user/articles/collaborating-with-your-team", - "/es/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/es/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/es/enterprise/2.15/articles/commenting-on-a-pull-request": "/es/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/es/enterprise/2.15/articles/commit-branch-and-tag-labels": "/es/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/es/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/es/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/es/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.15/articles/comparing-commits-across-time": "/es/enterprise/2.15/user/articles/comparing-commits-across-time", - "/es/enterprise/2.15/articles/conditions-for-large-files": "/es/enterprise/2.15/user/articles/conditions-for-large-files", - "/es/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/es/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/es/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/es/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/es/enterprise/2.15/articles/configuring-automation-for-project-boards": "/es/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/es/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.15/articles/configuring-git-large-file-storage": "/es/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/es/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/es/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/es/enterprise/2.15/articles/configuring-protected-branches": "/es/enterprise/2.15/user/articles/configuring-protected-branches", - "/es/enterprise/2.15/articles/configuring-pull-request-merges": "/es/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/es/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/es/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/es/enterprise/2.15/articles/configuring-two-factor-authentication": "/es/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/es/enterprise/2.15/articles/connecting-to-github-with-ssh": "/es/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/es/enterprise/2.15/articles/connecting-with-third-party-applications": "/es/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/es/enterprise/2.15/articles/converting-a-user-into-an-organization": "/es/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/es/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/es/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/es/enterprise/2.15/articles/converting-an-organization-into-a-user": "/es/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/es/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/es/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/es/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/es/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/es/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/es/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/es/enterprise/2.15/articles/create-a-repo": "/es/enterprise/2.15/user/articles/create-a-repo", - "/es/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/es/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/es/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/es/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/es/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/es/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/es/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/es/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/es/enterprise/2.15/articles/creating-a-github-pages-site": "/es/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/es/enterprise/2.15/articles/creating-a-label": "/es/enterprise/2.15/user/articles/creating-a-label", - "/es/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/es/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/es/enterprise/2.15/articles/creating-a-new-repository": "/es/enterprise/2.15/user/articles/creating-a-new-repository", - "/es/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/es/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/es/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/es/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/es/enterprise/2.15/articles/creating-a-project-board": "/es/enterprise/2.15/user/articles/creating-a-project-board", - "/es/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/es/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/es/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/es/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/es/enterprise/2.15/articles/creating-a-pull-request": "/es/enterprise/2.15/user/articles/creating-a-pull-request", - "/es/enterprise/2.15/articles/creating-a-repository-on-github": "/es/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/es/enterprise/2.15/articles/creating-a-saved-reply": "/es/enterprise/2.15/user/articles/creating-a-saved-reply", - "/es/enterprise/2.15/articles/creating-a-strong-password": "/es/enterprise/2.15/user/articles/creating-a-strong-password", - "/es/enterprise/2.15/articles/creating-a-team-discussion": "/es/enterprise/2.15/user/articles/creating-a-team-discussion", - "/es/enterprise/2.15/articles/creating-a-team": "/es/enterprise/2.15/user/articles/creating-a-team", - "/es/enterprise/2.15/articles/creating-an-issue": "/es/enterprise/2.15/user/articles/creating-an-issue", - "/es/enterprise/2.15/articles/creating-an-issues-only-repository": "/es/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/es/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/es/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/es/enterprise/2.15/articles/creating-and-editing-commits": "/es/enterprise/2.15/user/articles/creating-and-editing-commits", - "/es/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/es/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/es/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/es/enterprise/2.15/articles/creating-gists": "/es/enterprise/2.15/user/articles/creating-gists", - "/es/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/es/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/es/enterprise/2.15/articles/creating-new-files": "/es/enterprise/2.15/user/articles/creating-new-files", - "/es/enterprise/2.15/articles/creating-releases": "/es/enterprise/2.15/user/articles/creating-releases", - "/es/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.15/articles/customizing-your-profile": "/es/enterprise/2.15/user/articles/customizing-your-profile", - "/es/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/es/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/es/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.15/articles/deleting-a-label": "/es/enterprise/2.15/user/articles/deleting-a-label", - "/es/enterprise/2.15/articles/deleting-a-project-board": "/es/enterprise/2.15/user/articles/deleting-a-project-board", - "/es/enterprise/2.15/articles/deleting-a-repository": "/es/enterprise/2.15/user/articles/deleting-a-repository", - "/es/enterprise/2.15/articles/deleting-a-saved-reply": "/es/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/es/enterprise/2.15/articles/deleting-a-team": "/es/enterprise/2.15/user/articles/deleting-a-team", - "/es/enterprise/2.15/articles/deleting-an-organization-account": "/es/enterprise/2.15/user/articles/deleting-an-organization-account", - "/es/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.15/articles/deleting-files": "/es/enterprise/2.15/user/articles/deleting-files", - "/es/enterprise/2.15/articles/deleting-your-user-account": "/es/enterprise/2.15/user/articles/deleting-your-user-account", - "/es/enterprise/2.15/articles/differences-between-commit-views": "/es/enterprise/2.15/user/articles/differences-between-commit-views", - "/es/enterprise/2.15/articles/disabling-issues": "/es/enterprise/2.15/user/articles/disabling-issues", - "/es/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/es/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/es/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/es/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/es/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/es/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/es/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/es/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/es/enterprise/2.15/articles/disabling-wikis": "/es/enterprise/2.15/user/articles/disabling-wikis", - "/es/enterprise/2.15/articles/dismissing-a-pull-request-review": "/es/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/es/enterprise/2.15/articles/distributing-large-binaries": "/es/enterprise/2.15/user/articles/distributing-large-binaries", - "/es/enterprise/2.15/articles/documenting-your-project-with-wikis": "/es/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/es/enterprise/2.15/articles/duplicating-a-repository": "/es/enterprise/2.15/user/articles/duplicating-a-repository", - "/es/enterprise/2.15/articles/editing-a-label": "/es/enterprise/2.15/user/articles/editing-a-label", - "/es/enterprise/2.15/articles/editing-a-project-board": "/es/enterprise/2.15/user/articles/editing-a-project-board", - "/es/enterprise/2.15/articles/editing-a-saved-reply": "/es/enterprise/2.15/user/articles/editing-a-saved-reply", - "/es/enterprise/2.15/articles/editing-and-deleting-releases": "/es/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/es/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/es/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/es/enterprise/2.15/articles/editing-files-in-another-users-repository": "/es/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/es/enterprise/2.15/articles/editing-files-in-your-repository": "/es/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/es/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/es/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/es/enterprise/2.15/articles/editing-wiki-content": "/es/enterprise/2.15/user/articles/editing-wiki-content", - "/es/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.15/articles/enabling-branch-restrictions": "/es/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/es/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/es/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/es/enterprise/2.15/articles/enabling-required-commit-signing": "/es/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/es/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.15/articles/enabling-required-status-checks": "/es/enterprise/2.15/user/articles/enabling-required-status-checks", - "/es/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/es/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/es/enterprise/2.15/articles/error-bad-file-number": "/es/enterprise/2.15/user/articles/error-bad-file-number", - "/es/enterprise/2.15/articles/error-key-already-in-use": "/es/enterprise/2.15/user/articles/error-key-already-in-use", - "/es/enterprise/2.15/articles/error-permission-denied-publickey": "/es/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/es/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/es/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/es/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/es/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/es/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/es/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/es/enterprise/2.15/articles/error-repository-not-found": "/es/enterprise/2.15/user/articles/error-repository-not-found", - "/es/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/es/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/es/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/es/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/es/enterprise/2.15/articles/exploring-projects-on-github": "/es/enterprise/2.15/user/articles/exploring-projects-on-github", - "/es/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/es/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/es/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/es/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/es/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/es/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/es/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/es/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/es/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/es/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/es/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/es/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/es/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/es/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/es/enterprise/2.15/articles/finding-files-on-github": "/es/enterprise/2.15/user/articles/finding-files-on-github", - "/es/enterprise/2.15/articles/finding-information-in-a-repository": "/es/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/es/enterprise/2.15/articles/following-people": "/es/enterprise/2.15/user/articles/following-people", - "/es/enterprise/2.15/articles/fork-a-repo": "/es/enterprise/2.15/user/articles/fork-a-repo", - "/es/enterprise/2.15/articles/forking-and-cloning-gists": "/es/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/es/enterprise/2.15/articles/generating-a-new-gpg-key": "/es/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/es/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/es/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/es/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/es/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/es/enterprise/2.15/articles/getting-permanent-links-to-files": "/es/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/es/enterprise/2.15/articles/getting-started-with-git-and-github": "/es/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/es/enterprise/2.15/articles/getting-started-with-github-pages": "/es/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/es/enterprise/2.15/articles/getting-started-with-notifications": "/es/enterprise/2.15/user/articles/getting-started-with-notifications", - "/es/enterprise/2.15/articles/getting-started-with-searching-on-github": "/es/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/es/enterprise/2.15/articles/getting-started-with-the-api": "/es/enterprise/2.15/user/articles/getting-started-with-the-api", - "/es/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/es/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/es/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/es/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/es/enterprise/2.15/articles/git-and-github-learning-resources": "/es/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/es/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/es/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/es/enterprise/2.15/articles/git-cheatsheet": "/es/enterprise/2.15/user/articles/git-cheatsheet", - "/es/enterprise/2.15/articles/git-workflows": "/es/enterprise/2.15/user/articles/git-workflows", - "/es/enterprise/2.15/articles/github-flow": "/es/enterprise/2.15/user/articles/github-flow", - "/es/enterprise/2.15/articles/github-glossary": "/es/enterprise/2.15/user/articles/github-glossary", - "/es/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/es/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/es/enterprise/2.15/articles/https-cloning-errors": "/es/enterprise/2.15/user/articles/https-cloning-errors", - "/es/enterprise/2.15/articles/ignoring-files": "/es/enterprise/2.15/user/articles/ignoring-files", - "/es/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/es/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/es/enterprise/2.15/articles/importing-source-code-to-github": "/es/enterprise/2.15/user/articles/importing-source-code-to-github", - "/es/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/es/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/es/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/es/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/es/enterprise/2.15/articles/installing-git-large-file-storage": "/es/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/es/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/es/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/es/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/es/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/es/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/es/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/es/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/es/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/es/enterprise/2.15/articles/keeping-your-organization-secure": "/es/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/es/enterprise/2.15/articles/keyboard-shortcuts": "/es/enterprise/2.15/user/articles/keyboard-shortcuts", - "/es/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/es/enterprise/2.15/articles/learning-about-git": "/es/enterprise/2.15/user/articles/learning-about-git", - "/es/enterprise/2.15/articles/learning-about-github": "/es/enterprise/2.15/user/articles/learning-about-github", - "/es/enterprise/2.15/articles/licensing-a-repository": "/es/enterprise/2.15/user/articles/licensing-a-repository", - "/es/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/es/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/es/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/es/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/es/enterprise/2.15/articles/linking-to-releases": "/es/enterprise/2.15/user/articles/linking-to-releases", - "/es/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/es/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/es/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/es/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/es/enterprise/2.15/articles/locking-conversations": "/es/enterprise/2.15/user/articles/locking-conversations", - "/es/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/es/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/es/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/es/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/es/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/es/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/es/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/es/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/es/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/es/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/es/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/es/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/es/enterprise/2.15/articles/managing-branches-in-your-repository": "/es/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/es/enterprise/2.15/articles/managing-commit-signature-verification": "/es/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/es/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/es/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/es/enterprise/2.15/articles/managing-disruptive-comments": "/es/enterprise/2.15/user/articles/managing-disruptive-comments", - "/es/enterprise/2.15/articles/managing-email-preferences": "/es/enterprise/2.15/user/articles/managing-email-preferences", - "/es/enterprise/2.15/articles/managing-files-on-github": "/es/enterprise/2.15/user/articles/managing-files-on-github", - "/es/enterprise/2.15/articles/managing-files-using-the-command-line": "/es/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/es/enterprise/2.15/articles/managing-membership-in-your-organization": "/es/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/es/enterprise/2.15/articles/managing-organization-settings": "/es/enterprise/2.15/user/articles/managing-organization-settings", - "/es/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/es/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/es/enterprise/2.15/articles/managing-project-boards": "/es/enterprise/2.15/user/articles/managing-project-boards", - "/es/enterprise/2.15/articles/managing-releases-in-a-repository": "/es/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/es/enterprise/2.15/articles/managing-remote-repositories": "/es/enterprise/2.15/user/articles/managing-remote-repositories", - "/es/enterprise/2.15/articles/managing-repository-settings": "/es/enterprise/2.15/user/articles/managing-repository-settings", - "/es/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/es/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/es/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/es/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/es/enterprise/2.15/articles/managing-user-account-settings": "/es/enterprise/2.15/user/articles/managing-user-account-settings", - "/es/enterprise/2.15/articles/managing-your-membership-in-organizations": "/es/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/es/enterprise/2.15/articles/managing-your-notifications": "/es/enterprise/2.15/user/articles/managing-your-notifications", - "/es/enterprise/2.15/articles/managing-your-work-with-issues": "/es/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/es/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/es/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/es/enterprise/2.15/articles/mapping-geojson-files-on-github": "/es/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/es/enterprise/2.15/articles/marking-notifications-as-read": "/es/enterprise/2.15/user/articles/marking-notifications-as-read", - "/es/enterprise/2.15/articles/merging-a-pull-request": "/es/enterprise/2.15/user/articles/merging-a-pull-request", - "/es/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/es/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/es/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/es/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/es/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/es/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/es/enterprise/2.15/articles/moderating-comments-and-conversations": "/es/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/es/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/es/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/es/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/es/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/es/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/es/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/es/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/es/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/es/enterprise/2.15/articles/opening-an-issue-from-code": "/es/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/es/enterprise/2.15/articles/organizing-information-with-tables": "/es/enterprise/2.15/user/articles/organizing-information-with-tables", - "/es/enterprise/2.15/articles/organizing-members-into-teams": "/es/enterprise/2.15/user/articles/organizing-members-into-teams", - "/es/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/es/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/es/enterprise/2.15/articles/permission-levels-for-an-organization": "/es/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/es/enterprise/2.15/articles/personalizing-your-profile": "/es/enterprise/2.15/user/articles/personalizing-your-profile", - "/es/enterprise/2.15/articles/pinning-a-team-discussion": "/es/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/es/enterprise/2.15/articles/pinning-items-to-your-profile": "/es/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/es/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/es/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/es/enterprise/2.15/articles/preventing-unauthorized-access": "/es/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/es/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/es/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/es/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/es/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/es/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/es/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/es/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/es/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/es/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/es/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/es/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/es/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/es/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/es/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/es/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/es/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/es/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/es/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/es/enterprise/2.15/articles/remembering-your-github-username-or-email": "/es/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/es/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/es/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/es/enterprise/2.15/articles/removing-a-member-from-your-organization": "/es/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/es/enterprise/2.15/articles/removing-a-remote": "/es/enterprise/2.15/user/articles/removing-a-remote", - "/es/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/es/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/es/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/es/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/es/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/es/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/es/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/es/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/es/enterprise/2.15/articles/removing-organization-members-from-a-team": "/es/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/es/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/es/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/es/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/es/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/es/enterprise/2.15/articles/removing-yourself-from-an-organization": "/es/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/es/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/es/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/es/enterprise/2.15/articles/renaming-a-file": "/es/enterprise/2.15/user/articles/renaming-a-file", - "/es/enterprise/2.15/articles/renaming-a-remote": "/es/enterprise/2.15/user/articles/renaming-a-remote", - "/es/enterprise/2.15/articles/renaming-a-repository": "/es/enterprise/2.15/user/articles/renaming-a-repository", - "/es/enterprise/2.15/articles/renaming-a-team": "/es/enterprise/2.15/user/articles/renaming-a-team", - "/es/enterprise/2.15/articles/renaming-an-organization": "/es/enterprise/2.15/user/articles/renaming-an-organization", - "/es/enterprise/2.15/articles/rendering-and-diffing-images": "/es/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/es/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/es/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/es/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/es/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/es/enterprise/2.15/articles/rendering-pdf-documents": "/es/enterprise/2.15/user/articles/rendering-pdf-documents", - "/es/enterprise/2.15/articles/reopening-a-closed-project-board": "/es/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/es/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/es/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/es/enterprise/2.15/articles/requesting-a-pull-request-review": "/es/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/es/enterprise/2.15/articles/requesting-to-add-a-child-team": "/es/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/es/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/es/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/es/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/es/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/es/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/es/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/es/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/es/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/es/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/es/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/es/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/es/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/es/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/es/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.15/articles/reverting-a-pull-request": "/es/enterprise/2.15/user/articles/reverting-a-pull-request", - "/es/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/es/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/es/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/es/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/es/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/es/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/es/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/es/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/es/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/es/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/es/enterprise/2.15/articles/reviewing-your-deploy-keys": "/es/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/es/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/es/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/es/enterprise/2.15/articles/reviewing-your-security-log": "/es/enterprise/2.15/user/articles/reviewing-your-security-log", - "/es/enterprise/2.15/articles/reviewing-your-ssh-keys": "/es/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/es/enterprise/2.15/articles/saving-repositories-with-stars": "/es/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/es/enterprise/2.15/articles/searching-code": "/es/enterprise/2.15/user/articles/searching-code", - "/es/enterprise/2.15/articles/searching-commits": "/es/enterprise/2.15/user/articles/searching-commits", - "/es/enterprise/2.15/articles/searching-for-repositories": "/es/enterprise/2.15/user/articles/searching-for-repositories", - "/es/enterprise/2.15/articles/searching-in-forks": "/es/enterprise/2.15/user/articles/searching-in-forks", - "/es/enterprise/2.15/articles/searching-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/es/enterprise/2.15/articles/searching-on-github": "/es/enterprise/2.15/user/articles/searching-on-github", - "/es/enterprise/2.15/articles/searching-topics": "/es/enterprise/2.15/user/articles/searching-topics", - "/es/enterprise/2.15/articles/searching-users": "/es/enterprise/2.15/user/articles/searching-users", - "/es/enterprise/2.15/articles/searching-wikis": "/es/enterprise/2.15/user/articles/searching-wikis", - "/es/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/es/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/es/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/es/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/es/enterprise/2.15/articles/set-up-git": "/es/enterprise/2.15/user/articles/set-up-git", - "/es/enterprise/2.15/articles/setting-a-backup-email-address": "/es/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/es/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/es/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/es/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/es/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/es/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/es/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/es/enterprise/2.15/articles/setting-repository-visibility": "/es/enterprise/2.15/user/articles/setting-repository-visibility", - "/es/enterprise/2.15/articles/setting-the-default-branch": "/es/enterprise/2.15/user/articles/setting-the-default-branch", - "/es/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/es/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/es/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/es/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/es/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/es/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/es/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/es/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/es/enterprise/2.15/articles/setting-your-commit-email-address": "/es/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/es/enterprise/2.15/articles/setting-your-teams-profile-picture": "/es/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/es/enterprise/2.15/articles/setting-your-username-in-git": "/es/enterprise/2.15/user/articles/setting-your-username-in-git", - "/es/enterprise/2.15/articles/sharing-filters": "/es/enterprise/2.15/user/articles/sharing-filters", - "/es/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/es/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/es/enterprise/2.15/articles/signing-commits": "/es/enterprise/2.15/user/articles/signing-commits", - "/es/enterprise/2.15/articles/signing-tags": "/es/enterprise/2.15/user/articles/signing-tags", - "/es/enterprise/2.15/articles/signing-up-for-github": "/es/enterprise/2.15/user/articles/signing-up-for-github", - "/es/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/es/enterprise/2.15/articles/sorting-search-results": "/es/enterprise/2.15/user/articles/sorting-search-results", - "/es/enterprise/2.15/articles/source-code-migration-tools": "/es/enterprise/2.15/user/articles/source-code-migration-tools", - "/es/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/es/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/es/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/es/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/es/enterprise/2.15/articles/subversion-properties-supported-by-github": "/es/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/es/enterprise/2.15/articles/sudo-mode": "/es/enterprise/2.15/user/articles/sudo-mode", - "/es/enterprise/2.15/articles/support-for-subversion-clients": "/es/enterprise/2.15/user/articles/support-for-subversion-clients", - "/es/enterprise/2.15/articles/supported-browsers": "/es/enterprise/2.15/user/articles/supported-browsers", - "/es/enterprise/2.15/articles/syncing-a-fork": "/es/enterprise/2.15/user/articles/syncing-a-fork", - "/es/enterprise/2.15/articles/telling-git-about-your-signing-key": "/es/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/es/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/es/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/es/enterprise/2.15/articles/testing-your-ssh-connection": "/es/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/es/enterprise/2.15/articles/tracking-changes-in-a-comment": "/es/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/es/enterprise/2.15/articles/tracking-changes-in-a-file": "/es/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/es/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/es/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/es/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/es/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/es/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/es/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/es/enterprise/2.15/articles/transferring-a-repository": "/es/enterprise/2.15/user/articles/transferring-a-repository", - "/es/enterprise/2.15/articles/transferring-organization-ownership": "/es/enterprise/2.15/user/articles/transferring-organization-ownership", - "/es/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/es/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/es/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/es/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/es/enterprise/2.15/articles/troubleshooting-commits": "/es/enterprise/2.15/user/articles/troubleshooting-commits", - "/es/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.15/articles/troubleshooting-search-queries": "/es/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/es/enterprise/2.15/articles/troubleshooting-ssh": "/es/enterprise/2.15/user/articles/troubleshooting-ssh", - "/es/enterprise/2.15/articles/types-of-github-accounts": "/es/enterprise/2.15/user/articles/types-of-github-accounts", - "/es/enterprise/2.15/articles/types-of-required-status-checks": "/es/enterprise/2.15/user/articles/types-of-required-status-checks", - "/es/enterprise/2.15/articles/understanding-connections-between-repositories": "/es/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/es/enterprise/2.15/articles/understanding-the-search-syntax": "/es/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/es/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/es/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/es/enterprise/2.15/articles/updating-an-expired-gpg-key": "/es/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/es/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/es/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/es/enterprise/2.15/articles/updating-your-github-access-credentials": "/es/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/es/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/es/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/es/enterprise/2.15/articles/using-advanced-git-commands": "/es/enterprise/2.15/user/articles/using-advanced-git-commands", - "/es/enterprise/2.15/articles/using-common-git-commands": "/es/enterprise/2.15/user/articles/using-common-git-commands", - "/es/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/es/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/es/enterprise/2.15/articles/using-github": "/es/enterprise/2.15/user/articles/using-github", - "/es/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/es/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/es/enterprise/2.15/articles/using-saved-replies": "/es/enterprise/2.15/user/articles/using-saved-replies", - "/es/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/es/enterprise/2.15/articles/versioning-large-files": "/es/enterprise/2.15/user/articles/versioning-large-files", - "/es/enterprise/2.15/articles/viewing-a-projects-contributors": "/es/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/es/enterprise/2.15/articles/viewing-a-pull-request-review": "/es/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/es/enterprise/2.15/articles/viewing-a-repositorys-network": "/es/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/es/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/es/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/es/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/es/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/es/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/es/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/es/enterprise/2.15/articles/viewing-and-comparing-commits": "/es/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/es/enterprise/2.15/articles/viewing-branches-in-your-repository": "/es/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/es/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/es/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/es/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/es/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/es/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/es/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/es/enterprise/2.15/articles/viewing-your-milestones-progress": "/es/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/es/enterprise/2.15/articles/viewing-your-repositorys-tags": "/es/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/es/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/es/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/es/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/es/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/es/enterprise/2.15/articles/watching-and-unwatching-repositories": "/es/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/es/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/es/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/es/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/es/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/es/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/es/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/es/enterprise/2.15/articles/which-remote-url-should-i-use": "/es/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/es/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/es/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/es/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/es/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/es/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/es/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/es/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/es/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/es/enterprise/2.15/articles/working-with-advanced-formatting": "/es/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/es/enterprise/2.15/articles/working-with-forks": "/es/enterprise/2.15/user/articles/working-with-forks", - "/es/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/es/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/es/enterprise/2.15/articles/working-with-large-files": "/es/enterprise/2.15/user/articles/working-with-large-files", - "/es/enterprise/2.15/articles/working-with-non-code-files": "/es/enterprise/2.15/user/articles/working-with-non-code-files", - "/es/enterprise/2.15/articles/working-with-pre-receive-hooks": "/es/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/es/enterprise/2.15/articles/working-with-saved-replies": "/es/enterprise/2.15/user/articles/working-with-saved-replies", - "/es/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/es/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/es/enterprise/2.15/articles/working-with-subversion-on-github": "/es/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/es/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/es/enterprise/2.15/user/categories/administering-a-repository", - "/es/enterprise/2.15/categories/administering-a-repository": "/es/enterprise/2.15/user/categories/administering-a-repository", - "/es/enterprise/2.15/categories/authenticating-to-github": "/es/enterprise/2.15/user/categories/authenticating-to-github", - "/es/enterprise/2.15/categories/building-a-strong-community": "/es/enterprise/2.15/user/categories/building-a-strong-community", - "/es/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/es/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/es/enterprise/2.15/categories/committing-changes-to-your-project": "/es/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/es/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/es/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/es/enterprise/2.15/categories/extending-github": "/es/enterprise/2.15/user/categories/extending-github", - "/es/enterprise/2.15/categories/getting-started-with-github": "/es/enterprise/2.15/user/categories/getting-started-with-github", - "/es/enterprise/2.15/categories/importing-your-projects-to-github": "/es/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/es/enterprise/2.15/categories/managing-files-in-a-repository": "/es/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/es/enterprise/2.15/categories/managing-large-files": "/es/enterprise/2.15/user/categories/managing-large-files", - "/es/enterprise/2.15/categories/managing-your-work-on-github": "/es/enterprise/2.15/user/categories/managing-your-work-on-github", - "/es/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/es/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/es/enterprise/2.15/categories/searching-for-information-on-github": "/es/enterprise/2.15/user/categories/searching-for-information-on-github", - "/es/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/es/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/es/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/es/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/es/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/es/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/es/enterprise/2.15/categories/using-git": "/es/enterprise/2.15/user/categories/using-git", - "/es/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/es/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/es/enterprise/2.15/categories/working-with-github-pages": "/es/enterprise/2.15/user/categories/working-with-github-pages", - "/es/enterprise/2.15/categories/writing-on-github": "/es/enterprise/2.15/user/categories/writing-on-github", - "/ja/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/ja/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/ja/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/ja/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/ja/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/ja/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/ja/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/ja/enterprise/2.15/admin/articles/using-github-task-runner", - "/ja/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/ja/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/ja/enterprise/2.15/admin/guides/clustering/clustering-overview": "/ja/enterprise/2.15/admin/clustering/clustering-overview", - "/ja/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/ja/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/ja/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/ja/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/ja/enterprise/2.15/admin/guides/clustering": "/ja/enterprise/2.15/admin/clustering", - "/ja/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/ja/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/ja/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/ja/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/ja/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/ja/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/ja/enterprise/2.15/admin/guides/clustering/network-configuration": "/ja/enterprise/2.15/admin/clustering/network-configuration", - "/ja/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/ja/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/ja/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/ja/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/ja/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/ja/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/ja/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/ja/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/ja/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/ja/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/ja/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/ja/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/ja/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/ja/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/ja/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/ja/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/ja/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/ja/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/ja/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/ja/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/ja/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/ja/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/ja/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/ja/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/ja/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/ja/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/ja/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/ja/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/ja/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/ja/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/ja/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/ja/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/ja/enterprise/2.15/admin/guides/developer-workflow": "/ja/enterprise/2.15/admin/developer-workflow", - "/ja/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/ja/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/ja/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/ja/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/ja/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/ja/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/ja/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/ja/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/ja/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/ja/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/ja/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/ja/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/ja/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/ja/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/ja/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/ja/enterprise/2.15/admin/guides/enterprise-support": "/ja/enterprise/2.15/admin/enterprise-support", - "/ja/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/ja/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/ja/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/ja/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/ja/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/ja/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/ja/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/ja/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/ja/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/ja/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/ja/enterprise/2.15/admin/guides": "/ja/enterprise/2.15/admin", - "/ja/enterprise/2.15/admin/guides/installation/about-geo-replication": "/ja/enterprise/2.15/admin/installation/about-geo-replication", - "/ja/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/ja/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/ja/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/ja/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/ja/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/ja/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/ja/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/ja/enterprise/2.15/admin/installation/accessing-the-management-console", - "/ja/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/ja/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/ja/enterprise/2.15/admin/guides/installation/activity-dashboard": "/ja/enterprise/2.15/admin/installation/activity-dashboard", - "/ja/enterprise/2.15/admin/guides/installation/audit-logging": "/ja/enterprise/2.15/admin/installation/audit-logging", - "/ja/enterprise/2.15/admin/guides/installation/audited-actions": "/ja/enterprise/2.15/admin/installation/audited-actions", - "/ja/enterprise/2.15/admin/guides/installation/command-line-utilities": "/ja/enterprise/2.15/admin/installation/command-line-utilities", - "/ja/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/ja/enterprise/2.15/admin/installation/configuring-a-hostname", - "/ja/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/ja/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/ja/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/ja/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/ja/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/ja/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/ja/enterprise/2.15/admin/guides/installation/configuring-collectd": "/ja/enterprise/2.15/admin/installation/configuring-collectd", - "/ja/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/ja/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/ja/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/ja/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/ja/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/ja/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/ja/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/ja/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/ja/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/ja/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/ja/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/ja/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/ja/enterprise/2.15/admin/installation/configuring-rate-limits", - "/ja/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/ja/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/ja/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/ja/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/ja/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/ja/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/ja/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/ja/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/ja/enterprise/2.15/admin/guides/installation/configuring-tls": "/ja/enterprise/2.15/admin/installation/configuring-tls", - "/ja/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/ja/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/ja/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/ja/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/ja/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/ja/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/ja/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/ja/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/ja/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/ja/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/ja/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/ja/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/ja/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/ja/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/ja/enterprise/2.15/admin/installation/enabling-private-mode", - "/ja/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/ja/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/ja/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/ja/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/ja/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/ja/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/ja/enterprise/2.15/admin/guides/installation": "/ja/enterprise/2.15/admin/installation", - "/ja/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/ja/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/ja/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/ja/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/ja/enterprise/2.15/admin/guides/installation/log-forwarding": "/ja/enterprise/2.15/admin/installation/log-forwarding", - "/ja/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/ja/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/ja/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/ja/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/ja/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/ja/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/ja/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/ja/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/ja/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/ja/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/ja/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/ja/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/ja/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/ja/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/ja/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/ja/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/ja/enterprise/2.15/admin/guides/installation/network-ports": "/ja/enterprise/2.15/admin/installation/network-ports", - "/ja/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/ja/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/ja/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/ja/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/ja/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/ja/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/ja/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/ja/enterprise/2.15/admin/installation/searching-the-audit-log", - "/ja/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/ja/enterprise/2.15/admin/installation/setting-git-push-limits", - "/ja/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/ja/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/ja/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/ja/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/ja/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/ja/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/ja/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/ja/enterprise/2.15/admin/installation/site-admin-dashboard", - "/ja/enterprise/2.15/admin/guides/installation/system-overview": "/ja/enterprise/2.15/admin/installation/system-overview", - "/ja/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/ja/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/ja/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/ja/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/ja/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/ja/enterprise/2.15/admin/installation/upgrade-requirements", - "/ja/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/ja/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/ja/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/ja/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/ja/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/ja/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/ja/enterprise/2.15/admin/installation/viewing-push-logs", - "/ja/enterprise/2.15/admin/guides/migrations/about-migrations": "/ja/enterprise/2.15/admin/migrations/about-migrations", - "/ja/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/ja/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/ja/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/ja/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/ja/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/ja/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/ja/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/ja/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/ja/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/ja/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/ja/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/ja/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/ja/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/ja/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/ja/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/migrations": "/ja/enterprise/2.15/admin/migrations", - "/ja/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/ja/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/ja/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/ja/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/ja/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/ja/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/ja/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/ja/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/ja/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/ja/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/ja/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/ja/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/ja/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/ja/enterprise/2.15/admin/user-management/about-global-webhooks", - "/ja/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/ja/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/ja/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/ja/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/ja/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/ja/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/ja/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/ja/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/ja/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/ja/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/ja/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/ja/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/ja/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/ja/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/ja/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/ja/enterprise/2.15/admin/user-management/basic-account-settings", - "/ja/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/ja/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/ja/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/ja/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/ja/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/ja/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/ja/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/ja/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/ja/enterprise/2.15/admin/guides/user-management/creating-organizations": "/ja/enterprise/2.15/admin/user-management/creating-organizations", - "/ja/enterprise/2.15/admin/guides/user-management/creating-teams": "/ja/enterprise/2.15/admin/user-management/creating-teams", - "/ja/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/ja/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/ja/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/ja/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/ja/enterprise/2.15/admin/guides/user-management": "/ja/enterprise/2.15/admin/user-management", - "/ja/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/ja/enterprise/2.15/admin/user-management/managing-dormant-users", - "/ja/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/ja/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/ja/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/ja/enterprise/2.15/admin/user-management/organizations-and-teams", - "/ja/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/ja/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/ja/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/ja/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/ja/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/ja/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/ja/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/ja/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/ja/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/ja/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/ja/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/ja/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/ja/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/ja/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/ja/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/ja/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/ja/enterprise/2.15/admin/guides/user-management/repositories": "/ja/enterprise/2.15/admin/user-management/repositories", - "/ja/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/ja/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/ja/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/ja/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/ja/enterprise/2.15/admin/guides/user-management/user-security": "/ja/enterprise/2.15/admin/user-management/user-security", - "/ja/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/ja/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/ja/enterprise/2.15/admin/guides/user-management/using-cas": "/ja/enterprise/2.15/admin/user-management/using-cas", - "/ja/enterprise/2.15/admin/guides/user-management/using-ldap": "/ja/enterprise/2.15/admin/user-management/using-ldap", - "/ja/enterprise/2.15/admin/guides/user-management/using-saml": "/ja/enterprise/2.15/admin/user-management/using-saml", - "/ja/enterprise/2.15/articles/3d-file-viewer": "/ja/enterprise/2.15/user/articles/3d-file-viewer", - "/ja/enterprise/2.15/articles/about-archiving-repositories": "/ja/enterprise/2.15/user/articles/about-archiving-repositories", - "/ja/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/ja/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/ja/enterprise/2.15/articles/about-automation-for-project-boards": "/ja/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/ja/enterprise/2.15/articles/about-branch-restrictions": "/ja/enterprise/2.15/user/articles/about-branch-restrictions", - "/ja/enterprise/2.15/articles/about-branches": "/ja/enterprise/2.15/user/articles/about-branches", - "/ja/enterprise/2.15/articles/about-code-owners": "/ja/enterprise/2.15/user/articles/about-code-owners", - "/ja/enterprise/2.15/articles/about-collaborative-development-models": "/ja/enterprise/2.15/user/articles/about-collaborative-development-models", - "/ja/enterprise/2.15/articles/about-commit-signature-verification": "/ja/enterprise/2.15/user/articles/about-commit-signature-verification", - "/ja/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/ja/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/ja/enterprise/2.15/articles/about-conversations-on-github": "/ja/enterprise/2.15/user/articles/about-conversations-on-github", - "/ja/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.15/articles/about-email-notifications": "/ja/enterprise/2.15/user/articles/about-email-notifications", - "/ja/enterprise/2.15/articles/about-forks": "/ja/enterprise/2.15/user/articles/about-forks", - "/ja/enterprise/2.15/articles/about-git-large-file-storage": "/ja/enterprise/2.15/user/articles/about-git-large-file-storage", - "/ja/enterprise/2.15/articles/about-git-rebase": "/ja/enterprise/2.15/user/articles/about-git-rebase", - "/ja/enterprise/2.15/articles/about-git-subtree-merges": "/ja/enterprise/2.15/user/articles/about-git-subtree-merges", - "/ja/enterprise/2.15/articles/about-github-pages-and-jekyll": "/ja/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/ja/enterprise/2.15/articles/about-github-pages": "/ja/enterprise/2.15/user/articles/about-github-pages", - "/ja/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/ja/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/ja/enterprise/2.15/articles/about-issues": "/ja/enterprise/2.15/user/articles/about-issues", - "/ja/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.15/articles/about-labels": "/ja/enterprise/2.15/user/articles/about-labels", - "/ja/enterprise/2.15/articles/about-merge-conflicts": "/ja/enterprise/2.15/user/articles/about-merge-conflicts", - "/ja/enterprise/2.15/articles/about-merge-methods-on-github": "/ja/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/ja/enterprise/2.15/articles/about-milestones": "/ja/enterprise/2.15/user/articles/about-milestones", - "/ja/enterprise/2.15/articles/about-notifications": "/ja/enterprise/2.15/user/articles/about-notifications", - "/ja/enterprise/2.15/articles/about-organization-membership": "/ja/enterprise/2.15/user/articles/about-organization-membership", - "/ja/enterprise/2.15/articles/about-organizations": "/ja/enterprise/2.15/user/articles/about-organizations", - "/ja/enterprise/2.15/articles/about-project-boards": "/ja/enterprise/2.15/user/articles/about-project-boards", - "/ja/enterprise/2.15/articles/about-protected-branches": "/ja/enterprise/2.15/user/articles/about-protected-branches", - "/ja/enterprise/2.15/articles/about-pull-request-merges": "/ja/enterprise/2.15/user/articles/about-pull-request-merges", - "/ja/enterprise/2.15/articles/about-pull-request-reviews": "/ja/enterprise/2.15/user/articles/about-pull-request-reviews", - "/ja/enterprise/2.15/articles/about-pull-requests": "/ja/enterprise/2.15/user/articles/about-pull-requests", - "/ja/enterprise/2.15/articles/about-readmes": "/ja/enterprise/2.15/user/articles/about-readmes", - "/ja/enterprise/2.15/articles/about-releases": "/ja/enterprise/2.15/user/articles/about-releases", - "/ja/enterprise/2.15/articles/about-remote-repositories": "/ja/enterprise/2.15/user/articles/about-remote-repositories", - "/ja/enterprise/2.15/articles/about-repositories": "/ja/enterprise/2.15/user/articles/about-repositories", - "/ja/enterprise/2.15/articles/about-repository-graphs": "/ja/enterprise/2.15/user/articles/about-repository-graphs", - "/ja/enterprise/2.15/articles/about-repository-languages": "/ja/enterprise/2.15/user/articles/about-repository-languages", - "/ja/enterprise/2.15/articles/about-required-commit-signing": "/ja/enterprise/2.15/user/articles/about-required-commit-signing", - "/ja/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/ja/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.15/articles/about-required-status-checks": "/ja/enterprise/2.15/user/articles/about-required-status-checks", - "/ja/enterprise/2.15/articles/about-saved-replies": "/ja/enterprise/2.15/user/articles/about-saved-replies", - "/ja/enterprise/2.15/articles/about-searching-on-github": "/ja/enterprise/2.15/user/articles/about-searching-on-github", - "/ja/enterprise/2.15/articles/about-ssh": "/ja/enterprise/2.15/user/articles/about-ssh", - "/ja/enterprise/2.15/articles/about-status-checks": "/ja/enterprise/2.15/user/articles/about-status-checks", - "/ja/enterprise/2.15/articles/about-task-lists": "/ja/enterprise/2.15/user/articles/about-task-lists", - "/ja/enterprise/2.15/articles/about-team-discussions": "/ja/enterprise/2.15/user/articles/about-team-discussions", - "/ja/enterprise/2.15/articles/about-teams": "/ja/enterprise/2.15/user/articles/about-teams", - "/ja/enterprise/2.15/articles/about-two-factor-authentication": "/ja/enterprise/2.15/user/articles/about-two-factor-authentication", - "/ja/enterprise/2.15/articles/about-web-notifications": "/ja/enterprise/2.15/user/articles/about-web-notifications", - "/ja/enterprise/2.15/articles/about-webhooks": "/ja/enterprise/2.15/user/articles/about-webhooks", - "/ja/enterprise/2.15/articles/about-wikis": "/ja/enterprise/2.15/user/articles/about-wikis", - "/ja/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/ja/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/ja/enterprise/2.15/articles/about-your-organization-dashboard": "/ja/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/ja/enterprise/2.15/articles/about-your-organizations-news-feed": "/ja/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/ja/enterprise/2.15/articles/about-your-organizations-profile": "/ja/enterprise/2.15/user/articles/about-your-organizations-profile", - "/ja/enterprise/2.15/articles/about-your-personal-dashboard": "/ja/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/ja/enterprise/2.15/articles/about-your-profile": "/ja/enterprise/2.15/user/articles/about-your-profile", - "/ja/enterprise/2.15/articles/access-permissions-on-github": "/ja/enterprise/2.15/user/articles/access-permissions-on-github", - "/ja/enterprise/2.15/articles/accessing-an-organization": "/ja/enterprise/2.15/user/articles/accessing-an-organization", - "/ja/enterprise/2.15/articles/accessing-basic-repository-data": "/ja/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/ja/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/ja/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/ja/enterprise/2.15/articles/accessing-your-notifications": "/ja/enterprise/2.15/user/articles/accessing-your-notifications", - "/ja/enterprise/2.15/articles/accessing-your-organizations-settings": "/ja/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/ja/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/ja/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/ja/enterprise/2.15/articles/adding-a-file-to-a-repository": "/ja/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/ja/enterprise/2.15/articles/adding-a-license-to-a-repository": "/ja/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/ja/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/ja/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/ja/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/ja/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/ja/enterprise/2.15/articles/adding-a-remote": "/ja/enterprise/2.15/user/articles/adding-a-remote", - "/ja/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/ja/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/ja/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/ja/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/ja/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/ja/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/ja/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/ja/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/ja/enterprise/2.15/articles/adding-notes-to-a-project-board": "/ja/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/ja/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/ja/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/ja/enterprise/2.15/articles/adding-organization-members-to-a-team": "/ja/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/ja/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/ja/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/ja/enterprise/2.15/articles/adding-people-to-your-organization": "/ja/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/ja/enterprise/2.15/articles/adding-support-resources-to-your-project": "/ja/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/ja/enterprise/2.15/articles/addressing-merge-conflicts": "/ja/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/ja/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/ja/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/ja/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/ja/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/ja/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/ja/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/ja/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/ja/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/ja/enterprise/2.15/articles/archiving-a-github-repository": "/ja/enterprise/2.15/user/articles/archiving-a-github-repository", - "/ja/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/ja/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/ja/enterprise/2.15/articles/archiving-repositories": "/ja/enterprise/2.15/user/articles/archiving-repositories", - "/ja/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/ja/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/ja/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/ja/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/ja/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/associating-text-editors-with-git": "/ja/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/ja/enterprise/2.15/articles/authorizing-oauth-apps": "/ja/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/ja/enterprise/2.15/articles/autolinked-references-and-urls": "/ja/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/ja/enterprise/2.15/articles/backing-up-a-repository": "/ja/enterprise/2.15/user/articles/backing-up-a-repository", - "/ja/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/ja/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/ja/enterprise/2.15/articles/be-social": "/ja/enterprise/2.15/user/articles/be-social", - "/ja/enterprise/2.15/articles/caching-your-github-password-in-git": "/ja/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/ja/enterprise/2.15/articles/changing-a-commit-message": "/ja/enterprise/2.15/user/articles/changing-a-commit-message", - "/ja/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/ja/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/ja/enterprise/2.15/articles/changing-a-remotes-url": "/ja/enterprise/2.15/user/articles/changing-a-remotes-url", - "/ja/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/ja/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/ja/enterprise/2.15/articles/changing-author-info": "/ja/enterprise/2.15/user/articles/changing-author-info", - "/ja/enterprise/2.15/articles/changing-project-board-visibility": "/ja/enterprise/2.15/user/articles/changing-project-board-visibility", - "/ja/enterprise/2.15/articles/changing-team-visibility": "/ja/enterprise/2.15/user/articles/changing-team-visibility", - "/ja/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/ja/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/ja/enterprise/2.15/articles/changing-your-github-username": "/ja/enterprise/2.15/user/articles/changing-your-github-username", - "/ja/enterprise/2.15/articles/changing-your-primary-email-address": "/ja/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/ja/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/ja/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/ja/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/ja/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/ja/enterprise/2.15/articles/checking-out-pull-requests-locally": "/ja/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/ja/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/ja/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/ja/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/ja/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/ja/enterprise/2.15/articles/classifying-your-repository-with-topics": "/ja/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/ja/enterprise/2.15/articles/cloning-a-repository-from-github": "/ja/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/ja/enterprise/2.15/articles/cloning-a-repository": "/ja/enterprise/2.15/user/articles/cloning-a-repository", - "/ja/enterprise/2.15/articles/closing-a-project-board": "/ja/enterprise/2.15/user/articles/closing-a-project-board", - "/ja/enterprise/2.15/articles/closing-a-pull-request": "/ja/enterprise/2.15/user/articles/closing-a-pull-request", - "/ja/enterprise/2.15/articles/closing-issues-using-keywords": "/ja/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/ja/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/ja/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/ja/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/ja/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/ja/enterprise/2.15/articles/collaborating-with-your-team": "/ja/enterprise/2.15/user/articles/collaborating-with-your-team", - "/ja/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/ja/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/ja/enterprise/2.15/articles/commenting-on-a-pull-request": "/ja/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/ja/enterprise/2.15/articles/commit-branch-and-tag-labels": "/ja/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/ja/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/ja/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/ja/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.15/articles/comparing-commits-across-time": "/ja/enterprise/2.15/user/articles/comparing-commits-across-time", - "/ja/enterprise/2.15/articles/conditions-for-large-files": "/ja/enterprise/2.15/user/articles/conditions-for-large-files", - "/ja/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/ja/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/ja/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/ja/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/ja/enterprise/2.15/articles/configuring-automation-for-project-boards": "/ja/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/ja/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.15/articles/configuring-git-large-file-storage": "/ja/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/ja/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/ja/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/ja/enterprise/2.15/articles/configuring-protected-branches": "/ja/enterprise/2.15/user/articles/configuring-protected-branches", - "/ja/enterprise/2.15/articles/configuring-pull-request-merges": "/ja/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/ja/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/ja/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/ja/enterprise/2.15/articles/configuring-two-factor-authentication": "/ja/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/ja/enterprise/2.15/articles/connecting-to-github-with-ssh": "/ja/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/ja/enterprise/2.15/articles/connecting-with-third-party-applications": "/ja/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/ja/enterprise/2.15/articles/converting-a-user-into-an-organization": "/ja/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/ja/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/ja/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/ja/enterprise/2.15/articles/converting-an-organization-into-a-user": "/ja/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/ja/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/ja/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/ja/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/ja/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/ja/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/ja/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/ja/enterprise/2.15/articles/create-a-repo": "/ja/enterprise/2.15/user/articles/create-a-repo", - "/ja/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/ja/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/ja/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/ja/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/ja/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/ja/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/ja/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/ja/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.15/articles/creating-a-github-pages-site": "/ja/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/ja/enterprise/2.15/articles/creating-a-label": "/ja/enterprise/2.15/user/articles/creating-a-label", - "/ja/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/ja/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/ja/enterprise/2.15/articles/creating-a-new-repository": "/ja/enterprise/2.15/user/articles/creating-a-new-repository", - "/ja/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/ja/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/ja/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/ja/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/ja/enterprise/2.15/articles/creating-a-project-board": "/ja/enterprise/2.15/user/articles/creating-a-project-board", - "/ja/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/ja/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/ja/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/ja/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/ja/enterprise/2.15/articles/creating-a-pull-request": "/ja/enterprise/2.15/user/articles/creating-a-pull-request", - "/ja/enterprise/2.15/articles/creating-a-repository-on-github": "/ja/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/ja/enterprise/2.15/articles/creating-a-saved-reply": "/ja/enterprise/2.15/user/articles/creating-a-saved-reply", - "/ja/enterprise/2.15/articles/creating-a-strong-password": "/ja/enterprise/2.15/user/articles/creating-a-strong-password", - "/ja/enterprise/2.15/articles/creating-a-team-discussion": "/ja/enterprise/2.15/user/articles/creating-a-team-discussion", - "/ja/enterprise/2.15/articles/creating-a-team": "/ja/enterprise/2.15/user/articles/creating-a-team", - "/ja/enterprise/2.15/articles/creating-an-issue": "/ja/enterprise/2.15/user/articles/creating-an-issue", - "/ja/enterprise/2.15/articles/creating-an-issues-only-repository": "/ja/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/ja/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/ja/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/ja/enterprise/2.15/articles/creating-and-editing-commits": "/ja/enterprise/2.15/user/articles/creating-and-editing-commits", - "/ja/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/ja/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/ja/enterprise/2.15/articles/creating-gists": "/ja/enterprise/2.15/user/articles/creating-gists", - "/ja/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/ja/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/ja/enterprise/2.15/articles/creating-new-files": "/ja/enterprise/2.15/user/articles/creating-new-files", - "/ja/enterprise/2.15/articles/creating-releases": "/ja/enterprise/2.15/user/articles/creating-releases", - "/ja/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.15/articles/customizing-your-profile": "/ja/enterprise/2.15/user/articles/customizing-your-profile", - "/ja/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/ja/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/ja/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.15/articles/deleting-a-label": "/ja/enterprise/2.15/user/articles/deleting-a-label", - "/ja/enterprise/2.15/articles/deleting-a-project-board": "/ja/enterprise/2.15/user/articles/deleting-a-project-board", - "/ja/enterprise/2.15/articles/deleting-a-repository": "/ja/enterprise/2.15/user/articles/deleting-a-repository", - "/ja/enterprise/2.15/articles/deleting-a-saved-reply": "/ja/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/ja/enterprise/2.15/articles/deleting-a-team": "/ja/enterprise/2.15/user/articles/deleting-a-team", - "/ja/enterprise/2.15/articles/deleting-an-organization-account": "/ja/enterprise/2.15/user/articles/deleting-an-organization-account", - "/ja/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.15/articles/deleting-files": "/ja/enterprise/2.15/user/articles/deleting-files", - "/ja/enterprise/2.15/articles/deleting-your-user-account": "/ja/enterprise/2.15/user/articles/deleting-your-user-account", - "/ja/enterprise/2.15/articles/differences-between-commit-views": "/ja/enterprise/2.15/user/articles/differences-between-commit-views", - "/ja/enterprise/2.15/articles/disabling-issues": "/ja/enterprise/2.15/user/articles/disabling-issues", - "/ja/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/ja/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/ja/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/ja/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/ja/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/ja/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/ja/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/ja/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/ja/enterprise/2.15/articles/disabling-wikis": "/ja/enterprise/2.15/user/articles/disabling-wikis", - "/ja/enterprise/2.15/articles/dismissing-a-pull-request-review": "/ja/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/ja/enterprise/2.15/articles/distributing-large-binaries": "/ja/enterprise/2.15/user/articles/distributing-large-binaries", - "/ja/enterprise/2.15/articles/documenting-your-project-with-wikis": "/ja/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/ja/enterprise/2.15/articles/duplicating-a-repository": "/ja/enterprise/2.15/user/articles/duplicating-a-repository", - "/ja/enterprise/2.15/articles/editing-a-label": "/ja/enterprise/2.15/user/articles/editing-a-label", - "/ja/enterprise/2.15/articles/editing-a-project-board": "/ja/enterprise/2.15/user/articles/editing-a-project-board", - "/ja/enterprise/2.15/articles/editing-a-saved-reply": "/ja/enterprise/2.15/user/articles/editing-a-saved-reply", - "/ja/enterprise/2.15/articles/editing-and-deleting-releases": "/ja/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/ja/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/ja/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/ja/enterprise/2.15/articles/editing-files-in-another-users-repository": "/ja/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/ja/enterprise/2.15/articles/editing-files-in-your-repository": "/ja/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/ja/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/ja/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/ja/enterprise/2.15/articles/editing-wiki-content": "/ja/enterprise/2.15/user/articles/editing-wiki-content", - "/ja/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.15/articles/enabling-branch-restrictions": "/ja/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/ja/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/ja/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/ja/enterprise/2.15/articles/enabling-required-commit-signing": "/ja/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/ja/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.15/articles/enabling-required-status-checks": "/ja/enterprise/2.15/user/articles/enabling-required-status-checks", - "/ja/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/ja/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/ja/enterprise/2.15/articles/error-bad-file-number": "/ja/enterprise/2.15/user/articles/error-bad-file-number", - "/ja/enterprise/2.15/articles/error-key-already-in-use": "/ja/enterprise/2.15/user/articles/error-key-already-in-use", - "/ja/enterprise/2.15/articles/error-permission-denied-publickey": "/ja/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/ja/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/ja/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/ja/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/ja/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/ja/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/ja/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/ja/enterprise/2.15/articles/error-repository-not-found": "/ja/enterprise/2.15/user/articles/error-repository-not-found", - "/ja/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/ja/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/ja/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/ja/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/ja/enterprise/2.15/articles/exploring-projects-on-github": "/ja/enterprise/2.15/user/articles/exploring-projects-on-github", - "/ja/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/ja/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/ja/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/ja/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/ja/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/ja/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/ja/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/ja/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/ja/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/ja/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/ja/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/ja/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/ja/enterprise/2.15/articles/finding-files-on-github": "/ja/enterprise/2.15/user/articles/finding-files-on-github", - "/ja/enterprise/2.15/articles/finding-information-in-a-repository": "/ja/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/ja/enterprise/2.15/articles/following-people": "/ja/enterprise/2.15/user/articles/following-people", - "/ja/enterprise/2.15/articles/fork-a-repo": "/ja/enterprise/2.15/user/articles/fork-a-repo", - "/ja/enterprise/2.15/articles/forking-and-cloning-gists": "/ja/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/ja/enterprise/2.15/articles/generating-a-new-gpg-key": "/ja/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/ja/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/ja/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/ja/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/ja/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/ja/enterprise/2.15/articles/getting-permanent-links-to-files": "/ja/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/ja/enterprise/2.15/articles/getting-started-with-git-and-github": "/ja/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/ja/enterprise/2.15/articles/getting-started-with-github-pages": "/ja/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/ja/enterprise/2.15/articles/getting-started-with-notifications": "/ja/enterprise/2.15/user/articles/getting-started-with-notifications", - "/ja/enterprise/2.15/articles/getting-started-with-searching-on-github": "/ja/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/ja/enterprise/2.15/articles/getting-started-with-the-api": "/ja/enterprise/2.15/user/articles/getting-started-with-the-api", - "/ja/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/ja/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/ja/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/ja/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/ja/enterprise/2.15/articles/git-and-github-learning-resources": "/ja/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/ja/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/ja/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/ja/enterprise/2.15/articles/git-cheatsheet": "/ja/enterprise/2.15/user/articles/git-cheatsheet", - "/ja/enterprise/2.15/articles/git-workflows": "/ja/enterprise/2.15/user/articles/git-workflows", - "/ja/enterprise/2.15/articles/github-flow": "/ja/enterprise/2.15/user/articles/github-flow", - "/ja/enterprise/2.15/articles/github-glossary": "/ja/enterprise/2.15/user/articles/github-glossary", - "/ja/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/ja/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/ja/enterprise/2.15/articles/https-cloning-errors": "/ja/enterprise/2.15/user/articles/https-cloning-errors", - "/ja/enterprise/2.15/articles/ignoring-files": "/ja/enterprise/2.15/user/articles/ignoring-files", - "/ja/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/ja/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/ja/enterprise/2.15/articles/importing-source-code-to-github": "/ja/enterprise/2.15/user/articles/importing-source-code-to-github", - "/ja/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/ja/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/ja/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/ja/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/ja/enterprise/2.15/articles/installing-git-large-file-storage": "/ja/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/ja/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/ja/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/ja/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/ja/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/ja/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/ja/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/ja/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/ja/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/ja/enterprise/2.15/articles/keeping-your-organization-secure": "/ja/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/ja/enterprise/2.15/articles/keyboard-shortcuts": "/ja/enterprise/2.15/user/articles/keyboard-shortcuts", - "/ja/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/learning-about-git": "/ja/enterprise/2.15/user/articles/learning-about-git", - "/ja/enterprise/2.15/articles/learning-about-github": "/ja/enterprise/2.15/user/articles/learning-about-github", - "/ja/enterprise/2.15/articles/licensing-a-repository": "/ja/enterprise/2.15/user/articles/licensing-a-repository", - "/ja/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/ja/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/ja/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/ja/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/ja/enterprise/2.15/articles/linking-to-releases": "/ja/enterprise/2.15/user/articles/linking-to-releases", - "/ja/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/ja/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/ja/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/ja/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/ja/enterprise/2.15/articles/locking-conversations": "/ja/enterprise/2.15/user/articles/locking-conversations", - "/ja/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/ja/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/ja/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/ja/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/ja/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/ja/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/ja/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/ja/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/ja/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/ja/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/ja/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/ja/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/ja/enterprise/2.15/articles/managing-branches-in-your-repository": "/ja/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/ja/enterprise/2.15/articles/managing-commit-signature-verification": "/ja/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/ja/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/ja/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/ja/enterprise/2.15/articles/managing-disruptive-comments": "/ja/enterprise/2.15/user/articles/managing-disruptive-comments", - "/ja/enterprise/2.15/articles/managing-email-preferences": "/ja/enterprise/2.15/user/articles/managing-email-preferences", - "/ja/enterprise/2.15/articles/managing-files-on-github": "/ja/enterprise/2.15/user/articles/managing-files-on-github", - "/ja/enterprise/2.15/articles/managing-files-using-the-command-line": "/ja/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/ja/enterprise/2.15/articles/managing-membership-in-your-organization": "/ja/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/ja/enterprise/2.15/articles/managing-organization-settings": "/ja/enterprise/2.15/user/articles/managing-organization-settings", - "/ja/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/ja/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/ja/enterprise/2.15/articles/managing-project-boards": "/ja/enterprise/2.15/user/articles/managing-project-boards", - "/ja/enterprise/2.15/articles/managing-releases-in-a-repository": "/ja/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/ja/enterprise/2.15/articles/managing-remote-repositories": "/ja/enterprise/2.15/user/articles/managing-remote-repositories", - "/ja/enterprise/2.15/articles/managing-repository-settings": "/ja/enterprise/2.15/user/articles/managing-repository-settings", - "/ja/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/ja/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/ja/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/ja/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/ja/enterprise/2.15/articles/managing-user-account-settings": "/ja/enterprise/2.15/user/articles/managing-user-account-settings", - "/ja/enterprise/2.15/articles/managing-your-membership-in-organizations": "/ja/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/ja/enterprise/2.15/articles/managing-your-notifications": "/ja/enterprise/2.15/user/articles/managing-your-notifications", - "/ja/enterprise/2.15/articles/managing-your-work-with-issues": "/ja/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/ja/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/ja/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/ja/enterprise/2.15/articles/mapping-geojson-files-on-github": "/ja/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/ja/enterprise/2.15/articles/marking-notifications-as-read": "/ja/enterprise/2.15/user/articles/marking-notifications-as-read", - "/ja/enterprise/2.15/articles/merging-a-pull-request": "/ja/enterprise/2.15/user/articles/merging-a-pull-request", - "/ja/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/ja/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/ja/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/ja/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/ja/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/ja/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/ja/enterprise/2.15/articles/moderating-comments-and-conversations": "/ja/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/ja/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/ja/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/ja/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/ja/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/ja/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/ja/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/ja/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/ja/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/ja/enterprise/2.15/articles/opening-an-issue-from-code": "/ja/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/ja/enterprise/2.15/articles/organizing-information-with-tables": "/ja/enterprise/2.15/user/articles/organizing-information-with-tables", - "/ja/enterprise/2.15/articles/organizing-members-into-teams": "/ja/enterprise/2.15/user/articles/organizing-members-into-teams", - "/ja/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/ja/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/ja/enterprise/2.15/articles/permission-levels-for-an-organization": "/ja/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/ja/enterprise/2.15/articles/personalizing-your-profile": "/ja/enterprise/2.15/user/articles/personalizing-your-profile", - "/ja/enterprise/2.15/articles/pinning-a-team-discussion": "/ja/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/ja/enterprise/2.15/articles/pinning-items-to-your-profile": "/ja/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/ja/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/ja/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.15/articles/preventing-unauthorized-access": "/ja/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/ja/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/ja/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/ja/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/ja/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/ja/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/ja/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/ja/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/ja/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/ja/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/ja/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/ja/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/ja/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/ja/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/ja/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/ja/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/ja/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/ja/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/ja/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/ja/enterprise/2.15/articles/remembering-your-github-username-or-email": "/ja/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/ja/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/ja/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/ja/enterprise/2.15/articles/removing-a-member-from-your-organization": "/ja/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/ja/enterprise/2.15/articles/removing-a-remote": "/ja/enterprise/2.15/user/articles/removing-a-remote", - "/ja/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/ja/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/ja/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/ja/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/ja/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/ja/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/ja/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/ja/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/ja/enterprise/2.15/articles/removing-organization-members-from-a-team": "/ja/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/ja/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/ja/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/ja/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/ja/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/ja/enterprise/2.15/articles/removing-yourself-from-an-organization": "/ja/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/ja/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/ja/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/ja/enterprise/2.15/articles/renaming-a-file": "/ja/enterprise/2.15/user/articles/renaming-a-file", - "/ja/enterprise/2.15/articles/renaming-a-remote": "/ja/enterprise/2.15/user/articles/renaming-a-remote", - "/ja/enterprise/2.15/articles/renaming-a-repository": "/ja/enterprise/2.15/user/articles/renaming-a-repository", - "/ja/enterprise/2.15/articles/renaming-a-team": "/ja/enterprise/2.15/user/articles/renaming-a-team", - "/ja/enterprise/2.15/articles/renaming-an-organization": "/ja/enterprise/2.15/user/articles/renaming-an-organization", - "/ja/enterprise/2.15/articles/rendering-and-diffing-images": "/ja/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/ja/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/ja/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/ja/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/ja/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/ja/enterprise/2.15/articles/rendering-pdf-documents": "/ja/enterprise/2.15/user/articles/rendering-pdf-documents", - "/ja/enterprise/2.15/articles/reopening-a-closed-project-board": "/ja/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/ja/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/ja/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/ja/enterprise/2.15/articles/requesting-a-pull-request-review": "/ja/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/ja/enterprise/2.15/articles/requesting-to-add-a-child-team": "/ja/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/ja/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/ja/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/ja/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/ja/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/ja/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/ja/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/ja/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/ja/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/ja/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/ja/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/ja/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/ja/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.15/articles/reverting-a-pull-request": "/ja/enterprise/2.15/user/articles/reverting-a-pull-request", - "/ja/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/ja/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/ja/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/ja/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/ja/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/ja/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/ja/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/ja/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/ja/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/ja/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/ja/enterprise/2.15/articles/reviewing-your-deploy-keys": "/ja/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/ja/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/ja/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/ja/enterprise/2.15/articles/reviewing-your-security-log": "/ja/enterprise/2.15/user/articles/reviewing-your-security-log", - "/ja/enterprise/2.15/articles/reviewing-your-ssh-keys": "/ja/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/ja/enterprise/2.15/articles/saving-repositories-with-stars": "/ja/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/ja/enterprise/2.15/articles/searching-code": "/ja/enterprise/2.15/user/articles/searching-code", - "/ja/enterprise/2.15/articles/searching-commits": "/ja/enterprise/2.15/user/articles/searching-commits", - "/ja/enterprise/2.15/articles/searching-for-repositories": "/ja/enterprise/2.15/user/articles/searching-for-repositories", - "/ja/enterprise/2.15/articles/searching-in-forks": "/ja/enterprise/2.15/user/articles/searching-in-forks", - "/ja/enterprise/2.15/articles/searching-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/searching-on-github": "/ja/enterprise/2.15/user/articles/searching-on-github", - "/ja/enterprise/2.15/articles/searching-topics": "/ja/enterprise/2.15/user/articles/searching-topics", - "/ja/enterprise/2.15/articles/searching-users": "/ja/enterprise/2.15/user/articles/searching-users", - "/ja/enterprise/2.15/articles/searching-wikis": "/ja/enterprise/2.15/user/articles/searching-wikis", - "/ja/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/ja/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/ja/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/ja/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/ja/enterprise/2.15/articles/set-up-git": "/ja/enterprise/2.15/user/articles/set-up-git", - "/ja/enterprise/2.15/articles/setting-a-backup-email-address": "/ja/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/ja/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/ja/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/ja/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/ja/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/ja/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/ja/enterprise/2.15/articles/setting-repository-visibility": "/ja/enterprise/2.15/user/articles/setting-repository-visibility", - "/ja/enterprise/2.15/articles/setting-the-default-branch": "/ja/enterprise/2.15/user/articles/setting-the-default-branch", - "/ja/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/ja/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/ja/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/ja/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/ja/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/ja/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/ja/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/ja/enterprise/2.15/articles/setting-your-commit-email-address": "/ja/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/ja/enterprise/2.15/articles/setting-your-teams-profile-picture": "/ja/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/ja/enterprise/2.15/articles/setting-your-username-in-git": "/ja/enterprise/2.15/user/articles/setting-your-username-in-git", - "/ja/enterprise/2.15/articles/sharing-filters": "/ja/enterprise/2.15/user/articles/sharing-filters", - "/ja/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/ja/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/ja/enterprise/2.15/articles/signing-commits": "/ja/enterprise/2.15/user/articles/signing-commits", - "/ja/enterprise/2.15/articles/signing-tags": "/ja/enterprise/2.15/user/articles/signing-tags", - "/ja/enterprise/2.15/articles/signing-up-for-github": "/ja/enterprise/2.15/user/articles/signing-up-for-github", - "/ja/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/sorting-search-results": "/ja/enterprise/2.15/user/articles/sorting-search-results", - "/ja/enterprise/2.15/articles/source-code-migration-tools": "/ja/enterprise/2.15/user/articles/source-code-migration-tools", - "/ja/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/ja/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/ja/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/ja/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/ja/enterprise/2.15/articles/subversion-properties-supported-by-github": "/ja/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/ja/enterprise/2.15/articles/sudo-mode": "/ja/enterprise/2.15/user/articles/sudo-mode", - "/ja/enterprise/2.15/articles/support-for-subversion-clients": "/ja/enterprise/2.15/user/articles/support-for-subversion-clients", - "/ja/enterprise/2.15/articles/supported-browsers": "/ja/enterprise/2.15/user/articles/supported-browsers", - "/ja/enterprise/2.15/articles/syncing-a-fork": "/ja/enterprise/2.15/user/articles/syncing-a-fork", - "/ja/enterprise/2.15/articles/telling-git-about-your-signing-key": "/ja/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/ja/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/ja/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/ja/enterprise/2.15/articles/testing-your-ssh-connection": "/ja/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/ja/enterprise/2.15/articles/tracking-changes-in-a-comment": "/ja/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/ja/enterprise/2.15/articles/tracking-changes-in-a-file": "/ja/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/ja/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/ja/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/ja/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/ja/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/ja/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/ja/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/ja/enterprise/2.15/articles/transferring-a-repository": "/ja/enterprise/2.15/user/articles/transferring-a-repository", - "/ja/enterprise/2.15/articles/transferring-organization-ownership": "/ja/enterprise/2.15/user/articles/transferring-organization-ownership", - "/ja/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/ja/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/ja/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/ja/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/ja/enterprise/2.15/articles/troubleshooting-commits": "/ja/enterprise/2.15/user/articles/troubleshooting-commits", - "/ja/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.15/articles/troubleshooting-search-queries": "/ja/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/ja/enterprise/2.15/articles/troubleshooting-ssh": "/ja/enterprise/2.15/user/articles/troubleshooting-ssh", - "/ja/enterprise/2.15/articles/types-of-github-accounts": "/ja/enterprise/2.15/user/articles/types-of-github-accounts", - "/ja/enterprise/2.15/articles/types-of-required-status-checks": "/ja/enterprise/2.15/user/articles/types-of-required-status-checks", - "/ja/enterprise/2.15/articles/understanding-connections-between-repositories": "/ja/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/ja/enterprise/2.15/articles/understanding-the-search-syntax": "/ja/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/ja/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/ja/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/ja/enterprise/2.15/articles/updating-an-expired-gpg-key": "/ja/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/ja/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/ja/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/ja/enterprise/2.15/articles/updating-your-github-access-credentials": "/ja/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/ja/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/ja/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/ja/enterprise/2.15/articles/using-advanced-git-commands": "/ja/enterprise/2.15/user/articles/using-advanced-git-commands", - "/ja/enterprise/2.15/articles/using-common-git-commands": "/ja/enterprise/2.15/user/articles/using-common-git-commands", - "/ja/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/ja/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/ja/enterprise/2.15/articles/using-github": "/ja/enterprise/2.15/user/articles/using-github", - "/ja/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/ja/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/ja/enterprise/2.15/articles/using-saved-replies": "/ja/enterprise/2.15/user/articles/using-saved-replies", - "/ja/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/versioning-large-files": "/ja/enterprise/2.15/user/articles/versioning-large-files", - "/ja/enterprise/2.15/articles/viewing-a-projects-contributors": "/ja/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/ja/enterprise/2.15/articles/viewing-a-pull-request-review": "/ja/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/ja/enterprise/2.15/articles/viewing-a-repositorys-network": "/ja/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/ja/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/ja/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/ja/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/ja/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/ja/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/ja/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/ja/enterprise/2.15/articles/viewing-and-comparing-commits": "/ja/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/ja/enterprise/2.15/articles/viewing-branches-in-your-repository": "/ja/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/ja/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/ja/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/ja/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/ja/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/ja/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/ja/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/ja/enterprise/2.15/articles/viewing-your-milestones-progress": "/ja/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/ja/enterprise/2.15/articles/viewing-your-repositorys-tags": "/ja/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/ja/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/ja/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/ja/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/ja/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/ja/enterprise/2.15/articles/watching-and-unwatching-repositories": "/ja/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/ja/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/ja/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/ja/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/ja/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/ja/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/ja/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/ja/enterprise/2.15/articles/which-remote-url-should-i-use": "/ja/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/ja/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/ja/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/ja/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/ja/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/ja/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/ja/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/ja/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/ja/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/ja/enterprise/2.15/articles/working-with-advanced-formatting": "/ja/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/ja/enterprise/2.15/articles/working-with-forks": "/ja/enterprise/2.15/user/articles/working-with-forks", - "/ja/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/ja/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/ja/enterprise/2.15/articles/working-with-large-files": "/ja/enterprise/2.15/user/articles/working-with-large-files", - "/ja/enterprise/2.15/articles/working-with-non-code-files": "/ja/enterprise/2.15/user/articles/working-with-non-code-files", - "/ja/enterprise/2.15/articles/working-with-pre-receive-hooks": "/ja/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/ja/enterprise/2.15/articles/working-with-saved-replies": "/ja/enterprise/2.15/user/articles/working-with-saved-replies", - "/ja/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/ja/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/ja/enterprise/2.15/articles/working-with-subversion-on-github": "/ja/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/ja/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/ja/enterprise/2.15/user/categories/administering-a-repository", - "/ja/enterprise/2.15/categories/administering-a-repository": "/ja/enterprise/2.15/user/categories/administering-a-repository", - "/ja/enterprise/2.15/categories/authenticating-to-github": "/ja/enterprise/2.15/user/categories/authenticating-to-github", - "/ja/enterprise/2.15/categories/building-a-strong-community": "/ja/enterprise/2.15/user/categories/building-a-strong-community", - "/ja/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/ja/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/ja/enterprise/2.15/categories/committing-changes-to-your-project": "/ja/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/ja/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/ja/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/ja/enterprise/2.15/categories/extending-github": "/ja/enterprise/2.15/user/categories/extending-github", - "/ja/enterprise/2.15/categories/getting-started-with-github": "/ja/enterprise/2.15/user/categories/getting-started-with-github", - "/ja/enterprise/2.15/categories/importing-your-projects-to-github": "/ja/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/ja/enterprise/2.15/categories/managing-files-in-a-repository": "/ja/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/ja/enterprise/2.15/categories/managing-large-files": "/ja/enterprise/2.15/user/categories/managing-large-files", - "/ja/enterprise/2.15/categories/managing-your-work-on-github": "/ja/enterprise/2.15/user/categories/managing-your-work-on-github", - "/ja/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/ja/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/ja/enterprise/2.15/categories/searching-for-information-on-github": "/ja/enterprise/2.15/user/categories/searching-for-information-on-github", - "/ja/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/ja/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/ja/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/ja/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/ja/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/ja/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/ja/enterprise/2.15/categories/using-git": "/ja/enterprise/2.15/user/categories/using-git", - "/ja/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/ja/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/ja/enterprise/2.15/categories/working-with-github-pages": "/ja/enterprise/2.15/user/categories/working-with-github-pages", - "/ja/enterprise/2.15/categories/writing-on-github": "/ja/enterprise/2.15/user/categories/writing-on-github", - "/pt/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/pt/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/pt/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/pt/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/pt/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/pt/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/pt/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/pt/enterprise/2.15/admin/articles/using-github-task-runner", - "/pt/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/pt/enterprise/2.15/admin/clustering/about-cluster-nodes", - "/pt/enterprise/2.15/admin/guides/clustering/clustering-overview": "/pt/enterprise/2.15/admin/clustering/clustering-overview", - "/pt/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/pt/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/pt/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/pt/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", - "/pt/enterprise/2.15/admin/guides/clustering": "/pt/enterprise/2.15/admin/clustering", - "/pt/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/pt/enterprise/2.15/admin/clustering/initializing-the-cluster", - "/pt/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/pt/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", - "/pt/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/pt/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", - "/pt/enterprise/2.15/admin/guides/clustering/network-configuration": "/pt/enterprise/2.15/admin/clustering/network-configuration", - "/pt/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/pt/enterprise/2.15/admin/clustering/replacing-a-cluster-node", - "/pt/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/pt/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", - "/pt/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/pt/enterprise/2.15/admin/clustering/upgrading-a-cluster", - "/pt/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/pt/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", - "/pt/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/pt/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/pt/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/pt/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/pt/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/pt/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/pt/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/pt/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/pt/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/pt/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", - "/pt/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/pt/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/pt/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/pt/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", - "/pt/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/pt/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", - "/pt/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/pt/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/pt/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/pt/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/pt/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/pt/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", - "/pt/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/pt/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/pt/enterprise/2.15/admin/guides/developer-workflow": "/pt/enterprise/2.15/admin/developer-workflow", - "/pt/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/pt/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/pt/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/pt/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", - "/pt/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/pt/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", - "/pt/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/pt/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/pt/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/pt/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/pt/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/pt/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", - "/pt/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/pt/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/pt/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/pt/enterprise/2.15/admin/guides/enterprise-support": "/pt/enterprise/2.15/admin/enterprise-support", - "/pt/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/pt/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", - "/pt/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/pt/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", - "/pt/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/pt/enterprise/2.15/admin/enterprise-support/reaching-github-support", - "/pt/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/pt/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", - "/pt/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/pt/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", - "/pt/enterprise/2.15/admin/guides": "/pt/enterprise/2.15/admin", - "/pt/enterprise/2.15/admin/guides/installation/about-geo-replication": "/pt/enterprise/2.15/admin/installation/about-geo-replication", - "/pt/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/pt/enterprise/2.15/admin/installation/about-high-availability-configuration", - "/pt/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/pt/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", - "/pt/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/pt/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", - "/pt/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/pt/enterprise/2.15/admin/installation/accessing-the-management-console", - "/pt/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/pt/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", - "/pt/enterprise/2.15/admin/guides/installation/activity-dashboard": "/pt/enterprise/2.15/admin/installation/activity-dashboard", - "/pt/enterprise/2.15/admin/guides/installation/audit-logging": "/pt/enterprise/2.15/admin/installation/audit-logging", - "/pt/enterprise/2.15/admin/guides/installation/audited-actions": "/pt/enterprise/2.15/admin/installation/audited-actions", - "/pt/enterprise/2.15/admin/guides/installation/command-line-utilities": "/pt/enterprise/2.15/admin/installation/command-line-utilities", - "/pt/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/pt/enterprise/2.15/admin/installation/configuring-a-hostname", - "/pt/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/pt/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", - "/pt/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/pt/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", - "/pt/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/pt/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", - "/pt/enterprise/2.15/admin/guides/installation/configuring-collectd": "/pt/enterprise/2.15/admin/installation/configuring-collectd", - "/pt/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/pt/enterprise/2.15/admin/installation/configuring-dns-nameservers", - "/pt/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/pt/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/pt/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/pt/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/pt/enterprise/2.15/admin/installation/configuring-git-large-file-storage", - "/pt/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/pt/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/pt/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/pt/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", - "/pt/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/pt/enterprise/2.15/admin/installation/configuring-rate-limits", - "/pt/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/pt/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/pt/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/pt/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", - "/pt/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/pt/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/pt/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/pt/enterprise/2.15/admin/installation/configuring-time-synchronization", - "/pt/enterprise/2.15/admin/guides/installation/configuring-tls": "/pt/enterprise/2.15/admin/installation/configuring-tls", - "/pt/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/pt/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/pt/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/pt/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/pt/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/pt/enterprise/2.15/admin/installation/creating-a-high-availability-replica", - "/pt/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/pt/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/pt/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/pt/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/pt/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", - "/pt/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/pt/enterprise/2.15/admin/installation/enabling-automatic-update-checks", - "/pt/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/pt/enterprise/2.15/admin/installation/enabling-private-mode", - "/pt/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/pt/enterprise/2.15/admin/installation/enabling-subdomain-isolation", - "/pt/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/pt/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/pt/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/pt/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/pt/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/pt/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", - "/pt/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/pt/enterprise/2.15/admin/installation/increasing-storage-capacity", - "/pt/enterprise/2.15/admin/guides/installation": "/pt/enterprise/2.15/admin/installation", - "/pt/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/pt/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", - "/pt/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/pt/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", - "/pt/enterprise/2.15/admin/guides/installation/log-forwarding": "/pt/enterprise/2.15/admin/installation/log-forwarding", - "/pt/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/pt/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/pt/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/pt/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", - "/pt/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/pt/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/pt/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/pt/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/pt/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/pt/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/pt/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/pt/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/pt/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/pt/enterprise/2.15/admin/installation/monitoring-using-snmp", - "/pt/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/pt/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/pt/enterprise/2.15/admin/guides/installation/network-ports": "/pt/enterprise/2.15/admin/installation/network-ports", - "/pt/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/pt/enterprise/2.15/admin/installation/recommended-alert-thresholds", - "/pt/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/pt/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", - "/pt/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/pt/enterprise/2.15/admin/installation/removing-a-high-availability-replica", - "/pt/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/pt/enterprise/2.15/admin/installation/searching-the-audit-log", - "/pt/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/pt/enterprise/2.15/admin/installation/setting-git-push-limits", - "/pt/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/pt/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", - "/pt/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/pt/enterprise/2.15/admin/installation/setting-up-a-staging-instance", - "/pt/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/pt/enterprise/2.15/admin/installation/setting-up-external-monitoring", - "/pt/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/pt/enterprise/2.15/admin/installation/site-admin-dashboard", - "/pt/enterprise/2.15/admin/guides/installation/system-overview": "/pt/enterprise/2.15/admin/installation/system-overview", - "/pt/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/pt/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", - "/pt/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/pt/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/pt/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/pt/enterprise/2.15/admin/installation/upgrade-requirements", - "/pt/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/pt/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/pt/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/pt/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/pt/enterprise/2.15/admin/installation/validating-your-domain-settings", - "/pt/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/pt/enterprise/2.15/admin/installation/viewing-push-logs", - "/pt/enterprise/2.15/admin/guides/migrations/about-migrations": "/pt/enterprise/2.15/admin/migrations/about-migrations", - "/pt/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/pt/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/pt/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/pt/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/pt/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", - "/pt/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/pt/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/pt/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/pt/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/pt/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/pt/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", - "/pt/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/pt/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", - "/pt/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/pt/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/migrations": "/pt/enterprise/2.15/admin/migrations", - "/pt/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/pt/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/pt/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/pt/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", - "/pt/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/pt/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/pt/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/pt/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/pt/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/pt/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", - "/pt/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/pt/enterprise/2.15/admin/migrations/reviewing-migration-data", - "/pt/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/pt/enterprise/2.15/admin/user-management/about-global-webhooks", - "/pt/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/pt/enterprise/2.15/admin/user-management/adding-people-to-teams", - "/pt/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/pt/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/pt/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/pt/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/pt/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/pt/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", - "/pt/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/pt/enterprise/2.15/admin/user-management/auditing-ssh-keys", - "/pt/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/pt/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", - "/pt/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/pt/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/pt/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/pt/enterprise/2.15/admin/user-management/basic-account-settings", - "/pt/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/pt/enterprise/2.15/admin/user-management/best-practices-for-user-security", - "/pt/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/pt/enterprise/2.15/admin/user-management/changing-authentication-methods", - "/pt/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/pt/enterprise/2.15/admin/user-management/configuring-email-for-notifications", - "/pt/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/pt/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", - "/pt/enterprise/2.15/admin/guides/user-management/creating-organizations": "/pt/enterprise/2.15/admin/user-management/creating-organizations", - "/pt/enterprise/2.15/admin/guides/user-management/creating-teams": "/pt/enterprise/2.15/admin/user-management/creating-teams", - "/pt/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/pt/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", - "/pt/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/pt/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", - "/pt/enterprise/2.15/admin/guides/user-management": "/pt/enterprise/2.15/admin/user-management", - "/pt/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/pt/enterprise/2.15/admin/user-management/managing-dormant-users", - "/pt/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/pt/enterprise/2.15/admin/user-management/managing-global-webhooks", - "/pt/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/pt/enterprise/2.15/admin/user-management/organizations-and-teams", - "/pt/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/pt/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/pt/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/pt/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/pt/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/pt/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/pt/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/pt/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", - "/pt/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/pt/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/pt/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/pt/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", - "/pt/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/pt/enterprise/2.15/admin/user-management/rebuilding-contributions-data", - "/pt/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/pt/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", - "/pt/enterprise/2.15/admin/guides/user-management/repositories": "/pt/enterprise/2.15/admin/user-management/repositories", - "/pt/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/pt/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/pt/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/pt/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", - "/pt/enterprise/2.15/admin/guides/user-management/user-security": "/pt/enterprise/2.15/admin/user-management/user-security", - "/pt/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/pt/enterprise/2.15/admin/user-management/using-built-in-authentication", - "/pt/enterprise/2.15/admin/guides/user-management/using-cas": "/pt/enterprise/2.15/admin/user-management/using-cas", - "/pt/enterprise/2.15/admin/guides/user-management/using-ldap": "/pt/enterprise/2.15/admin/user-management/using-ldap", - "/pt/enterprise/2.15/admin/guides/user-management/using-saml": "/pt/enterprise/2.15/admin/user-management/using-saml", - "/pt/enterprise/2.15/articles/3d-file-viewer": "/pt/enterprise/2.15/user/articles/3d-file-viewer", - "/pt/enterprise/2.15/articles/about-archiving-repositories": "/pt/enterprise/2.15/user/articles/about-archiving-repositories", - "/pt/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/pt/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/pt/enterprise/2.15/articles/about-automation-for-project-boards": "/pt/enterprise/2.15/user/articles/about-automation-for-project-boards", - "/pt/enterprise/2.15/articles/about-branch-restrictions": "/pt/enterprise/2.15/user/articles/about-branch-restrictions", - "/pt/enterprise/2.15/articles/about-branches": "/pt/enterprise/2.15/user/articles/about-branches", - "/pt/enterprise/2.15/articles/about-code-owners": "/pt/enterprise/2.15/user/articles/about-code-owners", - "/pt/enterprise/2.15/articles/about-collaborative-development-models": "/pt/enterprise/2.15/user/articles/about-collaborative-development-models", - "/pt/enterprise/2.15/articles/about-commit-signature-verification": "/pt/enterprise/2.15/user/articles/about-commit-signature-verification", - "/pt/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/pt/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", - "/pt/enterprise/2.15/articles/about-conversations-on-github": "/pt/enterprise/2.15/user/articles/about-conversations-on-github", - "/pt/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/pt/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", - "/pt/enterprise/2.15/articles/about-email-notifications": "/pt/enterprise/2.15/user/articles/about-email-notifications", - "/pt/enterprise/2.15/articles/about-forks": "/pt/enterprise/2.15/user/articles/about-forks", - "/pt/enterprise/2.15/articles/about-git-large-file-storage": "/pt/enterprise/2.15/user/articles/about-git-large-file-storage", - "/pt/enterprise/2.15/articles/about-git-rebase": "/pt/enterprise/2.15/user/articles/about-git-rebase", - "/pt/enterprise/2.15/articles/about-git-subtree-merges": "/pt/enterprise/2.15/user/articles/about-git-subtree-merges", - "/pt/enterprise/2.15/articles/about-github-pages-and-jekyll": "/pt/enterprise/2.15/user/articles/about-github-pages-and-jekyll", - "/pt/enterprise/2.15/articles/about-github-pages": "/pt/enterprise/2.15/user/articles/about-github-pages", - "/pt/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/pt/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", - "/pt/enterprise/2.15/articles/about-issues": "/pt/enterprise/2.15/user/articles/about-issues", - "/pt/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.15/articles/about-labels": "/pt/enterprise/2.15/user/articles/about-labels", - "/pt/enterprise/2.15/articles/about-merge-conflicts": "/pt/enterprise/2.15/user/articles/about-merge-conflicts", - "/pt/enterprise/2.15/articles/about-merge-methods-on-github": "/pt/enterprise/2.15/user/articles/about-merge-methods-on-github", - "/pt/enterprise/2.15/articles/about-milestones": "/pt/enterprise/2.15/user/articles/about-milestones", - "/pt/enterprise/2.15/articles/about-notifications": "/pt/enterprise/2.15/user/articles/about-notifications", - "/pt/enterprise/2.15/articles/about-organization-membership": "/pt/enterprise/2.15/user/articles/about-organization-membership", - "/pt/enterprise/2.15/articles/about-organizations": "/pt/enterprise/2.15/user/articles/about-organizations", - "/pt/enterprise/2.15/articles/about-project-boards": "/pt/enterprise/2.15/user/articles/about-project-boards", - "/pt/enterprise/2.15/articles/about-protected-branches": "/pt/enterprise/2.15/user/articles/about-protected-branches", - "/pt/enterprise/2.15/articles/about-pull-request-merges": "/pt/enterprise/2.15/user/articles/about-pull-request-merges", - "/pt/enterprise/2.15/articles/about-pull-request-reviews": "/pt/enterprise/2.15/user/articles/about-pull-request-reviews", - "/pt/enterprise/2.15/articles/about-pull-requests": "/pt/enterprise/2.15/user/articles/about-pull-requests", - "/pt/enterprise/2.15/articles/about-readmes": "/pt/enterprise/2.15/user/articles/about-readmes", - "/pt/enterprise/2.15/articles/about-releases": "/pt/enterprise/2.15/user/articles/about-releases", - "/pt/enterprise/2.15/articles/about-remote-repositories": "/pt/enterprise/2.15/user/articles/about-remote-repositories", - "/pt/enterprise/2.15/articles/about-repositories": "/pt/enterprise/2.15/user/articles/about-repositories", - "/pt/enterprise/2.15/articles/about-repository-graphs": "/pt/enterprise/2.15/user/articles/about-repository-graphs", - "/pt/enterprise/2.15/articles/about-repository-languages": "/pt/enterprise/2.15/user/articles/about-repository-languages", - "/pt/enterprise/2.15/articles/about-required-commit-signing": "/pt/enterprise/2.15/user/articles/about-required-commit-signing", - "/pt/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/pt/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.15/articles/about-required-status-checks": "/pt/enterprise/2.15/user/articles/about-required-status-checks", - "/pt/enterprise/2.15/articles/about-saved-replies": "/pt/enterprise/2.15/user/articles/about-saved-replies", - "/pt/enterprise/2.15/articles/about-searching-on-github": "/pt/enterprise/2.15/user/articles/about-searching-on-github", - "/pt/enterprise/2.15/articles/about-ssh": "/pt/enterprise/2.15/user/articles/about-ssh", - "/pt/enterprise/2.15/articles/about-status-checks": "/pt/enterprise/2.15/user/articles/about-status-checks", - "/pt/enterprise/2.15/articles/about-task-lists": "/pt/enterprise/2.15/user/articles/about-task-lists", - "/pt/enterprise/2.15/articles/about-team-discussions": "/pt/enterprise/2.15/user/articles/about-team-discussions", - "/pt/enterprise/2.15/articles/about-teams": "/pt/enterprise/2.15/user/articles/about-teams", - "/pt/enterprise/2.15/articles/about-two-factor-authentication": "/pt/enterprise/2.15/user/articles/about-two-factor-authentication", - "/pt/enterprise/2.15/articles/about-web-notifications": "/pt/enterprise/2.15/user/articles/about-web-notifications", - "/pt/enterprise/2.15/articles/about-webhooks": "/pt/enterprise/2.15/user/articles/about-webhooks", - "/pt/enterprise/2.15/articles/about-wikis": "/pt/enterprise/2.15/user/articles/about-wikis", - "/pt/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/pt/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", - "/pt/enterprise/2.15/articles/about-your-organization-dashboard": "/pt/enterprise/2.15/user/articles/about-your-organization-dashboard", - "/pt/enterprise/2.15/articles/about-your-organizations-news-feed": "/pt/enterprise/2.15/user/articles/about-your-organizations-news-feed", - "/pt/enterprise/2.15/articles/about-your-organizations-profile": "/pt/enterprise/2.15/user/articles/about-your-organizations-profile", - "/pt/enterprise/2.15/articles/about-your-personal-dashboard": "/pt/enterprise/2.15/user/articles/about-your-personal-dashboard", - "/pt/enterprise/2.15/articles/about-your-profile": "/pt/enterprise/2.15/user/articles/about-your-profile", - "/pt/enterprise/2.15/articles/access-permissions-on-github": "/pt/enterprise/2.15/user/articles/access-permissions-on-github", - "/pt/enterprise/2.15/articles/accessing-an-organization": "/pt/enterprise/2.15/user/articles/accessing-an-organization", - "/pt/enterprise/2.15/articles/accessing-basic-repository-data": "/pt/enterprise/2.15/user/articles/accessing-basic-repository-data", - "/pt/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/pt/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", - "/pt/enterprise/2.15/articles/accessing-your-notifications": "/pt/enterprise/2.15/user/articles/accessing-your-notifications", - "/pt/enterprise/2.15/articles/accessing-your-organizations-settings": "/pt/enterprise/2.15/user/articles/accessing-your-organizations-settings", - "/pt/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/pt/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", - "/pt/enterprise/2.15/articles/adding-a-file-to-a-repository": "/pt/enterprise/2.15/user/articles/adding-a-file-to-a-repository", - "/pt/enterprise/2.15/articles/adding-a-license-to-a-repository": "/pt/enterprise/2.15/user/articles/adding-a-license-to-a-repository", - "/pt/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/pt/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", - "/pt/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/pt/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", - "/pt/enterprise/2.15/articles/adding-a-remote": "/pt/enterprise/2.15/user/articles/adding-a-remote", - "/pt/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/pt/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", - "/pt/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/pt/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", - "/pt/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/pt/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/pt/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/pt/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", - "/pt/enterprise/2.15/articles/adding-notes-to-a-project-board": "/pt/enterprise/2.15/user/articles/adding-notes-to-a-project-board", - "/pt/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/pt/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", - "/pt/enterprise/2.15/articles/adding-organization-members-to-a-team": "/pt/enterprise/2.15/user/articles/adding-organization-members-to-a-team", - "/pt/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/pt/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", - "/pt/enterprise/2.15/articles/adding-people-to-your-organization": "/pt/enterprise/2.15/user/articles/adding-people-to-your-organization", - "/pt/enterprise/2.15/articles/adding-support-resources-to-your-project": "/pt/enterprise/2.15/user/articles/adding-support-resources-to-your-project", - "/pt/enterprise/2.15/articles/addressing-merge-conflicts": "/pt/enterprise/2.15/user/articles/addressing-merge-conflicts", - "/pt/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/pt/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/pt/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/pt/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", - "/pt/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/pt/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", - "/pt/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/pt/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", - "/pt/enterprise/2.15/articles/archiving-a-github-repository": "/pt/enterprise/2.15/user/articles/archiving-a-github-repository", - "/pt/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/pt/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", - "/pt/enterprise/2.15/articles/archiving-repositories": "/pt/enterprise/2.15/user/articles/archiving-repositories", - "/pt/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/pt/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", - "/pt/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/pt/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", - "/pt/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/associating-text-editors-with-git": "/pt/enterprise/2.15/user/articles/associating-text-editors-with-git", - "/pt/enterprise/2.15/articles/authorizing-oauth-apps": "/pt/enterprise/2.15/user/articles/authorizing-oauth-apps", - "/pt/enterprise/2.15/articles/autolinked-references-and-urls": "/pt/enterprise/2.15/user/articles/autolinked-references-and-urls", - "/pt/enterprise/2.15/articles/backing-up-a-repository": "/pt/enterprise/2.15/user/articles/backing-up-a-repository", - "/pt/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/pt/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", - "/pt/enterprise/2.15/articles/be-social": "/pt/enterprise/2.15/user/articles/be-social", - "/pt/enterprise/2.15/articles/caching-your-github-password-in-git": "/pt/enterprise/2.15/user/articles/caching-your-github-password-in-git", - "/pt/enterprise/2.15/articles/changing-a-commit-message": "/pt/enterprise/2.15/user/articles/changing-a-commit-message", - "/pt/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/pt/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", - "/pt/enterprise/2.15/articles/changing-a-remotes-url": "/pt/enterprise/2.15/user/articles/changing-a-remotes-url", - "/pt/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/pt/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", - "/pt/enterprise/2.15/articles/changing-author-info": "/pt/enterprise/2.15/user/articles/changing-author-info", - "/pt/enterprise/2.15/articles/changing-project-board-visibility": "/pt/enterprise/2.15/user/articles/changing-project-board-visibility", - "/pt/enterprise/2.15/articles/changing-team-visibility": "/pt/enterprise/2.15/user/articles/changing-team-visibility", - "/pt/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/pt/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", - "/pt/enterprise/2.15/articles/changing-your-github-username": "/pt/enterprise/2.15/user/articles/changing-your-github-username", - "/pt/enterprise/2.15/articles/changing-your-primary-email-address": "/pt/enterprise/2.15/user/articles/changing-your-primary-email-address", - "/pt/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/pt/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", - "/pt/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/pt/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", - "/pt/enterprise/2.15/articles/checking-out-pull-requests-locally": "/pt/enterprise/2.15/user/articles/checking-out-pull-requests-locally", - "/pt/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/pt/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", - "/pt/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/pt/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", - "/pt/enterprise/2.15/articles/classifying-your-repository-with-topics": "/pt/enterprise/2.15/user/articles/classifying-your-repository-with-topics", - "/pt/enterprise/2.15/articles/cloning-a-repository-from-github": "/pt/enterprise/2.15/user/articles/cloning-a-repository-from-github", - "/pt/enterprise/2.15/articles/cloning-a-repository": "/pt/enterprise/2.15/user/articles/cloning-a-repository", - "/pt/enterprise/2.15/articles/closing-a-project-board": "/pt/enterprise/2.15/user/articles/closing-a-project-board", - "/pt/enterprise/2.15/articles/closing-a-pull-request": "/pt/enterprise/2.15/user/articles/closing-a-pull-request", - "/pt/enterprise/2.15/articles/closing-issues-using-keywords": "/pt/enterprise/2.15/user/articles/closing-issues-using-keywords", - "/pt/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/pt/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", - "/pt/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/pt/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", - "/pt/enterprise/2.15/articles/collaborating-with-your-team": "/pt/enterprise/2.15/user/articles/collaborating-with-your-team", - "/pt/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/pt/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", - "/pt/enterprise/2.15/articles/commenting-on-a-pull-request": "/pt/enterprise/2.15/user/articles/commenting-on-a-pull-request", - "/pt/enterprise/2.15/articles/commit-branch-and-tag-labels": "/pt/enterprise/2.15/user/articles/commit-branch-and-tag-labels", - "/pt/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/pt/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", - "/pt/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.15/articles/comparing-commits-across-time": "/pt/enterprise/2.15/user/articles/comparing-commits-across-time", - "/pt/enterprise/2.15/articles/conditions-for-large-files": "/pt/enterprise/2.15/user/articles/conditions-for-large-files", - "/pt/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/pt/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", - "/pt/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/pt/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", - "/pt/enterprise/2.15/articles/configuring-automation-for-project-boards": "/pt/enterprise/2.15/user/articles/configuring-automation-for-project-boards", - "/pt/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.15/articles/configuring-git-large-file-storage": "/pt/enterprise/2.15/user/articles/configuring-git-large-file-storage", - "/pt/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/pt/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", - "/pt/enterprise/2.15/articles/configuring-protected-branches": "/pt/enterprise/2.15/user/articles/configuring-protected-branches", - "/pt/enterprise/2.15/articles/configuring-pull-request-merges": "/pt/enterprise/2.15/user/articles/configuring-pull-request-merges", - "/pt/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/pt/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", - "/pt/enterprise/2.15/articles/configuring-two-factor-authentication": "/pt/enterprise/2.15/user/articles/configuring-two-factor-authentication", - "/pt/enterprise/2.15/articles/connecting-to-github-with-ssh": "/pt/enterprise/2.15/user/articles/connecting-to-github-with-ssh", - "/pt/enterprise/2.15/articles/connecting-with-third-party-applications": "/pt/enterprise/2.15/user/articles/connecting-with-third-party-applications", - "/pt/enterprise/2.15/articles/converting-a-user-into-an-organization": "/pt/enterprise/2.15/user/articles/converting-a-user-into-an-organization", - "/pt/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/pt/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", - "/pt/enterprise/2.15/articles/converting-an-organization-into-a-user": "/pt/enterprise/2.15/user/articles/converting-an-organization-into-a-user", - "/pt/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/pt/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", - "/pt/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/pt/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", - "/pt/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/pt/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", - "/pt/enterprise/2.15/articles/create-a-repo": "/pt/enterprise/2.15/user/articles/create-a-repo", - "/pt/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/pt/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", - "/pt/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/pt/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", - "/pt/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/pt/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", - "/pt/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/pt/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.15/articles/creating-a-github-pages-site": "/pt/enterprise/2.15/user/articles/creating-a-github-pages-site", - "/pt/enterprise/2.15/articles/creating-a-label": "/pt/enterprise/2.15/user/articles/creating-a-label", - "/pt/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/pt/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", - "/pt/enterprise/2.15/articles/creating-a-new-repository": "/pt/enterprise/2.15/user/articles/creating-a-new-repository", - "/pt/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/pt/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", - "/pt/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/pt/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", - "/pt/enterprise/2.15/articles/creating-a-project-board": "/pt/enterprise/2.15/user/articles/creating-a-project-board", - "/pt/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/pt/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", - "/pt/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/pt/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", - "/pt/enterprise/2.15/articles/creating-a-pull-request": "/pt/enterprise/2.15/user/articles/creating-a-pull-request", - "/pt/enterprise/2.15/articles/creating-a-repository-on-github": "/pt/enterprise/2.15/user/articles/creating-a-repository-on-github", - "/pt/enterprise/2.15/articles/creating-a-saved-reply": "/pt/enterprise/2.15/user/articles/creating-a-saved-reply", - "/pt/enterprise/2.15/articles/creating-a-strong-password": "/pt/enterprise/2.15/user/articles/creating-a-strong-password", - "/pt/enterprise/2.15/articles/creating-a-team-discussion": "/pt/enterprise/2.15/user/articles/creating-a-team-discussion", - "/pt/enterprise/2.15/articles/creating-a-team": "/pt/enterprise/2.15/user/articles/creating-a-team", - "/pt/enterprise/2.15/articles/creating-an-issue": "/pt/enterprise/2.15/user/articles/creating-an-issue", - "/pt/enterprise/2.15/articles/creating-an-issues-only-repository": "/pt/enterprise/2.15/user/articles/creating-an-issues-only-repository", - "/pt/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/pt/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", - "/pt/enterprise/2.15/articles/creating-and-editing-commits": "/pt/enterprise/2.15/user/articles/creating-and-editing-commits", - "/pt/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/pt/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", - "/pt/enterprise/2.15/articles/creating-gists": "/pt/enterprise/2.15/user/articles/creating-gists", - "/pt/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/pt/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", - "/pt/enterprise/2.15/articles/creating-new-files": "/pt/enterprise/2.15/user/articles/creating-new-files", - "/pt/enterprise/2.15/articles/creating-releases": "/pt/enterprise/2.15/user/articles/creating-releases", - "/pt/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.15/articles/customizing-your-profile": "/pt/enterprise/2.15/user/articles/customizing-your-profile", - "/pt/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/pt/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", - "/pt/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.15/articles/deleting-a-label": "/pt/enterprise/2.15/user/articles/deleting-a-label", - "/pt/enterprise/2.15/articles/deleting-a-project-board": "/pt/enterprise/2.15/user/articles/deleting-a-project-board", - "/pt/enterprise/2.15/articles/deleting-a-repository": "/pt/enterprise/2.15/user/articles/deleting-a-repository", - "/pt/enterprise/2.15/articles/deleting-a-saved-reply": "/pt/enterprise/2.15/user/articles/deleting-a-saved-reply", - "/pt/enterprise/2.15/articles/deleting-a-team": "/pt/enterprise/2.15/user/articles/deleting-a-team", - "/pt/enterprise/2.15/articles/deleting-an-organization-account": "/pt/enterprise/2.15/user/articles/deleting-an-organization-account", - "/pt/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.15/articles/deleting-files": "/pt/enterprise/2.15/user/articles/deleting-files", - "/pt/enterprise/2.15/articles/deleting-your-user-account": "/pt/enterprise/2.15/user/articles/deleting-your-user-account", - "/pt/enterprise/2.15/articles/differences-between-commit-views": "/pt/enterprise/2.15/user/articles/differences-between-commit-views", - "/pt/enterprise/2.15/articles/disabling-issues": "/pt/enterprise/2.15/user/articles/disabling-issues", - "/pt/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/pt/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", - "/pt/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/pt/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", - "/pt/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/pt/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", - "/pt/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/pt/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", - "/pt/enterprise/2.15/articles/disabling-wikis": "/pt/enterprise/2.15/user/articles/disabling-wikis", - "/pt/enterprise/2.15/articles/dismissing-a-pull-request-review": "/pt/enterprise/2.15/user/articles/dismissing-a-pull-request-review", - "/pt/enterprise/2.15/articles/distributing-large-binaries": "/pt/enterprise/2.15/user/articles/distributing-large-binaries", - "/pt/enterprise/2.15/articles/documenting-your-project-with-wikis": "/pt/enterprise/2.15/user/articles/documenting-your-project-with-wikis", - "/pt/enterprise/2.15/articles/duplicating-a-repository": "/pt/enterprise/2.15/user/articles/duplicating-a-repository", - "/pt/enterprise/2.15/articles/editing-a-label": "/pt/enterprise/2.15/user/articles/editing-a-label", - "/pt/enterprise/2.15/articles/editing-a-project-board": "/pt/enterprise/2.15/user/articles/editing-a-project-board", - "/pt/enterprise/2.15/articles/editing-a-saved-reply": "/pt/enterprise/2.15/user/articles/editing-a-saved-reply", - "/pt/enterprise/2.15/articles/editing-and-deleting-releases": "/pt/enterprise/2.15/user/articles/editing-and-deleting-releases", - "/pt/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/pt/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", - "/pt/enterprise/2.15/articles/editing-files-in-another-users-repository": "/pt/enterprise/2.15/user/articles/editing-files-in-another-users-repository", - "/pt/enterprise/2.15/articles/editing-files-in-your-repository": "/pt/enterprise/2.15/user/articles/editing-files-in-your-repository", - "/pt/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/pt/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", - "/pt/enterprise/2.15/articles/editing-wiki-content": "/pt/enterprise/2.15/user/articles/editing-wiki-content", - "/pt/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.15/articles/enabling-branch-restrictions": "/pt/enterprise/2.15/user/articles/enabling-branch-restrictions", - "/pt/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/pt/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", - "/pt/enterprise/2.15/articles/enabling-required-commit-signing": "/pt/enterprise/2.15/user/articles/enabling-required-commit-signing", - "/pt/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.15/articles/enabling-required-status-checks": "/pt/enterprise/2.15/user/articles/enabling-required-status-checks", - "/pt/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/pt/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", - "/pt/enterprise/2.15/articles/error-bad-file-number": "/pt/enterprise/2.15/user/articles/error-bad-file-number", - "/pt/enterprise/2.15/articles/error-key-already-in-use": "/pt/enterprise/2.15/user/articles/error-key-already-in-use", - "/pt/enterprise/2.15/articles/error-permission-denied-publickey": "/pt/enterprise/2.15/user/articles/error-permission-denied-publickey", - "/pt/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/pt/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", - "/pt/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/pt/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", - "/pt/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/pt/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/pt/enterprise/2.15/articles/error-repository-not-found": "/pt/enterprise/2.15/user/articles/error-repository-not-found", - "/pt/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/pt/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", - "/pt/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/pt/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", - "/pt/enterprise/2.15/articles/exploring-projects-on-github": "/pt/enterprise/2.15/user/articles/exploring-projects-on-github", - "/pt/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/pt/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", - "/pt/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/pt/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", - "/pt/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/pt/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", - "/pt/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/pt/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", - "/pt/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/pt/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", - "/pt/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/pt/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", - "/pt/enterprise/2.15/articles/finding-files-on-github": "/pt/enterprise/2.15/user/articles/finding-files-on-github", - "/pt/enterprise/2.15/articles/finding-information-in-a-repository": "/pt/enterprise/2.15/user/articles/finding-information-in-a-repository", - "/pt/enterprise/2.15/articles/following-people": "/pt/enterprise/2.15/user/articles/following-people", - "/pt/enterprise/2.15/articles/fork-a-repo": "/pt/enterprise/2.15/user/articles/fork-a-repo", - "/pt/enterprise/2.15/articles/forking-and-cloning-gists": "/pt/enterprise/2.15/user/articles/forking-and-cloning-gists", - "/pt/enterprise/2.15/articles/generating-a-new-gpg-key": "/pt/enterprise/2.15/user/articles/generating-a-new-gpg-key", - "/pt/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/pt/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/pt/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/pt/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", - "/pt/enterprise/2.15/articles/getting-permanent-links-to-files": "/pt/enterprise/2.15/user/articles/getting-permanent-links-to-files", - "/pt/enterprise/2.15/articles/getting-started-with-git-and-github": "/pt/enterprise/2.15/user/articles/getting-started-with-git-and-github", - "/pt/enterprise/2.15/articles/getting-started-with-github-pages": "/pt/enterprise/2.15/user/articles/getting-started-with-github-pages", - "/pt/enterprise/2.15/articles/getting-started-with-notifications": "/pt/enterprise/2.15/user/articles/getting-started-with-notifications", - "/pt/enterprise/2.15/articles/getting-started-with-searching-on-github": "/pt/enterprise/2.15/user/articles/getting-started-with-searching-on-github", - "/pt/enterprise/2.15/articles/getting-started-with-the-api": "/pt/enterprise/2.15/user/articles/getting-started-with-the-api", - "/pt/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/pt/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", - "/pt/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/pt/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", - "/pt/enterprise/2.15/articles/git-and-github-learning-resources": "/pt/enterprise/2.15/user/articles/git-and-github-learning-resources", - "/pt/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/pt/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", - "/pt/enterprise/2.15/articles/git-cheatsheet": "/pt/enterprise/2.15/user/articles/git-cheatsheet", - "/pt/enterprise/2.15/articles/git-workflows": "/pt/enterprise/2.15/user/articles/git-workflows", - "/pt/enterprise/2.15/articles/github-flow": "/pt/enterprise/2.15/user/articles/github-flow", - "/pt/enterprise/2.15/articles/github-glossary": "/pt/enterprise/2.15/user/articles/github-glossary", - "/pt/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/pt/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", - "/pt/enterprise/2.15/articles/https-cloning-errors": "/pt/enterprise/2.15/user/articles/https-cloning-errors", - "/pt/enterprise/2.15/articles/ignoring-files": "/pt/enterprise/2.15/user/articles/ignoring-files", - "/pt/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/pt/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", - "/pt/enterprise/2.15/articles/importing-source-code-to-github": "/pt/enterprise/2.15/user/articles/importing-source-code-to-github", - "/pt/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/pt/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", - "/pt/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/pt/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", - "/pt/enterprise/2.15/articles/installing-git-large-file-storage": "/pt/enterprise/2.15/user/articles/installing-git-large-file-storage", - "/pt/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/pt/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", - "/pt/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/pt/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", - "/pt/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/pt/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", - "/pt/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/pt/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", - "/pt/enterprise/2.15/articles/keeping-your-organization-secure": "/pt/enterprise/2.15/user/articles/keeping-your-organization-secure", - "/pt/enterprise/2.15/articles/keyboard-shortcuts": "/pt/enterprise/2.15/user/articles/keyboard-shortcuts", - "/pt/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/learning-about-git": "/pt/enterprise/2.15/user/articles/learning-about-git", - "/pt/enterprise/2.15/articles/learning-about-github": "/pt/enterprise/2.15/user/articles/learning-about-github", - "/pt/enterprise/2.15/articles/licensing-a-repository": "/pt/enterprise/2.15/user/articles/licensing-a-repository", - "/pt/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/pt/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", - "/pt/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/pt/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", - "/pt/enterprise/2.15/articles/linking-to-releases": "/pt/enterprise/2.15/user/articles/linking-to-releases", - "/pt/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/pt/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", - "/pt/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/pt/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", - "/pt/enterprise/2.15/articles/locking-conversations": "/pt/enterprise/2.15/user/articles/locking-conversations", - "/pt/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/pt/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", - "/pt/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/pt/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", - "/pt/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/pt/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", - "/pt/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/pt/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", - "/pt/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/pt/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", - "/pt/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/pt/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", - "/pt/enterprise/2.15/articles/managing-branches-in-your-repository": "/pt/enterprise/2.15/user/articles/managing-branches-in-your-repository", - "/pt/enterprise/2.15/articles/managing-commit-signature-verification": "/pt/enterprise/2.15/user/articles/managing-commit-signature-verification", - "/pt/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/pt/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", - "/pt/enterprise/2.15/articles/managing-disruptive-comments": "/pt/enterprise/2.15/user/articles/managing-disruptive-comments", - "/pt/enterprise/2.15/articles/managing-email-preferences": "/pt/enterprise/2.15/user/articles/managing-email-preferences", - "/pt/enterprise/2.15/articles/managing-files-on-github": "/pt/enterprise/2.15/user/articles/managing-files-on-github", - "/pt/enterprise/2.15/articles/managing-files-using-the-command-line": "/pt/enterprise/2.15/user/articles/managing-files-using-the-command-line", - "/pt/enterprise/2.15/articles/managing-membership-in-your-organization": "/pt/enterprise/2.15/user/articles/managing-membership-in-your-organization", - "/pt/enterprise/2.15/articles/managing-organization-settings": "/pt/enterprise/2.15/user/articles/managing-organization-settings", - "/pt/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/pt/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", - "/pt/enterprise/2.15/articles/managing-project-boards": "/pt/enterprise/2.15/user/articles/managing-project-boards", - "/pt/enterprise/2.15/articles/managing-releases-in-a-repository": "/pt/enterprise/2.15/user/articles/managing-releases-in-a-repository", - "/pt/enterprise/2.15/articles/managing-remote-repositories": "/pt/enterprise/2.15/user/articles/managing-remote-repositories", - "/pt/enterprise/2.15/articles/managing-repository-settings": "/pt/enterprise/2.15/user/articles/managing-repository-settings", - "/pt/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/pt/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", - "/pt/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/pt/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", - "/pt/enterprise/2.15/articles/managing-user-account-settings": "/pt/enterprise/2.15/user/articles/managing-user-account-settings", - "/pt/enterprise/2.15/articles/managing-your-membership-in-organizations": "/pt/enterprise/2.15/user/articles/managing-your-membership-in-organizations", - "/pt/enterprise/2.15/articles/managing-your-notifications": "/pt/enterprise/2.15/user/articles/managing-your-notifications", - "/pt/enterprise/2.15/articles/managing-your-work-with-issues": "/pt/enterprise/2.15/user/articles/managing-your-work-with-issues", - "/pt/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/pt/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", - "/pt/enterprise/2.15/articles/mapping-geojson-files-on-github": "/pt/enterprise/2.15/user/articles/mapping-geojson-files-on-github", - "/pt/enterprise/2.15/articles/marking-notifications-as-read": "/pt/enterprise/2.15/user/articles/marking-notifications-as-read", - "/pt/enterprise/2.15/articles/merging-a-pull-request": "/pt/enterprise/2.15/user/articles/merging-a-pull-request", - "/pt/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/pt/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", - "/pt/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/pt/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", - "/pt/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/pt/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", - "/pt/enterprise/2.15/articles/moderating-comments-and-conversations": "/pt/enterprise/2.15/user/articles/moderating-comments-and-conversations", - "/pt/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/pt/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", - "/pt/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/pt/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", - "/pt/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/pt/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", - "/pt/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/pt/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", - "/pt/enterprise/2.15/articles/opening-an-issue-from-code": "/pt/enterprise/2.15/user/articles/opening-an-issue-from-code", - "/pt/enterprise/2.15/articles/organizing-information-with-tables": "/pt/enterprise/2.15/user/articles/organizing-information-with-tables", - "/pt/enterprise/2.15/articles/organizing-members-into-teams": "/pt/enterprise/2.15/user/articles/organizing-members-into-teams", - "/pt/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/pt/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", - "/pt/enterprise/2.15/articles/permission-levels-for-an-organization": "/pt/enterprise/2.15/user/articles/permission-levels-for-an-organization", - "/pt/enterprise/2.15/articles/personalizing-your-profile": "/pt/enterprise/2.15/user/articles/personalizing-your-profile", - "/pt/enterprise/2.15/articles/pinning-a-team-discussion": "/pt/enterprise/2.15/user/articles/pinning-a-team-discussion", - "/pt/enterprise/2.15/articles/pinning-items-to-your-profile": "/pt/enterprise/2.15/user/articles/pinning-items-to-your-profile", - "/pt/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/pt/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.15/articles/preventing-unauthorized-access": "/pt/enterprise/2.15/user/articles/preventing-unauthorized-access", - "/pt/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/pt/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", - "/pt/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/pt/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", - "/pt/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/pt/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", - "/pt/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/pt/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/pt/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/pt/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", - "/pt/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/pt/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", - "/pt/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/pt/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", - "/pt/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/pt/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", - "/pt/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/pt/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/pt/enterprise/2.15/articles/remembering-your-github-username-or-email": "/pt/enterprise/2.15/user/articles/remembering-your-github-username-or-email", - "/pt/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/pt/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", - "/pt/enterprise/2.15/articles/removing-a-member-from-your-organization": "/pt/enterprise/2.15/user/articles/removing-a-member-from-your-organization", - "/pt/enterprise/2.15/articles/removing-a-remote": "/pt/enterprise/2.15/user/articles/removing-a-remote", - "/pt/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/pt/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", - "/pt/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/pt/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", - "/pt/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/pt/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", - "/pt/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/pt/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", - "/pt/enterprise/2.15/articles/removing-organization-members-from-a-team": "/pt/enterprise/2.15/user/articles/removing-organization-members-from-a-team", - "/pt/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/pt/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", - "/pt/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/pt/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", - "/pt/enterprise/2.15/articles/removing-yourself-from-an-organization": "/pt/enterprise/2.15/user/articles/removing-yourself-from-an-organization", - "/pt/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/pt/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", - "/pt/enterprise/2.15/articles/renaming-a-file": "/pt/enterprise/2.15/user/articles/renaming-a-file", - "/pt/enterprise/2.15/articles/renaming-a-remote": "/pt/enterprise/2.15/user/articles/renaming-a-remote", - "/pt/enterprise/2.15/articles/renaming-a-repository": "/pt/enterprise/2.15/user/articles/renaming-a-repository", - "/pt/enterprise/2.15/articles/renaming-a-team": "/pt/enterprise/2.15/user/articles/renaming-a-team", - "/pt/enterprise/2.15/articles/renaming-an-organization": "/pt/enterprise/2.15/user/articles/renaming-an-organization", - "/pt/enterprise/2.15/articles/rendering-and-diffing-images": "/pt/enterprise/2.15/user/articles/rendering-and-diffing-images", - "/pt/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/pt/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", - "/pt/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/pt/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", - "/pt/enterprise/2.15/articles/rendering-pdf-documents": "/pt/enterprise/2.15/user/articles/rendering-pdf-documents", - "/pt/enterprise/2.15/articles/reopening-a-closed-project-board": "/pt/enterprise/2.15/user/articles/reopening-a-closed-project-board", - "/pt/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/pt/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", - "/pt/enterprise/2.15/articles/requesting-a-pull-request-review": "/pt/enterprise/2.15/user/articles/requesting-a-pull-request-review", - "/pt/enterprise/2.15/articles/requesting-to-add-a-child-team": "/pt/enterprise/2.15/user/articles/requesting-to-add-a-child-team", - "/pt/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/pt/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", - "/pt/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/pt/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/pt/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", - "/pt/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/pt/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", - "/pt/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/pt/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", - "/pt/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/pt/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", - "/pt/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/pt/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.15/articles/reverting-a-pull-request": "/pt/enterprise/2.15/user/articles/reverting-a-pull-request", - "/pt/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/pt/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", - "/pt/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/pt/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", - "/pt/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/pt/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", - "/pt/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/pt/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", - "/pt/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/pt/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", - "/pt/enterprise/2.15/articles/reviewing-your-deploy-keys": "/pt/enterprise/2.15/user/articles/reviewing-your-deploy-keys", - "/pt/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/pt/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", - "/pt/enterprise/2.15/articles/reviewing-your-security-log": "/pt/enterprise/2.15/user/articles/reviewing-your-security-log", - "/pt/enterprise/2.15/articles/reviewing-your-ssh-keys": "/pt/enterprise/2.15/user/articles/reviewing-your-ssh-keys", - "/pt/enterprise/2.15/articles/saving-repositories-with-stars": "/pt/enterprise/2.15/user/articles/saving-repositories-with-stars", - "/pt/enterprise/2.15/articles/searching-code": "/pt/enterprise/2.15/user/articles/searching-code", - "/pt/enterprise/2.15/articles/searching-commits": "/pt/enterprise/2.15/user/articles/searching-commits", - "/pt/enterprise/2.15/articles/searching-for-repositories": "/pt/enterprise/2.15/user/articles/searching-for-repositories", - "/pt/enterprise/2.15/articles/searching-in-forks": "/pt/enterprise/2.15/user/articles/searching-in-forks", - "/pt/enterprise/2.15/articles/searching-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/searching-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/searching-on-github": "/pt/enterprise/2.15/user/articles/searching-on-github", - "/pt/enterprise/2.15/articles/searching-topics": "/pt/enterprise/2.15/user/articles/searching-topics", - "/pt/enterprise/2.15/articles/searching-users": "/pt/enterprise/2.15/user/articles/searching-users", - "/pt/enterprise/2.15/articles/searching-wikis": "/pt/enterprise/2.15/user/articles/searching-wikis", - "/pt/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/pt/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", - "/pt/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/pt/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/pt/enterprise/2.15/articles/set-up-git": "/pt/enterprise/2.15/user/articles/set-up-git", - "/pt/enterprise/2.15/articles/setting-a-backup-email-address": "/pt/enterprise/2.15/user/articles/setting-a-backup-email-address", - "/pt/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/pt/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/pt/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", - "/pt/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/pt/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", - "/pt/enterprise/2.15/articles/setting-repository-visibility": "/pt/enterprise/2.15/user/articles/setting-repository-visibility", - "/pt/enterprise/2.15/articles/setting-the-default-branch": "/pt/enterprise/2.15/user/articles/setting-the-default-branch", - "/pt/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/pt/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/pt/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", - "/pt/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/pt/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", - "/pt/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/pt/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", - "/pt/enterprise/2.15/articles/setting-your-commit-email-address": "/pt/enterprise/2.15/user/articles/setting-your-commit-email-address", - "/pt/enterprise/2.15/articles/setting-your-teams-profile-picture": "/pt/enterprise/2.15/user/articles/setting-your-teams-profile-picture", - "/pt/enterprise/2.15/articles/setting-your-username-in-git": "/pt/enterprise/2.15/user/articles/setting-your-username-in-git", - "/pt/enterprise/2.15/articles/sharing-filters": "/pt/enterprise/2.15/user/articles/sharing-filters", - "/pt/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/pt/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", - "/pt/enterprise/2.15/articles/signing-commits": "/pt/enterprise/2.15/user/articles/signing-commits", - "/pt/enterprise/2.15/articles/signing-tags": "/pt/enterprise/2.15/user/articles/signing-tags", - "/pt/enterprise/2.15/articles/signing-up-for-github": "/pt/enterprise/2.15/user/articles/signing-up-for-github", - "/pt/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/sorting-search-results": "/pt/enterprise/2.15/user/articles/sorting-search-results", - "/pt/enterprise/2.15/articles/source-code-migration-tools": "/pt/enterprise/2.15/user/articles/source-code-migration-tools", - "/pt/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/pt/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", - "/pt/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/pt/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", - "/pt/enterprise/2.15/articles/subversion-properties-supported-by-github": "/pt/enterprise/2.15/user/articles/subversion-properties-supported-by-github", - "/pt/enterprise/2.15/articles/sudo-mode": "/pt/enterprise/2.15/user/articles/sudo-mode", - "/pt/enterprise/2.15/articles/support-for-subversion-clients": "/pt/enterprise/2.15/user/articles/support-for-subversion-clients", - "/pt/enterprise/2.15/articles/supported-browsers": "/pt/enterprise/2.15/user/articles/supported-browsers", - "/pt/enterprise/2.15/articles/syncing-a-fork": "/pt/enterprise/2.15/user/articles/syncing-a-fork", - "/pt/enterprise/2.15/articles/telling-git-about-your-signing-key": "/pt/enterprise/2.15/user/articles/telling-git-about-your-signing-key", - "/pt/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/pt/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", - "/pt/enterprise/2.15/articles/testing-your-ssh-connection": "/pt/enterprise/2.15/user/articles/testing-your-ssh-connection", - "/pt/enterprise/2.15/articles/tracking-changes-in-a-comment": "/pt/enterprise/2.15/user/articles/tracking-changes-in-a-comment", - "/pt/enterprise/2.15/articles/tracking-changes-in-a-file": "/pt/enterprise/2.15/user/articles/tracking-changes-in-a-file", - "/pt/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/pt/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", - "/pt/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/pt/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", - "/pt/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/pt/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", - "/pt/enterprise/2.15/articles/transferring-a-repository": "/pt/enterprise/2.15/user/articles/transferring-a-repository", - "/pt/enterprise/2.15/articles/transferring-organization-ownership": "/pt/enterprise/2.15/user/articles/transferring-organization-ownership", - "/pt/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/pt/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", - "/pt/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/pt/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", - "/pt/enterprise/2.15/articles/troubleshooting-commits": "/pt/enterprise/2.15/user/articles/troubleshooting-commits", - "/pt/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.15/articles/troubleshooting-search-queries": "/pt/enterprise/2.15/user/articles/troubleshooting-search-queries", - "/pt/enterprise/2.15/articles/troubleshooting-ssh": "/pt/enterprise/2.15/user/articles/troubleshooting-ssh", - "/pt/enterprise/2.15/articles/types-of-github-accounts": "/pt/enterprise/2.15/user/articles/types-of-github-accounts", - "/pt/enterprise/2.15/articles/types-of-required-status-checks": "/pt/enterprise/2.15/user/articles/types-of-required-status-checks", - "/pt/enterprise/2.15/articles/understanding-connections-between-repositories": "/pt/enterprise/2.15/user/articles/understanding-connections-between-repositories", - "/pt/enterprise/2.15/articles/understanding-the-search-syntax": "/pt/enterprise/2.15/user/articles/understanding-the-search-syntax", - "/pt/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/pt/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", - "/pt/enterprise/2.15/articles/updating-an-expired-gpg-key": "/pt/enterprise/2.15/user/articles/updating-an-expired-gpg-key", - "/pt/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/pt/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", - "/pt/enterprise/2.15/articles/updating-your-github-access-credentials": "/pt/enterprise/2.15/user/articles/updating-your-github-access-credentials", - "/pt/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/pt/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", - "/pt/enterprise/2.15/articles/using-advanced-git-commands": "/pt/enterprise/2.15/user/articles/using-advanced-git-commands", - "/pt/enterprise/2.15/articles/using-common-git-commands": "/pt/enterprise/2.15/user/articles/using-common-git-commands", - "/pt/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/pt/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", - "/pt/enterprise/2.15/articles/using-github": "/pt/enterprise/2.15/user/articles/using-github", - "/pt/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/pt/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", - "/pt/enterprise/2.15/articles/using-saved-replies": "/pt/enterprise/2.15/user/articles/using-saved-replies", - "/pt/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/versioning-large-files": "/pt/enterprise/2.15/user/articles/versioning-large-files", - "/pt/enterprise/2.15/articles/viewing-a-projects-contributors": "/pt/enterprise/2.15/user/articles/viewing-a-projects-contributors", - "/pt/enterprise/2.15/articles/viewing-a-pull-request-review": "/pt/enterprise/2.15/user/articles/viewing-a-pull-request-review", - "/pt/enterprise/2.15/articles/viewing-a-repositorys-network": "/pt/enterprise/2.15/user/articles/viewing-a-repositorys-network", - "/pt/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/pt/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", - "/pt/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/pt/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", - "/pt/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/pt/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", - "/pt/enterprise/2.15/articles/viewing-and-comparing-commits": "/pt/enterprise/2.15/user/articles/viewing-and-comparing-commits", - "/pt/enterprise/2.15/articles/viewing-branches-in-your-repository": "/pt/enterprise/2.15/user/articles/viewing-branches-in-your-repository", - "/pt/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/pt/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", - "/pt/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/pt/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", - "/pt/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/pt/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/pt/enterprise/2.15/articles/viewing-your-milestones-progress": "/pt/enterprise/2.15/user/articles/viewing-your-milestones-progress", - "/pt/enterprise/2.15/articles/viewing-your-repositorys-tags": "/pt/enterprise/2.15/user/articles/viewing-your-repositorys-tags", - "/pt/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/pt/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", - "/pt/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/pt/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", - "/pt/enterprise/2.15/articles/watching-and-unwatching-repositories": "/pt/enterprise/2.15/user/articles/watching-and-unwatching-repositories", - "/pt/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/pt/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", - "/pt/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/pt/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", - "/pt/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/pt/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/pt/enterprise/2.15/articles/which-remote-url-should-i-use": "/pt/enterprise/2.15/user/articles/which-remote-url-should-i-use", - "/pt/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/pt/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", - "/pt/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/pt/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", - "/pt/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/pt/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", - "/pt/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/pt/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", - "/pt/enterprise/2.15/articles/working-with-advanced-formatting": "/pt/enterprise/2.15/user/articles/working-with-advanced-formatting", - "/pt/enterprise/2.15/articles/working-with-forks": "/pt/enterprise/2.15/user/articles/working-with-forks", - "/pt/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/pt/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", - "/pt/enterprise/2.15/articles/working-with-large-files": "/pt/enterprise/2.15/user/articles/working-with-large-files", - "/pt/enterprise/2.15/articles/working-with-non-code-files": "/pt/enterprise/2.15/user/articles/working-with-non-code-files", - "/pt/enterprise/2.15/articles/working-with-pre-receive-hooks": "/pt/enterprise/2.15/user/articles/working-with-pre-receive-hooks", - "/pt/enterprise/2.15/articles/working-with-saved-replies": "/pt/enterprise/2.15/user/articles/working-with-saved-replies", - "/pt/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/pt/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", - "/pt/enterprise/2.15/articles/working-with-subversion-on-github": "/pt/enterprise/2.15/user/articles/working-with-subversion-on-github", - "/pt/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/pt/enterprise/2.15/user/categories/administering-a-repository", - "/pt/enterprise/2.15/categories/administering-a-repository": "/pt/enterprise/2.15/user/categories/administering-a-repository", - "/pt/enterprise/2.15/categories/authenticating-to-github": "/pt/enterprise/2.15/user/categories/authenticating-to-github", - "/pt/enterprise/2.15/categories/building-a-strong-community": "/pt/enterprise/2.15/user/categories/building-a-strong-community", - "/pt/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/pt/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", - "/pt/enterprise/2.15/categories/committing-changes-to-your-project": "/pt/enterprise/2.15/user/categories/committing-changes-to-your-project", - "/pt/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/pt/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", - "/pt/enterprise/2.15/categories/extending-github": "/pt/enterprise/2.15/user/categories/extending-github", - "/pt/enterprise/2.15/categories/getting-started-with-github": "/pt/enterprise/2.15/user/categories/getting-started-with-github", - "/pt/enterprise/2.15/categories/importing-your-projects-to-github": "/pt/enterprise/2.15/user/categories/importing-your-projects-to-github", - "/pt/enterprise/2.15/categories/managing-files-in-a-repository": "/pt/enterprise/2.15/user/categories/managing-files-in-a-repository", - "/pt/enterprise/2.15/categories/managing-large-files": "/pt/enterprise/2.15/user/categories/managing-large-files", - "/pt/enterprise/2.15/categories/managing-your-work-on-github": "/pt/enterprise/2.15/user/categories/managing-your-work-on-github", - "/pt/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/pt/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", - "/pt/enterprise/2.15/categories/searching-for-information-on-github": "/pt/enterprise/2.15/user/categories/searching-for-information-on-github", - "/pt/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/pt/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", - "/pt/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/pt/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", - "/pt/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/pt/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", - "/pt/enterprise/2.15/categories/using-git": "/pt/enterprise/2.15/user/categories/using-git", - "/pt/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/pt/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", - "/pt/enterprise/2.15/categories/working-with-github-pages": "/pt/enterprise/2.15/user/categories/working-with-github-pages", - "/pt/enterprise/2.15/categories/writing-on-github": "/pt/enterprise/2.15/user/categories/writing-on-github", - "/cn/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/cn/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/cn/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/cn/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/cn/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/cn/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/cn/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/cn/enterprise/2.16/admin/articles/using-github-task-runner", - "/cn/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/cn/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/cn/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/cn/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/cn/enterprise/2.16/admin/guides/clustering/clustering-overview": "/cn/enterprise/2.16/admin/clustering/clustering-overview", - "/cn/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/cn/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/cn/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/cn/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/cn/enterprise/2.16/admin/guides/clustering": "/cn/enterprise/2.16/admin/clustering", - "/cn/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/cn/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/cn/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/cn/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/cn/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/cn/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/cn/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/cn/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/cn/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/cn/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/cn/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/cn/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/cn/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/cn/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/cn/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/cn/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/cn/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/cn/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/cn/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/cn/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/cn/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/cn/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/cn/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/cn/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/cn/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/cn/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/cn/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/cn/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/cn/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/cn/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/cn/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/cn/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/cn/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/cn/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/cn/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/cn/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/cn/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/cn/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/cn/enterprise/2.16/admin/guides/developer-workflow": "/cn/enterprise/2.16/admin/developer-workflow", - "/cn/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/cn/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/cn/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/cn/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/cn/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/cn/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/cn/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/cn/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/cn/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/cn/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/cn/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/cn/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/cn/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/cn/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/cn/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/cn/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/cn/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/cn/enterprise/2.16/admin/guides/enterprise-support": "/cn/enterprise/2.16/admin/enterprise-support", - "/cn/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/cn/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/cn/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/cn/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/cn/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/cn/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/cn/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/cn/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/cn/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/cn/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/cn/enterprise/2.16/admin/guides": "/cn/enterprise/2.16/admin", - "/cn/enterprise/2.16/admin/guides/installation/about-geo-replication": "/cn/enterprise/2.16/admin/installation/about-geo-replication", - "/cn/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/cn/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/cn/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/cn/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/cn/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/cn/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/cn/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/cn/enterprise/2.16/admin/installation/accessing-the-management-console", - "/cn/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/cn/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/cn/enterprise/2.16/admin/guides/installation/activity-dashboard": "/cn/enterprise/2.16/admin/installation/activity-dashboard", - "/cn/enterprise/2.16/admin/guides/installation/audit-logging": "/cn/enterprise/2.16/admin/installation/audit-logging", - "/cn/enterprise/2.16/admin/guides/installation/audited-actions": "/cn/enterprise/2.16/admin/installation/audited-actions", - "/cn/enterprise/2.16/admin/guides/installation/command-line-utilities": "/cn/enterprise/2.16/admin/installation/command-line-utilities", - "/cn/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/cn/enterprise/2.16/admin/installation/configuring-a-hostname", - "/cn/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/cn/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/cn/enterprise/2.16/admin/guides/installation/configuring-applications": "/cn/enterprise/2.16/admin/installation/configuring-applications", - "/cn/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/cn/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/cn/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/cn/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/cn/enterprise/2.16/admin/guides/installation/configuring-collectd": "/cn/enterprise/2.16/admin/installation/configuring-collectd", - "/cn/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/cn/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/cn/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/cn/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/cn/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/cn/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/cn/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/cn/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/cn/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/cn/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/cn/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/cn/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/cn/enterprise/2.16/admin/installation/configuring-rate-limits", - "/cn/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/cn/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/cn/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/cn/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/cn/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/cn/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/cn/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/cn/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/cn/enterprise/2.16/admin/guides/installation/configuring-tls": "/cn/enterprise/2.16/admin/installation/configuring-tls", - "/cn/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/cn/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/cn/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/cn/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/cn/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/cn/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/cn/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/cn/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/cn/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/cn/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/cn/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/cn/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/cn/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/cn/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/cn/enterprise/2.16/admin/installation/enabling-private-mode", - "/cn/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/cn/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/cn/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/cn/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/cn/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/cn/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/cn/enterprise/2.16/admin/guides/installation": "/cn/enterprise/2.16/admin/installation", - "/cn/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/cn/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/cn/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/cn/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/cn/enterprise/2.16/admin/guides/installation/log-forwarding": "/cn/enterprise/2.16/admin/installation/log-forwarding", - "/cn/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/cn/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/cn/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/cn/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/cn/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/cn/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/cn/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/cn/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/cn/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/cn/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/cn/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/cn/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/cn/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/cn/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/cn/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/cn/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/cn/enterprise/2.16/admin/guides/installation/network-ports": "/cn/enterprise/2.16/admin/installation/network-ports", - "/cn/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/cn/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/cn/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/cn/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/cn/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/cn/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/cn/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/cn/enterprise/2.16/admin/installation/searching-the-audit-log", - "/cn/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/cn/enterprise/2.16/admin/installation/setting-git-push-limits", - "/cn/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/cn/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/cn/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/cn/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/cn/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/cn/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/cn/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/cn/enterprise/2.16/admin/installation/site-admin-dashboard", - "/cn/enterprise/2.16/admin/guides/installation/system-overview": "/cn/enterprise/2.16/admin/installation/system-overview", - "/cn/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/cn/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/cn/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/cn/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/cn/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/cn/enterprise/2.16/admin/installation/upgrade-requirements", - "/cn/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/cn/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/cn/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/cn/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/cn/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/cn/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/cn/enterprise/2.16/admin/installation/viewing-push-logs", - "/cn/enterprise/2.16/admin/guides/migrations/about-migrations": "/cn/enterprise/2.16/admin/migrations/about-migrations", - "/cn/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/cn/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/cn/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/cn/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/cn/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/cn/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/cn/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/cn/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/cn/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/cn/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/cn/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/cn/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/cn/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/cn/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/cn/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/migrations": "/cn/enterprise/2.16/admin/migrations", - "/cn/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/cn/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/cn/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/cn/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/cn/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/cn/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/cn/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/cn/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/cn/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/cn/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/cn/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/cn/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/cn/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/cn/enterprise/2.16/admin/user-management/about-global-webhooks", - "/cn/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/cn/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/cn/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/cn/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/cn/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/cn/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/cn/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/cn/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/cn/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/cn/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/cn/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/cn/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/cn/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/cn/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/cn/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/cn/enterprise/2.16/admin/user-management/basic-account-settings", - "/cn/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/cn/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/cn/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/cn/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/cn/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/cn/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/cn/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/cn/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/cn/enterprise/2.16/admin/guides/user-management/creating-organizations": "/cn/enterprise/2.16/admin/user-management/creating-organizations", - "/cn/enterprise/2.16/admin/guides/user-management/creating-teams": "/cn/enterprise/2.16/admin/user-management/creating-teams", - "/cn/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/cn/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/cn/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/cn/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/cn/enterprise/2.16/admin/guides/user-management": "/cn/enterprise/2.16/admin/user-management", - "/cn/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/cn/enterprise/2.16/admin/user-management/managing-dormant-users", - "/cn/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/cn/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/cn/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/cn/enterprise/2.16/admin/user-management/organizations-and-teams", - "/cn/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/cn/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/cn/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/cn/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/cn/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/cn/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/cn/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/cn/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/cn/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/cn/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/cn/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/cn/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/cn/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/cn/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/cn/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/cn/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/cn/enterprise/2.16/admin/guides/user-management/repositories": "/cn/enterprise/2.16/admin/user-management/repositories", - "/cn/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/cn/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/cn/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/cn/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/cn/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/cn/enterprise/2.16/admin/guides/user-management/user-security": "/cn/enterprise/2.16/admin/user-management/user-security", - "/cn/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/cn/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/cn/enterprise/2.16/admin/guides/user-management/using-cas": "/cn/enterprise/2.16/admin/user-management/using-cas", - "/cn/enterprise/2.16/admin/guides/user-management/using-ldap": "/cn/enterprise/2.16/admin/user-management/using-ldap", - "/cn/enterprise/2.16/admin/guides/user-management/using-saml": "/cn/enterprise/2.16/admin/user-management/using-saml", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/cn/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/cn/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/cn/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/cn/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/cn/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/cn/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/cn/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/cn/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/cn/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/cn/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/cn/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/cn/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/cn/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/cn/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/cn/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/cn/enterprise/2.16/user/administering-a-repository/about-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/cn/enterprise/2.16/github/administering-a-repository/about-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/cn/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/cn/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/cn/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/cn/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/cn/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/cn/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/cn/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/cn/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/cn/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/cn/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/cn/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/cn/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/cn/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/cn/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/cn/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/cn/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/cn/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/cn/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/cn/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/cn/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/cn/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/cn/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/cn/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/cn/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/cn/enterprise/2.16/user/administering-a-repository/creating-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/cn/enterprise/2.16/github/administering-a-repository/creating-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/cn/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/cn/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/cn/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/cn/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/cn/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/cn/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/cn/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/cn/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/cn/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/cn/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/cn/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/cn/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository", - "/cn/enterprise/2.16/user/administering-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository", - "/cn/enterprise/2.16/github/administering-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/cn/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/cn/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/cn/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/cn/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/cn/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/cn/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/cn/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/cn/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/cn/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/cn/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/cn/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/cn/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/cn/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/cn/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/cn/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/cn/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/cn/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/cn/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/cn/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/cn/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/cn/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/cn/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/cn/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/cn/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/cn/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/cn/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/cn/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/cn/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/cn/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/cn/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/cn/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/cn/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/cn/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/cn/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/cn/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/cn/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/cn/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/cn/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/cn/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/cn/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/cn/enterprise/2.16/user/authenticating-to-github/about-ssh": "/cn/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/cn/enterprise/2.16/github/authenticating-to-github/about-ssh": "/cn/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/cn/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/cn/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/cn/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/cn/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/cn/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/cn/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/cn/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/cn/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/cn/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/cn/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/cn/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/cn/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/cn/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/cn/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/cn/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/cn/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/cn/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/cn/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/cn/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/cn/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/cn/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/cn/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/cn/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/cn/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/cn/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/cn/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/cn/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/cn/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/cn/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/cn/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/cn/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/cn/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/cn/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/cn/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/cn/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/cn/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/cn/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/cn/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/cn/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/cn/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/cn/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/cn/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/cn/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/cn/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/cn/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/cn/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/cn/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/cn/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/cn/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/cn/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/cn/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/cn/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/cn/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/cn/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/cn/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/cn/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/cn/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/cn/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/cn/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/cn/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/cn/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/cn/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/cn/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/cn/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/cn/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/cn/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/cn/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/cn/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/cn/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/cn/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/cn/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/cn/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/cn/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/cn/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/cn/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/cn/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/cn/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/cn/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/cn/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/cn/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/cn/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/cn/enterprise/2.16/user/authenticating-to-github": "/cn/enterprise/2.16/user/github/authenticating-to-github", - "/cn/enterprise/2.16/github/authenticating-to-github": "/cn/enterprise/2.16/user/github/authenticating-to-github", - "/cn/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/cn/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/cn/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/cn/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/cn/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/cn/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/cn/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/cn/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/cn/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/cn/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/cn/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/cn/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/cn/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/cn/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/cn/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/cn/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/cn/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/cn/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/cn/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/cn/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/cn/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/cn/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/cn/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/cn/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/cn/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/cn/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/cn/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/cn/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/cn/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/cn/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/cn/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/cn/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/cn/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/cn/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/cn/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/cn/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/cn/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/cn/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/cn/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/cn/enterprise/2.16/user/authenticating-to-github/signing-commits": "/cn/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/cn/enterprise/2.16/github/authenticating-to-github/signing-commits": "/cn/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/cn/enterprise/2.16/user/authenticating-to-github/signing-tags": "/cn/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/cn/enterprise/2.16/github/authenticating-to-github/signing-tags": "/cn/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/cn/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/cn/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/cn/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/cn/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/cn/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/cn/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/cn/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/cn/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/cn/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/cn/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/cn/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/cn/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/cn/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/cn/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/cn/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/cn/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/cn/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/cn/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/cn/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/cn/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/cn/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/cn/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/cn/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/cn/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/cn/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/cn/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/cn/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/cn/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/cn/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/cn/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/cn/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/cn/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/cn/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/cn/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/cn/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/cn/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/cn/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/cn/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/cn/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/cn/enterprise/2.16/user/building-a-strong-community/about-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/cn/enterprise/2.16/github/building-a-strong-community/about-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/cn/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/cn/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/cn/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/cn/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/cn/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/cn/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/cn/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/cn/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/cn/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/cn/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/cn/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/cn/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/cn/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/cn/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/cn/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/cn/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/cn/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/cn/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/cn/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/cn/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/cn/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/cn/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/cn/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/cn/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/cn/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/cn/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/cn/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/cn/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/cn/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/cn/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/cn/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/cn/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/cn/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/cn/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/cn/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/cn/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/cn/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/cn/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/cn/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/cn/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/cn/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/cn/enterprise/2.16/user/building-a-strong-community": "/cn/enterprise/2.16/user/github/building-a-strong-community", - "/cn/enterprise/2.16/github/building-a-strong-community": "/cn/enterprise/2.16/user/github/building-a-strong-community", - "/cn/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/cn/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/cn/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/cn/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/cn/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/cn/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/cn/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/cn/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/cn/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/cn/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/cn/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/cn/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/cn/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/cn/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/cn/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/cn/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/cn/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/cn/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/cn/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/cn/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/cn/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/cn/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/cn/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/cn/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/cn/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/cn/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/cn/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/cn/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/cn/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/cn/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/cn/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/cn/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/cn/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/cn/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/cn/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/cn/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/cn/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/cn/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/cn/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/cn/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/cn/enterprise/2.16/user/committing-changes-to-your-project": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project", - "/cn/enterprise/2.16/github/committing-changes-to-your-project": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/cn/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/cn/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/cn/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/cn/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/cn/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/cn/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/cn/enterprise/2.16/user/extending-github/about-webhooks": "/cn/enterprise/2.16/user/github/extending-github/about-webhooks", - "/cn/enterprise/2.16/github/extending-github/about-webhooks": "/cn/enterprise/2.16/user/github/extending-github/about-webhooks", - "/cn/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/cn/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/cn/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/cn/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/cn/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/cn/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/cn/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/cn/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/cn/enterprise/2.16/user/extending-github": "/cn/enterprise/2.16/user/github/extending-github", - "/cn/enterprise/2.16/github/extending-github": "/cn/enterprise/2.16/user/github/extending-github", - "/cn/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/cn/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/cn/enterprise/2.16/user/getting-started-with-github/be-social": "/cn/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/cn/enterprise/2.16/github/getting-started-with-github/be-social": "/cn/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/cn/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/cn/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/cn/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/cn/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/cn/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/cn/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/cn/enterprise/2.16/user/getting-started-with-github/following-people": "/cn/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/cn/enterprise/2.16/github/getting-started-with-github/following-people": "/cn/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/cn/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/cn/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/cn/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/cn/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/cn/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/cn/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/cn/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/cn/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/cn/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/cn/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/cn/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/cn/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/cn/enterprise/2.16/user/getting-started-with-github/github-glossary": "/cn/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/cn/enterprise/2.16/github/getting-started-with-github/github-glossary": "/cn/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/cn/enterprise/2.16/user/getting-started-with-github": "/cn/enterprise/2.16/user/github/getting-started-with-github", - "/cn/enterprise/2.16/github/getting-started-with-github": "/cn/enterprise/2.16/user/github/getting-started-with-github", - "/cn/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/cn/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/cn/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/cn/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/cn/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/cn/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/cn/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/cn/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/cn/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/cn/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/cn/enterprise/2.16/user/getting-started-with-github/set-up-git": "/cn/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/cn/enterprise/2.16/github/getting-started-with-github/set-up-git": "/cn/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/cn/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/cn/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/cn/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/cn/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/cn/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/cn/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/cn/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/cn/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/cn/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/cn/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/cn/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/cn/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/cn/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/cn/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/cn/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/cn/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/cn/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/cn/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/cn/enterprise/2.16/user/getting-started-with-github/using-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/cn/enterprise/2.16/github/getting-started-with-github/using-github": "/cn/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/cn/enterprise/2.16/user/importing-your-projects-to-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github", - "/cn/enterprise/2.16/github/importing-your-projects-to-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/cn/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/cn/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/cn/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/cn/enterprise/2.16/user": "/cn/enterprise/2.16/user/github", - "/cn/enterprise/2.16/github": "/cn/enterprise/2.16/user/github", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/cn/enterprise/2.16/user/managing-files-in-a-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository", - "/cn/enterprise/2.16/github/managing-files-in-a-repository": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/cn/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/cn/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/cn/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/cn/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/cn/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/cn/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/cn/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/cn/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/cn/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/cn/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/cn/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/cn/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/cn/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/cn/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/cn/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/cn/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/cn/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/cn/enterprise/2.16/user/managing-large-files": "/cn/enterprise/2.16/user/github/managing-large-files", - "/cn/enterprise/2.16/github/managing-large-files": "/cn/enterprise/2.16/user/github/managing-large-files", - "/cn/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/cn/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/cn/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/cn/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/cn/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/cn/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/cn/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/cn/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/cn/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/cn/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/cn/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/cn/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/cn/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/cn/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/cn/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/cn/enterprise/2.16/user/managing-large-files/versioning-large-files": "/cn/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/cn/enterprise/2.16/github/managing-large-files/versioning-large-files": "/cn/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/cn/enterprise/2.16/user/managing-large-files/working-with-large-files": "/cn/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/cn/enterprise/2.16/github/managing-large-files/working-with-large-files": "/cn/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/cn/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/cn/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/cn/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/cn/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/cn/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/cn/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/cn/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/cn/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/cn/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/cn/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/cn/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/cn/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/cn/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/cn/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/cn/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/cn/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/cn/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/cn/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/cn/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/cn/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/cn/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/cn/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/cn/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/cn/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/cn/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/cn/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/cn/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/cn/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/cn/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/cn/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/cn/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/cn/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/cn/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/cn/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/cn/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/cn/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/cn/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/cn/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/cn/enterprise/2.16/user/managing-your-work-on-github": "/cn/enterprise/2.16/user/github/managing-your-work-on-github", - "/cn/enterprise/2.16/github/managing-your-work-on-github": "/cn/enterprise/2.16/user/github/managing-your-work-on-github", - "/cn/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/cn/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/cn/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/cn/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/cn/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/cn/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/cn/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/cn/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/cn/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/cn/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/cn/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/cn/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/cn/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/cn/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/cn/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/cn/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/cn/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/cn/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/cn/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/cn/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/cn/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/cn/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/cn/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/cn/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/cn/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/cn/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/cn/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/cn/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/cn/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/cn/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/cn/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/cn/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/cn/enterprise/2.16/user/searching-for-information-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github", - "/cn/enterprise/2.16/github/searching-for-information-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/cn/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/cn/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/cn/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/cn/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/cn/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/cn/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/cn/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/cn/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/cn/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/cn/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/cn/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/cn/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/cn/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/cn/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/cn/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/cn/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/cn/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/cn/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/cn/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/cn/enterprise/2.16/user/using-git/about-git-rebase": "/cn/enterprise/2.16/user/github/using-git/about-git-rebase", - "/cn/enterprise/2.16/github/using-git/about-git-rebase": "/cn/enterprise/2.16/user/github/using-git/about-git-rebase", - "/cn/enterprise/2.16/user/using-git/about-git-subtree-merges": "/cn/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/cn/enterprise/2.16/github/using-git/about-git-subtree-merges": "/cn/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/cn/enterprise/2.16/user/using-git/about-remote-repositories": "/cn/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/cn/enterprise/2.16/github/using-git/about-remote-repositories": "/cn/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/cn/enterprise/2.16/user/using-git/adding-a-remote": "/cn/enterprise/2.16/user/github/using-git/adding-a-remote", - "/cn/enterprise/2.16/github/using-git/adding-a-remote": "/cn/enterprise/2.16/user/github/using-git/adding-a-remote", - "/cn/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/cn/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/cn/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/cn/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/cn/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/cn/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/cn/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/cn/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/cn/enterprise/2.16/user/using-git/changing-a-remotes-url": "/cn/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/cn/enterprise/2.16/github/using-git/changing-a-remotes-url": "/cn/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/cn/enterprise/2.16/user/using-git/changing-author-info": "/cn/enterprise/2.16/user/github/using-git/changing-author-info", - "/cn/enterprise/2.16/github/using-git/changing-author-info": "/cn/enterprise/2.16/user/github/using-git/changing-author-info", - "/cn/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/cn/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/cn/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/cn/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/cn/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/cn/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/cn/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/cn/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/cn/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/cn/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/cn/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/cn/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/cn/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/cn/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/cn/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/cn/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/cn/enterprise/2.16/user/using-git/git-workflows": "/cn/enterprise/2.16/user/github/using-git/git-workflows", - "/cn/enterprise/2.16/github/using-git/git-workflows": "/cn/enterprise/2.16/user/github/using-git/git-workflows", - "/cn/enterprise/2.16/user/using-git/ignoring-files": "/cn/enterprise/2.16/user/github/using-git/ignoring-files", - "/cn/enterprise/2.16/github/using-git/ignoring-files": "/cn/enterprise/2.16/user/github/using-git/ignoring-files", - "/cn/enterprise/2.16/user/using-git": "/cn/enterprise/2.16/user/github/using-git", - "/cn/enterprise/2.16/github/using-git": "/cn/enterprise/2.16/user/github/using-git", - "/cn/enterprise/2.16/user/using-git/learning-about-git": "/cn/enterprise/2.16/user/github/using-git/learning-about-git", - "/cn/enterprise/2.16/github/using-git/learning-about-git": "/cn/enterprise/2.16/user/github/using-git/learning-about-git", - "/cn/enterprise/2.16/user/using-git/managing-remote-repositories": "/cn/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/cn/enterprise/2.16/github/using-git/managing-remote-repositories": "/cn/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/cn/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/cn/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/cn/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/cn/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/cn/enterprise/2.16/user/using-git/removing-a-remote": "/cn/enterprise/2.16/user/github/using-git/removing-a-remote", - "/cn/enterprise/2.16/github/using-git/removing-a-remote": "/cn/enterprise/2.16/user/github/using-git/removing-a-remote", - "/cn/enterprise/2.16/user/using-git/renaming-a-remote": "/cn/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/cn/enterprise/2.16/github/using-git/renaming-a-remote": "/cn/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/cn/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/cn/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/cn/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/cn/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/cn/enterprise/2.16/user/using-git/setting-your-username-in-git": "/cn/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/cn/enterprise/2.16/github/using-git/setting-your-username-in-git": "/cn/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/cn/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/cn/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/cn/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/cn/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/cn/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/cn/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/cn/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/cn/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/cn/enterprise/2.16/user/using-git/using-advanced-git-commands": "/cn/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/cn/enterprise/2.16/github/using-git/using-advanced-git-commands": "/cn/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/cn/enterprise/2.16/user/using-git/using-common-git-commands": "/cn/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/cn/enterprise/2.16/github/using-git/using-common-git-commands": "/cn/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/cn/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/cn/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/cn/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/cn/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/cn/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/cn/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/cn/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/cn/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/cn/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/cn/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/cn/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/cn/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/cn/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/cn/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/cn/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/cn/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/cn/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/cn/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/cn/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/cn/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/cn/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/cn/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/cn/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/cn/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/cn/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/cn/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/cn/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/cn/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/cn/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/cn/enterprise/2.16/user/working-with-github-pages": "/cn/enterprise/2.16/user/github/working-with-github-pages", - "/cn/enterprise/2.16/github/working-with-github-pages": "/cn/enterprise/2.16/user/github/working-with-github-pages", - "/cn/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/cn/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/cn/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/cn/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/cn/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/cn/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/cn/enterprise/2.16/user/writing-on-github/about-saved-replies": "/cn/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/cn/enterprise/2.16/github/writing-on-github/about-saved-replies": "/cn/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/cn/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/cn/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/cn/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/cn/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/cn/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/cn/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/cn/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/cn/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/cn/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/cn/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/cn/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/cn/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/cn/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/cn/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/cn/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/cn/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/cn/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/cn/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/cn/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/cn/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/cn/enterprise/2.16/user/writing-on-github/creating-gists": "/cn/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/cn/enterprise/2.16/github/writing-on-github/creating-gists": "/cn/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/cn/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/cn/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/cn/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/cn/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/cn/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/cn/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/cn/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/cn/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/cn/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/cn/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/cn/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/cn/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/cn/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/cn/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/cn/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/cn/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/cn/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/cn/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/cn/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/cn/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/cn/enterprise/2.16/user/writing-on-github": "/cn/enterprise/2.16/user/github/writing-on-github", - "/cn/enterprise/2.16/github/writing-on-github": "/cn/enterprise/2.16/user/github/writing-on-github", - "/cn/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/cn/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/cn/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/cn/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/cn/enterprise/2.16/user/writing-on-github/using-saved-replies": "/cn/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/cn/enterprise/2.16/github/writing-on-github/using-saved-replies": "/cn/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/cn/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/cn/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/cn/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/cn/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/cn/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/cn/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/cn/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/cn/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/cn/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/cn/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/cn/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/cn/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/cn/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/cn/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/cn/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/cn/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/cn/enterprise/2.16/insights": "/cn/enterprise/2.16/user/insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/cn/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/cn/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/en/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/en/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/en/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/en/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/en/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.16/admin/articles/using-github-task-runner", - "/enterprise/2.16/admin/articles/using-github-task-runner": "/en/enterprise/2.16/admin/articles/using-github-task-runner", - "/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.16/admin/articles/using-github-task-runner", - "/en/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/enterprise/2.16/admin/clustering/about-cluster-nodes": "/en/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/en/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/en/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/enterprise/2.16/admin/clustering/cluster-network-configuration": "/en/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/en/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/en/enterprise/2.16/admin/guides/clustering/clustering-overview": "/en/enterprise/2.16/admin/clustering/clustering-overview", - "/enterprise/2.16/admin/clustering/clustering-overview": "/en/enterprise/2.16/admin/clustering/clustering-overview", - "/enterprise/2.16/admin/guides/clustering/clustering-overview": "/en/enterprise/2.16/admin/clustering/clustering-overview", - "/en/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/en/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.16/admin/clustering/evacuating-a-cluster-node": "/en/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/en/enterprise/2.16/admin/guides/clustering": "/en/enterprise/2.16/admin/clustering", - "/enterprise/2.16/admin/clustering": "/en/enterprise/2.16/admin/clustering", - "/enterprise/2.16/admin/guides/clustering": "/en/enterprise/2.16/admin/clustering", - "/en/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/enterprise/2.16/admin/clustering/initializing-the-cluster": "/en/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/en/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/en/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.16/admin/clustering/monitoring-cluster-nodes": "/en/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/en/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.16/admin/clustering/replacing-a-cluster-node": "/en/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/en/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/en/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/enterprise/2.16/admin/clustering/upgrading-a-cluster": "/en/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/en/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/en/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/en/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/en/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/en/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/en/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/en/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/en/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/en/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/en/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/en/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/en/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/en/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/en/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/en/enterprise/2.16/admin/guides/developer-workflow": "/en/enterprise/2.16/admin/developer-workflow", - "/enterprise/2.16/admin/developer-workflow": "/en/enterprise/2.16/admin/developer-workflow", - "/enterprise/2.16/admin/guides/developer-workflow": "/en/enterprise/2.16/admin/developer-workflow", - "/en/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/en/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/en/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/en/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/en/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/en/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/en/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/en/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/en/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security": "/en/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/en/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/en/enterprise/2.16/admin/guides/enterprise-support": "/en/enterprise/2.16/admin/enterprise-support", - "/enterprise/2.16/admin/enterprise-support": "/en/enterprise/2.16/admin/enterprise-support", - "/enterprise/2.16/admin/guides/enterprise-support": "/en/enterprise/2.16/admin/enterprise-support", - "/en/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/en/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/en/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/enterprise/2.16/admin/enterprise-support/reaching-github-support": "/en/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/en/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/en/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.16/admin/enterprise-support/submitting-a-ticket": "/en/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/en/enterprise/2.16/admin/guides": "/en/enterprise/2.16/admin", - "/enterprise/2.16/admin": "/en/enterprise/2.16/admin", - "/enterprise/2.16/admin/guides": "/en/enterprise/2.16/admin", - "/en/enterprise/2.16/admin/guides/installation/about-geo-replication": "/en/enterprise/2.16/admin/installation/about-geo-replication", - "/enterprise/2.16/admin/installation/about-geo-replication": "/en/enterprise/2.16/admin/installation/about-geo-replication", - "/enterprise/2.16/admin/guides/installation/about-geo-replication": "/en/enterprise/2.16/admin/installation/about-geo-replication", - "/en/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/enterprise/2.16/admin/installation/about-high-availability-configuration": "/en/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/en/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/en/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/en/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.16/admin/installation/accessing-the-management-console", - "/enterprise/2.16/admin/installation/accessing-the-management-console": "/en/enterprise/2.16/admin/installation/accessing-the-management-console", - "/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.16/admin/installation/accessing-the-management-console", - "/en/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/en/enterprise/2.16/admin/guides/installation/activity-dashboard": "/en/enterprise/2.16/admin/installation/activity-dashboard", - "/enterprise/2.16/admin/installation/activity-dashboard": "/en/enterprise/2.16/admin/installation/activity-dashboard", - "/enterprise/2.16/admin/guides/installation/activity-dashboard": "/en/enterprise/2.16/admin/installation/activity-dashboard", - "/en/enterprise/2.16/admin/guides/installation/audit-logging": "/en/enterprise/2.16/admin/installation/audit-logging", - "/enterprise/2.16/admin/installation/audit-logging": "/en/enterprise/2.16/admin/installation/audit-logging", - "/enterprise/2.16/admin/guides/installation/audit-logging": "/en/enterprise/2.16/admin/installation/audit-logging", - "/en/enterprise/2.16/admin/guides/installation/audited-actions": "/en/enterprise/2.16/admin/installation/audited-actions", - "/enterprise/2.16/admin/installation/audited-actions": "/en/enterprise/2.16/admin/installation/audited-actions", - "/enterprise/2.16/admin/guides/installation/audited-actions": "/en/enterprise/2.16/admin/installation/audited-actions", - "/en/enterprise/2.16/admin/guides/installation/command-line-utilities": "/en/enterprise/2.16/admin/installation/command-line-utilities", - "/enterprise/2.16/admin/installation/command-line-utilities": "/en/enterprise/2.16/admin/installation/command-line-utilities", - "/enterprise/2.16/admin/guides/installation/command-line-utilities": "/en/enterprise/2.16/admin/installation/command-line-utilities", - "/en/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.16/admin/installation/configuring-a-hostname", - "/enterprise/2.16/admin/installation/configuring-a-hostname": "/en/enterprise/2.16/admin/installation/configuring-a-hostname", - "/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.16/admin/installation/configuring-a-hostname", - "/en/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/en/enterprise/2.16/admin/guides/installation/configuring-applications": "/en/enterprise/2.16/admin/installation/configuring-applications", - "/enterprise/2.16/admin/installation/configuring-applications": "/en/enterprise/2.16/admin/installation/configuring-applications", - "/enterprise/2.16/admin/guides/installation/configuring-applications": "/en/enterprise/2.16/admin/installation/configuring-applications", - "/en/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/en/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/en/enterprise/2.16/admin/guides/installation/configuring-collectd": "/en/enterprise/2.16/admin/installation/configuring-collectd", - "/enterprise/2.16/admin/installation/configuring-collectd": "/en/enterprise/2.16/admin/installation/configuring-collectd", - "/enterprise/2.16/admin/guides/installation/configuring-collectd": "/en/enterprise/2.16/admin/installation/configuring-collectd", - "/en/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/enterprise/2.16/admin/installation/configuring-dns-nameservers": "/en/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/en/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/en/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.16/admin/installation/configuring-git-large-file-storage": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/en/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/en/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/en/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.16/admin/installation/configuring-rate-limits", - "/enterprise/2.16/admin/installation/configuring-rate-limits": "/en/enterprise/2.16/admin/installation/configuring-rate-limits", - "/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.16/admin/installation/configuring-rate-limits", - "/en/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/en/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/en/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/en/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/enterprise/2.16/admin/installation/configuring-time-synchronization": "/en/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/en/enterprise/2.16/admin/guides/installation/configuring-tls": "/en/enterprise/2.16/admin/installation/configuring-tls", - "/enterprise/2.16/admin/installation/configuring-tls": "/en/enterprise/2.16/admin/installation/configuring-tls", - "/enterprise/2.16/admin/guides/installation/configuring-tls": "/en/enterprise/2.16/admin/installation/configuring-tls", - "/en/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/en/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/en/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.16/admin/installation/creating-a-high-availability-replica": "/en/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/en/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/en/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/en/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.16/admin/installation/enabling-automatic-update-checks": "/en/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/en/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.16/admin/installation/enabling-private-mode", - "/enterprise/2.16/admin/installation/enabling-private-mode": "/en/enterprise/2.16/admin/installation/enabling-private-mode", - "/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.16/admin/installation/enabling-private-mode", - "/en/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.16/admin/installation/enabling-subdomain-isolation": "/en/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/en/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/en/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/enterprise/2.16/admin/installation/increasing-storage-capacity": "/en/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/en/enterprise/2.16/admin/guides/installation": "/en/enterprise/2.16/admin/installation", - "/enterprise/2.16/admin/installation": "/en/enterprise/2.16/admin/installation", - "/enterprise/2.16/admin/guides/installation": "/en/enterprise/2.16/admin/installation", - "/en/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/en/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/en/enterprise/2.16/admin/guides/installation/log-forwarding": "/en/enterprise/2.16/admin/installation/log-forwarding", - "/enterprise/2.16/admin/installation/log-forwarding": "/en/enterprise/2.16/admin/installation/log-forwarding", - "/enterprise/2.16/admin/guides/installation/log-forwarding": "/en/enterprise/2.16/admin/installation/log-forwarding", - "/en/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/en/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/en/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/en/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/en/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/en/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/en/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/en/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/enterprise/2.16/admin/installation/monitoring-using-snmp": "/en/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/en/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/en/enterprise/2.16/admin/guides/installation/network-ports": "/en/enterprise/2.16/admin/installation/network-ports", - "/enterprise/2.16/admin/installation/network-ports": "/en/enterprise/2.16/admin/installation/network-ports", - "/enterprise/2.16/admin/guides/installation/network-ports": "/en/enterprise/2.16/admin/installation/network-ports", - "/en/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/enterprise/2.16/admin/installation/recommended-alert-thresholds": "/en/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/en/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/en/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.16/admin/installation/removing-a-high-availability-replica": "/en/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/en/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.16/admin/installation/searching-the-audit-log", - "/enterprise/2.16/admin/installation/searching-the-audit-log": "/en/enterprise/2.16/admin/installation/searching-the-audit-log", - "/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.16/admin/installation/searching-the-audit-log", - "/en/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.16/admin/installation/setting-git-push-limits", - "/enterprise/2.16/admin/installation/setting-git-push-limits": "/en/enterprise/2.16/admin/installation/setting-git-push-limits", - "/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.16/admin/installation/setting-git-push-limits", - "/en/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/en/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.16/admin/installation/setting-up-a-staging-instance": "/en/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/en/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/enterprise/2.16/admin/installation/setting-up-external-monitoring": "/en/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/en/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.16/admin/installation/site-admin-dashboard", - "/enterprise/2.16/admin/installation/site-admin-dashboard": "/en/enterprise/2.16/admin/installation/site-admin-dashboard", - "/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.16/admin/installation/site-admin-dashboard", - "/en/enterprise/2.16/admin/guides/installation/system-overview": "/en/enterprise/2.16/admin/installation/system-overview", - "/enterprise/2.16/admin/installation/system-overview": "/en/enterprise/2.16/admin/installation/system-overview", - "/enterprise/2.16/admin/guides/installation/system-overview": "/en/enterprise/2.16/admin/installation/system-overview", - "/en/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.16/admin/installation/troubleshooting-ssl-errors": "/en/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/en/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/en/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.16/admin/installation/upgrade-requirements", - "/enterprise/2.16/admin/installation/upgrade-requirements": "/en/enterprise/2.16/admin/installation/upgrade-requirements", - "/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.16/admin/installation/upgrade-requirements", - "/en/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.16/admin/installation/upgrading-github-enterprise-server": "/en/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/en/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/enterprise/2.16/admin/installation/validating-your-domain-settings": "/en/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/en/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.16/admin/installation/viewing-push-logs", - "/enterprise/2.16/admin/installation/viewing-push-logs": "/en/enterprise/2.16/admin/installation/viewing-push-logs", - "/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.16/admin/installation/viewing-push-logs", - "/en/enterprise/2.16/admin/guides/migrations/about-migrations": "/en/enterprise/2.16/admin/migrations/about-migrations", - "/enterprise/2.16/admin/migrations/about-migrations": "/en/enterprise/2.16/admin/migrations/about-migrations", - "/enterprise/2.16/admin/guides/migrations/about-migrations": "/en/enterprise/2.16/admin/migrations/about-migrations", - "/en/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/en/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/en/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/en/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/en/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/en/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/migrations": "/en/enterprise/2.16/admin/migrations", - "/enterprise/2.16/admin/migrations": "/en/enterprise/2.16/admin/migrations", - "/enterprise/2.16/admin/guides/migrations": "/en/enterprise/2.16/admin/migrations", - "/en/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/en/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/en/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/en/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/en/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.16/admin/migrations/reviewing-migration-conflicts": "/en/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/en/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/enterprise/2.16/admin/migrations/reviewing-migration-data": "/en/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/en/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.16/admin/user-management/about-global-webhooks", - "/enterprise/2.16/admin/user-management/about-global-webhooks": "/en/enterprise/2.16/admin/user-management/about-global-webhooks", - "/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.16/admin/user-management/about-global-webhooks", - "/en/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/enterprise/2.16/admin/user-management/adding-people-to-teams": "/en/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/en/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/en/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/en/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/en/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/enterprise/2.16/admin/user-management/auditing-ssh-keys": "/en/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/en/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.16/admin/user-management/auditing-users-across-your-instance": "/en/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/en/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/en/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.16/admin/user-management/basic-account-settings", - "/enterprise/2.16/admin/user-management/basic-account-settings": "/en/enterprise/2.16/admin/user-management/basic-account-settings", - "/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.16/admin/user-management/basic-account-settings", - "/en/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/enterprise/2.16/admin/user-management/best-practices-for-user-security": "/en/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/en/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/enterprise/2.16/admin/user-management/changing-authentication-methods": "/en/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/en/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.16/admin/user-management/configuring-email-for-notifications": "/en/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/en/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/en/enterprise/2.16/admin/guides/user-management/creating-organizations": "/en/enterprise/2.16/admin/user-management/creating-organizations", - "/enterprise/2.16/admin/user-management/creating-organizations": "/en/enterprise/2.16/admin/user-management/creating-organizations", - "/enterprise/2.16/admin/guides/user-management/creating-organizations": "/en/enterprise/2.16/admin/user-management/creating-organizations", - "/en/enterprise/2.16/admin/guides/user-management/creating-teams": "/en/enterprise/2.16/admin/user-management/creating-teams", - "/enterprise/2.16/admin/user-management/creating-teams": "/en/enterprise/2.16/admin/user-management/creating-teams", - "/enterprise/2.16/admin/guides/user-management/creating-teams": "/en/enterprise/2.16/admin/user-management/creating-teams", - "/en/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/en/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/en/enterprise/2.16/admin/guides/user-management": "/en/enterprise/2.16/admin/user-management", - "/enterprise/2.16/admin/user-management": "/en/enterprise/2.16/admin/user-management", - "/enterprise/2.16/admin/guides/user-management": "/en/enterprise/2.16/admin/user-management", - "/en/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.16/admin/user-management/managing-dormant-users", - "/enterprise/2.16/admin/user-management/managing-dormant-users": "/en/enterprise/2.16/admin/user-management/managing-dormant-users", - "/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.16/admin/user-management/managing-dormant-users", - "/en/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/enterprise/2.16/admin/user-management/managing-global-webhooks": "/en/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/en/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.16/admin/user-management/organizations-and-teams", - "/enterprise/2.16/admin/user-management/organizations-and-teams": "/en/enterprise/2.16/admin/user-management/organizations-and-teams", - "/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.16/admin/user-management/organizations-and-teams", - "/en/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/en/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/en/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/en/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/en/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/en/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/en/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.16/admin/user-management/rebuilding-contributions-data": "/en/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/en/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/en/enterprise/2.16/admin/guides/user-management/repositories": "/en/enterprise/2.16/admin/user-management/repositories", - "/enterprise/2.16/admin/user-management/repositories": "/en/enterprise/2.16/admin/user-management/repositories", - "/enterprise/2.16/admin/guides/user-management/repositories": "/en/enterprise/2.16/admin/user-management/repositories", - "/en/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/en/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/en/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/en/enterprise/2.16/admin/guides/user-management/user-security": "/en/enterprise/2.16/admin/user-management/user-security", - "/enterprise/2.16/admin/user-management/user-security": "/en/enterprise/2.16/admin/user-management/user-security", - "/enterprise/2.16/admin/guides/user-management/user-security": "/en/enterprise/2.16/admin/user-management/user-security", - "/en/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/enterprise/2.16/admin/user-management/using-built-in-authentication": "/en/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/en/enterprise/2.16/admin/guides/user-management/using-cas": "/en/enterprise/2.16/admin/user-management/using-cas", - "/enterprise/2.16/admin/user-management/using-cas": "/en/enterprise/2.16/admin/user-management/using-cas", - "/enterprise/2.16/admin/guides/user-management/using-cas": "/en/enterprise/2.16/admin/user-management/using-cas", - "/en/enterprise/2.16/admin/guides/user-management/using-ldap": "/en/enterprise/2.16/admin/user-management/using-ldap", - "/enterprise/2.16/admin/user-management/using-ldap": "/en/enterprise/2.16/admin/user-management/using-ldap", - "/enterprise/2.16/admin/guides/user-management/using-ldap": "/en/enterprise/2.16/admin/user-management/using-ldap", - "/en/enterprise/2.16/admin/guides/user-management/using-saml": "/en/enterprise/2.16/admin/user-management/using-saml", - "/enterprise/2.16/admin/user-management/using-saml": "/en/enterprise/2.16/admin/user-management/using-saml", - "/enterprise/2.16/admin/guides/user-management/using-saml": "/en/enterprise/2.16/admin/user-management/using-saml", - "/enterprise/2.16": "/en/enterprise/2.16", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/en/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/en/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/en/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/en/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/en/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/en/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.16/user/github/administering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/en/enterprise/2.16/user/administering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/en/enterprise/2.16/github/administering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/enterprise/2.16/user/github/administering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/enterprise/2.16/user/administering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/enterprise/2.16/github/administering-a-repository/about-releases": "/en/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/en/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/en/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/en/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/en/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/en/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/en/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/en/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/en/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/en/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/en/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/en/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/en/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/en/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/en/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/en/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/en/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/en/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/en/enterprise/2.16/user/administering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/en/enterprise/2.16/github/administering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/enterprise/2.16/user/github/administering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/enterprise/2.16/user/administering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/enterprise/2.16/github/administering-a-repository/creating-releases": "/en/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/en/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/en/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/en/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/en/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/en/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/en/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/en/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/en/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/en/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/en/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/en/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/en/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/en/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/en/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/en/enterprise/2.16/user/administering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/en/enterprise/2.16/github/administering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/enterprise/2.16/user/github/administering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/enterprise/2.16/user/administering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/enterprise/2.16/github/administering-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/en/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/en/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.16/user/github/administering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/en/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/en/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/en/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/en/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/en/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/en/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/en/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/en/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/en/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/en/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/en/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/en/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/en/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/en/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/en/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/en/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/en/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/en/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/en/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/en/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/en/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/en/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/en/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/en/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/en/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/en/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/en/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/en/enterprise/2.16/user/authenticating-to-github/about-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/en/enterprise/2.16/github/authenticating-to-github/about-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/enterprise/2.16/user/github/authenticating-to-github/about-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/enterprise/2.16/user/authenticating-to-github/about-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/enterprise/2.16/github/authenticating-to-github/about-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/en/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/en/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/en/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/en/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/en/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/en/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/en/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/en/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/en/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/en/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/en/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/en/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/en/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/en/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/en/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/en/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/en/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/en/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/en/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/en/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/en/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/en/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/en/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/en/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/en/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/en/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/en/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.16/user/authenticating-to-github": "/en/enterprise/2.16/user/github/authenticating-to-github", - "/en/enterprise/2.16/github/authenticating-to-github": "/en/enterprise/2.16/user/github/authenticating-to-github", - "/enterprise/2.16/user/github/authenticating-to-github": "/en/enterprise/2.16/user/github/authenticating-to-github", - "/enterprise/2.16/user/authenticating-to-github": "/en/enterprise/2.16/user/github/authenticating-to-github", - "/enterprise/2.16/github/authenticating-to-github": "/en/enterprise/2.16/user/github/authenticating-to-github", - "/en/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/en/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/en/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/en/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/en/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/en/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/en/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/en/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/en/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/en/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/en/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/en/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/en/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/en/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/en/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.16/user/authenticating-to-github/signing-commits": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/en/enterprise/2.16/github/authenticating-to-github/signing-commits": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/enterprise/2.16/user/github/authenticating-to-github/signing-commits": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/enterprise/2.16/user/authenticating-to-github/signing-commits": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/enterprise/2.16/github/authenticating-to-github/signing-commits": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/en/enterprise/2.16/user/authenticating-to-github/signing-tags": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/en/enterprise/2.16/github/authenticating-to-github/signing-tags": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/enterprise/2.16/user/github/authenticating-to-github/signing-tags": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/enterprise/2.16/user/authenticating-to-github/signing-tags": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/enterprise/2.16/github/authenticating-to-github/signing-tags": "/en/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/en/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/en/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/en/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/en/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/enterprise/2.16/user/github/authenticating-to-github/sudo-mode": "/en/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/en/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/en/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/en/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/en/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/en/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/en/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/en/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/en/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/en/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/en/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/en/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/en/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/en/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/en/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/en/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/en/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/en/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/en/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/en/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/en/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/en/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/en/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions": "/en/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/en/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/en/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/en/enterprise/2.16/user/building-a-strong-community/about-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/en/enterprise/2.16/github/building-a-strong-community/about-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/enterprise/2.16/user/github/building-a-strong-community/about-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/enterprise/2.16/user/building-a-strong-community/about-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/enterprise/2.16/github/building-a-strong-community/about-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/en/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/en/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/en/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/en/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/en/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/en/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/en/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/en/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/en/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/en/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/en/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/en/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/en/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/en/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/en/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/en/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/en/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/en/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/en/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/en/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/en/enterprise/2.16/user/building-a-strong-community": "/en/enterprise/2.16/user/github/building-a-strong-community", - "/en/enterprise/2.16/github/building-a-strong-community": "/en/enterprise/2.16/user/github/building-a-strong-community", - "/enterprise/2.16/user/github/building-a-strong-community": "/en/enterprise/2.16/user/github/building-a-strong-community", - "/enterprise/2.16/user/building-a-strong-community": "/en/enterprise/2.16/user/github/building-a-strong-community", - "/enterprise/2.16/github/building-a-strong-community": "/en/enterprise/2.16/user/github/building-a-strong-community", - "/en/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/en/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/enterprise/2.16/user/github/building-a-strong-community/locking-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/en/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/en/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/en/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/en/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/en/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/en/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/en/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/en/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/en/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/en/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/en/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/en/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/en/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/en/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/en/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/en/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/en/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/en/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/en/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/en/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/en/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/en/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/en/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/en/enterprise/2.16/user/committing-changes-to-your-project": "/en/enterprise/2.16/user/github/committing-changes-to-your-project", - "/en/enterprise/2.16/github/committing-changes-to-your-project": "/en/enterprise/2.16/user/github/committing-changes-to-your-project", - "/enterprise/2.16/user/github/committing-changes-to-your-project": "/en/enterprise/2.16/user/github/committing-changes-to-your-project", - "/enterprise/2.16/user/committing-changes-to-your-project": "/en/enterprise/2.16/user/github/committing-changes-to-your-project", - "/enterprise/2.16/github/committing-changes-to-your-project": "/en/enterprise/2.16/user/github/committing-changes-to-your-project", - "/en/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/en/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/en/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/en/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/en/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/en/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.16/user/extending-github/about-webhooks": "/en/enterprise/2.16/user/github/extending-github/about-webhooks", - "/en/enterprise/2.16/github/extending-github/about-webhooks": "/en/enterprise/2.16/user/github/extending-github/about-webhooks", - "/enterprise/2.16/user/github/extending-github/about-webhooks": "/en/enterprise/2.16/user/github/extending-github/about-webhooks", - "/enterprise/2.16/user/extending-github/about-webhooks": "/en/enterprise/2.16/user/github/extending-github/about-webhooks", - "/enterprise/2.16/github/extending-github/about-webhooks": "/en/enterprise/2.16/user/github/extending-github/about-webhooks", - "/en/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/en/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/en/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/en/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/enterprise/2.16/user/github/extending-github/getting-started-with-the-api": "/en/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/en/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/en/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/en/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/en/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/en/enterprise/2.16/user/extending-github": "/en/enterprise/2.16/user/github/extending-github", - "/en/enterprise/2.16/github/extending-github": "/en/enterprise/2.16/user/github/extending-github", - "/enterprise/2.16/user/github/extending-github": "/en/enterprise/2.16/user/github/extending-github", - "/enterprise/2.16/user/extending-github": "/en/enterprise/2.16/user/github/extending-github", - "/enterprise/2.16/github/extending-github": "/en/enterprise/2.16/user/github/extending-github", - "/en/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/en/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/en/enterprise/2.16/user/getting-started-with-github/be-social": "/en/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/en/enterprise/2.16/github/getting-started-with-github/be-social": "/en/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/enterprise/2.16/user/github/getting-started-with-github/be-social": "/en/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/enterprise/2.16/user/getting-started-with-github/be-social": "/en/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/enterprise/2.16/github/getting-started-with-github/be-social": "/en/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/en/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/en/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/enterprise/2.16/user/github/getting-started-with-github/create-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/en/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/en/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/en/enterprise/2.16/user/getting-started-with-github/following-people": "/en/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/en/enterprise/2.16/github/getting-started-with-github/following-people": "/en/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/enterprise/2.16/user/github/getting-started-with-github/following-people": "/en/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/enterprise/2.16/user/getting-started-with-github/following-people": "/en/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/enterprise/2.16/github/getting-started-with-github/following-people": "/en/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/en/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/en/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/en/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/en/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/en/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/en/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/en/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/en/enterprise/2.16/user/getting-started-with-github/github-glossary": "/en/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/en/enterprise/2.16/github/getting-started-with-github/github-glossary": "/en/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/enterprise/2.16/user/github/getting-started-with-github/github-glossary": "/en/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/enterprise/2.16/user/getting-started-with-github/github-glossary": "/en/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/enterprise/2.16/github/getting-started-with-github/github-glossary": "/en/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/en/enterprise/2.16/user/getting-started-with-github": "/en/enterprise/2.16/user/github/getting-started-with-github", - "/en/enterprise/2.16/github/getting-started-with-github": "/en/enterprise/2.16/user/github/getting-started-with-github", - "/enterprise/2.16/user/github/getting-started-with-github": "/en/enterprise/2.16/user/github/getting-started-with-github", - "/enterprise/2.16/user/getting-started-with-github": "/en/enterprise/2.16/user/github/getting-started-with-github", - "/enterprise/2.16/github/getting-started-with-github": "/en/enterprise/2.16/user/github/getting-started-with-github", - "/en/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/en/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/en/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/en/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/en/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/en/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/enterprise/2.16/user/github/getting-started-with-github/learning-about-github": "/en/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/en/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/en/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/en/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/en/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/en/enterprise/2.16/user/getting-started-with-github/set-up-git": "/en/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/en/enterprise/2.16/github/getting-started-with-github/set-up-git": "/en/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/enterprise/2.16/user/github/getting-started-with-github/set-up-git": "/en/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/enterprise/2.16/user/getting-started-with-github/set-up-git": "/en/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/enterprise/2.16/github/getting-started-with-github/set-up-git": "/en/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/en/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/en/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/en/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/en/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/en/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/en/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/en/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/en/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/en/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/en/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/enterprise/2.16/user/github/getting-started-with-github/supported-browsers": "/en/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/en/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/en/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/en/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/en/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/en/enterprise/2.16/user/getting-started-with-github/using-github": "/en/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/en/enterprise/2.16/github/getting-started-with-github/using-github": "/en/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/enterprise/2.16/user/github/getting-started-with-github/using-github": "/en/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/enterprise/2.16/user/getting-started-with-github/using-github": "/en/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/enterprise/2.16/github/getting-started-with-github/using-github": "/en/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/en/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/en/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/en/enterprise/2.16/user/importing-your-projects-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github", - "/en/enterprise/2.16/github/importing-your-projects-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github", - "/enterprise/2.16/user/github/importing-your-projects-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github", - "/enterprise/2.16/user/importing-your-projects-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github", - "/enterprise/2.16/github/importing-your-projects-to-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github", - "/en/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/en/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/en/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/en/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/en/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/en/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/en/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/en/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/en/enterprise/2.16/user": "/en/enterprise/2.16/user/github", - "/en/enterprise/2.16/github": "/en/enterprise/2.16/user/github", - "/enterprise/2.16/user/github": "/en/enterprise/2.16/user/github", - "/enterprise/2.16/user": "/en/enterprise/2.16/user/github", - "/enterprise/2.16/github": "/en/enterprise/2.16/user/github", - "/en/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/en/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/en/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/en/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/en/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/en/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/en/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/en/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/en/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/en/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/en/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/en/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/en/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/en/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/en/enterprise/2.16/user/managing-files-in-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository", - "/en/enterprise/2.16/github/managing-files-in-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository", - "/enterprise/2.16/user/github/managing-files-in-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository", - "/enterprise/2.16/user/managing-files-in-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository", - "/enterprise/2.16/github/managing-files-in-a-repository": "/en/enterprise/2.16/user/github/managing-files-in-a-repository", - "/en/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/en/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/en/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/en/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/en/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/en/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/en/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/en/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/en/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/en/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/en/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/en/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/en/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/en/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/en/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/en/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/en/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/en/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/en/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/en/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/en/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/en/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/en/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/en/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/en/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/en/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/en/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/en/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/en/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/en/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/en/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/en/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files": "/en/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/en/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/en/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/en/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/en/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/en/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/en/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/en/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/en/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries": "/en/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/en/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/en/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/en/enterprise/2.16/user/managing-large-files": "/en/enterprise/2.16/user/github/managing-large-files", - "/en/enterprise/2.16/github/managing-large-files": "/en/enterprise/2.16/user/github/managing-large-files", - "/enterprise/2.16/user/github/managing-large-files": "/en/enterprise/2.16/user/github/managing-large-files", - "/enterprise/2.16/user/managing-large-files": "/en/enterprise/2.16/user/github/managing-large-files", - "/enterprise/2.16/github/managing-large-files": "/en/enterprise/2.16/user/github/managing-large-files", - "/en/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/en/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/en/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/en/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/en/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/en/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/en/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.16/user/managing-large-files/versioning-large-files": "/en/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/en/enterprise/2.16/github/managing-large-files/versioning-large-files": "/en/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/enterprise/2.16/user/github/managing-large-files/versioning-large-files": "/en/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/enterprise/2.16/user/managing-large-files/versioning-large-files": "/en/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/enterprise/2.16/github/managing-large-files/versioning-large-files": "/en/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/en/enterprise/2.16/user/managing-large-files/working-with-large-files": "/en/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/en/enterprise/2.16/github/managing-large-files/working-with-large-files": "/en/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/enterprise/2.16/user/github/managing-large-files/working-with-large-files": "/en/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/enterprise/2.16/user/managing-large-files/working-with-large-files": "/en/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/enterprise/2.16/github/managing-large-files/working-with-large-files": "/en/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/en/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/en/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/en/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/en/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/en/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/en/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/en/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/en/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/en/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/en/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/en/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/en/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/en/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/en/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/en/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/en/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/en/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/en/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/en/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/en/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/en/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/en/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/en/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/en/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/en/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/en/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/en/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/en/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/en/enterprise/2.16/user/managing-your-work-on-github": "/en/enterprise/2.16/user/github/managing-your-work-on-github", - "/en/enterprise/2.16/github/managing-your-work-on-github": "/en/enterprise/2.16/user/github/managing-your-work-on-github", - "/enterprise/2.16/user/github/managing-your-work-on-github": "/en/enterprise/2.16/user/github/managing-your-work-on-github", - "/enterprise/2.16/user/managing-your-work-on-github": "/en/enterprise/2.16/user/github/managing-your-work-on-github", - "/enterprise/2.16/github/managing-your-work-on-github": "/en/enterprise/2.16/user/github/managing-your-work-on-github", - "/en/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/en/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/en/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/en/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/en/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/en/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/en/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/en/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/en/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/en/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/en/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/en/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/en/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/en/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/en/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/en/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/en/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/en/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/en/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/en/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/en/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/en/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/en/enterprise/2.16/user/searching-for-information-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github", - "/en/enterprise/2.16/github/searching-for-information-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github", - "/enterprise/2.16/user/github/searching-for-information-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github", - "/enterprise/2.16/user/searching-for-information-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github", - "/enterprise/2.16/github/searching-for-information-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-code": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-users": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/en/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/en/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/en/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/en/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/en/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/en/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/en/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/en/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/en/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/en/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/en/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/en/enterprise/2.16/user/using-git/about-git-rebase": "/en/enterprise/2.16/user/github/using-git/about-git-rebase", - "/en/enterprise/2.16/github/using-git/about-git-rebase": "/en/enterprise/2.16/user/github/using-git/about-git-rebase", - "/enterprise/2.16/user/github/using-git/about-git-rebase": "/en/enterprise/2.16/user/github/using-git/about-git-rebase", - "/enterprise/2.16/user/using-git/about-git-rebase": "/en/enterprise/2.16/user/github/using-git/about-git-rebase", - "/enterprise/2.16/github/using-git/about-git-rebase": "/en/enterprise/2.16/user/github/using-git/about-git-rebase", - "/en/enterprise/2.16/user/using-git/about-git-subtree-merges": "/en/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/en/enterprise/2.16/github/using-git/about-git-subtree-merges": "/en/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/enterprise/2.16/user/github/using-git/about-git-subtree-merges": "/en/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/enterprise/2.16/user/using-git/about-git-subtree-merges": "/en/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/enterprise/2.16/github/using-git/about-git-subtree-merges": "/en/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/en/enterprise/2.16/user/using-git/about-remote-repositories": "/en/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/en/enterprise/2.16/github/using-git/about-remote-repositories": "/en/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/enterprise/2.16/user/github/using-git/about-remote-repositories": "/en/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/enterprise/2.16/user/using-git/about-remote-repositories": "/en/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/enterprise/2.16/github/using-git/about-remote-repositories": "/en/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/en/enterprise/2.16/user/using-git/adding-a-remote": "/en/enterprise/2.16/user/github/using-git/adding-a-remote", - "/en/enterprise/2.16/github/using-git/adding-a-remote": "/en/enterprise/2.16/user/github/using-git/adding-a-remote", - "/enterprise/2.16/user/github/using-git/adding-a-remote": "/en/enterprise/2.16/user/github/using-git/adding-a-remote", - "/enterprise/2.16/user/using-git/adding-a-remote": "/en/enterprise/2.16/user/github/using-git/adding-a-remote", - "/enterprise/2.16/github/using-git/adding-a-remote": "/en/enterprise/2.16/user/github/using-git/adding-a-remote", - "/en/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/en/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/en/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/en/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/enterprise/2.16/user/github/using-git/associating-text-editors-with-git": "/en/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/en/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/en/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/en/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/en/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/en/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/en/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git": "/en/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/en/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/en/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/en/enterprise/2.16/user/using-git/changing-a-remotes-url": "/en/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/en/enterprise/2.16/github/using-git/changing-a-remotes-url": "/en/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/enterprise/2.16/user/github/using-git/changing-a-remotes-url": "/en/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/enterprise/2.16/user/using-git/changing-a-remotes-url": "/en/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/enterprise/2.16/github/using-git/changing-a-remotes-url": "/en/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/en/enterprise/2.16/user/using-git/changing-author-info": "/en/enterprise/2.16/user/github/using-git/changing-author-info", - "/en/enterprise/2.16/github/using-git/changing-author-info": "/en/enterprise/2.16/user/github/using-git/changing-author-info", - "/enterprise/2.16/user/github/using-git/changing-author-info": "/en/enterprise/2.16/user/github/using-git/changing-author-info", - "/enterprise/2.16/user/using-git/changing-author-info": "/en/enterprise/2.16/user/github/using-git/changing-author-info", - "/enterprise/2.16/github/using-git/changing-author-info": "/en/enterprise/2.16/user/github/using-git/changing-author-info", - "/en/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/en/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/en/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/en/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/en/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/en/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/en/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/en/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github": "/en/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/en/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/en/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/en/enterprise/2.16/user/using-git/git-workflows": "/en/enterprise/2.16/user/github/using-git/git-workflows", - "/en/enterprise/2.16/github/using-git/git-workflows": "/en/enterprise/2.16/user/github/using-git/git-workflows", - "/enterprise/2.16/user/github/using-git/git-workflows": "/en/enterprise/2.16/user/github/using-git/git-workflows", - "/enterprise/2.16/user/using-git/git-workflows": "/en/enterprise/2.16/user/github/using-git/git-workflows", - "/enterprise/2.16/github/using-git/git-workflows": "/en/enterprise/2.16/user/github/using-git/git-workflows", - "/en/enterprise/2.16/user/using-git/ignoring-files": "/en/enterprise/2.16/user/github/using-git/ignoring-files", - "/en/enterprise/2.16/github/using-git/ignoring-files": "/en/enterprise/2.16/user/github/using-git/ignoring-files", - "/enterprise/2.16/user/github/using-git/ignoring-files": "/en/enterprise/2.16/user/github/using-git/ignoring-files", - "/enterprise/2.16/user/using-git/ignoring-files": "/en/enterprise/2.16/user/github/using-git/ignoring-files", - "/enterprise/2.16/github/using-git/ignoring-files": "/en/enterprise/2.16/user/github/using-git/ignoring-files", - "/en/enterprise/2.16/user/using-git": "/en/enterprise/2.16/user/github/using-git", - "/en/enterprise/2.16/github/using-git": "/en/enterprise/2.16/user/github/using-git", - "/enterprise/2.16/user/github/using-git": "/en/enterprise/2.16/user/github/using-git", - "/enterprise/2.16/user/using-git": "/en/enterprise/2.16/user/github/using-git", - "/enterprise/2.16/github/using-git": "/en/enterprise/2.16/user/github/using-git", - "/en/enterprise/2.16/user/using-git/learning-about-git": "/en/enterprise/2.16/user/github/using-git/learning-about-git", - "/en/enterprise/2.16/github/using-git/learning-about-git": "/en/enterprise/2.16/user/github/using-git/learning-about-git", - "/enterprise/2.16/user/github/using-git/learning-about-git": "/en/enterprise/2.16/user/github/using-git/learning-about-git", - "/enterprise/2.16/user/using-git/learning-about-git": "/en/enterprise/2.16/user/github/using-git/learning-about-git", - "/enterprise/2.16/github/using-git/learning-about-git": "/en/enterprise/2.16/user/github/using-git/learning-about-git", - "/en/enterprise/2.16/user/using-git/managing-remote-repositories": "/en/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/en/enterprise/2.16/github/using-git/managing-remote-repositories": "/en/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/enterprise/2.16/user/github/using-git/managing-remote-repositories": "/en/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/enterprise/2.16/user/using-git/managing-remote-repositories": "/en/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/enterprise/2.16/github/using-git/managing-remote-repositories": "/en/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/en/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/en/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/en/enterprise/2.16/user/using-git/removing-a-remote": "/en/enterprise/2.16/user/github/using-git/removing-a-remote", - "/en/enterprise/2.16/github/using-git/removing-a-remote": "/en/enterprise/2.16/user/github/using-git/removing-a-remote", - "/enterprise/2.16/user/github/using-git/removing-a-remote": "/en/enterprise/2.16/user/github/using-git/removing-a-remote", - "/enterprise/2.16/user/using-git/removing-a-remote": "/en/enterprise/2.16/user/github/using-git/removing-a-remote", - "/enterprise/2.16/github/using-git/removing-a-remote": "/en/enterprise/2.16/user/github/using-git/removing-a-remote", - "/en/enterprise/2.16/user/using-git/renaming-a-remote": "/en/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/en/enterprise/2.16/github/using-git/renaming-a-remote": "/en/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/enterprise/2.16/user/github/using-git/renaming-a-remote": "/en/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/enterprise/2.16/user/using-git/renaming-a-remote": "/en/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/enterprise/2.16/github/using-git/renaming-a-remote": "/en/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/en/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.16/user/using-git/setting-your-username-in-git": "/en/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/en/enterprise/2.16/github/using-git/setting-your-username-in-git": "/en/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/enterprise/2.16/user/github/using-git/setting-your-username-in-git": "/en/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/enterprise/2.16/user/using-git/setting-your-username-in-git": "/en/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/enterprise/2.16/github/using-git/setting-your-username-in-git": "/en/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/en/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.16/user/using-git/using-advanced-git-commands": "/en/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/en/enterprise/2.16/github/using-git/using-advanced-git-commands": "/en/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/enterprise/2.16/user/github/using-git/using-advanced-git-commands": "/en/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/enterprise/2.16/user/using-git/using-advanced-git-commands": "/en/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/enterprise/2.16/github/using-git/using-advanced-git-commands": "/en/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/en/enterprise/2.16/user/using-git/using-common-git-commands": "/en/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/en/enterprise/2.16/github/using-git/using-common-git-commands": "/en/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/enterprise/2.16/user/github/using-git/using-common-git-commands": "/en/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/enterprise/2.16/user/using-git/using-common-git-commands": "/en/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/enterprise/2.16/github/using-git/using-common-git-commands": "/en/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/en/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/en/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/en/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/en/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/en/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/en/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use": "/en/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/en/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/en/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/en/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/en/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/en/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/en/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/en/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/en/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/en/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/en/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/en/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/en/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/en/enterprise/2.16/user/working-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages", - "/en/enterprise/2.16/github/working-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages", - "/enterprise/2.16/user/github/working-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages", - "/enterprise/2.16/user/working-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages", - "/enterprise/2.16/github/working-with-github-pages": "/en/enterprise/2.16/user/github/working-with-github-pages", - "/en/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/en/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/en/enterprise/2.16/user/writing-on-github/about-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/en/enterprise/2.16/github/writing-on-github/about-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/enterprise/2.16/user/github/writing-on-github/about-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/enterprise/2.16/user/writing-on-github/about-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/enterprise/2.16/github/writing-on-github/about-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/en/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/en/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/en/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/en/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/en/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/en/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/en/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/en/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/en/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/en/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/en/enterprise/2.16/user/writing-on-github/creating-gists": "/en/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/en/enterprise/2.16/github/writing-on-github/creating-gists": "/en/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/enterprise/2.16/user/github/writing-on-github/creating-gists": "/en/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/enterprise/2.16/user/writing-on-github/creating-gists": "/en/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/enterprise/2.16/github/writing-on-github/creating-gists": "/en/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/en/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/en/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/en/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/en/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/en/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/en/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/en/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/en/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/en/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.16/user/writing-on-github": "/en/enterprise/2.16/user/github/writing-on-github", - "/en/enterprise/2.16/github/writing-on-github": "/en/enterprise/2.16/user/github/writing-on-github", - "/enterprise/2.16/user/github/writing-on-github": "/en/enterprise/2.16/user/github/writing-on-github", - "/enterprise/2.16/user/writing-on-github": "/en/enterprise/2.16/user/github/writing-on-github", - "/enterprise/2.16/github/writing-on-github": "/en/enterprise/2.16/user/github/writing-on-github", - "/en/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/en/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/en/enterprise/2.16/user/writing-on-github/using-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/en/enterprise/2.16/github/writing-on-github/using-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/enterprise/2.16/user/github/writing-on-github/using-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/enterprise/2.16/user/writing-on-github/using-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/enterprise/2.16/github/writing-on-github/using-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/en/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/en/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/en/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/en/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/en/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/en/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/en/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/en/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/en/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/en/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/en/enterprise/2.16/insights": "/en/enterprise/2.16/user/insights", - "/enterprise/2.16/user/insights": "/en/enterprise/2.16/user/insights", - "/enterprise/2.16/insights": "/en/enterprise/2.16/user/insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/en/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/en/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/es/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/es/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/es/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/es/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/es/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/es/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/es/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/es/enterprise/2.16/admin/articles/using-github-task-runner", - "/es/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/es/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/es/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/es/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/es/enterprise/2.16/admin/guides/clustering/clustering-overview": "/es/enterprise/2.16/admin/clustering/clustering-overview", - "/es/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/es/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/es/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/es/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/es/enterprise/2.16/admin/guides/clustering": "/es/enterprise/2.16/admin/clustering", - "/es/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/es/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/es/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/es/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/es/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/es/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/es/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/es/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/es/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/es/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/es/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/es/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/es/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/es/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/es/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/es/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/es/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/es/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/es/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/es/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/es/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/es/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/es/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/es/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/es/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/es/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/es/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/es/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/es/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/es/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/es/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/es/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/es/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/es/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/es/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/es/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/es/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/es/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/es/enterprise/2.16/admin/guides/developer-workflow": "/es/enterprise/2.16/admin/developer-workflow", - "/es/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/es/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/es/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/es/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/es/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/es/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/es/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/es/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/es/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/es/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/es/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/es/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/es/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/es/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/es/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/es/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/es/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/es/enterprise/2.16/admin/guides/enterprise-support": "/es/enterprise/2.16/admin/enterprise-support", - "/es/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/es/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/es/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/es/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/es/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/es/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/es/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/es/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/es/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/es/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/es/enterprise/2.16/admin/guides": "/es/enterprise/2.16/admin", - "/es/enterprise/2.16/admin/guides/installation/about-geo-replication": "/es/enterprise/2.16/admin/installation/about-geo-replication", - "/es/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/es/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/es/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/es/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/es/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/es/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/es/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/es/enterprise/2.16/admin/installation/accessing-the-management-console", - "/es/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/es/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/es/enterprise/2.16/admin/guides/installation/activity-dashboard": "/es/enterprise/2.16/admin/installation/activity-dashboard", - "/es/enterprise/2.16/admin/guides/installation/audit-logging": "/es/enterprise/2.16/admin/installation/audit-logging", - "/es/enterprise/2.16/admin/guides/installation/audited-actions": "/es/enterprise/2.16/admin/installation/audited-actions", - "/es/enterprise/2.16/admin/guides/installation/command-line-utilities": "/es/enterprise/2.16/admin/installation/command-line-utilities", - "/es/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/es/enterprise/2.16/admin/installation/configuring-a-hostname", - "/es/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/es/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/es/enterprise/2.16/admin/guides/installation/configuring-applications": "/es/enterprise/2.16/admin/installation/configuring-applications", - "/es/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/es/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/es/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/es/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/es/enterprise/2.16/admin/guides/installation/configuring-collectd": "/es/enterprise/2.16/admin/installation/configuring-collectd", - "/es/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/es/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/es/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/es/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/es/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/es/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/es/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/es/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/es/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/es/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/es/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/es/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/es/enterprise/2.16/admin/installation/configuring-rate-limits", - "/es/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/es/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/es/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/es/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/es/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/es/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/es/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/es/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/es/enterprise/2.16/admin/guides/installation/configuring-tls": "/es/enterprise/2.16/admin/installation/configuring-tls", - "/es/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/es/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/es/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/es/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/es/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/es/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/es/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/es/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/es/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/es/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/es/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/es/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/es/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/es/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/es/enterprise/2.16/admin/installation/enabling-private-mode", - "/es/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/es/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/es/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/es/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/es/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/es/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/es/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/es/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/es/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/es/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/es/enterprise/2.16/admin/guides/installation": "/es/enterprise/2.16/admin/installation", - "/es/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/es/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/es/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/es/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/es/enterprise/2.16/admin/guides/installation/log-forwarding": "/es/enterprise/2.16/admin/installation/log-forwarding", - "/es/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/es/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/es/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/es/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/es/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/es/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/es/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/es/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/es/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/es/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/es/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/es/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/es/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/es/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/es/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/es/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/es/enterprise/2.16/admin/guides/installation/network-ports": "/es/enterprise/2.16/admin/installation/network-ports", - "/es/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/es/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/es/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/es/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/es/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/es/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/es/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/es/enterprise/2.16/admin/installation/searching-the-audit-log", - "/es/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/es/enterprise/2.16/admin/installation/setting-git-push-limits", - "/es/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/es/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/es/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/es/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/es/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/es/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/es/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/es/enterprise/2.16/admin/installation/site-admin-dashboard", - "/es/enterprise/2.16/admin/guides/installation/system-overview": "/es/enterprise/2.16/admin/installation/system-overview", - "/es/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/es/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/es/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/es/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/es/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/es/enterprise/2.16/admin/installation/upgrade-requirements", - "/es/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/es/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/es/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/es/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/es/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/es/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/es/enterprise/2.16/admin/installation/viewing-push-logs", - "/es/enterprise/2.16/admin/guides/migrations/about-migrations": "/es/enterprise/2.16/admin/migrations/about-migrations", - "/es/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/es/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/es/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/es/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/es/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/es/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/es/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/es/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/es/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/es/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/es/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/es/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/es/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/es/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/es/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/migrations": "/es/enterprise/2.16/admin/migrations", - "/es/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/es/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/es/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/es/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/es/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/es/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/es/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/es/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/es/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/es/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/es/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/es/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/es/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/es/enterprise/2.16/admin/user-management/about-global-webhooks", - "/es/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/es/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/es/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/es/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/es/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/es/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/es/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/es/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/es/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/es/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/es/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/es/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/es/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/es/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/es/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/es/enterprise/2.16/admin/user-management/basic-account-settings", - "/es/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/es/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/es/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/es/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/es/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/es/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/es/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/es/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/es/enterprise/2.16/admin/guides/user-management/creating-organizations": "/es/enterprise/2.16/admin/user-management/creating-organizations", - "/es/enterprise/2.16/admin/guides/user-management/creating-teams": "/es/enterprise/2.16/admin/user-management/creating-teams", - "/es/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/es/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/es/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/es/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/es/enterprise/2.16/admin/guides/user-management": "/es/enterprise/2.16/admin/user-management", - "/es/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/es/enterprise/2.16/admin/user-management/managing-dormant-users", - "/es/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/es/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/es/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/es/enterprise/2.16/admin/user-management/organizations-and-teams", - "/es/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/es/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/es/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/es/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/es/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/es/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/es/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/es/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/es/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/es/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/es/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/es/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/es/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/es/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/es/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/es/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/es/enterprise/2.16/admin/guides/user-management/repositories": "/es/enterprise/2.16/admin/user-management/repositories", - "/es/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/es/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/es/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/es/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/es/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/es/enterprise/2.16/admin/guides/user-management/user-security": "/es/enterprise/2.16/admin/user-management/user-security", - "/es/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/es/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/es/enterprise/2.16/admin/guides/user-management/using-cas": "/es/enterprise/2.16/admin/user-management/using-cas", - "/es/enterprise/2.16/admin/guides/user-management/using-ldap": "/es/enterprise/2.16/admin/user-management/using-ldap", - "/es/enterprise/2.16/admin/guides/user-management/using-saml": "/es/enterprise/2.16/admin/user-management/using-saml", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/es/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/es/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/es/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/es/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/es/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/es/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/es/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/es/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/es/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/es/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/es/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/es/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/es/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/es/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/es/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/es/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/es/enterprise/2.16/user/administering-a-repository/about-releases": "/es/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/es/enterprise/2.16/github/administering-a-repository/about-releases": "/es/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/es/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/es/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/es/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/es/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/es/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/es/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/es/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/es/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/es/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/es/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/es/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/es/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/es/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/es/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/es/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/es/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/es/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/es/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/es/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/es/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/es/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/es/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/es/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/es/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/es/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/es/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/es/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/es/enterprise/2.16/user/administering-a-repository/creating-releases": "/es/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/es/enterprise/2.16/github/administering-a-repository/creating-releases": "/es/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/es/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/es/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/es/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/es/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/es/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/es/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/es/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/es/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/es/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/es/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/es/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/es/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/es/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/es/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/es/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/es/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/es/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/es/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository", - "/es/enterprise/2.16/user/administering-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository", - "/es/enterprise/2.16/github/administering-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/es/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/es/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/es/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/es/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/es/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/es/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/es/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/es/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/es/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/es/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/es/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/es/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/es/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/es/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/es/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/es/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/es/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/es/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/es/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/es/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/es/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/es/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/es/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/es/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/es/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/es/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/es/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/es/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/es/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/es/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/es/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/es/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/es/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/es/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/es/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/es/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/es/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/es/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/es/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/es/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/es/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/es/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/es/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/es/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/es/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/es/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/es/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/es/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/es/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/es/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/es/enterprise/2.16/user/authenticating-to-github/about-ssh": "/es/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/es/enterprise/2.16/github/authenticating-to-github/about-ssh": "/es/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/es/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/es/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/es/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/es/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/es/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/es/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/es/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/es/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/es/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/es/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/es/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/es/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/es/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/es/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/es/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/es/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/es/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/es/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/es/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/es/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/es/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/es/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/es/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/es/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/es/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/es/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/es/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/es/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/es/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/es/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/es/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/es/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/es/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/es/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/es/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/es/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/es/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/es/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/es/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/es/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/es/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/es/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/es/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/es/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/es/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/es/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/es/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/es/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/es/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/es/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/es/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/es/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/es/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/es/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/es/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/es/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/es/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/es/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/es/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/es/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/es/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/es/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/es/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/es/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/es/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/es/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/es/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/es/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/es/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/es/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/es/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/es/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/es/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/es/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/es/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/es/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/es/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/es/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/es/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/es/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/es/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/es/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/es/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/es/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/es/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/es/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/es/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/es/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/es/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/es/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/es/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/es/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/es/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/es/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/es/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/es/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/es/enterprise/2.16/user/authenticating-to-github": "/es/enterprise/2.16/user/github/authenticating-to-github", - "/es/enterprise/2.16/github/authenticating-to-github": "/es/enterprise/2.16/user/github/authenticating-to-github", - "/es/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/es/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/es/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/es/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/es/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/es/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/es/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/es/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/es/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/es/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/es/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/es/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/es/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/es/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/es/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/es/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/es/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/es/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/es/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/es/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/es/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/es/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/es/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/es/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/es/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/es/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/es/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/es/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/es/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/es/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/es/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/es/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/es/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/es/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/es/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/es/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/es/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/es/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/es/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/es/enterprise/2.16/user/authenticating-to-github/signing-commits": "/es/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/es/enterprise/2.16/github/authenticating-to-github/signing-commits": "/es/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/es/enterprise/2.16/user/authenticating-to-github/signing-tags": "/es/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/es/enterprise/2.16/github/authenticating-to-github/signing-tags": "/es/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/es/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/es/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/es/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/es/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/es/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/es/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/es/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/es/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/es/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/es/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/es/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/es/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/es/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/es/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/es/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/es/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/es/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/es/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/es/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/es/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/es/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/es/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/es/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/es/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/es/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/es/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/es/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/es/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/es/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/es/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/es/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/es/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/es/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/es/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/es/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/es/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/es/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/es/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/es/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/es/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/es/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/es/enterprise/2.16/user/building-a-strong-community/about-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/es/enterprise/2.16/github/building-a-strong-community/about-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/es/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/es/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/es/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/es/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/es/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/es/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/es/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/es/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/es/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/es/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/es/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/es/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/es/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/es/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/es/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/es/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/es/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/es/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/es/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/es/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/es/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/es/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/es/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/es/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/es/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/es/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/es/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/es/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/es/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/es/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/es/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/es/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/es/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/es/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/es/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/es/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/es/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/es/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/es/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/es/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/es/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/es/enterprise/2.16/user/building-a-strong-community": "/es/enterprise/2.16/user/github/building-a-strong-community", - "/es/enterprise/2.16/github/building-a-strong-community": "/es/enterprise/2.16/user/github/building-a-strong-community", - "/es/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/es/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/es/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/es/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/es/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/es/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/es/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/es/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/es/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/es/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/es/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/es/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/es/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/es/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/es/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/es/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/es/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/es/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/es/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/es/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/es/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/es/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/es/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/es/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/es/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/es/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/es/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/es/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/es/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/es/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/es/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/es/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/es/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/es/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/es/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/es/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/es/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/es/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/es/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/es/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/es/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/es/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/es/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/es/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/es/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/es/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/es/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/es/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/es/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/es/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/es/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/es/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/es/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/es/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/es/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/es/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/es/enterprise/2.16/user/committing-changes-to-your-project": "/es/enterprise/2.16/user/github/committing-changes-to-your-project", - "/es/enterprise/2.16/github/committing-changes-to-your-project": "/es/enterprise/2.16/user/github/committing-changes-to-your-project", - "/es/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/es/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/es/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/es/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/es/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/es/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/es/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/es/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/es/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/es/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/es/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/es/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/es/enterprise/2.16/user/extending-github/about-webhooks": "/es/enterprise/2.16/user/github/extending-github/about-webhooks", - "/es/enterprise/2.16/github/extending-github/about-webhooks": "/es/enterprise/2.16/user/github/extending-github/about-webhooks", - "/es/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/es/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/es/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/es/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/es/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/es/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/es/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/es/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/es/enterprise/2.16/user/extending-github": "/es/enterprise/2.16/user/github/extending-github", - "/es/enterprise/2.16/github/extending-github": "/es/enterprise/2.16/user/github/extending-github", - "/es/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/es/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/es/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/es/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/es/enterprise/2.16/user/getting-started-with-github/be-social": "/es/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/es/enterprise/2.16/github/getting-started-with-github/be-social": "/es/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/es/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/es/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/es/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/es/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/es/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/es/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/es/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/es/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/es/enterprise/2.16/user/getting-started-with-github/following-people": "/es/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/es/enterprise/2.16/github/getting-started-with-github/following-people": "/es/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/es/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/es/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/es/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/es/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/es/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/es/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/es/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/es/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/es/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/es/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/es/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/es/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/es/enterprise/2.16/user/getting-started-with-github/github-glossary": "/es/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/es/enterprise/2.16/github/getting-started-with-github/github-glossary": "/es/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/es/enterprise/2.16/user/getting-started-with-github": "/es/enterprise/2.16/user/github/getting-started-with-github", - "/es/enterprise/2.16/github/getting-started-with-github": "/es/enterprise/2.16/user/github/getting-started-with-github", - "/es/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/es/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/es/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/es/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/es/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/es/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/es/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/es/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/es/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/es/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/es/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/es/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/es/enterprise/2.16/user/getting-started-with-github/set-up-git": "/es/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/es/enterprise/2.16/github/getting-started-with-github/set-up-git": "/es/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/es/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/es/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/es/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/es/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/es/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/es/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/es/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/es/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/es/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/es/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/es/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/es/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/es/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/es/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/es/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/es/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/es/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/es/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/es/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/es/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/es/enterprise/2.16/user/getting-started-with-github/using-github": "/es/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/es/enterprise/2.16/github/getting-started-with-github/using-github": "/es/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/es/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/es/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/es/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/es/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/es/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/es/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/es/enterprise/2.16/user/importing-your-projects-to-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github", - "/es/enterprise/2.16/github/importing-your-projects-to-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github", - "/es/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/es/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/es/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/es/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/es/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/es/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/es/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/es/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/es/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/es/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/es/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/es/enterprise/2.16/user": "/es/enterprise/2.16/user/github", - "/es/enterprise/2.16/github": "/es/enterprise/2.16/user/github", - "/es/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/es/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/es/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/es/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/es/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/es/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/es/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/es/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/es/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/es/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/es/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/es/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/es/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/es/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/es/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/es/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/es/enterprise/2.16/user/managing-files-in-a-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository", - "/es/enterprise/2.16/github/managing-files-in-a-repository": "/es/enterprise/2.16/user/github/managing-files-in-a-repository", - "/es/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/es/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/es/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/es/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/es/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/es/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/es/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/es/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/es/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/es/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/es/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/es/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/es/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/es/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/es/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/es/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/es/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/es/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/es/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/es/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/es/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/es/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/es/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/es/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/es/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/es/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/es/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/es/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/es/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/es/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/es/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/es/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/es/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/es/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/es/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/es/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/es/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/es/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/es/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/es/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/es/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/es/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/es/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/es/enterprise/2.16/user/managing-large-files": "/es/enterprise/2.16/user/github/managing-large-files", - "/es/enterprise/2.16/github/managing-large-files": "/es/enterprise/2.16/user/github/managing-large-files", - "/es/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/es/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/es/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/es/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/es/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/es/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/es/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/es/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/es/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/es/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/es/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/es/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/es/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/es/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/es/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/es/enterprise/2.16/user/managing-large-files/versioning-large-files": "/es/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/es/enterprise/2.16/github/managing-large-files/versioning-large-files": "/es/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/es/enterprise/2.16/user/managing-large-files/working-with-large-files": "/es/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/es/enterprise/2.16/github/managing-large-files/working-with-large-files": "/es/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/es/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/es/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/es/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/es/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/es/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/es/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/es/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/es/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/es/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/es/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/es/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/es/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/es/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/es/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/es/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/es/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/es/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/es/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/es/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/es/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/es/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/es/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/es/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/es/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/es/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/es/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/es/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/es/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/es/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/es/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/es/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/es/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/es/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/es/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/es/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/es/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/es/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/es/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/es/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/es/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/es/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/es/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/es/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/es/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/es/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/es/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/es/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/es/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/es/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/es/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/es/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/es/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/es/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/es/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/es/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/es/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/es/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/es/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/es/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/es/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/es/enterprise/2.16/user/managing-your-work-on-github": "/es/enterprise/2.16/user/github/managing-your-work-on-github", - "/es/enterprise/2.16/github/managing-your-work-on-github": "/es/enterprise/2.16/user/github/managing-your-work-on-github", - "/es/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/es/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/es/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/es/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/es/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/es/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/es/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/es/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/es/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/es/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/es/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/es/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/es/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/es/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/es/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/es/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/es/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/es/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/es/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/es/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/es/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/es/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/es/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/es/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/es/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/es/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/es/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/es/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/es/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/es/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/es/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/es/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/es/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/es/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/es/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/es/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/es/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/es/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/es/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/es/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/es/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/es/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/es/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/es/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/es/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/es/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/es/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/es/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/es/enterprise/2.16/user/searching-for-information-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github", - "/es/enterprise/2.16/github/searching-for-information-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/es/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/es/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/es/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/es/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/es/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/es/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/es/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/es/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/es/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/es/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/es/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/es/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/es/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/es/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/es/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/es/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/es/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/es/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/es/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/es/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/es/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/es/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/es/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/es/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/es/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/es/enterprise/2.16/user/using-git/about-git-rebase": "/es/enterprise/2.16/user/github/using-git/about-git-rebase", - "/es/enterprise/2.16/github/using-git/about-git-rebase": "/es/enterprise/2.16/user/github/using-git/about-git-rebase", - "/es/enterprise/2.16/user/using-git/about-git-subtree-merges": "/es/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/es/enterprise/2.16/github/using-git/about-git-subtree-merges": "/es/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/es/enterprise/2.16/user/using-git/about-remote-repositories": "/es/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/es/enterprise/2.16/github/using-git/about-remote-repositories": "/es/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/es/enterprise/2.16/user/using-git/adding-a-remote": "/es/enterprise/2.16/user/github/using-git/adding-a-remote", - "/es/enterprise/2.16/github/using-git/adding-a-remote": "/es/enterprise/2.16/user/github/using-git/adding-a-remote", - "/es/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/es/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/es/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/es/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/es/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/es/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/es/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/es/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/es/enterprise/2.16/user/using-git/changing-a-remotes-url": "/es/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/es/enterprise/2.16/github/using-git/changing-a-remotes-url": "/es/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/es/enterprise/2.16/user/using-git/changing-author-info": "/es/enterprise/2.16/user/github/using-git/changing-author-info", - "/es/enterprise/2.16/github/using-git/changing-author-info": "/es/enterprise/2.16/user/github/using-git/changing-author-info", - "/es/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/es/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/es/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/es/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/es/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/es/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/es/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/es/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/es/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/es/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/es/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/es/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/es/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/es/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/es/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/es/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/es/enterprise/2.16/user/using-git/git-workflows": "/es/enterprise/2.16/user/github/using-git/git-workflows", - "/es/enterprise/2.16/github/using-git/git-workflows": "/es/enterprise/2.16/user/github/using-git/git-workflows", - "/es/enterprise/2.16/user/using-git/ignoring-files": "/es/enterprise/2.16/user/github/using-git/ignoring-files", - "/es/enterprise/2.16/github/using-git/ignoring-files": "/es/enterprise/2.16/user/github/using-git/ignoring-files", - "/es/enterprise/2.16/user/using-git": "/es/enterprise/2.16/user/github/using-git", - "/es/enterprise/2.16/github/using-git": "/es/enterprise/2.16/user/github/using-git", - "/es/enterprise/2.16/user/using-git/learning-about-git": "/es/enterprise/2.16/user/github/using-git/learning-about-git", - "/es/enterprise/2.16/github/using-git/learning-about-git": "/es/enterprise/2.16/user/github/using-git/learning-about-git", - "/es/enterprise/2.16/user/using-git/managing-remote-repositories": "/es/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/es/enterprise/2.16/github/using-git/managing-remote-repositories": "/es/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/es/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/es/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/es/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/es/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/es/enterprise/2.16/user/using-git/removing-a-remote": "/es/enterprise/2.16/user/github/using-git/removing-a-remote", - "/es/enterprise/2.16/github/using-git/removing-a-remote": "/es/enterprise/2.16/user/github/using-git/removing-a-remote", - "/es/enterprise/2.16/user/using-git/renaming-a-remote": "/es/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/es/enterprise/2.16/github/using-git/renaming-a-remote": "/es/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/es/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/es/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/es/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/es/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/es/enterprise/2.16/user/using-git/setting-your-username-in-git": "/es/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/es/enterprise/2.16/github/using-git/setting-your-username-in-git": "/es/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/es/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/es/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/es/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/es/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/es/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/es/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/es/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/es/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/es/enterprise/2.16/user/using-git/using-advanced-git-commands": "/es/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/es/enterprise/2.16/github/using-git/using-advanced-git-commands": "/es/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/es/enterprise/2.16/user/using-git/using-common-git-commands": "/es/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/es/enterprise/2.16/github/using-git/using-common-git-commands": "/es/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/es/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/es/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/es/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/es/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/es/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/es/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/es/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/es/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/es/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/es/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/es/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/es/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/es/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/es/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/es/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/es/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/es/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/es/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/es/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/es/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/es/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/es/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/es/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/es/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/es/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/es/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/es/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/es/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/es/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/es/enterprise/2.16/user/working-with-github-pages": "/es/enterprise/2.16/user/github/working-with-github-pages", - "/es/enterprise/2.16/github/working-with-github-pages": "/es/enterprise/2.16/user/github/working-with-github-pages", - "/es/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/es/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/es/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/es/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/es/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/es/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/es/enterprise/2.16/user/writing-on-github/about-saved-replies": "/es/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/es/enterprise/2.16/github/writing-on-github/about-saved-replies": "/es/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/es/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/es/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/es/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/es/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/es/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/es/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/es/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/es/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/es/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/es/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/es/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/es/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/es/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/es/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/es/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/es/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/es/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/es/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/es/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/es/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/es/enterprise/2.16/user/writing-on-github/creating-gists": "/es/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/es/enterprise/2.16/github/writing-on-github/creating-gists": "/es/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/es/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/es/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/es/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/es/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/es/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/es/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/es/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/es/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/es/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/es/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/es/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/es/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/es/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/es/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/es/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/es/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/es/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/es/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/es/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/es/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/es/enterprise/2.16/user/writing-on-github": "/es/enterprise/2.16/user/github/writing-on-github", - "/es/enterprise/2.16/github/writing-on-github": "/es/enterprise/2.16/user/github/writing-on-github", - "/es/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/es/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/es/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/es/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/es/enterprise/2.16/user/writing-on-github/using-saved-replies": "/es/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/es/enterprise/2.16/github/writing-on-github/using-saved-replies": "/es/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/es/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/es/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/es/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/es/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/es/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/es/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/es/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/es/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/es/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/es/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/es/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/es/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/es/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/es/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/es/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/es/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/es/enterprise/2.16/insights": "/es/enterprise/2.16/user/insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/es/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/es/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/ja/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/ja/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/ja/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/ja/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/ja/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/ja/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/ja/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/ja/enterprise/2.16/admin/articles/using-github-task-runner", - "/ja/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/ja/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/ja/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/ja/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/ja/enterprise/2.16/admin/guides/clustering/clustering-overview": "/ja/enterprise/2.16/admin/clustering/clustering-overview", - "/ja/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/ja/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/ja/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/ja/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/ja/enterprise/2.16/admin/guides/clustering": "/ja/enterprise/2.16/admin/clustering", - "/ja/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/ja/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/ja/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/ja/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/ja/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/ja/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/ja/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/ja/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/ja/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/ja/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/ja/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/ja/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/ja/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/ja/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/ja/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/ja/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/ja/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/ja/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/ja/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/ja/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/ja/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/ja/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/ja/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/ja/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/ja/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/ja/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/ja/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/ja/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/ja/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/ja/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/ja/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/ja/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/ja/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/ja/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/ja/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/ja/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/ja/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/ja/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/ja/enterprise/2.16/admin/guides/developer-workflow": "/ja/enterprise/2.16/admin/developer-workflow", - "/ja/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/ja/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/ja/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/ja/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/ja/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/ja/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/ja/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/ja/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/ja/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/ja/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/ja/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/ja/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/ja/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/ja/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/ja/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/ja/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/ja/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/ja/enterprise/2.16/admin/guides/enterprise-support": "/ja/enterprise/2.16/admin/enterprise-support", - "/ja/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/ja/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/ja/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/ja/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/ja/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/ja/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/ja/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/ja/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/ja/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/ja/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/ja/enterprise/2.16/admin/guides": "/ja/enterprise/2.16/admin", - "/ja/enterprise/2.16/admin/guides/installation/about-geo-replication": "/ja/enterprise/2.16/admin/installation/about-geo-replication", - "/ja/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/ja/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/ja/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/ja/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/ja/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/ja/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/ja/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/ja/enterprise/2.16/admin/installation/accessing-the-management-console", - "/ja/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/ja/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/ja/enterprise/2.16/admin/guides/installation/activity-dashboard": "/ja/enterprise/2.16/admin/installation/activity-dashboard", - "/ja/enterprise/2.16/admin/guides/installation/audit-logging": "/ja/enterprise/2.16/admin/installation/audit-logging", - "/ja/enterprise/2.16/admin/guides/installation/audited-actions": "/ja/enterprise/2.16/admin/installation/audited-actions", - "/ja/enterprise/2.16/admin/guides/installation/command-line-utilities": "/ja/enterprise/2.16/admin/installation/command-line-utilities", - "/ja/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/ja/enterprise/2.16/admin/installation/configuring-a-hostname", - "/ja/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/ja/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/ja/enterprise/2.16/admin/guides/installation/configuring-applications": "/ja/enterprise/2.16/admin/installation/configuring-applications", - "/ja/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/ja/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/ja/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/ja/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/ja/enterprise/2.16/admin/guides/installation/configuring-collectd": "/ja/enterprise/2.16/admin/installation/configuring-collectd", - "/ja/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/ja/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/ja/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/ja/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/ja/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/ja/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/ja/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/ja/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/ja/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/ja/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/ja/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/ja/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/ja/enterprise/2.16/admin/installation/configuring-rate-limits", - "/ja/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/ja/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/ja/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/ja/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/ja/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/ja/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/ja/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/ja/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/ja/enterprise/2.16/admin/guides/installation/configuring-tls": "/ja/enterprise/2.16/admin/installation/configuring-tls", - "/ja/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/ja/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/ja/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/ja/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/ja/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/ja/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/ja/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/ja/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/ja/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/ja/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/ja/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/ja/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/ja/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/ja/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/ja/enterprise/2.16/admin/installation/enabling-private-mode", - "/ja/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/ja/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/ja/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/ja/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/ja/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/ja/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/ja/enterprise/2.16/admin/guides/installation": "/ja/enterprise/2.16/admin/installation", - "/ja/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/ja/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/ja/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/ja/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/ja/enterprise/2.16/admin/guides/installation/log-forwarding": "/ja/enterprise/2.16/admin/installation/log-forwarding", - "/ja/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/ja/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/ja/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/ja/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/ja/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/ja/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/ja/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/ja/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/ja/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/ja/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/ja/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/ja/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/ja/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/ja/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/ja/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/ja/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/ja/enterprise/2.16/admin/guides/installation/network-ports": "/ja/enterprise/2.16/admin/installation/network-ports", - "/ja/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/ja/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/ja/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/ja/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/ja/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/ja/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/ja/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/ja/enterprise/2.16/admin/installation/searching-the-audit-log", - "/ja/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/ja/enterprise/2.16/admin/installation/setting-git-push-limits", - "/ja/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/ja/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/ja/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/ja/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/ja/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/ja/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/ja/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/ja/enterprise/2.16/admin/installation/site-admin-dashboard", - "/ja/enterprise/2.16/admin/guides/installation/system-overview": "/ja/enterprise/2.16/admin/installation/system-overview", - "/ja/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/ja/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/ja/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/ja/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/ja/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/ja/enterprise/2.16/admin/installation/upgrade-requirements", - "/ja/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/ja/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/ja/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/ja/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/ja/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/ja/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/ja/enterprise/2.16/admin/installation/viewing-push-logs", - "/ja/enterprise/2.16/admin/guides/migrations/about-migrations": "/ja/enterprise/2.16/admin/migrations/about-migrations", - "/ja/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/ja/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/ja/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/ja/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/ja/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/ja/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/ja/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/ja/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/ja/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/ja/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/ja/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/ja/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/ja/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/ja/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/ja/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/migrations": "/ja/enterprise/2.16/admin/migrations", - "/ja/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/ja/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/ja/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/ja/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/ja/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/ja/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/ja/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/ja/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/ja/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/ja/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/ja/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/ja/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/ja/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/ja/enterprise/2.16/admin/user-management/about-global-webhooks", - "/ja/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/ja/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/ja/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/ja/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/ja/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/ja/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/ja/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/ja/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/ja/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/ja/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/ja/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/ja/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/ja/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/ja/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/ja/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/ja/enterprise/2.16/admin/user-management/basic-account-settings", - "/ja/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/ja/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/ja/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/ja/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/ja/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/ja/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/ja/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/ja/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/ja/enterprise/2.16/admin/guides/user-management/creating-organizations": "/ja/enterprise/2.16/admin/user-management/creating-organizations", - "/ja/enterprise/2.16/admin/guides/user-management/creating-teams": "/ja/enterprise/2.16/admin/user-management/creating-teams", - "/ja/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/ja/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/ja/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/ja/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/ja/enterprise/2.16/admin/guides/user-management": "/ja/enterprise/2.16/admin/user-management", - "/ja/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/ja/enterprise/2.16/admin/user-management/managing-dormant-users", - "/ja/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/ja/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/ja/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/ja/enterprise/2.16/admin/user-management/organizations-and-teams", - "/ja/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/ja/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/ja/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/ja/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/ja/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/ja/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/ja/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/ja/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/ja/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/ja/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/ja/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/ja/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/ja/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/ja/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/ja/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/ja/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/ja/enterprise/2.16/admin/guides/user-management/repositories": "/ja/enterprise/2.16/admin/user-management/repositories", - "/ja/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/ja/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/ja/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/ja/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/ja/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/ja/enterprise/2.16/admin/guides/user-management/user-security": "/ja/enterprise/2.16/admin/user-management/user-security", - "/ja/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/ja/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/ja/enterprise/2.16/admin/guides/user-management/using-cas": "/ja/enterprise/2.16/admin/user-management/using-cas", - "/ja/enterprise/2.16/admin/guides/user-management/using-ldap": "/ja/enterprise/2.16/admin/user-management/using-ldap", - "/ja/enterprise/2.16/admin/guides/user-management/using-saml": "/ja/enterprise/2.16/admin/user-management/using-saml", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/ja/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/ja/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/ja/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/ja/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/ja/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/ja/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/ja/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/ja/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/ja/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/ja/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/ja/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/ja/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/ja/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/ja/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/ja/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/ja/enterprise/2.16/user/administering-a-repository/about-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/ja/enterprise/2.16/github/administering-a-repository/about-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/ja/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/ja/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/ja/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/ja/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/ja/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/ja/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/ja/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/ja/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/ja/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/ja/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/ja/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/ja/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/ja/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/ja/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/ja/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/ja/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/ja/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/ja/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/ja/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/ja/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/ja/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/ja/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/ja/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/ja/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/ja/enterprise/2.16/user/administering-a-repository/creating-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/ja/enterprise/2.16/github/administering-a-repository/creating-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/ja/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/ja/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/ja/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/ja/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/ja/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/ja/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/ja/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/ja/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/ja/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/ja/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/ja/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/ja/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository", - "/ja/enterprise/2.16/user/administering-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository", - "/ja/enterprise/2.16/github/administering-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/ja/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/ja/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/ja/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/ja/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/ja/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/ja/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/ja/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/ja/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/ja/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/ja/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/ja/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/ja/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/ja/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/ja/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/ja/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/ja/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/ja/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/ja/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/ja/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/ja/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/ja/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/ja/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/ja/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/ja/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/ja/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/ja/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/ja/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/ja/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/ja/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/ja/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/ja/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/ja/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/ja/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/ja/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/ja/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/ja/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/ja/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/ja/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/ja/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/ja/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/ja/enterprise/2.16/user/authenticating-to-github/about-ssh": "/ja/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/ja/enterprise/2.16/github/authenticating-to-github/about-ssh": "/ja/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/ja/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/ja/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/ja/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/ja/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/ja/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/ja/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/ja/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/ja/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/ja/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/ja/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/ja/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/ja/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/ja/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/ja/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/ja/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/ja/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/ja/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/ja/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/ja/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/ja/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/ja/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/ja/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/ja/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/ja/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/ja/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/ja/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/ja/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/ja/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/ja/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/ja/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/ja/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/ja/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/ja/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/ja/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/ja/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/ja/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/ja/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/ja/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/ja/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/ja/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/ja/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/ja/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/ja/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/ja/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/ja/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/ja/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/ja/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/ja/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/ja/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/ja/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/ja/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/ja/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/ja/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/ja/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/ja/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/ja/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/ja/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/ja/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/ja/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/ja/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/ja/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/ja/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/ja/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/ja/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/ja/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/ja/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/ja/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/ja/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/ja/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/ja/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/ja/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/ja/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/ja/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/ja/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/ja/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/ja/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/ja/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/ja/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/ja/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/ja/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/ja/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/ja/enterprise/2.16/user/authenticating-to-github": "/ja/enterprise/2.16/user/github/authenticating-to-github", - "/ja/enterprise/2.16/github/authenticating-to-github": "/ja/enterprise/2.16/user/github/authenticating-to-github", - "/ja/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/ja/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/ja/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/ja/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/ja/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/ja/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/ja/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/ja/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/ja/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/ja/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/ja/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/ja/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/ja/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/ja/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/ja/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/ja/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/ja/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/ja/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/ja/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/ja/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/ja/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/ja/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/ja/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/ja/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/ja/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/ja/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/ja/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/ja/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/ja/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/ja/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/ja/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/ja/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/ja/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/ja/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/ja/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/ja/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/ja/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/ja/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/ja/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/ja/enterprise/2.16/user/authenticating-to-github/signing-commits": "/ja/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/ja/enterprise/2.16/github/authenticating-to-github/signing-commits": "/ja/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/ja/enterprise/2.16/user/authenticating-to-github/signing-tags": "/ja/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/ja/enterprise/2.16/github/authenticating-to-github/signing-tags": "/ja/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/ja/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/ja/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/ja/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/ja/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/ja/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/ja/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/ja/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/ja/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/ja/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/ja/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/ja/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/ja/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/ja/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/ja/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/ja/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/ja/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/ja/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/ja/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/ja/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/ja/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/ja/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/ja/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/ja/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/ja/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/ja/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/ja/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/ja/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/ja/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/ja/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/ja/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/ja/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/ja/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/ja/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/ja/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/ja/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/ja/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/ja/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/ja/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/ja/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/ja/enterprise/2.16/user/building-a-strong-community/about-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/ja/enterprise/2.16/github/building-a-strong-community/about-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/ja/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/ja/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/ja/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/ja/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/ja/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/ja/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/ja/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/ja/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/ja/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/ja/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/ja/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/ja/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/ja/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/ja/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/ja/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/ja/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/ja/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/ja/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/ja/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/ja/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/ja/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/ja/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/ja/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/ja/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/ja/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/ja/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/ja/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/ja/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/ja/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/ja/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/ja/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/ja/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/ja/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/ja/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/ja/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/ja/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/ja/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/ja/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/ja/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/ja/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/ja/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/ja/enterprise/2.16/user/building-a-strong-community": "/ja/enterprise/2.16/user/github/building-a-strong-community", - "/ja/enterprise/2.16/github/building-a-strong-community": "/ja/enterprise/2.16/user/github/building-a-strong-community", - "/ja/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/ja/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/ja/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/ja/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/ja/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/ja/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/ja/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/ja/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/ja/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/ja/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/ja/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/ja/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/ja/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/ja/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/ja/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/ja/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/ja/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/ja/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/ja/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/ja/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/ja/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/ja/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/ja/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/ja/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/ja/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/ja/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/ja/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/ja/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/ja/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/ja/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/ja/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/ja/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/ja/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/ja/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/ja/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/ja/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/ja/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/ja/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/ja/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/ja/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/ja/enterprise/2.16/user/committing-changes-to-your-project": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project", - "/ja/enterprise/2.16/github/committing-changes-to-your-project": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/ja/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/ja/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/ja/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/ja/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/ja/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/ja/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/ja/enterprise/2.16/user/extending-github/about-webhooks": "/ja/enterprise/2.16/user/github/extending-github/about-webhooks", - "/ja/enterprise/2.16/github/extending-github/about-webhooks": "/ja/enterprise/2.16/user/github/extending-github/about-webhooks", - "/ja/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/ja/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/ja/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/ja/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/ja/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/ja/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/ja/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/ja/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/ja/enterprise/2.16/user/extending-github": "/ja/enterprise/2.16/user/github/extending-github", - "/ja/enterprise/2.16/github/extending-github": "/ja/enterprise/2.16/user/github/extending-github", - "/ja/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/ja/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/ja/enterprise/2.16/user/getting-started-with-github/be-social": "/ja/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/ja/enterprise/2.16/github/getting-started-with-github/be-social": "/ja/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/ja/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/ja/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/ja/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/ja/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/ja/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/ja/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/ja/enterprise/2.16/user/getting-started-with-github/following-people": "/ja/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/ja/enterprise/2.16/github/getting-started-with-github/following-people": "/ja/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/ja/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/ja/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/ja/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/ja/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/ja/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/ja/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/ja/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/ja/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/ja/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/ja/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/ja/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/ja/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/ja/enterprise/2.16/user/getting-started-with-github/github-glossary": "/ja/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/ja/enterprise/2.16/github/getting-started-with-github/github-glossary": "/ja/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/ja/enterprise/2.16/user/getting-started-with-github": "/ja/enterprise/2.16/user/github/getting-started-with-github", - "/ja/enterprise/2.16/github/getting-started-with-github": "/ja/enterprise/2.16/user/github/getting-started-with-github", - "/ja/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/ja/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/ja/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/ja/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/ja/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/ja/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/ja/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/ja/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/ja/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/ja/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/ja/enterprise/2.16/user/getting-started-with-github/set-up-git": "/ja/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/ja/enterprise/2.16/github/getting-started-with-github/set-up-git": "/ja/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/ja/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/ja/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/ja/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/ja/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/ja/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/ja/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/ja/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/ja/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/ja/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/ja/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/ja/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/ja/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/ja/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/ja/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/ja/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/ja/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/ja/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/ja/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/ja/enterprise/2.16/user/getting-started-with-github/using-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/ja/enterprise/2.16/github/getting-started-with-github/using-github": "/ja/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/ja/enterprise/2.16/user/importing-your-projects-to-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github", - "/ja/enterprise/2.16/github/importing-your-projects-to-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/ja/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/ja/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/ja/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/ja/enterprise/2.16/user": "/ja/enterprise/2.16/user/github", - "/ja/enterprise/2.16/github": "/ja/enterprise/2.16/user/github", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/ja/enterprise/2.16/user/managing-files-in-a-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository", - "/ja/enterprise/2.16/github/managing-files-in-a-repository": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/ja/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/ja/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/ja/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/ja/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/ja/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/ja/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/ja/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/ja/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/ja/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/ja/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/ja/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/ja/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/ja/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/ja/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/ja/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/ja/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/ja/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/ja/enterprise/2.16/user/managing-large-files": "/ja/enterprise/2.16/user/github/managing-large-files", - "/ja/enterprise/2.16/github/managing-large-files": "/ja/enterprise/2.16/user/github/managing-large-files", - "/ja/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/ja/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/ja/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/ja/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/ja/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/ja/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/ja/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/ja/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/ja/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/ja/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/ja/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/ja/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/ja/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/ja/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/ja/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/ja/enterprise/2.16/user/managing-large-files/versioning-large-files": "/ja/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/ja/enterprise/2.16/github/managing-large-files/versioning-large-files": "/ja/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/ja/enterprise/2.16/user/managing-large-files/working-with-large-files": "/ja/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/ja/enterprise/2.16/github/managing-large-files/working-with-large-files": "/ja/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/ja/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/ja/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/ja/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/ja/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/ja/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/ja/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/ja/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/ja/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/ja/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/ja/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/ja/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/ja/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/ja/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/ja/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/ja/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/ja/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/ja/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/ja/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/ja/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/ja/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/ja/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/ja/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/ja/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/ja/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/ja/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/ja/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/ja/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/ja/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/ja/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/ja/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/ja/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/ja/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/ja/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/ja/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/ja/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/ja/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/ja/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/ja/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/ja/enterprise/2.16/user/managing-your-work-on-github": "/ja/enterprise/2.16/user/github/managing-your-work-on-github", - "/ja/enterprise/2.16/github/managing-your-work-on-github": "/ja/enterprise/2.16/user/github/managing-your-work-on-github", - "/ja/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/ja/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/ja/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/ja/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/ja/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/ja/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/ja/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/ja/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/ja/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/ja/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/ja/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/ja/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/ja/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/ja/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/ja/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/ja/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/ja/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/ja/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/ja/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/ja/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/ja/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/ja/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/ja/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/ja/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/ja/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/ja/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/ja/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/ja/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/ja/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/ja/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/ja/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/ja/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/ja/enterprise/2.16/user/searching-for-information-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github", - "/ja/enterprise/2.16/github/searching-for-information-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/ja/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/ja/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/ja/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/ja/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/ja/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/ja/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/ja/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/ja/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/ja/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/ja/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/ja/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/ja/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/ja/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/ja/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/ja/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/ja/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/ja/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/ja/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/ja/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/ja/enterprise/2.16/user/using-git/about-git-rebase": "/ja/enterprise/2.16/user/github/using-git/about-git-rebase", - "/ja/enterprise/2.16/github/using-git/about-git-rebase": "/ja/enterprise/2.16/user/github/using-git/about-git-rebase", - "/ja/enterprise/2.16/user/using-git/about-git-subtree-merges": "/ja/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/ja/enterprise/2.16/github/using-git/about-git-subtree-merges": "/ja/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/ja/enterprise/2.16/user/using-git/about-remote-repositories": "/ja/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/ja/enterprise/2.16/github/using-git/about-remote-repositories": "/ja/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/ja/enterprise/2.16/user/using-git/adding-a-remote": "/ja/enterprise/2.16/user/github/using-git/adding-a-remote", - "/ja/enterprise/2.16/github/using-git/adding-a-remote": "/ja/enterprise/2.16/user/github/using-git/adding-a-remote", - "/ja/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/ja/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/ja/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/ja/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/ja/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/ja/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/ja/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/ja/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/ja/enterprise/2.16/user/using-git/changing-a-remotes-url": "/ja/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/ja/enterprise/2.16/github/using-git/changing-a-remotes-url": "/ja/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/ja/enterprise/2.16/user/using-git/changing-author-info": "/ja/enterprise/2.16/user/github/using-git/changing-author-info", - "/ja/enterprise/2.16/github/using-git/changing-author-info": "/ja/enterprise/2.16/user/github/using-git/changing-author-info", - "/ja/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/ja/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/ja/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/ja/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/ja/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/ja/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/ja/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/ja/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/ja/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/ja/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/ja/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/ja/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/ja/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/ja/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/ja/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/ja/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/ja/enterprise/2.16/user/using-git/git-workflows": "/ja/enterprise/2.16/user/github/using-git/git-workflows", - "/ja/enterprise/2.16/github/using-git/git-workflows": "/ja/enterprise/2.16/user/github/using-git/git-workflows", - "/ja/enterprise/2.16/user/using-git/ignoring-files": "/ja/enterprise/2.16/user/github/using-git/ignoring-files", - "/ja/enterprise/2.16/github/using-git/ignoring-files": "/ja/enterprise/2.16/user/github/using-git/ignoring-files", - "/ja/enterprise/2.16/user/using-git": "/ja/enterprise/2.16/user/github/using-git", - "/ja/enterprise/2.16/github/using-git": "/ja/enterprise/2.16/user/github/using-git", - "/ja/enterprise/2.16/user/using-git/learning-about-git": "/ja/enterprise/2.16/user/github/using-git/learning-about-git", - "/ja/enterprise/2.16/github/using-git/learning-about-git": "/ja/enterprise/2.16/user/github/using-git/learning-about-git", - "/ja/enterprise/2.16/user/using-git/managing-remote-repositories": "/ja/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/ja/enterprise/2.16/github/using-git/managing-remote-repositories": "/ja/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/ja/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/ja/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/ja/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/ja/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/ja/enterprise/2.16/user/using-git/removing-a-remote": "/ja/enterprise/2.16/user/github/using-git/removing-a-remote", - "/ja/enterprise/2.16/github/using-git/removing-a-remote": "/ja/enterprise/2.16/user/github/using-git/removing-a-remote", - "/ja/enterprise/2.16/user/using-git/renaming-a-remote": "/ja/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/ja/enterprise/2.16/github/using-git/renaming-a-remote": "/ja/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/ja/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/ja/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/ja/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/ja/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/ja/enterprise/2.16/user/using-git/setting-your-username-in-git": "/ja/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/ja/enterprise/2.16/github/using-git/setting-your-username-in-git": "/ja/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/ja/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/ja/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/ja/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/ja/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/ja/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/ja/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/ja/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/ja/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/ja/enterprise/2.16/user/using-git/using-advanced-git-commands": "/ja/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/ja/enterprise/2.16/github/using-git/using-advanced-git-commands": "/ja/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/ja/enterprise/2.16/user/using-git/using-common-git-commands": "/ja/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/ja/enterprise/2.16/github/using-git/using-common-git-commands": "/ja/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/ja/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/ja/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/ja/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/ja/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/ja/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/ja/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/ja/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/ja/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/ja/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/ja/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/ja/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/ja/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/ja/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/ja/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/ja/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/ja/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/ja/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/ja/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/ja/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/ja/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/ja/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/ja/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/ja/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/ja/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/ja/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/ja/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/ja/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/ja/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/ja/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/ja/enterprise/2.16/user/working-with-github-pages": "/ja/enterprise/2.16/user/github/working-with-github-pages", - "/ja/enterprise/2.16/github/working-with-github-pages": "/ja/enterprise/2.16/user/github/working-with-github-pages", - "/ja/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/ja/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/ja/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/ja/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/ja/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/ja/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/ja/enterprise/2.16/user/writing-on-github/about-saved-replies": "/ja/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/ja/enterprise/2.16/github/writing-on-github/about-saved-replies": "/ja/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/ja/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/ja/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/ja/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/ja/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/ja/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/ja/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/ja/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/ja/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/ja/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/ja/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/ja/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/ja/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/ja/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/ja/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/ja/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/ja/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/ja/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/ja/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/ja/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/ja/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/ja/enterprise/2.16/user/writing-on-github/creating-gists": "/ja/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/ja/enterprise/2.16/github/writing-on-github/creating-gists": "/ja/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/ja/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/ja/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/ja/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/ja/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/ja/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/ja/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/ja/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/ja/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/ja/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/ja/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/ja/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/ja/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/ja/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/ja/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/ja/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/ja/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/ja/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/ja/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/ja/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/ja/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/ja/enterprise/2.16/user/writing-on-github": "/ja/enterprise/2.16/user/github/writing-on-github", - "/ja/enterprise/2.16/github/writing-on-github": "/ja/enterprise/2.16/user/github/writing-on-github", - "/ja/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/ja/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/ja/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/ja/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/ja/enterprise/2.16/user/writing-on-github/using-saved-replies": "/ja/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/ja/enterprise/2.16/github/writing-on-github/using-saved-replies": "/ja/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/ja/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/ja/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/ja/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/ja/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/ja/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/ja/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/ja/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/ja/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/ja/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/ja/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/ja/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/ja/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/ja/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/ja/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/ja/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/ja/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/ja/enterprise/2.16/insights": "/ja/enterprise/2.16/user/insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/ja/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/ja/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/pt/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/pt/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/pt/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/pt/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/pt/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/pt/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", - "/pt/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/pt/enterprise/2.16/admin/articles/using-github-task-runner", - "/pt/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/pt/enterprise/2.16/admin/clustering/about-cluster-nodes", - "/pt/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/pt/enterprise/2.16/admin/clustering/cluster-network-configuration", - "/pt/enterprise/2.16/admin/guides/clustering/clustering-overview": "/pt/enterprise/2.16/admin/clustering/clustering-overview", - "/pt/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/pt/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/pt/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/pt/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", - "/pt/enterprise/2.16/admin/guides/clustering": "/pt/enterprise/2.16/admin/clustering", - "/pt/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/pt/enterprise/2.16/admin/clustering/initializing-the-cluster", - "/pt/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/pt/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", - "/pt/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/pt/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", - "/pt/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/pt/enterprise/2.16/admin/clustering/replacing-a-cluster-node", - "/pt/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/pt/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", - "/pt/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/pt/enterprise/2.16/admin/clustering/upgrading-a-cluster", - "/pt/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/pt/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", - "/pt/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/pt/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/pt/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/pt/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/pt/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/pt/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/pt/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/pt/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/pt/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/pt/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", - "/pt/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/pt/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/pt/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/pt/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", - "/pt/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/pt/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", - "/pt/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/pt/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/pt/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/pt/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/pt/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/pt/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", - "/pt/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/pt/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/pt/enterprise/2.16/admin/guides/developer-workflow": "/pt/enterprise/2.16/admin/developer-workflow", - "/pt/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/pt/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/pt/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/pt/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", - "/pt/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/pt/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", - "/pt/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/pt/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/pt/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/pt/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/pt/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/pt/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", - "/pt/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/pt/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/pt/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/pt/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/pt/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", - "/pt/enterprise/2.16/admin/guides/enterprise-support": "/pt/enterprise/2.16/admin/enterprise-support", - "/pt/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/pt/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", - "/pt/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/pt/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", - "/pt/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/pt/enterprise/2.16/admin/enterprise-support/reaching-github-support", - "/pt/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/pt/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", - "/pt/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/pt/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", - "/pt/enterprise/2.16/admin/guides": "/pt/enterprise/2.16/admin", - "/pt/enterprise/2.16/admin/guides/installation/about-geo-replication": "/pt/enterprise/2.16/admin/installation/about-geo-replication", - "/pt/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/pt/enterprise/2.16/admin/installation/about-high-availability-configuration", - "/pt/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/pt/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", - "/pt/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/pt/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", - "/pt/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/pt/enterprise/2.16/admin/installation/accessing-the-management-console", - "/pt/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/pt/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", - "/pt/enterprise/2.16/admin/guides/installation/activity-dashboard": "/pt/enterprise/2.16/admin/installation/activity-dashboard", - "/pt/enterprise/2.16/admin/guides/installation/audit-logging": "/pt/enterprise/2.16/admin/installation/audit-logging", - "/pt/enterprise/2.16/admin/guides/installation/audited-actions": "/pt/enterprise/2.16/admin/installation/audited-actions", - "/pt/enterprise/2.16/admin/guides/installation/command-line-utilities": "/pt/enterprise/2.16/admin/installation/command-line-utilities", - "/pt/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/pt/enterprise/2.16/admin/installation/configuring-a-hostname", - "/pt/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/pt/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", - "/pt/enterprise/2.16/admin/guides/installation/configuring-applications": "/pt/enterprise/2.16/admin/installation/configuring-applications", - "/pt/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/pt/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", - "/pt/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/pt/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", - "/pt/enterprise/2.16/admin/guides/installation/configuring-collectd": "/pt/enterprise/2.16/admin/installation/configuring-collectd", - "/pt/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/pt/enterprise/2.16/admin/installation/configuring-dns-nameservers", - "/pt/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/pt/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/pt/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/pt/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/pt/enterprise/2.16/admin/installation/configuring-git-large-file-storage", - "/pt/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/pt/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/pt/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/pt/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", - "/pt/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/pt/enterprise/2.16/admin/installation/configuring-rate-limits", - "/pt/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/pt/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/pt/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/pt/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", - "/pt/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/pt/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/pt/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/pt/enterprise/2.16/admin/installation/configuring-time-synchronization", - "/pt/enterprise/2.16/admin/guides/installation/configuring-tls": "/pt/enterprise/2.16/admin/installation/configuring-tls", - "/pt/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/pt/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/pt/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/pt/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/pt/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/pt/enterprise/2.16/admin/installation/creating-a-high-availability-replica", - "/pt/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/pt/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/pt/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/pt/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/pt/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", - "/pt/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/pt/enterprise/2.16/admin/installation/enabling-automatic-update-checks", - "/pt/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/pt/enterprise/2.16/admin/installation/enabling-private-mode", - "/pt/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/pt/enterprise/2.16/admin/installation/enabling-subdomain-isolation", - "/pt/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/pt/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/pt/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/pt/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/pt/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/pt/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", - "/pt/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/pt/enterprise/2.16/admin/installation/increasing-storage-capacity", - "/pt/enterprise/2.16/admin/guides/installation": "/pt/enterprise/2.16/admin/installation", - "/pt/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/pt/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", - "/pt/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/pt/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", - "/pt/enterprise/2.16/admin/guides/installation/log-forwarding": "/pt/enterprise/2.16/admin/installation/log-forwarding", - "/pt/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/pt/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/pt/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/pt/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", - "/pt/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/pt/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/pt/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/pt/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/pt/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/pt/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/pt/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/pt/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/pt/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/pt/enterprise/2.16/admin/installation/monitoring-using-snmp", - "/pt/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/pt/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/pt/enterprise/2.16/admin/guides/installation/network-ports": "/pt/enterprise/2.16/admin/installation/network-ports", - "/pt/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/pt/enterprise/2.16/admin/installation/recommended-alert-thresholds", - "/pt/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/pt/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", - "/pt/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/pt/enterprise/2.16/admin/installation/removing-a-high-availability-replica", - "/pt/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/pt/enterprise/2.16/admin/installation/searching-the-audit-log", - "/pt/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/pt/enterprise/2.16/admin/installation/setting-git-push-limits", - "/pt/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/pt/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", - "/pt/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/pt/enterprise/2.16/admin/installation/setting-up-a-staging-instance", - "/pt/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/pt/enterprise/2.16/admin/installation/setting-up-external-monitoring", - "/pt/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/pt/enterprise/2.16/admin/installation/site-admin-dashboard", - "/pt/enterprise/2.16/admin/guides/installation/system-overview": "/pt/enterprise/2.16/admin/installation/system-overview", - "/pt/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/pt/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", - "/pt/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/pt/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/pt/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/pt/enterprise/2.16/admin/installation/upgrade-requirements", - "/pt/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/pt/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/pt/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/pt/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/pt/enterprise/2.16/admin/installation/validating-your-domain-settings", - "/pt/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/pt/enterprise/2.16/admin/installation/viewing-push-logs", - "/pt/enterprise/2.16/admin/guides/migrations/about-migrations": "/pt/enterprise/2.16/admin/migrations/about-migrations", - "/pt/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/pt/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/pt/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/pt/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/pt/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", - "/pt/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/pt/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/pt/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/pt/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/pt/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/pt/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", - "/pt/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/pt/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", - "/pt/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/pt/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/migrations": "/pt/enterprise/2.16/admin/migrations", - "/pt/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/pt/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/pt/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/pt/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", - "/pt/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/pt/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/pt/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/pt/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/pt/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/pt/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", - "/pt/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/pt/enterprise/2.16/admin/migrations/reviewing-migration-data", - "/pt/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/pt/enterprise/2.16/admin/user-management/about-global-webhooks", - "/pt/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/pt/enterprise/2.16/admin/user-management/adding-people-to-teams", - "/pt/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/pt/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/pt/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/pt/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/pt/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/pt/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", - "/pt/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/pt/enterprise/2.16/admin/user-management/auditing-ssh-keys", - "/pt/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/pt/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", - "/pt/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/pt/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/pt/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/pt/enterprise/2.16/admin/user-management/basic-account-settings", - "/pt/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/pt/enterprise/2.16/admin/user-management/best-practices-for-user-security", - "/pt/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/pt/enterprise/2.16/admin/user-management/changing-authentication-methods", - "/pt/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/pt/enterprise/2.16/admin/user-management/configuring-email-for-notifications", - "/pt/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/pt/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", - "/pt/enterprise/2.16/admin/guides/user-management/creating-organizations": "/pt/enterprise/2.16/admin/user-management/creating-organizations", - "/pt/enterprise/2.16/admin/guides/user-management/creating-teams": "/pt/enterprise/2.16/admin/user-management/creating-teams", - "/pt/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/pt/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", - "/pt/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/pt/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", - "/pt/enterprise/2.16/admin/guides/user-management": "/pt/enterprise/2.16/admin/user-management", - "/pt/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/pt/enterprise/2.16/admin/user-management/managing-dormant-users", - "/pt/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/pt/enterprise/2.16/admin/user-management/managing-global-webhooks", - "/pt/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/pt/enterprise/2.16/admin/user-management/organizations-and-teams", - "/pt/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/pt/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/pt/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/pt/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/pt/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/pt/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/pt/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/pt/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", - "/pt/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/pt/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/pt/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/pt/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", - "/pt/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/pt/enterprise/2.16/admin/user-management/rebuilding-contributions-data", - "/pt/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/pt/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", - "/pt/enterprise/2.16/admin/guides/user-management/repositories": "/pt/enterprise/2.16/admin/user-management/repositories", - "/pt/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/pt/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/pt/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", - "/pt/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/pt/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", - "/pt/enterprise/2.16/admin/guides/user-management/user-security": "/pt/enterprise/2.16/admin/user-management/user-security", - "/pt/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/pt/enterprise/2.16/admin/user-management/using-built-in-authentication", - "/pt/enterprise/2.16/admin/guides/user-management/using-cas": "/pt/enterprise/2.16/admin/user-management/using-cas", - "/pt/enterprise/2.16/admin/guides/user-management/using-ldap": "/pt/enterprise/2.16/admin/user-management/using-ldap", - "/pt/enterprise/2.16/admin/guides/user-management/using-saml": "/pt/enterprise/2.16/admin/user-management/using-saml", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/pt/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/pt/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/pt/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/pt/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/pt/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/pt/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/pt/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/pt/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/pt/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/pt/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/pt/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/pt/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/pt/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/pt/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/pt/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/pt/enterprise/2.16/user/administering-a-repository/about-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/pt/enterprise/2.16/github/administering-a-repository/about-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/about-releases", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/pt/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/pt/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/pt/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/pt/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/pt/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/pt/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/pt/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/pt/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/pt/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/pt/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/pt/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/pt/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/pt/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/pt/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/pt/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/pt/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/pt/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/pt/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/pt/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/pt/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/pt/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/pt/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/pt/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/pt/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/pt/enterprise/2.16/user/administering-a-repository/creating-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/pt/enterprise/2.16/github/administering-a-repository/creating-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/creating-releases", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/pt/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/pt/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/pt/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/pt/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/pt/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/pt/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/pt/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/pt/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/pt/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/pt/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/pt/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/pt/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository", - "/pt/enterprise/2.16/user/administering-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository", - "/pt/enterprise/2.16/github/administering-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/pt/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/pt/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/pt/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/pt/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/pt/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/pt/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/pt/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/pt/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/pt/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/pt/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/pt/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/pt/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/pt/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/pt/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/pt/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/pt/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/pt/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/pt/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/pt/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/pt/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/pt/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/pt/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/pt/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/pt/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/pt/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/pt/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/pt/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/pt/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/pt/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/pt/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/pt/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/pt/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/pt/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/pt/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/pt/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/pt/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", - "/pt/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/pt/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/pt/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/pt/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", - "/pt/enterprise/2.16/user/authenticating-to-github/about-ssh": "/pt/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/pt/enterprise/2.16/github/authenticating-to-github/about-ssh": "/pt/enterprise/2.16/user/github/authenticating-to-github/about-ssh", - "/pt/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/pt/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/pt/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/pt/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", - "/pt/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/pt/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/pt/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/pt/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/pt/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/pt/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/pt/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/pt/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/pt/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/pt/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/pt/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/pt/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/pt/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/pt/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/pt/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/pt/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/pt/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/pt/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", - "/pt/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/pt/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/pt/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/pt/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/pt/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/pt/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/pt/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/pt/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/pt/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/pt/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/pt/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/pt/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/pt/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/pt/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/pt/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/pt/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/pt/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/pt/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/pt/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/pt/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/pt/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/pt/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/pt/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/pt/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/pt/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/pt/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/pt/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/pt/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/pt/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/pt/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/pt/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/pt/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", - "/pt/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/pt/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/pt/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/pt/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/pt/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/pt/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/pt/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/pt/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", - "/pt/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/pt/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", - "/pt/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/pt/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", - "/pt/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/pt/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/pt/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/pt/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/pt/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/pt/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/pt/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/pt/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/pt/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/pt/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/pt/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/pt/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/pt/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/pt/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/pt/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/pt/enterprise/2.16/user/authenticating-to-github": "/pt/enterprise/2.16/user/github/authenticating-to-github", - "/pt/enterprise/2.16/github/authenticating-to-github": "/pt/enterprise/2.16/user/github/authenticating-to-github", - "/pt/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/pt/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/pt/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/pt/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/pt/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/pt/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/pt/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/pt/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", - "/pt/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/pt/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/pt/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/pt/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", - "/pt/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/pt/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/pt/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/pt/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/pt/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/pt/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/pt/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/pt/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/pt/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/pt/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/pt/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/pt/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/pt/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/pt/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/pt/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/pt/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/pt/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/pt/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/pt/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/pt/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", - "/pt/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/pt/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/pt/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/pt/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/pt/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/pt/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/pt/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/pt/enterprise/2.16/user/authenticating-to-github/signing-commits": "/pt/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/pt/enterprise/2.16/github/authenticating-to-github/signing-commits": "/pt/enterprise/2.16/user/github/authenticating-to-github/signing-commits", - "/pt/enterprise/2.16/user/authenticating-to-github/signing-tags": "/pt/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/pt/enterprise/2.16/github/authenticating-to-github/signing-tags": "/pt/enterprise/2.16/user/github/authenticating-to-github/signing-tags", - "/pt/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/pt/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/pt/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/pt/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", - "/pt/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/pt/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/pt/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/pt/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/pt/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/pt/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", - "/pt/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/pt/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/pt/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/pt/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/pt/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/pt/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/pt/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/pt/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", - "/pt/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/pt/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/pt/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/pt/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/pt/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/pt/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/pt/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/pt/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/pt/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/pt/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/pt/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/pt/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/pt/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/pt/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/pt/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/pt/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/pt/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/pt/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/pt/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/pt/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/pt/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", - "/pt/enterprise/2.16/user/building-a-strong-community/about-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/pt/enterprise/2.16/github/building-a-strong-community/about-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/about-wikis", - "/pt/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/pt/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/pt/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/pt/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/pt/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/pt/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/pt/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/pt/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/pt/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/pt/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/pt/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/pt/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/pt/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/pt/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/pt/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/pt/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", - "/pt/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/pt/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/pt/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/pt/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/pt/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/pt/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/pt/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/pt/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/pt/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/pt/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/pt/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/pt/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", - "/pt/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/pt/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", - "/pt/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/pt/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/pt/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/pt/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/pt/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/pt/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/pt/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/pt/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/pt/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/pt/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/pt/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", - "/pt/enterprise/2.16/user/building-a-strong-community": "/pt/enterprise/2.16/user/github/building-a-strong-community", - "/pt/enterprise/2.16/github/building-a-strong-community": "/pt/enterprise/2.16/user/github/building-a-strong-community", - "/pt/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/pt/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/pt/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/pt/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", - "/pt/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/pt/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/pt/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/pt/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", - "/pt/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/pt/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/pt/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/pt/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/pt/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/pt/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/pt/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/pt/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/pt/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/pt/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/pt/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", - "/pt/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/pt/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/pt/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/pt/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/pt/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/pt/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/pt/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/pt/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/pt/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/pt/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/pt/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/pt/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/pt/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/pt/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/pt/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/pt/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/pt/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/pt/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/pt/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/pt/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/pt/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/pt/enterprise/2.16/user/committing-changes-to-your-project": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project", - "/pt/enterprise/2.16/github/committing-changes-to-your-project": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/pt/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/pt/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/pt/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/pt/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/pt/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/pt/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/pt/enterprise/2.16/user/extending-github/about-webhooks": "/pt/enterprise/2.16/user/github/extending-github/about-webhooks", - "/pt/enterprise/2.16/github/extending-github/about-webhooks": "/pt/enterprise/2.16/user/github/extending-github/about-webhooks", - "/pt/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/pt/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/pt/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/pt/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", - "/pt/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/pt/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/pt/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/pt/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", - "/pt/enterprise/2.16/user/extending-github": "/pt/enterprise/2.16/user/github/extending-github", - "/pt/enterprise/2.16/github/extending-github": "/pt/enterprise/2.16/user/github/extending-github", - "/pt/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/pt/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", - "/pt/enterprise/2.16/user/getting-started-with-github/be-social": "/pt/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/pt/enterprise/2.16/github/getting-started-with-github/be-social": "/pt/enterprise/2.16/user/github/getting-started-with-github/be-social", - "/pt/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/pt/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/pt/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/pt/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", - "/pt/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/pt/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", - "/pt/enterprise/2.16/user/getting-started-with-github/following-people": "/pt/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/pt/enterprise/2.16/github/getting-started-with-github/following-people": "/pt/enterprise/2.16/user/github/getting-started-with-github/following-people", - "/pt/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/pt/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/pt/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/pt/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", - "/pt/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/pt/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/pt/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/pt/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", - "/pt/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/pt/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/pt/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/pt/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", - "/pt/enterprise/2.16/user/getting-started-with-github/github-glossary": "/pt/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/pt/enterprise/2.16/github/getting-started-with-github/github-glossary": "/pt/enterprise/2.16/user/github/getting-started-with-github/github-glossary", - "/pt/enterprise/2.16/user/getting-started-with-github": "/pt/enterprise/2.16/user/github/getting-started-with-github", - "/pt/enterprise/2.16/github/getting-started-with-github": "/pt/enterprise/2.16/user/github/getting-started-with-github", - "/pt/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/pt/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/pt/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/pt/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", - "/pt/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/pt/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", - "/pt/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/pt/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/pt/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/pt/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", - "/pt/enterprise/2.16/user/getting-started-with-github/set-up-git": "/pt/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/pt/enterprise/2.16/github/getting-started-with-github/set-up-git": "/pt/enterprise/2.16/user/github/getting-started-with-github/set-up-git", - "/pt/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/pt/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/pt/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/pt/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/pt/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/pt/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/pt/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/pt/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/pt/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/pt/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", - "/pt/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/pt/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/pt/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/pt/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", - "/pt/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/pt/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/pt/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/pt/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", - "/pt/enterprise/2.16/user/getting-started-with-github/using-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/pt/enterprise/2.16/github/getting-started-with-github/using-github": "/pt/enterprise/2.16/user/github/getting-started-with-github/using-github", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/pt/enterprise/2.16/user/importing-your-projects-to-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github", - "/pt/enterprise/2.16/github/importing-your-projects-to-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/pt/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/pt/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/pt/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/pt/enterprise/2.16/user": "/pt/enterprise/2.16/user/github", - "/pt/enterprise/2.16/github": "/pt/enterprise/2.16/user/github", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/pt/enterprise/2.16/user/managing-files-in-a-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository", - "/pt/enterprise/2.16/github/managing-files-in-a-repository": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/pt/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/pt/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/pt/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/pt/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/pt/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", - "/pt/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/pt/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/pt/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/pt/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/pt/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/pt/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", - "/pt/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/pt/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", - "/pt/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/pt/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/pt/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/pt/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", - "/pt/enterprise/2.16/user/managing-large-files": "/pt/enterprise/2.16/user/github/managing-large-files", - "/pt/enterprise/2.16/github/managing-large-files": "/pt/enterprise/2.16/user/github/managing-large-files", - "/pt/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/pt/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", - "/pt/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/pt/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/pt/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/pt/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/pt/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/pt/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/pt/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/pt/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/pt/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/pt/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/pt/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/pt/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/pt/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/pt/enterprise/2.16/user/managing-large-files/versioning-large-files": "/pt/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/pt/enterprise/2.16/github/managing-large-files/versioning-large-files": "/pt/enterprise/2.16/user/github/managing-large-files/versioning-large-files", - "/pt/enterprise/2.16/user/managing-large-files/working-with-large-files": "/pt/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/pt/enterprise/2.16/github/managing-large-files/working-with-large-files": "/pt/enterprise/2.16/user/github/managing-large-files/working-with-large-files", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", - "/pt/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/pt/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", - "/pt/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/pt/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/pt/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/pt/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/pt/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/pt/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", - "/pt/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/pt/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/pt/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/pt/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", - "/pt/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/pt/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/pt/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/pt/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", - "/pt/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/pt/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", - "/pt/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/pt/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", - "/pt/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/pt/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", - "/pt/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/pt/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/pt/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/pt/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/pt/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/pt/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", - "/pt/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/pt/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/pt/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/pt/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/pt/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/pt/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/pt/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/pt/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/pt/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/pt/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/pt/enterprise/2.16/user/managing-your-work-on-github": "/pt/enterprise/2.16/user/github/managing-your-work-on-github", - "/pt/enterprise/2.16/github/managing-your-work-on-github": "/pt/enterprise/2.16/user/github/managing-your-work-on-github", - "/pt/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/pt/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", - "/pt/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/pt/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/pt/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/pt/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/pt/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/pt/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/pt/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/pt/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", - "/pt/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/pt/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/pt/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/pt/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/pt/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/pt/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/pt/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/pt/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/pt/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/pt/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/pt/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/pt/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/pt/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/pt/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/pt/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/pt/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", - "/pt/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/pt/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/pt/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/pt/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", - "/pt/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/pt/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/pt/enterprise/2.16/user/searching-for-information-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github", - "/pt/enterprise/2.16/github/searching-for-information-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", - "/pt/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/pt/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", - "/pt/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/pt/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", - "/pt/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/pt/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/pt/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/pt/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/pt/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/pt/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/pt/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/pt/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/pt/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/pt/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/pt/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/pt/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/pt/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/pt/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/pt/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/pt/enterprise/2.16/user/using-git/about-git-rebase": "/pt/enterprise/2.16/user/github/using-git/about-git-rebase", - "/pt/enterprise/2.16/github/using-git/about-git-rebase": "/pt/enterprise/2.16/user/github/using-git/about-git-rebase", - "/pt/enterprise/2.16/user/using-git/about-git-subtree-merges": "/pt/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/pt/enterprise/2.16/github/using-git/about-git-subtree-merges": "/pt/enterprise/2.16/user/github/using-git/about-git-subtree-merges", - "/pt/enterprise/2.16/user/using-git/about-remote-repositories": "/pt/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/pt/enterprise/2.16/github/using-git/about-remote-repositories": "/pt/enterprise/2.16/user/github/using-git/about-remote-repositories", - "/pt/enterprise/2.16/user/using-git/adding-a-remote": "/pt/enterprise/2.16/user/github/using-git/adding-a-remote", - "/pt/enterprise/2.16/github/using-git/adding-a-remote": "/pt/enterprise/2.16/user/github/using-git/adding-a-remote", - "/pt/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/pt/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/pt/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/pt/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", - "/pt/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/pt/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/pt/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/pt/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", - "/pt/enterprise/2.16/user/using-git/changing-a-remotes-url": "/pt/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/pt/enterprise/2.16/github/using-git/changing-a-remotes-url": "/pt/enterprise/2.16/user/github/using-git/changing-a-remotes-url", - "/pt/enterprise/2.16/user/using-git/changing-author-info": "/pt/enterprise/2.16/user/github/using-git/changing-author-info", - "/pt/enterprise/2.16/github/using-git/changing-author-info": "/pt/enterprise/2.16/user/github/using-git/changing-author-info", - "/pt/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/pt/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/pt/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/pt/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", - "/pt/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/pt/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/pt/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/pt/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", - "/pt/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/pt/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/pt/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/pt/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", - "/pt/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/pt/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/pt/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/pt/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", - "/pt/enterprise/2.16/user/using-git/git-workflows": "/pt/enterprise/2.16/user/github/using-git/git-workflows", - "/pt/enterprise/2.16/github/using-git/git-workflows": "/pt/enterprise/2.16/user/github/using-git/git-workflows", - "/pt/enterprise/2.16/user/using-git/ignoring-files": "/pt/enterprise/2.16/user/github/using-git/ignoring-files", - "/pt/enterprise/2.16/github/using-git/ignoring-files": "/pt/enterprise/2.16/user/github/using-git/ignoring-files", - "/pt/enterprise/2.16/user/using-git": "/pt/enterprise/2.16/user/github/using-git", - "/pt/enterprise/2.16/github/using-git": "/pt/enterprise/2.16/user/github/using-git", - "/pt/enterprise/2.16/user/using-git/learning-about-git": "/pt/enterprise/2.16/user/github/using-git/learning-about-git", - "/pt/enterprise/2.16/github/using-git/learning-about-git": "/pt/enterprise/2.16/user/github/using-git/learning-about-git", - "/pt/enterprise/2.16/user/using-git/managing-remote-repositories": "/pt/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/pt/enterprise/2.16/github/using-git/managing-remote-repositories": "/pt/enterprise/2.16/user/github/using-git/managing-remote-repositories", - "/pt/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/pt/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/pt/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/pt/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", - "/pt/enterprise/2.16/user/using-git/removing-a-remote": "/pt/enterprise/2.16/user/github/using-git/removing-a-remote", - "/pt/enterprise/2.16/github/using-git/removing-a-remote": "/pt/enterprise/2.16/user/github/using-git/removing-a-remote", - "/pt/enterprise/2.16/user/using-git/renaming-a-remote": "/pt/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/pt/enterprise/2.16/github/using-git/renaming-a-remote": "/pt/enterprise/2.16/user/github/using-git/renaming-a-remote", - "/pt/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/pt/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/pt/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/pt/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/pt/enterprise/2.16/user/using-git/setting-your-username-in-git": "/pt/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/pt/enterprise/2.16/github/using-git/setting-your-username-in-git": "/pt/enterprise/2.16/user/github/using-git/setting-your-username-in-git", - "/pt/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/pt/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/pt/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/pt/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/pt/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/pt/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/pt/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/pt/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/pt/enterprise/2.16/user/using-git/using-advanced-git-commands": "/pt/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/pt/enterprise/2.16/github/using-git/using-advanced-git-commands": "/pt/enterprise/2.16/user/github/using-git/using-advanced-git-commands", - "/pt/enterprise/2.16/user/using-git/using-common-git-commands": "/pt/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/pt/enterprise/2.16/github/using-git/using-common-git-commands": "/pt/enterprise/2.16/user/github/using-git/using-common-git-commands", - "/pt/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/pt/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/pt/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/pt/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", - "/pt/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/pt/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/pt/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/pt/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", - "/pt/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/pt/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/pt/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/pt/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/pt/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/pt/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/pt/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/pt/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/pt/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/pt/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/pt/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", - "/pt/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/pt/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/pt/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/pt/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/pt/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/pt/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", - "/pt/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/pt/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/pt/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/pt/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", - "/pt/enterprise/2.16/user/working-with-github-pages": "/pt/enterprise/2.16/user/github/working-with-github-pages", - "/pt/enterprise/2.16/github/working-with-github-pages": "/pt/enterprise/2.16/user/github/working-with-github-pages", - "/pt/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/pt/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/pt/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/pt/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/pt/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/pt/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/pt/enterprise/2.16/user/writing-on-github/about-saved-replies": "/pt/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/pt/enterprise/2.16/github/writing-on-github/about-saved-replies": "/pt/enterprise/2.16/user/github/writing-on-github/about-saved-replies", - "/pt/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/pt/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/pt/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/pt/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/pt/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/pt/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/pt/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/pt/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", - "/pt/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/pt/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/pt/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/pt/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/pt/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/pt/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/pt/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/pt/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", - "/pt/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/pt/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/pt/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/pt/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/pt/enterprise/2.16/user/writing-on-github/creating-gists": "/pt/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/pt/enterprise/2.16/github/writing-on-github/creating-gists": "/pt/enterprise/2.16/user/github/writing-on-github/creating-gists", - "/pt/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/pt/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/pt/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/pt/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", - "/pt/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/pt/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/pt/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/pt/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", - "/pt/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/pt/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/pt/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/pt/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/pt/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/pt/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/pt/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/pt/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", - "/pt/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/pt/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/pt/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/pt/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/pt/enterprise/2.16/user/writing-on-github": "/pt/enterprise/2.16/user/github/writing-on-github", - "/pt/enterprise/2.16/github/writing-on-github": "/pt/enterprise/2.16/user/github/writing-on-github", - "/pt/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/pt/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/pt/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/pt/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", - "/pt/enterprise/2.16/user/writing-on-github/using-saved-replies": "/pt/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/pt/enterprise/2.16/github/writing-on-github/using-saved-replies": "/pt/enterprise/2.16/user/github/writing-on-github/using-saved-replies", - "/pt/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/pt/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/pt/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/pt/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", - "/pt/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/pt/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/pt/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/pt/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", - "/pt/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/pt/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", - "/pt/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/pt/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/pt/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/pt/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/pt/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/pt/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/pt/enterprise/2.16/insights": "/pt/enterprise/2.16/user/insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/pt/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/pt/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/cn/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/cn/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/cn/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/cn/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/cn/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/cn/enterprise/2.17/admin/articles/using-github-task-runner", - "/cn/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/cn/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/cn/enterprise/2.17/admin/guides/clustering/about-clustering": "/cn/enterprise/2.17/admin/clustering/about-clustering", - "/cn/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/cn/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/cn/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/cn/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/cn/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/cn/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/cn/enterprise/2.17/admin/guides/clustering": "/cn/enterprise/2.17/admin/clustering", - "/cn/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/cn/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/cn/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/cn/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/cn/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/cn/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/cn/enterprise/2.17/admin/guides/clustering/overview": "/cn/enterprise/2.17/admin/clustering/overview", - "/cn/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/cn/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/cn/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/cn/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/cn/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/cn/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/cn/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/cn/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/cn/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/cn/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/cn/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/cn/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/cn/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/cn/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/cn/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/cn/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/cn/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/cn/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/cn/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/cn/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/cn/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/cn/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/cn/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/cn/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/cn/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/cn/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/cn/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/cn/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/cn/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/cn/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/cn/enterprise/2.17/admin/guides/developer-workflow": "/cn/enterprise/2.17/admin/developer-workflow", - "/cn/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/cn/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/cn/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/cn/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/cn/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/cn/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/cn/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/cn/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/cn/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/cn/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/cn/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/cn/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/cn/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/cn/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/cn/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/cn/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/cn/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/cn/enterprise/2.17/admin/guides/enterprise-support": "/cn/enterprise/2.17/admin/enterprise-support", - "/cn/enterprise/2.17/admin/guides/enterprise-support/overview": "/cn/enterprise/2.17/admin/enterprise-support/overview", - "/cn/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/cn/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/cn/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/cn/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/cn/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/cn/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/cn/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/cn/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/cn/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/cn/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/cn/enterprise/2.17/admin/guides": "/cn/enterprise/2.17/admin", - "/cn/enterprise/2.17/admin/guides/installation/about-geo-replication": "/cn/enterprise/2.17/admin/installation/about-geo-replication", - "/cn/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/cn/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/cn/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/cn/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/cn/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/cn/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/cn/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/cn/enterprise/2.17/admin/installation/accessing-the-management-console", - "/cn/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/cn/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/cn/enterprise/2.17/admin/guides/installation/activity-dashboard": "/cn/enterprise/2.17/admin/installation/activity-dashboard", - "/cn/enterprise/2.17/admin/guides/installation/audit-logging": "/cn/enterprise/2.17/admin/installation/audit-logging", - "/cn/enterprise/2.17/admin/guides/installation/audited-actions": "/cn/enterprise/2.17/admin/installation/audited-actions", - "/cn/enterprise/2.17/admin/guides/installation/command-line-utilities": "/cn/enterprise/2.17/admin/installation/command-line-utilities", - "/cn/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/cn/enterprise/2.17/admin/installation/configuring-a-hostname", - "/cn/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/cn/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/cn/enterprise/2.17/admin/guides/installation/configuring-applications": "/cn/enterprise/2.17/admin/installation/configuring-applications", - "/cn/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/cn/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/cn/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/cn/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/cn/enterprise/2.17/admin/guides/installation/configuring-collectd": "/cn/enterprise/2.17/admin/installation/configuring-collectd", - "/cn/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/cn/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/cn/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/cn/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/cn/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/cn/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/cn/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/cn/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/cn/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/cn/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/cn/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/cn/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/cn/enterprise/2.17/admin/installation/configuring-rate-limits", - "/cn/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/cn/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/cn/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/cn/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/cn/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/cn/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/cn/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/cn/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/cn/enterprise/2.17/admin/guides/installation/configuring-tls": "/cn/enterprise/2.17/admin/installation/configuring-tls", - "/cn/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/cn/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/cn/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/cn/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/cn/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/cn/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/cn/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/cn/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/cn/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/cn/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/cn/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/cn/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/cn/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/cn/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/cn/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/cn/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/cn/enterprise/2.17/admin/installation/enabling-private-mode", - "/cn/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/cn/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/cn/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/cn/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/cn/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/cn/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/cn/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/cn/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/cn/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/cn/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/cn/enterprise/2.17/admin/guides/installation": "/cn/enterprise/2.17/admin/installation", - "/cn/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/cn/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/cn/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/cn/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/cn/enterprise/2.17/admin/guides/installation/log-forwarding": "/cn/enterprise/2.17/admin/installation/log-forwarding", - "/cn/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/cn/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/cn/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/cn/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/cn/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/cn/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/cn/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/cn/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/cn/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/cn/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/cn/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/cn/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/cn/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/cn/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/cn/enterprise/2.17/admin/guides/installation/network-ports": "/cn/enterprise/2.17/admin/installation/network-ports", - "/cn/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/cn/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/cn/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/cn/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/cn/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/cn/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/cn/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/cn/enterprise/2.17/admin/installation/searching-the-audit-log", - "/cn/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/cn/enterprise/2.17/admin/installation/setting-git-push-limits", - "/cn/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/cn/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/cn/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/cn/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/cn/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/cn/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/cn/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/cn/enterprise/2.17/admin/installation/site-admin-dashboard", - "/cn/enterprise/2.17/admin/guides/installation/system-overview": "/cn/enterprise/2.17/admin/installation/system-overview", - "/cn/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/cn/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/cn/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/cn/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/cn/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/cn/enterprise/2.17/admin/installation/upgrade-requirements", - "/cn/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/cn/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/cn/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/cn/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/cn/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/cn/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/cn/enterprise/2.17/admin/installation/viewing-push-logs", - "/cn/enterprise/2.17/admin/guides/migrations/about-migrations": "/cn/enterprise/2.17/admin/migrations/about-migrations", - "/cn/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/cn/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/cn/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/cn/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/cn/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/cn/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/cn/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/cn/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/cn/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/cn/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/cn/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/cn/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/cn/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/cn/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/cn/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/migrations": "/cn/enterprise/2.17/admin/migrations", - "/cn/enterprise/2.17/admin/guides/migrations/overview": "/cn/enterprise/2.17/admin/migrations/overview", - "/cn/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/cn/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/cn/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/cn/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/cn/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/cn/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/cn/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/cn/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/cn/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/cn/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/cn/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/cn/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/cn/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/cn/enterprise/2.17/admin/user-management/about-global-webhooks", - "/cn/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/cn/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/cn/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/cn/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/cn/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/cn/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/cn/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/cn/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/cn/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/cn/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/cn/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/cn/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/cn/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/cn/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/cn/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/cn/enterprise/2.17/admin/user-management/basic-account-settings", - "/cn/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/cn/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/cn/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/cn/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/cn/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/cn/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/cn/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/cn/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/cn/enterprise/2.17/admin/guides/user-management/creating-organizations": "/cn/enterprise/2.17/admin/user-management/creating-organizations", - "/cn/enterprise/2.17/admin/guides/user-management/creating-teams": "/cn/enterprise/2.17/admin/user-management/creating-teams", - "/cn/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/cn/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/cn/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/cn/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/cn/enterprise/2.17/admin/guides/user-management": "/cn/enterprise/2.17/admin/user-management", - "/cn/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/cn/enterprise/2.17/admin/user-management/managing-dormant-users", - "/cn/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/cn/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/cn/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/cn/enterprise/2.17/admin/user-management/organizations-and-teams", - "/cn/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/cn/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/cn/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/cn/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/cn/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/cn/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/cn/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/cn/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/cn/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/cn/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/cn/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/cn/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/cn/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/cn/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/cn/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/cn/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/cn/enterprise/2.17/admin/guides/user-management/repositories": "/cn/enterprise/2.17/admin/user-management/repositories", - "/cn/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/cn/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/cn/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/cn/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/cn/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/cn/enterprise/2.17/admin/guides/user-management/user-security": "/cn/enterprise/2.17/admin/user-management/user-security", - "/cn/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/cn/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/cn/enterprise/2.17/admin/guides/user-management/using-cas": "/cn/enterprise/2.17/admin/user-management/using-cas", - "/cn/enterprise/2.17/admin/guides/user-management/using-ldap": "/cn/enterprise/2.17/admin/user-management/using-ldap", - "/cn/enterprise/2.17/admin/guides/user-management/using-saml": "/cn/enterprise/2.17/admin/user-management/using-saml", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/cn/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/cn/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/cn/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/cn/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/cn/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/cn/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/cn/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/cn/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/cn/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/cn/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/cn/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/cn/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/cn/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/cn/enterprise/2.17/user/administering-a-repository/about-releases": "/cn/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/cn/enterprise/2.17/github/administering-a-repository/about-releases": "/cn/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/cn/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/cn/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/cn/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/cn/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/cn/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/cn/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/cn/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/cn/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/cn/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/cn/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/cn/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/cn/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/cn/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/cn/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/cn/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/cn/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/cn/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/cn/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/cn/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/cn/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/cn/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/cn/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/cn/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/cn/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/cn/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/cn/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/cn/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/cn/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository", - "/cn/enterprise/2.17/user/administering-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository", - "/cn/enterprise/2.17/github/administering-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/cn/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/cn/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/cn/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/cn/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/cn/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/cn/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/cn/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/cn/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/cn/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/cn/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/cn/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/cn/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/cn/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/cn/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/cn/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/cn/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/cn/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/cn/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/cn/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/cn/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/cn/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/cn/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/cn/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/cn/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/cn/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/cn/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/cn/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/cn/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/cn/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/cn/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/cn/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/cn/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/cn/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/cn/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/cn/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/cn/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/cn/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/cn/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/cn/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/cn/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/cn/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/cn/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/cn/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/cn/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/cn/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/cn/enterprise/2.17/user/authenticating-to-github/about-ssh": "/cn/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/cn/enterprise/2.17/github/authenticating-to-github/about-ssh": "/cn/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/cn/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/cn/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/cn/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/cn/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/cn/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/cn/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/cn/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/cn/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/cn/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/cn/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/cn/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/cn/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/cn/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/cn/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/cn/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/cn/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/cn/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/cn/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/cn/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/cn/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/cn/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/cn/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/cn/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/cn/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/cn/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/cn/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/cn/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/cn/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/cn/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/cn/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/cn/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/cn/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/cn/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/cn/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/cn/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/cn/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/cn/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/cn/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/cn/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/cn/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/cn/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/cn/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/cn/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/cn/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/cn/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/cn/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/cn/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/cn/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/cn/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/cn/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/cn/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/cn/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/cn/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/cn/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/cn/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/cn/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/cn/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/cn/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/cn/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/cn/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/cn/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/cn/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/cn/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/cn/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/cn/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/cn/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/cn/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/cn/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/cn/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/cn/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/cn/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/cn/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/cn/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/cn/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/cn/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/cn/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/cn/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/cn/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/cn/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/cn/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/cn/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/cn/enterprise/2.17/user/authenticating-to-github": "/cn/enterprise/2.17/user/github/authenticating-to-github", - "/cn/enterprise/2.17/github/authenticating-to-github": "/cn/enterprise/2.17/user/github/authenticating-to-github", - "/cn/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/cn/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/cn/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/cn/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/cn/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/cn/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/cn/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/cn/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/cn/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/cn/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/cn/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/cn/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/cn/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/cn/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/cn/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/cn/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/cn/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/cn/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/cn/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/cn/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/cn/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/cn/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/cn/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/cn/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/cn/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/cn/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/cn/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/cn/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/cn/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/cn/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/cn/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/cn/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/cn/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/cn/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/cn/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/cn/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/cn/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/cn/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/cn/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/cn/enterprise/2.17/user/authenticating-to-github/signing-commits": "/cn/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/cn/enterprise/2.17/github/authenticating-to-github/signing-commits": "/cn/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/cn/enterprise/2.17/user/authenticating-to-github/signing-tags": "/cn/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/cn/enterprise/2.17/github/authenticating-to-github/signing-tags": "/cn/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/cn/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/cn/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/cn/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/cn/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/cn/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/cn/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/cn/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/cn/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/cn/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/cn/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/cn/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/cn/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/cn/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/cn/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/cn/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/cn/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/cn/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/cn/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/cn/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/cn/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/cn/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/cn/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/cn/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/cn/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/cn/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/cn/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/cn/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/cn/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/cn/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/cn/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/cn/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/cn/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/cn/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/cn/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/cn/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/cn/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/cn/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/cn/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/cn/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/cn/enterprise/2.17/user/building-a-strong-community/about-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/cn/enterprise/2.17/github/building-a-strong-community/about-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/cn/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/cn/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/cn/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/cn/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/cn/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/cn/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/cn/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/cn/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/cn/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/cn/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/cn/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/cn/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/cn/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/cn/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/cn/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/cn/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/cn/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/cn/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/cn/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/cn/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/cn/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/cn/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/cn/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/cn/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/cn/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/cn/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/cn/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/cn/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/cn/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/cn/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/cn/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/cn/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/cn/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/cn/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/cn/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/cn/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/cn/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/cn/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/cn/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/cn/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/cn/enterprise/2.17/user/building-a-strong-community": "/cn/enterprise/2.17/user/github/building-a-strong-community", - "/cn/enterprise/2.17/github/building-a-strong-community": "/cn/enterprise/2.17/user/github/building-a-strong-community", - "/cn/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/cn/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/cn/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/cn/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/cn/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/cn/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/cn/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/cn/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/cn/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/cn/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/cn/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/cn/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/cn/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/cn/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/cn/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/cn/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/cn/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/cn/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/cn/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/cn/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/cn/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/cn/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/cn/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/cn/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/cn/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/cn/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/cn/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/cn/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/cn/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/cn/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/cn/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/cn/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/cn/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/cn/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/cn/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/cn/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/cn/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/cn/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/cn/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/cn/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/cn/enterprise/2.17/user/committing-changes-to-your-project": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project", - "/cn/enterprise/2.17/github/committing-changes-to-your-project": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/cn/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/cn/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/cn/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/cn/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/cn/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/cn/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/cn/enterprise/2.17/user/extending-github/about-webhooks": "/cn/enterprise/2.17/user/github/extending-github/about-webhooks", - "/cn/enterprise/2.17/github/extending-github/about-webhooks": "/cn/enterprise/2.17/user/github/extending-github/about-webhooks", - "/cn/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/cn/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/cn/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/cn/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/cn/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/cn/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/cn/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/cn/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/cn/enterprise/2.17/user/extending-github": "/cn/enterprise/2.17/user/github/extending-github", - "/cn/enterprise/2.17/github/extending-github": "/cn/enterprise/2.17/user/github/extending-github", - "/cn/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/cn/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/cn/enterprise/2.17/user/getting-started-with-github/be-social": "/cn/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/cn/enterprise/2.17/github/getting-started-with-github/be-social": "/cn/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/cn/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/cn/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/cn/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/cn/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/cn/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/cn/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/cn/enterprise/2.17/user/getting-started-with-github/following-people": "/cn/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/cn/enterprise/2.17/github/getting-started-with-github/following-people": "/cn/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/cn/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/cn/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/cn/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/cn/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/cn/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/cn/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/cn/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/cn/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/cn/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/cn/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/cn/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/cn/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/cn/enterprise/2.17/user/getting-started-with-github/github-desktop": "/cn/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/cn/enterprise/2.17/github/getting-started-with-github/github-desktop": "/cn/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/cn/enterprise/2.17/user/getting-started-with-github/github-glossary": "/cn/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/cn/enterprise/2.17/github/getting-started-with-github/github-glossary": "/cn/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/cn/enterprise/2.17/user/getting-started-with-github/githubs-products": "/cn/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/cn/enterprise/2.17/github/getting-started-with-github/githubs-products": "/cn/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/cn/enterprise/2.17/user/getting-started-with-github": "/cn/enterprise/2.17/user/github/getting-started-with-github", - "/cn/enterprise/2.17/github/getting-started-with-github": "/cn/enterprise/2.17/user/github/getting-started-with-github", - "/cn/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/cn/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/cn/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/cn/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/cn/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/cn/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/cn/enterprise/2.17/user/getting-started-with-github/quickstart": "/cn/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/cn/enterprise/2.17/github/getting-started-with-github/quickstart": "/cn/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/cn/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/cn/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/cn/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/cn/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/cn/enterprise/2.17/user/getting-started-with-github/set-up-git": "/cn/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/cn/enterprise/2.17/github/getting-started-with-github/set-up-git": "/cn/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/cn/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/cn/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/cn/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/cn/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/cn/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/cn/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/cn/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/cn/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/cn/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/cn/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/cn/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/cn/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/cn/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/cn/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/cn/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/cn/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/cn/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/cn/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/cn/enterprise/2.17/user/getting-started-with-github/using-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/cn/enterprise/2.17/github/getting-started-with-github/using-github": "/cn/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/cn/enterprise/2.17/user/importing-your-projects-to-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github", - "/cn/enterprise/2.17/github/importing-your-projects-to-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/cn/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/cn/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/cn/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/cn/enterprise/2.17/user": "/cn/enterprise/2.17/user/github", - "/cn/enterprise/2.17/github": "/cn/enterprise/2.17/user/github", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/cn/enterprise/2.17/user/managing-files-in-a-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository", - "/cn/enterprise/2.17/github/managing-files-in-a-repository": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/cn/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/cn/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/cn/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/cn/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/cn/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/cn/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/cn/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/cn/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/cn/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/cn/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/cn/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/cn/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/cn/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/cn/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/cn/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/cn/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/cn/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/cn/enterprise/2.17/user/managing-large-files": "/cn/enterprise/2.17/user/github/managing-large-files", - "/cn/enterprise/2.17/github/managing-large-files": "/cn/enterprise/2.17/user/github/managing-large-files", - "/cn/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/cn/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/cn/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/cn/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/cn/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/cn/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/cn/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/cn/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/cn/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/cn/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/cn/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/cn/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/cn/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/cn/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/cn/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/cn/enterprise/2.17/user/managing-large-files/versioning-large-files": "/cn/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/cn/enterprise/2.17/github/managing-large-files/versioning-large-files": "/cn/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/cn/enterprise/2.17/user/managing-large-files/working-with-large-files": "/cn/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/cn/enterprise/2.17/github/managing-large-files/working-with-large-files": "/cn/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/cn/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/cn/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/cn/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/cn/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/cn/enterprise/2.17/user/managing-security-vulnerabilities": "/cn/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/cn/enterprise/2.17/github/managing-security-vulnerabilities": "/cn/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/cn/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/cn/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/cn/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/cn/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/cn/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/cn/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/cn/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/cn/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/cn/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/cn/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/cn/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/cn/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/cn/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/cn/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/cn/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/cn/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/cn/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/cn/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/cn/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/cn/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/cn/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/cn/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/cn/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/cn/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/cn/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/cn/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/cn/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/cn/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/cn/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/cn/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/cn/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/cn/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/cn/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/cn/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/cn/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/cn/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/cn/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/cn/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/cn/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/cn/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/cn/enterprise/2.17/user/managing-your-work-on-github": "/cn/enterprise/2.17/user/github/managing-your-work-on-github", - "/cn/enterprise/2.17/github/managing-your-work-on-github": "/cn/enterprise/2.17/user/github/managing-your-work-on-github", - "/cn/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/cn/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/cn/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/cn/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/cn/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/cn/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/cn/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/cn/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/cn/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/cn/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/cn/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/cn/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/cn/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/cn/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/cn/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/cn/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/cn/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/cn/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/cn/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/cn/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/cn/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/cn/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/cn/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/cn/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/cn/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/cn/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/cn/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/cn/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/cn/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/cn/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/cn/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/cn/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/cn/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/cn/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/cn/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/cn/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/cn/enterprise/2.17/user/searching-for-information-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github", - "/cn/enterprise/2.17/github/searching-for-information-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/cn/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/cn/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/cn/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/cn/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/cn/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/cn/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/cn/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/cn/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/cn/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/cn/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/cn/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/cn/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/cn/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/cn/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/cn/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/cn/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/cn/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/cn/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/cn/enterprise/2.17/user/using-git/about-git-rebase": "/cn/enterprise/2.17/user/github/using-git/about-git-rebase", - "/cn/enterprise/2.17/github/using-git/about-git-rebase": "/cn/enterprise/2.17/user/github/using-git/about-git-rebase", - "/cn/enterprise/2.17/user/using-git/about-git-subtree-merges": "/cn/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/cn/enterprise/2.17/github/using-git/about-git-subtree-merges": "/cn/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/cn/enterprise/2.17/user/using-git/about-remote-repositories": "/cn/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/cn/enterprise/2.17/github/using-git/about-remote-repositories": "/cn/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/cn/enterprise/2.17/user/using-git/adding-a-remote": "/cn/enterprise/2.17/user/github/using-git/adding-a-remote", - "/cn/enterprise/2.17/github/using-git/adding-a-remote": "/cn/enterprise/2.17/user/github/using-git/adding-a-remote", - "/cn/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/cn/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/cn/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/cn/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/cn/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/cn/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/cn/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/cn/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/cn/enterprise/2.17/user/using-git/changing-a-remotes-url": "/cn/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/cn/enterprise/2.17/github/using-git/changing-a-remotes-url": "/cn/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/cn/enterprise/2.17/user/using-git/changing-author-info": "/cn/enterprise/2.17/user/github/using-git/changing-author-info", - "/cn/enterprise/2.17/github/using-git/changing-author-info": "/cn/enterprise/2.17/user/github/using-git/changing-author-info", - "/cn/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/cn/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/cn/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/cn/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/cn/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/cn/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/cn/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/cn/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/cn/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/cn/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/cn/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/cn/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/cn/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/cn/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/cn/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/cn/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/cn/enterprise/2.17/user/using-git/git-workflows": "/cn/enterprise/2.17/user/github/using-git/git-workflows", - "/cn/enterprise/2.17/github/using-git/git-workflows": "/cn/enterprise/2.17/user/github/using-git/git-workflows", - "/cn/enterprise/2.17/user/using-git/ignoring-files": "/cn/enterprise/2.17/user/github/using-git/ignoring-files", - "/cn/enterprise/2.17/github/using-git/ignoring-files": "/cn/enterprise/2.17/user/github/using-git/ignoring-files", - "/cn/enterprise/2.17/user/using-git": "/cn/enterprise/2.17/user/github/using-git", - "/cn/enterprise/2.17/github/using-git": "/cn/enterprise/2.17/user/github/using-git", - "/cn/enterprise/2.17/user/using-git/learning-about-git": "/cn/enterprise/2.17/user/github/using-git/learning-about-git", - "/cn/enterprise/2.17/github/using-git/learning-about-git": "/cn/enterprise/2.17/user/github/using-git/learning-about-git", - "/cn/enterprise/2.17/user/using-git/managing-remote-repositories": "/cn/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/cn/enterprise/2.17/github/using-git/managing-remote-repositories": "/cn/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/cn/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/cn/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/cn/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/cn/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/cn/enterprise/2.17/user/using-git/removing-a-remote": "/cn/enterprise/2.17/user/github/using-git/removing-a-remote", - "/cn/enterprise/2.17/github/using-git/removing-a-remote": "/cn/enterprise/2.17/user/github/using-git/removing-a-remote", - "/cn/enterprise/2.17/user/using-git/renaming-a-remote": "/cn/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/cn/enterprise/2.17/github/using-git/renaming-a-remote": "/cn/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/cn/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/cn/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/cn/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/cn/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/cn/enterprise/2.17/user/using-git/setting-your-username-in-git": "/cn/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/cn/enterprise/2.17/github/using-git/setting-your-username-in-git": "/cn/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/cn/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/cn/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/cn/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/cn/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/cn/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/cn/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/cn/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/cn/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/cn/enterprise/2.17/user/using-git/using-advanced-git-commands": "/cn/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/cn/enterprise/2.17/github/using-git/using-advanced-git-commands": "/cn/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/cn/enterprise/2.17/user/using-git/using-common-git-commands": "/cn/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/cn/enterprise/2.17/github/using-git/using-common-git-commands": "/cn/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/cn/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/cn/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/cn/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/cn/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/cn/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/cn/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/cn/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/cn/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/cn/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/cn/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/cn/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/cn/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/cn/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/cn/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/cn/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/cn/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/cn/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/cn/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/cn/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/cn/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/cn/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/cn/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/cn/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/cn/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/cn/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/cn/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/cn/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/cn/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/cn/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/cn/enterprise/2.17/user/working-with-github-pages": "/cn/enterprise/2.17/user/github/working-with-github-pages", - "/cn/enterprise/2.17/github/working-with-github-pages": "/cn/enterprise/2.17/user/github/working-with-github-pages", - "/cn/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/cn/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/cn/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/cn/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/cn/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/cn/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/cn/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/cn/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/cn/enterprise/2.17/user/writing-on-github/about-saved-replies": "/cn/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/cn/enterprise/2.17/github/writing-on-github/about-saved-replies": "/cn/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/cn/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/cn/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/cn/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/cn/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/cn/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/cn/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/cn/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/cn/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/cn/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/cn/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/cn/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/cn/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/cn/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/cn/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/cn/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/cn/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/cn/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/cn/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/cn/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/cn/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/cn/enterprise/2.17/user/writing-on-github/creating-gists": "/cn/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/cn/enterprise/2.17/github/writing-on-github/creating-gists": "/cn/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/cn/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/cn/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/cn/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/cn/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/cn/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/cn/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/cn/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/cn/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/cn/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/cn/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/cn/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/cn/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/cn/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/cn/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/cn/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/cn/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/cn/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/cn/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/cn/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/cn/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/cn/enterprise/2.17/user/writing-on-github": "/cn/enterprise/2.17/user/github/writing-on-github", - "/cn/enterprise/2.17/github/writing-on-github": "/cn/enterprise/2.17/user/github/writing-on-github", - "/cn/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/cn/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/cn/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/cn/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/cn/enterprise/2.17/user/writing-on-github/using-saved-replies": "/cn/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/cn/enterprise/2.17/github/writing-on-github/using-saved-replies": "/cn/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/cn/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/cn/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/cn/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/cn/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/cn/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/cn/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/cn/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/cn/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/cn/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/cn/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/2.17/graphql/guides": "/cn/enterprise/2.17/user/graphql/guides", - "/cn/enterprise/2.17/graphql/guides/introduction-to-graphql": "/cn/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/cn/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/cn/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/2.17/graphql/guides/using-global-node-ids": "/cn/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/cn/enterprise/2.17/graphql/guides/using-the-explorer": "/cn/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/cn/enterprise/2.17/graphql": "/cn/enterprise/2.17/user/graphql", - "/cn/enterprise/2.17/graphql/overview/about-the-graphql-api": "/cn/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/cn/enterprise/2.17/graphql/overview/breaking-changes": "/cn/enterprise/2.17/user/graphql/overview/breaking-changes", - "/cn/enterprise/2.17/graphql/overview/changelog": "/cn/enterprise/2.17/user/graphql/overview/changelog", - "/cn/enterprise/2.17/graphql/overview/explorer": "/cn/enterprise/2.17/user/graphql/overview/explorer", - "/cn/enterprise/2.17/graphql/overview": "/cn/enterprise/2.17/user/graphql/overview", - "/cn/enterprise/2.17/graphql/overview/resource-limitations": "/cn/enterprise/2.17/user/graphql/overview/resource-limitations", - "/cn/enterprise/2.17/graphql/overview/schema-previews": "/cn/enterprise/2.17/user/graphql/overview/schema-previews", - "/cn/enterprise/2.17/graphql/reference/enums": "/cn/enterprise/2.17/user/graphql/reference/enums", - "/cn/enterprise/2.17/graphql/reference": "/cn/enterprise/2.17/user/graphql/reference", - "/cn/enterprise/2.17/graphql/reference/input-objects": "/cn/enterprise/2.17/user/graphql/reference/input-objects", - "/cn/enterprise/2.17/graphql/reference/interfaces": "/cn/enterprise/2.17/user/graphql/reference/interfaces", - "/cn/enterprise/2.17/graphql/reference/mutations": "/cn/enterprise/2.17/user/graphql/reference/mutations", - "/cn/enterprise/2.17/graphql/reference/objects": "/cn/enterprise/2.17/user/graphql/reference/objects", - "/cn/enterprise/2.17/graphql/reference/queries": "/cn/enterprise/2.17/user/graphql/reference/queries", - "/cn/enterprise/2.17/graphql/reference/scalars": "/cn/enterprise/2.17/user/graphql/reference/scalars", - "/cn/enterprise/2.17/graphql/reference/unions": "/cn/enterprise/2.17/user/graphql/reference/unions", - "/cn/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/cn/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/cn/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/cn/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/cn/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/cn/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/cn/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/cn/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/cn/enterprise/2.17/insights": "/cn/enterprise/2.17/user/insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/cn/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/cn/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/cn/enterprise/2.17/rest": "/cn/enterprise/2.17/user/rest", - "/cn/enterprise/2.17/rest/reference/actions": "/cn/enterprise/2.17/user/rest/reference/actions", - "/cn/enterprise/2.17/rest/reference/activity": "/cn/enterprise/2.17/user/rest/reference/activity", - "/cn/enterprise/2.17/rest/reference/apps": "/cn/enterprise/2.17/user/rest/reference/apps", - "/cn/enterprise/2.17/rest/reference/checks": "/cn/enterprise/2.17/user/rest/reference/checks", - "/cn/enterprise/2.17/rest/reference/codes-of-conduct": "/cn/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/cn/enterprise/2.17/rest/reference/emojis": "/cn/enterprise/2.17/user/rest/reference/emojis", - "/cn/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/cn/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/cn/enterprise/2.17/rest/reference/enterprise-admin": "/cn/enterprise/2.17/user/rest/reference/enterprise-admin", - "/cn/enterprise/2.17/rest/reference/gists": "/cn/enterprise/2.17/user/rest/reference/gists", - "/cn/enterprise/2.17/rest/reference/git": "/cn/enterprise/2.17/user/rest/reference/git", - "/cn/enterprise/2.17/rest/reference/gitignore": "/cn/enterprise/2.17/user/rest/reference/gitignore", - "/cn/enterprise/2.17/rest/reference": "/cn/enterprise/2.17/user/rest/reference", - "/cn/enterprise/2.17/rest/reference/interactions": "/cn/enterprise/2.17/user/rest/reference/interactions", - "/cn/enterprise/2.17/rest/reference/issues": "/cn/enterprise/2.17/user/rest/reference/issues", - "/cn/enterprise/2.17/rest/reference/licenses": "/cn/enterprise/2.17/user/rest/reference/licenses", - "/cn/enterprise/2.17/rest/reference/markdown": "/cn/enterprise/2.17/user/rest/reference/markdown", - "/cn/enterprise/2.17/rest/reference/meta": "/cn/enterprise/2.17/user/rest/reference/meta", - "/cn/enterprise/2.17/rest/reference/migrations": "/cn/enterprise/2.17/user/rest/reference/migrations", - "/cn/enterprise/2.17/rest/reference/oauth-authorizations": "/cn/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/cn/enterprise/2.17/rest/reference/orgs": "/cn/enterprise/2.17/user/rest/reference/orgs", - "/cn/enterprise/2.17/rest/reference/projects": "/cn/enterprise/2.17/user/rest/reference/projects", - "/cn/enterprise/2.17/rest/reference/pulls": "/cn/enterprise/2.17/user/rest/reference/pulls", - "/cn/enterprise/2.17/rest/reference/rate-limit": "/cn/enterprise/2.17/user/rest/reference/rate-limit", - "/cn/enterprise/2.17/rest/reference/reactions": "/cn/enterprise/2.17/user/rest/reference/reactions", - "/cn/enterprise/2.17/rest/reference/repos": "/cn/enterprise/2.17/user/rest/reference/repos", - "/cn/enterprise/2.17/rest/reference/scim": "/cn/enterprise/2.17/user/rest/reference/scim", - "/cn/enterprise/2.17/rest/reference/search": "/cn/enterprise/2.17/user/rest/reference/search", - "/cn/enterprise/2.17/rest/reference/teams": "/cn/enterprise/2.17/user/rest/reference/teams", - "/cn/enterprise/2.17/rest/reference/users": "/cn/enterprise/2.17/user/rest/reference/users", - "/en/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/en/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/en/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/en/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/en/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.17/admin/articles/using-github-task-runner", - "/enterprise/2.17/admin/articles/using-github-task-runner": "/en/enterprise/2.17/admin/articles/using-github-task-runner", - "/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/en/enterprise/2.17/admin/articles/using-github-task-runner", - "/en/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/enterprise/2.17/admin/clustering/about-cluster-nodes": "/en/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/en/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/en/enterprise/2.17/admin/guides/clustering/about-clustering": "/en/enterprise/2.17/admin/clustering/about-clustering", - "/enterprise/2.17/admin/clustering/about-clustering": "/en/enterprise/2.17/admin/clustering/about-clustering", - "/enterprise/2.17/admin/guides/clustering/about-clustering": "/en/enterprise/2.17/admin/clustering/about-clustering", - "/en/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/en/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/enterprise/2.17/admin/clustering/cluster-network-configuration": "/en/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/en/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/en/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/en/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/en/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.17/admin/clustering/evacuating-a-cluster-node": "/en/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/en/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/en/enterprise/2.17/admin/guides/clustering": "/en/enterprise/2.17/admin/clustering", - "/enterprise/2.17/admin/clustering": "/en/enterprise/2.17/admin/clustering", - "/enterprise/2.17/admin/guides/clustering": "/en/enterprise/2.17/admin/clustering", - "/en/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/enterprise/2.17/admin/clustering/initializing-the-cluster": "/en/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/en/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/en/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/en/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/en/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.17/admin/clustering/monitoring-cluster-nodes": "/en/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/en/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/en/enterprise/2.17/admin/guides/clustering/overview": "/en/enterprise/2.17/admin/clustering/overview", - "/enterprise/2.17/admin/clustering/overview": "/en/enterprise/2.17/admin/clustering/overview", - "/enterprise/2.17/admin/guides/clustering/overview": "/en/enterprise/2.17/admin/clustering/overview", - "/en/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.17/admin/clustering/replacing-a-cluster-node": "/en/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/en/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/en/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/en/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/en/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/enterprise/2.17/admin/clustering/upgrading-a-cluster": "/en/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/en/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/en/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/en/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/en/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/en/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/en/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/en/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/en/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/en/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/en/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/en/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/en/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/en/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/en/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/en/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/en/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/en/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/en/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/en/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/en/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/en/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/en/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/en/enterprise/2.17/admin/guides/developer-workflow": "/en/enterprise/2.17/admin/developer-workflow", - "/enterprise/2.17/admin/developer-workflow": "/en/enterprise/2.17/admin/developer-workflow", - "/enterprise/2.17/admin/guides/developer-workflow": "/en/enterprise/2.17/admin/developer-workflow", - "/en/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/en/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/en/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/en/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/en/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/en/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/en/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/en/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/en/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/en/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/en/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/en/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/en/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/en/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/en/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/en/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security": "/en/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/en/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/en/enterprise/2.17/admin/guides/enterprise-support": "/en/enterprise/2.17/admin/enterprise-support", - "/enterprise/2.17/admin/enterprise-support": "/en/enterprise/2.17/admin/enterprise-support", - "/enterprise/2.17/admin/guides/enterprise-support": "/en/enterprise/2.17/admin/enterprise-support", - "/en/enterprise/2.17/admin/guides/enterprise-support/overview": "/en/enterprise/2.17/admin/enterprise-support/overview", - "/enterprise/2.17/admin/enterprise-support/overview": "/en/enterprise/2.17/admin/enterprise-support/overview", - "/enterprise/2.17/admin/guides/enterprise-support/overview": "/en/enterprise/2.17/admin/enterprise-support/overview", - "/en/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/en/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/en/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/en/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/en/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/enterprise/2.17/admin/enterprise-support/reaching-github-support": "/en/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/en/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/en/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/en/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/en/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.17/admin/enterprise-support/submitting-a-ticket": "/en/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/en/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/en/enterprise/2.17/admin/guides": "/en/enterprise/2.17/admin", - "/enterprise/2.17/admin": "/en/enterprise/2.17/admin", - "/enterprise/2.17/admin/guides": "/en/enterprise/2.17/admin", - "/en/enterprise/2.17/admin/guides/installation/about-enterprise-accounts": "/en/enterprise/2.17/admin/installation/about-enterprise-accounts", - "/enterprise/2.17/admin/installation/about-enterprise-accounts": "/en/enterprise/2.17/admin/installation/about-enterprise-accounts", - "/enterprise/2.17/admin/guides/installation/about-enterprise-accounts": "/en/enterprise/2.17/admin/installation/about-enterprise-accounts", - "/en/enterprise/2.17/admin/guides/installation/about-geo-replication": "/en/enterprise/2.17/admin/installation/about-geo-replication", - "/enterprise/2.17/admin/installation/about-geo-replication": "/en/enterprise/2.17/admin/installation/about-geo-replication", - "/enterprise/2.17/admin/guides/installation/about-geo-replication": "/en/enterprise/2.17/admin/installation/about-geo-replication", - "/en/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/enterprise/2.17/admin/installation/about-high-availability-configuration": "/en/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/en/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/en/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/en/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/en/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/en/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/en/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.17/admin/installation/accessing-the-management-console", - "/enterprise/2.17/admin/installation/accessing-the-management-console": "/en/enterprise/2.17/admin/installation/accessing-the-management-console", - "/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/en/enterprise/2.17/admin/installation/accessing-the-management-console", - "/en/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/en/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/en/enterprise/2.17/admin/guides/installation/activity-dashboard": "/en/enterprise/2.17/admin/installation/activity-dashboard", - "/enterprise/2.17/admin/installation/activity-dashboard": "/en/enterprise/2.17/admin/installation/activity-dashboard", - "/enterprise/2.17/admin/guides/installation/activity-dashboard": "/en/enterprise/2.17/admin/installation/activity-dashboard", - "/en/enterprise/2.17/admin/guides/installation/audit-logging": "/en/enterprise/2.17/admin/installation/audit-logging", - "/enterprise/2.17/admin/installation/audit-logging": "/en/enterprise/2.17/admin/installation/audit-logging", - "/enterprise/2.17/admin/guides/installation/audit-logging": "/en/enterprise/2.17/admin/installation/audit-logging", - "/en/enterprise/2.17/admin/guides/installation/audited-actions": "/en/enterprise/2.17/admin/installation/audited-actions", - "/enterprise/2.17/admin/installation/audited-actions": "/en/enterprise/2.17/admin/installation/audited-actions", - "/enterprise/2.17/admin/guides/installation/audited-actions": "/en/enterprise/2.17/admin/installation/audited-actions", - "/en/enterprise/2.17/admin/guides/installation/command-line-utilities": "/en/enterprise/2.17/admin/installation/command-line-utilities", - "/enterprise/2.17/admin/installation/command-line-utilities": "/en/enterprise/2.17/admin/installation/command-line-utilities", - "/enterprise/2.17/admin/guides/installation/command-line-utilities": "/en/enterprise/2.17/admin/installation/command-line-utilities", - "/en/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.17/admin/installation/configuring-a-hostname", - "/enterprise/2.17/admin/installation/configuring-a-hostname": "/en/enterprise/2.17/admin/installation/configuring-a-hostname", - "/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/en/enterprise/2.17/admin/installation/configuring-a-hostname", - "/en/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/en/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/en/enterprise/2.17/admin/guides/installation/configuring-applications": "/en/enterprise/2.17/admin/installation/configuring-applications", - "/enterprise/2.17/admin/installation/configuring-applications": "/en/enterprise/2.17/admin/installation/configuring-applications", - "/enterprise/2.17/admin/guides/installation/configuring-applications": "/en/enterprise/2.17/admin/installation/configuring-applications", - "/en/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/en/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/en/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/en/enterprise/2.17/admin/guides/installation/configuring-collectd": "/en/enterprise/2.17/admin/installation/configuring-collectd", - "/enterprise/2.17/admin/installation/configuring-collectd": "/en/enterprise/2.17/admin/installation/configuring-collectd", - "/enterprise/2.17/admin/guides/installation/configuring-collectd": "/en/enterprise/2.17/admin/installation/configuring-collectd", - "/en/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/enterprise/2.17/admin/installation/configuring-dns-nameservers": "/en/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/en/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/en/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/en/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.17/admin/installation/configuring-git-large-file-storage": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/en/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/en/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/en/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/en/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/en/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.17/admin/installation/configuring-rate-limits", - "/enterprise/2.17/admin/installation/configuring-rate-limits": "/en/enterprise/2.17/admin/installation/configuring-rate-limits", - "/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/en/enterprise/2.17/admin/installation/configuring-rate-limits", - "/en/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/en/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/en/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/en/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/en/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/en/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/enterprise/2.17/admin/installation/configuring-time-synchronization": "/en/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/en/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/en/enterprise/2.17/admin/guides/installation/configuring-tls": "/en/enterprise/2.17/admin/installation/configuring-tls", - "/enterprise/2.17/admin/installation/configuring-tls": "/en/enterprise/2.17/admin/installation/configuring-tls", - "/enterprise/2.17/admin/guides/installation/configuring-tls": "/en/enterprise/2.17/admin/installation/configuring-tls", - "/en/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/en/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/en/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/en/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.17/admin/installation/creating-a-high-availability-replica": "/en/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/en/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/en/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/en/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/en/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/en/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/en/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.17/admin/installation/enabling-automatic-update-checks": "/en/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/en/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/en/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/en/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.17/admin/installation/enabling-private-mode", - "/enterprise/2.17/admin/installation/enabling-private-mode": "/en/enterprise/2.17/admin/installation/enabling-private-mode", - "/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/en/enterprise/2.17/admin/installation/enabling-private-mode", - "/en/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/en/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.17/admin/installation/enabling-subdomain-isolation": "/en/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/en/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/en/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/en/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/en/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/en/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server": "/en/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/en/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/en/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/en/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/enterprise/2.17/admin/installation/increasing-storage-capacity": "/en/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/en/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/en/enterprise/2.17/admin/guides/installation": "/en/enterprise/2.17/admin/installation", - "/enterprise/2.17/admin/installation": "/en/enterprise/2.17/admin/installation", - "/enterprise/2.17/admin/guides/installation": "/en/enterprise/2.17/admin/installation", - "/en/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/en/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/en/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/en/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/en/enterprise/2.17/admin/guides/installation/log-forwarding": "/en/enterprise/2.17/admin/installation/log-forwarding", - "/enterprise/2.17/admin/installation/log-forwarding": "/en/enterprise/2.17/admin/installation/log-forwarding", - "/enterprise/2.17/admin/guides/installation/log-forwarding": "/en/enterprise/2.17/admin/installation/log-forwarding", - "/en/enterprise/2.17/admin/guides/installation/managing-billing-for-github-enterprise": "/en/enterprise/2.17/admin/installation/managing-billing-for-github-enterprise", - "/enterprise/2.17/admin/installation/managing-billing-for-github-enterprise": "/en/enterprise/2.17/admin/installation/managing-billing-for-github-enterprise", - "/enterprise/2.17/admin/guides/installation/managing-billing-for-github-enterprise": "/en/enterprise/2.17/admin/installation/managing-billing-for-github-enterprise", - "/en/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/en/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/en/enterprise/2.17/admin/guides/installation/managing-your-github-enterprise-license": "/en/enterprise/2.17/admin/installation/managing-your-github-enterprise-license", - "/enterprise/2.17/admin/installation/managing-your-github-enterprise-license": "/en/enterprise/2.17/admin/installation/managing-your-github-enterprise-license", - "/enterprise/2.17/admin/guides/installation/managing-your-github-enterprise-license": "/en/enterprise/2.17/admin/installation/managing-your-github-enterprise-license", - "/en/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/en/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/en/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/en/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/en/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/en/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/en/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/en/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/en/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/enterprise/2.17/admin/installation/monitoring-using-snmp": "/en/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/en/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/en/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/en/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/en/enterprise/2.17/admin/guides/installation/network-ports": "/en/enterprise/2.17/admin/installation/network-ports", - "/enterprise/2.17/admin/installation/network-ports": "/en/enterprise/2.17/admin/installation/network-ports", - "/enterprise/2.17/admin/guides/installation/network-ports": "/en/enterprise/2.17/admin/installation/network-ports", - "/en/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/enterprise/2.17/admin/installation/recommended-alert-thresholds": "/en/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/en/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/en/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/en/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/en/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.17/admin/installation/removing-a-high-availability-replica": "/en/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/en/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/en/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.17/admin/installation/searching-the-audit-log", - "/enterprise/2.17/admin/installation/searching-the-audit-log": "/en/enterprise/2.17/admin/installation/searching-the-audit-log", - "/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/en/enterprise/2.17/admin/installation/searching-the-audit-log", - "/en/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.17/admin/installation/setting-git-push-limits", - "/enterprise/2.17/admin/installation/setting-git-push-limits": "/en/enterprise/2.17/admin/installation/setting-git-push-limits", - "/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/en/enterprise/2.17/admin/installation/setting-git-push-limits", - "/en/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/en/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/en/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.17/admin/installation/setting-up-a-staging-instance": "/en/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/en/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/en/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/enterprise/2.17/admin/installation/setting-up-external-monitoring": "/en/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/en/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/en/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.17/admin/installation/site-admin-dashboard", - "/enterprise/2.17/admin/installation/site-admin-dashboard": "/en/enterprise/2.17/admin/installation/site-admin-dashboard", - "/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/en/enterprise/2.17/admin/installation/site-admin-dashboard", - "/en/enterprise/2.17/admin/guides/installation/system-overview": "/en/enterprise/2.17/admin/installation/system-overview", - "/enterprise/2.17/admin/installation/system-overview": "/en/enterprise/2.17/admin/installation/system-overview", - "/enterprise/2.17/admin/guides/installation/system-overview": "/en/enterprise/2.17/admin/installation/system-overview", - "/en/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.17/admin/installation/troubleshooting-ssl-errors": "/en/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/en/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/en/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/en/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/en/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.17/admin/installation/upgrade-requirements", - "/enterprise/2.17/admin/installation/upgrade-requirements": "/en/enterprise/2.17/admin/installation/upgrade-requirements", - "/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/en/enterprise/2.17/admin/installation/upgrade-requirements", - "/en/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.17/admin/installation/upgrading-github-enterprise-server": "/en/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/en/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/en/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/en/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/enterprise/2.17/admin/installation/validating-your-domain-settings": "/en/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/en/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/en/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.17/admin/installation/viewing-push-logs", - "/enterprise/2.17/admin/installation/viewing-push-logs": "/en/enterprise/2.17/admin/installation/viewing-push-logs", - "/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/en/enterprise/2.17/admin/installation/viewing-push-logs", - "/en/enterprise/2.17/admin/guides/migrations/about-migrations": "/en/enterprise/2.17/admin/migrations/about-migrations", - "/enterprise/2.17/admin/migrations/about-migrations": "/en/enterprise/2.17/admin/migrations/about-migrations", - "/enterprise/2.17/admin/guides/migrations/about-migrations": "/en/enterprise/2.17/admin/migrations/about-migrations", - "/en/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/en/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/en/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/en/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/en/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/en/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/en/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/en/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/en/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/en/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/en/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/migrations": "/en/enterprise/2.17/admin/migrations", - "/enterprise/2.17/admin/migrations": "/en/enterprise/2.17/admin/migrations", - "/enterprise/2.17/admin/guides/migrations": "/en/enterprise/2.17/admin/migrations", - "/en/enterprise/2.17/admin/guides/migrations/overview": "/en/enterprise/2.17/admin/migrations/overview", - "/enterprise/2.17/admin/migrations/overview": "/en/enterprise/2.17/admin/migrations/overview", - "/enterprise/2.17/admin/guides/migrations/overview": "/en/enterprise/2.17/admin/migrations/overview", - "/en/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/en/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/en/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/en/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/en/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/en/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/en/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/en/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/en/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.17/admin/migrations/reviewing-migration-conflicts": "/en/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/en/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/en/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/enterprise/2.17/admin/migrations/reviewing-migration-data": "/en/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/en/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/en/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.17/admin/user-management/about-global-webhooks", - "/enterprise/2.17/admin/user-management/about-global-webhooks": "/en/enterprise/2.17/admin/user-management/about-global-webhooks", - "/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/en/enterprise/2.17/admin/user-management/about-global-webhooks", - "/en/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/enterprise/2.17/admin/user-management/adding-people-to-teams": "/en/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/en/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/en/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/en/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/en/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/en/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/en/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/en/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/en/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/enterprise/2.17/admin/user-management/auditing-ssh-keys": "/en/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/en/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/en/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.17/admin/user-management/auditing-users-across-your-instance": "/en/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/en/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/en/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/en/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/en/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.17/admin/user-management/basic-account-settings", - "/enterprise/2.17/admin/user-management/basic-account-settings": "/en/enterprise/2.17/admin/user-management/basic-account-settings", - "/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/en/enterprise/2.17/admin/user-management/basic-account-settings", - "/en/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/enterprise/2.17/admin/user-management/best-practices-for-user-security": "/en/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/en/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/en/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/enterprise/2.17/admin/user-management/changing-authentication-methods": "/en/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/en/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/en/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.17/admin/user-management/configuring-email-for-notifications": "/en/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/en/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/en/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/en/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/en/enterprise/2.17/admin/guides/user-management/creating-organizations": "/en/enterprise/2.17/admin/user-management/creating-organizations", - "/enterprise/2.17/admin/user-management/creating-organizations": "/en/enterprise/2.17/admin/user-management/creating-organizations", - "/enterprise/2.17/admin/guides/user-management/creating-organizations": "/en/enterprise/2.17/admin/user-management/creating-organizations", - "/en/enterprise/2.17/admin/guides/user-management/creating-teams": "/en/enterprise/2.17/admin/user-management/creating-teams", - "/enterprise/2.17/admin/user-management/creating-teams": "/en/enterprise/2.17/admin/user-management/creating-teams", - "/enterprise/2.17/admin/guides/user-management/creating-teams": "/en/enterprise/2.17/admin/user-management/creating-teams", - "/en/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/en/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/en/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/en/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/en/enterprise/2.17/admin/guides/user-management": "/en/enterprise/2.17/admin/user-management", - "/enterprise/2.17/admin/user-management": "/en/enterprise/2.17/admin/user-management", - "/enterprise/2.17/admin/guides/user-management": "/en/enterprise/2.17/admin/user-management", - "/en/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.17/admin/user-management/managing-dormant-users", - "/enterprise/2.17/admin/user-management/managing-dormant-users": "/en/enterprise/2.17/admin/user-management/managing-dormant-users", - "/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/en/enterprise/2.17/admin/user-management/managing-dormant-users", - "/en/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/enterprise/2.17/admin/user-management/managing-global-webhooks": "/en/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/en/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/en/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.17/admin/user-management/organizations-and-teams", - "/enterprise/2.17/admin/user-management/organizations-and-teams": "/en/enterprise/2.17/admin/user-management/organizations-and-teams", - "/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/en/enterprise/2.17/admin/user-management/organizations-and-teams", - "/en/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/en/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/en/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/en/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/en/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/en/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/en/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/en/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/en/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/en/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/en/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/en/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/en/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.17/admin/user-management/rebuilding-contributions-data": "/en/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/en/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/en/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/en/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/en/enterprise/2.17/admin/guides/user-management/repositories": "/en/enterprise/2.17/admin/user-management/repositories", - "/enterprise/2.17/admin/user-management/repositories": "/en/enterprise/2.17/admin/user-management/repositories", - "/enterprise/2.17/admin/guides/user-management/repositories": "/en/enterprise/2.17/admin/user-management/repositories", - "/en/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/en/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/en/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/en/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/en/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/en/enterprise/2.17/admin/guides/user-management/user-security": "/en/enterprise/2.17/admin/user-management/user-security", - "/enterprise/2.17/admin/user-management/user-security": "/en/enterprise/2.17/admin/user-management/user-security", - "/enterprise/2.17/admin/guides/user-management/user-security": "/en/enterprise/2.17/admin/user-management/user-security", - "/en/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/enterprise/2.17/admin/user-management/using-built-in-authentication": "/en/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/en/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/en/enterprise/2.17/admin/guides/user-management/using-cas": "/en/enterprise/2.17/admin/user-management/using-cas", - "/enterprise/2.17/admin/user-management/using-cas": "/en/enterprise/2.17/admin/user-management/using-cas", - "/enterprise/2.17/admin/guides/user-management/using-cas": "/en/enterprise/2.17/admin/user-management/using-cas", - "/en/enterprise/2.17/admin/guides/user-management/using-ldap": "/en/enterprise/2.17/admin/user-management/using-ldap", - "/enterprise/2.17/admin/user-management/using-ldap": "/en/enterprise/2.17/admin/user-management/using-ldap", - "/enterprise/2.17/admin/guides/user-management/using-ldap": "/en/enterprise/2.17/admin/user-management/using-ldap", - "/en/enterprise/2.17/admin/guides/user-management/using-saml": "/en/enterprise/2.17/admin/user-management/using-saml", - "/enterprise/2.17/admin/user-management/using-saml": "/en/enterprise/2.17/admin/user-management/using-saml", - "/enterprise/2.17/admin/guides/user-management/using-saml": "/en/enterprise/2.17/admin/user-management/using-saml", - "/enterprise/2.17": "/en/enterprise/2.17", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/en/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/en/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/en/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/en/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/en/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/en/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.17/user/github/administering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/en/enterprise/2.17/user/administering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/en/enterprise/2.17/github/administering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/enterprise/2.17/user/github/administering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/enterprise/2.17/user/administering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/enterprise/2.17/github/administering-a-repository/about-releases": "/en/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/en/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/en/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/en/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/en/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/en/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/en/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/en/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/en/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/en/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/en/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/en/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/en/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/en/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/en/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/en/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/en/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/en/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/en/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/en/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/en/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/en/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/en/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/en/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/en/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/en/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/en/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/en/enterprise/2.17/user/administering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/en/enterprise/2.17/github/administering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/enterprise/2.17/user/github/administering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/enterprise/2.17/user/administering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/enterprise/2.17/github/administering-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/en/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/en/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.17/user/github/administering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/en/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/en/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/en/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/en/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/en/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/en/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/en/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/en/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/en/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/en/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/en/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/en/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/en/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/en/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/en/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/en/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/en/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/en/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/en/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/en/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/en/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/en/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/en/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/en/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/en/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/en/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/en/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/en/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/en/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/en/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/en/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/en/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/en/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/en/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/en/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/en/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/en/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/en/enterprise/2.17/user/authenticating-to-github/about-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/en/enterprise/2.17/github/authenticating-to-github/about-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/enterprise/2.17/user/github/authenticating-to-github/about-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/enterprise/2.17/user/authenticating-to-github/about-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/enterprise/2.17/github/authenticating-to-github/about-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/en/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/en/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/en/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/en/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/en/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/en/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/en/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/en/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/en/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/en/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/en/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/en/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/en/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/en/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/en/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/en/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/en/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/en/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/en/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/en/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/en/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/en/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/en/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/en/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/en/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/en/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/en/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/en/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/en/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/en/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/en/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/en/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/en/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/en/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/en/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/en/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/en/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/en/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/en/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/en/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/en/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/en/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/en/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/en/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/en/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/en/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/en/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/en/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/en/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/en/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/en/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/en/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/en/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/en/enterprise/2.17/user/authenticating-to-github": "/en/enterprise/2.17/user/github/authenticating-to-github", - "/en/enterprise/2.17/github/authenticating-to-github": "/en/enterprise/2.17/user/github/authenticating-to-github", - "/enterprise/2.17/user/github/authenticating-to-github": "/en/enterprise/2.17/user/github/authenticating-to-github", - "/enterprise/2.17/user/authenticating-to-github": "/en/enterprise/2.17/user/github/authenticating-to-github", - "/enterprise/2.17/github/authenticating-to-github": "/en/enterprise/2.17/user/github/authenticating-to-github", - "/en/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/en/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/en/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/en/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/en/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/en/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/en/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/en/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/en/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/en/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/en/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/en/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/en/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/en/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/en/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/en/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/en/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/en/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/en/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/en/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/en/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/en/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/en/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/en/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/en/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/en/enterprise/2.17/user/authenticating-to-github/signing-commits": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/en/enterprise/2.17/github/authenticating-to-github/signing-commits": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/enterprise/2.17/user/github/authenticating-to-github/signing-commits": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/enterprise/2.17/user/authenticating-to-github/signing-commits": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/enterprise/2.17/github/authenticating-to-github/signing-commits": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/en/enterprise/2.17/user/authenticating-to-github/signing-tags": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/en/enterprise/2.17/github/authenticating-to-github/signing-tags": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/enterprise/2.17/user/github/authenticating-to-github/signing-tags": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/enterprise/2.17/user/authenticating-to-github/signing-tags": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/enterprise/2.17/github/authenticating-to-github/signing-tags": "/en/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/en/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/en/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/en/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/en/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/enterprise/2.17/user/github/authenticating-to-github/sudo-mode": "/en/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/en/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/en/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/en/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/en/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/en/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/en/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/en/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/en/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/en/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/en/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/en/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/en/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/en/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/en/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/en/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/en/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/en/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/en/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/en/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/en/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/en/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/en/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/en/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/en/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/en/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/en/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/en/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/en/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/en/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/en/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions": "/en/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/en/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/en/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/en/enterprise/2.17/user/building-a-strong-community/about-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/en/enterprise/2.17/github/building-a-strong-community/about-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/enterprise/2.17/user/github/building-a-strong-community/about-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/enterprise/2.17/user/building-a-strong-community/about-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/enterprise/2.17/github/building-a-strong-community/about-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/en/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/en/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/en/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/en/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/en/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/en/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/en/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/en/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/en/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/en/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/en/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/en/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/en/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/en/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/en/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/en/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/en/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/en/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/en/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/en/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/en/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/en/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/en/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/en/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/en/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/en/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/en/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/en/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/en/enterprise/2.17/user/building-a-strong-community": "/en/enterprise/2.17/user/github/building-a-strong-community", - "/en/enterprise/2.17/github/building-a-strong-community": "/en/enterprise/2.17/user/github/building-a-strong-community", - "/enterprise/2.17/user/github/building-a-strong-community": "/en/enterprise/2.17/user/github/building-a-strong-community", - "/enterprise/2.17/user/building-a-strong-community": "/en/enterprise/2.17/user/github/building-a-strong-community", - "/enterprise/2.17/github/building-a-strong-community": "/en/enterprise/2.17/user/github/building-a-strong-community", - "/en/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/en/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/enterprise/2.17/user/github/building-a-strong-community/locking-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/en/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/en/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/en/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/en/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/en/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/en/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/en/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/en/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/en/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/en/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/en/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/en/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/en/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/en/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/en/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/en/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/en/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/en/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/en/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/en/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/en/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/en/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/en/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/en/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/en/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/en/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/en/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/en/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/en/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/en/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/en/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/en/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/en/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/en/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/en/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/en/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/en/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/en/enterprise/2.17/user/committing-changes-to-your-project": "/en/enterprise/2.17/user/github/committing-changes-to-your-project", - "/en/enterprise/2.17/github/committing-changes-to-your-project": "/en/enterprise/2.17/user/github/committing-changes-to-your-project", - "/enterprise/2.17/user/github/committing-changes-to-your-project": "/en/enterprise/2.17/user/github/committing-changes-to-your-project", - "/enterprise/2.17/user/committing-changes-to-your-project": "/en/enterprise/2.17/user/github/committing-changes-to-your-project", - "/enterprise/2.17/github/committing-changes-to-your-project": "/en/enterprise/2.17/user/github/committing-changes-to-your-project", - "/en/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/en/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/en/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/en/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/en/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/en/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/en/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/en/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/en/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/en/enterprise/2.17/user/extending-github/about-webhooks": "/en/enterprise/2.17/user/github/extending-github/about-webhooks", - "/en/enterprise/2.17/github/extending-github/about-webhooks": "/en/enterprise/2.17/user/github/extending-github/about-webhooks", - "/enterprise/2.17/user/github/extending-github/about-webhooks": "/en/enterprise/2.17/user/github/extending-github/about-webhooks", - "/enterprise/2.17/user/extending-github/about-webhooks": "/en/enterprise/2.17/user/github/extending-github/about-webhooks", - "/enterprise/2.17/github/extending-github/about-webhooks": "/en/enterprise/2.17/user/github/extending-github/about-webhooks", - "/en/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/en/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/en/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/en/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/enterprise/2.17/user/github/extending-github/getting-started-with-the-api": "/en/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/en/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/en/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/en/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/en/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/en/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/en/enterprise/2.17/user/extending-github": "/en/enterprise/2.17/user/github/extending-github", - "/en/enterprise/2.17/github/extending-github": "/en/enterprise/2.17/user/github/extending-github", - "/enterprise/2.17/user/github/extending-github": "/en/enterprise/2.17/user/github/extending-github", - "/enterprise/2.17/user/extending-github": "/en/enterprise/2.17/user/github/extending-github", - "/enterprise/2.17/github/extending-github": "/en/enterprise/2.17/user/github/extending-github", - "/en/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/en/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/en/enterprise/2.17/user/getting-started-with-github/be-social": "/en/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/en/enterprise/2.17/github/getting-started-with-github/be-social": "/en/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/enterprise/2.17/user/github/getting-started-with-github/be-social": "/en/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/enterprise/2.17/user/getting-started-with-github/be-social": "/en/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/enterprise/2.17/github/getting-started-with-github/be-social": "/en/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/en/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/en/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/enterprise/2.17/user/github/getting-started-with-github/create-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/en/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/en/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/en/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/en/enterprise/2.17/user/getting-started-with-github/following-people": "/en/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/en/enterprise/2.17/github/getting-started-with-github/following-people": "/en/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/enterprise/2.17/user/github/getting-started-with-github/following-people": "/en/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/enterprise/2.17/user/getting-started-with-github/following-people": "/en/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/enterprise/2.17/github/getting-started-with-github/following-people": "/en/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/en/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/en/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/en/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/en/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/en/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/en/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/en/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/en/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/en/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/en/enterprise/2.17/user/getting-started-with-github/github-desktop": "/en/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/en/enterprise/2.17/github/getting-started-with-github/github-desktop": "/en/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/enterprise/2.17/user/github/getting-started-with-github/github-desktop": "/en/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/enterprise/2.17/user/getting-started-with-github/github-desktop": "/en/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/enterprise/2.17/github/getting-started-with-github/github-desktop": "/en/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/en/enterprise/2.17/user/getting-started-with-github/github-glossary": "/en/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/en/enterprise/2.17/github/getting-started-with-github/github-glossary": "/en/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/enterprise/2.17/user/github/getting-started-with-github/github-glossary": "/en/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/enterprise/2.17/user/getting-started-with-github/github-glossary": "/en/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/enterprise/2.17/github/getting-started-with-github/github-glossary": "/en/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/en/enterprise/2.17/user/getting-started-with-github/githubs-products": "/en/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/en/enterprise/2.17/github/getting-started-with-github/githubs-products": "/en/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/enterprise/2.17/user/github/getting-started-with-github/githubs-products": "/en/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/enterprise/2.17/user/getting-started-with-github/githubs-products": "/en/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/enterprise/2.17/github/getting-started-with-github/githubs-products": "/en/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/en/enterprise/2.17/user/getting-started-with-github": "/en/enterprise/2.17/user/github/getting-started-with-github", - "/en/enterprise/2.17/github/getting-started-with-github": "/en/enterprise/2.17/user/github/getting-started-with-github", - "/enterprise/2.17/user/github/getting-started-with-github": "/en/enterprise/2.17/user/github/getting-started-with-github", - "/enterprise/2.17/user/getting-started-with-github": "/en/enterprise/2.17/user/github/getting-started-with-github", - "/enterprise/2.17/github/getting-started-with-github": "/en/enterprise/2.17/user/github/getting-started-with-github", - "/en/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/en/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/en/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/en/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/en/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/en/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/en/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/enterprise/2.17/user/github/getting-started-with-github/learning-about-github": "/en/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/en/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/en/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/en/enterprise/2.17/user/getting-started-with-github/quickstart": "/en/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/en/enterprise/2.17/github/getting-started-with-github/quickstart": "/en/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/enterprise/2.17/user/github/getting-started-with-github/quickstart": "/en/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/enterprise/2.17/user/getting-started-with-github/quickstart": "/en/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/enterprise/2.17/github/getting-started-with-github/quickstart": "/en/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/en/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/en/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/en/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/en/enterprise/2.17/user/getting-started-with-github/set-up-git": "/en/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/en/enterprise/2.17/github/getting-started-with-github/set-up-git": "/en/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/enterprise/2.17/user/github/getting-started-with-github/set-up-git": "/en/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/enterprise/2.17/user/getting-started-with-github/set-up-git": "/en/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/enterprise/2.17/github/getting-started-with-github/set-up-git": "/en/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/en/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/en/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/en/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/en/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/en/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/en/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/en/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/en/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/en/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/en/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/en/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/en/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/enterprise/2.17/user/github/getting-started-with-github/supported-browsers": "/en/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/en/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/en/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/en/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/en/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/en/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/en/enterprise/2.17/user/getting-started-with-github/using-github": "/en/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/en/enterprise/2.17/github/getting-started-with-github/using-github": "/en/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/enterprise/2.17/user/github/getting-started-with-github/using-github": "/en/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/enterprise/2.17/user/getting-started-with-github/using-github": "/en/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/enterprise/2.17/github/getting-started-with-github/using-github": "/en/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/en/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/en/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/en/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/en/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/en/enterprise/2.17/user/importing-your-projects-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github", - "/en/enterprise/2.17/github/importing-your-projects-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github", - "/enterprise/2.17/user/github/importing-your-projects-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github", - "/enterprise/2.17/user/importing-your-projects-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github", - "/enterprise/2.17/github/importing-your-projects-to-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github", - "/en/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/en/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/en/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/en/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/en/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/en/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/en/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/en/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/en/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/en/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/en/enterprise/2.17/user": "/en/enterprise/2.17/user/github", - "/en/enterprise/2.17/github": "/en/enterprise/2.17/user/github", - "/enterprise/2.17/user/github": "/en/enterprise/2.17/user/github", - "/enterprise/2.17/user": "/en/enterprise/2.17/user/github", - "/enterprise/2.17/github": "/en/enterprise/2.17/user/github", - "/en/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/en/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/en/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/en/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/en/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/en/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/en/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/en/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/en/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/en/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/en/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/en/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/en/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/en/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/en/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/en/enterprise/2.17/user/managing-files-in-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository", - "/en/enterprise/2.17/github/managing-files-in-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository", - "/enterprise/2.17/user/github/managing-files-in-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository", - "/enterprise/2.17/user/managing-files-in-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository", - "/enterprise/2.17/github/managing-files-in-a-repository": "/en/enterprise/2.17/user/github/managing-files-in-a-repository", - "/en/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/en/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/en/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/en/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/en/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/en/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/en/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/en/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/en/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/en/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/en/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/en/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/en/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/en/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/en/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/en/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/en/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/en/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/en/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/en/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/en/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/en/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/en/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/en/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/en/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/en/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/en/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/en/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/en/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/en/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/en/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/en/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/en/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/en/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/en/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files": "/en/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/en/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/en/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/en/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/en/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/en/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/en/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/en/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/en/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries": "/en/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/en/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/en/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/en/enterprise/2.17/user/managing-large-files": "/en/enterprise/2.17/user/github/managing-large-files", - "/en/enterprise/2.17/github/managing-large-files": "/en/enterprise/2.17/user/github/managing-large-files", - "/enterprise/2.17/user/github/managing-large-files": "/en/enterprise/2.17/user/github/managing-large-files", - "/enterprise/2.17/user/managing-large-files": "/en/enterprise/2.17/user/github/managing-large-files", - "/enterprise/2.17/github/managing-large-files": "/en/enterprise/2.17/user/github/managing-large-files", - "/en/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/en/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/en/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/en/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/en/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/en/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/en/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/en/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/en/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/en/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/en/enterprise/2.17/user/managing-large-files/versioning-large-files": "/en/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/en/enterprise/2.17/github/managing-large-files/versioning-large-files": "/en/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/enterprise/2.17/user/github/managing-large-files/versioning-large-files": "/en/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/enterprise/2.17/user/managing-large-files/versioning-large-files": "/en/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/enterprise/2.17/github/managing-large-files/versioning-large-files": "/en/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/en/enterprise/2.17/user/managing-large-files/working-with-large-files": "/en/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/en/enterprise/2.17/github/managing-large-files/working-with-large-files": "/en/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/enterprise/2.17/user/github/managing-large-files/working-with-large-files": "/en/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/enterprise/2.17/user/managing-large-files/working-with-large-files": "/en/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/enterprise/2.17/github/managing-large-files/working-with-large-files": "/en/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/en/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/en/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/en/enterprise/2.17/user/managing-security-vulnerabilities": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/en/enterprise/2.17/github/managing-security-vulnerabilities": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/enterprise/2.17/user/github/managing-security-vulnerabilities": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/enterprise/2.17/user/managing-security-vulnerabilities": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/enterprise/2.17/github/managing-security-vulnerabilities": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/en/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/en/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/en/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/en/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/en/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/en/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/en/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/en/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/en/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/en/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/en/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/en/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/en/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/en/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/en/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/en/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/en/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/en/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/en/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/en/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/en/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/en/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/en/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/en/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/en/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/en/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/en/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/en/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/en/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/en/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/en/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/en/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/en/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/en/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/en/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/en/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/en/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/en/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/en/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/en/enterprise/2.17/user/managing-your-work-on-github": "/en/enterprise/2.17/user/github/managing-your-work-on-github", - "/en/enterprise/2.17/github/managing-your-work-on-github": "/en/enterprise/2.17/user/github/managing-your-work-on-github", - "/enterprise/2.17/user/github/managing-your-work-on-github": "/en/enterprise/2.17/user/github/managing-your-work-on-github", - "/enterprise/2.17/user/managing-your-work-on-github": "/en/enterprise/2.17/user/github/managing-your-work-on-github", - "/enterprise/2.17/github/managing-your-work-on-github": "/en/enterprise/2.17/user/github/managing-your-work-on-github", - "/en/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/en/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/en/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/en/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/en/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/en/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/en/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/en/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/en/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/en/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/en/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/en/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/en/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/en/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/en/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/en/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/en/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/en/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/en/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/en/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/en/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/en/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/en/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/en/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/en/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/en/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/en/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/en/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/en/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/en/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/en/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/en/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/en/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/en/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/en/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/en/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/en/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/en/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/en/enterprise/2.17/user/searching-for-information-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github", - "/en/enterprise/2.17/github/searching-for-information-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github", - "/enterprise/2.17/user/github/searching-for-information-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github", - "/enterprise/2.17/user/searching-for-information-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github", - "/enterprise/2.17/github/searching-for-information-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-code": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-users": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/en/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/en/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/en/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/en/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/en/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/en/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/en/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/en/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/en/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/en/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/en/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/en/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/en/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account", - "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account", - "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/en/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/en/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/en/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/en/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/en/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/en/enterprise/2.17/user/using-git/about-git-rebase": "/en/enterprise/2.17/user/github/using-git/about-git-rebase", - "/en/enterprise/2.17/github/using-git/about-git-rebase": "/en/enterprise/2.17/user/github/using-git/about-git-rebase", - "/enterprise/2.17/user/github/using-git/about-git-rebase": "/en/enterprise/2.17/user/github/using-git/about-git-rebase", - "/enterprise/2.17/user/using-git/about-git-rebase": "/en/enterprise/2.17/user/github/using-git/about-git-rebase", - "/enterprise/2.17/github/using-git/about-git-rebase": "/en/enterprise/2.17/user/github/using-git/about-git-rebase", - "/en/enterprise/2.17/user/using-git/about-git-subtree-merges": "/en/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/en/enterprise/2.17/github/using-git/about-git-subtree-merges": "/en/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/enterprise/2.17/user/github/using-git/about-git-subtree-merges": "/en/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/enterprise/2.17/user/using-git/about-git-subtree-merges": "/en/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/enterprise/2.17/github/using-git/about-git-subtree-merges": "/en/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/en/enterprise/2.17/user/using-git/about-remote-repositories": "/en/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/en/enterprise/2.17/github/using-git/about-remote-repositories": "/en/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/enterprise/2.17/user/github/using-git/about-remote-repositories": "/en/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/enterprise/2.17/user/using-git/about-remote-repositories": "/en/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/enterprise/2.17/github/using-git/about-remote-repositories": "/en/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/en/enterprise/2.17/user/using-git/adding-a-remote": "/en/enterprise/2.17/user/github/using-git/adding-a-remote", - "/en/enterprise/2.17/github/using-git/adding-a-remote": "/en/enterprise/2.17/user/github/using-git/adding-a-remote", - "/enterprise/2.17/user/github/using-git/adding-a-remote": "/en/enterprise/2.17/user/github/using-git/adding-a-remote", - "/enterprise/2.17/user/using-git/adding-a-remote": "/en/enterprise/2.17/user/github/using-git/adding-a-remote", - "/enterprise/2.17/github/using-git/adding-a-remote": "/en/enterprise/2.17/user/github/using-git/adding-a-remote", - "/en/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/en/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/en/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/en/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/enterprise/2.17/user/github/using-git/associating-text-editors-with-git": "/en/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/en/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/en/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/en/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/en/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/en/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/en/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git": "/en/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/en/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/en/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/en/enterprise/2.17/user/using-git/changing-a-remotes-url": "/en/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/en/enterprise/2.17/github/using-git/changing-a-remotes-url": "/en/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/enterprise/2.17/user/github/using-git/changing-a-remotes-url": "/en/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/enterprise/2.17/user/using-git/changing-a-remotes-url": "/en/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/enterprise/2.17/github/using-git/changing-a-remotes-url": "/en/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/en/enterprise/2.17/user/using-git/changing-author-info": "/en/enterprise/2.17/user/github/using-git/changing-author-info", - "/en/enterprise/2.17/github/using-git/changing-author-info": "/en/enterprise/2.17/user/github/using-git/changing-author-info", - "/enterprise/2.17/user/github/using-git/changing-author-info": "/en/enterprise/2.17/user/github/using-git/changing-author-info", - "/enterprise/2.17/user/using-git/changing-author-info": "/en/enterprise/2.17/user/github/using-git/changing-author-info", - "/enterprise/2.17/github/using-git/changing-author-info": "/en/enterprise/2.17/user/github/using-git/changing-author-info", - "/en/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/en/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/en/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/en/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/en/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/en/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/en/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/en/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/en/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/en/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/en/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github": "/en/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/en/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/en/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/en/enterprise/2.17/user/using-git/git-workflows": "/en/enterprise/2.17/user/github/using-git/git-workflows", - "/en/enterprise/2.17/github/using-git/git-workflows": "/en/enterprise/2.17/user/github/using-git/git-workflows", - "/enterprise/2.17/user/github/using-git/git-workflows": "/en/enterprise/2.17/user/github/using-git/git-workflows", - "/enterprise/2.17/user/using-git/git-workflows": "/en/enterprise/2.17/user/github/using-git/git-workflows", - "/enterprise/2.17/github/using-git/git-workflows": "/en/enterprise/2.17/user/github/using-git/git-workflows", - "/en/enterprise/2.17/user/using-git/ignoring-files": "/en/enterprise/2.17/user/github/using-git/ignoring-files", - "/en/enterprise/2.17/github/using-git/ignoring-files": "/en/enterprise/2.17/user/github/using-git/ignoring-files", - "/enterprise/2.17/user/github/using-git/ignoring-files": "/en/enterprise/2.17/user/github/using-git/ignoring-files", - "/enterprise/2.17/user/using-git/ignoring-files": "/en/enterprise/2.17/user/github/using-git/ignoring-files", - "/enterprise/2.17/github/using-git/ignoring-files": "/en/enterprise/2.17/user/github/using-git/ignoring-files", - "/en/enterprise/2.17/user/using-git": "/en/enterprise/2.17/user/github/using-git", - "/en/enterprise/2.17/github/using-git": "/en/enterprise/2.17/user/github/using-git", - "/enterprise/2.17/user/github/using-git": "/en/enterprise/2.17/user/github/using-git", - "/enterprise/2.17/user/using-git": "/en/enterprise/2.17/user/github/using-git", - "/enterprise/2.17/github/using-git": "/en/enterprise/2.17/user/github/using-git", - "/en/enterprise/2.17/user/using-git/learning-about-git": "/en/enterprise/2.17/user/github/using-git/learning-about-git", - "/en/enterprise/2.17/github/using-git/learning-about-git": "/en/enterprise/2.17/user/github/using-git/learning-about-git", - "/enterprise/2.17/user/github/using-git/learning-about-git": "/en/enterprise/2.17/user/github/using-git/learning-about-git", - "/enterprise/2.17/user/using-git/learning-about-git": "/en/enterprise/2.17/user/github/using-git/learning-about-git", - "/enterprise/2.17/github/using-git/learning-about-git": "/en/enterprise/2.17/user/github/using-git/learning-about-git", - "/en/enterprise/2.17/user/using-git/managing-remote-repositories": "/en/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/en/enterprise/2.17/github/using-git/managing-remote-repositories": "/en/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/enterprise/2.17/user/github/using-git/managing-remote-repositories": "/en/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/enterprise/2.17/user/using-git/managing-remote-repositories": "/en/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/enterprise/2.17/github/using-git/managing-remote-repositories": "/en/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/en/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/en/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/en/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/en/enterprise/2.17/user/using-git/removing-a-remote": "/en/enterprise/2.17/user/github/using-git/removing-a-remote", - "/en/enterprise/2.17/github/using-git/removing-a-remote": "/en/enterprise/2.17/user/github/using-git/removing-a-remote", - "/enterprise/2.17/user/github/using-git/removing-a-remote": "/en/enterprise/2.17/user/github/using-git/removing-a-remote", - "/enterprise/2.17/user/using-git/removing-a-remote": "/en/enterprise/2.17/user/github/using-git/removing-a-remote", - "/enterprise/2.17/github/using-git/removing-a-remote": "/en/enterprise/2.17/user/github/using-git/removing-a-remote", - "/en/enterprise/2.17/user/using-git/renaming-a-remote": "/en/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/en/enterprise/2.17/github/using-git/renaming-a-remote": "/en/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/enterprise/2.17/user/github/using-git/renaming-a-remote": "/en/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/enterprise/2.17/user/using-git/renaming-a-remote": "/en/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/enterprise/2.17/github/using-git/renaming-a-remote": "/en/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/en/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/en/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/en/enterprise/2.17/user/using-git/setting-your-username-in-git": "/en/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/en/enterprise/2.17/github/using-git/setting-your-username-in-git": "/en/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/enterprise/2.17/user/github/using-git/setting-your-username-in-git": "/en/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/enterprise/2.17/user/using-git/setting-your-username-in-git": "/en/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/enterprise/2.17/github/using-git/setting-your-username-in-git": "/en/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/en/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/en/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/en/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/en/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/en/enterprise/2.17/user/using-git/using-advanced-git-commands": "/en/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/en/enterprise/2.17/github/using-git/using-advanced-git-commands": "/en/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/enterprise/2.17/user/github/using-git/using-advanced-git-commands": "/en/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/enterprise/2.17/user/using-git/using-advanced-git-commands": "/en/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/enterprise/2.17/github/using-git/using-advanced-git-commands": "/en/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/en/enterprise/2.17/user/using-git/using-common-git-commands": "/en/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/en/enterprise/2.17/github/using-git/using-common-git-commands": "/en/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/enterprise/2.17/user/github/using-git/using-common-git-commands": "/en/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/enterprise/2.17/user/using-git/using-common-git-commands": "/en/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/enterprise/2.17/github/using-git/using-common-git-commands": "/en/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/en/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/en/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/en/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/en/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/en/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/en/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/en/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use": "/en/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/en/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/en/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/en/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/en/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/en/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/en/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/en/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/en/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/en/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/en/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/en/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/en/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/en/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/en/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/en/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/en/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/en/enterprise/2.17/user/working-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages", - "/en/enterprise/2.17/github/working-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages", - "/enterprise/2.17/user/github/working-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages", - "/enterprise/2.17/user/working-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages", - "/enterprise/2.17/github/working-with-github-pages": "/en/enterprise/2.17/user/github/working-with-github-pages", - "/en/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/en/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/en/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/en/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/en/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/en/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/en/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/en/enterprise/2.17/user/writing-on-github/about-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/en/enterprise/2.17/github/writing-on-github/about-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/enterprise/2.17/user/github/writing-on-github/about-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/enterprise/2.17/user/writing-on-github/about-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/enterprise/2.17/github/writing-on-github/about-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/en/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/en/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/en/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/en/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/en/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/en/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/en/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/en/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/en/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/en/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/en/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/en/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/en/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/en/enterprise/2.17/user/writing-on-github/creating-gists": "/en/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/en/enterprise/2.17/github/writing-on-github/creating-gists": "/en/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/enterprise/2.17/user/github/writing-on-github/creating-gists": "/en/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/enterprise/2.17/user/writing-on-github/creating-gists": "/en/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/enterprise/2.17/github/writing-on-github/creating-gists": "/en/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/en/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/en/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/en/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/en/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/en/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/en/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/en/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/en/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/en/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/en/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/en/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/en/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/en/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/en/enterprise/2.17/user/writing-on-github": "/en/enterprise/2.17/user/github/writing-on-github", - "/en/enterprise/2.17/github/writing-on-github": "/en/enterprise/2.17/user/github/writing-on-github", - "/enterprise/2.17/user/github/writing-on-github": "/en/enterprise/2.17/user/github/writing-on-github", - "/enterprise/2.17/user/writing-on-github": "/en/enterprise/2.17/user/github/writing-on-github", - "/enterprise/2.17/github/writing-on-github": "/en/enterprise/2.17/user/github/writing-on-github", - "/en/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/en/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/en/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/en/enterprise/2.17/user/writing-on-github/using-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/en/enterprise/2.17/github/writing-on-github/using-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/enterprise/2.17/user/github/writing-on-github/using-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/enterprise/2.17/user/writing-on-github/using-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/enterprise/2.17/github/writing-on-github/using-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/en/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/en/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/en/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/en/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/en/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/en/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/en/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/en/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql": "/en/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/en/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/2.17/graphql/guides": "/en/enterprise/2.17/user/graphql/guides", - "/enterprise/2.17/user/graphql/guides": "/en/enterprise/2.17/user/graphql/guides", - "/enterprise/2.17/graphql/guides": "/en/enterprise/2.17/user/graphql/guides", - "/en/enterprise/2.17/graphql/guides/introduction-to-graphql": "/en/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/enterprise/2.17/user/graphql/guides/introduction-to-graphql": "/en/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/enterprise/2.17/graphql/guides/introduction-to-graphql": "/en/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/en/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/2.17/graphql/guides/using-global-node-ids": "/en/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/enterprise/2.17/user/graphql/guides/using-global-node-ids": "/en/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/enterprise/2.17/graphql/guides/using-global-node-ids": "/en/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/en/enterprise/2.17/graphql/guides/using-the-explorer": "/en/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/enterprise/2.17/user/graphql/guides/using-the-explorer": "/en/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/enterprise/2.17/graphql/guides/using-the-explorer": "/en/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/en/enterprise/2.17/graphql": "/en/enterprise/2.17/user/graphql", - "/enterprise/2.17/user/graphql": "/en/enterprise/2.17/user/graphql", - "/enterprise/2.17/graphql": "/en/enterprise/2.17/user/graphql", - "/en/enterprise/2.17/graphql/overview/about-the-graphql-api": "/en/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/enterprise/2.17/user/graphql/overview/about-the-graphql-api": "/en/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/enterprise/2.17/graphql/overview/about-the-graphql-api": "/en/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/en/enterprise/2.17/graphql/overview/breaking-changes": "/en/enterprise/2.17/user/graphql/overview/breaking-changes", - "/enterprise/2.17/user/graphql/overview/breaking-changes": "/en/enterprise/2.17/user/graphql/overview/breaking-changes", - "/enterprise/2.17/graphql/overview/breaking-changes": "/en/enterprise/2.17/user/graphql/overview/breaking-changes", - "/en/enterprise/2.17/graphql/overview/changelog": "/en/enterprise/2.17/user/graphql/overview/changelog", - "/enterprise/2.17/user/graphql/overview/changelog": "/en/enterprise/2.17/user/graphql/overview/changelog", - "/enterprise/2.17/graphql/overview/changelog": "/en/enterprise/2.17/user/graphql/overview/changelog", - "/en/enterprise/2.17/graphql/overview/explorer": "/en/enterprise/2.17/user/graphql/overview/explorer", - "/enterprise/2.17/user/graphql/overview/explorer": "/en/enterprise/2.17/user/graphql/overview/explorer", - "/enterprise/2.17/graphql/overview/explorer": "/en/enterprise/2.17/user/graphql/overview/explorer", - "/en/enterprise/2.17/graphql/overview": "/en/enterprise/2.17/user/graphql/overview", - "/enterprise/2.17/user/graphql/overview": "/en/enterprise/2.17/user/graphql/overview", - "/enterprise/2.17/graphql/overview": "/en/enterprise/2.17/user/graphql/overview", - "/en/enterprise/2.17/graphql/overview/resource-limitations": "/en/enterprise/2.17/user/graphql/overview/resource-limitations", - "/enterprise/2.17/user/graphql/overview/resource-limitations": "/en/enterprise/2.17/user/graphql/overview/resource-limitations", - "/enterprise/2.17/graphql/overview/resource-limitations": "/en/enterprise/2.17/user/graphql/overview/resource-limitations", - "/en/enterprise/2.17/graphql/overview/schema-previews": "/en/enterprise/2.17/user/graphql/overview/schema-previews", - "/enterprise/2.17/user/graphql/overview/schema-previews": "/en/enterprise/2.17/user/graphql/overview/schema-previews", - "/enterprise/2.17/graphql/overview/schema-previews": "/en/enterprise/2.17/user/graphql/overview/schema-previews", - "/en/enterprise/2.17/graphql/reference/enums": "/en/enterprise/2.17/user/graphql/reference/enums", - "/enterprise/2.17/user/graphql/reference/enums": "/en/enterprise/2.17/user/graphql/reference/enums", - "/enterprise/2.17/graphql/reference/enums": "/en/enterprise/2.17/user/graphql/reference/enums", - "/en/enterprise/2.17/graphql/reference": "/en/enterprise/2.17/user/graphql/reference", - "/enterprise/2.17/user/graphql/reference": "/en/enterprise/2.17/user/graphql/reference", - "/enterprise/2.17/graphql/reference": "/en/enterprise/2.17/user/graphql/reference", - "/en/enterprise/2.17/graphql/reference/input-objects": "/en/enterprise/2.17/user/graphql/reference/input-objects", - "/enterprise/2.17/user/graphql/reference/input-objects": "/en/enterprise/2.17/user/graphql/reference/input-objects", - "/enterprise/2.17/graphql/reference/input-objects": "/en/enterprise/2.17/user/graphql/reference/input-objects", - "/en/enterprise/2.17/graphql/reference/interfaces": "/en/enterprise/2.17/user/graphql/reference/interfaces", - "/enterprise/2.17/user/graphql/reference/interfaces": "/en/enterprise/2.17/user/graphql/reference/interfaces", - "/enterprise/2.17/graphql/reference/interfaces": "/en/enterprise/2.17/user/graphql/reference/interfaces", - "/en/enterprise/2.17/graphql/reference/mutations": "/en/enterprise/2.17/user/graphql/reference/mutations", - "/enterprise/2.17/user/graphql/reference/mutations": "/en/enterprise/2.17/user/graphql/reference/mutations", - "/enterprise/2.17/graphql/reference/mutations": "/en/enterprise/2.17/user/graphql/reference/mutations", - "/en/enterprise/2.17/graphql/reference/objects": "/en/enterprise/2.17/user/graphql/reference/objects", - "/enterprise/2.17/user/graphql/reference/objects": "/en/enterprise/2.17/user/graphql/reference/objects", - "/enterprise/2.17/graphql/reference/objects": "/en/enterprise/2.17/user/graphql/reference/objects", - "/en/enterprise/2.17/graphql/reference/queries": "/en/enterprise/2.17/user/graphql/reference/queries", - "/enterprise/2.17/user/graphql/reference/queries": "/en/enterprise/2.17/user/graphql/reference/queries", - "/enterprise/2.17/graphql/reference/queries": "/en/enterprise/2.17/user/graphql/reference/queries", - "/en/enterprise/2.17/graphql/reference/scalars": "/en/enterprise/2.17/user/graphql/reference/scalars", - "/enterprise/2.17/user/graphql/reference/scalars": "/en/enterprise/2.17/user/graphql/reference/scalars", - "/enterprise/2.17/graphql/reference/scalars": "/en/enterprise/2.17/user/graphql/reference/scalars", - "/en/enterprise/2.17/graphql/reference/unions": "/en/enterprise/2.17/user/graphql/reference/unions", - "/enterprise/2.17/user/graphql/reference/unions": "/en/enterprise/2.17/user/graphql/reference/unions", - "/enterprise/2.17/graphql/reference/unions": "/en/enterprise/2.17/user/graphql/reference/unions", - "/en/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/en/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/en/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/en/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/en/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/en/enterprise/2.17/insights": "/en/enterprise/2.17/user/insights", - "/enterprise/2.17/user/insights": "/en/enterprise/2.17/user/insights", - "/enterprise/2.17/insights": "/en/enterprise/2.17/user/insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/en/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/en/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/en/enterprise/2.17/rest": "/en/enterprise/2.17/user/rest", - "/enterprise/2.17/user/rest": "/en/enterprise/2.17/user/rest", - "/enterprise/2.17/rest": "/en/enterprise/2.17/user/rest", - "/en/enterprise/2.17/rest/reference/activity": "/en/enterprise/2.17/user/rest/reference/activity", - "/enterprise/2.17/user/rest/reference/activity": "/en/enterprise/2.17/user/rest/reference/activity", - "/enterprise/2.17/rest/reference/activity": "/en/enterprise/2.17/user/rest/reference/activity", - "/en/enterprise/2.17/rest/reference/apps": "/en/enterprise/2.17/user/rest/reference/apps", - "/enterprise/2.17/user/rest/reference/apps": "/en/enterprise/2.17/user/rest/reference/apps", - "/enterprise/2.17/rest/reference/apps": "/en/enterprise/2.17/user/rest/reference/apps", - "/en/enterprise/2.17/rest/reference/checks": "/en/enterprise/2.17/user/rest/reference/checks", - "/enterprise/2.17/user/rest/reference/checks": "/en/enterprise/2.17/user/rest/reference/checks", - "/enterprise/2.17/rest/reference/checks": "/en/enterprise/2.17/user/rest/reference/checks", - "/en/enterprise/2.17/rest/reference/codes-of-conduct": "/en/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/enterprise/2.17/user/rest/reference/codes-of-conduct": "/en/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/enterprise/2.17/rest/reference/codes-of-conduct": "/en/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/en/enterprise/2.17/rest/reference/emojis": "/en/enterprise/2.17/user/rest/reference/emojis", - "/enterprise/2.17/user/rest/reference/emojis": "/en/enterprise/2.17/user/rest/reference/emojis", - "/enterprise/2.17/rest/reference/emojis": "/en/enterprise/2.17/user/rest/reference/emojis", - "/en/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/en/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps": "/en/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/en/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/en/enterprise/2.17/rest/reference/enterprise-admin": "/en/enterprise/2.17/user/rest/reference/enterprise-admin", - "/enterprise/2.17/user/rest/reference/enterprise-admin": "/en/enterprise/2.17/user/rest/reference/enterprise-admin", - "/enterprise/2.17/rest/reference/enterprise-admin": "/en/enterprise/2.17/user/rest/reference/enterprise-admin", - "/en/enterprise/2.17/rest/reference/gists": "/en/enterprise/2.17/user/rest/reference/gists", - "/enterprise/2.17/user/rest/reference/gists": "/en/enterprise/2.17/user/rest/reference/gists", - "/enterprise/2.17/rest/reference/gists": "/en/enterprise/2.17/user/rest/reference/gists", - "/en/enterprise/2.17/rest/reference/git": "/en/enterprise/2.17/user/rest/reference/git", - "/enterprise/2.17/user/rest/reference/git": "/en/enterprise/2.17/user/rest/reference/git", - "/enterprise/2.17/rest/reference/git": "/en/enterprise/2.17/user/rest/reference/git", - "/en/enterprise/2.17/rest/reference/gitignore": "/en/enterprise/2.17/user/rest/reference/gitignore", - "/enterprise/2.17/user/rest/reference/gitignore": "/en/enterprise/2.17/user/rest/reference/gitignore", - "/enterprise/2.17/rest/reference/gitignore": "/en/enterprise/2.17/user/rest/reference/gitignore", - "/en/enterprise/2.17/rest/reference": "/en/enterprise/2.17/user/rest/reference", - "/enterprise/2.17/user/rest/reference": "/en/enterprise/2.17/user/rest/reference", - "/enterprise/2.17/rest/reference": "/en/enterprise/2.17/user/rest/reference", - "/en/enterprise/2.17/rest/reference/issues": "/en/enterprise/2.17/user/rest/reference/issues", - "/enterprise/2.17/user/rest/reference/issues": "/en/enterprise/2.17/user/rest/reference/issues", - "/enterprise/2.17/rest/reference/issues": "/en/enterprise/2.17/user/rest/reference/issues", - "/en/enterprise/2.17/rest/reference/licenses": "/en/enterprise/2.17/user/rest/reference/licenses", - "/enterprise/2.17/user/rest/reference/licenses": "/en/enterprise/2.17/user/rest/reference/licenses", - "/enterprise/2.17/rest/reference/licenses": "/en/enterprise/2.17/user/rest/reference/licenses", - "/en/enterprise/2.17/rest/reference/markdown": "/en/enterprise/2.17/user/rest/reference/markdown", - "/enterprise/2.17/user/rest/reference/markdown": "/en/enterprise/2.17/user/rest/reference/markdown", - "/enterprise/2.17/rest/reference/markdown": "/en/enterprise/2.17/user/rest/reference/markdown", - "/en/enterprise/2.17/rest/reference/meta": "/en/enterprise/2.17/user/rest/reference/meta", - "/enterprise/2.17/user/rest/reference/meta": "/en/enterprise/2.17/user/rest/reference/meta", - "/enterprise/2.17/rest/reference/meta": "/en/enterprise/2.17/user/rest/reference/meta", - "/en/enterprise/2.17/rest/reference/oauth-authorizations": "/en/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/enterprise/2.17/user/rest/reference/oauth-authorizations": "/en/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/enterprise/2.17/rest/reference/oauth-authorizations": "/en/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/en/enterprise/2.17/rest/reference/orgs": "/en/enterprise/2.17/user/rest/reference/orgs", - "/enterprise/2.17/user/rest/reference/orgs": "/en/enterprise/2.17/user/rest/reference/orgs", - "/enterprise/2.17/rest/reference/orgs": "/en/enterprise/2.17/user/rest/reference/orgs", - "/en/enterprise/2.17/rest/reference/projects": "/en/enterprise/2.17/user/rest/reference/projects", - "/enterprise/2.17/user/rest/reference/projects": "/en/enterprise/2.17/user/rest/reference/projects", - "/enterprise/2.17/rest/reference/projects": "/en/enterprise/2.17/user/rest/reference/projects", - "/en/enterprise/2.17/rest/reference/pulls": "/en/enterprise/2.17/user/rest/reference/pulls", - "/enterprise/2.17/user/rest/reference/pulls": "/en/enterprise/2.17/user/rest/reference/pulls", - "/enterprise/2.17/rest/reference/pulls": "/en/enterprise/2.17/user/rest/reference/pulls", - "/en/enterprise/2.17/rest/reference/rate-limit": "/en/enterprise/2.17/user/rest/reference/rate-limit", - "/enterprise/2.17/user/rest/reference/rate-limit": "/en/enterprise/2.17/user/rest/reference/rate-limit", - "/enterprise/2.17/rest/reference/rate-limit": "/en/enterprise/2.17/user/rest/reference/rate-limit", - "/en/enterprise/2.17/rest/reference/reactions": "/en/enterprise/2.17/user/rest/reference/reactions", - "/enterprise/2.17/user/rest/reference/reactions": "/en/enterprise/2.17/user/rest/reference/reactions", - "/enterprise/2.17/rest/reference/reactions": "/en/enterprise/2.17/user/rest/reference/reactions", - "/en/enterprise/2.17/rest/reference/repos": "/en/enterprise/2.17/user/rest/reference/repos", - "/enterprise/2.17/user/rest/reference/repos": "/en/enterprise/2.17/user/rest/reference/repos", - "/enterprise/2.17/rest/reference/repos": "/en/enterprise/2.17/user/rest/reference/repos", - "/en/enterprise/2.17/rest/reference/search": "/en/enterprise/2.17/user/rest/reference/search", - "/enterprise/2.17/user/rest/reference/search": "/en/enterprise/2.17/user/rest/reference/search", - "/enterprise/2.17/rest/reference/search": "/en/enterprise/2.17/user/rest/reference/search", - "/en/enterprise/2.17/rest/reference/teams": "/en/enterprise/2.17/user/rest/reference/teams", - "/enterprise/2.17/user/rest/reference/teams": "/en/enterprise/2.17/user/rest/reference/teams", - "/enterprise/2.17/rest/reference/teams": "/en/enterprise/2.17/user/rest/reference/teams", - "/en/enterprise/2.17/rest/reference/users": "/en/enterprise/2.17/user/rest/reference/users", - "/enterprise/2.17/user/rest/reference/users": "/en/enterprise/2.17/user/rest/reference/users", - "/enterprise/2.17/rest/reference/users": "/en/enterprise/2.17/user/rest/reference/users", - "/es/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/es/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/es/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/es/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/es/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/es/enterprise/2.17/admin/articles/using-github-task-runner", - "/es/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/es/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/es/enterprise/2.17/admin/guides/clustering/about-clustering": "/es/enterprise/2.17/admin/clustering/about-clustering", - "/es/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/es/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/es/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/es/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/es/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/es/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/es/enterprise/2.17/admin/guides/clustering": "/es/enterprise/2.17/admin/clustering", - "/es/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/es/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/es/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/es/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/es/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/es/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/es/enterprise/2.17/admin/guides/clustering/overview": "/es/enterprise/2.17/admin/clustering/overview", - "/es/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/es/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/es/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/es/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/es/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/es/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/es/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/es/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/es/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/es/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/es/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/es/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/es/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/es/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/es/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/es/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/es/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/es/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/es/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/es/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/es/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/es/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/es/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/es/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/es/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/es/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/es/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/es/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/es/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/es/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/es/enterprise/2.17/admin/guides/developer-workflow": "/es/enterprise/2.17/admin/developer-workflow", - "/es/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/es/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/es/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/es/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/es/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/es/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/es/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/es/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/es/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/es/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/es/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/es/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/es/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/es/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/es/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/es/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/es/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/es/enterprise/2.17/admin/guides/enterprise-support": "/es/enterprise/2.17/admin/enterprise-support", - "/es/enterprise/2.17/admin/guides/enterprise-support/overview": "/es/enterprise/2.17/admin/enterprise-support/overview", - "/es/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/es/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/es/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/es/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/es/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/es/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/es/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/es/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/es/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/es/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/es/enterprise/2.17/admin/guides": "/es/enterprise/2.17/admin", - "/es/enterprise/2.17/admin/guides/installation/about-geo-replication": "/es/enterprise/2.17/admin/installation/about-geo-replication", - "/es/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/es/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/es/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/es/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/es/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/es/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/es/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/es/enterprise/2.17/admin/installation/accessing-the-management-console", - "/es/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/es/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/es/enterprise/2.17/admin/guides/installation/activity-dashboard": "/es/enterprise/2.17/admin/installation/activity-dashboard", - "/es/enterprise/2.17/admin/guides/installation/audit-logging": "/es/enterprise/2.17/admin/installation/audit-logging", - "/es/enterprise/2.17/admin/guides/installation/audited-actions": "/es/enterprise/2.17/admin/installation/audited-actions", - "/es/enterprise/2.17/admin/guides/installation/command-line-utilities": "/es/enterprise/2.17/admin/installation/command-line-utilities", - "/es/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/es/enterprise/2.17/admin/installation/configuring-a-hostname", - "/es/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/es/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/es/enterprise/2.17/admin/guides/installation/configuring-applications": "/es/enterprise/2.17/admin/installation/configuring-applications", - "/es/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/es/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/es/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/es/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/es/enterprise/2.17/admin/guides/installation/configuring-collectd": "/es/enterprise/2.17/admin/installation/configuring-collectd", - "/es/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/es/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/es/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/es/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/es/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/es/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/es/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/es/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/es/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/es/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/es/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/es/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/es/enterprise/2.17/admin/installation/configuring-rate-limits", - "/es/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/es/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/es/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/es/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/es/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/es/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/es/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/es/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/es/enterprise/2.17/admin/guides/installation/configuring-tls": "/es/enterprise/2.17/admin/installation/configuring-tls", - "/es/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/es/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/es/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/es/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/es/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/es/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/es/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/es/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/es/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/es/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/es/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/es/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/es/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/es/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/es/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/es/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/es/enterprise/2.17/admin/installation/enabling-private-mode", - "/es/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/es/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/es/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/es/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/es/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/es/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/es/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/es/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/es/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/es/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/es/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/es/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/es/enterprise/2.17/admin/guides/installation": "/es/enterprise/2.17/admin/installation", - "/es/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/es/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/es/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/es/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/es/enterprise/2.17/admin/guides/installation/log-forwarding": "/es/enterprise/2.17/admin/installation/log-forwarding", - "/es/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/es/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/es/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/es/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/es/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/es/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/es/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/es/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/es/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/es/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/es/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/es/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/es/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/es/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/es/enterprise/2.17/admin/guides/installation/network-ports": "/es/enterprise/2.17/admin/installation/network-ports", - "/es/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/es/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/es/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/es/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/es/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/es/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/es/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/es/enterprise/2.17/admin/installation/searching-the-audit-log", - "/es/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/es/enterprise/2.17/admin/installation/setting-git-push-limits", - "/es/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/es/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/es/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/es/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/es/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/es/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/es/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/es/enterprise/2.17/admin/installation/site-admin-dashboard", - "/es/enterprise/2.17/admin/guides/installation/system-overview": "/es/enterprise/2.17/admin/installation/system-overview", - "/es/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/es/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/es/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/es/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/es/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/es/enterprise/2.17/admin/installation/upgrade-requirements", - "/es/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/es/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/es/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/es/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/es/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/es/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/es/enterprise/2.17/admin/installation/viewing-push-logs", - "/es/enterprise/2.17/admin/guides/migrations/about-migrations": "/es/enterprise/2.17/admin/migrations/about-migrations", - "/es/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/es/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/es/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/es/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/es/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/es/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/es/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/es/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/es/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/es/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/es/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/es/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/es/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/es/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/es/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/migrations": "/es/enterprise/2.17/admin/migrations", - "/es/enterprise/2.17/admin/guides/migrations/overview": "/es/enterprise/2.17/admin/migrations/overview", - "/es/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/es/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/es/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/es/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/es/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/es/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/es/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/es/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/es/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/es/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/es/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/es/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/es/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/es/enterprise/2.17/admin/user-management/about-global-webhooks", - "/es/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/es/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/es/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/es/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/es/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/es/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/es/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/es/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/es/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/es/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/es/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/es/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/es/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/es/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/es/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/es/enterprise/2.17/admin/user-management/basic-account-settings", - "/es/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/es/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/es/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/es/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/es/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/es/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/es/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/es/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/es/enterprise/2.17/admin/guides/user-management/creating-organizations": "/es/enterprise/2.17/admin/user-management/creating-organizations", - "/es/enterprise/2.17/admin/guides/user-management/creating-teams": "/es/enterprise/2.17/admin/user-management/creating-teams", - "/es/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/es/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/es/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/es/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/es/enterprise/2.17/admin/guides/user-management": "/es/enterprise/2.17/admin/user-management", - "/es/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/es/enterprise/2.17/admin/user-management/managing-dormant-users", - "/es/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/es/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/es/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/es/enterprise/2.17/admin/user-management/organizations-and-teams", - "/es/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/es/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/es/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/es/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/es/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/es/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/es/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/es/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/es/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/es/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/es/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/es/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/es/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/es/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/es/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/es/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/es/enterprise/2.17/admin/guides/user-management/repositories": "/es/enterprise/2.17/admin/user-management/repositories", - "/es/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/es/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/es/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/es/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/es/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/es/enterprise/2.17/admin/guides/user-management/user-security": "/es/enterprise/2.17/admin/user-management/user-security", - "/es/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/es/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/es/enterprise/2.17/admin/guides/user-management/using-cas": "/es/enterprise/2.17/admin/user-management/using-cas", - "/es/enterprise/2.17/admin/guides/user-management/using-ldap": "/es/enterprise/2.17/admin/user-management/using-ldap", - "/es/enterprise/2.17/admin/guides/user-management/using-saml": "/es/enterprise/2.17/admin/user-management/using-saml", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/es/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/es/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/es/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/es/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/es/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/es/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/es/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/es/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/es/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/es/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/es/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/es/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/es/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/es/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/es/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/es/enterprise/2.17/user/administering-a-repository/about-releases": "/es/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/es/enterprise/2.17/github/administering-a-repository/about-releases": "/es/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/es/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/es/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/es/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/es/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/es/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/es/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/es/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/es/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/es/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/es/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/es/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/es/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/es/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/es/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/es/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/es/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/es/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/es/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/es/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/es/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/es/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/es/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/es/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/es/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/es/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/es/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/es/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/es/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/es/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/es/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository", - "/es/enterprise/2.17/user/administering-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository", - "/es/enterprise/2.17/github/administering-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/es/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/es/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/es/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/es/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/es/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/es/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/es/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/es/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/es/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/es/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/es/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/es/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/es/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/es/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/es/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/es/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/es/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/es/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/es/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/es/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/es/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/es/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/es/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/es/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/es/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/es/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/es/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/es/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/es/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/es/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/es/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/es/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/es/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/es/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/es/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/es/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/es/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/es/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/es/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/es/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/es/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/es/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/es/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/es/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/es/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/es/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/es/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/es/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/es/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/es/enterprise/2.17/user/authenticating-to-github/about-ssh": "/es/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/es/enterprise/2.17/github/authenticating-to-github/about-ssh": "/es/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/es/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/es/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/es/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/es/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/es/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/es/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/es/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/es/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/es/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/es/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/es/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/es/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/es/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/es/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/es/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/es/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/es/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/es/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/es/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/es/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/es/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/es/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/es/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/es/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/es/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/es/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/es/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/es/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/es/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/es/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/es/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/es/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/es/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/es/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/es/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/es/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/es/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/es/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/es/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/es/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/es/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/es/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/es/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/es/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/es/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/es/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/es/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/es/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/es/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/es/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/es/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/es/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/es/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/es/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/es/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/es/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/es/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/es/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/es/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/es/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/es/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/es/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/es/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/es/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/es/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/es/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/es/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/es/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/es/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/es/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/es/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/es/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/es/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/es/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/es/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/es/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/es/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/es/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/es/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/es/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/es/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/es/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/es/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/es/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/es/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/es/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/es/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/es/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/es/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/es/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/es/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/es/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/es/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/es/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/es/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/es/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/es/enterprise/2.17/user/authenticating-to-github": "/es/enterprise/2.17/user/github/authenticating-to-github", - "/es/enterprise/2.17/github/authenticating-to-github": "/es/enterprise/2.17/user/github/authenticating-to-github", - "/es/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/es/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/es/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/es/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/es/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/es/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/es/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/es/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/es/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/es/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/es/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/es/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/es/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/es/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/es/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/es/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/es/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/es/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/es/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/es/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/es/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/es/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/es/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/es/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/es/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/es/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/es/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/es/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/es/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/es/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/es/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/es/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/es/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/es/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/es/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/es/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/es/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/es/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/es/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/es/enterprise/2.17/user/authenticating-to-github/signing-commits": "/es/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/es/enterprise/2.17/github/authenticating-to-github/signing-commits": "/es/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/es/enterprise/2.17/user/authenticating-to-github/signing-tags": "/es/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/es/enterprise/2.17/github/authenticating-to-github/signing-tags": "/es/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/es/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/es/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/es/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/es/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/es/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/es/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/es/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/es/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/es/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/es/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/es/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/es/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/es/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/es/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/es/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/es/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/es/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/es/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/es/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/es/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/es/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/es/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/es/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/es/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/es/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/es/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/es/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/es/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/es/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/es/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/es/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/es/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/es/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/es/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/es/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/es/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/es/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/es/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/es/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/es/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/es/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/es/enterprise/2.17/user/building-a-strong-community/about-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/es/enterprise/2.17/github/building-a-strong-community/about-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/es/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/es/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/es/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/es/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/es/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/es/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/es/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/es/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/es/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/es/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/es/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/es/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/es/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/es/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/es/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/es/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/es/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/es/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/es/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/es/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/es/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/es/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/es/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/es/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/es/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/es/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/es/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/es/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/es/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/es/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/es/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/es/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/es/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/es/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/es/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/es/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/es/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/es/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/es/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/es/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/es/enterprise/2.17/user/building-a-strong-community": "/es/enterprise/2.17/user/github/building-a-strong-community", - "/es/enterprise/2.17/github/building-a-strong-community": "/es/enterprise/2.17/user/github/building-a-strong-community", - "/es/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/es/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/es/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/es/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/es/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/es/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/es/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/es/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/es/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/es/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/es/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/es/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/es/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/es/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/es/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/es/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/es/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/es/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/es/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/es/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/es/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/es/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/es/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/es/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/es/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/es/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/es/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/es/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/es/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/es/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/es/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/es/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/es/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/es/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/es/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/es/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/es/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/es/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/es/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/es/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/es/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/es/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/es/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/es/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/es/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/es/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/es/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/es/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/es/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/es/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/es/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/es/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/es/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/es/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/es/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/es/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/es/enterprise/2.17/user/committing-changes-to-your-project": "/es/enterprise/2.17/user/github/committing-changes-to-your-project", - "/es/enterprise/2.17/github/committing-changes-to-your-project": "/es/enterprise/2.17/user/github/committing-changes-to-your-project", - "/es/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/es/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/es/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/es/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/es/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/es/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/es/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/es/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/es/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/es/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/es/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/es/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/es/enterprise/2.17/user/extending-github/about-webhooks": "/es/enterprise/2.17/user/github/extending-github/about-webhooks", - "/es/enterprise/2.17/github/extending-github/about-webhooks": "/es/enterprise/2.17/user/github/extending-github/about-webhooks", - "/es/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/es/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/es/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/es/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/es/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/es/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/es/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/es/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/es/enterprise/2.17/user/extending-github": "/es/enterprise/2.17/user/github/extending-github", - "/es/enterprise/2.17/github/extending-github": "/es/enterprise/2.17/user/github/extending-github", - "/es/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/es/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/es/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/es/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/es/enterprise/2.17/user/getting-started-with-github/be-social": "/es/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/es/enterprise/2.17/github/getting-started-with-github/be-social": "/es/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/es/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/es/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/es/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/es/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/es/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/es/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/es/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/es/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/es/enterprise/2.17/user/getting-started-with-github/following-people": "/es/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/es/enterprise/2.17/github/getting-started-with-github/following-people": "/es/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/es/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/es/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/es/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/es/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/es/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/es/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/es/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/es/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/es/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/es/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/es/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/es/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/es/enterprise/2.17/user/getting-started-with-github/github-desktop": "/es/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/es/enterprise/2.17/github/getting-started-with-github/github-desktop": "/es/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/es/enterprise/2.17/user/getting-started-with-github/github-glossary": "/es/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/es/enterprise/2.17/github/getting-started-with-github/github-glossary": "/es/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/es/enterprise/2.17/user/getting-started-with-github/githubs-products": "/es/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/es/enterprise/2.17/github/getting-started-with-github/githubs-products": "/es/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/es/enterprise/2.17/user/getting-started-with-github": "/es/enterprise/2.17/user/github/getting-started-with-github", - "/es/enterprise/2.17/github/getting-started-with-github": "/es/enterprise/2.17/user/github/getting-started-with-github", - "/es/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/es/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/es/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/es/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/es/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/es/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/es/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/es/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/es/enterprise/2.17/user/getting-started-with-github/quickstart": "/es/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/es/enterprise/2.17/github/getting-started-with-github/quickstart": "/es/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/es/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/es/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/es/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/es/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/es/enterprise/2.17/user/getting-started-with-github/set-up-git": "/es/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/es/enterprise/2.17/github/getting-started-with-github/set-up-git": "/es/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/es/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/es/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/es/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/es/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/es/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/es/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/es/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/es/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/es/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/es/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/es/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/es/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/es/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/es/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/es/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/es/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/es/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/es/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/es/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/es/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/es/enterprise/2.17/user/getting-started-with-github/using-github": "/es/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/es/enterprise/2.17/github/getting-started-with-github/using-github": "/es/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/es/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/es/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/es/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/es/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/es/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/es/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/es/enterprise/2.17/user/importing-your-projects-to-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github", - "/es/enterprise/2.17/github/importing-your-projects-to-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github", - "/es/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/es/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/es/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/es/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/es/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/es/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/es/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/es/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/es/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/es/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/es/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/es/enterprise/2.17/user": "/es/enterprise/2.17/user/github", - "/es/enterprise/2.17/github": "/es/enterprise/2.17/user/github", - "/es/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/es/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/es/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/es/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/es/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/es/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/es/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/es/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/es/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/es/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/es/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/es/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/es/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/es/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/es/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/es/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/es/enterprise/2.17/user/managing-files-in-a-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository", - "/es/enterprise/2.17/github/managing-files-in-a-repository": "/es/enterprise/2.17/user/github/managing-files-in-a-repository", - "/es/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/es/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/es/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/es/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/es/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/es/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/es/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/es/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/es/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/es/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/es/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/es/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/es/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/es/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/es/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/es/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/es/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/es/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/es/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/es/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/es/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/es/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/es/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/es/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/es/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/es/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/es/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/es/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/es/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/es/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/es/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/es/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/es/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/es/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/es/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/es/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/es/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/es/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/es/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/es/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/es/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/es/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/es/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/es/enterprise/2.17/user/managing-large-files": "/es/enterprise/2.17/user/github/managing-large-files", - "/es/enterprise/2.17/github/managing-large-files": "/es/enterprise/2.17/user/github/managing-large-files", - "/es/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/es/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/es/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/es/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/es/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/es/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/es/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/es/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/es/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/es/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/es/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/es/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/es/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/es/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/es/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/es/enterprise/2.17/user/managing-large-files/versioning-large-files": "/es/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/es/enterprise/2.17/github/managing-large-files/versioning-large-files": "/es/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/es/enterprise/2.17/user/managing-large-files/working-with-large-files": "/es/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/es/enterprise/2.17/github/managing-large-files/working-with-large-files": "/es/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/es/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/es/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/es/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/es/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/es/enterprise/2.17/user/managing-security-vulnerabilities": "/es/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/es/enterprise/2.17/github/managing-security-vulnerabilities": "/es/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/es/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/es/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/es/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/es/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/es/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/es/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/es/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/es/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/es/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/es/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/es/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/es/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/es/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/es/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/es/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/es/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/es/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/es/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/es/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/es/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/es/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/es/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/es/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/es/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/es/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/es/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/es/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/es/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/es/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/es/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/es/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/es/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/es/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/es/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/es/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/es/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/es/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/es/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/es/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/es/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/es/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/es/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/es/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/es/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/es/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/es/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/es/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/es/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/es/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/es/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/es/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/es/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/es/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/es/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/es/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/es/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/es/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/es/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/es/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/es/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/es/enterprise/2.17/user/managing-your-work-on-github": "/es/enterprise/2.17/user/github/managing-your-work-on-github", - "/es/enterprise/2.17/github/managing-your-work-on-github": "/es/enterprise/2.17/user/github/managing-your-work-on-github", - "/es/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/es/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/es/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/es/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/es/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/es/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/es/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/es/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/es/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/es/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/es/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/es/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/es/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/es/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/es/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/es/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/es/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/es/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/es/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/es/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/es/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/es/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/es/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/es/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/es/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/es/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/es/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/es/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/es/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/es/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/es/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/es/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/es/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/es/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/es/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/es/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/es/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/es/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/es/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/es/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/es/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/es/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/es/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/es/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/es/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/es/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/es/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/es/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/es/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/es/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/es/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/es/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/es/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/es/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/es/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/es/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/es/enterprise/2.17/user/searching-for-information-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github", - "/es/enterprise/2.17/github/searching-for-information-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/es/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/es/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/es/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/es/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/es/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/es/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/es/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/es/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/es/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/es/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/es/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/es/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/es/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/es/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/es/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/es/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/es/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/es/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/es/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/es/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/es/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/es/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/es/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/es/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/es/enterprise/2.17/user/using-git/about-git-rebase": "/es/enterprise/2.17/user/github/using-git/about-git-rebase", - "/es/enterprise/2.17/github/using-git/about-git-rebase": "/es/enterprise/2.17/user/github/using-git/about-git-rebase", - "/es/enterprise/2.17/user/using-git/about-git-subtree-merges": "/es/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/es/enterprise/2.17/github/using-git/about-git-subtree-merges": "/es/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/es/enterprise/2.17/user/using-git/about-remote-repositories": "/es/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/es/enterprise/2.17/github/using-git/about-remote-repositories": "/es/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/es/enterprise/2.17/user/using-git/adding-a-remote": "/es/enterprise/2.17/user/github/using-git/adding-a-remote", - "/es/enterprise/2.17/github/using-git/adding-a-remote": "/es/enterprise/2.17/user/github/using-git/adding-a-remote", - "/es/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/es/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/es/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/es/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/es/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/es/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/es/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/es/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/es/enterprise/2.17/user/using-git/changing-a-remotes-url": "/es/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/es/enterprise/2.17/github/using-git/changing-a-remotes-url": "/es/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/es/enterprise/2.17/user/using-git/changing-author-info": "/es/enterprise/2.17/user/github/using-git/changing-author-info", - "/es/enterprise/2.17/github/using-git/changing-author-info": "/es/enterprise/2.17/user/github/using-git/changing-author-info", - "/es/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/es/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/es/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/es/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/es/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/es/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/es/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/es/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/es/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/es/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/es/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/es/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/es/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/es/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/es/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/es/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/es/enterprise/2.17/user/using-git/git-workflows": "/es/enterprise/2.17/user/github/using-git/git-workflows", - "/es/enterprise/2.17/github/using-git/git-workflows": "/es/enterprise/2.17/user/github/using-git/git-workflows", - "/es/enterprise/2.17/user/using-git/ignoring-files": "/es/enterprise/2.17/user/github/using-git/ignoring-files", - "/es/enterprise/2.17/github/using-git/ignoring-files": "/es/enterprise/2.17/user/github/using-git/ignoring-files", - "/es/enterprise/2.17/user/using-git": "/es/enterprise/2.17/user/github/using-git", - "/es/enterprise/2.17/github/using-git": "/es/enterprise/2.17/user/github/using-git", - "/es/enterprise/2.17/user/using-git/learning-about-git": "/es/enterprise/2.17/user/github/using-git/learning-about-git", - "/es/enterprise/2.17/github/using-git/learning-about-git": "/es/enterprise/2.17/user/github/using-git/learning-about-git", - "/es/enterprise/2.17/user/using-git/managing-remote-repositories": "/es/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/es/enterprise/2.17/github/using-git/managing-remote-repositories": "/es/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/es/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/es/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/es/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/es/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/es/enterprise/2.17/user/using-git/removing-a-remote": "/es/enterprise/2.17/user/github/using-git/removing-a-remote", - "/es/enterprise/2.17/github/using-git/removing-a-remote": "/es/enterprise/2.17/user/github/using-git/removing-a-remote", - "/es/enterprise/2.17/user/using-git/renaming-a-remote": "/es/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/es/enterprise/2.17/github/using-git/renaming-a-remote": "/es/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/es/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/es/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/es/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/es/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/es/enterprise/2.17/user/using-git/setting-your-username-in-git": "/es/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/es/enterprise/2.17/github/using-git/setting-your-username-in-git": "/es/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/es/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/es/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/es/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/es/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/es/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/es/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/es/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/es/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/es/enterprise/2.17/user/using-git/using-advanced-git-commands": "/es/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/es/enterprise/2.17/github/using-git/using-advanced-git-commands": "/es/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/es/enterprise/2.17/user/using-git/using-common-git-commands": "/es/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/es/enterprise/2.17/github/using-git/using-common-git-commands": "/es/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/es/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/es/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/es/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/es/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/es/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/es/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/es/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/es/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/es/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/es/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/es/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/es/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/es/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/es/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/es/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/es/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/es/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/es/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/es/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/es/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/es/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/es/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/es/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/es/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/es/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/es/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/es/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/es/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/es/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/es/enterprise/2.17/user/working-with-github-pages": "/es/enterprise/2.17/user/github/working-with-github-pages", - "/es/enterprise/2.17/github/working-with-github-pages": "/es/enterprise/2.17/user/github/working-with-github-pages", - "/es/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/es/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/es/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/es/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/es/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/es/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/es/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/es/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/es/enterprise/2.17/user/writing-on-github/about-saved-replies": "/es/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/es/enterprise/2.17/github/writing-on-github/about-saved-replies": "/es/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/es/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/es/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/es/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/es/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/es/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/es/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/es/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/es/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/es/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/es/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/es/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/es/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/es/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/es/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/es/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/es/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/es/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/es/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/es/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/es/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/es/enterprise/2.17/user/writing-on-github/creating-gists": "/es/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/es/enterprise/2.17/github/writing-on-github/creating-gists": "/es/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/es/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/es/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/es/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/es/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/es/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/es/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/es/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/es/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/es/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/es/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/es/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/es/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/es/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/es/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/es/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/es/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/es/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/es/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/es/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/es/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/es/enterprise/2.17/user/writing-on-github": "/es/enterprise/2.17/user/github/writing-on-github", - "/es/enterprise/2.17/github/writing-on-github": "/es/enterprise/2.17/user/github/writing-on-github", - "/es/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/es/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/es/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/es/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/es/enterprise/2.17/user/writing-on-github/using-saved-replies": "/es/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/es/enterprise/2.17/github/writing-on-github/using-saved-replies": "/es/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/es/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/es/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/es/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/es/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/es/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/es/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/es/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/es/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/es/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/es/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/2.17/graphql/guides": "/es/enterprise/2.17/user/graphql/guides", - "/es/enterprise/2.17/graphql/guides/introduction-to-graphql": "/es/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/es/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/es/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/2.17/graphql/guides/using-global-node-ids": "/es/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/es/enterprise/2.17/graphql/guides/using-the-explorer": "/es/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/es/enterprise/2.17/graphql": "/es/enterprise/2.17/user/graphql", - "/es/enterprise/2.17/graphql/overview/about-the-graphql-api": "/es/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/es/enterprise/2.17/graphql/overview/breaking-changes": "/es/enterprise/2.17/user/graphql/overview/breaking-changes", - "/es/enterprise/2.17/graphql/overview/changelog": "/es/enterprise/2.17/user/graphql/overview/changelog", - "/es/enterprise/2.17/graphql/overview/explorer": "/es/enterprise/2.17/user/graphql/overview/explorer", - "/es/enterprise/2.17/graphql/overview": "/es/enterprise/2.17/user/graphql/overview", - "/es/enterprise/2.17/graphql/overview/resource-limitations": "/es/enterprise/2.17/user/graphql/overview/resource-limitations", - "/es/enterprise/2.17/graphql/overview/schema-previews": "/es/enterprise/2.17/user/graphql/overview/schema-previews", - "/es/enterprise/2.17/graphql/reference/enums": "/es/enterprise/2.17/user/graphql/reference/enums", - "/es/enterprise/2.17/graphql/reference": "/es/enterprise/2.17/user/graphql/reference", - "/es/enterprise/2.17/graphql/reference/input-objects": "/es/enterprise/2.17/user/graphql/reference/input-objects", - "/es/enterprise/2.17/graphql/reference/interfaces": "/es/enterprise/2.17/user/graphql/reference/interfaces", - "/es/enterprise/2.17/graphql/reference/mutations": "/es/enterprise/2.17/user/graphql/reference/mutations", - "/es/enterprise/2.17/graphql/reference/objects": "/es/enterprise/2.17/user/graphql/reference/objects", - "/es/enterprise/2.17/graphql/reference/queries": "/es/enterprise/2.17/user/graphql/reference/queries", - "/es/enterprise/2.17/graphql/reference/scalars": "/es/enterprise/2.17/user/graphql/reference/scalars", - "/es/enterprise/2.17/graphql/reference/unions": "/es/enterprise/2.17/user/graphql/reference/unions", - "/es/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/es/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/es/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/es/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/es/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/es/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/es/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/es/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/es/enterprise/2.17/insights": "/es/enterprise/2.17/user/insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/es/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/es/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/es/enterprise/2.17/rest": "/es/enterprise/2.17/user/rest", - "/es/enterprise/2.17/rest/reference/actions": "/es/enterprise/2.17/user/rest/reference/actions", - "/es/enterprise/2.17/rest/reference/activity": "/es/enterprise/2.17/user/rest/reference/activity", - "/es/enterprise/2.17/rest/reference/apps": "/es/enterprise/2.17/user/rest/reference/apps", - "/es/enterprise/2.17/rest/reference/checks": "/es/enterprise/2.17/user/rest/reference/checks", - "/es/enterprise/2.17/rest/reference/codes-of-conduct": "/es/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/es/enterprise/2.17/rest/reference/emojis": "/es/enterprise/2.17/user/rest/reference/emojis", - "/es/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/es/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/es/enterprise/2.17/rest/reference/enterprise-admin": "/es/enterprise/2.17/user/rest/reference/enterprise-admin", - "/es/enterprise/2.17/rest/reference/gists": "/es/enterprise/2.17/user/rest/reference/gists", - "/es/enterprise/2.17/rest/reference/git": "/es/enterprise/2.17/user/rest/reference/git", - "/es/enterprise/2.17/rest/reference/gitignore": "/es/enterprise/2.17/user/rest/reference/gitignore", - "/es/enterprise/2.17/rest/reference": "/es/enterprise/2.17/user/rest/reference", - "/es/enterprise/2.17/rest/reference/interactions": "/es/enterprise/2.17/user/rest/reference/interactions", - "/es/enterprise/2.17/rest/reference/issues": "/es/enterprise/2.17/user/rest/reference/issues", - "/es/enterprise/2.17/rest/reference/licenses": "/es/enterprise/2.17/user/rest/reference/licenses", - "/es/enterprise/2.17/rest/reference/markdown": "/es/enterprise/2.17/user/rest/reference/markdown", - "/es/enterprise/2.17/rest/reference/meta": "/es/enterprise/2.17/user/rest/reference/meta", - "/es/enterprise/2.17/rest/reference/migrations": "/es/enterprise/2.17/user/rest/reference/migrations", - "/es/enterprise/2.17/rest/reference/oauth-authorizations": "/es/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/es/enterprise/2.17/rest/reference/orgs": "/es/enterprise/2.17/user/rest/reference/orgs", - "/es/enterprise/2.17/rest/reference/projects": "/es/enterprise/2.17/user/rest/reference/projects", - "/es/enterprise/2.17/rest/reference/pulls": "/es/enterprise/2.17/user/rest/reference/pulls", - "/es/enterprise/2.17/rest/reference/rate-limit": "/es/enterprise/2.17/user/rest/reference/rate-limit", - "/es/enterprise/2.17/rest/reference/reactions": "/es/enterprise/2.17/user/rest/reference/reactions", - "/es/enterprise/2.17/rest/reference/repos": "/es/enterprise/2.17/user/rest/reference/repos", - "/es/enterprise/2.17/rest/reference/scim": "/es/enterprise/2.17/user/rest/reference/scim", - "/es/enterprise/2.17/rest/reference/search": "/es/enterprise/2.17/user/rest/reference/search", - "/es/enterprise/2.17/rest/reference/teams": "/es/enterprise/2.17/user/rest/reference/teams", - "/es/enterprise/2.17/rest/reference/users": "/es/enterprise/2.17/user/rest/reference/users", - "/ja/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/ja/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/ja/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/ja/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/ja/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/ja/enterprise/2.17/admin/articles/using-github-task-runner", - "/ja/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/ja/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/ja/enterprise/2.17/admin/guides/clustering/about-clustering": "/ja/enterprise/2.17/admin/clustering/about-clustering", - "/ja/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/ja/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/ja/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/ja/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/ja/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/ja/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/ja/enterprise/2.17/admin/guides/clustering": "/ja/enterprise/2.17/admin/clustering", - "/ja/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/ja/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/ja/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/ja/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/ja/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/ja/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/ja/enterprise/2.17/admin/guides/clustering/overview": "/ja/enterprise/2.17/admin/clustering/overview", - "/ja/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/ja/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/ja/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/ja/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/ja/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/ja/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/ja/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/ja/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/ja/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/ja/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/ja/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/ja/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/ja/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/ja/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/ja/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/ja/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/ja/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/ja/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/ja/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/ja/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/ja/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/ja/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/ja/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/ja/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/ja/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/ja/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/ja/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/ja/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/ja/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/ja/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/ja/enterprise/2.17/admin/guides/developer-workflow": "/ja/enterprise/2.17/admin/developer-workflow", - "/ja/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/ja/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/ja/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/ja/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/ja/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/ja/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/ja/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/ja/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/ja/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/ja/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/ja/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/ja/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/ja/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/ja/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/ja/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/ja/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/ja/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/ja/enterprise/2.17/admin/guides/enterprise-support": "/ja/enterprise/2.17/admin/enterprise-support", - "/ja/enterprise/2.17/admin/guides/enterprise-support/overview": "/ja/enterprise/2.17/admin/enterprise-support/overview", - "/ja/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/ja/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/ja/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/ja/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/ja/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/ja/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/ja/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/ja/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/ja/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/ja/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/ja/enterprise/2.17/admin/guides": "/ja/enterprise/2.17/admin", - "/ja/enterprise/2.17/admin/guides/installation/about-geo-replication": "/ja/enterprise/2.17/admin/installation/about-geo-replication", - "/ja/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/ja/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/ja/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/ja/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/ja/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/ja/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/ja/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/ja/enterprise/2.17/admin/installation/accessing-the-management-console", - "/ja/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/ja/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/ja/enterprise/2.17/admin/guides/installation/activity-dashboard": "/ja/enterprise/2.17/admin/installation/activity-dashboard", - "/ja/enterprise/2.17/admin/guides/installation/audit-logging": "/ja/enterprise/2.17/admin/installation/audit-logging", - "/ja/enterprise/2.17/admin/guides/installation/audited-actions": "/ja/enterprise/2.17/admin/installation/audited-actions", - "/ja/enterprise/2.17/admin/guides/installation/command-line-utilities": "/ja/enterprise/2.17/admin/installation/command-line-utilities", - "/ja/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/ja/enterprise/2.17/admin/installation/configuring-a-hostname", - "/ja/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/ja/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/ja/enterprise/2.17/admin/guides/installation/configuring-applications": "/ja/enterprise/2.17/admin/installation/configuring-applications", - "/ja/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/ja/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/ja/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/ja/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/ja/enterprise/2.17/admin/guides/installation/configuring-collectd": "/ja/enterprise/2.17/admin/installation/configuring-collectd", - "/ja/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/ja/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/ja/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/ja/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/ja/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/ja/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/ja/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/ja/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/ja/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/ja/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/ja/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/ja/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/ja/enterprise/2.17/admin/installation/configuring-rate-limits", - "/ja/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/ja/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/ja/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/ja/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/ja/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/ja/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/ja/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/ja/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/ja/enterprise/2.17/admin/guides/installation/configuring-tls": "/ja/enterprise/2.17/admin/installation/configuring-tls", - "/ja/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/ja/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/ja/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/ja/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/ja/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/ja/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/ja/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/ja/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/ja/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/ja/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/ja/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/ja/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/ja/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/ja/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/ja/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/ja/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/ja/enterprise/2.17/admin/installation/enabling-private-mode", - "/ja/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/ja/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/ja/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/ja/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/ja/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/ja/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/ja/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/ja/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/ja/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/ja/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/ja/enterprise/2.17/admin/guides/installation": "/ja/enterprise/2.17/admin/installation", - "/ja/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/ja/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/ja/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/ja/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/ja/enterprise/2.17/admin/guides/installation/log-forwarding": "/ja/enterprise/2.17/admin/installation/log-forwarding", - "/ja/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/ja/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/ja/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/ja/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/ja/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/ja/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/ja/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/ja/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/ja/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/ja/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/ja/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/ja/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/ja/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/ja/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/ja/enterprise/2.17/admin/guides/installation/network-ports": "/ja/enterprise/2.17/admin/installation/network-ports", - "/ja/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/ja/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/ja/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/ja/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/ja/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/ja/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/ja/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/ja/enterprise/2.17/admin/installation/searching-the-audit-log", - "/ja/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/ja/enterprise/2.17/admin/installation/setting-git-push-limits", - "/ja/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/ja/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/ja/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/ja/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/ja/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/ja/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/ja/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/ja/enterprise/2.17/admin/installation/site-admin-dashboard", - "/ja/enterprise/2.17/admin/guides/installation/system-overview": "/ja/enterprise/2.17/admin/installation/system-overview", - "/ja/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/ja/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/ja/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/ja/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/ja/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/ja/enterprise/2.17/admin/installation/upgrade-requirements", - "/ja/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/ja/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/ja/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/ja/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/ja/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/ja/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/ja/enterprise/2.17/admin/installation/viewing-push-logs", - "/ja/enterprise/2.17/admin/guides/migrations/about-migrations": "/ja/enterprise/2.17/admin/migrations/about-migrations", - "/ja/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/ja/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/ja/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/ja/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/ja/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/ja/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/ja/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/ja/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/ja/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/ja/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/ja/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/ja/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/ja/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/ja/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/ja/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/migrations": "/ja/enterprise/2.17/admin/migrations", - "/ja/enterprise/2.17/admin/guides/migrations/overview": "/ja/enterprise/2.17/admin/migrations/overview", - "/ja/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/ja/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/ja/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/ja/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/ja/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/ja/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/ja/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/ja/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/ja/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/ja/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/ja/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/ja/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/ja/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/ja/enterprise/2.17/admin/user-management/about-global-webhooks", - "/ja/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/ja/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/ja/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/ja/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/ja/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/ja/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/ja/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/ja/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/ja/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/ja/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/ja/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/ja/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/ja/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/ja/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/ja/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/ja/enterprise/2.17/admin/user-management/basic-account-settings", - "/ja/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/ja/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/ja/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/ja/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/ja/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/ja/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/ja/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/ja/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/ja/enterprise/2.17/admin/guides/user-management/creating-organizations": "/ja/enterprise/2.17/admin/user-management/creating-organizations", - "/ja/enterprise/2.17/admin/guides/user-management/creating-teams": "/ja/enterprise/2.17/admin/user-management/creating-teams", - "/ja/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/ja/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/ja/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/ja/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/ja/enterprise/2.17/admin/guides/user-management": "/ja/enterprise/2.17/admin/user-management", - "/ja/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/ja/enterprise/2.17/admin/user-management/managing-dormant-users", - "/ja/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/ja/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/ja/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/ja/enterprise/2.17/admin/user-management/organizations-and-teams", - "/ja/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/ja/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/ja/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/ja/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/ja/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/ja/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/ja/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/ja/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/ja/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/ja/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/ja/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/ja/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/ja/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/ja/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/ja/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/ja/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/ja/enterprise/2.17/admin/guides/user-management/repositories": "/ja/enterprise/2.17/admin/user-management/repositories", - "/ja/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/ja/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/ja/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/ja/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/ja/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/ja/enterprise/2.17/admin/guides/user-management/user-security": "/ja/enterprise/2.17/admin/user-management/user-security", - "/ja/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/ja/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/ja/enterprise/2.17/admin/guides/user-management/using-cas": "/ja/enterprise/2.17/admin/user-management/using-cas", - "/ja/enterprise/2.17/admin/guides/user-management/using-ldap": "/ja/enterprise/2.17/admin/user-management/using-ldap", - "/ja/enterprise/2.17/admin/guides/user-management/using-saml": "/ja/enterprise/2.17/admin/user-management/using-saml", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/ja/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/ja/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/ja/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/ja/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/ja/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/ja/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/ja/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/ja/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/ja/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/ja/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/ja/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/ja/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/ja/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/ja/enterprise/2.17/user/administering-a-repository/about-releases": "/ja/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/ja/enterprise/2.17/github/administering-a-repository/about-releases": "/ja/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/ja/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/ja/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/ja/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/ja/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/ja/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/ja/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/ja/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/ja/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/ja/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/ja/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/ja/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/ja/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/ja/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/ja/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/ja/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/ja/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/ja/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/ja/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/ja/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/ja/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/ja/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/ja/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/ja/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/ja/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/ja/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/ja/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/ja/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/ja/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository", - "/ja/enterprise/2.17/user/administering-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository", - "/ja/enterprise/2.17/github/administering-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/ja/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/ja/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/ja/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/ja/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/ja/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/ja/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/ja/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/ja/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/ja/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/ja/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/ja/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/ja/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/ja/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/ja/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/ja/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/ja/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/ja/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/ja/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/ja/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/ja/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/ja/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/ja/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/ja/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/ja/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/ja/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/ja/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/ja/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/ja/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/ja/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/ja/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/ja/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/ja/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/ja/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/ja/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/ja/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/ja/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/ja/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/ja/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/ja/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/ja/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/ja/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/ja/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/ja/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/ja/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/ja/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/ja/enterprise/2.17/user/authenticating-to-github/about-ssh": "/ja/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/ja/enterprise/2.17/github/authenticating-to-github/about-ssh": "/ja/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/ja/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/ja/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/ja/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/ja/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/ja/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/ja/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/ja/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/ja/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/ja/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/ja/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/ja/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/ja/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/ja/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/ja/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/ja/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/ja/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/ja/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/ja/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/ja/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/ja/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/ja/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/ja/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/ja/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/ja/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/ja/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/ja/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/ja/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/ja/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/ja/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/ja/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/ja/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/ja/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/ja/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/ja/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/ja/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/ja/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/ja/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/ja/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/ja/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/ja/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/ja/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/ja/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/ja/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/ja/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/ja/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/ja/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/ja/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/ja/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/ja/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/ja/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/ja/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/ja/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/ja/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/ja/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/ja/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/ja/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/ja/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/ja/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/ja/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/ja/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/ja/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/ja/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/ja/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/ja/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/ja/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/ja/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/ja/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/ja/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/ja/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/ja/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/ja/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/ja/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/ja/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/ja/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/ja/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/ja/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/ja/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/ja/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/ja/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/ja/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/ja/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/ja/enterprise/2.17/user/authenticating-to-github": "/ja/enterprise/2.17/user/github/authenticating-to-github", - "/ja/enterprise/2.17/github/authenticating-to-github": "/ja/enterprise/2.17/user/github/authenticating-to-github", - "/ja/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/ja/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/ja/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/ja/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/ja/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/ja/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/ja/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/ja/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/ja/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/ja/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/ja/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/ja/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/ja/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/ja/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/ja/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/ja/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/ja/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/ja/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/ja/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/ja/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/ja/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/ja/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/ja/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/ja/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/ja/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/ja/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/ja/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/ja/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/ja/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/ja/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/ja/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/ja/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/ja/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/ja/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/ja/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/ja/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/ja/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/ja/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/ja/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/ja/enterprise/2.17/user/authenticating-to-github/signing-commits": "/ja/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/ja/enterprise/2.17/github/authenticating-to-github/signing-commits": "/ja/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/ja/enterprise/2.17/user/authenticating-to-github/signing-tags": "/ja/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/ja/enterprise/2.17/github/authenticating-to-github/signing-tags": "/ja/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/ja/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/ja/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/ja/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/ja/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/ja/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/ja/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/ja/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/ja/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/ja/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/ja/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/ja/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/ja/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/ja/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/ja/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/ja/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/ja/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/ja/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/ja/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/ja/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/ja/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/ja/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/ja/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/ja/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/ja/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/ja/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/ja/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/ja/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/ja/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/ja/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/ja/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/ja/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/ja/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/ja/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/ja/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/ja/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/ja/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/ja/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/ja/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/ja/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/ja/enterprise/2.17/user/building-a-strong-community/about-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/ja/enterprise/2.17/github/building-a-strong-community/about-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/ja/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/ja/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/ja/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/ja/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/ja/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/ja/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/ja/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/ja/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/ja/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/ja/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/ja/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/ja/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/ja/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/ja/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/ja/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/ja/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/ja/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/ja/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/ja/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/ja/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/ja/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/ja/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/ja/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/ja/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/ja/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/ja/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/ja/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/ja/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/ja/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/ja/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/ja/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/ja/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/ja/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/ja/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/ja/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/ja/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/ja/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/ja/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/ja/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/ja/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/ja/enterprise/2.17/user/building-a-strong-community": "/ja/enterprise/2.17/user/github/building-a-strong-community", - "/ja/enterprise/2.17/github/building-a-strong-community": "/ja/enterprise/2.17/user/github/building-a-strong-community", - "/ja/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/ja/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/ja/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/ja/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/ja/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/ja/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/ja/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/ja/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/ja/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/ja/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/ja/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/ja/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/ja/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/ja/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/ja/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/ja/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/ja/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/ja/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/ja/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/ja/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/ja/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/ja/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/ja/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/ja/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/ja/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/ja/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/ja/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/ja/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/ja/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/ja/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/ja/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/ja/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/ja/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/ja/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/ja/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/ja/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/ja/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/ja/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/ja/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/ja/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/ja/enterprise/2.17/user/committing-changes-to-your-project": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project", - "/ja/enterprise/2.17/github/committing-changes-to-your-project": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/ja/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/ja/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/ja/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/ja/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/ja/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/ja/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/ja/enterprise/2.17/user/extending-github/about-webhooks": "/ja/enterprise/2.17/user/github/extending-github/about-webhooks", - "/ja/enterprise/2.17/github/extending-github/about-webhooks": "/ja/enterprise/2.17/user/github/extending-github/about-webhooks", - "/ja/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/ja/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/ja/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/ja/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/ja/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/ja/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/ja/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/ja/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/ja/enterprise/2.17/user/extending-github": "/ja/enterprise/2.17/user/github/extending-github", - "/ja/enterprise/2.17/github/extending-github": "/ja/enterprise/2.17/user/github/extending-github", - "/ja/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/ja/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/ja/enterprise/2.17/user/getting-started-with-github/be-social": "/ja/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/ja/enterprise/2.17/github/getting-started-with-github/be-social": "/ja/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/ja/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/ja/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/ja/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/ja/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/ja/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/ja/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/ja/enterprise/2.17/user/getting-started-with-github/following-people": "/ja/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/ja/enterprise/2.17/github/getting-started-with-github/following-people": "/ja/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/ja/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/ja/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/ja/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/ja/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/ja/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/ja/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/ja/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/ja/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/ja/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/ja/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/ja/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/ja/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/ja/enterprise/2.17/user/getting-started-with-github/github-desktop": "/ja/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/ja/enterprise/2.17/github/getting-started-with-github/github-desktop": "/ja/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/ja/enterprise/2.17/user/getting-started-with-github/github-glossary": "/ja/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/ja/enterprise/2.17/github/getting-started-with-github/github-glossary": "/ja/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/ja/enterprise/2.17/user/getting-started-with-github/githubs-products": "/ja/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/ja/enterprise/2.17/github/getting-started-with-github/githubs-products": "/ja/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/ja/enterprise/2.17/user/getting-started-with-github": "/ja/enterprise/2.17/user/github/getting-started-with-github", - "/ja/enterprise/2.17/github/getting-started-with-github": "/ja/enterprise/2.17/user/github/getting-started-with-github", - "/ja/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/ja/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/ja/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/ja/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/ja/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/ja/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/ja/enterprise/2.17/user/getting-started-with-github/quickstart": "/ja/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/ja/enterprise/2.17/github/getting-started-with-github/quickstart": "/ja/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/ja/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/ja/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/ja/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/ja/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/ja/enterprise/2.17/user/getting-started-with-github/set-up-git": "/ja/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/ja/enterprise/2.17/github/getting-started-with-github/set-up-git": "/ja/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/ja/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/ja/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/ja/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/ja/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/ja/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/ja/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/ja/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/ja/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/ja/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/ja/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/ja/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/ja/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/ja/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/ja/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/ja/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/ja/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/ja/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/ja/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/ja/enterprise/2.17/user/getting-started-with-github/using-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/ja/enterprise/2.17/github/getting-started-with-github/using-github": "/ja/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/ja/enterprise/2.17/user/importing-your-projects-to-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github", - "/ja/enterprise/2.17/github/importing-your-projects-to-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/ja/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/ja/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/ja/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/ja/enterprise/2.17/user": "/ja/enterprise/2.17/user/github", - "/ja/enterprise/2.17/github": "/ja/enterprise/2.17/user/github", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/ja/enterprise/2.17/user/managing-files-in-a-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository", - "/ja/enterprise/2.17/github/managing-files-in-a-repository": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/ja/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/ja/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/ja/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/ja/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/ja/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/ja/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/ja/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/ja/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/ja/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/ja/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/ja/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/ja/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/ja/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/ja/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/ja/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/ja/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/ja/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/ja/enterprise/2.17/user/managing-large-files": "/ja/enterprise/2.17/user/github/managing-large-files", - "/ja/enterprise/2.17/github/managing-large-files": "/ja/enterprise/2.17/user/github/managing-large-files", - "/ja/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/ja/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/ja/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/ja/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/ja/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/ja/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/ja/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/ja/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/ja/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/ja/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/ja/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/ja/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/ja/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/ja/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/ja/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/ja/enterprise/2.17/user/managing-large-files/versioning-large-files": "/ja/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/ja/enterprise/2.17/github/managing-large-files/versioning-large-files": "/ja/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/ja/enterprise/2.17/user/managing-large-files/working-with-large-files": "/ja/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/ja/enterprise/2.17/github/managing-large-files/working-with-large-files": "/ja/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/ja/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/ja/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/ja/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/ja/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/ja/enterprise/2.17/user/managing-security-vulnerabilities": "/ja/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/ja/enterprise/2.17/github/managing-security-vulnerabilities": "/ja/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/ja/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/ja/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/ja/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/ja/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/ja/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/ja/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/ja/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/ja/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/ja/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/ja/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/ja/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/ja/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/ja/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/ja/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/ja/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/ja/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/ja/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/ja/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/ja/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/ja/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/ja/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/ja/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/ja/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/ja/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/ja/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/ja/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/ja/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/ja/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/ja/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/ja/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/ja/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/ja/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/ja/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/ja/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/ja/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/ja/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/ja/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/ja/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/ja/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/ja/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/ja/enterprise/2.17/user/managing-your-work-on-github": "/ja/enterprise/2.17/user/github/managing-your-work-on-github", - "/ja/enterprise/2.17/github/managing-your-work-on-github": "/ja/enterprise/2.17/user/github/managing-your-work-on-github", - "/ja/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/ja/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/ja/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/ja/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/ja/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/ja/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/ja/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/ja/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/ja/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/ja/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/ja/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/ja/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/ja/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/ja/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/ja/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/ja/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/ja/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/ja/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/ja/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/ja/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/ja/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/ja/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/ja/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/ja/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/ja/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/ja/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/ja/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/ja/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/ja/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/ja/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/ja/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/ja/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/ja/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/ja/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/ja/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/ja/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/ja/enterprise/2.17/user/searching-for-information-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github", - "/ja/enterprise/2.17/github/searching-for-information-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/ja/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/ja/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/ja/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/ja/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/ja/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/ja/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/ja/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/ja/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/ja/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/ja/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/ja/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/ja/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/ja/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/ja/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/ja/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/ja/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/ja/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/ja/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/ja/enterprise/2.17/user/using-git/about-git-rebase": "/ja/enterprise/2.17/user/github/using-git/about-git-rebase", - "/ja/enterprise/2.17/github/using-git/about-git-rebase": "/ja/enterprise/2.17/user/github/using-git/about-git-rebase", - "/ja/enterprise/2.17/user/using-git/about-git-subtree-merges": "/ja/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/ja/enterprise/2.17/github/using-git/about-git-subtree-merges": "/ja/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/ja/enterprise/2.17/user/using-git/about-remote-repositories": "/ja/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/ja/enterprise/2.17/github/using-git/about-remote-repositories": "/ja/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/ja/enterprise/2.17/user/using-git/adding-a-remote": "/ja/enterprise/2.17/user/github/using-git/adding-a-remote", - "/ja/enterprise/2.17/github/using-git/adding-a-remote": "/ja/enterprise/2.17/user/github/using-git/adding-a-remote", - "/ja/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/ja/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/ja/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/ja/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/ja/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/ja/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/ja/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/ja/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/ja/enterprise/2.17/user/using-git/changing-a-remotes-url": "/ja/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/ja/enterprise/2.17/github/using-git/changing-a-remotes-url": "/ja/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/ja/enterprise/2.17/user/using-git/changing-author-info": "/ja/enterprise/2.17/user/github/using-git/changing-author-info", - "/ja/enterprise/2.17/github/using-git/changing-author-info": "/ja/enterprise/2.17/user/github/using-git/changing-author-info", - "/ja/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/ja/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/ja/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/ja/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/ja/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/ja/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/ja/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/ja/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/ja/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/ja/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/ja/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/ja/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/ja/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/ja/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/ja/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/ja/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/ja/enterprise/2.17/user/using-git/git-workflows": "/ja/enterprise/2.17/user/github/using-git/git-workflows", - "/ja/enterprise/2.17/github/using-git/git-workflows": "/ja/enterprise/2.17/user/github/using-git/git-workflows", - "/ja/enterprise/2.17/user/using-git/ignoring-files": "/ja/enterprise/2.17/user/github/using-git/ignoring-files", - "/ja/enterprise/2.17/github/using-git/ignoring-files": "/ja/enterprise/2.17/user/github/using-git/ignoring-files", - "/ja/enterprise/2.17/user/using-git": "/ja/enterprise/2.17/user/github/using-git", - "/ja/enterprise/2.17/github/using-git": "/ja/enterprise/2.17/user/github/using-git", - "/ja/enterprise/2.17/user/using-git/learning-about-git": "/ja/enterprise/2.17/user/github/using-git/learning-about-git", - "/ja/enterprise/2.17/github/using-git/learning-about-git": "/ja/enterprise/2.17/user/github/using-git/learning-about-git", - "/ja/enterprise/2.17/user/using-git/managing-remote-repositories": "/ja/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/ja/enterprise/2.17/github/using-git/managing-remote-repositories": "/ja/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/ja/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/ja/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/ja/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/ja/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/ja/enterprise/2.17/user/using-git/removing-a-remote": "/ja/enterprise/2.17/user/github/using-git/removing-a-remote", - "/ja/enterprise/2.17/github/using-git/removing-a-remote": "/ja/enterprise/2.17/user/github/using-git/removing-a-remote", - "/ja/enterprise/2.17/user/using-git/renaming-a-remote": "/ja/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/ja/enterprise/2.17/github/using-git/renaming-a-remote": "/ja/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/ja/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/ja/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/ja/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/ja/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/ja/enterprise/2.17/user/using-git/setting-your-username-in-git": "/ja/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/ja/enterprise/2.17/github/using-git/setting-your-username-in-git": "/ja/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/ja/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/ja/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/ja/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/ja/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/ja/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/ja/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/ja/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/ja/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/ja/enterprise/2.17/user/using-git/using-advanced-git-commands": "/ja/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/ja/enterprise/2.17/github/using-git/using-advanced-git-commands": "/ja/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/ja/enterprise/2.17/user/using-git/using-common-git-commands": "/ja/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/ja/enterprise/2.17/github/using-git/using-common-git-commands": "/ja/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/ja/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/ja/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/ja/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/ja/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/ja/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/ja/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/ja/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/ja/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/ja/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/ja/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/ja/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/ja/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/ja/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/ja/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/ja/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/ja/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/ja/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/ja/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/ja/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/ja/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/ja/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/ja/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/ja/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/ja/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/ja/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/ja/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/ja/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/ja/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/ja/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/ja/enterprise/2.17/user/working-with-github-pages": "/ja/enterprise/2.17/user/github/working-with-github-pages", - "/ja/enterprise/2.17/github/working-with-github-pages": "/ja/enterprise/2.17/user/github/working-with-github-pages", - "/ja/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/ja/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/ja/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/ja/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/ja/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/ja/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/ja/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/ja/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/ja/enterprise/2.17/user/writing-on-github/about-saved-replies": "/ja/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/ja/enterprise/2.17/github/writing-on-github/about-saved-replies": "/ja/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/ja/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/ja/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/ja/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/ja/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/ja/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/ja/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/ja/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/ja/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/ja/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/ja/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/ja/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/ja/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/ja/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/ja/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/ja/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/ja/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/ja/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/ja/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/ja/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/ja/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/ja/enterprise/2.17/user/writing-on-github/creating-gists": "/ja/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/ja/enterprise/2.17/github/writing-on-github/creating-gists": "/ja/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/ja/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/ja/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/ja/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/ja/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/ja/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/ja/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/ja/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/ja/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/ja/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/ja/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/ja/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/ja/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/ja/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/ja/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/ja/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/ja/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/ja/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/ja/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/ja/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/ja/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/ja/enterprise/2.17/user/writing-on-github": "/ja/enterprise/2.17/user/github/writing-on-github", - "/ja/enterprise/2.17/github/writing-on-github": "/ja/enterprise/2.17/user/github/writing-on-github", - "/ja/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/ja/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/ja/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/ja/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/ja/enterprise/2.17/user/writing-on-github/using-saved-replies": "/ja/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/ja/enterprise/2.17/github/writing-on-github/using-saved-replies": "/ja/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/ja/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/ja/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/ja/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/ja/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/ja/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/ja/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/ja/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/ja/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/ja/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/ja/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/2.17/graphql/guides": "/ja/enterprise/2.17/user/graphql/guides", - "/ja/enterprise/2.17/graphql/guides/introduction-to-graphql": "/ja/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/ja/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/ja/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/2.17/graphql/guides/using-global-node-ids": "/ja/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/ja/enterprise/2.17/graphql/guides/using-the-explorer": "/ja/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/ja/enterprise/2.17/graphql": "/ja/enterprise/2.17/user/graphql", - "/ja/enterprise/2.17/graphql/overview/about-the-graphql-api": "/ja/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/ja/enterprise/2.17/graphql/overview/breaking-changes": "/ja/enterprise/2.17/user/graphql/overview/breaking-changes", - "/ja/enterprise/2.17/graphql/overview/changelog": "/ja/enterprise/2.17/user/graphql/overview/changelog", - "/ja/enterprise/2.17/graphql/overview/explorer": "/ja/enterprise/2.17/user/graphql/overview/explorer", - "/ja/enterprise/2.17/graphql/overview": "/ja/enterprise/2.17/user/graphql/overview", - "/ja/enterprise/2.17/graphql/overview/resource-limitations": "/ja/enterprise/2.17/user/graphql/overview/resource-limitations", - "/ja/enterprise/2.17/graphql/overview/schema-previews": "/ja/enterprise/2.17/user/graphql/overview/schema-previews", - "/ja/enterprise/2.17/graphql/reference/enums": "/ja/enterprise/2.17/user/graphql/reference/enums", - "/ja/enterprise/2.17/graphql/reference": "/ja/enterprise/2.17/user/graphql/reference", - "/ja/enterprise/2.17/graphql/reference/input-objects": "/ja/enterprise/2.17/user/graphql/reference/input-objects", - "/ja/enterprise/2.17/graphql/reference/interfaces": "/ja/enterprise/2.17/user/graphql/reference/interfaces", - "/ja/enterprise/2.17/graphql/reference/mutations": "/ja/enterprise/2.17/user/graphql/reference/mutations", - "/ja/enterprise/2.17/graphql/reference/objects": "/ja/enterprise/2.17/user/graphql/reference/objects", - "/ja/enterprise/2.17/graphql/reference/queries": "/ja/enterprise/2.17/user/graphql/reference/queries", - "/ja/enterprise/2.17/graphql/reference/scalars": "/ja/enterprise/2.17/user/graphql/reference/scalars", - "/ja/enterprise/2.17/graphql/reference/unions": "/ja/enterprise/2.17/user/graphql/reference/unions", - "/ja/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/ja/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/ja/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/ja/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/ja/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/ja/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/ja/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/ja/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/ja/enterprise/2.17/insights": "/ja/enterprise/2.17/user/insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/ja/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/ja/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/ja/enterprise/2.17/rest": "/ja/enterprise/2.17/user/rest", - "/ja/enterprise/2.17/rest/reference/actions": "/ja/enterprise/2.17/user/rest/reference/actions", - "/ja/enterprise/2.17/rest/reference/activity": "/ja/enterprise/2.17/user/rest/reference/activity", - "/ja/enterprise/2.17/rest/reference/apps": "/ja/enterprise/2.17/user/rest/reference/apps", - "/ja/enterprise/2.17/rest/reference/checks": "/ja/enterprise/2.17/user/rest/reference/checks", - "/ja/enterprise/2.17/rest/reference/codes-of-conduct": "/ja/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/ja/enterprise/2.17/rest/reference/emojis": "/ja/enterprise/2.17/user/rest/reference/emojis", - "/ja/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/ja/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/ja/enterprise/2.17/rest/reference/enterprise-admin": "/ja/enterprise/2.17/user/rest/reference/enterprise-admin", - "/ja/enterprise/2.17/rest/reference/gists": "/ja/enterprise/2.17/user/rest/reference/gists", - "/ja/enterprise/2.17/rest/reference/git": "/ja/enterprise/2.17/user/rest/reference/git", - "/ja/enterprise/2.17/rest/reference/gitignore": "/ja/enterprise/2.17/user/rest/reference/gitignore", - "/ja/enterprise/2.17/rest/reference": "/ja/enterprise/2.17/user/rest/reference", - "/ja/enterprise/2.17/rest/reference/interactions": "/ja/enterprise/2.17/user/rest/reference/interactions", - "/ja/enterprise/2.17/rest/reference/issues": "/ja/enterprise/2.17/user/rest/reference/issues", - "/ja/enterprise/2.17/rest/reference/licenses": "/ja/enterprise/2.17/user/rest/reference/licenses", - "/ja/enterprise/2.17/rest/reference/markdown": "/ja/enterprise/2.17/user/rest/reference/markdown", - "/ja/enterprise/2.17/rest/reference/meta": "/ja/enterprise/2.17/user/rest/reference/meta", - "/ja/enterprise/2.17/rest/reference/migrations": "/ja/enterprise/2.17/user/rest/reference/migrations", - "/ja/enterprise/2.17/rest/reference/oauth-authorizations": "/ja/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/ja/enterprise/2.17/rest/reference/orgs": "/ja/enterprise/2.17/user/rest/reference/orgs", - "/ja/enterprise/2.17/rest/reference/projects": "/ja/enterprise/2.17/user/rest/reference/projects", - "/ja/enterprise/2.17/rest/reference/pulls": "/ja/enterprise/2.17/user/rest/reference/pulls", - "/ja/enterprise/2.17/rest/reference/rate-limit": "/ja/enterprise/2.17/user/rest/reference/rate-limit", - "/ja/enterprise/2.17/rest/reference/reactions": "/ja/enterprise/2.17/user/rest/reference/reactions", - "/ja/enterprise/2.17/rest/reference/repos": "/ja/enterprise/2.17/user/rest/reference/repos", - "/ja/enterprise/2.17/rest/reference/scim": "/ja/enterprise/2.17/user/rest/reference/scim", - "/ja/enterprise/2.17/rest/reference/search": "/ja/enterprise/2.17/user/rest/reference/search", - "/ja/enterprise/2.17/rest/reference/teams": "/ja/enterprise/2.17/user/rest/reference/teams", - "/ja/enterprise/2.17/rest/reference/users": "/ja/enterprise/2.17/user/rest/reference/users", - "/pt/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/pt/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", - "/pt/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/pt/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", - "/pt/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/pt/enterprise/2.17/admin/articles/using-github-task-runner", - "/pt/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/pt/enterprise/2.17/admin/clustering/about-cluster-nodes", - "/pt/enterprise/2.17/admin/guides/clustering/about-clustering": "/pt/enterprise/2.17/admin/clustering/about-clustering", - "/pt/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/pt/enterprise/2.17/admin/clustering/cluster-network-configuration", - "/pt/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/pt/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", - "/pt/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/pt/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", - "/pt/enterprise/2.17/admin/guides/clustering": "/pt/enterprise/2.17/admin/clustering", - "/pt/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/pt/enterprise/2.17/admin/clustering/initializing-the-cluster", - "/pt/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/pt/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", - "/pt/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/pt/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", - "/pt/enterprise/2.17/admin/guides/clustering/overview": "/pt/enterprise/2.17/admin/clustering/overview", - "/pt/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/pt/enterprise/2.17/admin/clustering/replacing-a-cluster-node", - "/pt/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/pt/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", - "/pt/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/pt/enterprise/2.17/admin/clustering/upgrading-a-cluster", - "/pt/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/pt/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", - "/pt/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/pt/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", - "/pt/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/pt/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", - "/pt/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/pt/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", - "/pt/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/pt/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", - "/pt/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/pt/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", - "/pt/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/pt/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", - "/pt/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/pt/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", - "/pt/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/pt/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", - "/pt/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/pt/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", - "/pt/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/pt/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", - "/pt/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/pt/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", - "/pt/enterprise/2.17/admin/guides/developer-workflow": "/pt/enterprise/2.17/admin/developer-workflow", - "/pt/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/pt/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", - "/pt/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/pt/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", - "/pt/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/pt/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", - "/pt/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/pt/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", - "/pt/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/pt/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", - "/pt/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/pt/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", - "/pt/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/pt/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/pt/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", - "/pt/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/pt/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", - "/pt/enterprise/2.17/admin/guides/enterprise-support": "/pt/enterprise/2.17/admin/enterprise-support", - "/pt/enterprise/2.17/admin/guides/enterprise-support/overview": "/pt/enterprise/2.17/admin/enterprise-support/overview", - "/pt/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/pt/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", - "/pt/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/pt/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", - "/pt/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/pt/enterprise/2.17/admin/enterprise-support/reaching-github-support", - "/pt/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/pt/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", - "/pt/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/pt/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", - "/pt/enterprise/2.17/admin/guides": "/pt/enterprise/2.17/admin", - "/pt/enterprise/2.17/admin/guides/installation/about-geo-replication": "/pt/enterprise/2.17/admin/installation/about-geo-replication", - "/pt/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/pt/enterprise/2.17/admin/installation/about-high-availability-configuration", - "/pt/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/pt/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", - "/pt/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/pt/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", - "/pt/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/pt/enterprise/2.17/admin/installation/accessing-the-management-console", - "/pt/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/pt/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", - "/pt/enterprise/2.17/admin/guides/installation/activity-dashboard": "/pt/enterprise/2.17/admin/installation/activity-dashboard", - "/pt/enterprise/2.17/admin/guides/installation/audit-logging": "/pt/enterprise/2.17/admin/installation/audit-logging", - "/pt/enterprise/2.17/admin/guides/installation/audited-actions": "/pt/enterprise/2.17/admin/installation/audited-actions", - "/pt/enterprise/2.17/admin/guides/installation/command-line-utilities": "/pt/enterprise/2.17/admin/installation/command-line-utilities", - "/pt/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/pt/enterprise/2.17/admin/installation/configuring-a-hostname", - "/pt/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/pt/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", - "/pt/enterprise/2.17/admin/guides/installation/configuring-applications": "/pt/enterprise/2.17/admin/installation/configuring-applications", - "/pt/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/pt/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", - "/pt/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/pt/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", - "/pt/enterprise/2.17/admin/guides/installation/configuring-collectd": "/pt/enterprise/2.17/admin/installation/configuring-collectd", - "/pt/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/pt/enterprise/2.17/admin/installation/configuring-dns-nameservers", - "/pt/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/pt/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/pt/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", - "/pt/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/pt/enterprise/2.17/admin/installation/configuring-git-large-file-storage", - "/pt/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/pt/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", - "/pt/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/pt/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", - "/pt/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/pt/enterprise/2.17/admin/installation/configuring-rate-limits", - "/pt/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/pt/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", - "/pt/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/pt/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", - "/pt/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/pt/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", - "/pt/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/pt/enterprise/2.17/admin/installation/configuring-time-synchronization", - "/pt/enterprise/2.17/admin/guides/installation/configuring-tls": "/pt/enterprise/2.17/admin/installation/configuring-tls", - "/pt/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/pt/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", - "/pt/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/pt/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", - "/pt/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/pt/enterprise/2.17/admin/installation/creating-a-high-availability-replica", - "/pt/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/pt/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/pt/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", - "/pt/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/pt/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", - "/pt/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/pt/enterprise/2.17/admin/installation/enabling-automatic-update-checks", - "/pt/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/pt/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", - "/pt/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/pt/enterprise/2.17/admin/installation/enabling-private-mode", - "/pt/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/pt/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/pt/enterprise/2.17/admin/installation/enabling-subdomain-isolation", - "/pt/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/pt/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", - "/pt/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/pt/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", - "/pt/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/pt/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/pt/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", - "/pt/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/pt/enterprise/2.17/admin/installation/increasing-storage-capacity", - "/pt/enterprise/2.17/admin/guides/installation": "/pt/enterprise/2.17/admin/installation", - "/pt/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/pt/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", - "/pt/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/pt/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", - "/pt/enterprise/2.17/admin/guides/installation/log-forwarding": "/pt/enterprise/2.17/admin/installation/log-forwarding", - "/pt/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/pt/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", - "/pt/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/pt/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", - "/pt/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/pt/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", - "/pt/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/pt/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", - "/pt/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/pt/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", - "/pt/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/pt/enterprise/2.17/admin/installation/monitoring-using-snmp", - "/pt/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/pt/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", - "/pt/enterprise/2.17/admin/guides/installation/network-ports": "/pt/enterprise/2.17/admin/installation/network-ports", - "/pt/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/pt/enterprise/2.17/admin/installation/recommended-alert-thresholds", - "/pt/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/pt/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", - "/pt/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/pt/enterprise/2.17/admin/installation/removing-a-high-availability-replica", - "/pt/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/pt/enterprise/2.17/admin/installation/searching-the-audit-log", - "/pt/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/pt/enterprise/2.17/admin/installation/setting-git-push-limits", - "/pt/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/pt/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", - "/pt/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/pt/enterprise/2.17/admin/installation/setting-up-a-staging-instance", - "/pt/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/pt/enterprise/2.17/admin/installation/setting-up-external-monitoring", - "/pt/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/pt/enterprise/2.17/admin/installation/site-admin-dashboard", - "/pt/enterprise/2.17/admin/guides/installation/system-overview": "/pt/enterprise/2.17/admin/installation/system-overview", - "/pt/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/pt/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", - "/pt/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/pt/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", - "/pt/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/pt/enterprise/2.17/admin/installation/upgrade-requirements", - "/pt/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/pt/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/pt/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", - "/pt/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/pt/enterprise/2.17/admin/installation/validating-your-domain-settings", - "/pt/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/pt/enterprise/2.17/admin/installation/viewing-push-logs", - "/pt/enterprise/2.17/admin/guides/migrations/about-migrations": "/pt/enterprise/2.17/admin/migrations/about-migrations", - "/pt/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/pt/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/pt/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/pt/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/pt/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", - "/pt/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/pt/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", - "/pt/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/pt/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", - "/pt/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/pt/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", - "/pt/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/pt/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", - "/pt/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/pt/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/migrations": "/pt/enterprise/2.17/admin/migrations", - "/pt/enterprise/2.17/admin/guides/migrations/overview": "/pt/enterprise/2.17/admin/migrations/overview", - "/pt/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/pt/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", - "/pt/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/pt/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", - "/pt/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/pt/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", - "/pt/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/pt/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", - "/pt/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/pt/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", - "/pt/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/pt/enterprise/2.17/admin/migrations/reviewing-migration-data", - "/pt/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/pt/enterprise/2.17/admin/user-management/about-global-webhooks", - "/pt/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/pt/enterprise/2.17/admin/user-management/adding-people-to-teams", - "/pt/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/pt/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", - "/pt/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/pt/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", - "/pt/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/pt/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", - "/pt/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/pt/enterprise/2.17/admin/user-management/auditing-ssh-keys", - "/pt/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/pt/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", - "/pt/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/pt/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", - "/pt/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/pt/enterprise/2.17/admin/user-management/basic-account-settings", - "/pt/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/pt/enterprise/2.17/admin/user-management/best-practices-for-user-security", - "/pt/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/pt/enterprise/2.17/admin/user-management/changing-authentication-methods", - "/pt/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/pt/enterprise/2.17/admin/user-management/configuring-email-for-notifications", - "/pt/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/pt/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", - "/pt/enterprise/2.17/admin/guides/user-management/creating-organizations": "/pt/enterprise/2.17/admin/user-management/creating-organizations", - "/pt/enterprise/2.17/admin/guides/user-management/creating-teams": "/pt/enterprise/2.17/admin/user-management/creating-teams", - "/pt/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/pt/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", - "/pt/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/pt/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", - "/pt/enterprise/2.17/admin/guides/user-management": "/pt/enterprise/2.17/admin/user-management", - "/pt/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/pt/enterprise/2.17/admin/user-management/managing-dormant-users", - "/pt/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/pt/enterprise/2.17/admin/user-management/managing-global-webhooks", - "/pt/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/pt/enterprise/2.17/admin/user-management/organizations-and-teams", - "/pt/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/pt/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", - "/pt/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/pt/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", - "/pt/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/pt/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", - "/pt/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/pt/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", - "/pt/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/pt/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", - "/pt/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/pt/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", - "/pt/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/pt/enterprise/2.17/admin/user-management/rebuilding-contributions-data", - "/pt/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/pt/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", - "/pt/enterprise/2.17/admin/guides/user-management/repositories": "/pt/enterprise/2.17/admin/user-management/repositories", - "/pt/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/pt/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", - "/pt/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", - "/pt/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/pt/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", - "/pt/enterprise/2.17/admin/guides/user-management/user-security": "/pt/enterprise/2.17/admin/user-management/user-security", - "/pt/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/pt/enterprise/2.17/admin/user-management/using-built-in-authentication", - "/pt/enterprise/2.17/admin/guides/user-management/using-cas": "/pt/enterprise/2.17/admin/user-management/using-cas", - "/pt/enterprise/2.17/admin/guides/user-management/using-ldap": "/pt/enterprise/2.17/admin/user-management/using-ldap", - "/pt/enterprise/2.17/admin/guides/user-management/using-saml": "/pt/enterprise/2.17/admin/user-management/using-saml", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/pt/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/pt/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/pt/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/pt/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/pt/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/pt/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/pt/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/pt/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/pt/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/pt/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/pt/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/pt/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/pt/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/pt/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/pt/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/pt/enterprise/2.17/user/administering-a-repository/about-releases": "/pt/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/pt/enterprise/2.17/github/administering-a-repository/about-releases": "/pt/enterprise/2.17/user/github/administering-a-repository/about-releases", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/pt/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/pt/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/pt/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/pt/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/pt/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/pt/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/pt/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/pt/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/pt/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/pt/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/pt/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/pt/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/pt/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/pt/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/pt/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/pt/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/pt/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/pt/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/pt/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/pt/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/pt/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/pt/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/pt/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/pt/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/pt/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/pt/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/pt/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/pt/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository", - "/pt/enterprise/2.17/user/administering-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository", - "/pt/enterprise/2.17/github/administering-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/pt/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/pt/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/pt/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/pt/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/pt/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/pt/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/pt/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/pt/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/pt/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/pt/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/pt/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/pt/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/pt/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/pt/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/pt/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/pt/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/pt/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/pt/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/pt/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/pt/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/pt/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/pt/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/pt/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/pt/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/pt/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/pt/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/pt/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/pt/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/pt/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/pt/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/pt/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/pt/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/pt/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/pt/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/pt/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/pt/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/pt/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", - "/pt/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/pt/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/pt/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/pt/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", - "/pt/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/pt/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/pt/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/pt/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", - "/pt/enterprise/2.17/user/authenticating-to-github/about-ssh": "/pt/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/pt/enterprise/2.17/github/authenticating-to-github/about-ssh": "/pt/enterprise/2.17/user/github/authenticating-to-github/about-ssh", - "/pt/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/pt/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/pt/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/pt/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", - "/pt/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/pt/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/pt/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/pt/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", - "/pt/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/pt/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/pt/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/pt/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", - "/pt/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/pt/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/pt/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/pt/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", - "/pt/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/pt/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", - "/pt/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/pt/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/pt/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/pt/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", - "/pt/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/pt/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", - "/pt/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/pt/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", - "/pt/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/pt/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/pt/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/pt/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", - "/pt/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/pt/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/pt/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/pt/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", - "/pt/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/pt/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/pt/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/pt/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", - "/pt/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/pt/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/pt/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/pt/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", - "/pt/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/pt/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/pt/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/pt/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", - "/pt/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/pt/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/pt/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/pt/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", - "/pt/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/pt/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/pt/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/pt/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", - "/pt/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/pt/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/pt/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/pt/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", - "/pt/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/pt/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", - "/pt/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/pt/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", - "/pt/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/pt/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", - "/pt/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/pt/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", - "/pt/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/pt/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", - "/pt/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/pt/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", - "/pt/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/pt/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", - "/pt/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/pt/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/pt/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", - "/pt/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/pt/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", - "/pt/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/pt/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/pt/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/pt/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", - "/pt/enterprise/2.17/user/authenticating-to-github": "/pt/enterprise/2.17/user/github/authenticating-to-github", - "/pt/enterprise/2.17/github/authenticating-to-github": "/pt/enterprise/2.17/user/github/authenticating-to-github", - "/pt/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/pt/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/pt/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/pt/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", - "/pt/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/pt/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/pt/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/pt/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", - "/pt/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/pt/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/pt/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/pt/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", - "/pt/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/pt/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/pt/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/pt/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", - "/pt/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/pt/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/pt/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/pt/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", - "/pt/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/pt/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/pt/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/pt/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", - "/pt/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/pt/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", - "/pt/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/pt/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", - "/pt/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/pt/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", - "/pt/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/pt/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", - "/pt/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/pt/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/pt/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", - "/pt/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/pt/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/pt/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/pt/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", - "/pt/enterprise/2.17/user/authenticating-to-github/signing-commits": "/pt/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/pt/enterprise/2.17/github/authenticating-to-github/signing-commits": "/pt/enterprise/2.17/user/github/authenticating-to-github/signing-commits", - "/pt/enterprise/2.17/user/authenticating-to-github/signing-tags": "/pt/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/pt/enterprise/2.17/github/authenticating-to-github/signing-tags": "/pt/enterprise/2.17/user/github/authenticating-to-github/signing-tags", - "/pt/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/pt/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/pt/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/pt/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", - "/pt/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/pt/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", - "/pt/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/pt/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/pt/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/pt/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", - "/pt/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/pt/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/pt/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/pt/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", - "/pt/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/pt/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/pt/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/pt/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", - "/pt/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/pt/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", - "/pt/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/pt/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/pt/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/pt/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", - "/pt/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/pt/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/pt/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", - "/pt/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/pt/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/pt/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/pt/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", - "/pt/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/pt/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/pt/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/pt/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", - "/pt/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/pt/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/pt/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/pt/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", - "/pt/enterprise/2.17/user/building-a-strong-community/about-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/pt/enterprise/2.17/github/building-a-strong-community/about-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/about-wikis", - "/pt/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/pt/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", - "/pt/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/pt/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/pt/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/pt/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", - "/pt/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/pt/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/pt/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/pt/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", - "/pt/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/pt/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", - "/pt/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/pt/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/pt/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/pt/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", - "/pt/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/pt/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", - "/pt/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/pt/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", - "/pt/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/pt/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", - "/pt/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/pt/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", - "/pt/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/pt/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/pt/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", - "/pt/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/pt/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", - "/pt/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/pt/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/pt/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", - "/pt/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/pt/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/pt/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/pt/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", - "/pt/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/pt/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/pt/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/pt/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", - "/pt/enterprise/2.17/user/building-a-strong-community": "/pt/enterprise/2.17/user/github/building-a-strong-community", - "/pt/enterprise/2.17/github/building-a-strong-community": "/pt/enterprise/2.17/user/github/building-a-strong-community", - "/pt/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/pt/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/pt/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/pt/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", - "/pt/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/pt/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/pt/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/pt/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", - "/pt/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/pt/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/pt/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", - "/pt/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/pt/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/pt/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/pt/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", - "/pt/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/pt/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/pt/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/pt/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", - "/pt/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/pt/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/pt/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/pt/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", - "/pt/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/pt/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/pt/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/pt/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", - "/pt/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/pt/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/pt/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/pt/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", - "/pt/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/pt/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", - "/pt/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/pt/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/pt/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/pt/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", - "/pt/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/pt/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/pt/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", - "/pt/enterprise/2.17/user/committing-changes-to-your-project": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project", - "/pt/enterprise/2.17/github/committing-changes-to-your-project": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", - "/pt/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/pt/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/pt/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", - "/pt/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/pt/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/pt/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", - "/pt/enterprise/2.17/user/extending-github/about-webhooks": "/pt/enterprise/2.17/user/github/extending-github/about-webhooks", - "/pt/enterprise/2.17/github/extending-github/about-webhooks": "/pt/enterprise/2.17/user/github/extending-github/about-webhooks", - "/pt/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/pt/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/pt/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/pt/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", - "/pt/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/pt/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/pt/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/pt/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", - "/pt/enterprise/2.17/user/extending-github": "/pt/enterprise/2.17/user/github/extending-github", - "/pt/enterprise/2.17/github/extending-github": "/pt/enterprise/2.17/user/github/extending-github", - "/pt/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/pt/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", - "/pt/enterprise/2.17/user/getting-started-with-github/be-social": "/pt/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/pt/enterprise/2.17/github/getting-started-with-github/be-social": "/pt/enterprise/2.17/user/github/getting-started-with-github/be-social", - "/pt/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/pt/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/pt/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/pt/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", - "/pt/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/pt/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", - "/pt/enterprise/2.17/user/getting-started-with-github/following-people": "/pt/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/pt/enterprise/2.17/github/getting-started-with-github/following-people": "/pt/enterprise/2.17/user/github/getting-started-with-github/following-people", - "/pt/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/pt/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/pt/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/pt/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", - "/pt/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/pt/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/pt/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/pt/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", - "/pt/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/pt/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/pt/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/pt/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", - "/pt/enterprise/2.17/user/getting-started-with-github/github-desktop": "/pt/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/pt/enterprise/2.17/github/getting-started-with-github/github-desktop": "/pt/enterprise/2.17/user/github/getting-started-with-github/github-desktop", - "/pt/enterprise/2.17/user/getting-started-with-github/github-glossary": "/pt/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/pt/enterprise/2.17/github/getting-started-with-github/github-glossary": "/pt/enterprise/2.17/user/github/getting-started-with-github/github-glossary", - "/pt/enterprise/2.17/user/getting-started-with-github/githubs-products": "/pt/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/pt/enterprise/2.17/github/getting-started-with-github/githubs-products": "/pt/enterprise/2.17/user/github/getting-started-with-github/githubs-products", - "/pt/enterprise/2.17/user/getting-started-with-github": "/pt/enterprise/2.17/user/github/getting-started-with-github", - "/pt/enterprise/2.17/github/getting-started-with-github": "/pt/enterprise/2.17/user/github/getting-started-with-github", - "/pt/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/pt/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/pt/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/pt/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", - "/pt/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/pt/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", - "/pt/enterprise/2.17/user/getting-started-with-github/quickstart": "/pt/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/pt/enterprise/2.17/github/getting-started-with-github/quickstart": "/pt/enterprise/2.17/user/github/getting-started-with-github/quickstart", - "/pt/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/pt/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/pt/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/pt/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", - "/pt/enterprise/2.17/user/getting-started-with-github/set-up-git": "/pt/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/pt/enterprise/2.17/github/getting-started-with-github/set-up-git": "/pt/enterprise/2.17/user/github/getting-started-with-github/set-up-git", - "/pt/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/pt/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/pt/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/pt/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", - "/pt/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/pt/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/pt/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/pt/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", - "/pt/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/pt/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", - "/pt/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/pt/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/pt/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/pt/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", - "/pt/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/pt/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/pt/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/pt/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", - "/pt/enterprise/2.17/user/getting-started-with-github/using-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/pt/enterprise/2.17/github/getting-started-with-github/using-github": "/pt/enterprise/2.17/user/github/getting-started-with-github/using-github", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", - "/pt/enterprise/2.17/user/importing-your-projects-to-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github", - "/pt/enterprise/2.17/github/importing-your-projects-to-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", - "/pt/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/pt/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/pt/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", - "/pt/enterprise/2.17/user": "/pt/enterprise/2.17/user/github", - "/pt/enterprise/2.17/github": "/pt/enterprise/2.17/user/github", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", - "/pt/enterprise/2.17/user/managing-files-in-a-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository", - "/pt/enterprise/2.17/github/managing-files-in-a-repository": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", - "/pt/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/pt/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/pt/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", - "/pt/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/pt/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", - "/pt/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/pt/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", - "/pt/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/pt/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/pt/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/pt/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", - "/pt/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/pt/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", - "/pt/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/pt/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/pt/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/pt/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", - "/pt/enterprise/2.17/user/managing-large-files": "/pt/enterprise/2.17/user/github/managing-large-files", - "/pt/enterprise/2.17/github/managing-large-files": "/pt/enterprise/2.17/user/github/managing-large-files", - "/pt/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/pt/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", - "/pt/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/pt/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", - "/pt/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/pt/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/pt/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/pt/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", - "/pt/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/pt/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/pt/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", - "/pt/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/pt/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/pt/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/pt/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", - "/pt/enterprise/2.17/user/managing-large-files/versioning-large-files": "/pt/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/pt/enterprise/2.17/github/managing-large-files/versioning-large-files": "/pt/enterprise/2.17/user/github/managing-large-files/versioning-large-files", - "/pt/enterprise/2.17/user/managing-large-files/working-with-large-files": "/pt/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/pt/enterprise/2.17/github/managing-large-files/working-with-large-files": "/pt/enterprise/2.17/user/github/managing-large-files/working-with-large-files", - "/pt/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/pt/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/pt/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/pt/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", - "/pt/enterprise/2.17/user/managing-security-vulnerabilities": "/pt/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/pt/enterprise/2.17/github/managing-security-vulnerabilities": "/pt/enterprise/2.17/user/github/managing-security-vulnerabilities", - "/pt/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/pt/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/pt/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/pt/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", - "/pt/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/pt/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", - "/pt/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/pt/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", - "/pt/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/pt/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", - "/pt/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/pt/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", - "/pt/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/pt/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", - "/pt/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/pt/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", - "/pt/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/pt/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", - "/pt/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/pt/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", - "/pt/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/pt/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", - "/pt/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/pt/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", - "/pt/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/pt/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", - "/pt/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/pt/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", - "/pt/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/pt/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", - "/pt/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/pt/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", - "/pt/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/pt/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", - "/pt/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/pt/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", - "/pt/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/pt/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", - "/pt/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/pt/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", - "/pt/enterprise/2.17/user/managing-your-work-on-github": "/pt/enterprise/2.17/user/github/managing-your-work-on-github", - "/pt/enterprise/2.17/github/managing-your-work-on-github": "/pt/enterprise/2.17/user/github/managing-your-work-on-github", - "/pt/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/pt/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", - "/pt/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/pt/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", - "/pt/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/pt/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", - "/pt/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/pt/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", - "/pt/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/pt/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", - "/pt/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/pt/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", - "/pt/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/pt/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", - "/pt/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/pt/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", - "/pt/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/pt/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", - "/pt/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/pt/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", - "/pt/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/pt/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", - "/pt/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/pt/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/pt/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", - "/pt/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/pt/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/pt/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", - "/pt/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/pt/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", - "/pt/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/pt/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", - "/pt/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/pt/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", - "/pt/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/pt/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", - "/pt/enterprise/2.17/user/searching-for-information-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github", - "/pt/enterprise/2.17/github/searching-for-information-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", - "/pt/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/pt/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", - "/pt/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/pt/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", - "/pt/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/pt/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", - "/pt/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/pt/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/pt/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/pt/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/pt/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", - "/pt/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/pt/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/pt/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", - "/pt/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/pt/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/pt/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/pt/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", - "/pt/enterprise/2.17/user/using-git/about-git-rebase": "/pt/enterprise/2.17/user/github/using-git/about-git-rebase", - "/pt/enterprise/2.17/github/using-git/about-git-rebase": "/pt/enterprise/2.17/user/github/using-git/about-git-rebase", - "/pt/enterprise/2.17/user/using-git/about-git-subtree-merges": "/pt/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/pt/enterprise/2.17/github/using-git/about-git-subtree-merges": "/pt/enterprise/2.17/user/github/using-git/about-git-subtree-merges", - "/pt/enterprise/2.17/user/using-git/about-remote-repositories": "/pt/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/pt/enterprise/2.17/github/using-git/about-remote-repositories": "/pt/enterprise/2.17/user/github/using-git/about-remote-repositories", - "/pt/enterprise/2.17/user/using-git/adding-a-remote": "/pt/enterprise/2.17/user/github/using-git/adding-a-remote", - "/pt/enterprise/2.17/github/using-git/adding-a-remote": "/pt/enterprise/2.17/user/github/using-git/adding-a-remote", - "/pt/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/pt/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/pt/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/pt/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", - "/pt/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/pt/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/pt/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/pt/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", - "/pt/enterprise/2.17/user/using-git/changing-a-remotes-url": "/pt/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/pt/enterprise/2.17/github/using-git/changing-a-remotes-url": "/pt/enterprise/2.17/user/github/using-git/changing-a-remotes-url", - "/pt/enterprise/2.17/user/using-git/changing-author-info": "/pt/enterprise/2.17/user/github/using-git/changing-author-info", - "/pt/enterprise/2.17/github/using-git/changing-author-info": "/pt/enterprise/2.17/user/github/using-git/changing-author-info", - "/pt/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/pt/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/pt/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/pt/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", - "/pt/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/pt/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/pt/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/pt/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", - "/pt/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/pt/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/pt/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/pt/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", - "/pt/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/pt/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/pt/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/pt/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", - "/pt/enterprise/2.17/user/using-git/git-workflows": "/pt/enterprise/2.17/user/github/using-git/git-workflows", - "/pt/enterprise/2.17/github/using-git/git-workflows": "/pt/enterprise/2.17/user/github/using-git/git-workflows", - "/pt/enterprise/2.17/user/using-git/ignoring-files": "/pt/enterprise/2.17/user/github/using-git/ignoring-files", - "/pt/enterprise/2.17/github/using-git/ignoring-files": "/pt/enterprise/2.17/user/github/using-git/ignoring-files", - "/pt/enterprise/2.17/user/using-git": "/pt/enterprise/2.17/user/github/using-git", - "/pt/enterprise/2.17/github/using-git": "/pt/enterprise/2.17/user/github/using-git", - "/pt/enterprise/2.17/user/using-git/learning-about-git": "/pt/enterprise/2.17/user/github/using-git/learning-about-git", - "/pt/enterprise/2.17/github/using-git/learning-about-git": "/pt/enterprise/2.17/user/github/using-git/learning-about-git", - "/pt/enterprise/2.17/user/using-git/managing-remote-repositories": "/pt/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/pt/enterprise/2.17/github/using-git/managing-remote-repositories": "/pt/enterprise/2.17/user/github/using-git/managing-remote-repositories", - "/pt/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/pt/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/pt/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/pt/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", - "/pt/enterprise/2.17/user/using-git/removing-a-remote": "/pt/enterprise/2.17/user/github/using-git/removing-a-remote", - "/pt/enterprise/2.17/github/using-git/removing-a-remote": "/pt/enterprise/2.17/user/github/using-git/removing-a-remote", - "/pt/enterprise/2.17/user/using-git/renaming-a-remote": "/pt/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/pt/enterprise/2.17/github/using-git/renaming-a-remote": "/pt/enterprise/2.17/user/github/using-git/renaming-a-remote", - "/pt/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/pt/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/pt/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/pt/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", - "/pt/enterprise/2.17/user/using-git/setting-your-username-in-git": "/pt/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/pt/enterprise/2.17/github/using-git/setting-your-username-in-git": "/pt/enterprise/2.17/user/github/using-git/setting-your-username-in-git", - "/pt/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/pt/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/pt/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/pt/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", - "/pt/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/pt/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/pt/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/pt/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", - "/pt/enterprise/2.17/user/using-git/using-advanced-git-commands": "/pt/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/pt/enterprise/2.17/github/using-git/using-advanced-git-commands": "/pt/enterprise/2.17/user/github/using-git/using-advanced-git-commands", - "/pt/enterprise/2.17/user/using-git/using-common-git-commands": "/pt/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/pt/enterprise/2.17/github/using-git/using-common-git-commands": "/pt/enterprise/2.17/user/github/using-git/using-common-git-commands", - "/pt/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/pt/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/pt/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/pt/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", - "/pt/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/pt/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/pt/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/pt/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", - "/pt/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/pt/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/pt/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/pt/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", - "/pt/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/pt/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/pt/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", - "/pt/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/pt/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/pt/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/pt/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", - "/pt/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/pt/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", - "/pt/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/pt/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", - "/pt/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/pt/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", - "/pt/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/pt/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/pt/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/pt/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", - "/pt/enterprise/2.17/user/working-with-github-pages": "/pt/enterprise/2.17/user/github/working-with-github-pages", - "/pt/enterprise/2.17/github/working-with-github-pages": "/pt/enterprise/2.17/user/github/working-with-github-pages", - "/pt/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/pt/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/pt/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", - "/pt/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/pt/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", - "/pt/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/pt/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/pt/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", - "/pt/enterprise/2.17/user/writing-on-github/about-saved-replies": "/pt/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/pt/enterprise/2.17/github/writing-on-github/about-saved-replies": "/pt/enterprise/2.17/user/github/writing-on-github/about-saved-replies", - "/pt/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/pt/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/pt/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/pt/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", - "/pt/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/pt/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/pt/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/pt/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", - "/pt/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/pt/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/pt/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/pt/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", - "/pt/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/pt/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/pt/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/pt/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", - "/pt/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/pt/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/pt/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/pt/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", - "/pt/enterprise/2.17/user/writing-on-github/creating-gists": "/pt/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/pt/enterprise/2.17/github/writing-on-github/creating-gists": "/pt/enterprise/2.17/user/github/writing-on-github/creating-gists", - "/pt/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/pt/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/pt/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/pt/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", - "/pt/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/pt/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/pt/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/pt/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", - "/pt/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/pt/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/pt/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/pt/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", - "/pt/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/pt/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/pt/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/pt/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", - "/pt/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/pt/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/pt/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/pt/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", - "/pt/enterprise/2.17/user/writing-on-github": "/pt/enterprise/2.17/user/github/writing-on-github", - "/pt/enterprise/2.17/github/writing-on-github": "/pt/enterprise/2.17/user/github/writing-on-github", - "/pt/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/pt/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/pt/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/pt/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", - "/pt/enterprise/2.17/user/writing-on-github/using-saved-replies": "/pt/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/pt/enterprise/2.17/github/writing-on-github/using-saved-replies": "/pt/enterprise/2.17/user/github/writing-on-github/using-saved-replies", - "/pt/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/pt/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/pt/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/pt/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", - "/pt/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/pt/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/pt/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/pt/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", - "/pt/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/pt/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/2.17/graphql/guides": "/pt/enterprise/2.17/user/graphql/guides", - "/pt/enterprise/2.17/graphql/guides/introduction-to-graphql": "/pt/enterprise/2.17/user/graphql/guides/introduction-to-graphql", - "/pt/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/pt/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/2.17/graphql/guides/using-global-node-ids": "/pt/enterprise/2.17/user/graphql/guides/using-global-node-ids", - "/pt/enterprise/2.17/graphql/guides/using-the-explorer": "/pt/enterprise/2.17/user/graphql/guides/using-the-explorer", - "/pt/enterprise/2.17/graphql": "/pt/enterprise/2.17/user/graphql", - "/pt/enterprise/2.17/graphql/overview/about-the-graphql-api": "/pt/enterprise/2.17/user/graphql/overview/about-the-graphql-api", - "/pt/enterprise/2.17/graphql/overview/breaking-changes": "/pt/enterprise/2.17/user/graphql/overview/breaking-changes", - "/pt/enterprise/2.17/graphql/overview/changelog": "/pt/enterprise/2.17/user/graphql/overview/changelog", - "/pt/enterprise/2.17/graphql/overview/explorer": "/pt/enterprise/2.17/user/graphql/overview/explorer", - "/pt/enterprise/2.17/graphql/overview": "/pt/enterprise/2.17/user/graphql/overview", - "/pt/enterprise/2.17/graphql/overview/resource-limitations": "/pt/enterprise/2.17/user/graphql/overview/resource-limitations", - "/pt/enterprise/2.17/graphql/overview/schema-previews": "/pt/enterprise/2.17/user/graphql/overview/schema-previews", - "/pt/enterprise/2.17/graphql/reference/enums": "/pt/enterprise/2.17/user/graphql/reference/enums", - "/pt/enterprise/2.17/graphql/reference": "/pt/enterprise/2.17/user/graphql/reference", - "/pt/enterprise/2.17/graphql/reference/input-objects": "/pt/enterprise/2.17/user/graphql/reference/input-objects", - "/pt/enterprise/2.17/graphql/reference/interfaces": "/pt/enterprise/2.17/user/graphql/reference/interfaces", - "/pt/enterprise/2.17/graphql/reference/mutations": "/pt/enterprise/2.17/user/graphql/reference/mutations", - "/pt/enterprise/2.17/graphql/reference/objects": "/pt/enterprise/2.17/user/graphql/reference/objects", - "/pt/enterprise/2.17/graphql/reference/queries": "/pt/enterprise/2.17/user/graphql/reference/queries", - "/pt/enterprise/2.17/graphql/reference/scalars": "/pt/enterprise/2.17/user/graphql/reference/scalars", - "/pt/enterprise/2.17/graphql/reference/unions": "/pt/enterprise/2.17/user/graphql/reference/unions", - "/pt/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/pt/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", - "/pt/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/pt/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", - "/pt/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/pt/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", - "/pt/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/pt/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", - "/pt/enterprise/2.17/insights": "/pt/enterprise/2.17/user/insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", - "/pt/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/pt/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", - "/pt/enterprise/2.17/rest": "/pt/enterprise/2.17/user/rest", - "/pt/enterprise/2.17/rest/reference/actions": "/pt/enterprise/2.17/user/rest/reference/actions", - "/pt/enterprise/2.17/rest/reference/activity": "/pt/enterprise/2.17/user/rest/reference/activity", - "/pt/enterprise/2.17/rest/reference/apps": "/pt/enterprise/2.17/user/rest/reference/apps", - "/pt/enterprise/2.17/rest/reference/checks": "/pt/enterprise/2.17/user/rest/reference/checks", - "/pt/enterprise/2.17/rest/reference/codes-of-conduct": "/pt/enterprise/2.17/user/rest/reference/codes-of-conduct", - "/pt/enterprise/2.17/rest/reference/emojis": "/pt/enterprise/2.17/user/rest/reference/emojis", - "/pt/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/pt/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", - "/pt/enterprise/2.17/rest/reference/enterprise-admin": "/pt/enterprise/2.17/user/rest/reference/enterprise-admin", - "/pt/enterprise/2.17/rest/reference/gists": "/pt/enterprise/2.17/user/rest/reference/gists", - "/pt/enterprise/2.17/rest/reference/git": "/pt/enterprise/2.17/user/rest/reference/git", - "/pt/enterprise/2.17/rest/reference/gitignore": "/pt/enterprise/2.17/user/rest/reference/gitignore", - "/pt/enterprise/2.17/rest/reference": "/pt/enterprise/2.17/user/rest/reference", - "/pt/enterprise/2.17/rest/reference/interactions": "/pt/enterprise/2.17/user/rest/reference/interactions", - "/pt/enterprise/2.17/rest/reference/issues": "/pt/enterprise/2.17/user/rest/reference/issues", - "/pt/enterprise/2.17/rest/reference/licenses": "/pt/enterprise/2.17/user/rest/reference/licenses", - "/pt/enterprise/2.17/rest/reference/markdown": "/pt/enterprise/2.17/user/rest/reference/markdown", - "/pt/enterprise/2.17/rest/reference/meta": "/pt/enterprise/2.17/user/rest/reference/meta", - "/pt/enterprise/2.17/rest/reference/migrations": "/pt/enterprise/2.17/user/rest/reference/migrations", - "/pt/enterprise/2.17/rest/reference/oauth-authorizations": "/pt/enterprise/2.17/user/rest/reference/oauth-authorizations", - "/pt/enterprise/2.17/rest/reference/orgs": "/pt/enterprise/2.17/user/rest/reference/orgs", - "/pt/enterprise/2.17/rest/reference/projects": "/pt/enterprise/2.17/user/rest/reference/projects", - "/pt/enterprise/2.17/rest/reference/pulls": "/pt/enterprise/2.17/user/rest/reference/pulls", - "/pt/enterprise/2.17/rest/reference/rate-limit": "/pt/enterprise/2.17/user/rest/reference/rate-limit", - "/pt/enterprise/2.17/rest/reference/reactions": "/pt/enterprise/2.17/user/rest/reference/reactions", - "/pt/enterprise/2.17/rest/reference/repos": "/pt/enterprise/2.17/user/rest/reference/repos", - "/pt/enterprise/2.17/rest/reference/scim": "/pt/enterprise/2.17/user/rest/reference/scim", - "/pt/enterprise/2.17/rest/reference/search": "/pt/enterprise/2.17/user/rest/reference/search", - "/pt/enterprise/2.17/rest/reference/teams": "/pt/enterprise/2.17/user/rest/reference/teams", - "/pt/enterprise/2.17/rest/reference/users": "/pt/enterprise/2.17/user/rest/reference/users" + "/enterprise/2.13/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": null, + "/enterprise/2.13/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": null, + "/enterprise/2.13/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": null, + "/enterprise/2.13/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": null, + "/enterprise/2.13/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": null, + "/enterprise/2.13/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": null, + "/enterprise/2.13/admin/guides/articles/using-github-task-runner": null, + "/enterprise/2.13/admin/articles/using-github-task-runner": null, + "/enterprise/2.13/admin/guides/clustering/about-cluster-nodes": null, + "/enterprise/2.13/admin/clustering/about-cluster-nodes": null, + "/enterprise/2.13/admin/guides/clustering/clustering-overview": null, + "/enterprise/2.13/admin/clustering/clustering-overview": null, + "/enterprise/2.13/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": null, + "/enterprise/2.13/admin/clustering/differences-between-clustering-and-high-availability-ha": null, + "/enterprise/2.13/admin/guides/clustering": null, + "/enterprise/2.13/admin/clustering": null, + "/enterprise/2.13/admin/guides/clustering/initializing-the-cluster": null, + "/enterprise/2.13/admin/clustering/initializing-the-cluster": null, + "/enterprise/2.13/admin/guides/clustering/managing-a-github-enterprise-server-cluster": null, + "/enterprise/2.13/admin/clustering/managing-a-github-enterprise-server-cluster": null, + "/enterprise/2.13/admin/guides/clustering/monitoring-cluster-nodes": null, + "/enterprise/2.13/admin/clustering/monitoring-cluster-nodes": null, + "/enterprise/2.13/admin/guides/clustering/network-configuration": null, + "/enterprise/2.13/admin/clustering/network-configuration": null, + "/enterprise/2.13/admin/guides/clustering/replacing-a-cluster-node": null, + "/enterprise/2.13/admin/clustering/replacing-a-cluster-node": null, + "/enterprise/2.13/admin/guides/clustering/setting-up-the-cluster-instances": null, + "/enterprise/2.13/admin/clustering/setting-up-the-cluster-instances": null, + "/enterprise/2.13/admin/guides/clustering/upgrading-a-cluster": null, + "/enterprise/2.13/admin/clustering/upgrading-a-cluster": null, + "/enterprise/2.13/admin/guides/developer-workflow/about-pre-receive-hooks": null, + "/enterprise/2.13/admin/developer-workflow/about-pre-receive-hooks": null, + "/enterprise/2.13/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": null, + "/enterprise/2.13/admin/developer-workflow/about-protected-branches-and-required-status-checks": null, + "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": null, + "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-on-your-appliance": null, + "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": null, + "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-a-repository": null, + "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": null, + "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": null, + "/enterprise/2.13/admin/guides/developer-workflow/blocking-force-pushes": null, + "/enterprise/2.13/admin/developer-workflow/blocking-force-pushes": null, + "/enterprise/2.13/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": null, + "/enterprise/2.13/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": null, + "/enterprise/2.13/admin/guides/developer-workflow/continuous-integration-using-jenkins": null, + "/enterprise/2.13/admin/developer-workflow/continuous-integration-using-jenkins": null, + "/enterprise/2.13/admin/guides/developer-workflow/continuous-integration-using-travis-ci": null, + "/enterprise/2.13/admin/developer-workflow/continuous-integration-using-travis-ci": null, + "/enterprise/2.13/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": null, + "/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-environment": null, + "/enterprise/2.13/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": null, + "/enterprise/2.13/admin/developer-workflow/creating-a-pre-receive-hook-script": null, + "/enterprise/2.13/admin/guides/developer-workflow/customizing-your-instance-with-integrations": null, + "/enterprise/2.13/admin/developer-workflow/customizing-your-instance-with-integrations": null, + "/enterprise/2.13/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": null, + "/enterprise/2.13/admin/developer-workflow/establishing-pull-request-merge-conditions": null, + "/enterprise/2.13/admin/guides/developer-workflow": null, + "/enterprise/2.13/admin/developer-workflow": null, + "/enterprise/2.13/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": null, + "/enterprise/2.13/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": null, + "/enterprise/2.13/admin/guides/developer-workflow/managing-projects-using-jira": null, + "/enterprise/2.13/admin/developer-workflow/managing-projects-using-jira": null, + "/enterprise/2.13/admin/guides/developer-workflow/troubleshooting-service-hooks": null, + "/enterprise/2.13/admin/developer-workflow/troubleshooting-service-hooks": null, + "/enterprise/2.13/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": null, + "/enterprise/2.13/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": null, + "/enterprise/2.13/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": null, + "/enterprise/2.13/admin/developer-workflow/using-webhooks-for-continuous-integration": null, + "/enterprise/2.13/admin/guides/enterprise-support/about-github-enterprise-support": null, + "/enterprise/2.13/admin/enterprise-support/about-github-enterprise-support": null, + "/enterprise/2.13/admin/guides/enterprise-support/about-github-premium-support": null, + "/enterprise/2.13/admin/enterprise-support/about-github-premium-support": null, + "/enterprise/2.13/admin/guides/enterprise-support": null, + "/enterprise/2.13/admin/enterprise-support": null, + "/enterprise/2.13/admin/guides/enterprise-support/preparing-to-submit-a-ticket": null, + "/enterprise/2.13/admin/enterprise-support/preparing-to-submit-a-ticket": null, + "/enterprise/2.13/admin/guides/enterprise-support/providing-data-to-github-support": null, + "/enterprise/2.13/admin/enterprise-support/providing-data-to-github-support": null, + "/enterprise/2.13/admin/guides/enterprise-support/reaching-github-support": null, + "/enterprise/2.13/admin/enterprise-support/reaching-github-support": null, + "/enterprise/2.13/admin/guides/enterprise-support/receiving-help-from-github-support": null, + "/enterprise/2.13/admin/enterprise-support/receiving-help-from-github-support": null, + "/enterprise/2.13/admin/guides/enterprise-support/submitting-a-ticket": null, + "/enterprise/2.13/admin/enterprise-support/submitting-a-ticket": null, + "/enterprise/2.13/admin/guides": null, + "/enterprise/2.13/admin": null, + "/enterprise/2.13/admin/guides/installation/about-geo-replication": null, + "/enterprise/2.13/admin/installation/about-geo-replication": null, + "/enterprise/2.13/admin/guides/installation/about-high-availability-configuration": null, + "/enterprise/2.13/admin/installation/about-high-availability-configuration": null, + "/enterprise/2.13/admin/guides/installation/about-license-files": null, + "/enterprise/2.13/admin/installation/about-license-files": null, + "/enterprise/2.13/admin/guides/installation/about-the-github-enterprise-server-api": null, + "/enterprise/2.13/admin/installation/about-the-github-enterprise-server-api": null, + "/enterprise/2.13/admin/guides/installation/accessing-the-administrative-shell-ssh": null, + "/enterprise/2.13/admin/installation/accessing-the-administrative-shell-ssh": null, + "/enterprise/2.13/admin/guides/installation/accessing-the-management-console": null, + "/enterprise/2.13/admin/installation/accessing-the-management-console": null, + "/enterprise/2.13/admin/guides/installation/accessing-the-monitor-dashboard": null, + "/enterprise/2.13/admin/installation/accessing-the-monitor-dashboard": null, + "/enterprise/2.13/admin/guides/installation/activity-dashboard": null, + "/enterprise/2.13/admin/installation/activity-dashboard": null, + "/enterprise/2.13/admin/guides/installation/audit-logging": null, + "/enterprise/2.13/admin/installation/audit-logging": null, + "/enterprise/2.13/admin/guides/installation/audited-actions": null, + "/enterprise/2.13/admin/installation/audited-actions": null, + "/enterprise/2.13/admin/guides/installation/command-line-utilities": null, + "/enterprise/2.13/admin/installation/command-line-utilities": null, + "/enterprise/2.13/admin/guides/installation/configuring-a-hostname": null, + "/enterprise/2.13/admin/installation/configuring-a-hostname": null, + "/enterprise/2.13/admin/guides/installation/configuring-an-outbound-web-proxy-server": null, + "/enterprise/2.13/admin/installation/configuring-an-outbound-web-proxy-server": null, + "/enterprise/2.13/admin/guides/installation/configuring-backups-on-your-appliance": null, + "/enterprise/2.13/admin/installation/configuring-backups-on-your-appliance": null, + "/enterprise/2.13/admin/guides/installation/configuring-built-in-firewall-rules": null, + "/enterprise/2.13/admin/installation/configuring-built-in-firewall-rules": null, + "/enterprise/2.13/admin/guides/installation/configuring-collectd": null, + "/enterprise/2.13/admin/installation/configuring-collectd": null, + "/enterprise/2.13/admin/guides/installation/configuring-dns-nameservers": null, + "/enterprise/2.13/admin/installation/configuring-dns-nameservers": null, + "/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": null, + "/enterprise/2.13/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": null, + "/enterprise/2.13/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": null, + "/enterprise/2.13/admin/guides/installation/configuring-git-large-file-storage": null, + "/enterprise/2.13/admin/installation/configuring-git-large-file-storage": null, + "/enterprise/2.13/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": null, + "/enterprise/2.13/admin/installation/configuring-github-enterprise-server-for-high-availability": null, + "/enterprise/2.13/admin/guides/installation/configuring-github-pages-on-your-appliance": null, + "/enterprise/2.13/admin/installation/configuring-github-pages-on-your-appliance": null, + "/enterprise/2.13/admin/guides/installation/configuring-rate-limits": null, + "/enterprise/2.13/admin/installation/configuring-rate-limits": null, + "/enterprise/2.13/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": null, + "/enterprise/2.13/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": null, + "/enterprise/2.13/admin/guides/installation/configuring-the-github-enterprise-server-appliance": null, + "/enterprise/2.13/admin/installation/configuring-the-github-enterprise-server-appliance": null, + "/enterprise/2.13/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": null, + "/enterprise/2.13/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": null, + "/enterprise/2.13/admin/guides/installation/configuring-time-synchronization": null, + "/enterprise/2.13/admin/installation/configuring-time-synchronization": null, + "/enterprise/2.13/admin/guides/installation/configuring-tls": null, + "/enterprise/2.13/admin/installation/configuring-tls": null, + "/enterprise/2.13/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": null, + "/enterprise/2.13/admin/installation/configuring-your-github-enterprise-server-network-settings": null, + "/enterprise/2.13/admin/guides/installation/creating-a-high-availability-replica": null, + "/enterprise/2.13/admin/installation/creating-a-high-availability-replica": null, + "/enterprise/2.13/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": null, + "/enterprise/2.13/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": null, + "/enterprise/2.13/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": null, + "/enterprise/2.13/admin/guides/installation/downloading-your-license": null, + "/enterprise/2.13/admin/installation/downloading-your-license": null, + "/enterprise/2.13/admin/guides/installation/enabling-and-scheduling-maintenance-mode": null, + "/enterprise/2.13/admin/installation/enabling-and-scheduling-maintenance-mode": null, + "/enterprise/2.13/admin/guides/installation/enabling-automatic-update-checks": null, + "/enterprise/2.13/admin/installation/enabling-automatic-update-checks": null, + "/enterprise/2.13/admin/guides/installation/enabling-private-mode": null, + "/enterprise/2.13/admin/installation/enabling-private-mode": null, + "/enterprise/2.13/admin/guides/installation/enabling-subdomain-isolation": null, + "/enterprise/2.13/admin/installation/enabling-subdomain-isolation": null, + "/enterprise/2.13/admin/guides/installation/increasing-cpu-or-memory-resources": null, + "/enterprise/2.13/admin/installation/increasing-cpu-or-memory-resources": null, + "/enterprise/2.13/admin/guides/installation/increasing-storage-capacity": null, + "/enterprise/2.13/admin/installation/increasing-storage-capacity": null, + "/enterprise/2.13/admin/guides/installation": null, + "/enterprise/2.13/admin/installation": null, + "/enterprise/2.13/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": null, + "/enterprise/2.13/admin/installation/initiating-a-failover-to-your-replica-appliance": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-aws": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-aws": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-azure": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-azure": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-hyper-v": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-openstack-kvm": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-vmware": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-vmware": null, + "/enterprise/2.13/admin/guides/installation/installing-github-enterprise-server-on-xenserver": null, + "/enterprise/2.13/admin/installation/installing-github-enterprise-server-on-xenserver": null, + "/enterprise/2.13/admin/guides/installation/log-forwarding": null, + "/enterprise/2.13/admin/installation/log-forwarding": null, + "/enterprise/2.13/admin/guides/installation/managing-your-github-enterprise-server-license": null, + "/enterprise/2.13/admin/installation/managing-your-github-enterprise-server-license": null, + "/enterprise/2.13/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": null, + "/enterprise/2.13/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": null, + "/enterprise/2.13/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": null, + "/enterprise/2.13/admin/installation/migrating-from-github-enterprise-1110x-to-2123": null, + "/enterprise/2.13/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": null, + "/enterprise/2.13/admin/installation/migrating-to-a-different-git-large-file-storage-server": null, + "/enterprise/2.13/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": null, + "/enterprise/2.13/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": null, + "/enterprise/2.13/admin/guides/installation/monitoring-using-snmp": null, + "/enterprise/2.13/admin/installation/monitoring-using-snmp": null, + "/enterprise/2.13/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": null, + "/enterprise/2.13/admin/installation/monitoring-your-github-enterprise-server-appliance": null, + "/enterprise/2.13/admin/guides/installation/network-ports": null, + "/enterprise/2.13/admin/installation/network-ports": null, + "/enterprise/2.13/admin/guides/installation/recommended-alert-thresholds": null, + "/enterprise/2.13/admin/installation/recommended-alert-thresholds": null, + "/enterprise/2.13/admin/guides/installation/recovering-a-high-availability-configuration": null, + "/enterprise/2.13/admin/installation/recovering-a-high-availability-configuration": null, + "/enterprise/2.13/admin/guides/installation/removing-a-high-availability-replica": null, + "/enterprise/2.13/admin/installation/removing-a-high-availability-replica": null, + "/enterprise/2.13/admin/guides/installation/searching-the-audit-log": null, + "/enterprise/2.13/admin/installation/searching-the-audit-log": null, + "/enterprise/2.13/admin/guides/installation/setting-git-push-limits": null, + "/enterprise/2.13/admin/installation/setting-git-push-limits": null, + "/enterprise/2.13/admin/guides/installation/setting-up-a-github-enterprise-server-instance": null, + "/enterprise/2.13/admin/installation/setting-up-a-github-enterprise-server-instance": null, + "/enterprise/2.13/admin/guides/installation/setting-up-a-staging-instance": null, + "/enterprise/2.13/admin/installation/setting-up-a-staging-instance": null, + "/enterprise/2.13/admin/guides/installation/setting-up-external-monitoring": null, + "/enterprise/2.13/admin/installation/setting-up-external-monitoring": null, + "/enterprise/2.13/admin/guides/installation/site-admin-dashboard": null, + "/enterprise/2.13/admin/installation/site-admin-dashboard": null, + "/enterprise/2.13/admin/guides/installation/system-overview": null, + "/enterprise/2.13/admin/installation/system-overview": null, + "/enterprise/2.13/admin/guides/installation/troubleshooting-ssl-errors": null, + "/enterprise/2.13/admin/installation/troubleshooting-ssl-errors": null, + "/enterprise/2.13/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": null, + "/enterprise/2.13/admin/installation/updating-the-virtual-machine-and-physical-resources": null, + "/enterprise/2.13/admin/guides/installation/updating-your-license": null, + "/enterprise/2.13/admin/installation/updating-your-license": null, + "/enterprise/2.13/admin/guides/installation/upgrade-requirements": null, + "/enterprise/2.13/admin/installation/upgrade-requirements": null, + "/enterprise/2.13/admin/guides/installation/upgrading-github-enterprise-server": null, + "/enterprise/2.13/admin/installation/upgrading-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": null, + "/enterprise/2.13/admin/installation/using-github-enterprise-server-with-a-load-balancer": null, + "/enterprise/2.13/admin/guides/installation/validating-your-domain-settings": null, + "/enterprise/2.13/admin/installation/validating-your-domain-settings": null, + "/enterprise/2.13/admin/guides/installation/viewing-push-logs": null, + "/enterprise/2.13/admin/installation/viewing-push-logs": null, + "/enterprise/2.13/admin/guides/migrations/about-migrations": null, + "/enterprise/2.13/admin/migrations/about-migrations": null, + "/enterprise/2.13/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": null, + "/enterprise/2.13/admin/migrations/applying-the-imported-data-on-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/migrations/completing-the-import-on-github-enterprise-server": null, + "/enterprise/2.13/admin/migrations/completing-the-import-on-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": null, + "/enterprise/2.13/admin/migrations/exporting-migration-data-from-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/migrations/exporting-migration-data-from-githubcom": null, + "/enterprise/2.13/admin/migrations/exporting-migration-data-from-githubcom": null, + "/enterprise/2.13/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": null, + "/enterprise/2.13/admin/migrations/exporting-the-github-enterprise-server-source-repositories": null, + "/enterprise/2.13/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": null, + "/enterprise/2.13/admin/migrations/exporting-the-githubcom-organizations-repositories": null, + "/enterprise/2.13/admin/guides/migrations/generating-a-list-of-migration-conflicts": null, + "/enterprise/2.13/admin/migrations/generating-a-list-of-migration-conflicts": null, + "/enterprise/2.13/admin/guides/migrations/importing-data-from-third-party-version-control-systems": null, + "/enterprise/2.13/admin/migrations/importing-data-from-third-party-version-control-systems": null, + "/enterprise/2.13/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": null, + "/enterprise/2.13/admin/migrations/importing-migration-data-to-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/migrations": null, + "/enterprise/2.13/admin/migrations": null, + "/enterprise/2.13/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": null, + "/enterprise/2.13/admin/migrations/preparing-the-github-enterprise-server-source-instance": null, + "/enterprise/2.13/admin/guides/migrations/preparing-the-githubcom-source-organization": null, + "/enterprise/2.13/admin/migrations/preparing-the-githubcom-source-organization": null, + "/enterprise/2.13/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": null, + "/enterprise/2.13/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": null, + "/enterprise/2.13/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": null, + "/enterprise/2.13/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": null, + "/enterprise/2.13/admin/guides/migrations/reviewing-migration-conflicts": null, + "/enterprise/2.13/admin/migrations/reviewing-migration-conflicts": null, + "/enterprise/2.13/admin/guides/migrations/reviewing-migration-data": null, + "/enterprise/2.13/admin/migrations/reviewing-migration-data": null, + "/enterprise/2.13/admin/guides/user-management/about-global-webhooks": null, + "/enterprise/2.13/admin/user-management/about-global-webhooks": null, + "/enterprise/2.13/admin/guides/user-management/adding-people-to-teams": null, + "/enterprise/2.13/admin/user-management/adding-people-to-teams": null, + "/enterprise/2.13/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": null, + "/enterprise/2.13/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": null, + "/enterprise/2.13/admin/guides/user-management/archiving-and-unarchiving-repositories": null, + "/enterprise/2.13/admin/user-management/archiving-and-unarchiving-repositories": null, + "/enterprise/2.13/admin/guides/user-management/auditing-ssh-keys": null, + "/enterprise/2.13/admin/user-management/auditing-ssh-keys": null, + "/enterprise/2.13/admin/guides/user-management/auditing-users-across-your-instance": null, + "/enterprise/2.13/admin/user-management/auditing-users-across-your-instance": null, + "/enterprise/2.13/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": null, + "/enterprise/2.13/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": null, + "/enterprise/2.13/admin/guides/user-management/basic-account-settings": null, + "/enterprise/2.13/admin/user-management/basic-account-settings": null, + "/enterprise/2.13/admin/guides/user-management/best-practices-for-user-security": null, + "/enterprise/2.13/admin/user-management/best-practices-for-user-security": null, + "/enterprise/2.13/admin/guides/user-management/changing-authentication-methods": null, + "/enterprise/2.13/admin/user-management/changing-authentication-methods": null, + "/enterprise/2.13/admin/guides/user-management/configuring-email-for-notifications": null, + "/enterprise/2.13/admin/user-management/configuring-email-for-notifications": null, + "/enterprise/2.13/admin/guides/user-management/creating-organizations": null, + "/enterprise/2.13/admin/user-management/creating-organizations": null, + "/enterprise/2.13/admin/guides/user-management/creating-teams": null, + "/enterprise/2.13/admin/user-management/creating-teams": null, + "/enterprise/2.13/admin/guides/user-management/customizing-user-messages-on-your-instance": null, + "/enterprise/2.13/admin/user-management/customizing-user-messages-on-your-instance": null, + "/enterprise/2.13/admin/guides/user-management/disabling-unauthenticated-sign-ups": null, + "/enterprise/2.13/admin/user-management/disabling-unauthenticated-sign-ups": null, + "/enterprise/2.13/admin/guides/user-management": null, + "/enterprise/2.13/admin/user-management": null, + "/enterprise/2.13/admin/guides/user-management/managing-dormant-users": null, + "/enterprise/2.13/admin/user-management/managing-dormant-users": null, + "/enterprise/2.13/admin/guides/user-management/managing-global-webhooks": null, + "/enterprise/2.13/admin/user-management/managing-global-webhooks": null, + "/enterprise/2.13/admin/guides/user-management/organizations-and-teams": null, + "/enterprise/2.13/admin/user-management/organizations-and-teams": null, + "/enterprise/2.13/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": null, + "/enterprise/2.13/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": null, + "/enterprise/2.13/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": null, + "/enterprise/2.13/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": null, + "/enterprise/2.13/admin/guides/user-management/preventing-users-from-creating-organizations": null, + "/enterprise/2.13/admin/user-management/preventing-users-from-creating-organizations": null, + "/enterprise/2.13/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": null, + "/enterprise/2.13/admin/user-management/preventing-users-from-deleting-organization-repositories": null, + "/enterprise/2.13/admin/guides/user-management/promoting-or-demoting-a-site-administrator": null, + "/enterprise/2.13/admin/user-management/promoting-or-demoting-a-site-administrator": null, + "/enterprise/2.13/admin/guides/user-management/rebuilding-contributions-data": null, + "/enterprise/2.13/admin/user-management/rebuilding-contributions-data": null, + "/enterprise/2.13/admin/guides/user-management/removing-users-from-teams-and-organizations": null, + "/enterprise/2.13/admin/user-management/removing-users-from-teams-and-organizations": null, + "/enterprise/2.13/admin/guides/user-management/repositories": null, + "/enterprise/2.13/admin/user-management/repositories": null, + "/enterprise/2.13/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": null, + "/enterprise/2.13/admin/user-management/requiring-two-factor-authentication-for-an-organization": null, + "/enterprise/2.13/admin/guides/user-management/suspending-and-unsuspending-users": null, + "/enterprise/2.13/admin/user-management/suspending-and-unsuspending-users": null, + "/enterprise/2.13/admin/guides/user-management/user-security": null, + "/enterprise/2.13/admin/user-management/user-security": null, + "/enterprise/2.13/admin/guides/user-management/using-built-in-authentication": null, + "/enterprise/2.13/admin/user-management/using-built-in-authentication": null, + "/enterprise/2.13/admin/guides/user-management/using-cas": null, + "/enterprise/2.13/admin/user-management/using-cas": null, + "/enterprise/2.13/admin/guides/user-management/using-ldap": null, + "/enterprise/2.13/admin/user-management/using-ldap": null, + "/enterprise/2.13/admin/guides/user-management/using-saml": null, + "/enterprise/2.13/admin/user-management/using-saml": null, + "/enterprise/2.13": null, + "/enterprise/2.13/articles/3d-file-viewer": null, + "/enterprise/2.13/user/articles/3d-file-viewer": null, + "/enterprise/2.13/articles/about-archiving-repositories": null, + "/enterprise/2.13/user/articles/about-archiving-repositories": null, + "/enterprise/2.13/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": null, + "/enterprise/2.13/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": null, + "/enterprise/2.13/articles/about-automation-for-project-boards": null, + "/enterprise/2.13/user/articles/about-automation-for-project-boards": null, + "/enterprise/2.13/articles/about-branch-restrictions": null, + "/enterprise/2.13/user/articles/about-branch-restrictions": null, + "/enterprise/2.13/articles/about-branches": null, + "/enterprise/2.13/user/articles/about-branches": null, + "/enterprise/2.13/articles/about-code-owners": null, + "/enterprise/2.13/user/articles/about-code-owners": null, + "/enterprise/2.13/articles/about-collaborative-development-models": null, + "/enterprise/2.13/user/articles/about-collaborative-development-models": null, + "/enterprise/2.13/articles/about-commit-email-addresses": null, + "/enterprise/2.13/user/articles/about-commit-email-addresses": null, + "/enterprise/2.13/articles/about-commit-signature-verification": null, + "/enterprise/2.13/user/articles/about-commit-signature-verification": null, + "/enterprise/2.13/articles/about-comparing-branches-in-pull-requests": null, + "/enterprise/2.13/user/articles/about-comparing-branches-in-pull-requests": null, + "/enterprise/2.13/articles/about-conversations-on-github": null, + "/enterprise/2.13/user/articles/about-conversations-on-github": null, + "/enterprise/2.13/articles/about-duplicate-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/about-duplicate-issues-and-pull-requests": null, + "/enterprise/2.13/articles/about-email-notifications-for-pushes-to-your-repository": null, + "/enterprise/2.13/user/articles/about-email-notifications-for-pushes-to-your-repository": null, + "/enterprise/2.13/articles/about-email-notifications": null, + "/enterprise/2.13/user/articles/about-email-notifications": null, + "/enterprise/2.13/articles/about-forks": null, + "/enterprise/2.13/user/articles/about-forks": null, + "/enterprise/2.13/articles/about-gists": null, + "/enterprise/2.13/user/articles/about-gists": null, + "/enterprise/2.13/articles/about-git-large-file-storage": null, + "/enterprise/2.13/user/articles/about-git-large-file-storage": null, + "/enterprise/2.13/articles/about-git-rebase": null, + "/enterprise/2.13/user/articles/about-git-rebase": null, + "/enterprise/2.13/articles/about-git-subtree-merges": null, + "/enterprise/2.13/user/articles/about-git-subtree-merges": null, + "/enterprise/2.13/articles/about-github-mirrors": null, + "/enterprise/2.13/user/articles/about-github-mirrors": null, + "/enterprise/2.13/articles/about-github-pages-and-jekyll": null, + "/enterprise/2.13/user/articles/about-github-pages-and-jekyll": null, + "/enterprise/2.13/articles/about-issue-and-pull-request-templates": null, + "/enterprise/2.13/user/articles/about-issue-and-pull-request-templates": null, + "/enterprise/2.13/articles/about-issues": null, + "/enterprise/2.13/user/articles/about-issues": null, + "/enterprise/2.13/articles/about-jekyll-themes-on-github": null, + "/enterprise/2.13/user/articles/about-jekyll-themes-on-github": null, + "/enterprise/2.13/articles/about-labels": null, + "/enterprise/2.13/user/articles/about-labels": null, + "/enterprise/2.13/articles/about-merge-conflicts": null, + "/enterprise/2.13/user/articles/about-merge-conflicts": null, + "/enterprise/2.13/articles/about-merge-methods-on-github": null, + "/enterprise/2.13/user/articles/about-merge-methods-on-github": null, + "/enterprise/2.13/articles/about-milestones": null, + "/enterprise/2.13/user/articles/about-milestones": null, + "/enterprise/2.13/articles/about-notifications": null, + "/enterprise/2.13/user/articles/about-notifications": null, + "/enterprise/2.13/articles/about-organization-membership": null, + "/enterprise/2.13/user/articles/about-organization-membership": null, + "/enterprise/2.13/articles/about-organizations": null, + "/enterprise/2.13/user/articles/about-organizations": null, + "/enterprise/2.13/articles/about-project-boards": null, + "/enterprise/2.13/user/articles/about-project-boards": null, + "/enterprise/2.13/articles/about-protected-branches": null, + "/enterprise/2.13/user/articles/about-protected-branches": null, + "/enterprise/2.13/articles/about-pull-request-merges": null, + "/enterprise/2.13/user/articles/about-pull-request-merges": null, + "/enterprise/2.13/articles/about-pull-request-reviews": null, + "/enterprise/2.13/user/articles/about-pull-request-reviews": null, + "/enterprise/2.13/articles/about-pull-requests": null, + "/enterprise/2.13/user/articles/about-pull-requests": null, + "/enterprise/2.13/articles/about-readmes": null, + "/enterprise/2.13/user/articles/about-readmes": null, + "/enterprise/2.13/articles/about-releases": null, + "/enterprise/2.13/user/articles/about-releases": null, + "/enterprise/2.13/articles/about-remote-repositories": null, + "/enterprise/2.13/user/articles/about-remote-repositories": null, + "/enterprise/2.13/articles/about-repositories": null, + "/enterprise/2.13/user/articles/about-repositories": null, + "/enterprise/2.13/articles/about-repository-graphs": null, + "/enterprise/2.13/user/articles/about-repository-graphs": null, + "/enterprise/2.13/articles/about-repository-languages": null, + "/enterprise/2.13/user/articles/about-repository-languages": null, + "/enterprise/2.13/articles/about-required-commit-signing": null, + "/enterprise/2.13/user/articles/about-required-commit-signing": null, + "/enterprise/2.13/articles/about-required-reviews-for-pull-requests": null, + "/enterprise/2.13/user/articles/about-required-reviews-for-pull-requests": null, + "/enterprise/2.13/articles/about-required-status-checks": null, + "/enterprise/2.13/user/articles/about-required-status-checks": null, + "/enterprise/2.13/articles/about-saved-replies": null, + "/enterprise/2.13/user/articles/about-saved-replies": null, + "/enterprise/2.13/articles/about-searching-on-github": null, + "/enterprise/2.13/user/articles/about-searching-on-github": null, + "/enterprise/2.13/articles/about-ssh": null, + "/enterprise/2.13/user/articles/about-ssh": null, + "/enterprise/2.13/articles/about-stars": null, + "/enterprise/2.13/user/articles/about-stars": null, + "/enterprise/2.13/articles/about-status-checks": null, + "/enterprise/2.13/user/articles/about-status-checks": null, + "/enterprise/2.13/articles/about-task-lists": null, + "/enterprise/2.13/user/articles/about-task-lists": null, + "/enterprise/2.13/articles/about-team-discussions": null, + "/enterprise/2.13/user/articles/about-team-discussions": null, + "/enterprise/2.13/articles/about-teams": null, + "/enterprise/2.13/user/articles/about-teams": null, + "/enterprise/2.13/articles/about-topics": null, + "/enterprise/2.13/user/articles/about-topics": null, + "/enterprise/2.13/articles/about-two-factor-authentication": null, + "/enterprise/2.13/user/articles/about-two-factor-authentication": null, + "/enterprise/2.13/articles/about-web-notifications": null, + "/enterprise/2.13/user/articles/about-web-notifications": null, + "/enterprise/2.13/articles/about-webhooks": null, + "/enterprise/2.13/user/articles/about-webhooks": null, + "/enterprise/2.13/articles/about-wikis": null, + "/enterprise/2.13/user/articles/about-wikis": null, + "/enterprise/2.13/articles/about-writing-and-formatting-on-github": null, + "/enterprise/2.13/user/articles/about-writing-and-formatting-on-github": null, + "/enterprise/2.13/articles/about-your-organizations-news-feed": null, + "/enterprise/2.13/user/articles/about-your-organizations-news-feed": null, + "/enterprise/2.13/articles/about-your-organizations-profile": null, + "/enterprise/2.13/user/articles/about-your-organizations-profile": null, + "/enterprise/2.13/articles/about-your-profile": null, + "/enterprise/2.13/user/articles/about-your-profile": null, + "/enterprise/2.13/articles/access-permissions-on-github": null, + "/enterprise/2.13/user/articles/access-permissions-on-github": null, + "/enterprise/2.13/articles/accessing-an-organization": null, + "/enterprise/2.13/user/articles/accessing-an-organization": null, + "/enterprise/2.13/articles/accessing-basic-repository-data": null, + "/enterprise/2.13/user/articles/accessing-basic-repository-data": null, + "/enterprise/2.13/articles/accessing-github-using-two-factor-authentication": null, + "/enterprise/2.13/user/articles/accessing-github-using-two-factor-authentication": null, + "/enterprise/2.13/articles/accessing-your-notifications": null, + "/enterprise/2.13/user/articles/accessing-your-notifications": null, + "/enterprise/2.13/articles/accessing-your-organizations-settings": null, + "/enterprise/2.13/user/articles/accessing-your-organizations-settings": null, + "/enterprise/2.13/articles/adding-a-file-to-a-repository-using-the-command-line": null, + "/enterprise/2.13/user/articles/adding-a-file-to-a-repository-using-the-command-line": null, + "/enterprise/2.13/articles/adding-a-file-to-a-repository": null, + "/enterprise/2.13/user/articles/adding-a-file-to-a-repository": null, + "/enterprise/2.13/articles/adding-a-jekyll-theme-to-your-github-pages-site": null, + "/enterprise/2.13/user/articles/adding-a-jekyll-theme-to-your-github-pages-site": null, + "/enterprise/2.13/articles/adding-a-license-to-a-repository": null, + "/enterprise/2.13/user/articles/adding-a-license-to-a-repository": null, + "/enterprise/2.13/articles/adding-a-new-gpg-key-to-your-github-account": null, + "/enterprise/2.13/user/articles/adding-a-new-gpg-key-to-your-github-account": null, + "/enterprise/2.13/articles/adding-a-new-ssh-key-to-your-github-account": null, + "/enterprise/2.13/user/articles/adding-a-new-ssh-key-to-your-github-account": null, + "/enterprise/2.13/articles/adding-a-remote": null, + "/enterprise/2.13/user/articles/adding-a-remote": null, + "/enterprise/2.13/articles/adding-an-email-address-to-your-github-account": null, + "/enterprise/2.13/user/articles/adding-an-email-address-to-your-github-account": null, + "/enterprise/2.13/articles/adding-an-existing-project-to-github-using-the-command-line": null, + "/enterprise/2.13/user/articles/adding-an-existing-project-to-github-using-the-command-line": null, + "/enterprise/2.13/articles/adding-issues-and-pull-requests-to-a-project-board": null, + "/enterprise/2.13/user/articles/adding-issues-and-pull-requests-to-a-project-board": null, + "/enterprise/2.13/articles/adding-jekyll-plugins-to-a-github-pages-site": null, + "/enterprise/2.13/user/articles/adding-jekyll-plugins-to-a-github-pages-site": null, + "/enterprise/2.13/articles/adding-notes-to-a-project-board": null, + "/enterprise/2.13/user/articles/adding-notes-to-a-project-board": null, + "/enterprise/2.13/articles/adding-or-editing-wiki-pages": null, + "/enterprise/2.13/user/articles/adding-or-editing-wiki-pages": null, + "/enterprise/2.13/articles/adding-organization-members-to-a-team": null, + "/enterprise/2.13/user/articles/adding-organization-members-to-a-team": null, + "/enterprise/2.13/articles/adding-outside-collaborators-to-repositories-in-your-organization": null, + "/enterprise/2.13/user/articles/adding-outside-collaborators-to-repositories-in-your-organization": null, + "/enterprise/2.13/articles/adding-people-to-your-organization": null, + "/enterprise/2.13/user/articles/adding-people-to-your-organization": null, + "/enterprise/2.13/articles/adding-support-resources-to-your-project": null, + "/enterprise/2.13/user/articles/adding-support-resources-to-your-project": null, + "/enterprise/2.13/articles/additional-customizations-for-github-pages": null, + "/enterprise/2.13/user/articles/additional-customizations-for-github-pages": null, + "/enterprise/2.13/articles/addressing-merge-conflicts": null, + "/enterprise/2.13/user/articles/addressing-merge-conflicts": null, + "/enterprise/2.13/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.13/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.13/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": null, + "/enterprise/2.13/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": null, + "/enterprise/2.13/articles/allowing-people-to-fork-private-repositories-in-your-organization": null, + "/enterprise/2.13/user/articles/allowing-people-to-fork-private-repositories-in-your-organization": null, + "/enterprise/2.13/articles/analyzing-changes-to-a-repositorys-content": null, + "/enterprise/2.13/user/articles/analyzing-changes-to-a-repositorys-content": null, + "/enterprise/2.13/articles/applying-labels-to-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/applying-labels-to-issues-and-pull-requests": null, + "/enterprise/2.13/articles/approving-a-pull-request-with-required-reviews": null, + "/enterprise/2.13/user/articles/approving-a-pull-request-with-required-reviews": null, + "/enterprise/2.13/articles/archiving-a-github-repository": null, + "/enterprise/2.13/user/articles/archiving-a-github-repository": null, + "/enterprise/2.13/articles/archiving-repositories": null, + "/enterprise/2.13/user/articles/archiving-repositories": null, + "/enterprise/2.13/articles/assigning-issues-and-pull-requests-to-other-github-users": null, + "/enterprise/2.13/user/articles/assigning-issues-and-pull-requests-to-other-github-users": null, + "/enterprise/2.13/articles/associating-an-email-with-your-gpg-key": null, + "/enterprise/2.13/user/articles/associating-an-email-with-your-gpg-key": null, + "/enterprise/2.13/articles/associating-milestones-with-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/associating-milestones-with-issues-and-pull-requests": null, + "/enterprise/2.13/articles/associating-text-editors-with-git": null, + "/enterprise/2.13/user/articles/associating-text-editors-with-git": null, + "/enterprise/2.13/articles/authorizing-oauth-apps": null, + "/enterprise/2.13/user/articles/authorizing-oauth-apps": null, + "/enterprise/2.13/articles/autolinked-references-and-urls": null, + "/enterprise/2.13/user/articles/autolinked-references-and-urls": null, + "/enterprise/2.13/articles/backing-up-a-repository": null, + "/enterprise/2.13/user/articles/backing-up-a-repository": null, + "/enterprise/2.13/articles/basic-writing-and-formatting-syntax": null, + "/enterprise/2.13/user/articles/basic-writing-and-formatting-syntax": null, + "/enterprise/2.13/articles/be-social": null, + "/enterprise/2.13/user/articles/be-social": null, + "/enterprise/2.13/articles/caching-your-github-password-in-git": null, + "/enterprise/2.13/user/articles/caching-your-github-password-in-git": null, + "/enterprise/2.13/articles/changing-a-commit-message": null, + "/enterprise/2.13/user/articles/changing-a-commit-message": null, + "/enterprise/2.13/articles/changing-a-persons-role-to-owner": null, + "/enterprise/2.13/user/articles/changing-a-persons-role-to-owner": null, + "/enterprise/2.13/articles/changing-a-remotes-url": null, + "/enterprise/2.13/user/articles/changing-a-remotes-url": null, + "/enterprise/2.13/articles/changing-access-permissions-for-wikis": null, + "/enterprise/2.13/user/articles/changing-access-permissions-for-wikis": null, + "/enterprise/2.13/articles/changing-author-info": null, + "/enterprise/2.13/user/articles/changing-author-info": null, + "/enterprise/2.13/articles/changing-team-visibility": null, + "/enterprise/2.13/user/articles/changing-team-visibility": null, + "/enterprise/2.13/articles/changing-the-base-branch-of-a-pull-request": null, + "/enterprise/2.13/user/articles/changing-the-base-branch-of-a-pull-request": null, + "/enterprise/2.13/articles/changing-your-github-username": null, + "/enterprise/2.13/user/articles/changing-your-github-username": null, + "/enterprise/2.13/articles/changing-your-primary-email-address": null, + "/enterprise/2.13/user/articles/changing-your-primary-email-address": null, + "/enterprise/2.13/articles/checking-for-existing-gpg-keys": null, + "/enterprise/2.13/user/articles/checking-for-existing-gpg-keys": null, + "/enterprise/2.13/articles/checking-for-existing-ssh-keys": null, + "/enterprise/2.13/user/articles/checking-for-existing-ssh-keys": null, + "/enterprise/2.13/articles/checking-out-pull-requests-locally": null, + "/enterprise/2.13/user/articles/checking-out-pull-requests-locally": null, + "/enterprise/2.13/articles/checking-your-commit-and-tag-signature-verification-status": null, + "/enterprise/2.13/user/articles/checking-your-commit-and-tag-signature-verification-status": null, + "/enterprise/2.13/articles/choosing-the-delivery-method-for-your-notifications": null, + "/enterprise/2.13/user/articles/choosing-the-delivery-method-for-your-notifications": null, + "/enterprise/2.13/articles/classifying-your-repository-with-topics": null, + "/enterprise/2.13/user/articles/classifying-your-repository-with-topics": null, + "/enterprise/2.13/articles/cloning-a-repository-from-github": null, + "/enterprise/2.13/user/articles/cloning-a-repository-from-github": null, + "/enterprise/2.13/articles/cloning-a-repository": null, + "/enterprise/2.13/user/articles/cloning-a-repository": null, + "/enterprise/2.13/articles/closing-a-project-board": null, + "/enterprise/2.13/user/articles/closing-a-project-board": null, + "/enterprise/2.13/articles/closing-a-pull-request": null, + "/enterprise/2.13/user/articles/closing-a-pull-request": null, + "/enterprise/2.13/articles/closing-issues-using-keywords": null, + "/enterprise/2.13/user/articles/closing-issues-using-keywords": null, + "/enterprise/2.13/articles/collaborating-on-repositories-with-code-quality-features-enabled": null, + "/enterprise/2.13/user/articles/collaborating-on-repositories-with-code-quality-features-enabled": null, + "/enterprise/2.13/articles/collaborating-with-groups-in-organizations": null, + "/enterprise/2.13/user/articles/collaborating-with-groups-in-organizations": null, + "/enterprise/2.13/articles/collaborating-with-your-team": null, + "/enterprise/2.13/user/articles/collaborating-with-your-team": null, + "/enterprise/2.13/articles/collaboration-with-git-large-file-storage": null, + "/enterprise/2.13/user/articles/collaboration-with-git-large-file-storage": null, + "/enterprise/2.13/articles/commenting-on-a-pull-request": null, + "/enterprise/2.13/user/articles/commenting-on-a-pull-request": null, + "/enterprise/2.13/articles/commit-branch-and-tag-labels": null, + "/enterprise/2.13/user/articles/commit-branch-and-tag-labels": null, + "/enterprise/2.13/articles/commit-exists-on-github-but-not-in-my-local-clone": null, + "/enterprise/2.13/user/articles/commit-exists-on-github-but-not-in-my-local-clone": null, + "/enterprise/2.13/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.13/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.13/articles/comparing-commits-across-time": null, + "/enterprise/2.13/user/articles/comparing-commits-across-time": null, + "/enterprise/2.13/articles/conditions-for-large-files": null, + "/enterprise/2.13/user/articles/conditions-for-large-files": null, + "/enterprise/2.13/articles/configuring-a-publishing-source-for-github-pages": null, + "/enterprise/2.13/user/articles/configuring-a-publishing-source-for-github-pages": null, + "/enterprise/2.13/articles/configuring-a-remote-for-a-fork": null, + "/enterprise/2.13/user/articles/configuring-a-remote-for-a-fork": null, + "/enterprise/2.13/articles/configuring-automation-for-project-boards": null, + "/enterprise/2.13/user/articles/configuring-automation-for-project-boards": null, + "/enterprise/2.13/articles/configuring-commit-rebasing-for-pull-requests": null, + "/enterprise/2.13/user/articles/configuring-commit-rebasing-for-pull-requests": null, + "/enterprise/2.13/articles/configuring-commit-squashing-for-pull-requests": null, + "/enterprise/2.13/user/articles/configuring-commit-squashing-for-pull-requests": null, + "/enterprise/2.13/articles/configuring-git-large-file-storage": null, + "/enterprise/2.13/user/articles/configuring-git-large-file-storage": null, + "/enterprise/2.13/articles/configuring-jekyll-plugins": null, + "/enterprise/2.13/user/articles/configuring-jekyll-plugins": null, + "/enterprise/2.13/articles/configuring-jekyll": null, + "/enterprise/2.13/user/articles/configuring-jekyll": null, + "/enterprise/2.13/articles/configuring-protected-branches": null, + "/enterprise/2.13/user/articles/configuring-protected-branches": null, + "/enterprise/2.13/articles/configuring-pull-request-merges": null, + "/enterprise/2.13/user/articles/configuring-pull-request-merges": null, + "/enterprise/2.13/articles/configuring-two-factor-authentication-recovery-methods": null, + "/enterprise/2.13/user/articles/configuring-two-factor-authentication-recovery-methods": null, + "/enterprise/2.13/articles/configuring-two-factor-authentication": null, + "/enterprise/2.13/user/articles/configuring-two-factor-authentication": null, + "/enterprise/2.13/articles/connecting-to-github-with-ssh": null, + "/enterprise/2.13/user/articles/connecting-to-github-with-ssh": null, + "/enterprise/2.13/articles/connecting-with-third-party-applications": null, + "/enterprise/2.13/user/articles/connecting-with-third-party-applications": null, + "/enterprise/2.13/articles/converting-a-user-into-an-organization": null, + "/enterprise/2.13/user/articles/converting-a-user-into-an-organization": null, + "/enterprise/2.13/articles/converting-an-organization-into-a-user": null, + "/enterprise/2.13/user/articles/converting-an-organization-into-a-user": null, + "/enterprise/2.13/articles/converting-an-organization-member-to-an-outside-collaborator": null, + "/enterprise/2.13/user/articles/converting-an-organization-member-to-an-outside-collaborator": null, + "/enterprise/2.13/articles/converting-an-outside-collaborator-to-an-organization-member": null, + "/enterprise/2.13/user/articles/converting-an-outside-collaborator-to-an-organization-member": null, + "/enterprise/2.13/articles/create-a-repo": null, + "/enterprise/2.13/user/articles/create-a-repo": null, + "/enterprise/2.13/articles/creating-a-commit-with-multiple-authors": null, + "/enterprise/2.13/user/articles/creating-a-commit-with-multiple-authors": null, + "/enterprise/2.13/articles/creating-a-custom-404-page-for-your-github-pages-site": null, + "/enterprise/2.13/user/articles/creating-a-custom-404-page-for-your-github-pages-site": null, + "/enterprise/2.13/articles/creating-a-footer-or-sidebar-for-your-wiki": null, + "/enterprise/2.13/user/articles/creating-a-footer-or-sidebar-for-your-wiki": null, + "/enterprise/2.13/articles/creating-a-label": null, + "/enterprise/2.13/user/articles/creating-a-label": null, + "/enterprise/2.13/articles/creating-a-new-organization-from-scratch": null, + "/enterprise/2.13/user/articles/creating-a-new-organization-from-scratch": null, + "/enterprise/2.13/articles/creating-a-new-repository": null, + "/enterprise/2.13/user/articles/creating-a-new-repository": null, + "/enterprise/2.13/articles/creating-a-permanent-link-to-a-code-snippet": null, + "/enterprise/2.13/user/articles/creating-a-permanent-link-to-a-code-snippet": null, + "/enterprise/2.13/articles/creating-a-personal-access-token-for-the-command-line": null, + "/enterprise/2.13/user/articles/creating-a-personal-access-token-for-the-command-line": null, + "/enterprise/2.13/articles/creating-a-project-board": null, + "/enterprise/2.13/user/articles/creating-a-project-board": null, + "/enterprise/2.13/articles/creating-a-pull-request-from-a-fork": null, + "/enterprise/2.13/user/articles/creating-a-pull-request-from-a-fork": null, + "/enterprise/2.13/articles/creating-a-pull-request-template-for-your-repository": null, + "/enterprise/2.13/user/articles/creating-a-pull-request-template-for-your-repository": null, + "/enterprise/2.13/articles/creating-a-pull-request": null, + "/enterprise/2.13/user/articles/creating-a-pull-request": null, + "/enterprise/2.13/articles/creating-a-repository-on-github": null, + "/enterprise/2.13/user/articles/creating-a-repository-on-github": null, + "/enterprise/2.13/articles/creating-a-saved-reply": null, + "/enterprise/2.13/user/articles/creating-a-saved-reply": null, + "/enterprise/2.13/articles/creating-a-strong-password": null, + "/enterprise/2.13/user/articles/creating-a-strong-password": null, + "/enterprise/2.13/articles/creating-a-team-discussion": null, + "/enterprise/2.13/user/articles/creating-a-team-discussion": null, + "/enterprise/2.13/articles/creating-a-team": null, + "/enterprise/2.13/user/articles/creating-a-team": null, + "/enterprise/2.13/articles/creating-an-issue": null, + "/enterprise/2.13/user/articles/creating-an-issue": null, + "/enterprise/2.13/articles/creating-an-issues-only-repository": null, + "/enterprise/2.13/user/articles/creating-an-issues-only-repository": null, + "/enterprise/2.13/articles/creating-and-deleting-branches-within-your-repository": null, + "/enterprise/2.13/user/articles/creating-and-deleting-branches-within-your-repository": null, + "/enterprise/2.13/articles/creating-and-editing-milestones-for-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests": null, + "/enterprise/2.13/articles/creating-and-highlighting-code-blocks": null, + "/enterprise/2.13/user/articles/creating-and-highlighting-code-blocks": null, + "/enterprise/2.13/articles/creating-gists": null, + "/enterprise/2.13/user/articles/creating-gists": null, + "/enterprise/2.13/articles/creating-new-files": null, + "/enterprise/2.13/user/articles/creating-new-files": null, + "/enterprise/2.13/articles/creating-pages-with-the-automatic-generator": null, + "/enterprise/2.13/user/articles/creating-pages-with-the-automatic-generator": null, + "/enterprise/2.13/articles/creating-project-pages-using-the-command-line": null, + "/enterprise/2.13/user/articles/creating-project-pages-using-the-command-line": null, + "/enterprise/2.13/articles/creating-releases": null, + "/enterprise/2.13/user/articles/creating-releases": null, + "/enterprise/2.13/articles/customizing-css-and-html-in-your-jekyll-theme": null, + "/enterprise/2.13/user/articles/customizing-css-and-html-in-your-jekyll-theme": null, + "/enterprise/2.13/articles/customizing-how-changed-files-appear-on-github": null, + "/enterprise/2.13/user/articles/customizing-how-changed-files-appear-on-github": null, + "/enterprise/2.13/articles/customizing-your-profile": null, + "/enterprise/2.13/user/articles/customizing-your-profile": null, + "/enterprise/2.13/articles/dealing-with-line-endings": null, + "/enterprise/2.13/user/articles/dealing-with-line-endings": null, + "/enterprise/2.13/articles/dealing-with-non-fast-forward-errors": null, + "/enterprise/2.13/user/articles/dealing-with-non-fast-forward-errors": null, + "/enterprise/2.13/articles/defining-the-mergeability-of-pull-requests": null, + "/enterprise/2.13/user/articles/defining-the-mergeability-of-pull-requests": null, + "/enterprise/2.13/articles/deleting-a-label": null, + "/enterprise/2.13/user/articles/deleting-a-label": null, + "/enterprise/2.13/articles/deleting-a-project-board": null, + "/enterprise/2.13/user/articles/deleting-a-project-board": null, + "/enterprise/2.13/articles/deleting-a-repository": null, + "/enterprise/2.13/user/articles/deleting-a-repository": null, + "/enterprise/2.13/articles/deleting-a-saved-reply": null, + "/enterprise/2.13/user/articles/deleting-a-saved-reply": null, + "/enterprise/2.13/articles/deleting-a-team": null, + "/enterprise/2.13/user/articles/deleting-a-team": null, + "/enterprise/2.13/articles/deleting-an-organization-account": null, + "/enterprise/2.13/user/articles/deleting-an-organization-account": null, + "/enterprise/2.13/articles/deleting-and-restoring-branches-in-a-pull-request": null, + "/enterprise/2.13/user/articles/deleting-and-restoring-branches-in-a-pull-request": null, + "/enterprise/2.13/articles/deleting-files": null, + "/enterprise/2.13/user/articles/deleting-files": null, + "/enterprise/2.13/articles/deleting-your-user-account": null, + "/enterprise/2.13/user/articles/deleting-your-user-account": null, + "/enterprise/2.13/articles/differences-between-commit-views": null, + "/enterprise/2.13/user/articles/differences-between-commit-views": null, + "/enterprise/2.13/articles/differences-between-user-and-organization-accounts": null, + "/enterprise/2.13/user/articles/differences-between-user-and-organization-accounts": null, + "/enterprise/2.13/articles/disabling-issues": null, + "/enterprise/2.13/user/articles/disabling-issues": null, + "/enterprise/2.13/articles/disabling-project-boards-in-a-repository": null, + "/enterprise/2.13/user/articles/disabling-project-boards-in-a-repository": null, + "/enterprise/2.13/articles/disabling-project-boards-in-your-organization": null, + "/enterprise/2.13/user/articles/disabling-project-boards-in-your-organization": null, + "/enterprise/2.13/articles/disabling-team-discussions-for-your-organization": null, + "/enterprise/2.13/user/articles/disabling-team-discussions-for-your-organization": null, + "/enterprise/2.13/articles/disabling-two-factor-authentication-for-your-personal-account": null, + "/enterprise/2.13/user/articles/disabling-two-factor-authentication-for-your-personal-account": null, + "/enterprise/2.13/articles/disabling-wikis": null, + "/enterprise/2.13/user/articles/disabling-wikis": null, + "/enterprise/2.13/articles/dismissing-a-pull-request-review": null, + "/enterprise/2.13/user/articles/dismissing-a-pull-request-review": null, + "/enterprise/2.13/articles/distributing-large-binaries": null, + "/enterprise/2.13/user/articles/distributing-large-binaries": null, + "/enterprise/2.13/articles/documenting-your-project-with-wikis": null, + "/enterprise/2.13/user/articles/documenting-your-project-with-wikis": null, + "/enterprise/2.13/articles/duplicating-a-repository": null, + "/enterprise/2.13/user/articles/duplicating-a-repository": null, + "/enterprise/2.13/articles/editing-a-label": null, + "/enterprise/2.13/user/articles/editing-a-label": null, + "/enterprise/2.13/articles/editing-a-project-board": null, + "/enterprise/2.13/user/articles/editing-a-project-board": null, + "/enterprise/2.13/articles/editing-a-saved-reply": null, + "/enterprise/2.13/user/articles/editing-a-saved-reply": null, + "/enterprise/2.13/articles/editing-and-deleting-releases": null, + "/enterprise/2.13/user/articles/editing-and-deleting-releases": null, + "/enterprise/2.13/articles/editing-files-in-another-users-repository": null, + "/enterprise/2.13/user/articles/editing-files-in-another-users-repository": null, + "/enterprise/2.13/articles/editing-files-in-your-repository": null, + "/enterprise/2.13/user/articles/editing-files-in-your-repository": null, + "/enterprise/2.13/articles/editing-or-deleting-a-team-discussion": null, + "/enterprise/2.13/user/articles/editing-or-deleting-a-team-discussion": null, + "/enterprise/2.13/articles/editing-wiki-content": null, + "/enterprise/2.13/user/articles/editing-wiki-content": null, + "/enterprise/2.13/articles/emoji-on-github-pages": null, + "/enterprise/2.13/user/articles/emoji-on-github-pages": null, + "/enterprise/2.13/articles/enabling-branch-restrictions": null, + "/enterprise/2.13/user/articles/enabling-branch-restrictions": null, + "/enterprise/2.13/articles/enabling-required-commit-signing": null, + "/enterprise/2.13/user/articles/enabling-required-commit-signing": null, + "/enterprise/2.13/articles/enabling-required-reviews-for-pull-requests": null, + "/enterprise/2.13/user/articles/enabling-required-reviews-for-pull-requests": null, + "/enterprise/2.13/articles/enabling-required-status-checks": null, + "/enterprise/2.13/user/articles/enabling-required-status-checks": null, + "/enterprise/2.13/articles/error-agent-admitted-failure-to-sign": null, + "/enterprise/2.13/user/articles/error-agent-admitted-failure-to-sign": null, + "/enterprise/2.13/articles/error-bad-file-number": null, + "/enterprise/2.13/user/articles/error-bad-file-number": null, + "/enterprise/2.13/articles/error-key-already-in-use": null, + "/enterprise/2.13/user/articles/error-key-already-in-use": null, + "/enterprise/2.13/articles/error-permission-denied-publickey": null, + "/enterprise/2.13/user/articles/error-permission-denied-publickey": null, + "/enterprise/2.13/articles/error-permission-to-userrepo-denied-to-other-user": null, + "/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-other-user": null, + "/enterprise/2.13/articles/error-permission-to-userrepo-denied-to-userother-repo": null, + "/enterprise/2.13/user/articles/error-permission-to-userrepo-denied-to-userother-repo": null, + "/enterprise/2.13/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": null, + "/enterprise/2.13/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": null, + "/enterprise/2.13/articles/error-repository-not-found": null, + "/enterprise/2.13/user/articles/error-repository-not-found": null, + "/enterprise/2.13/articles/error-ssh-add-illegal-option----k": null, + "/enterprise/2.13/user/articles/error-ssh-add-illegal-option----k": null, + "/enterprise/2.13/articles/error-were-doing-an-ssh-key-audit": null, + "/enterprise/2.13/user/articles/error-were-doing-an-ssh-key-audit": null, + "/enterprise/2.13/articles/fetching-a-remote": null, + "/enterprise/2.13/user/articles/fetching-a-remote": null, + "/enterprise/2.13/articles/file-attachments-on-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/file-attachments-on-issues-and-pull-requests": null, + "/enterprise/2.13/articles/files-that-start-with-an-underscore-are-missing": null, + "/enterprise/2.13/user/articles/files-that-start-with-an-underscore-are-missing": null, + "/enterprise/2.13/articles/filtering-cards-on-a-project-board": null, + "/enterprise/2.13/user/articles/filtering-cards-on-a-project-board": null, + "/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-assignees": null, + "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-assignees": null, + "/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-labels": null, + "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-labels": null, + "/enterprise/2.13/articles/filtering-issues-and-pull-requests-by-milestone": null, + "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests-by-milestone": null, + "/enterprise/2.13/articles/filtering-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/filtering-issues-and-pull-requests": null, + "/enterprise/2.13/articles/filtering-pull-requests-by-review-status": null, + "/enterprise/2.13/user/articles/filtering-pull-requests-by-review-status": null, + "/enterprise/2.13/articles/finding-changed-methods-and-functions-in-a-pull-request": null, + "/enterprise/2.13/user/articles/finding-changed-methods-and-functions-in-a-pull-request": null, + "/enterprise/2.13/articles/finding-files-on-github": null, + "/enterprise/2.13/user/articles/finding-files-on-github": null, + "/enterprise/2.13/articles/finding-information-in-a-repository": null, + "/enterprise/2.13/user/articles/finding-information-in-a-repository": null, + "/enterprise/2.13/articles/following-people": null, + "/enterprise/2.13/user/articles/following-people": null, + "/enterprise/2.13/articles/fork-a-repo": null, + "/enterprise/2.13/user/articles/fork-a-repo": null, + "/enterprise/2.13/articles/forking-and-cloning-gists": null, + "/enterprise/2.13/user/articles/forking-and-cloning-gists": null, + "/enterprise/2.13/articles/further-reading-on-github-pages": null, + "/enterprise/2.13/user/articles/further-reading-on-github-pages": null, + "/enterprise/2.13/articles/generating-a-new-gpg-key": null, + "/enterprise/2.13/user/articles/generating-a-new-gpg-key": null, + "/enterprise/2.13/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": null, + "/enterprise/2.13/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": null, + "/enterprise/2.13/articles/generic-jekyll-build-failures": null, + "/enterprise/2.13/user/articles/generic-jekyll-build-failures": null, + "/enterprise/2.13/articles/getting-permanent-links-to-files": null, + "/enterprise/2.13/user/articles/getting-permanent-links-to-files": null, + "/enterprise/2.13/articles/getting-started-with-notifications": null, + "/enterprise/2.13/user/articles/getting-started-with-notifications": null, + "/enterprise/2.13/articles/getting-started-with-searching-on-github": null, + "/enterprise/2.13/user/articles/getting-started-with-searching-on-github": null, + "/enterprise/2.13/articles/getting-started-with-the-api": null, + "/enterprise/2.13/user/articles/getting-started-with-the-api": null, + "/enterprise/2.13/articles/getting-started-with-writing-and-formatting-on-github": null, + "/enterprise/2.13/user/articles/getting-started-with-writing-and-formatting-on-github": null, + "/enterprise/2.13/articles/getting-the-download-count-for-your-releases": null, + "/enterprise/2.13/user/articles/getting-the-download-count-for-your-releases": null, + "/enterprise/2.13/articles/git-and-github-learning-resources": null, + "/enterprise/2.13/user/articles/git-and-github-learning-resources": null, + "/enterprise/2.13/articles/git-automation-with-oauth-tokens": null, + "/enterprise/2.13/user/articles/git-automation-with-oauth-tokens": null, + "/enterprise/2.13/articles/git-cheatsheet": null, + "/enterprise/2.13/user/articles/git-cheatsheet": null, + "/enterprise/2.13/articles/github-flow": null, + "/enterprise/2.13/user/articles/github-flow": null, + "/enterprise/2.13/articles/github-glossary": null, + "/enterprise/2.13/user/articles/github-glossary": null, + "/enterprise/2.13/articles/giving-team-maintainer-permissions-to-an-organization-member": null, + "/enterprise/2.13/user/articles/giving-team-maintainer-permissions-to-an-organization-member": null, + "/enterprise/2.13/articles/https-cloning-errors": null, + "/enterprise/2.13/user/articles/https-cloning-errors": null, + "/enterprise/2.13/articles/ignoring-files": null, + "/enterprise/2.13/user/articles/ignoring-files": null, + "/enterprise/2.13/articles/importing-a-git-repository-using-the-command-line": null, + "/enterprise/2.13/user/articles/importing-a-git-repository-using-the-command-line": null, + "/enterprise/2.13/articles/importing-source-code-to-github": null, + "/enterprise/2.13/user/articles/importing-source-code-to-github": null, + "/enterprise/2.13/articles/incorporating-changes-from-a-pull-request": null, + "/enterprise/2.13/user/articles/incorporating-changes-from-a-pull-request": null, + "/enterprise/2.13/articles/initializing-an-empty-repository-with-a-readme": null, + "/enterprise/2.13/user/articles/initializing-an-empty-repository-with-a-readme": null, + "/enterprise/2.13/articles/installing-git-large-file-storage": null, + "/enterprise/2.13/user/articles/installing-git-large-file-storage": null, + "/enterprise/2.13/articles/integrating-jira-with-your-organization-project-board": null, + "/enterprise/2.13/user/articles/integrating-jira-with-your-organization-project-board": null, + "/enterprise/2.13/articles/integrating-jira-with-your-personal-projects": null, + "/enterprise/2.13/user/articles/integrating-jira-with-your-personal-projects": null, + "/enterprise/2.13/articles/inviting-collaborators-to-a-personal-repository": null, + "/enterprise/2.13/user/articles/inviting-collaborators-to-a-personal-repository": null, + "/enterprise/2.13/articles/keeping-your-account-and-data-secure": null, + "/enterprise/2.13/user/articles/keeping-your-account-and-data-secure": null, + "/enterprise/2.13/articles/keeping-your-organization-secure": null, + "/enterprise/2.13/user/articles/keeping-your-organization-secure": null, + "/enterprise/2.13/articles/labeling-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/labeling-issues-and-pull-requests": null, + "/enterprise/2.13/articles/licensing-a-repository": null, + "/enterprise/2.13/user/articles/licensing-a-repository": null, + "/enterprise/2.13/articles/limits-for-viewing-content-and-diffs-in-a-repository": null, + "/enterprise/2.13/user/articles/limits-for-viewing-content-and-diffs-in-a-repository": null, + "/enterprise/2.13/articles/linking-to-releases": null, + "/enterprise/2.13/user/articles/linking-to-releases": null, + "/enterprise/2.13/articles/listing-the-forks-of-a-repository": null, + "/enterprise/2.13/user/articles/listing-the-forks-of-a-repository": null, + "/enterprise/2.13/articles/listing-the-repositories-youre-watching": null, + "/enterprise/2.13/user/articles/listing-the-repositories-youre-watching": null, + "/enterprise/2.13/articles/locking-conversations": null, + "/enterprise/2.13/user/articles/locking-conversations": null, + "/enterprise/2.13/articles/managing-access-to-your-organizations-repositories": null, + "/enterprise/2.13/user/articles/managing-access-to-your-organizations-repositories": null, + "/enterprise/2.13/articles/managing-access-to-your-personal-repositories": null, + "/enterprise/2.13/user/articles/managing-access-to-your-personal-repositories": null, + "/enterprise/2.13/articles/managing-an-individuals-access-to-an-organization-repository": null, + "/enterprise/2.13/user/articles/managing-an-individuals-access-to-an-organization-repository": null, + "/enterprise/2.13/articles/managing-branches-in-your-repository": null, + "/enterprise/2.13/user/articles/managing-branches-in-your-repository": null, + "/enterprise/2.13/articles/managing-commit-signature-verification": null, + "/enterprise/2.13/user/articles/managing-commit-signature-verification": null, + "/enterprise/2.13/articles/managing-contribution-graphs-on-your-profile": null, + "/enterprise/2.13/user/articles/managing-contribution-graphs-on-your-profile": null, + "/enterprise/2.13/articles/managing-disruptive-comments": null, + "/enterprise/2.13/user/articles/managing-disruptive-comments": null, + "/enterprise/2.13/articles/managing-email-preferences": null, + "/enterprise/2.13/user/articles/managing-email-preferences": null, + "/enterprise/2.13/articles/managing-files-on-github": null, + "/enterprise/2.13/user/articles/managing-files-on-github": null, + "/enterprise/2.13/articles/managing-files-using-the-command-line": null, + "/enterprise/2.13/user/articles/managing-files-using-the-command-line": null, + "/enterprise/2.13/articles/managing-membership-in-your-organization": null, + "/enterprise/2.13/user/articles/managing-membership-in-your-organization": null, + "/enterprise/2.13/articles/managing-organization-settings": null, + "/enterprise/2.13/user/articles/managing-organization-settings": null, + "/enterprise/2.13/articles/managing-peoples-access-to-your-organization-with-roles": null, + "/enterprise/2.13/user/articles/managing-peoples-access-to-your-organization-with-roles": null, + "/enterprise/2.13/articles/managing-project-boards": null, + "/enterprise/2.13/user/articles/managing-project-boards": null, + "/enterprise/2.13/articles/managing-repository-settings": null, + "/enterprise/2.13/user/articles/managing-repository-settings": null, + "/enterprise/2.13/articles/managing-team-access-to-an-organization-repository": null, + "/enterprise/2.13/user/articles/managing-team-access-to-an-organization-repository": null, + "/enterprise/2.13/articles/managing-user-account-settings": null, + "/enterprise/2.13/user/articles/managing-user-account-settings": null, + "/enterprise/2.13/articles/managing-your-membership-in-organizations": null, + "/enterprise/2.13/user/articles/managing-your-membership-in-organizations": null, + "/enterprise/2.13/articles/managing-your-notifications": null, + "/enterprise/2.13/user/articles/managing-your-notifications": null, + "/enterprise/2.13/articles/managing-your-stars": null, + "/enterprise/2.13/user/articles/managing-your-stars": null, + "/enterprise/2.13/articles/managing-your-work-with-issues": null, + "/enterprise/2.13/user/articles/managing-your-work-with-issues": null, + "/enterprise/2.13/articles/manually-creating-a-single-issue-template-for-your-repository": null, + "/enterprise/2.13/user/articles/manually-creating-a-single-issue-template-for-your-repository": null, + "/enterprise/2.13/articles/mapping-geojson-files-on-github": null, + "/enterprise/2.13/user/articles/mapping-geojson-files-on-github": null, + "/enterprise/2.13/articles/marking-notifications-as-read": null, + "/enterprise/2.13/user/articles/marking-notifications-as-read": null, + "/enterprise/2.13/articles/mentions-on-github-pages": null, + "/enterprise/2.13/user/articles/mentions-on-github-pages": null, + "/enterprise/2.13/articles/merging-a-pull-request": null, + "/enterprise/2.13/user/articles/merging-a-pull-request": null, + "/enterprise/2.13/articles/merging-an-upstream-repository-into-your-fork": null, + "/enterprise/2.13/user/articles/merging-an-upstream-repository-into-your-fork": null, + "/enterprise/2.13/articles/mime-types-on-github-pages": null, + "/enterprise/2.13/user/articles/mime-types-on-github-pages": null, + "/enterprise/2.13/articles/moderating-comments-and-conversations": null, + "/enterprise/2.13/user/articles/moderating-comments-and-conversations": null, + "/enterprise/2.13/articles/moving-a-file-in-your-repository-to-git-large-file-storage": null, + "/enterprise/2.13/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage": null, + "/enterprise/2.13/articles/moving-a-file-to-a-new-location-using-the-command-line": null, + "/enterprise/2.13/user/articles/moving-a-file-to-a-new-location-using-the-command-line": null, + "/enterprise/2.13/articles/moving-a-file-to-a-new-location": null, + "/enterprise/2.13/user/articles/moving-a-file-to-a-new-location": null, + "/enterprise/2.13/articles/moving-a-team-in-your-organizations-hierarchy": null, + "/enterprise/2.13/user/articles/moving-a-team-in-your-organizations-hierarchy": null, + "/enterprise/2.13/articles/opening-an-issue-from-code": null, + "/enterprise/2.13/user/articles/opening-an-issue-from-code": null, + "/enterprise/2.13/articles/organizing-information-with-tables": null, + "/enterprise/2.13/user/articles/organizing-information-with-tables": null, + "/enterprise/2.13/articles/organizing-members-into-teams": null, + "/enterprise/2.13/user/articles/organizing-members-into-teams": null, + "/enterprise/2.13/articles/page-build-failed-config-file-error": null, + "/enterprise/2.13/user/articles/page-build-failed-config-file-error": null, + "/enterprise/2.13/articles/page-build-failed-date-is-not-a-valid-datetime": null, + "/enterprise/2.13/user/articles/page-build-failed-date-is-not-a-valid-datetime": null, + "/enterprise/2.13/articles/page-build-failed-file-does-not-exist-in-includes-directory": null, + "/enterprise/2.13/user/articles/page-build-failed-file-does-not-exist-in-includes-directory": null, + "/enterprise/2.13/articles/page-build-failed-file-is-a-symlink": null, + "/enterprise/2.13/user/articles/page-build-failed-file-is-a-symlink": null, + "/enterprise/2.13/articles/page-build-failed-file-is-not-properly-utf-8-encoded": null, + "/enterprise/2.13/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded": null, + "/enterprise/2.13/articles/page-build-failed-invalid-highlighter-language": null, + "/enterprise/2.13/user/articles/page-build-failed-invalid-highlighter-language": null, + "/enterprise/2.13/articles/page-build-failed-invalid-post-date": null, + "/enterprise/2.13/user/articles/page-build-failed-invalid-post-date": null, + "/enterprise/2.13/articles/page-build-failed-invalid-sass-or-scss": null, + "/enterprise/2.13/user/articles/page-build-failed-invalid-sass-or-scss": null, + "/enterprise/2.13/articles/page-build-failed-invalid-submodule": null, + "/enterprise/2.13/user/articles/page-build-failed-invalid-submodule": null, + "/enterprise/2.13/articles/page-build-failed-invalid-yaml-in-data-file": null, + "/enterprise/2.13/user/articles/page-build-failed-invalid-yaml-in-data-file": null, + "/enterprise/2.13/articles/page-build-failed-markdown-errors": null, + "/enterprise/2.13/user/articles/page-build-failed-markdown-errors": null, + "/enterprise/2.13/articles/page-build-failed-missing-docs-folder": null, + "/enterprise/2.13/user/articles/page-build-failed-missing-docs-folder": null, + "/enterprise/2.13/articles/page-build-failed-missing-submodule": null, + "/enterprise/2.13/user/articles/page-build-failed-missing-submodule": null, + "/enterprise/2.13/articles/page-build-failed-relative-permalinks-configured": null, + "/enterprise/2.13/user/articles/page-build-failed-relative-permalinks-configured": null, + "/enterprise/2.13/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": null, + "/enterprise/2.13/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": null, + "/enterprise/2.13/articles/page-build-failed-syntax-error-in-for-loop": null, + "/enterprise/2.13/user/articles/page-build-failed-syntax-error-in-for-loop": null, + "/enterprise/2.13/articles/page-build-failed-tag-not-properly-closed": null, + "/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-closed": null, + "/enterprise/2.13/articles/page-build-failed-tag-not-properly-terminated": null, + "/enterprise/2.13/user/articles/page-build-failed-tag-not-properly-terminated": null, + "/enterprise/2.13/articles/page-build-failed-unknown-tag-error": null, + "/enterprise/2.13/user/articles/page-build-failed-unknown-tag-error": null, + "/enterprise/2.13/articles/permission-levels-for-a-user-account-repository": null, + "/enterprise/2.13/user/articles/permission-levels-for-a-user-account-repository": null, + "/enterprise/2.13/articles/permission-levels-for-an-organization": null, + "/enterprise/2.13/user/articles/permission-levels-for-an-organization": null, + "/enterprise/2.13/articles/personalizing-your-profile": null, + "/enterprise/2.13/user/articles/personalizing-your-profile": null, + "/enterprise/2.13/articles/pinning-a-team-discussion": null, + "/enterprise/2.13/user/articles/pinning-a-team-discussion": null, + "/enterprise/2.13/articles/pinning-items-to-your-profile": null, + "/enterprise/2.13/user/articles/pinning-items-to-your-profile": null, + "/enterprise/2.13/articles/preparing-to-require-two-factor-authentication-in-your-organization": null, + "/enterprise/2.13/user/articles/preparing-to-require-two-factor-authentication-in-your-organization": null, + "/enterprise/2.13/articles/preventing-unauthorized-access": null, + "/enterprise/2.13/user/articles/preventing-unauthorized-access": null, + "/enterprise/2.13/articles/proposing-changes-to-your-work-with-pull-requests": null, + "/enterprise/2.13/user/articles/proposing-changes-to-your-work-with-pull-requests": null, + "/enterprise/2.13/articles/publicizing-or-hiding-organization-membership": null, + "/enterprise/2.13/user/articles/publicizing-or-hiding-organization-membership": null, + "/enterprise/2.13/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": null, + "/enterprise/2.13/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": null, + "/enterprise/2.13/articles/pushing-to-a-remote": null, + "/enterprise/2.13/user/articles/pushing-to-a-remote": null, + "/enterprise/2.13/articles/recovering-your-account-if-you-lose-your-2fa-credentials": null, + "/enterprise/2.13/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials": null, + "/enterprise/2.13/articles/recovering-your-ssh-key-passphrase": null, + "/enterprise/2.13/user/articles/recovering-your-ssh-key-passphrase": null, + "/enterprise/2.13/articles/redirects-on-github-pages": null, + "/enterprise/2.13/user/articles/redirects-on-github-pages": null, + "/enterprise/2.13/articles/reinstating-a-former-member-of-your-organization": null, + "/enterprise/2.13/user/articles/reinstating-a-former-member-of-your-organization": null, + "/enterprise/2.13/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": null, + "/enterprise/2.13/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": null, + "/enterprise/2.13/articles/remembering-your-github-username-or-email": null, + "/enterprise/2.13/user/articles/remembering-your-github-username-or-email": null, + "/enterprise/2.13/articles/removing-a-collaborator-from-a-personal-repository": null, + "/enterprise/2.13/user/articles/removing-a-collaborator-from-a-personal-repository": null, + "/enterprise/2.13/articles/removing-a-member-from-your-organization": null, + "/enterprise/2.13/user/articles/removing-a-member-from-your-organization": null, + "/enterprise/2.13/articles/removing-a-remote": null, + "/enterprise/2.13/user/articles/removing-a-remote": null, + "/enterprise/2.13/articles/removing-an-outside-collaborator-from-an-organization-repository": null, + "/enterprise/2.13/user/articles/removing-an-outside-collaborator-from-an-organization-repository": null, + "/enterprise/2.13/articles/removing-files-from-a-repositorys-history": null, + "/enterprise/2.13/user/articles/removing-files-from-a-repositorys-history": null, + "/enterprise/2.13/articles/removing-files-from-git-large-file-storage": null, + "/enterprise/2.13/user/articles/removing-files-from-git-large-file-storage": null, + "/enterprise/2.13/articles/removing-organization-members-from-a-team": null, + "/enterprise/2.13/user/articles/removing-organization-members-from-a-team": null, + "/enterprise/2.13/articles/removing-sensitive-data-from-a-repository": null, + "/enterprise/2.13/user/articles/removing-sensitive-data-from-a-repository": null, + "/enterprise/2.13/articles/removing-yourself-from-a-collaborators-repository": null, + "/enterprise/2.13/user/articles/removing-yourself-from-a-collaborators-repository": null, + "/enterprise/2.13/articles/removing-yourself-from-an-organization": null, + "/enterprise/2.13/user/articles/removing-yourself-from-an-organization": null, + "/enterprise/2.13/articles/renaming-a-file-using-the-command-line": null, + "/enterprise/2.13/user/articles/renaming-a-file-using-the-command-line": null, + "/enterprise/2.13/articles/renaming-a-file": null, + "/enterprise/2.13/user/articles/renaming-a-file": null, + "/enterprise/2.13/articles/renaming-a-remote": null, + "/enterprise/2.13/user/articles/renaming-a-remote": null, + "/enterprise/2.13/articles/renaming-a-repository": null, + "/enterprise/2.13/user/articles/renaming-a-repository": null, + "/enterprise/2.13/articles/renaming-a-team": null, + "/enterprise/2.13/user/articles/renaming-a-team": null, + "/enterprise/2.13/articles/renaming-an-organization": null, + "/enterprise/2.13/user/articles/renaming-an-organization": null, + "/enterprise/2.13/articles/rendering-and-diffing-images": null, + "/enterprise/2.13/user/articles/rendering-and-diffing-images": null, + "/enterprise/2.13/articles/rendering-csv-and-tsv-data": null, + "/enterprise/2.13/user/articles/rendering-csv-and-tsv-data": null, + "/enterprise/2.13/articles/rendering-differences-in-prose-documents": null, + "/enterprise/2.13/user/articles/rendering-differences-in-prose-documents": null, + "/enterprise/2.13/articles/rendering-pdf-documents": null, + "/enterprise/2.13/user/articles/rendering-pdf-documents": null, + "/enterprise/2.13/articles/repository-metadata-on-github-pages": null, + "/enterprise/2.13/user/articles/repository-metadata-on-github-pages": null, + "/enterprise/2.13/articles/repository-permission-levels-for-an-organization": null, + "/enterprise/2.13/user/articles/repository-permission-levels-for-an-organization": null, + "/enterprise/2.13/articles/requesting-a-pull-request-review": null, + "/enterprise/2.13/user/articles/requesting-a-pull-request-review": null, + "/enterprise/2.13/articles/requesting-to-add-a-child-team": null, + "/enterprise/2.13/user/articles/requesting-to-add-a-child-team": null, + "/enterprise/2.13/articles/requiring-two-factor-authentication-in-your-organization": null, + "/enterprise/2.13/user/articles/requiring-two-factor-authentication-in-your-organization": null, + "/enterprise/2.13/articles/resolving-a-merge-conflict-on-github": null, + "/enterprise/2.13/user/articles/resolving-a-merge-conflict-on-github": null, + "/enterprise/2.13/articles/resolving-a-merge-conflict-using-the-command-line": null, + "/enterprise/2.13/user/articles/resolving-a-merge-conflict-using-the-command-line": null, + "/enterprise/2.13/articles/resolving-git-large-file-storage-upload-failures": null, + "/enterprise/2.13/user/articles/resolving-git-large-file-storage-upload-failures": null, + "/enterprise/2.13/articles/resolving-merge-conflicts-after-a-git-rebase": null, + "/enterprise/2.13/user/articles/resolving-merge-conflicts-after-a-git-rebase": null, + "/enterprise/2.13/articles/restricting-repository-creation-in-your-organization": null, + "/enterprise/2.13/user/articles/restricting-repository-creation-in-your-organization": null, + "/enterprise/2.13/articles/restricting-repository-visibility-changes-in-your-organization": null, + "/enterprise/2.13/user/articles/restricting-repository-visibility-changes-in-your-organization": null, + "/enterprise/2.13/articles/reverting-a-pull-request": null, + "/enterprise/2.13/user/articles/reverting-a-pull-request": null, + "/enterprise/2.13/articles/reviewing-changes-in-pull-requests": null, + "/enterprise/2.13/user/articles/reviewing-changes-in-pull-requests": null, + "/enterprise/2.13/articles/reviewing-proposed-changes-in-a-pull-request": null, + "/enterprise/2.13/user/articles/reviewing-proposed-changes-in-a-pull-request": null, + "/enterprise/2.13/articles/reviewing-the-audit-log-for-your-organization": null, + "/enterprise/2.13/user/articles/reviewing-the-audit-log-for-your-organization": null, + "/enterprise/2.13/articles/reviewing-your-authorized-applications-oauth": null, + "/enterprise/2.13/user/articles/reviewing-your-authorized-applications-oauth": null, + "/enterprise/2.13/articles/reviewing-your-authorized-integrations": null, + "/enterprise/2.13/user/articles/reviewing-your-authorized-integrations": null, + "/enterprise/2.13/articles/reviewing-your-deploy-keys": null, + "/enterprise/2.13/user/articles/reviewing-your-deploy-keys": null, + "/enterprise/2.13/articles/reviewing-your-organizations-installed-integrations": null, + "/enterprise/2.13/user/articles/reviewing-your-organizations-installed-integrations": null, + "/enterprise/2.13/articles/reviewing-your-security-log": null, + "/enterprise/2.13/user/articles/reviewing-your-security-log": null, + "/enterprise/2.13/articles/reviewing-your-ssh-keys": null, + "/enterprise/2.13/user/articles/reviewing-your-ssh-keys": null, + "/enterprise/2.13/articles/searching-code": null, + "/enterprise/2.13/user/articles/searching-code": null, + "/enterprise/2.13/articles/searching-commits": null, + "/enterprise/2.13/user/articles/searching-commits": null, + "/enterprise/2.13/articles/searching-for-repositories": null, + "/enterprise/2.13/user/articles/searching-for-repositories": null, + "/enterprise/2.13/articles/searching-in-forks": null, + "/enterprise/2.13/user/articles/searching-in-forks": null, + "/enterprise/2.13/articles/searching-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/searching-issues-and-pull-requests": null, + "/enterprise/2.13/articles/searching-on-github": null, + "/enterprise/2.13/user/articles/searching-on-github": null, + "/enterprise/2.13/articles/searching-topics": null, + "/enterprise/2.13/user/articles/searching-topics": null, + "/enterprise/2.13/articles/searching-users": null, + "/enterprise/2.13/user/articles/searching-users": null, + "/enterprise/2.13/articles/searching-wikis": null, + "/enterprise/2.13/user/articles/searching-wikis": null, + "/enterprise/2.13/articles/securing-your-account-with-two-factor-authentication-2fa": null, + "/enterprise/2.13/user/articles/securing-your-account-with-two-factor-authentication-2fa": null, + "/enterprise/2.13/articles/set-up-git": null, + "/enterprise/2.13/user/articles/set-up-git": null, + "/enterprise/2.13/articles/setting-a-backup-email-address": null, + "/enterprise/2.13/user/articles/setting-a-backup-email-address": null, + "/enterprise/2.13/articles/setting-guidelines-for-repository-contributors": null, + "/enterprise/2.13/user/articles/setting-guidelines-for-repository-contributors": null, + "/enterprise/2.13/articles/setting-repository-visibility": null, + "/enterprise/2.13/user/articles/setting-repository-visibility": null, + "/enterprise/2.13/articles/setting-the-default-branch": null, + "/enterprise/2.13/user/articles/setting-the-default-branch": null, + "/enterprise/2.13/articles/setting-up-your-github-pages-site-locally-with-jekyll": null, + "/enterprise/2.13/user/articles/setting-up-your-github-pages-site-locally-with-jekyll": null, + "/enterprise/2.13/articles/setting-up-your-project-for-healthy-contributions": null, + "/enterprise/2.13/user/articles/setting-up-your-project-for-healthy-contributions": null, + "/enterprise/2.13/articles/setting-your-commit-email-address-in-git": null, + "/enterprise/2.13/user/articles/setting-your-commit-email-address-in-git": null, + "/enterprise/2.13/articles/setting-your-commit-email-address-on-github": null, + "/enterprise/2.13/user/articles/setting-your-commit-email-address-on-github": null, + "/enterprise/2.13/articles/setting-your-teams-profile-picture": null, + "/enterprise/2.13/user/articles/setting-your-teams-profile-picture": null, + "/enterprise/2.13/articles/setting-your-username-in-git": null, + "/enterprise/2.13/user/articles/setting-your-username-in-git": null, + "/enterprise/2.13/articles/sharing-filters": null, + "/enterprise/2.13/user/articles/sharing-filters": null, + "/enterprise/2.13/articles/signing-commits": null, + "/enterprise/2.13/user/articles/signing-commits": null, + "/enterprise/2.13/articles/signing-tags": null, + "/enterprise/2.13/user/articles/signing-tags": null, + "/enterprise/2.13/articles/sitemaps-for-github-pages": null, + "/enterprise/2.13/user/articles/sitemaps-for-github-pages": null, + "/enterprise/2.13/articles/sorting-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/sorting-issues-and-pull-requests": null, + "/enterprise/2.13/articles/sorting-search-results": null, + "/enterprise/2.13/user/articles/sorting-search-results": null, + "/enterprise/2.13/articles/source-code-migration-tools": null, + "/enterprise/2.13/user/articles/source-code-migration-tools": null, + "/enterprise/2.13/articles/splitting-a-subfolder-out-into-a-new-repository": null, + "/enterprise/2.13/user/articles/splitting-a-subfolder-out-into-a-new-repository": null, + "/enterprise/2.13/articles/subscribing-to-and-unsubscribing-from-notifications": null, + "/enterprise/2.13/user/articles/subscribing-to-and-unsubscribing-from-notifications": null, + "/enterprise/2.13/articles/subversion-properties-supported-by-github": null, + "/enterprise/2.13/user/articles/subversion-properties-supported-by-github": null, + "/enterprise/2.13/articles/sudo-mode": null, + "/enterprise/2.13/user/articles/sudo-mode": null, + "/enterprise/2.13/articles/support-for-subversion-clients": null, + "/enterprise/2.13/user/articles/support-for-subversion-clients": null, + "/enterprise/2.13/articles/supported-browsers": null, + "/enterprise/2.13/user/articles/supported-browsers": null, + "/enterprise/2.13/articles/syncing-a-fork": null, + "/enterprise/2.13/user/articles/syncing-a-fork": null, + "/enterprise/2.13/articles/telling-git-about-your-signing-key": null, + "/enterprise/2.13/user/articles/telling-git-about-your-signing-key": null, + "/enterprise/2.13/articles/testing-your-ssh-connection": null, + "/enterprise/2.13/user/articles/testing-your-ssh-connection": null, + "/enterprise/2.13/articles/tracking-changes-in-a-file": null, + "/enterprise/2.13/user/articles/tracking-changes-in-a-file": null, + "/enterprise/2.13/articles/tracking-progress-on-your-project-board": null, + "/enterprise/2.13/user/articles/tracking-progress-on-your-project-board": null, + "/enterprise/2.13/articles/tracking-the-progress-of-your-work-with-milestones": null, + "/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-milestones": null, + "/enterprise/2.13/articles/tracking-the-progress-of-your-work-with-project-boards": null, + "/enterprise/2.13/user/articles/tracking-the-progress-of-your-work-with-project-boards": null, + "/enterprise/2.13/articles/transferring-a-repository": null, + "/enterprise/2.13/user/articles/transferring-a-repository": null, + "/enterprise/2.13/articles/transferring-organization-ownership": null, + "/enterprise/2.13/user/articles/transferring-organization-ownership": null, + "/enterprise/2.13/articles/troubleshooting-commit-signature-verification": null, + "/enterprise/2.13/user/articles/troubleshooting-commit-signature-verification": null, + "/enterprise/2.13/articles/troubleshooting-commits-on-your-timeline": null, + "/enterprise/2.13/user/articles/troubleshooting-commits-on-your-timeline": null, + "/enterprise/2.13/articles/troubleshooting-github-pages-builds": null, + "/enterprise/2.13/user/articles/troubleshooting-github-pages-builds": null, + "/enterprise/2.13/articles/troubleshooting-search-queries": null, + "/enterprise/2.13/user/articles/troubleshooting-search-queries": null, + "/enterprise/2.13/articles/troubleshooting-ssh": null, + "/enterprise/2.13/user/articles/troubleshooting-ssh": null, + "/enterprise/2.13/articles/types-of-required-status-checks": null, + "/enterprise/2.13/user/articles/types-of-required-status-checks": null, + "/enterprise/2.13/articles/understanding-connections-between-repositories": null, + "/enterprise/2.13/user/articles/understanding-connections-between-repositories": null, + "/enterprise/2.13/articles/understanding-the-search-syntax": null, + "/enterprise/2.13/user/articles/understanding-the-search-syntax": null, + "/enterprise/2.13/articles/unpublishing-a-project-pages-site": null, + "/enterprise/2.13/user/articles/unpublishing-a-project-pages-site": null, + "/enterprise/2.13/articles/unpublishing-a-user-pages-site": null, + "/enterprise/2.13/user/articles/unpublishing-a-user-pages-site": null, + "/enterprise/2.13/articles/updating-an-expired-gpg-key": null, + "/enterprise/2.13/user/articles/updating-an-expired-gpg-key": null, + "/enterprise/2.13/articles/updating-credentials-from-the-osx-keychain": null, + "/enterprise/2.13/user/articles/updating-credentials-from-the-osx-keychain": null, + "/enterprise/2.13/articles/updating-your-github-access-credentials": null, + "/enterprise/2.13/user/articles/updating-your-github-access-credentials": null, + "/enterprise/2.13/articles/updating-your-markdown-processor-to-kramdown": null, + "/enterprise/2.13/user/articles/updating-your-markdown-processor-to-kramdown": null, + "/enterprise/2.13/articles/user-organization-and-project-pages": null, + "/enterprise/2.13/user/articles/user-organization-and-project-pages": null, + "/enterprise/2.13/articles/using-a-static-site-generator-other-than-jekyll": null, + "/enterprise/2.13/user/articles/using-a-static-site-generator-other-than-jekyll": null, + "/enterprise/2.13/articles/using-a-verified-email-address-in-your-gpg-key": null, + "/enterprise/2.13/user/articles/using-a-verified-email-address-in-your-gpg-key": null, + "/enterprise/2.13/articles/using-git-rebase-on-the-command-line": null, + "/enterprise/2.13/user/articles/using-git-rebase-on-the-command-line": null, + "/enterprise/2.13/articles/using-jekyll-as-a-static-site-generator-with-github-pages": null, + "/enterprise/2.13/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages": null, + "/enterprise/2.13/articles/using-keyboard-shortcuts": null, + "/enterprise/2.13/user/articles/using-keyboard-shortcuts": null, + "/enterprise/2.13/articles/using-saved-replies": null, + "/enterprise/2.13/user/articles/using-saved-replies": null, + "/enterprise/2.13/articles/using-search-to-filter-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/using-search-to-filter-issues-and-pull-requests": null, + "/enterprise/2.13/articles/using-syntax-highlighting-on-github-pages": null, + "/enterprise/2.13/user/articles/using-syntax-highlighting-on-github-pages": null, + "/enterprise/2.13/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": null, + "/enterprise/2.13/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": null, + "/enterprise/2.13/articles/versioning-large-files": null, + "/enterprise/2.13/user/articles/versioning-large-files": null, + "/enterprise/2.13/articles/viewing-a-pull-request-review": null, + "/enterprise/2.13/user/articles/viewing-a-pull-request-review": null, + "/enterprise/2.13/articles/viewing-a-repositorys-network": null, + "/enterprise/2.13/user/articles/viewing-a-repositorys-network": null, + "/enterprise/2.13/articles/viewing-a-summary-of-repository-activity": null, + "/enterprise/2.13/user/articles/viewing-a-summary-of-repository-activity": null, + "/enterprise/2.13/articles/viewing-a-wikis-history-of-changes": null, + "/enterprise/2.13/user/articles/viewing-a-wikis-history-of-changes": null, + "/enterprise/2.13/articles/viewing-all-of-your-issues-and-pull-requests": null, + "/enterprise/2.13/user/articles/viewing-all-of-your-issues-and-pull-requests": null, + "/enterprise/2.13/articles/viewing-branches-in-your-repository": null, + "/enterprise/2.13/user/articles/viewing-branches-in-your-repository": null, + "/enterprise/2.13/articles/viewing-contribution-activity-in-a-repository": null, + "/enterprise/2.13/user/articles/viewing-contribution-activity-in-a-repository": null, + "/enterprise/2.13/articles/viewing-contributions-on-your-profile": null, + "/enterprise/2.13/user/articles/viewing-contributions-on-your-profile": null, + "/enterprise/2.13/articles/viewing-jekyll-build-error-messages": null, + "/enterprise/2.13/user/articles/viewing-jekyll-build-error-messages": null, + "/enterprise/2.13/articles/viewing-peoples-roles-in-an-organization": null, + "/enterprise/2.13/user/articles/viewing-peoples-roles-in-an-organization": null, + "/enterprise/2.13/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": null, + "/enterprise/2.13/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": null, + "/enterprise/2.13/articles/viewing-your-milestones-progress": null, + "/enterprise/2.13/user/articles/viewing-your-milestones-progress": null, + "/enterprise/2.13/articles/visualizing-additions-and-deletions-to-content-in-a-repository": null, + "/enterprise/2.13/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository": null, + "/enterprise/2.13/articles/visualizing-commits-in-a-repository": null, + "/enterprise/2.13/user/articles/visualizing-commits-in-a-repository": null, + "/enterprise/2.13/articles/watching-and-unwatching-repositories": null, + "/enterprise/2.13/user/articles/watching-and-unwatching-repositories": null, + "/enterprise/2.13/articles/watching-and-unwatching-team-discussions": null, + "/enterprise/2.13/user/articles/watching-and-unwatching-team-discussions": null, + "/enterprise/2.13/articles/what-are-the-differences-between-subversion-and-git": null, + "/enterprise/2.13/user/articles/what-are-the-differences-between-subversion-and-git": null, + "/enterprise/2.13/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": null, + "/enterprise/2.13/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": null, + "/enterprise/2.13/articles/what-happens-when-i-change-my-username": null, + "/enterprise/2.13/user/articles/what-happens-when-i-change-my-username": null, + "/enterprise/2.13/articles/what-is-a-good-git-workflow": null, + "/enterprise/2.13/user/articles/what-is-a-good-git-workflow": null, + "/enterprise/2.13/articles/what-is-github-pages": null, + "/enterprise/2.13/user/articles/what-is-github-pages": null, + "/enterprise/2.13/articles/which-remote-url-should-i-use": null, + "/enterprise/2.13/user/articles/which-remote-url-should-i-use": null, + "/enterprise/2.13/articles/why-are-my-commits-in-the-wrong-order": null, + "/enterprise/2.13/user/articles/why-are-my-commits-in-the-wrong-order": null, + "/enterprise/2.13/articles/why-are-my-commits-linked-to-the-wrong-user": null, + "/enterprise/2.13/user/articles/why-are-my-commits-linked-to-the-wrong-user": null, + "/enterprise/2.13/articles/why-are-my-contributions-not-showing-up-on-my-profile": null, + "/enterprise/2.13/user/articles/why-are-my-contributions-not-showing-up-on-my-profile": null, + "/enterprise/2.13/articles/why-is-git-always-asking-for-my-password": null, + "/enterprise/2.13/user/articles/why-is-git-always-asking-for-my-password": null, + "/enterprise/2.13/articles/working-with-advanced-formatting": null, + "/enterprise/2.13/user/articles/working-with-advanced-formatting": null, + "/enterprise/2.13/articles/working-with-forks": null, + "/enterprise/2.13/user/articles/working-with-forks": null, + "/enterprise/2.13/articles/working-with-jupyter-notebook-files-on-github": null, + "/enterprise/2.13/user/articles/working-with-jupyter-notebook-files-on-github": null, + "/enterprise/2.13/articles/working-with-large-files": null, + "/enterprise/2.13/user/articles/working-with-large-files": null, + "/enterprise/2.13/articles/working-with-pre-receive-hooks": null, + "/enterprise/2.13/user/articles/working-with-pre-receive-hooks": null, + "/enterprise/2.13/articles/working-with-saved-replies": null, + "/enterprise/2.13/user/articles/working-with-saved-replies": null, + "/enterprise/2.13/articles/working-with-ssh-key-passphrases": null, + "/enterprise/2.13/user/articles/working-with-ssh-key-passphrases": null, + "/enterprise/2.13/articles/working-with-subversion-on-github": null, + "/enterprise/2.13/user/articles/working-with-subversion-on-github": null, + "/enterprise/2.13/articles/working-with-tags": null, + "/enterprise/2.13/user/articles/working-with-tags": null, + "/enterprise/2.13/categories/about-github": null, + "/enterprise/2.13/user/categories/about-github": null, + "/enterprise/2.13/user/categories/admin/guidesistering-a-repository": null, + "/enterprise/2.13/categories/administering-a-repository": null, + "/enterprise/2.13/user/categories/administering-a-repository": null, + "/enterprise/2.13/categories/advanced-git": null, + "/enterprise/2.13/user/categories/advanced-git": null, + "/enterprise/2.13/categories/authenticating-to-github": null, + "/enterprise/2.13/user/categories/authenticating-to-github": null, + "/enterprise/2.13/categories/automation": null, + "/enterprise/2.13/user/categories/automation": null, + "/enterprise/2.13/categories/bootcamp": null, + "/enterprise/2.13/user/categories/bootcamp": null, + "/enterprise/2.13/categories/building-a-strong-community": null, + "/enterprise/2.13/user/categories/building-a-strong-community": null, + "/enterprise/2.13/categories/collaborating-with-issues-and-pull-requests": null, + "/enterprise/2.13/user/categories/collaborating-with-issues-and-pull-requests": null, + "/enterprise/2.13/categories/commits": null, + "/enterprise/2.13/user/categories/commits": null, + "/enterprise/2.13/categories/creating-cloning-and-archiving-repositories": null, + "/enterprise/2.13/user/categories/creating-cloning-and-archiving-repositories": null, + "/enterprise/2.13/categories/customizing-github-pages": null, + "/enterprise/2.13/user/categories/customizing-github-pages": null, + "/enterprise/2.13/categories/exploring-projects-on-github": null, + "/enterprise/2.13/user/categories/exploring-projects-on-github": null, + "/enterprise/2.13/categories/gists": null, + "/enterprise/2.13/user/categories/gists": null, + "/enterprise/2.13/categories/github-pages-basics": null, + "/enterprise/2.13/user/categories/github-pages-basics": null, + "/enterprise/2.13/categories/importing-your-projects-to-github": null, + "/enterprise/2.13/user/categories/importing-your-projects-to-github": null, + "/enterprise/2.13/categories/keyboard-shortcuts": null, + "/enterprise/2.13/user/categories/keyboard-shortcuts": null, + "/enterprise/2.13/categories/managing-files-in-a-repository": null, + "/enterprise/2.13/user/categories/managing-files-in-a-repository": null, + "/enterprise/2.13/categories/managing-large-files": null, + "/enterprise/2.13/user/categories/managing-large-files": null, + "/enterprise/2.13/categories/managing-remotes": null, + "/enterprise/2.13/user/categories/managing-remotes": null, + "/enterprise/2.13/categories/managing-your-work-on-github": null, + "/enterprise/2.13/user/categories/managing-your-work-on-github": null, + "/enterprise/2.13/categories/receiving-notifications-about-activity-on-github": null, + "/enterprise/2.13/user/categories/receiving-notifications-about-activity-on-github": null, + "/enterprise/2.13/categories/releases": null, + "/enterprise/2.13/user/categories/releases": null, + "/enterprise/2.13/categories/searching-for-information-on-github": null, + "/enterprise/2.13/user/categories/searching-for-information-on-github": null, + "/enterprise/2.13/categories/setting-up-and-managing-organizations-and-teams": null, + "/enterprise/2.13/user/categories/setting-up-and-managing-organizations-and-teams": null, + "/enterprise/2.13/categories/setting-up-and-managing-your-github-profile": null, + "/enterprise/2.13/user/categories/setting-up-and-managing-your-github-profile": null, + "/enterprise/2.13/categories/setting-up-and-managing-your-github-user-account": null, + "/enterprise/2.13/user/categories/setting-up-and-managing-your-github-user-account": null, + "/enterprise/2.13/categories/setup": null, + "/enterprise/2.13/user/categories/setup": null, + "/enterprise/2.13/categories/using-git": null, + "/enterprise/2.13/user/categories/using-git": null, + "/enterprise/2.13/categories/visualizing-repository-data-with-graphs": null, + "/enterprise/2.13/user/categories/visualizing-repository-data-with-graphs": null, + "/enterprise/2.13/categories/working-with-non-code-files": null, + "/enterprise/2.13/user/categories/working-with-non-code-files": null, + "/enterprise/2.13/categories/writing-on-github": null, + "/enterprise/2.13/user/categories/writing-on-github": null, + "/enterprise/2.13/user": null, + "/enterprise/2.14/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", + "/enterprise/2.14/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", + "/enterprise/2.14/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", + "/enterprise/2.14/admin/guides/articles/using-github-task-runner": "/enterprise/2.14/admin/articles/using-github-task-runner", + "/enterprise/2.14/admin/guides/clustering/about-cluster-nodes": "/enterprise/2.14/admin/clustering/about-cluster-nodes", + "/enterprise/2.14/admin/guides/clustering/clustering-overview": "/enterprise/2.14/admin/clustering/clustering-overview", + "/enterprise/2.14/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha", + "/enterprise/2.14/admin/guides/clustering/evacuating-a-cluster-node": "/enterprise/2.14/admin/clustering/evacuating-a-cluster-node", + "/enterprise/2.14/admin/guides/clustering": "/enterprise/2.14/admin/clustering", + "/enterprise/2.14/admin/guides/clustering/initializing-the-cluster": "/enterprise/2.14/admin/clustering/initializing-the-cluster", + "/enterprise/2.14/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster", + "/enterprise/2.14/admin/guides/clustering/monitoring-cluster-nodes": "/enterprise/2.14/admin/clustering/monitoring-cluster-nodes", + "/enterprise/2.14/admin/guides/clustering/network-configuration": "/enterprise/2.14/admin/clustering/network-configuration", + "/enterprise/2.14/admin/guides/clustering/replacing-a-cluster-node": "/enterprise/2.14/admin/clustering/replacing-a-cluster-node", + "/enterprise/2.14/admin/guides/clustering/setting-up-the-cluster-instances": "/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances", + "/enterprise/2.14/admin/guides/clustering/upgrading-a-cluster": "/enterprise/2.14/admin/clustering/upgrading-a-cluster", + "/enterprise/2.14/admin/guides/developer-workflow/about-pre-receive-hooks": "/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks", + "/enterprise/2.14/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks", + "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance", + "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository", + "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", + "/enterprise/2.14/admin/guides/developer-workflow/blocking-force-pushes": "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes", + "/enterprise/2.14/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", + "/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins", + "/enterprise/2.14/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci", + "/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment", + "/enterprise/2.14/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script", + "/enterprise/2.14/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations", + "/enterprise/2.14/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions", + "/enterprise/2.14/admin/guides/developer-workflow": "/enterprise/2.14/admin/developer-workflow", + "/enterprise/2.14/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", + "/enterprise/2.14/admin/guides/developer-workflow/managing-projects-using-jira": "/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira", + "/enterprise/2.14/admin/guides/developer-workflow/troubleshooting-service-hooks": "/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks", + "/enterprise/2.14/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", + "/enterprise/2.14/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration", + "/enterprise/2.14/admin/guides/enterprise-support/about-github-enterprise-support": "/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support", + "/enterprise/2.14/admin/guides/enterprise-support": "/enterprise/2.14/admin/enterprise-support", + "/enterprise/2.14/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket", + "/enterprise/2.14/admin/guides/enterprise-support/providing-data-to-github-support": "/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support", + "/enterprise/2.14/admin/guides/enterprise-support/reaching-github-support": "/enterprise/2.14/admin/enterprise-support/reaching-github-support", + "/enterprise/2.14/admin/guides/enterprise-support/receiving-help-from-github-support": "/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support", + "/enterprise/2.14/admin/guides/enterprise-support/submitting-a-ticket": "/enterprise/2.14/admin/enterprise-support/submitting-a-ticket", + "/enterprise/2.14/admin/guides": "/enterprise/2.14/admin", + "/enterprise/2.14/admin/guides/installation/about-geo-replication": "/enterprise/2.14/admin/installation/about-geo-replication", + "/enterprise/2.14/admin/guides/installation/about-high-availability-configuration": "/enterprise/2.14/admin/installation/about-high-availability-configuration", + "/enterprise/2.14/admin/guides/installation/about-the-github-enterprise-server-api": "/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api", + "/enterprise/2.14/admin/guides/installation/accessing-the-administrative-shell-ssh": "/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh", + "/enterprise/2.14/admin/guides/installation/accessing-the-management-console": "/enterprise/2.14/admin/installation/accessing-the-management-console", + "/enterprise/2.14/admin/guides/installation/accessing-the-monitor-dashboard": "/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard", + "/enterprise/2.14/admin/guides/installation/activity-dashboard": "/enterprise/2.14/admin/installation/activity-dashboard", + "/enterprise/2.14/admin/guides/installation/audit-logging": "/enterprise/2.14/admin/installation/audit-logging", + "/enterprise/2.14/admin/guides/installation/audited-actions": "/enterprise/2.14/admin/installation/audited-actions", + "/enterprise/2.14/admin/guides/installation/command-line-utilities": "/enterprise/2.14/admin/installation/command-line-utilities", + "/enterprise/2.14/admin/guides/installation/configuring-a-hostname": "/enterprise/2.14/admin/installation/configuring-a-hostname", + "/enterprise/2.14/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server", + "/enterprise/2.14/admin/guides/installation/configuring-backups-on-your-appliance": "/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance", + "/enterprise/2.14/admin/guides/installation/configuring-built-in-firewall-rules": "/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules", + "/enterprise/2.14/admin/guides/installation/configuring-collectd": "/enterprise/2.14/admin/installation/configuring-collectd", + "/enterprise/2.14/admin/guides/installation/configuring-dns-nameservers": "/enterprise/2.14/admin/installation/configuring-dns-nameservers", + "/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", + "/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", + "/enterprise/2.14/admin/guides/installation/configuring-git-large-file-storage": "/enterprise/2.14/admin/installation/configuring-git-large-file-storage", + "/enterprise/2.14/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability", + "/enterprise/2.14/admin/guides/installation/configuring-github-pages-on-your-appliance": "/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance", + "/enterprise/2.14/admin/guides/installation/configuring-rate-limits": "/enterprise/2.14/admin/installation/configuring-rate-limits", + "/enterprise/2.14/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", + "/enterprise/2.14/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance", + "/enterprise/2.14/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", + "/enterprise/2.14/admin/guides/installation/configuring-time-synchronization": "/enterprise/2.14/admin/installation/configuring-time-synchronization", + "/enterprise/2.14/admin/guides/installation/configuring-tls": "/enterprise/2.14/admin/installation/configuring-tls", + "/enterprise/2.14/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings", + "/enterprise/2.14/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", + "/enterprise/2.14/admin/guides/installation/creating-a-high-availability-replica": "/enterprise/2.14/admin/installation/creating-a-high-availability-replica", + "/enterprise/2.14/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", + "/enterprise/2.14/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", + "/enterprise/2.14/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode", + "/enterprise/2.14/admin/guides/installation/enabling-automatic-update-checks": "/enterprise/2.14/admin/installation/enabling-automatic-update-checks", + "/enterprise/2.14/admin/guides/installation/enabling-private-mode": "/enterprise/2.14/admin/installation/enabling-private-mode", + "/enterprise/2.14/admin/guides/installation/enabling-subdomain-isolation": "/enterprise/2.14/admin/installation/enabling-subdomain-isolation", + "/enterprise/2.14/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", + "/enterprise/2.14/admin/guides/installation/increasing-cpu-or-memory-resources": "/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources", + "/enterprise/2.14/admin/guides/installation/increasing-storage-capacity": "/enterprise/2.14/admin/installation/increasing-storage-capacity", + "/enterprise/2.14/admin/guides/installation": "/enterprise/2.14/admin/installation", + "/enterprise/2.14/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-aws": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-azure": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware", + "/enterprise/2.14/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver", + "/enterprise/2.14/admin/guides/installation/log-forwarding": "/enterprise/2.14/admin/installation/log-forwarding", + "/enterprise/2.14/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", + "/enterprise/2.14/admin/guides/installation/managing-your-github-enterprise-server-license": "/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license", + "/enterprise/2.14/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", + "/enterprise/2.14/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123", + "/enterprise/2.14/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server", + "/enterprise/2.14/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", + "/enterprise/2.14/admin/guides/installation/monitoring-using-snmp": "/enterprise/2.14/admin/installation/monitoring-using-snmp", + "/enterprise/2.14/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance", + "/enterprise/2.14/admin/guides/installation/network-ports": "/enterprise/2.14/admin/installation/network-ports", + "/enterprise/2.14/admin/guides/installation/recommended-alert-thresholds": "/enterprise/2.14/admin/installation/recommended-alert-thresholds", + "/enterprise/2.14/admin/guides/installation/recovering-a-high-availability-configuration": "/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration", + "/enterprise/2.14/admin/guides/installation/removing-a-high-availability-replica": "/enterprise/2.14/admin/installation/removing-a-high-availability-replica", + "/enterprise/2.14/admin/guides/installation/searching-the-audit-log": "/enterprise/2.14/admin/installation/searching-the-audit-log", + "/enterprise/2.14/admin/guides/installation/setting-git-push-limits": "/enterprise/2.14/admin/installation/setting-git-push-limits", + "/enterprise/2.14/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance", + "/enterprise/2.14/admin/guides/installation/setting-up-a-staging-instance": "/enterprise/2.14/admin/installation/setting-up-a-staging-instance", + "/enterprise/2.14/admin/guides/installation/setting-up-external-monitoring": "/enterprise/2.14/admin/installation/setting-up-external-monitoring", + "/enterprise/2.14/admin/guides/installation/site-admin-dashboard": "/enterprise/2.14/admin/installation/site-admin-dashboard", + "/enterprise/2.14/admin/guides/installation/system-overview": "/enterprise/2.14/admin/installation/system-overview", + "/enterprise/2.14/admin/guides/installation/troubleshooting-ssl-errors": "/enterprise/2.14/admin/installation/troubleshooting-ssl-errors", + "/enterprise/2.14/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources", + "/enterprise/2.14/admin/guides/installation/upgrade-requirements": "/enterprise/2.14/admin/installation/upgrade-requirements", + "/enterprise/2.14/admin/guides/installation/upgrading-github-enterprise-server": "/enterprise/2.14/admin/installation/upgrading-github-enterprise-server", + "/enterprise/2.14/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer", + "/enterprise/2.14/admin/guides/installation/validating-your-domain-settings": "/enterprise/2.14/admin/installation/validating-your-domain-settings", + "/enterprise/2.14/admin/guides/installation/viewing-push-logs": "/enterprise/2.14/admin/installation/viewing-push-logs", + "/enterprise/2.14/admin/guides/migrations/about-migrations": "/enterprise/2.14/admin/migrations/about-migrations", + "/enterprise/2.14/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server", + "/enterprise/2.14/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server", + "/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server", + "/enterprise/2.14/admin/guides/migrations/exporting-migration-data-from-githubcom": "/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom", + "/enterprise/2.14/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories", + "/enterprise/2.14/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories", + "/enterprise/2.14/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts", + "/enterprise/2.14/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems", + "/enterprise/2.14/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server", + "/enterprise/2.14/admin/guides/migrations": "/enterprise/2.14/admin/migrations", + "/enterprise/2.14/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance", + "/enterprise/2.14/admin/guides/migrations/preparing-the-githubcom-source-organization": "/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization", + "/enterprise/2.14/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", + "/enterprise/2.14/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", + "/enterprise/2.14/admin/guides/migrations/reviewing-migration-conflicts": "/enterprise/2.14/admin/migrations/reviewing-migration-conflicts", + "/enterprise/2.14/admin/guides/migrations/reviewing-migration-data": "/enterprise/2.14/admin/migrations/reviewing-migration-data", + "/enterprise/2.14/admin/guides/user-management/about-global-webhooks": "/enterprise/2.14/admin/user-management/about-global-webhooks", + "/enterprise/2.14/admin/guides/user-management/adding-people-to-teams": "/enterprise/2.14/admin/user-management/adding-people-to-teams", + "/enterprise/2.14/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", + "/enterprise/2.14/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", + "/enterprise/2.14/admin/guides/user-management/archiving-and-unarchiving-repositories": "/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories", + "/enterprise/2.14/admin/guides/user-management/auditing-ssh-keys": "/enterprise/2.14/admin/user-management/auditing-ssh-keys", + "/enterprise/2.14/admin/guides/user-management/auditing-users-across-your-instance": "/enterprise/2.14/admin/user-management/auditing-users-across-your-instance", + "/enterprise/2.14/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", + "/enterprise/2.14/admin/guides/user-management/basic-account-settings": "/enterprise/2.14/admin/user-management/basic-account-settings", + "/enterprise/2.14/admin/guides/user-management/best-practices-for-user-security": "/enterprise/2.14/admin/user-management/best-practices-for-user-security", + "/enterprise/2.14/admin/guides/user-management/changing-authentication-methods": "/enterprise/2.14/admin/user-management/changing-authentication-methods", + "/enterprise/2.14/admin/guides/user-management/configuring-email-for-notifications": "/enterprise/2.14/admin/user-management/configuring-email-for-notifications", + "/enterprise/2.14/admin/guides/user-management/configuring-visibility-for-organization-membership": "/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership", + "/enterprise/2.14/admin/guides/user-management/creating-organizations": "/enterprise/2.14/admin/user-management/creating-organizations", + "/enterprise/2.14/admin/guides/user-management/creating-teams": "/enterprise/2.14/admin/user-management/creating-teams", + "/enterprise/2.14/admin/guides/user-management/customizing-user-messages-on-your-instance": "/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance", + "/enterprise/2.14/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups", + "/enterprise/2.14/admin/guides/user-management": "/enterprise/2.14/admin/user-management", + "/enterprise/2.14/admin/guides/user-management/managing-dormant-users": "/enterprise/2.14/admin/user-management/managing-dormant-users", + "/enterprise/2.14/admin/guides/user-management/managing-global-webhooks": "/enterprise/2.14/admin/user-management/managing-global-webhooks", + "/enterprise/2.14/admin/guides/user-management/organizations-and-teams": "/enterprise/2.14/admin/user-management/organizations-and-teams", + "/enterprise/2.14/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", + "/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", + "/enterprise/2.14/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", + "/enterprise/2.14/admin/guides/user-management/preventing-users-from-creating-organizations": "/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations", + "/enterprise/2.14/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories", + "/enterprise/2.14/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator", + "/enterprise/2.14/admin/guides/user-management/rebuilding-contributions-data": "/enterprise/2.14/admin/user-management/rebuilding-contributions-data", + "/enterprise/2.14/admin/guides/user-management/removing-users-from-teams-and-organizations": "/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations", + "/enterprise/2.14/admin/guides/user-management/repositories": "/enterprise/2.14/admin/user-management/repositories", + "/enterprise/2.14/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization", + "/enterprise/2.14/admin/guides/user-management/suspending-and-unsuspending-users": "/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users", + "/enterprise/2.14/admin/guides/user-management/user-security": "/enterprise/2.14/admin/user-management/user-security", + "/enterprise/2.14/admin/guides/user-management/using-built-in-authentication": "/enterprise/2.14/admin/user-management/using-built-in-authentication", + "/enterprise/2.14/admin/guides/user-management/using-cas": "/enterprise/2.14/admin/user-management/using-cas", + "/enterprise/2.14/admin/guides/user-management/using-ldap": "/enterprise/2.14/admin/user-management/using-ldap", + "/enterprise/2.14/admin/guides/user-management/using-saml": "/enterprise/2.14/admin/user-management/using-saml", + "/enterprise/2.14/articles/3d-file-viewer": "/enterprise/2.14/user/articles/3d-file-viewer", + "/enterprise/2.14/articles/about-archiving-repositories": "/enterprise/2.14/user/articles/about-archiving-repositories", + "/enterprise/2.14/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", + "/enterprise/2.14/articles/about-automation-for-project-boards": "/enterprise/2.14/user/articles/about-automation-for-project-boards", + "/enterprise/2.14/articles/about-branch-restrictions": "/enterprise/2.14/user/articles/about-branch-restrictions", + "/enterprise/2.14/articles/about-branches": "/enterprise/2.14/user/articles/about-branches", + "/enterprise/2.14/articles/about-code-owners": "/enterprise/2.14/user/articles/about-code-owners", + "/enterprise/2.14/articles/about-collaborative-development-models": "/enterprise/2.14/user/articles/about-collaborative-development-models", + "/enterprise/2.14/articles/about-commit-signature-verification": "/enterprise/2.14/user/articles/about-commit-signature-verification", + "/enterprise/2.14/articles/about-comparing-branches-in-pull-requests": "/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests", + "/enterprise/2.14/articles/about-conversations-on-github": "/enterprise/2.14/user/articles/about-conversations-on-github", + "/enterprise/2.14/articles/about-duplicate-issues-and-pull-requests": "/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests", + "/enterprise/2.14/articles/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.14/articles/about-email-notifications": "/enterprise/2.14/user/articles/about-email-notifications", + "/enterprise/2.14/articles/about-forks": "/enterprise/2.14/user/articles/about-forks", + "/enterprise/2.14/articles/about-git-large-file-storage": "/enterprise/2.14/user/articles/about-git-large-file-storage", + "/enterprise/2.14/articles/about-git-rebase": "/enterprise/2.14/user/articles/about-git-rebase", + "/enterprise/2.14/articles/about-git-subtree-merges": "/enterprise/2.14/user/articles/about-git-subtree-merges", + "/enterprise/2.14/articles/about-github-pages-and-jekyll": "/enterprise/2.14/user/articles/about-github-pages-and-jekyll", + "/enterprise/2.14/articles/about-issue-and-pull-request-templates": "/enterprise/2.14/user/articles/about-issue-and-pull-request-templates", + "/enterprise/2.14/articles/about-issues": "/enterprise/2.14/user/articles/about-issues", + "/enterprise/2.14/articles/about-jekyll-themes-on-github": "/enterprise/2.14/user/articles/about-jekyll-themes-on-github", + "/enterprise/2.14/articles/about-labels": "/enterprise/2.14/user/articles/about-labels", + "/enterprise/2.14/articles/about-merge-conflicts": "/enterprise/2.14/user/articles/about-merge-conflicts", + "/enterprise/2.14/articles/about-merge-methods-on-github": "/enterprise/2.14/user/articles/about-merge-methods-on-github", + "/enterprise/2.14/articles/about-milestones": "/enterprise/2.14/user/articles/about-milestones", + "/enterprise/2.14/articles/about-notifications": "/enterprise/2.14/user/articles/about-notifications", + "/enterprise/2.14/articles/about-organization-membership": "/enterprise/2.14/user/articles/about-organization-membership", + "/enterprise/2.14/articles/about-organizations": "/enterprise/2.14/user/articles/about-organizations", + "/enterprise/2.14/articles/about-project-boards": "/enterprise/2.14/user/articles/about-project-boards", + "/enterprise/2.14/articles/about-protected-branches": "/enterprise/2.14/user/articles/about-protected-branches", + "/enterprise/2.14/articles/about-pull-request-merges": "/enterprise/2.14/user/articles/about-pull-request-merges", + "/enterprise/2.14/articles/about-pull-request-reviews": "/enterprise/2.14/user/articles/about-pull-request-reviews", + "/enterprise/2.14/articles/about-pull-requests": "/enterprise/2.14/user/articles/about-pull-requests", + "/enterprise/2.14/articles/about-readmes": "/enterprise/2.14/user/articles/about-readmes", + "/enterprise/2.14/articles/about-releases": "/enterprise/2.14/user/articles/about-releases", + "/enterprise/2.14/articles/about-remote-repositories": "/enterprise/2.14/user/articles/about-remote-repositories", + "/enterprise/2.14/articles/about-repositories": "/enterprise/2.14/user/articles/about-repositories", + "/enterprise/2.14/articles/about-repository-graphs": "/enterprise/2.14/user/articles/about-repository-graphs", + "/enterprise/2.14/articles/about-repository-languages": "/enterprise/2.14/user/articles/about-repository-languages", + "/enterprise/2.14/articles/about-required-commit-signing": "/enterprise/2.14/user/articles/about-required-commit-signing", + "/enterprise/2.14/articles/about-required-reviews-for-pull-requests": "/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests", + "/enterprise/2.14/articles/about-required-status-checks": "/enterprise/2.14/user/articles/about-required-status-checks", + "/enterprise/2.14/articles/about-saved-replies": "/enterprise/2.14/user/articles/about-saved-replies", + "/enterprise/2.14/articles/about-searching-on-github": "/enterprise/2.14/user/articles/about-searching-on-github", + "/enterprise/2.14/articles/about-ssh": "/enterprise/2.14/user/articles/about-ssh", + "/enterprise/2.14/articles/about-status-checks": "/enterprise/2.14/user/articles/about-status-checks", + "/enterprise/2.14/articles/about-task-lists": "/enterprise/2.14/user/articles/about-task-lists", + "/enterprise/2.14/articles/about-team-discussions": "/enterprise/2.14/user/articles/about-team-discussions", + "/enterprise/2.14/articles/about-teams": "/enterprise/2.14/user/articles/about-teams", + "/enterprise/2.14/articles/about-two-factor-authentication": "/enterprise/2.14/user/articles/about-two-factor-authentication", + "/enterprise/2.14/articles/about-web-notifications": "/enterprise/2.14/user/articles/about-web-notifications", + "/enterprise/2.14/articles/about-webhooks": "/enterprise/2.14/user/articles/about-webhooks", + "/enterprise/2.14/articles/about-wikis": "/enterprise/2.14/user/articles/about-wikis", + "/enterprise/2.14/articles/about-writing-and-formatting-on-github": "/enterprise/2.14/user/articles/about-writing-and-formatting-on-github", + "/enterprise/2.14/articles/about-your-organization-dashboard": "/enterprise/2.14/user/articles/about-your-organization-dashboard", + "/enterprise/2.14/articles/about-your-organizations-news-feed": "/enterprise/2.14/user/articles/about-your-organizations-news-feed", + "/enterprise/2.14/articles/about-your-organizations-profile": "/enterprise/2.14/user/articles/about-your-organizations-profile", + "/enterprise/2.14/articles/about-your-personal-dashboard": "/enterprise/2.14/user/articles/about-your-personal-dashboard", + "/enterprise/2.14/articles/about-your-profile": "/enterprise/2.14/user/articles/about-your-profile", + "/enterprise/2.14/articles/access-permissions-on-github": "/enterprise/2.14/user/articles/access-permissions-on-github", + "/enterprise/2.14/articles/accessing-an-organization": "/enterprise/2.14/user/articles/accessing-an-organization", + "/enterprise/2.14/articles/accessing-basic-repository-data": "/enterprise/2.14/user/articles/accessing-basic-repository-data", + "/enterprise/2.14/articles/accessing-github-using-two-factor-authentication": "/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication", + "/enterprise/2.14/articles/accessing-your-notifications": "/enterprise/2.14/user/articles/accessing-your-notifications", + "/enterprise/2.14/articles/accessing-your-organizations-settings": "/enterprise/2.14/user/articles/accessing-your-organizations-settings", + "/enterprise/2.14/articles/adding-a-file-to-a-repository-using-the-command-line": "/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line", + "/enterprise/2.14/articles/adding-a-file-to-a-repository": "/enterprise/2.14/user/articles/adding-a-file-to-a-repository", + "/enterprise/2.14/articles/adding-a-jekyll-theme-to-your-github-pages-site": "/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site", + "/enterprise/2.14/articles/adding-a-license-to-a-repository": "/enterprise/2.14/user/articles/adding-a-license-to-a-repository", + "/enterprise/2.14/articles/adding-a-new-gpg-key-to-your-github-account": "/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account", + "/enterprise/2.14/articles/adding-a-new-ssh-key-to-your-github-account": "/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account", + "/enterprise/2.14/articles/adding-a-remote": "/enterprise/2.14/user/articles/adding-a-remote", + "/enterprise/2.14/articles/adding-an-email-address-to-your-github-account": "/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account", + "/enterprise/2.14/articles/adding-an-existing-project-to-github-using-the-command-line": "/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line", + "/enterprise/2.14/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", + "/enterprise/2.14/articles/adding-issues-and-pull-requests-to-a-project-board": "/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board", + "/enterprise/2.14/articles/adding-jekyll-plugins-to-a-github-pages-site": "/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site", + "/enterprise/2.14/articles/adding-notes-to-a-project-board": "/enterprise/2.14/user/articles/adding-notes-to-a-project-board", + "/enterprise/2.14/articles/adding-or-editing-wiki-pages": "/enterprise/2.14/user/articles/adding-or-editing-wiki-pages", + "/enterprise/2.14/articles/adding-organization-members-to-a-team": "/enterprise/2.14/user/articles/adding-organization-members-to-a-team", + "/enterprise/2.14/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", + "/enterprise/2.14/articles/adding-people-to-your-organization": "/enterprise/2.14/user/articles/adding-people-to-your-organization", + "/enterprise/2.14/articles/adding-support-resources-to-your-project": "/enterprise/2.14/user/articles/adding-support-resources-to-your-project", + "/enterprise/2.14/articles/additional-customizations-for-github-pages": "/enterprise/2.14/user/articles/additional-customizations-for-github-pages", + "/enterprise/2.14/articles/addressing-merge-conflicts": "/enterprise/2.14/user/articles/addressing-merge-conflicts", + "/enterprise/2.14/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.14/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", + "/enterprise/2.14/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", + "/enterprise/2.14/articles/analyzing-changes-to-a-repositorys-content": "/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content", + "/enterprise/2.14/articles/applying-labels-to-issues-and-pull-requests": "/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests", + "/enterprise/2.14/articles/approving-a-pull-request-with-required-reviews": "/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews", + "/enterprise/2.14/articles/archiving-a-github-repository": "/enterprise/2.14/user/articles/archiving-a-github-repository", + "/enterprise/2.14/articles/archiving-repositories": "/enterprise/2.14/user/articles/archiving-repositories", + "/enterprise/2.14/articles/assigning-issues-and-pull-requests-to-other-github-users": "/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users", + "/enterprise/2.14/articles/associating-an-email-with-your-gpg-key": "/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key", + "/enterprise/2.14/articles/associating-milestones-with-issues-and-pull-requests": "/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests", + "/enterprise/2.14/articles/associating-text-editors-with-git": "/enterprise/2.14/user/articles/associating-text-editors-with-git", + "/enterprise/2.14/articles/authorizing-oauth-apps": "/enterprise/2.14/user/articles/authorizing-oauth-apps", + "/enterprise/2.14/articles/autolinked-references-and-urls": "/enterprise/2.14/user/articles/autolinked-references-and-urls", + "/enterprise/2.14/articles/backing-up-a-repository": "/enterprise/2.14/user/articles/backing-up-a-repository", + "/enterprise/2.14/articles/basic-writing-and-formatting-syntax": "/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax", + "/enterprise/2.14/articles/be-social": "/enterprise/2.14/user/articles/be-social", + "/enterprise/2.14/articles/caching-your-github-password-in-git": "/enterprise/2.14/user/articles/caching-your-github-password-in-git", + "/enterprise/2.14/articles/changing-a-commit-message": "/enterprise/2.14/user/articles/changing-a-commit-message", + "/enterprise/2.14/articles/changing-a-persons-role-to-owner": "/enterprise/2.14/user/articles/changing-a-persons-role-to-owner", + "/enterprise/2.14/articles/changing-a-remotes-url": "/enterprise/2.14/user/articles/changing-a-remotes-url", + "/enterprise/2.14/articles/changing-access-permissions-for-wikis": "/enterprise/2.14/user/articles/changing-access-permissions-for-wikis", + "/enterprise/2.14/articles/changing-author-info": "/enterprise/2.14/user/articles/changing-author-info", + "/enterprise/2.14/articles/changing-project-board-visibility": "/enterprise/2.14/user/articles/changing-project-board-visibility", + "/enterprise/2.14/articles/changing-team-visibility": "/enterprise/2.14/user/articles/changing-team-visibility", + "/enterprise/2.14/articles/changing-the-base-branch-of-a-pull-request": "/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request", + "/enterprise/2.14/articles/changing-your-github-username": "/enterprise/2.14/user/articles/changing-your-github-username", + "/enterprise/2.14/articles/changing-your-primary-email-address": "/enterprise/2.14/user/articles/changing-your-primary-email-address", + "/enterprise/2.14/articles/checking-for-existing-gpg-keys": "/enterprise/2.14/user/articles/checking-for-existing-gpg-keys", + "/enterprise/2.14/articles/checking-for-existing-ssh-keys": "/enterprise/2.14/user/articles/checking-for-existing-ssh-keys", + "/enterprise/2.14/articles/checking-out-pull-requests-locally": "/enterprise/2.14/user/articles/checking-out-pull-requests-locally", + "/enterprise/2.14/articles/checking-your-commit-and-tag-signature-verification-status": "/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status", + "/enterprise/2.14/articles/choosing-the-delivery-method-for-your-notifications": "/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications", + "/enterprise/2.14/articles/classifying-your-repository-with-topics": "/enterprise/2.14/user/articles/classifying-your-repository-with-topics", + "/enterprise/2.14/articles/cloning-a-repository-from-github": "/enterprise/2.14/user/articles/cloning-a-repository-from-github", + "/enterprise/2.14/articles/cloning-a-repository": "/enterprise/2.14/user/articles/cloning-a-repository", + "/enterprise/2.14/articles/closing-a-project-board": "/enterprise/2.14/user/articles/closing-a-project-board", + "/enterprise/2.14/articles/closing-a-pull-request": "/enterprise/2.14/user/articles/closing-a-pull-request", + "/enterprise/2.14/articles/closing-issues-using-keywords": "/enterprise/2.14/user/articles/closing-issues-using-keywords", + "/enterprise/2.14/articles/collaborating-on-repositories-with-code-quality-features-enabled": "/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled", + "/enterprise/2.14/articles/collaborating-with-groups-in-organizations": "/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations", + "/enterprise/2.14/articles/collaborating-with-your-team": "/enterprise/2.14/user/articles/collaborating-with-your-team", + "/enterprise/2.14/articles/collaboration-with-git-large-file-storage": "/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage", + "/enterprise/2.14/articles/commenting-on-a-pull-request": "/enterprise/2.14/user/articles/commenting-on-a-pull-request", + "/enterprise/2.14/articles/commit-branch-and-tag-labels": "/enterprise/2.14/user/articles/commit-branch-and-tag-labels", + "/enterprise/2.14/articles/commit-exists-on-github-but-not-in-my-local-clone": "/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone", + "/enterprise/2.14/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.14/articles/comparing-commits-across-time": "/enterprise/2.14/user/articles/comparing-commits-across-time", + "/enterprise/2.14/articles/conditions-for-large-files": "/enterprise/2.14/user/articles/conditions-for-large-files", + "/enterprise/2.14/articles/configuring-a-publishing-source-for-github-pages": "/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages", + "/enterprise/2.14/articles/configuring-a-remote-for-a-fork": "/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork", + "/enterprise/2.14/articles/configuring-automation-for-project-boards": "/enterprise/2.14/user/articles/configuring-automation-for-project-boards", + "/enterprise/2.14/articles/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.14/articles/configuring-commit-squashing-for-pull-requests": "/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.14/articles/configuring-git-large-file-storage": "/enterprise/2.14/user/articles/configuring-git-large-file-storage", + "/enterprise/2.14/articles/configuring-git-to-handle-line-endings": "/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings", + "/enterprise/2.14/articles/configuring-jekyll-plugins": "/enterprise/2.14/user/articles/configuring-jekyll-plugins", + "/enterprise/2.14/articles/configuring-jekyll": "/enterprise/2.14/user/articles/configuring-jekyll", + "/enterprise/2.14/articles/configuring-protected-branches": "/enterprise/2.14/user/articles/configuring-protected-branches", + "/enterprise/2.14/articles/configuring-pull-request-merges": "/enterprise/2.14/user/articles/configuring-pull-request-merges", + "/enterprise/2.14/articles/configuring-two-factor-authentication-recovery-methods": "/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods", + "/enterprise/2.14/articles/configuring-two-factor-authentication": "/enterprise/2.14/user/articles/configuring-two-factor-authentication", + "/enterprise/2.14/articles/connecting-to-github-with-ssh": "/enterprise/2.14/user/articles/connecting-to-github-with-ssh", + "/enterprise/2.14/articles/connecting-with-third-party-applications": "/enterprise/2.14/user/articles/connecting-with-third-party-applications", + "/enterprise/2.14/articles/converting-a-user-into-an-organization": "/enterprise/2.14/user/articles/converting-a-user-into-an-organization", + "/enterprise/2.14/articles/converting-an-organization-into-a-user": "/enterprise/2.14/user/articles/converting-an-organization-into-a-user", + "/enterprise/2.14/articles/converting-an-organization-member-to-an-outside-collaborator": "/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator", + "/enterprise/2.14/articles/converting-an-outside-collaborator-to-an-organization-member": "/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member", + "/enterprise/2.14/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": "/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions", + "/enterprise/2.14/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": "/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions", + "/enterprise/2.14/articles/create-a-repo": "/enterprise/2.14/user/articles/create-a-repo", + "/enterprise/2.14/articles/creating-a-commit-with-multiple-authors": "/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors", + "/enterprise/2.14/articles/creating-a-custom-404-page-for-your-github-pages-site": "/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site", + "/enterprise/2.14/articles/creating-a-footer-or-sidebar-for-your-wiki": "/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki", + "/enterprise/2.14/articles/creating-a-label": "/enterprise/2.14/user/articles/creating-a-label", + "/enterprise/2.14/articles/creating-a-new-organization-from-scratch": "/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch", + "/enterprise/2.14/articles/creating-a-new-repository": "/enterprise/2.14/user/articles/creating-a-new-repository", + "/enterprise/2.14/articles/creating-a-permanent-link-to-a-code-snippet": "/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet", + "/enterprise/2.14/articles/creating-a-personal-access-token-for-the-command-line": "/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line", + "/enterprise/2.14/articles/creating-a-project-board": "/enterprise/2.14/user/articles/creating-a-project-board", + "/enterprise/2.14/articles/creating-a-pull-request-from-a-fork": "/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork", + "/enterprise/2.14/articles/creating-a-pull-request-template-for-your-repository": "/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository", + "/enterprise/2.14/articles/creating-a-pull-request": "/enterprise/2.14/user/articles/creating-a-pull-request", + "/enterprise/2.14/articles/creating-a-repository-on-github": "/enterprise/2.14/user/articles/creating-a-repository-on-github", + "/enterprise/2.14/articles/creating-a-saved-reply": "/enterprise/2.14/user/articles/creating-a-saved-reply", + "/enterprise/2.14/articles/creating-a-strong-password": "/enterprise/2.14/user/articles/creating-a-strong-password", + "/enterprise/2.14/articles/creating-a-team-discussion": "/enterprise/2.14/user/articles/creating-a-team-discussion", + "/enterprise/2.14/articles/creating-a-team": "/enterprise/2.14/user/articles/creating-a-team", + "/enterprise/2.14/articles/creating-an-issue": "/enterprise/2.14/user/articles/creating-an-issue", + "/enterprise/2.14/articles/creating-an-issues-only-repository": "/enterprise/2.14/user/articles/creating-an-issues-only-repository", + "/enterprise/2.14/articles/creating-and-deleting-branches-within-your-repository": "/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository", + "/enterprise/2.14/articles/creating-and-editing-commits": "/enterprise/2.14/user/articles/creating-and-editing-commits", + "/enterprise/2.14/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", + "/enterprise/2.14/articles/creating-and-highlighting-code-blocks": "/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks", + "/enterprise/2.14/articles/creating-gists": "/enterprise/2.14/user/articles/creating-gists", + "/enterprise/2.14/articles/creating-issue-templates-for-your-repository": "/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository", + "/enterprise/2.14/articles/creating-new-files": "/enterprise/2.14/user/articles/creating-new-files", + "/enterprise/2.14/articles/creating-pages-with-the-automatic-generator": "/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator", + "/enterprise/2.14/articles/creating-project-pages-using-the-command-line": "/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line", + "/enterprise/2.14/articles/creating-releases": "/enterprise/2.14/user/articles/creating-releases", + "/enterprise/2.14/articles/customizing-css-and-html-in-your-jekyll-theme": "/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme", + "/enterprise/2.14/articles/customizing-how-changed-files-appear-on-github": "/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github", + "/enterprise/2.14/articles/customizing-your-profile": "/enterprise/2.14/user/articles/customizing-your-profile", + "/enterprise/2.14/articles/dealing-with-non-fast-forward-errors": "/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors", + "/enterprise/2.14/articles/defining-the-mergeability-of-pull-requests": "/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests", + "/enterprise/2.14/articles/deleting-a-label": "/enterprise/2.14/user/articles/deleting-a-label", + "/enterprise/2.14/articles/deleting-a-project-board": "/enterprise/2.14/user/articles/deleting-a-project-board", + "/enterprise/2.14/articles/deleting-a-repository": "/enterprise/2.14/user/articles/deleting-a-repository", + "/enterprise/2.14/articles/deleting-a-saved-reply": "/enterprise/2.14/user/articles/deleting-a-saved-reply", + "/enterprise/2.14/articles/deleting-a-team": "/enterprise/2.14/user/articles/deleting-a-team", + "/enterprise/2.14/articles/deleting-an-organization-account": "/enterprise/2.14/user/articles/deleting-an-organization-account", + "/enterprise/2.14/articles/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.14/articles/deleting-files": "/enterprise/2.14/user/articles/deleting-files", + "/enterprise/2.14/articles/deleting-your-user-account": "/enterprise/2.14/user/articles/deleting-your-user-account", + "/enterprise/2.14/articles/differences-between-commit-views": "/enterprise/2.14/user/articles/differences-between-commit-views", + "/enterprise/2.14/articles/disabling-issues": "/enterprise/2.14/user/articles/disabling-issues", + "/enterprise/2.14/articles/disabling-project-boards-in-a-repository": "/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository", + "/enterprise/2.14/articles/disabling-project-boards-in-your-organization": "/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization", + "/enterprise/2.14/articles/disabling-team-discussions-for-your-organization": "/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization", + "/enterprise/2.14/articles/disabling-two-factor-authentication-for-your-personal-account": "/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account", + "/enterprise/2.14/articles/disabling-wikis": "/enterprise/2.14/user/articles/disabling-wikis", + "/enterprise/2.14/articles/dismissing-a-pull-request-review": "/enterprise/2.14/user/articles/dismissing-a-pull-request-review", + "/enterprise/2.14/articles/distributing-large-binaries": "/enterprise/2.14/user/articles/distributing-large-binaries", + "/enterprise/2.14/articles/documenting-your-project-with-wikis": "/enterprise/2.14/user/articles/documenting-your-project-with-wikis", + "/enterprise/2.14/articles/duplicating-a-repository": "/enterprise/2.14/user/articles/duplicating-a-repository", + "/enterprise/2.14/articles/editing-a-label": "/enterprise/2.14/user/articles/editing-a-label", + "/enterprise/2.14/articles/editing-a-project-board": "/enterprise/2.14/user/articles/editing-a-project-board", + "/enterprise/2.14/articles/editing-a-saved-reply": "/enterprise/2.14/user/articles/editing-a-saved-reply", + "/enterprise/2.14/articles/editing-and-deleting-releases": "/enterprise/2.14/user/articles/editing-and-deleting-releases", + "/enterprise/2.14/articles/editing-and-sharing-content-with-gists": "/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists", + "/enterprise/2.14/articles/editing-files-in-another-users-repository": "/enterprise/2.14/user/articles/editing-files-in-another-users-repository", + "/enterprise/2.14/articles/editing-files-in-your-repository": "/enterprise/2.14/user/articles/editing-files-in-your-repository", + "/enterprise/2.14/articles/editing-or-deleting-a-team-discussion": "/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion", + "/enterprise/2.14/articles/editing-wiki-content": "/enterprise/2.14/user/articles/editing-wiki-content", + "/enterprise/2.14/articles/emoji-on-github-pages": "/enterprise/2.14/user/articles/emoji-on-github-pages", + "/enterprise/2.14/articles/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.14/articles/enabling-branch-restrictions": "/enterprise/2.14/user/articles/enabling-branch-restrictions", + "/enterprise/2.14/articles/enabling-required-commit-signing": "/enterprise/2.14/user/articles/enabling-required-commit-signing", + "/enterprise/2.14/articles/enabling-required-reviews-for-pull-requests": "/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests", + "/enterprise/2.14/articles/enabling-required-status-checks": "/enterprise/2.14/user/articles/enabling-required-status-checks", + "/enterprise/2.14/articles/error-agent-admitted-failure-to-sign": "/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign", + "/enterprise/2.14/articles/error-bad-file-number": "/enterprise/2.14/user/articles/error-bad-file-number", + "/enterprise/2.14/articles/error-key-already-in-use": "/enterprise/2.14/user/articles/error-key-already-in-use", + "/enterprise/2.14/articles/error-permission-denied-publickey": "/enterprise/2.14/user/articles/error-permission-denied-publickey", + "/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-other-user": "/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user", + "/enterprise/2.14/articles/error-permission-to-userrepo-denied-to-userother-repo": "/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo", + "/enterprise/2.14/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", + "/enterprise/2.14/articles/error-repository-not-found": "/enterprise/2.14/user/articles/error-repository-not-found", + "/enterprise/2.14/articles/error-ssh-add-illegal-option----k": "/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k", + "/enterprise/2.14/articles/error-were-doing-an-ssh-key-audit": "/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit", + "/enterprise/2.14/articles/exploring-projects-on-github": "/enterprise/2.14/user/articles/exploring-projects-on-github", + "/enterprise/2.14/articles/file-attachments-on-issues-and-pull-requests": "/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests", + "/enterprise/2.14/articles/files-that-start-with-an-underscore-are-missing": "/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing", + "/enterprise/2.14/articles/filtering-cards-on-a-project-board": "/enterprise/2.14/user/articles/filtering-cards-on-a-project-board", + "/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-assignees": "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees", + "/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-labels": "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels", + "/enterprise/2.14/articles/filtering-issues-and-pull-requests-by-milestone": "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone", + "/enterprise/2.14/articles/filtering-issues-and-pull-requests": "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests", + "/enterprise/2.14/articles/filtering-pull-requests-by-review-status": "/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status", + "/enterprise/2.14/articles/finding-changed-methods-and-functions-in-a-pull-request": "/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request", + "/enterprise/2.14/articles/finding-files-on-github": "/enterprise/2.14/user/articles/finding-files-on-github", + "/enterprise/2.14/articles/finding-information-in-a-repository": "/enterprise/2.14/user/articles/finding-information-in-a-repository", + "/enterprise/2.14/articles/following-people": "/enterprise/2.14/user/articles/following-people", + "/enterprise/2.14/articles/fork-a-repo": "/enterprise/2.14/user/articles/fork-a-repo", + "/enterprise/2.14/articles/forking-and-cloning-gists": "/enterprise/2.14/user/articles/forking-and-cloning-gists", + "/enterprise/2.14/articles/further-reading-on-github-pages": "/enterprise/2.14/user/articles/further-reading-on-github-pages", + "/enterprise/2.14/articles/generating-a-new-gpg-key": "/enterprise/2.14/user/articles/generating-a-new-gpg-key", + "/enterprise/2.14/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", + "/enterprise/2.14/articles/generic-jekyll-build-failures": "/enterprise/2.14/user/articles/generic-jekyll-build-failures", + "/enterprise/2.14/articles/getting-changes-from-a-remote-repository": "/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository", + "/enterprise/2.14/articles/getting-permanent-links-to-files": "/enterprise/2.14/user/articles/getting-permanent-links-to-files", + "/enterprise/2.14/articles/getting-started-with-git-and-github": "/enterprise/2.14/user/articles/getting-started-with-git-and-github", + "/enterprise/2.14/articles/getting-started-with-notifications": "/enterprise/2.14/user/articles/getting-started-with-notifications", + "/enterprise/2.14/articles/getting-started-with-searching-on-github": "/enterprise/2.14/user/articles/getting-started-with-searching-on-github", + "/enterprise/2.14/articles/getting-started-with-the-api": "/enterprise/2.14/user/articles/getting-started-with-the-api", + "/enterprise/2.14/articles/getting-started-with-writing-and-formatting-on-github": "/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github", + "/enterprise/2.14/articles/getting-the-download-count-for-your-releases": "/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases", + "/enterprise/2.14/articles/git-and-github-learning-resources": "/enterprise/2.14/user/articles/git-and-github-learning-resources", + "/enterprise/2.14/articles/git-automation-with-oauth-tokens": "/enterprise/2.14/user/articles/git-automation-with-oauth-tokens", + "/enterprise/2.14/articles/git-cheatsheet": "/enterprise/2.14/user/articles/git-cheatsheet", + "/enterprise/2.14/articles/git-workflows": "/enterprise/2.14/user/articles/git-workflows", + "/enterprise/2.14/articles/github-flow": "/enterprise/2.14/user/articles/github-flow", + "/enterprise/2.14/articles/github-glossary": "/enterprise/2.14/user/articles/github-glossary", + "/enterprise/2.14/articles/giving-team-maintainer-permissions-to-an-organization-member": "/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member", + "/enterprise/2.14/articles/https-cloning-errors": "/enterprise/2.14/user/articles/https-cloning-errors", + "/enterprise/2.14/articles/ignoring-files": "/enterprise/2.14/user/articles/ignoring-files", + "/enterprise/2.14/articles/importing-a-git-repository-using-the-command-line": "/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line", + "/enterprise/2.14/articles/importing-source-code-to-github": "/enterprise/2.14/user/articles/importing-source-code-to-github", + "/enterprise/2.14/articles/incorporating-changes-from-a-pull-request": "/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request", + "/enterprise/2.14/articles/initializing-an-empty-repository-with-a-readme": "/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme", + "/enterprise/2.14/articles/installing-git-large-file-storage": "/enterprise/2.14/user/articles/installing-git-large-file-storage", + "/enterprise/2.14/articles/integrating-jira-with-your-organization-project-board": "/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board", + "/enterprise/2.14/articles/integrating-jira-with-your-personal-projects": "/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects", + "/enterprise/2.14/articles/inviting-collaborators-to-a-personal-repository": "/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository", + "/enterprise/2.14/articles/keeping-your-account-and-data-secure": "/enterprise/2.14/user/articles/keeping-your-account-and-data-secure", + "/enterprise/2.14/articles/keeping-your-organization-secure": "/enterprise/2.14/user/articles/keeping-your-organization-secure", + "/enterprise/2.14/articles/keyboard-shortcuts": "/enterprise/2.14/user/articles/keyboard-shortcuts", + "/enterprise/2.14/articles/labeling-issues-and-pull-requests": "/enterprise/2.14/user/articles/labeling-issues-and-pull-requests", + "/enterprise/2.14/articles/learning-about-git": "/enterprise/2.14/user/articles/learning-about-git", + "/enterprise/2.14/articles/learning-about-github": "/enterprise/2.14/user/articles/learning-about-github", + "/enterprise/2.14/articles/licensing-a-repository": "/enterprise/2.14/user/articles/licensing-a-repository", + "/enterprise/2.14/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", + "/enterprise/2.14/articles/linking-to-releases": "/enterprise/2.14/user/articles/linking-to-releases", + "/enterprise/2.14/articles/listing-the-forks-of-a-repository": "/enterprise/2.14/user/articles/listing-the-forks-of-a-repository", + "/enterprise/2.14/articles/listing-the-repositories-youre-watching": "/enterprise/2.14/user/articles/listing-the-repositories-youre-watching", + "/enterprise/2.14/articles/locking-conversations": "/enterprise/2.14/user/articles/locking-conversations", + "/enterprise/2.14/articles/managing-access-to-a-project-board-for-organization-members": "/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members", + "/enterprise/2.14/articles/managing-access-to-your-organizations-project-boards": "/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards", + "/enterprise/2.14/articles/managing-access-to-your-organizations-repositories": "/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories", + "/enterprise/2.14/articles/managing-access-to-your-personal-repositories": "/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories", + "/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-project-board": "/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board", + "/enterprise/2.14/articles/managing-an-individuals-access-to-an-organization-repository": "/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository", + "/enterprise/2.14/articles/managing-branches-in-your-repository": "/enterprise/2.14/user/articles/managing-branches-in-your-repository", + "/enterprise/2.14/articles/managing-commit-signature-verification": "/enterprise/2.14/user/articles/managing-commit-signature-verification", + "/enterprise/2.14/articles/managing-contribution-graphs-on-your-profile": "/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile", + "/enterprise/2.14/articles/managing-disruptive-comments": "/enterprise/2.14/user/articles/managing-disruptive-comments", + "/enterprise/2.14/articles/managing-email-preferences": "/enterprise/2.14/user/articles/managing-email-preferences", + "/enterprise/2.14/articles/managing-files-on-github": "/enterprise/2.14/user/articles/managing-files-on-github", + "/enterprise/2.14/articles/managing-files-using-the-command-line": "/enterprise/2.14/user/articles/managing-files-using-the-command-line", + "/enterprise/2.14/articles/managing-membership-in-your-organization": "/enterprise/2.14/user/articles/managing-membership-in-your-organization", + "/enterprise/2.14/articles/managing-organization-settings": "/enterprise/2.14/user/articles/managing-organization-settings", + "/enterprise/2.14/articles/managing-peoples-access-to-your-organization-with-roles": "/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles", + "/enterprise/2.14/articles/managing-project-boards": "/enterprise/2.14/user/articles/managing-project-boards", + "/enterprise/2.14/articles/managing-releases-in-a-repository": "/enterprise/2.14/user/articles/managing-releases-in-a-repository", + "/enterprise/2.14/articles/managing-remote-repositories": "/enterprise/2.14/user/articles/managing-remote-repositories", + "/enterprise/2.14/articles/managing-repository-settings": "/enterprise/2.14/user/articles/managing-repository-settings", + "/enterprise/2.14/articles/managing-team-access-to-an-organization-project-board": "/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board", + "/enterprise/2.14/articles/managing-team-access-to-an-organization-repository": "/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository", + "/enterprise/2.14/articles/managing-user-account-settings": "/enterprise/2.14/user/articles/managing-user-account-settings", + "/enterprise/2.14/articles/managing-your-membership-in-organizations": "/enterprise/2.14/user/articles/managing-your-membership-in-organizations", + "/enterprise/2.14/articles/managing-your-notifications": "/enterprise/2.14/user/articles/managing-your-notifications", + "/enterprise/2.14/articles/managing-your-work-with-issues": "/enterprise/2.14/user/articles/managing-your-work-with-issues", + "/enterprise/2.14/articles/manually-creating-a-single-issue-template-for-your-repository": "/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository", + "/enterprise/2.14/articles/mapping-geojson-files-on-github": "/enterprise/2.14/user/articles/mapping-geojson-files-on-github", + "/enterprise/2.14/articles/marking-notifications-as-read": "/enterprise/2.14/user/articles/marking-notifications-as-read", + "/enterprise/2.14/articles/mentions-on-github-pages": "/enterprise/2.14/user/articles/mentions-on-github-pages", + "/enterprise/2.14/articles/merging-a-pull-request": "/enterprise/2.14/user/articles/merging-a-pull-request", + "/enterprise/2.14/articles/merging-an-upstream-repository-into-your-fork": "/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork", + "/enterprise/2.14/articles/migrating-your-organization-to-improved-organization-permissions": "/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions", + "/enterprise/2.14/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": "/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions", + "/enterprise/2.14/articles/mime-types-on-github-pages": "/enterprise/2.14/user/articles/mime-types-on-github-pages", + "/enterprise/2.14/articles/moderating-comments-and-conversations": "/enterprise/2.14/user/articles/moderating-comments-and-conversations", + "/enterprise/2.14/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", + "/enterprise/2.14/articles/moving-a-file-to-a-new-location-using-the-command-line": "/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line", + "/enterprise/2.14/articles/moving-a-file-to-a-new-location": "/enterprise/2.14/user/articles/moving-a-file-to-a-new-location", + "/enterprise/2.14/articles/moving-a-team-in-your-organizations-hierarchy": "/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy", + "/enterprise/2.14/articles/opening-an-issue-from-code": "/enterprise/2.14/user/articles/opening-an-issue-from-code", + "/enterprise/2.14/articles/organizing-information-with-tables": "/enterprise/2.14/user/articles/organizing-information-with-tables", + "/enterprise/2.14/articles/organizing-members-into-teams": "/enterprise/2.14/user/articles/organizing-members-into-teams", + "/enterprise/2.14/articles/page-build-failed-config-file-error": "/enterprise/2.14/user/articles/page-build-failed-config-file-error", + "/enterprise/2.14/articles/page-build-failed-date-is-not-a-valid-datetime": "/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime", + "/enterprise/2.14/articles/page-build-failed-file-does-not-exist-in-includes-directory": "/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory", + "/enterprise/2.14/articles/page-build-failed-file-is-a-symlink": "/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink", + "/enterprise/2.14/articles/page-build-failed-file-is-not-properly-utf-8-encoded": "/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded", + "/enterprise/2.14/articles/page-build-failed-invalid-highlighter-language": "/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language", + "/enterprise/2.14/articles/page-build-failed-invalid-post-date": "/enterprise/2.14/user/articles/page-build-failed-invalid-post-date", + "/enterprise/2.14/articles/page-build-failed-invalid-sass-or-scss": "/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss", + "/enterprise/2.14/articles/page-build-failed-invalid-submodule": "/enterprise/2.14/user/articles/page-build-failed-invalid-submodule", + "/enterprise/2.14/articles/page-build-failed-invalid-yaml-in-data-file": "/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file", + "/enterprise/2.14/articles/page-build-failed-markdown-errors": "/enterprise/2.14/user/articles/page-build-failed-markdown-errors", + "/enterprise/2.14/articles/page-build-failed-missing-docs-folder": "/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder", + "/enterprise/2.14/articles/page-build-failed-missing-submodule": "/enterprise/2.14/user/articles/page-build-failed-missing-submodule", + "/enterprise/2.14/articles/page-build-failed-relative-permalinks-configured": "/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured", + "/enterprise/2.14/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": "/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository", + "/enterprise/2.14/articles/page-build-failed-syntax-error-in-for-loop": "/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop", + "/enterprise/2.14/articles/page-build-failed-tag-not-properly-closed": "/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed", + "/enterprise/2.14/articles/page-build-failed-tag-not-properly-terminated": "/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated", + "/enterprise/2.14/articles/page-build-failed-unknown-tag-error": "/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error", + "/enterprise/2.14/articles/permission-levels-for-a-user-account-repository": "/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository", + "/enterprise/2.14/articles/permission-levels-for-an-organization": "/enterprise/2.14/user/articles/permission-levels-for-an-organization", + "/enterprise/2.14/articles/personalizing-your-profile": "/enterprise/2.14/user/articles/personalizing-your-profile", + "/enterprise/2.14/articles/pinning-a-team-discussion": "/enterprise/2.14/user/articles/pinning-a-team-discussion", + "/enterprise/2.14/articles/pinning-items-to-your-profile": "/enterprise/2.14/user/articles/pinning-items-to-your-profile", + "/enterprise/2.14/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", + "/enterprise/2.14/articles/preventing-unauthorized-access": "/enterprise/2.14/user/articles/preventing-unauthorized-access", + "/enterprise/2.14/articles/project-board-permissions-for-an-organization": "/enterprise/2.14/user/articles/project-board-permissions-for-an-organization", + "/enterprise/2.14/articles/proposing-changes-to-your-work-with-pull-requests": "/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests", + "/enterprise/2.14/articles/publicizing-or-hiding-organization-membership": "/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership", + "/enterprise/2.14/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", + "/enterprise/2.14/articles/pushing-commits-to-a-remote-repository": "/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository", + "/enterprise/2.14/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", + "/enterprise/2.14/articles/recovering-your-ssh-key-passphrase": "/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase", + "/enterprise/2.14/articles/redirects-on-github-pages": "/enterprise/2.14/user/articles/redirects-on-github-pages", + "/enterprise/2.14/articles/reinstating-a-former-member-of-your-organization": "/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization", + "/enterprise/2.14/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", + "/enterprise/2.14/articles/remembering-your-github-username-or-email": "/enterprise/2.14/user/articles/remembering-your-github-username-or-email", + "/enterprise/2.14/articles/removing-a-collaborator-from-a-personal-repository": "/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository", + "/enterprise/2.14/articles/removing-a-member-from-your-organization": "/enterprise/2.14/user/articles/removing-a-member-from-your-organization", + "/enterprise/2.14/articles/removing-a-remote": "/enterprise/2.14/user/articles/removing-a-remote", + "/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", + "/enterprise/2.14/articles/removing-an-outside-collaborator-from-an-organization-repository": "/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository", + "/enterprise/2.14/articles/removing-files-from-a-repositorys-history": "/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history", + "/enterprise/2.14/articles/removing-files-from-git-large-file-storage": "/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage", + "/enterprise/2.14/articles/removing-organization-members-from-a-team": "/enterprise/2.14/user/articles/removing-organization-members-from-a-team", + "/enterprise/2.14/articles/removing-sensitive-data-from-a-repository": "/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository", + "/enterprise/2.14/articles/removing-yourself-from-a-collaborators-repository": "/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository", + "/enterprise/2.14/articles/removing-yourself-from-an-organization": "/enterprise/2.14/user/articles/removing-yourself-from-an-organization", + "/enterprise/2.14/articles/renaming-a-file-using-the-command-line": "/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line", + "/enterprise/2.14/articles/renaming-a-file": "/enterprise/2.14/user/articles/renaming-a-file", + "/enterprise/2.14/articles/renaming-a-remote": "/enterprise/2.14/user/articles/renaming-a-remote", + "/enterprise/2.14/articles/renaming-a-repository": "/enterprise/2.14/user/articles/renaming-a-repository", + "/enterprise/2.14/articles/renaming-a-team": "/enterprise/2.14/user/articles/renaming-a-team", + "/enterprise/2.14/articles/renaming-an-organization": "/enterprise/2.14/user/articles/renaming-an-organization", + "/enterprise/2.14/articles/rendering-and-diffing-images": "/enterprise/2.14/user/articles/rendering-and-diffing-images", + "/enterprise/2.14/articles/rendering-csv-and-tsv-data": "/enterprise/2.14/user/articles/rendering-csv-and-tsv-data", + "/enterprise/2.14/articles/rendering-differences-in-prose-documents": "/enterprise/2.14/user/articles/rendering-differences-in-prose-documents", + "/enterprise/2.14/articles/rendering-pdf-documents": "/enterprise/2.14/user/articles/rendering-pdf-documents", + "/enterprise/2.14/articles/reopening-a-closed-project-board": "/enterprise/2.14/user/articles/reopening-a-closed-project-board", + "/enterprise/2.14/articles/repository-metadata-on-github-pages": "/enterprise/2.14/user/articles/repository-metadata-on-github-pages", + "/enterprise/2.14/articles/repository-permission-levels-for-an-organization": "/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization", + "/enterprise/2.14/articles/requesting-a-pull-request-review": "/enterprise/2.14/user/articles/requesting-a-pull-request-review", + "/enterprise/2.14/articles/requesting-a-trial-of-github-enterprise": "/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise", + "/enterprise/2.14/articles/requesting-to-add-a-child-team": "/enterprise/2.14/user/articles/requesting-to-add-a-child-team", + "/enterprise/2.14/articles/requesting-to-add-or-change-a-parent-team": "/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team", + "/enterprise/2.14/articles/requiring-two-factor-authentication-in-your-organization": "/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization", + "/enterprise/2.14/articles/resolving-a-merge-conflict-on-github": "/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github", + "/enterprise/2.14/articles/resolving-a-merge-conflict-using-the-command-line": "/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line", + "/enterprise/2.14/articles/resolving-git-large-file-storage-upload-failures": "/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures", + "/enterprise/2.14/articles/resolving-merge-conflicts-after-a-git-rebase": "/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase", + "/enterprise/2.14/articles/restricting-repository-creation-in-your-organization": "/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization", + "/enterprise/2.14/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.14/articles/reverting-a-pull-request": "/enterprise/2.14/user/articles/reverting-a-pull-request", + "/enterprise/2.14/articles/reviewing-changes-in-pull-requests": "/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests", + "/enterprise/2.14/articles/reviewing-proposed-changes-in-a-pull-request": "/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request", + "/enterprise/2.14/articles/reviewing-the-audit-log-for-your-organization": "/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization", + "/enterprise/2.14/articles/reviewing-your-authorized-applications-oauth": "/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth", + "/enterprise/2.14/articles/reviewing-your-authorized-integrations": "/enterprise/2.14/user/articles/reviewing-your-authorized-integrations", + "/enterprise/2.14/articles/reviewing-your-deploy-keys": "/enterprise/2.14/user/articles/reviewing-your-deploy-keys", + "/enterprise/2.14/articles/reviewing-your-organizations-installed-integrations": "/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations", + "/enterprise/2.14/articles/reviewing-your-security-log": "/enterprise/2.14/user/articles/reviewing-your-security-log", + "/enterprise/2.14/articles/reviewing-your-ssh-keys": "/enterprise/2.14/user/articles/reviewing-your-ssh-keys", + "/enterprise/2.14/articles/saving-repositories-with-stars": "/enterprise/2.14/user/articles/saving-repositories-with-stars", + "/enterprise/2.14/articles/searching-code": "/enterprise/2.14/user/articles/searching-code", + "/enterprise/2.14/articles/searching-commits": "/enterprise/2.14/user/articles/searching-commits", + "/enterprise/2.14/articles/searching-for-repositories": "/enterprise/2.14/user/articles/searching-for-repositories", + "/enterprise/2.14/articles/searching-in-forks": "/enterprise/2.14/user/articles/searching-in-forks", + "/enterprise/2.14/articles/searching-issues-and-pull-requests": "/enterprise/2.14/user/articles/searching-issues-and-pull-requests", + "/enterprise/2.14/articles/searching-on-github": "/enterprise/2.14/user/articles/searching-on-github", + "/enterprise/2.14/articles/searching-topics": "/enterprise/2.14/user/articles/searching-topics", + "/enterprise/2.14/articles/searching-users": "/enterprise/2.14/user/articles/searching-users", + "/enterprise/2.14/articles/searching-wikis": "/enterprise/2.14/user/articles/searching-wikis", + "/enterprise/2.14/articles/securing-your-account-with-two-factor-authentication-2fa": "/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa", + "/enterprise/2.14/articles/set-up-git": "/enterprise/2.14/user/articles/set-up-git", + "/enterprise/2.14/articles/setting-a-backup-email-address": "/enterprise/2.14/user/articles/setting-a-backup-email-address", + "/enterprise/2.14/articles/setting-guidelines-for-repository-contributors": "/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors", + "/enterprise/2.14/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": "/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization", + "/enterprise/2.14/articles/setting-repository-visibility": "/enterprise/2.14/user/articles/setting-repository-visibility", + "/enterprise/2.14/articles/setting-the-default-branch": "/enterprise/2.14/user/articles/setting-the-default-branch", + "/enterprise/2.14/articles/setting-up-your-github-pages-site-locally-with-jekyll": "/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll", + "/enterprise/2.14/articles/setting-up-your-project-for-healthy-contributions": "/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions", + "/enterprise/2.14/articles/setting-your-commit-email-address": "/enterprise/2.14/user/articles/setting-your-commit-email-address", + "/enterprise/2.14/articles/setting-your-teams-profile-picture": "/enterprise/2.14/user/articles/setting-your-teams-profile-picture", + "/enterprise/2.14/articles/setting-your-username-in-git": "/enterprise/2.14/user/articles/setting-your-username-in-git", + "/enterprise/2.14/articles/sharing-filters": "/enterprise/2.14/user/articles/sharing-filters", + "/enterprise/2.14/articles/signing-commits": "/enterprise/2.14/user/articles/signing-commits", + "/enterprise/2.14/articles/signing-tags": "/enterprise/2.14/user/articles/signing-tags", + "/enterprise/2.14/articles/signing-up-for-github": "/enterprise/2.14/user/articles/signing-up-for-github", + "/enterprise/2.14/articles/sitemaps-for-github-pages": "/enterprise/2.14/user/articles/sitemaps-for-github-pages", + "/enterprise/2.14/articles/sorting-issues-and-pull-requests": "/enterprise/2.14/user/articles/sorting-issues-and-pull-requests", + "/enterprise/2.14/articles/sorting-search-results": "/enterprise/2.14/user/articles/sorting-search-results", + "/enterprise/2.14/articles/source-code-migration-tools": "/enterprise/2.14/user/articles/source-code-migration-tools", + "/enterprise/2.14/articles/splitting-a-subfolder-out-into-a-new-repository": "/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository", + "/enterprise/2.14/articles/subscribing-to-and-unsubscribing-from-notifications": "/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications", + "/enterprise/2.14/articles/subversion-properties-supported-by-github": "/enterprise/2.14/user/articles/subversion-properties-supported-by-github", + "/enterprise/2.14/articles/sudo-mode": "/enterprise/2.14/user/articles/sudo-mode", + "/enterprise/2.14/articles/support-for-subversion-clients": "/enterprise/2.14/user/articles/support-for-subversion-clients", + "/enterprise/2.14/articles/supported-browsers": "/enterprise/2.14/user/articles/supported-browsers", + "/enterprise/2.14/articles/syncing-a-fork": "/enterprise/2.14/user/articles/syncing-a-fork", + "/enterprise/2.14/articles/telling-git-about-your-signing-key": "/enterprise/2.14/user/articles/telling-git-about-your-signing-key", + "/enterprise/2.14/articles/testing-your-ssh-connection": "/enterprise/2.14/user/articles/testing-your-ssh-connection", + "/enterprise/2.14/articles/tracking-changes-in-a-comment": "/enterprise/2.14/user/articles/tracking-changes-in-a-comment", + "/enterprise/2.14/articles/tracking-changes-in-a-file": "/enterprise/2.14/user/articles/tracking-changes-in-a-file", + "/enterprise/2.14/articles/tracking-progress-on-your-project-board": "/enterprise/2.14/user/articles/tracking-progress-on-your-project-board", + "/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-milestones": "/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones", + "/enterprise/2.14/articles/tracking-the-progress-of-your-work-with-project-boards": "/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards", + "/enterprise/2.14/articles/transferring-a-repository": "/enterprise/2.14/user/articles/transferring-a-repository", + "/enterprise/2.14/articles/transferring-organization-ownership": "/enterprise/2.14/user/articles/transferring-organization-ownership", + "/enterprise/2.14/articles/troubleshooting-commit-signature-verification": "/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification", + "/enterprise/2.14/articles/troubleshooting-commits-on-your-timeline": "/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline", + "/enterprise/2.14/articles/troubleshooting-commits": "/enterprise/2.14/user/articles/troubleshooting-commits", + "/enterprise/2.14/articles/troubleshooting-github-pages-builds": "/enterprise/2.14/user/articles/troubleshooting-github-pages-builds", + "/enterprise/2.14/articles/troubleshooting-search-queries": "/enterprise/2.14/user/articles/troubleshooting-search-queries", + "/enterprise/2.14/articles/troubleshooting-ssh": "/enterprise/2.14/user/articles/troubleshooting-ssh", + "/enterprise/2.14/articles/types-of-github-accounts": "/enterprise/2.14/user/articles/types-of-github-accounts", + "/enterprise/2.14/articles/types-of-required-status-checks": "/enterprise/2.14/user/articles/types-of-required-status-checks", + "/enterprise/2.14/articles/understanding-connections-between-repositories": "/enterprise/2.14/user/articles/understanding-connections-between-repositories", + "/enterprise/2.14/articles/understanding-the-search-syntax": "/enterprise/2.14/user/articles/understanding-the-search-syntax", + "/enterprise/2.14/articles/unpublishing-a-project-pages-site": "/enterprise/2.14/user/articles/unpublishing-a-project-pages-site", + "/enterprise/2.14/articles/unpublishing-a-user-pages-site": "/enterprise/2.14/user/articles/unpublishing-a-user-pages-site", + "/enterprise/2.14/articles/updating-an-expired-gpg-key": "/enterprise/2.14/user/articles/updating-an-expired-gpg-key", + "/enterprise/2.14/articles/updating-credentials-from-the-osx-keychain": "/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain", + "/enterprise/2.14/articles/updating-your-github-access-credentials": "/enterprise/2.14/user/articles/updating-your-github-access-credentials", + "/enterprise/2.14/articles/updating-your-markdown-processor-to-kramdown": "/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown", + "/enterprise/2.14/articles/user-organization-and-project-pages": "/enterprise/2.14/user/articles/user-organization-and-project-pages", + "/enterprise/2.14/articles/using-a-static-site-generator-other-than-jekyll": "/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll", + "/enterprise/2.14/articles/using-a-verified-email-address-in-your-gpg-key": "/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key", + "/enterprise/2.14/articles/using-advanced-git-commands": "/enterprise/2.14/user/articles/using-advanced-git-commands", + "/enterprise/2.14/articles/using-common-git-commands": "/enterprise/2.14/user/articles/using-common-git-commands", + "/enterprise/2.14/articles/using-git-rebase-on-the-command-line": "/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line", + "/enterprise/2.14/articles/using-github": "/enterprise/2.14/user/articles/using-github", + "/enterprise/2.14/articles/using-jekyll-as-a-static-site-generator-with-github-pages": "/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages", + "/enterprise/2.14/articles/using-saved-replies": "/enterprise/2.14/user/articles/using-saved-replies", + "/enterprise/2.14/articles/using-search-to-filter-issues-and-pull-requests": "/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests", + "/enterprise/2.14/articles/using-syntax-highlighting-on-github-pages": "/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages", + "/enterprise/2.14/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": "/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository", + "/enterprise/2.14/articles/versioning-large-files": "/enterprise/2.14/user/articles/versioning-large-files", + "/enterprise/2.14/articles/viewing-a-projects-contributors": "/enterprise/2.14/user/articles/viewing-a-projects-contributors", + "/enterprise/2.14/articles/viewing-a-pull-request-review": "/enterprise/2.14/user/articles/viewing-a-pull-request-review", + "/enterprise/2.14/articles/viewing-a-repositorys-network": "/enterprise/2.14/user/articles/viewing-a-repositorys-network", + "/enterprise/2.14/articles/viewing-a-summary-of-repository-activity": "/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity", + "/enterprise/2.14/articles/viewing-a-wikis-history-of-changes": "/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes", + "/enterprise/2.14/articles/viewing-all-of-your-issues-and-pull-requests": "/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests", + "/enterprise/2.14/articles/viewing-and-comparing-commits": "/enterprise/2.14/user/articles/viewing-and-comparing-commits", + "/enterprise/2.14/articles/viewing-branches-in-your-repository": "/enterprise/2.14/user/articles/viewing-branches-in-your-repository", + "/enterprise/2.14/articles/viewing-contributions-on-your-profile": "/enterprise/2.14/user/articles/viewing-contributions-on-your-profile", + "/enterprise/2.14/articles/viewing-jekyll-build-error-messages": "/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages", + "/enterprise/2.14/articles/viewing-peoples-roles-in-an-organization": "/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization", + "/enterprise/2.14/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", + "/enterprise/2.14/articles/viewing-your-milestones-progress": "/enterprise/2.14/user/articles/viewing-your-milestones-progress", + "/enterprise/2.14/articles/viewing-your-repositorys-tags": "/enterprise/2.14/user/articles/viewing-your-repositorys-tags", + "/enterprise/2.14/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", + "/enterprise/2.14/articles/visualizing-commits-in-a-repository": "/enterprise/2.14/user/articles/visualizing-commits-in-a-repository", + "/enterprise/2.14/articles/watching-and-unwatching-repositories": "/enterprise/2.14/user/articles/watching-and-unwatching-repositories", + "/enterprise/2.14/articles/watching-and-unwatching-team-discussions": "/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions", + "/enterprise/2.14/articles/what-are-the-differences-between-subversion-and-git": "/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git", + "/enterprise/2.14/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", + "/enterprise/2.14/articles/what-is-github-pages": "/enterprise/2.14/user/articles/what-is-github-pages", + "/enterprise/2.14/articles/which-remote-url-should-i-use": "/enterprise/2.14/user/articles/which-remote-url-should-i-use", + "/enterprise/2.14/articles/why-are-my-commits-in-the-wrong-order": "/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order", + "/enterprise/2.14/articles/why-are-my-commits-linked-to-the-wrong-user": "/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user", + "/enterprise/2.14/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", + "/enterprise/2.14/articles/why-is-git-always-asking-for-my-password": "/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password", + "/enterprise/2.14/articles/working-with-advanced-formatting": "/enterprise/2.14/user/articles/working-with-advanced-formatting", + "/enterprise/2.14/articles/working-with-forks": "/enterprise/2.14/user/articles/working-with-forks", + "/enterprise/2.14/articles/working-with-jupyter-notebook-files-on-github": "/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github", + "/enterprise/2.14/articles/working-with-large-files": "/enterprise/2.14/user/articles/working-with-large-files", + "/enterprise/2.14/articles/working-with-non-code-files": "/enterprise/2.14/user/articles/working-with-non-code-files", + "/enterprise/2.14/articles/working-with-pre-receive-hooks": "/enterprise/2.14/user/articles/working-with-pre-receive-hooks", + "/enterprise/2.14/articles/working-with-saved-replies": "/enterprise/2.14/user/articles/working-with-saved-replies", + "/enterprise/2.14/articles/working-with-ssh-key-passphrases": "/enterprise/2.14/user/articles/working-with-ssh-key-passphrases", + "/enterprise/2.14/articles/working-with-subversion-on-github": "/enterprise/2.14/user/articles/working-with-subversion-on-github", + "/enterprise/2.14/user/categories/admin/guidesistering-a-repository": "/enterprise/2.14/user/categories/administering-a-repository", + "/enterprise/2.14/categories/administering-a-repository": "/enterprise/2.14/user/categories/administering-a-repository", + "/enterprise/2.14/categories/authenticating-to-github": "/enterprise/2.14/user/categories/authenticating-to-github", + "/enterprise/2.14/categories/building-a-strong-community": "/enterprise/2.14/user/categories/building-a-strong-community", + "/enterprise/2.14/categories/collaborating-with-issues-and-pull-requests": "/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests", + "/enterprise/2.14/categories/committing-changes-to-your-project": "/enterprise/2.14/user/categories/committing-changes-to-your-project", + "/enterprise/2.14/categories/creating-cloning-and-archiving-repositories": "/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories", + "/enterprise/2.14/categories/customizing-github-pages": "/enterprise/2.14/user/categories/customizing-github-pages", + "/enterprise/2.14/categories/extending-github": "/enterprise/2.14/user/categories/extending-github", + "/enterprise/2.14/categories/getting-started-with-github": "/enterprise/2.14/user/categories/getting-started-with-github", + "/enterprise/2.14/categories/github-pages-basics": "/enterprise/2.14/user/categories/github-pages-basics", + "/enterprise/2.14/categories/importing-your-projects-to-github": "/enterprise/2.14/user/categories/importing-your-projects-to-github", + "/enterprise/2.14/categories/managing-files-in-a-repository": "/enterprise/2.14/user/categories/managing-files-in-a-repository", + "/enterprise/2.14/categories/managing-large-files": "/enterprise/2.14/user/categories/managing-large-files", + "/enterprise/2.14/categories/managing-your-work-on-github": "/enterprise/2.14/user/categories/managing-your-work-on-github", + "/enterprise/2.14/categories/receiving-notifications-about-activity-on-github": "/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github", + "/enterprise/2.14/categories/searching-for-information-on-github": "/enterprise/2.14/user/categories/searching-for-information-on-github", + "/enterprise/2.14/categories/setting-up-and-managing-organizations-and-teams": "/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams", + "/enterprise/2.14/categories/setting-up-and-managing-your-github-profile": "/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile", + "/enterprise/2.14/categories/setting-up-and-managing-your-github-user-account": "/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account", + "/enterprise/2.14/categories/using-git": "/enterprise/2.14/user/categories/using-git", + "/enterprise/2.14/categories/visualizing-repository-data-with-graphs": "/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs", + "/enterprise/2.14/categories/writing-on-github": "/enterprise/2.14/user/categories/writing-on-github", + "/enterprise/2.14/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": null, + "/enterprise/2.14/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": null, + "/enterprise/2.14/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": null, + "/enterprise/2.14/admin/articles/using-github-task-runner": null, + "/enterprise/2.14/admin/clustering/about-cluster-nodes": null, + "/enterprise/2.14/admin/clustering/clustering-overview": null, + "/enterprise/2.14/admin/clustering/differences-between-clustering-and-high-availability-ha": null, + "/enterprise/2.14/admin/clustering/evacuating-a-cluster-node": null, + "/enterprise/2.14/admin/clustering": null, + "/enterprise/2.14/admin/clustering/initializing-the-cluster": null, + "/enterprise/2.14/admin/clustering/managing-a-github-enterprise-server-cluster": null, + "/enterprise/2.14/admin/clustering/monitoring-cluster-nodes": null, + "/enterprise/2.14/admin/clustering/network-configuration": null, + "/enterprise/2.14/admin/clustering/replacing-a-cluster-node": null, + "/enterprise/2.14/admin/clustering/setting-up-the-cluster-instances": null, + "/enterprise/2.14/admin/clustering/upgrading-a-cluster": null, + "/enterprise/2.14/admin/developer-workflow/about-pre-receive-hooks": null, + "/enterprise/2.14/admin/developer-workflow/about-protected-branches-and-required-status-checks": null, + "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-on-your-appliance": null, + "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-a-repository": null, + "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": null, + "/enterprise/2.14/admin/developer-workflow/blocking-force-pushes": null, + "/enterprise/2.14/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": null, + "/enterprise/2.14/admin/developer-workflow/continuous-integration-using-jenkins": null, + "/enterprise/2.14/admin/developer-workflow/continuous-integration-using-travis-ci": null, + "/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-environment": null, + "/enterprise/2.14/admin/developer-workflow/creating-a-pre-receive-hook-script": null, + "/enterprise/2.14/admin/developer-workflow/customizing-your-instance-with-integrations": null, + "/enterprise/2.14/admin/developer-workflow/establishing-pull-request-merge-conditions": null, + "/enterprise/2.14/admin/developer-workflow": null, + "/enterprise/2.14/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": null, + "/enterprise/2.14/admin/developer-workflow/managing-projects-using-jira": null, + "/enterprise/2.14/admin/developer-workflow/troubleshooting-service-hooks": null, + "/enterprise/2.14/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": null, + "/enterprise/2.14/admin/developer-workflow/using-webhooks-for-continuous-integration": null, + "/enterprise/2.14/admin/enterprise-support/about-github-enterprise-support": null, + "/enterprise/2.14/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": null, + "/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": null, + "/enterprise/2.14/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": null, + "/enterprise/2.14/admin/enterprise-support/about-github-premium-support-for-github-enterprise": null, + "/enterprise/2.14/admin/enterprise-support": null, + "/enterprise/2.14/admin/enterprise-support/preparing-to-submit-a-ticket": null, + "/enterprise/2.14/admin/enterprise-support/providing-data-to-github-support": null, + "/enterprise/2.14/admin/enterprise-support/reaching-github-support": null, + "/enterprise/2.14/admin/enterprise-support/receiving-help-from-github-support": null, + "/enterprise/2.14/admin/enterprise-support/submitting-a-ticket": null, + "/enterprise/2.14/admin": null, + "/enterprise/2.14/admin/installation/about-geo-replication": null, + "/enterprise/2.14/admin/installation/about-high-availability-configuration": null, + "/enterprise/2.14/admin/installation/about-the-github-enterprise-server-api": null, + "/enterprise/2.14/admin/installation/accessing-the-administrative-shell-ssh": null, + "/enterprise/2.14/admin/installation/accessing-the-management-console": null, + "/enterprise/2.14/admin/installation/accessing-the-monitor-dashboard": null, + "/enterprise/2.14/admin/installation/activity-dashboard": null, + "/enterprise/2.14/admin/installation/audit-logging": null, + "/enterprise/2.14/admin/installation/audited-actions": null, + "/enterprise/2.14/admin/installation/command-line-utilities": null, + "/enterprise/2.14/admin/installation/configuring-a-hostname": null, + "/enterprise/2.14/admin/installation/configuring-an-outbound-web-proxy-server": null, + "/enterprise/2.14/admin/installation/configuring-backups-on-your-appliance": null, + "/enterprise/2.14/admin/installation/configuring-built-in-firewall-rules": null, + "/enterprise/2.14/admin/installation/configuring-collectd": null, + "/enterprise/2.14/admin/installation/configuring-dns-nameservers": null, + "/enterprise/2.14/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": null, + "/enterprise/2.14/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": null, + "/enterprise/2.14/admin/installation/configuring-git-large-file-storage": null, + "/enterprise/2.14/admin/installation/configuring-github-enterprise-server-for-high-availability": null, + "/enterprise/2.14/admin/installation/configuring-github-pages-on-your-appliance": null, + "/enterprise/2.14/admin/installation/configuring-rate-limits": null, + "/enterprise/2.14/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": null, + "/enterprise/2.14/admin/installation/configuring-the-github-enterprise-server-appliance": null, + "/enterprise/2.14/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": null, + "/enterprise/2.14/admin/installation/configuring-time-synchronization": null, + "/enterprise/2.14/admin/installation/configuring-tls": null, + "/enterprise/2.14/admin/installation/configuring-your-github-enterprise-server-network-settings": null, + "/enterprise/2.14/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": null, + "/enterprise/2.14/admin/installation/creating-a-high-availability-replica": null, + "/enterprise/2.14/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": null, + "/enterprise/2.14/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": null, + "/enterprise/2.14/admin/installation/enabling-and-scheduling-maintenance-mode": null, + "/enterprise/2.14/admin/installation/enabling-automatic-update-checks": null, + "/enterprise/2.14/admin/installation/enabling-private-mode": null, + "/enterprise/2.14/admin/installation/enabling-subdomain-isolation": null, + "/enterprise/2.14/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.14/admin/installation/increasing-cpu-or-memory-resources": null, + "/enterprise/2.14/admin/installation/increasing-storage-capacity": null, + "/enterprise/2.14/admin/installation": null, + "/enterprise/2.14/admin/installation/initiating-a-failover-to-your-replica-appliance": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-aws": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-azure": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-hyper-v": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-openstack-kvm": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-vmware": null, + "/enterprise/2.14/admin/installation/installing-github-enterprise-server-on-xenserver": null, + "/enterprise/2.14/admin/installation/log-forwarding": null, + "/enterprise/2.14/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": null, + "/enterprise/2.14/admin/installation/managing-your-github-enterprise-server-license": null, + "/enterprise/2.14/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": null, + "/enterprise/2.14/admin/installation/migrating-from-github-enterprise-1110x-to-2123": null, + "/enterprise/2.14/admin/installation/migrating-to-a-different-git-large-file-storage-server": null, + "/enterprise/2.14/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": null, + "/enterprise/2.14/admin/installation/monitoring-using-snmp": null, + "/enterprise/2.14/admin/installation/monitoring-your-github-enterprise-server-appliance": null, + "/enterprise/2.14/admin/installation/network-ports": null, + "/enterprise/2.14/admin/installation/recommended-alert-thresholds": null, + "/enterprise/2.14/admin/installation/recovering-a-high-availability-configuration": null, + "/enterprise/2.14/admin/installation/removing-a-high-availability-replica": null, + "/enterprise/2.14/admin/installation/searching-the-audit-log": null, + "/enterprise/2.14/admin/installation/setting-git-push-limits": null, + "/enterprise/2.14/admin/installation/setting-up-a-github-enterprise-server-instance": null, + "/enterprise/2.14/admin/installation/setting-up-a-staging-instance": null, + "/enterprise/2.14/admin/installation/setting-up-external-monitoring": null, + "/enterprise/2.14/admin/installation/site-admin-dashboard": null, + "/enterprise/2.14/admin/installation/system-overview": null, + "/enterprise/2.14/admin/installation/troubleshooting-ssl-errors": null, + "/enterprise/2.14/admin/installation/updating-the-virtual-machine-and-physical-resources": null, + "/enterprise/2.14/admin/installation/upgrade-requirements": null, + "/enterprise/2.14/admin/installation/upgrading-github-enterprise-server": null, + "/enterprise/2.14/admin/installation/using-github-enterprise-server-with-a-load-balancer": null, + "/enterprise/2.14/admin/installation/validating-your-domain-settings": null, + "/enterprise/2.14/admin/installation/viewing-push-logs": null, + "/enterprise/2.14/admin/migrations/about-migrations": null, + "/enterprise/2.14/admin/migrations/applying-the-imported-data-on-github-enterprise-server": null, + "/enterprise/2.14/admin/migrations/completing-the-import-on-github-enterprise-server": null, + "/enterprise/2.14/admin/migrations/exporting-migration-data-from-github-enterprise-server": null, + "/enterprise/2.14/admin/migrations/exporting-migration-data-from-githubcom": null, + "/enterprise/2.14/admin/migrations/exporting-the-github-enterprise-server-source-repositories": null, + "/enterprise/2.14/admin/migrations/exporting-the-githubcom-organizations-repositories": null, + "/enterprise/2.14/admin/migrations/generating-a-list-of-migration-conflicts": null, + "/enterprise/2.14/admin/migrations/importing-data-from-third-party-version-control-systems": null, + "/enterprise/2.14/admin/migrations/importing-migration-data-to-github-enterprise-server": null, + "/enterprise/2.14/admin/migrations": null, + "/enterprise/2.14/admin/migrations/preparing-the-github-enterprise-server-source-instance": null, + "/enterprise/2.14/admin/migrations/preparing-the-githubcom-source-organization": null, + "/enterprise/2.14/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": null, + "/enterprise/2.14/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": null, + "/enterprise/2.14/admin/migrations/reviewing-migration-conflicts": null, + "/enterprise/2.14/admin/migrations/reviewing-migration-data": null, + "/enterprise/2.14/admin/user-management/about-global-webhooks": null, + "/enterprise/2.14/admin/user-management/adding-people-to-teams": null, + "/enterprise/2.14/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": null, + "/enterprise/2.14/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": null, + "/enterprise/2.14/admin/user-management/archiving-and-unarchiving-repositories": null, + "/enterprise/2.14/admin/user-management/auditing-ssh-keys": null, + "/enterprise/2.14/admin/user-management/auditing-users-across-your-instance": null, + "/enterprise/2.14/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": null, + "/enterprise/2.14/admin/user-management/basic-account-settings": null, + "/enterprise/2.14/admin/user-management/best-practices-for-user-security": null, + "/enterprise/2.14/admin/user-management/changing-authentication-methods": null, + "/enterprise/2.14/admin/user-management/configuring-email-for-notifications": null, + "/enterprise/2.14/admin/user-management/configuring-visibility-for-organization-membership": null, + "/enterprise/2.14/admin/user-management/creating-organizations": null, + "/enterprise/2.14/admin/user-management/creating-teams": null, + "/enterprise/2.14/admin/user-management/customizing-user-messages-on-your-instance": null, + "/enterprise/2.14/admin/user-management/disabling-unauthenticated-sign-ups": null, + "/enterprise/2.14/admin/user-management": null, + "/enterprise/2.14/admin/user-management/managing-dormant-users": null, + "/enterprise/2.14/admin/user-management/managing-global-webhooks": null, + "/enterprise/2.14/admin/user-management/organizations-and-teams": null, + "/enterprise/2.14/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": null, + "/enterprise/2.14/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": null, + "/enterprise/2.14/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": null, + "/enterprise/2.14/admin/user-management/preventing-users-from-creating-organizations": null, + "/enterprise/2.14/admin/user-management/preventing-users-from-deleting-organization-repositories": null, + "/enterprise/2.14/admin/user-management/promoting-or-demoting-a-site-administrator": null, + "/enterprise/2.14/admin/user-management/rebuilding-contributions-data": null, + "/enterprise/2.14/admin/user-management/removing-users-from-teams-and-organizations": null, + "/enterprise/2.14/admin/user-management/repositories": null, + "/enterprise/2.14/admin/user-management/requiring-two-factor-authentication-for-an-organization": null, + "/enterprise/2.14/admin/user-management/suspending-and-unsuspending-users": null, + "/enterprise/2.14/admin/user-management/user-security": null, + "/enterprise/2.14/admin/user-management/using-built-in-authentication": null, + "/enterprise/2.14/admin/user-management/using-cas": null, + "/enterprise/2.14/admin/user-management/using-ldap": null, + "/enterprise/2.14/admin/user-management/using-saml": null, + "/enterprise/2.14": null, + "/enterprise/2.14/user/articles/3d-file-viewer": null, + "/enterprise/2.14/user/articles/about-archiving-repositories": null, + "/enterprise/2.14/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": null, + "/enterprise/2.14/user/articles/about-automation-for-project-boards": null, + "/enterprise/2.14/user/articles/about-branch-restrictions": null, + "/enterprise/2.14/user/articles/about-branches": null, + "/enterprise/2.14/user/articles/about-code-owners": null, + "/enterprise/2.14/user/articles/about-collaborative-development-models": null, + "/enterprise/2.14/user/articles/about-commit-signature-verification": null, + "/enterprise/2.14/user/articles/about-comparing-branches-in-pull-requests": null, + "/enterprise/2.14/user/articles/about-conversations-on-github": null, + "/enterprise/2.14/user/articles/about-duplicate-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/about-email-notifications-for-pushes-to-your-repository": null, + "/enterprise/2.14/user/articles/about-email-notifications": null, + "/enterprise/2.14/user/articles/about-forks": null, + "/enterprise/2.14/user/articles/about-git-large-file-storage": null, + "/enterprise/2.14/user/articles/about-git-rebase": null, + "/enterprise/2.14/user/articles/about-git-subtree-merges": null, + "/enterprise/2.14/user/articles/about-github-pages-and-jekyll": null, + "/enterprise/2.14/user/articles/about-issue-and-pull-request-templates": null, + "/enterprise/2.14/user/articles/about-issues": null, + "/enterprise/2.14/user/articles/about-jekyll-themes-on-github": null, + "/enterprise/2.14/user/articles/about-labels": null, + "/enterprise/2.14/user/articles/about-merge-conflicts": null, + "/enterprise/2.14/user/articles/about-merge-methods-on-github": null, + "/enterprise/2.14/user/articles/about-milestones": null, + "/enterprise/2.14/user/articles/about-notifications": null, + "/enterprise/2.14/user/articles/about-organization-membership": null, + "/enterprise/2.14/user/articles/about-organizations": null, + "/enterprise/2.14/user/articles/about-project-boards": null, + "/enterprise/2.14/user/articles/about-protected-branches": null, + "/enterprise/2.14/user/articles/about-pull-request-merges": null, + "/enterprise/2.14/user/articles/about-pull-request-reviews": null, + "/enterprise/2.14/user/articles/about-pull-requests": null, + "/enterprise/2.14/user/articles/about-readmes": null, + "/enterprise/2.14/user/articles/about-releases": null, + "/enterprise/2.14/user/articles/about-remote-repositories": null, + "/enterprise/2.14/user/articles/about-repositories": null, + "/enterprise/2.14/user/articles/about-repository-graphs": null, + "/enterprise/2.14/user/articles/about-repository-languages": null, + "/enterprise/2.14/user/articles/about-required-commit-signing": null, + "/enterprise/2.14/user/articles/about-required-reviews-for-pull-requests": null, + "/enterprise/2.14/user/articles/about-required-status-checks": null, + "/enterprise/2.14/user/articles/about-saved-replies": null, + "/enterprise/2.14/user/articles/about-searching-on-github": null, + "/enterprise/2.14/user/articles/about-ssh": null, + "/enterprise/2.14/user/articles/about-status-checks": null, + "/enterprise/2.14/user/articles/about-task-lists": null, + "/enterprise/2.14/user/articles/about-team-discussions": null, + "/enterprise/2.14/user/articles/about-teams": null, + "/enterprise/2.14/user/articles/about-two-factor-authentication": null, + "/enterprise/2.14/user/articles/about-web-notifications": null, + "/enterprise/2.14/user/articles/about-webhooks": null, + "/enterprise/2.14/user/articles/about-wikis": null, + "/enterprise/2.14/user/articles/about-writing-and-formatting-on-github": null, + "/enterprise/2.14/user/articles/about-your-organization-dashboard": null, + "/enterprise/2.14/user/articles/about-your-organizations-news-feed": null, + "/enterprise/2.14/user/articles/about-your-organizations-profile": null, + "/enterprise/2.14/user/articles/about-your-personal-dashboard": null, + "/enterprise/2.14/user/articles/about-your-profile": null, + "/enterprise/2.14/user/articles/access-permissions-on-github": null, + "/enterprise/2.14/user/articles/accessing-an-organization": null, + "/enterprise/2.14/user/articles/accessing-basic-repository-data": null, + "/enterprise/2.14/user/articles/accessing-github-using-two-factor-authentication": null, + "/enterprise/2.14/user/articles/accessing-your-notifications": null, + "/enterprise/2.14/user/articles/accessing-your-organizations-settings": null, + "/enterprise/2.14/user/articles/adding-a-file-to-a-repository-using-the-command-line": null, + "/enterprise/2.14/user/articles/adding-a-file-to-a-repository": null, + "/enterprise/2.14/user/articles/adding-a-jekyll-theme-to-your-github-pages-site": null, + "/enterprise/2.14/user/articles/adding-a-license-to-a-repository": null, + "/enterprise/2.14/user/articles/adding-a-new-gpg-key-to-your-github-account": null, + "/enterprise/2.14/user/articles/adding-a-new-ssh-key-to-your-github-account": null, + "/enterprise/2.14/user/articles/adding-a-remote": null, + "/enterprise/2.14/user/articles/adding-an-email-address-to-your-github-account": null, + "/enterprise/2.14/user/articles/adding-an-existing-project-to-github-using-the-command-line": null, + "/enterprise/2.14/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": null, + "/enterprise/2.14/user/articles/adding-issues-and-pull-requests-to-a-project-board": null, + "/enterprise/2.14/user/articles/adding-jekyll-plugins-to-a-github-pages-site": null, + "/enterprise/2.14/user/articles/adding-notes-to-a-project-board": null, + "/enterprise/2.14/user/articles/adding-or-editing-wiki-pages": null, + "/enterprise/2.14/user/articles/adding-organization-members-to-a-team": null, + "/enterprise/2.14/user/articles/adding-outside-collaborators-to-repositories-in-your-organization": null, + "/enterprise/2.14/user/articles/adding-people-to-your-organization": null, + "/enterprise/2.14/user/articles/adding-support-resources-to-your-project": null, + "/enterprise/2.14/user/articles/additional-customizations-for-github-pages": null, + "/enterprise/2.14/user/articles/addressing-merge-conflicts": null, + "/enterprise/2.14/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.14/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": null, + "/enterprise/2.14/user/articles/allowing-people-to-fork-private-repositories-in-your-organization": null, + "/enterprise/2.14/user/articles/analyzing-changes-to-a-repositorys-content": null, + "/enterprise/2.14/user/articles/applying-labels-to-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/approving-a-pull-request-with-required-reviews": null, + "/enterprise/2.14/user/articles/archiving-a-github-repository": null, + "/enterprise/2.14/user/articles/archiving-repositories": null, + "/enterprise/2.14/user/articles/assigning-issues-and-pull-requests-to-other-github-users": null, + "/enterprise/2.14/user/articles/associating-an-email-with-your-gpg-key": null, + "/enterprise/2.14/user/articles/associating-milestones-with-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/associating-text-editors-with-git": null, + "/enterprise/2.14/user/articles/authorizing-oauth-apps": null, + "/enterprise/2.14/user/articles/autolinked-references-and-urls": null, + "/enterprise/2.14/user/articles/backing-up-a-repository": null, + "/enterprise/2.14/user/articles/basic-writing-and-formatting-syntax": null, + "/enterprise/2.14/user/articles/be-social": null, + "/enterprise/2.14/user/articles/caching-your-github-password-in-git": null, + "/enterprise/2.14/user/articles/changing-a-commit-message": null, + "/enterprise/2.14/user/articles/changing-a-persons-role-to-owner": null, + "/enterprise/2.14/user/articles/changing-a-remotes-url": null, + "/enterprise/2.14/user/articles/changing-access-permissions-for-wikis": null, + "/enterprise/2.14/user/articles/changing-author-info": null, + "/enterprise/2.14/user/articles/changing-project-board-visibility": null, + "/enterprise/2.14/user/articles/changing-team-visibility": null, + "/enterprise/2.14/user/articles/changing-the-base-branch-of-a-pull-request": null, + "/enterprise/2.14/user/articles/changing-your-github-username": null, + "/enterprise/2.14/user/articles/changing-your-primary-email-address": null, + "/enterprise/2.14/user/articles/checking-for-existing-gpg-keys": null, + "/enterprise/2.14/user/articles/checking-for-existing-ssh-keys": null, + "/enterprise/2.14/user/articles/checking-out-pull-requests-locally": null, + "/enterprise/2.14/user/articles/checking-your-commit-and-tag-signature-verification-status": null, + "/enterprise/2.14/user/articles/choosing-the-delivery-method-for-your-notifications": null, + "/enterprise/2.14/user/articles/classifying-your-repository-with-topics": null, + "/enterprise/2.14/user/articles/cloning-a-repository-from-github": null, + "/enterprise/2.14/user/articles/cloning-a-repository": null, + "/enterprise/2.14/user/articles/closing-a-project-board": null, + "/enterprise/2.14/user/articles/closing-a-pull-request": null, + "/enterprise/2.14/user/articles/closing-issues-using-keywords": null, + "/enterprise/2.14/user/articles/collaborating-on-repositories-with-code-quality-features-enabled": null, + "/enterprise/2.14/user/articles/collaborating-with-groups-in-organizations": null, + "/enterprise/2.14/user/articles/collaborating-with-your-team": null, + "/enterprise/2.14/user/articles/collaboration-with-git-large-file-storage": null, + "/enterprise/2.14/user/articles/commenting-on-a-pull-request": null, + "/enterprise/2.14/user/articles/commit-branch-and-tag-labels": null, + "/enterprise/2.14/user/articles/commit-exists-on-github-but-not-in-my-local-clone": null, + "/enterprise/2.14/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.14/user/articles/comparing-commits-across-time": null, + "/enterprise/2.14/user/articles/conditions-for-large-files": null, + "/enterprise/2.14/user/articles/configuring-a-publishing-source-for-github-pages": null, + "/enterprise/2.14/user/articles/configuring-a-remote-for-a-fork": null, + "/enterprise/2.14/user/articles/configuring-automation-for-project-boards": null, + "/enterprise/2.14/user/articles/configuring-commit-rebasing-for-pull-requests": null, + "/enterprise/2.14/user/articles/configuring-commit-squashing-for-pull-requests": null, + "/enterprise/2.14/user/articles/configuring-git-large-file-storage": null, + "/enterprise/2.14/user/articles/configuring-git-to-handle-line-endings": null, + "/enterprise/2.14/user/articles/configuring-jekyll-plugins": null, + "/enterprise/2.14/user/articles/configuring-jekyll": null, + "/enterprise/2.14/user/articles/configuring-protected-branches": null, + "/enterprise/2.14/user/articles/configuring-pull-request-merges": null, + "/enterprise/2.14/user/articles/configuring-two-factor-authentication-recovery-methods": null, + "/enterprise/2.14/user/articles/configuring-two-factor-authentication": null, + "/enterprise/2.14/user/articles/connecting-to-github-with-ssh": null, + "/enterprise/2.14/user/articles/connecting-with-third-party-applications": null, + "/enterprise/2.14/user/articles/converting-a-user-into-an-organization": null, + "/enterprise/2.14/user/articles/converting-an-organization-into-a-user": null, + "/enterprise/2.14/user/articles/converting-an-organization-member-to-an-outside-collaborator": null, + "/enterprise/2.14/user/articles/converting-an-outside-collaborator-to-an-organization-member": null, + "/enterprise/2.14/user/articles/converting-your-previous-admin-team-to-the-improved-organization-permissions": null, + "/enterprise/2.14/user/articles/converting-your-previous-owners-team-to-the-improved-organization-permissions": null, + "/enterprise/2.14/user/articles/create-a-repo": null, + "/enterprise/2.14/user/articles/creating-a-commit-with-multiple-authors": null, + "/enterprise/2.14/user/articles/creating-a-custom-404-page-for-your-github-pages-site": null, + "/enterprise/2.14/user/articles/creating-a-footer-or-sidebar-for-your-wiki": null, + "/enterprise/2.14/user/articles/creating-a-label": null, + "/enterprise/2.14/user/articles/creating-a-new-organization-from-scratch": null, + "/enterprise/2.14/user/articles/creating-a-new-repository": null, + "/enterprise/2.14/user/articles/creating-a-permanent-link-to-a-code-snippet": null, + "/enterprise/2.14/user/articles/creating-a-personal-access-token-for-the-command-line": null, + "/enterprise/2.14/user/articles/creating-a-project-board": null, + "/enterprise/2.14/user/articles/creating-a-pull-request-from-a-fork": null, + "/enterprise/2.14/user/articles/creating-a-pull-request-template-for-your-repository": null, + "/enterprise/2.14/user/articles/creating-a-pull-request": null, + "/enterprise/2.14/user/articles/creating-a-repository-on-github": null, + "/enterprise/2.14/user/articles/creating-a-saved-reply": null, + "/enterprise/2.14/user/articles/creating-a-strong-password": null, + "/enterprise/2.14/user/articles/creating-a-team-discussion": null, + "/enterprise/2.14/user/articles/creating-a-team": null, + "/enterprise/2.14/user/articles/creating-an-issue": null, + "/enterprise/2.14/user/articles/creating-an-issues-only-repository": null, + "/enterprise/2.14/user/articles/creating-and-deleting-branches-within-your-repository": null, + "/enterprise/2.14/user/articles/creating-and-editing-commits": null, + "/enterprise/2.14/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/creating-and-highlighting-code-blocks": null, + "/enterprise/2.14/user/articles/creating-gists": null, + "/enterprise/2.14/user/articles/creating-issue-templates-for-your-repository": null, + "/enterprise/2.14/user/articles/creating-new-files": null, + "/enterprise/2.14/user/articles/creating-pages-with-the-automatic-generator": null, + "/enterprise/2.14/user/articles/creating-project-pages-using-the-command-line": null, + "/enterprise/2.14/user/articles/creating-releases": null, + "/enterprise/2.14/user/articles/customizing-css-and-html-in-your-jekyll-theme": null, + "/enterprise/2.14/user/articles/customizing-how-changed-files-appear-on-github": null, + "/enterprise/2.14/user/articles/customizing-your-profile": null, + "/enterprise/2.14/user/articles/dealing-with-non-fast-forward-errors": null, + "/enterprise/2.14/user/articles/defining-the-mergeability-of-pull-requests": null, + "/enterprise/2.14/user/articles/deleting-a-label": null, + "/enterprise/2.14/user/articles/deleting-a-project-board": null, + "/enterprise/2.14/user/articles/deleting-a-repository": null, + "/enterprise/2.14/user/articles/deleting-a-saved-reply": null, + "/enterprise/2.14/user/articles/deleting-a-team": null, + "/enterprise/2.14/user/articles/deleting-an-organization-account": null, + "/enterprise/2.14/user/articles/deleting-and-restoring-branches-in-a-pull-request": null, + "/enterprise/2.14/user/articles/deleting-files": null, + "/enterprise/2.14/user/articles/deleting-your-user-account": null, + "/enterprise/2.14/user/articles/differences-between-commit-views": null, + "/enterprise/2.14/user/articles/disabling-issues": null, + "/enterprise/2.14/user/articles/disabling-project-boards-in-a-repository": null, + "/enterprise/2.14/user/articles/disabling-project-boards-in-your-organization": null, + "/enterprise/2.14/user/articles/disabling-team-discussions-for-your-organization": null, + "/enterprise/2.14/user/articles/disabling-two-factor-authentication-for-your-personal-account": null, + "/enterprise/2.14/user/articles/disabling-wikis": null, + "/enterprise/2.14/user/articles/dismissing-a-pull-request-review": null, + "/enterprise/2.14/user/articles/distributing-large-binaries": null, + "/enterprise/2.14/user/articles/documenting-your-project-with-wikis": null, + "/enterprise/2.14/user/articles/duplicating-a-repository": null, + "/enterprise/2.14/user/articles/editing-a-label": null, + "/enterprise/2.14/user/articles/editing-a-project-board": null, + "/enterprise/2.14/user/articles/editing-a-saved-reply": null, + "/enterprise/2.14/user/articles/editing-and-deleting-releases": null, + "/enterprise/2.14/user/articles/editing-and-sharing-content-with-gists": null, + "/enterprise/2.14/user/articles/editing-files-in-another-users-repository": null, + "/enterprise/2.14/user/articles/editing-files-in-your-repository": null, + "/enterprise/2.14/user/articles/editing-or-deleting-a-team-discussion": null, + "/enterprise/2.14/user/articles/editing-wiki-content": null, + "/enterprise/2.14/user/articles/emoji-on-github-pages": null, + "/enterprise/2.14/user/articles/enabling-anonymous-git-read-access-for-a-repository": null, + "/enterprise/2.14/user/articles/enabling-branch-restrictions": null, + "/enterprise/2.14/user/articles/enabling-required-commit-signing": null, + "/enterprise/2.14/user/articles/enabling-required-reviews-for-pull-requests": null, + "/enterprise/2.14/user/articles/enabling-required-status-checks": null, + "/enterprise/2.14/user/articles/error-agent-admitted-failure-to-sign": null, + "/enterprise/2.14/user/articles/error-bad-file-number": null, + "/enterprise/2.14/user/articles/error-key-already-in-use": null, + "/enterprise/2.14/user/articles/error-permission-denied-publickey": null, + "/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-other-user": null, + "/enterprise/2.14/user/articles/error-permission-to-userrepo-denied-to-userother-repo": null, + "/enterprise/2.14/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": null, + "/enterprise/2.14/user/articles/error-repository-not-found": null, + "/enterprise/2.14/user/articles/error-ssh-add-illegal-option----k": null, + "/enterprise/2.14/user/articles/error-were-doing-an-ssh-key-audit": null, + "/enterprise/2.14/user/articles/exploring-projects-on-github": null, + "/enterprise/2.14/user/articles/file-attachments-on-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/files-that-start-with-an-underscore-are-missing": null, + "/enterprise/2.14/user/articles/filtering-cards-on-a-project-board": null, + "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-assignees": null, + "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-labels": null, + "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests-by-milestone": null, + "/enterprise/2.14/user/articles/filtering-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/filtering-pull-requests-by-review-status": null, + "/enterprise/2.14/user/articles/finding-changed-methods-and-functions-in-a-pull-request": null, + "/enterprise/2.14/user/articles/finding-files-on-github": null, + "/enterprise/2.14/user/articles/finding-information-in-a-repository": null, + "/enterprise/2.14/user/articles/following-people": null, + "/enterprise/2.14/user/articles/fork-a-repo": null, + "/enterprise/2.14/user/articles/forking-and-cloning-gists": null, + "/enterprise/2.14/user/articles/further-reading-on-github-pages": null, + "/enterprise/2.14/user/articles/generating-a-new-gpg-key": null, + "/enterprise/2.14/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": null, + "/enterprise/2.14/user/articles/generic-jekyll-build-failures": null, + "/enterprise/2.14/user/articles/getting-changes-from-a-remote-repository": null, + "/enterprise/2.14/user/articles/getting-permanent-links-to-files": null, + "/enterprise/2.14/user/articles/getting-started-with-git-and-github": null, + "/enterprise/2.14/user/articles/getting-started-with-notifications": null, + "/enterprise/2.14/user/articles/getting-started-with-searching-on-github": null, + "/enterprise/2.14/user/articles/getting-started-with-the-api": null, + "/enterprise/2.14/user/articles/getting-started-with-writing-and-formatting-on-github": null, + "/enterprise/2.14/user/articles/getting-the-download-count-for-your-releases": null, + "/enterprise/2.14/user/articles/git-and-github-learning-resources": null, + "/enterprise/2.14/user/articles/git-automation-with-oauth-tokens": null, + "/enterprise/2.14/user/articles/git-cheatsheet": null, + "/enterprise/2.14/user/articles/git-workflows": null, + "/enterprise/2.14/user/articles/github-flow": null, + "/enterprise/2.14/user/articles/github-glossary": null, + "/enterprise/2.14/user/articles/giving-team-maintainer-permissions-to-an-organization-member": null, + "/enterprise/2.14/user/articles/https-cloning-errors": null, + "/enterprise/2.14/user/articles/ignoring-files": null, + "/enterprise/2.14/user/articles/importing-a-git-repository-using-the-command-line": null, + "/enterprise/2.14/user/articles/importing-source-code-to-github": null, + "/enterprise/2.14/user/articles/incorporating-changes-from-a-pull-request": null, + "/enterprise/2.14/user/articles/initializing-an-empty-repository-with-a-readme": null, + "/enterprise/2.14/user/articles/installing-git-large-file-storage": null, + "/enterprise/2.14/user/articles/integrating-jira-with-your-organization-project-board": null, + "/enterprise/2.14/user/articles/integrating-jira-with-your-personal-projects": null, + "/enterprise/2.14/user/articles/inviting-collaborators-to-a-personal-repository": null, + "/enterprise/2.14/user/articles/keeping-your-account-and-data-secure": null, + "/enterprise/2.14/user/articles/keeping-your-organization-secure": null, + "/enterprise/2.14/user/articles/keyboard-shortcuts": null, + "/enterprise/2.14/user/articles/labeling-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/learning-about-git": null, + "/enterprise/2.14/user/articles/learning-about-github": null, + "/enterprise/2.14/user/articles/licensing-a-repository": null, + "/enterprise/2.14/user/articles/limits-for-viewing-content-and-diffs-in-a-repository": null, + "/enterprise/2.14/user/articles/linking-to-releases": null, + "/enterprise/2.14/user/articles/listing-the-forks-of-a-repository": null, + "/enterprise/2.14/user/articles/listing-the-repositories-youre-watching": null, + "/enterprise/2.14/user/articles/locking-conversations": null, + "/enterprise/2.14/user/articles/managing-access-to-a-project-board-for-organization-members": null, + "/enterprise/2.14/user/articles/managing-access-to-your-organizations-project-boards": null, + "/enterprise/2.14/user/articles/managing-access-to-your-organizations-repositories": null, + "/enterprise/2.14/user/articles/managing-access-to-your-personal-repositories": null, + "/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-project-board": null, + "/enterprise/2.14/user/articles/managing-an-individuals-access-to-an-organization-repository": null, + "/enterprise/2.14/user/articles/managing-branches-in-your-repository": null, + "/enterprise/2.14/user/articles/managing-commit-signature-verification": null, + "/enterprise/2.14/user/articles/managing-contribution-graphs-on-your-profile": null, + "/enterprise/2.14/user/articles/managing-disruptive-comments": null, + "/enterprise/2.14/user/articles/managing-email-preferences": null, + "/enterprise/2.14/user/articles/managing-files-on-github": null, + "/enterprise/2.14/user/articles/managing-files-using-the-command-line": null, + "/enterprise/2.14/user/articles/managing-membership-in-your-organization": null, + "/enterprise/2.14/user/articles/managing-organization-settings": null, + "/enterprise/2.14/user/articles/managing-peoples-access-to-your-organization-with-roles": null, + "/enterprise/2.14/user/articles/managing-project-boards": null, + "/enterprise/2.14/user/articles/managing-releases-in-a-repository": null, + "/enterprise/2.14/user/articles/managing-remote-repositories": null, + "/enterprise/2.14/user/articles/managing-repository-settings": null, + "/enterprise/2.14/user/articles/managing-team-access-to-an-organization-project-board": null, + "/enterprise/2.14/user/articles/managing-team-access-to-an-organization-repository": null, + "/enterprise/2.14/user/articles/managing-user-account-settings": null, + "/enterprise/2.14/user/articles/managing-your-membership-in-organizations": null, + "/enterprise/2.14/user/articles/managing-your-notifications": null, + "/enterprise/2.14/user/articles/managing-your-work-with-issues": null, + "/enterprise/2.14/user/articles/manually-creating-a-single-issue-template-for-your-repository": null, + "/enterprise/2.14/user/articles/mapping-geojson-files-on-github": null, + "/enterprise/2.14/user/articles/marking-notifications-as-read": null, + "/enterprise/2.14/user/articles/mentions-on-github-pages": null, + "/enterprise/2.14/user/articles/merging-a-pull-request": null, + "/enterprise/2.14/user/articles/merging-an-upstream-repository-into-your-fork": null, + "/enterprise/2.14/user/articles/migrating-your-organization-to-improved-organization-permissions": null, + "/enterprise/2.14/user/articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions": null, + "/enterprise/2.14/user/articles/mime-types-on-github-pages": null, + "/enterprise/2.14/user/articles/moderating-comments-and-conversations": null, + "/enterprise/2.14/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage": null, + "/enterprise/2.14/user/articles/moving-a-file-to-a-new-location-using-the-command-line": null, + "/enterprise/2.14/user/articles/moving-a-file-to-a-new-location": null, + "/enterprise/2.14/user/articles/moving-a-team-in-your-organizations-hierarchy": null, + "/enterprise/2.14/user/articles/opening-an-issue-from-code": null, + "/enterprise/2.14/user/articles/organizing-information-with-tables": null, + "/enterprise/2.14/user/articles/organizing-members-into-teams": null, + "/enterprise/2.14/user/articles/page-build-failed-config-file-error": null, + "/enterprise/2.14/user/articles/page-build-failed-date-is-not-a-valid-datetime": null, + "/enterprise/2.14/user/articles/page-build-failed-file-does-not-exist-in-includes-directory": null, + "/enterprise/2.14/user/articles/page-build-failed-file-is-a-symlink": null, + "/enterprise/2.14/user/articles/page-build-failed-file-is-not-properly-utf-8-encoded": null, + "/enterprise/2.14/user/articles/page-build-failed-invalid-highlighter-language": null, + "/enterprise/2.14/user/articles/page-build-failed-invalid-post-date": null, + "/enterprise/2.14/user/articles/page-build-failed-invalid-sass-or-scss": null, + "/enterprise/2.14/user/articles/page-build-failed-invalid-submodule": null, + "/enterprise/2.14/user/articles/page-build-failed-invalid-yaml-in-data-file": null, + "/enterprise/2.14/user/articles/page-build-failed-markdown-errors": null, + "/enterprise/2.14/user/articles/page-build-failed-missing-docs-folder": null, + "/enterprise/2.14/user/articles/page-build-failed-missing-submodule": null, + "/enterprise/2.14/user/articles/page-build-failed-relative-permalinks-configured": null, + "/enterprise/2.14/user/articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository": null, + "/enterprise/2.14/user/articles/page-build-failed-syntax-error-in-for-loop": null, + "/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-closed": null, + "/enterprise/2.14/user/articles/page-build-failed-tag-not-properly-terminated": null, + "/enterprise/2.14/user/articles/page-build-failed-unknown-tag-error": null, + "/enterprise/2.14/user/articles/permission-levels-for-a-user-account-repository": null, + "/enterprise/2.14/user/articles/permission-levels-for-an-organization": null, + "/enterprise/2.14/user/articles/personalizing-your-profile": null, + "/enterprise/2.14/user/articles/pinning-a-team-discussion": null, + "/enterprise/2.14/user/articles/pinning-items-to-your-profile": null, + "/enterprise/2.14/user/articles/preparing-to-require-two-factor-authentication-in-your-organization": null, + "/enterprise/2.14/user/articles/preventing-unauthorized-access": null, + "/enterprise/2.14/user/articles/project-board-permissions-for-an-organization": null, + "/enterprise/2.14/user/articles/proposing-changes-to-your-work-with-pull-requests": null, + "/enterprise/2.14/user/articles/publicizing-or-hiding-organization-membership": null, + "/enterprise/2.14/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": null, + "/enterprise/2.14/user/articles/pushing-commits-to-a-remote-repository": null, + "/enterprise/2.14/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials": null, + "/enterprise/2.14/user/articles/recovering-your-ssh-key-passphrase": null, + "/enterprise/2.14/user/articles/redirects-on-github-pages": null, + "/enterprise/2.14/user/articles/reinstating-a-former-member-of-your-organization": null, + "/enterprise/2.14/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": null, + "/enterprise/2.14/user/articles/remembering-your-github-username-or-email": null, + "/enterprise/2.14/user/articles/removing-a-collaborator-from-a-personal-repository": null, + "/enterprise/2.14/user/articles/removing-a-member-from-your-organization": null, + "/enterprise/2.14/user/articles/removing-a-remote": null, + "/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-project-board": null, + "/enterprise/2.14/user/articles/removing-an-outside-collaborator-from-an-organization-repository": null, + "/enterprise/2.14/user/articles/removing-files-from-a-repositorys-history": null, + "/enterprise/2.14/user/articles/removing-files-from-git-large-file-storage": null, + "/enterprise/2.14/user/articles/removing-organization-members-from-a-team": null, + "/enterprise/2.14/user/articles/removing-sensitive-data-from-a-repository": null, + "/enterprise/2.14/user/articles/removing-yourself-from-a-collaborators-repository": null, + "/enterprise/2.14/user/articles/removing-yourself-from-an-organization": null, + "/enterprise/2.14/user/articles/renaming-a-file-using-the-command-line": null, + "/enterprise/2.14/user/articles/renaming-a-file": null, + "/enterprise/2.14/user/articles/renaming-a-remote": null, + "/enterprise/2.14/user/articles/renaming-a-repository": null, + "/enterprise/2.14/user/articles/renaming-a-team": null, + "/enterprise/2.14/user/articles/renaming-an-organization": null, + "/enterprise/2.14/user/articles/rendering-and-diffing-images": null, + "/enterprise/2.14/user/articles/rendering-csv-and-tsv-data": null, + "/enterprise/2.14/user/articles/rendering-differences-in-prose-documents": null, + "/enterprise/2.14/user/articles/rendering-pdf-documents": null, + "/enterprise/2.14/user/articles/reopening-a-closed-project-board": null, + "/enterprise/2.14/user/articles/repository-metadata-on-github-pages": null, + "/enterprise/2.14/user/articles/repository-permission-levels-for-an-organization": null, + "/enterprise/2.14/user/articles/requesting-a-pull-request-review": null, + "/enterprise/2.14/user/articles/requesting-a-trial-of-github-enterprise": null, + "/enterprise/2.14/user/articles/requesting-to-add-a-child-team": null, + "/enterprise/2.14/user/articles/requesting-to-add-or-change-a-parent-team": null, + "/enterprise/2.14/user/articles/requiring-two-factor-authentication-in-your-organization": null, + "/enterprise/2.14/user/articles/resolving-a-merge-conflict-on-github": null, + "/enterprise/2.14/user/articles/resolving-a-merge-conflict-using-the-command-line": null, + "/enterprise/2.14/user/articles/resolving-git-large-file-storage-upload-failures": null, + "/enterprise/2.14/user/articles/resolving-merge-conflicts-after-a-git-rebase": null, + "/enterprise/2.14/user/articles/restricting-repository-creation-in-your-organization": null, + "/enterprise/2.14/user/articles/restricting-repository-visibility-changes-in-your-organization": null, + "/enterprise/2.14/user/articles/reverting-a-pull-request": null, + "/enterprise/2.14/user/articles/reviewing-changes-in-pull-requests": null, + "/enterprise/2.14/user/articles/reviewing-proposed-changes-in-a-pull-request": null, + "/enterprise/2.14/user/articles/reviewing-the-audit-log-for-your-organization": null, + "/enterprise/2.14/user/articles/reviewing-your-authorized-applications-oauth": null, + "/enterprise/2.14/user/articles/reviewing-your-authorized-integrations": null, + "/enterprise/2.14/user/articles/reviewing-your-deploy-keys": null, + "/enterprise/2.14/user/articles/reviewing-your-organizations-installed-integrations": null, + "/enterprise/2.14/user/articles/reviewing-your-security-log": null, + "/enterprise/2.14/user/articles/reviewing-your-ssh-keys": null, + "/enterprise/2.14/user/articles/saving-repositories-with-stars": null, + "/enterprise/2.14/user/articles/searching-code": null, + "/enterprise/2.14/user/articles/searching-commits": null, + "/enterprise/2.14/user/articles/searching-for-repositories": null, + "/enterprise/2.14/user/articles/searching-in-forks": null, + "/enterprise/2.14/user/articles/searching-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/searching-on-github": null, + "/enterprise/2.14/user/articles/searching-topics": null, + "/enterprise/2.14/user/articles/searching-users": null, + "/enterprise/2.14/user/articles/searching-wikis": null, + "/enterprise/2.14/user/articles/securing-your-account-with-two-factor-authentication-2fa": null, + "/enterprise/2.14/user/articles/set-up-git": null, + "/enterprise/2.14/user/articles/setting-a-backup-email-address": null, + "/enterprise/2.14/user/articles/setting-guidelines-for-repository-contributors": null, + "/enterprise/2.14/user/articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization": null, + "/enterprise/2.14/user/articles/setting-repository-visibility": null, + "/enterprise/2.14/user/articles/setting-the-default-branch": null, + "/enterprise/2.14/user/articles/setting-up-your-github-pages-site-locally-with-jekyll": null, + "/enterprise/2.14/user/articles/setting-up-your-project-for-healthy-contributions": null, + "/enterprise/2.14/user/articles/setting-your-commit-email-address": null, + "/enterprise/2.14/user/articles/setting-your-teams-profile-picture": null, + "/enterprise/2.14/user/articles/setting-your-username-in-git": null, + "/enterprise/2.14/user/articles/sharing-filters": null, + "/enterprise/2.14/user/articles/signing-commits": null, + "/enterprise/2.14/user/articles/signing-tags": null, + "/enterprise/2.14/user/articles/signing-up-for-github": null, + "/enterprise/2.14/user/articles/sitemaps-for-github-pages": null, + "/enterprise/2.14/user/articles/sorting-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/sorting-search-results": null, + "/enterprise/2.14/user/articles/source-code-migration-tools": null, + "/enterprise/2.14/user/articles/splitting-a-subfolder-out-into-a-new-repository": null, + "/enterprise/2.14/user/articles/subscribing-to-and-unsubscribing-from-notifications": null, + "/enterprise/2.14/user/articles/subversion-properties-supported-by-github": null, + "/enterprise/2.14/user/articles/sudo-mode": null, + "/enterprise/2.14/user/articles/support-for-subversion-clients": null, + "/enterprise/2.14/user/articles/supported-browsers": null, + "/enterprise/2.14/user/articles/syncing-a-fork": null, + "/enterprise/2.14/user/articles/telling-git-about-your-signing-key": null, + "/enterprise/2.14/user/articles/testing-your-ssh-connection": null, + "/enterprise/2.14/user/articles/tracking-changes-in-a-comment": null, + "/enterprise/2.14/user/articles/tracking-changes-in-a-file": null, + "/enterprise/2.14/user/articles/tracking-progress-on-your-project-board": null, + "/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-milestones": null, + "/enterprise/2.14/user/articles/tracking-the-progress-of-your-work-with-project-boards": null, + "/enterprise/2.14/user/articles/transferring-a-repository": null, + "/enterprise/2.14/user/articles/transferring-organization-ownership": null, + "/enterprise/2.14/user/articles/troubleshooting-commit-signature-verification": null, + "/enterprise/2.14/user/articles/troubleshooting-commits-on-your-timeline": null, + "/enterprise/2.14/user/articles/troubleshooting-commits": null, + "/enterprise/2.14/user/articles/troubleshooting-github-pages-builds": null, + "/enterprise/2.14/user/articles/troubleshooting-search-queries": null, + "/enterprise/2.14/user/articles/troubleshooting-ssh": null, + "/enterprise/2.14/user/articles/types-of-github-accounts": null, + "/enterprise/2.14/user/articles/types-of-required-status-checks": null, + "/enterprise/2.14/user/articles/understanding-connections-between-repositories": null, + "/enterprise/2.14/user/articles/understanding-the-search-syntax": null, + "/enterprise/2.14/user/articles/unpublishing-a-project-pages-site": null, + "/enterprise/2.14/user/articles/unpublishing-a-user-pages-site": null, + "/enterprise/2.14/user/articles/updating-an-expired-gpg-key": null, + "/enterprise/2.14/user/articles/updating-credentials-from-the-osx-keychain": null, + "/enterprise/2.14/user/articles/updating-your-github-access-credentials": null, + "/enterprise/2.14/user/articles/updating-your-markdown-processor-to-kramdown": null, + "/enterprise/2.14/user/articles/user-organization-and-project-pages": null, + "/enterprise/2.14/user/articles/using-a-static-site-generator-other-than-jekyll": null, + "/enterprise/2.14/user/articles/using-a-verified-email-address-in-your-gpg-key": null, + "/enterprise/2.14/user/articles/using-advanced-git-commands": null, + "/enterprise/2.14/user/articles/using-common-git-commands": null, + "/enterprise/2.14/user/articles/using-git-rebase-on-the-command-line": null, + "/enterprise/2.14/user/articles/using-github": null, + "/enterprise/2.14/user/articles/using-jekyll-as-a-static-site-generator-with-github-pages": null, + "/enterprise/2.14/user/articles/using-saved-replies": null, + "/enterprise/2.14/user/articles/using-search-to-filter-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/using-syntax-highlighting-on-github-pages": null, + "/enterprise/2.14/user/articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository": null, + "/enterprise/2.14/user/articles/versioning-large-files": null, + "/enterprise/2.14/user/articles/viewing-a-projects-contributors": null, + "/enterprise/2.14/user/articles/viewing-a-pull-request-review": null, + "/enterprise/2.14/user/articles/viewing-a-repositorys-network": null, + "/enterprise/2.14/user/articles/viewing-a-summary-of-repository-activity": null, + "/enterprise/2.14/user/articles/viewing-a-wikis-history-of-changes": null, + "/enterprise/2.14/user/articles/viewing-all-of-your-issues-and-pull-requests": null, + "/enterprise/2.14/user/articles/viewing-and-comparing-commits": null, + "/enterprise/2.14/user/articles/viewing-branches-in-your-repository": null, + "/enterprise/2.14/user/articles/viewing-contributions-on-your-profile": null, + "/enterprise/2.14/user/articles/viewing-jekyll-build-error-messages": null, + "/enterprise/2.14/user/articles/viewing-peoples-roles-in-an-organization": null, + "/enterprise/2.14/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": null, + "/enterprise/2.14/user/articles/viewing-your-milestones-progress": null, + "/enterprise/2.14/user/articles/viewing-your-repositorys-tags": null, + "/enterprise/2.14/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository": null, + "/enterprise/2.14/user/articles/visualizing-commits-in-a-repository": null, + "/enterprise/2.14/user/articles/watching-and-unwatching-repositories": null, + "/enterprise/2.14/user/articles/watching-and-unwatching-team-discussions": null, + "/enterprise/2.14/user/articles/what-are-the-differences-between-subversion-and-git": null, + "/enterprise/2.14/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": null, + "/enterprise/2.14/user/articles/what-is-github-pages": null, + "/enterprise/2.14/user/articles/which-remote-url-should-i-use": null, + "/enterprise/2.14/user/articles/why-are-my-commits-in-the-wrong-order": null, + "/enterprise/2.14/user/articles/why-are-my-commits-linked-to-the-wrong-user": null, + "/enterprise/2.14/user/articles/why-are-my-contributions-not-showing-up-on-my-profile": null, + "/enterprise/2.14/user/articles/why-is-git-always-asking-for-my-password": null, + "/enterprise/2.14/user/articles/working-with-advanced-formatting": null, + "/enterprise/2.14/user/articles/working-with-forks": null, + "/enterprise/2.14/user/articles/working-with-jupyter-notebook-files-on-github": null, + "/enterprise/2.14/user/articles/working-with-large-files": null, + "/enterprise/2.14/user/articles/working-with-non-code-files": null, + "/enterprise/2.14/user/articles/working-with-pre-receive-hooks": null, + "/enterprise/2.14/user/articles/working-with-saved-replies": null, + "/enterprise/2.14/user/articles/working-with-ssh-key-passphrases": null, + "/enterprise/2.14/user/articles/working-with-subversion-on-github": null, + "/enterprise/2.14/user/categories/administering-a-repository": null, + "/enterprise/2.14/user/categories/authenticating-to-github": null, + "/enterprise/2.14/user/categories/building-a-strong-community": null, + "/enterprise/2.14/user/categories/collaborating-with-issues-and-pull-requests": null, + "/enterprise/2.14/user/categories/committing-changes-to-your-project": null, + "/enterprise/2.14/user/categories/creating-cloning-and-archiving-repositories": null, + "/enterprise/2.14/user/categories/customizing-github-pages": null, + "/enterprise/2.14/user/categories/extending-github": null, + "/enterprise/2.14/user/categories/getting-started-with-github": null, + "/enterprise/2.14/user/categories/github-pages-basics": null, + "/enterprise/2.14/user/categories/importing-your-projects-to-github": null, + "/enterprise/2.14/user/categories/managing-files-in-a-repository": null, + "/enterprise/2.14/user/categories/managing-large-files": null, + "/enterprise/2.14/user/categories/managing-your-work-on-github": null, + "/enterprise/2.14/user/categories/receiving-notifications-about-activity-on-github": null, + "/enterprise/2.14/user/categories/searching-for-information-on-github": null, + "/enterprise/2.14/user/categories/setting-up-and-managing-organizations-and-teams": null, + "/enterprise/2.14/user/categories/setting-up-and-managing-your-github-profile": null, + "/enterprise/2.14/user/categories/setting-up-and-managing-your-github-user-account": null, + "/enterprise/2.14/user/categories/using-git": null, + "/enterprise/2.14/user/categories/visualizing-repository-data-with-graphs": null, + "/enterprise/2.14/user/categories/writing-on-github": null, + "/enterprise/2.14/user": null, + "/enterprise/2.15/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", + "/enterprise/2.15/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", + "/enterprise/2.15/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", + "/enterprise/2.15/admin/guides/articles/using-github-task-runner": "/enterprise/2.15/admin/articles/using-github-task-runner", + "/enterprise/2.15/admin/guides/clustering/about-cluster-nodes": "/enterprise/2.15/admin/clustering/about-cluster-nodes", + "/enterprise/2.15/admin/guides/clustering/clustering-overview": "/enterprise/2.15/admin/clustering/clustering-overview", + "/enterprise/2.15/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha", + "/enterprise/2.15/admin/guides/clustering/evacuating-a-cluster-node": "/enterprise/2.15/admin/clustering/evacuating-a-cluster-node", + "/enterprise/2.15/admin/guides/clustering": "/enterprise/2.15/admin/clustering", + "/enterprise/2.15/admin/guides/clustering/initializing-the-cluster": "/enterprise/2.15/admin/clustering/initializing-the-cluster", + "/enterprise/2.15/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster", + "/enterprise/2.15/admin/guides/clustering/monitoring-cluster-nodes": "/enterprise/2.15/admin/clustering/monitoring-cluster-nodes", + "/enterprise/2.15/admin/guides/clustering/network-configuration": "/enterprise/2.15/admin/clustering/network-configuration", + "/enterprise/2.15/admin/guides/clustering/replacing-a-cluster-node": "/enterprise/2.15/admin/clustering/replacing-a-cluster-node", + "/enterprise/2.15/admin/guides/clustering/setting-up-the-cluster-instances": "/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances", + "/enterprise/2.15/admin/guides/clustering/upgrading-a-cluster": "/enterprise/2.15/admin/clustering/upgrading-a-cluster", + "/enterprise/2.15/admin/guides/developer-workflow/about-pre-receive-hooks": "/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks", + "/enterprise/2.15/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks", + "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance", + "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository", + "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", + "/enterprise/2.15/admin/guides/developer-workflow/blocking-force-pushes": "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes", + "/enterprise/2.15/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", + "/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins", + "/enterprise/2.15/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci", + "/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment", + "/enterprise/2.15/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script", + "/enterprise/2.15/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations", + "/enterprise/2.15/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions", + "/enterprise/2.15/admin/guides/developer-workflow": "/enterprise/2.15/admin/developer-workflow", + "/enterprise/2.15/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", + "/enterprise/2.15/admin/guides/developer-workflow/managing-projects-using-jira": "/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira", + "/enterprise/2.15/admin/guides/developer-workflow/troubleshooting-service-hooks": "/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks", + "/enterprise/2.15/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", + "/enterprise/2.15/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration", + "/enterprise/2.15/admin/guides/enterprise-support/about-github-enterprise-support": "/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support", + "/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", + "/enterprise/2.15/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise", + "/enterprise/2.15/admin/guides/enterprise-support": "/enterprise/2.15/admin/enterprise-support", + "/enterprise/2.15/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket", + "/enterprise/2.15/admin/guides/enterprise-support/providing-data-to-github-support": "/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support", + "/enterprise/2.15/admin/guides/enterprise-support/reaching-github-support": "/enterprise/2.15/admin/enterprise-support/reaching-github-support", + "/enterprise/2.15/admin/guides/enterprise-support/receiving-help-from-github-support": "/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support", + "/enterprise/2.15/admin/guides/enterprise-support/submitting-a-ticket": "/enterprise/2.15/admin/enterprise-support/submitting-a-ticket", + "/enterprise/2.15/admin/guides": "/enterprise/2.15/admin", + "/enterprise/2.15/admin/guides/installation/about-geo-replication": "/enterprise/2.15/admin/installation/about-geo-replication", + "/enterprise/2.15/admin/guides/installation/about-high-availability-configuration": "/enterprise/2.15/admin/installation/about-high-availability-configuration", + "/enterprise/2.15/admin/guides/installation/about-the-github-enterprise-server-api": "/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api", + "/enterprise/2.15/admin/guides/installation/accessing-the-administrative-shell-ssh": "/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh", + "/enterprise/2.15/admin/guides/installation/accessing-the-management-console": "/enterprise/2.15/admin/installation/accessing-the-management-console", + "/enterprise/2.15/admin/guides/installation/accessing-the-monitor-dashboard": "/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard", + "/enterprise/2.15/admin/guides/installation/activity-dashboard": "/enterprise/2.15/admin/installation/activity-dashboard", + "/enterprise/2.15/admin/guides/installation/audit-logging": "/enterprise/2.15/admin/installation/audit-logging", + "/enterprise/2.15/admin/guides/installation/audited-actions": "/enterprise/2.15/admin/installation/audited-actions", + "/enterprise/2.15/admin/guides/installation/command-line-utilities": "/enterprise/2.15/admin/installation/command-line-utilities", + "/enterprise/2.15/admin/guides/installation/configuring-a-hostname": "/enterprise/2.15/admin/installation/configuring-a-hostname", + "/enterprise/2.15/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server", + "/enterprise/2.15/admin/guides/installation/configuring-backups-on-your-appliance": "/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance", + "/enterprise/2.15/admin/guides/installation/configuring-built-in-firewall-rules": "/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules", + "/enterprise/2.15/admin/guides/installation/configuring-collectd": "/enterprise/2.15/admin/installation/configuring-collectd", + "/enterprise/2.15/admin/guides/installation/configuring-dns-nameservers": "/enterprise/2.15/admin/installation/configuring-dns-nameservers", + "/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", + "/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", + "/enterprise/2.15/admin/guides/installation/configuring-git-large-file-storage": "/enterprise/2.15/admin/installation/configuring-git-large-file-storage", + "/enterprise/2.15/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability", + "/enterprise/2.15/admin/guides/installation/configuring-github-pages-on-your-appliance": "/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance", + "/enterprise/2.15/admin/guides/installation/configuring-rate-limits": "/enterprise/2.15/admin/installation/configuring-rate-limits", + "/enterprise/2.15/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", + "/enterprise/2.15/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance", + "/enterprise/2.15/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", + "/enterprise/2.15/admin/guides/installation/configuring-time-synchronization": "/enterprise/2.15/admin/installation/configuring-time-synchronization", + "/enterprise/2.15/admin/guides/installation/configuring-tls": "/enterprise/2.15/admin/installation/configuring-tls", + "/enterprise/2.15/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings", + "/enterprise/2.15/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", + "/enterprise/2.15/admin/guides/installation/creating-a-high-availability-replica": "/enterprise/2.15/admin/installation/creating-a-high-availability-replica", + "/enterprise/2.15/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", + "/enterprise/2.15/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", + "/enterprise/2.15/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode", + "/enterprise/2.15/admin/guides/installation/enabling-automatic-update-checks": "/enterprise/2.15/admin/installation/enabling-automatic-update-checks", + "/enterprise/2.15/admin/guides/installation/enabling-private-mode": "/enterprise/2.15/admin/installation/enabling-private-mode", + "/enterprise/2.15/admin/guides/installation/enabling-subdomain-isolation": "/enterprise/2.15/admin/installation/enabling-subdomain-isolation", + "/enterprise/2.15/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", + "/enterprise/2.15/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", + "/enterprise/2.15/admin/guides/installation/increasing-cpu-or-memory-resources": "/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources", + "/enterprise/2.15/admin/guides/installation/increasing-storage-capacity": "/enterprise/2.15/admin/installation/increasing-storage-capacity", + "/enterprise/2.15/admin/guides/installation": "/enterprise/2.15/admin/installation", + "/enterprise/2.15/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-aws": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-azure": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware", + "/enterprise/2.15/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver", + "/enterprise/2.15/admin/guides/installation/log-forwarding": "/enterprise/2.15/admin/installation/log-forwarding", + "/enterprise/2.15/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", + "/enterprise/2.15/admin/guides/installation/managing-your-github-enterprise-server-license": "/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license", + "/enterprise/2.15/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", + "/enterprise/2.15/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123", + "/enterprise/2.15/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server", + "/enterprise/2.15/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", + "/enterprise/2.15/admin/guides/installation/monitoring-using-snmp": "/enterprise/2.15/admin/installation/monitoring-using-snmp", + "/enterprise/2.15/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance", + "/enterprise/2.15/admin/guides/installation/network-ports": "/enterprise/2.15/admin/installation/network-ports", + "/enterprise/2.15/admin/guides/installation/recommended-alert-thresholds": "/enterprise/2.15/admin/installation/recommended-alert-thresholds", + "/enterprise/2.15/admin/guides/installation/recovering-a-high-availability-configuration": "/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration", + "/enterprise/2.15/admin/guides/installation/removing-a-high-availability-replica": "/enterprise/2.15/admin/installation/removing-a-high-availability-replica", + "/enterprise/2.15/admin/guides/installation/searching-the-audit-log": "/enterprise/2.15/admin/installation/searching-the-audit-log", + "/enterprise/2.15/admin/guides/installation/setting-git-push-limits": "/enterprise/2.15/admin/installation/setting-git-push-limits", + "/enterprise/2.15/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance", + "/enterprise/2.15/admin/guides/installation/setting-up-a-staging-instance": "/enterprise/2.15/admin/installation/setting-up-a-staging-instance", + "/enterprise/2.15/admin/guides/installation/setting-up-external-monitoring": "/enterprise/2.15/admin/installation/setting-up-external-monitoring", + "/enterprise/2.15/admin/guides/installation/site-admin-dashboard": "/enterprise/2.15/admin/installation/site-admin-dashboard", + "/enterprise/2.15/admin/guides/installation/system-overview": "/enterprise/2.15/admin/installation/system-overview", + "/enterprise/2.15/admin/guides/installation/troubleshooting-ssl-errors": "/enterprise/2.15/admin/installation/troubleshooting-ssl-errors", + "/enterprise/2.15/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources", + "/enterprise/2.15/admin/guides/installation/upgrade-requirements": "/enterprise/2.15/admin/installation/upgrade-requirements", + "/enterprise/2.15/admin/guides/installation/upgrading-github-enterprise-server": "/enterprise/2.15/admin/installation/upgrading-github-enterprise-server", + "/enterprise/2.15/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer", + "/enterprise/2.15/admin/guides/installation/validating-your-domain-settings": "/enterprise/2.15/admin/installation/validating-your-domain-settings", + "/enterprise/2.15/admin/guides/installation/viewing-push-logs": "/enterprise/2.15/admin/installation/viewing-push-logs", + "/enterprise/2.15/admin/guides/migrations/about-migrations": "/enterprise/2.15/admin/migrations/about-migrations", + "/enterprise/2.15/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server", + "/enterprise/2.15/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server", + "/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server", + "/enterprise/2.15/admin/guides/migrations/exporting-migration-data-from-githubcom": "/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom", + "/enterprise/2.15/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories", + "/enterprise/2.15/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories", + "/enterprise/2.15/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts", + "/enterprise/2.15/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems", + "/enterprise/2.15/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server", + "/enterprise/2.15/admin/guides/migrations": "/enterprise/2.15/admin/migrations", + "/enterprise/2.15/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance", + "/enterprise/2.15/admin/guides/migrations/preparing-the-githubcom-source-organization": "/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization", + "/enterprise/2.15/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", + "/enterprise/2.15/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", + "/enterprise/2.15/admin/guides/migrations/reviewing-migration-conflicts": "/enterprise/2.15/admin/migrations/reviewing-migration-conflicts", + "/enterprise/2.15/admin/guides/migrations/reviewing-migration-data": "/enterprise/2.15/admin/migrations/reviewing-migration-data", + "/enterprise/2.15/admin/guides/user-management/about-global-webhooks": "/enterprise/2.15/admin/user-management/about-global-webhooks", + "/enterprise/2.15/admin/guides/user-management/adding-people-to-teams": "/enterprise/2.15/admin/user-management/adding-people-to-teams", + "/enterprise/2.15/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", + "/enterprise/2.15/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", + "/enterprise/2.15/admin/guides/user-management/archiving-and-unarchiving-repositories": "/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories", + "/enterprise/2.15/admin/guides/user-management/auditing-ssh-keys": "/enterprise/2.15/admin/user-management/auditing-ssh-keys", + "/enterprise/2.15/admin/guides/user-management/auditing-users-across-your-instance": "/enterprise/2.15/admin/user-management/auditing-users-across-your-instance", + "/enterprise/2.15/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", + "/enterprise/2.15/admin/guides/user-management/basic-account-settings": "/enterprise/2.15/admin/user-management/basic-account-settings", + "/enterprise/2.15/admin/guides/user-management/best-practices-for-user-security": "/enterprise/2.15/admin/user-management/best-practices-for-user-security", + "/enterprise/2.15/admin/guides/user-management/changing-authentication-methods": "/enterprise/2.15/admin/user-management/changing-authentication-methods", + "/enterprise/2.15/admin/guides/user-management/configuring-email-for-notifications": "/enterprise/2.15/admin/user-management/configuring-email-for-notifications", + "/enterprise/2.15/admin/guides/user-management/configuring-visibility-for-organization-membership": "/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership", + "/enterprise/2.15/admin/guides/user-management/creating-organizations": "/enterprise/2.15/admin/user-management/creating-organizations", + "/enterprise/2.15/admin/guides/user-management/creating-teams": "/enterprise/2.15/admin/user-management/creating-teams", + "/enterprise/2.15/admin/guides/user-management/customizing-user-messages-on-your-instance": "/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance", + "/enterprise/2.15/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups", + "/enterprise/2.15/admin/guides/user-management": "/enterprise/2.15/admin/user-management", + "/enterprise/2.15/admin/guides/user-management/managing-dormant-users": "/enterprise/2.15/admin/user-management/managing-dormant-users", + "/enterprise/2.15/admin/guides/user-management/managing-global-webhooks": "/enterprise/2.15/admin/user-management/managing-global-webhooks", + "/enterprise/2.15/admin/guides/user-management/organizations-and-teams": "/enterprise/2.15/admin/user-management/organizations-and-teams", + "/enterprise/2.15/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", + "/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", + "/enterprise/2.15/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", + "/enterprise/2.15/admin/guides/user-management/preventing-users-from-creating-organizations": "/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations", + "/enterprise/2.15/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories", + "/enterprise/2.15/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator", + "/enterprise/2.15/admin/guides/user-management/rebuilding-contributions-data": "/enterprise/2.15/admin/user-management/rebuilding-contributions-data", + "/enterprise/2.15/admin/guides/user-management/removing-users-from-teams-and-organizations": "/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations", + "/enterprise/2.15/admin/guides/user-management/repositories": "/enterprise/2.15/admin/user-management/repositories", + "/enterprise/2.15/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization", + "/enterprise/2.15/admin/guides/user-management/suspending-and-unsuspending-users": "/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users", + "/enterprise/2.15/admin/guides/user-management/user-security": "/enterprise/2.15/admin/user-management/user-security", + "/enterprise/2.15/admin/guides/user-management/using-built-in-authentication": "/enterprise/2.15/admin/user-management/using-built-in-authentication", + "/enterprise/2.15/admin/guides/user-management/using-cas": "/enterprise/2.15/admin/user-management/using-cas", + "/enterprise/2.15/admin/guides/user-management/using-ldap": "/enterprise/2.15/admin/user-management/using-ldap", + "/enterprise/2.15/admin/guides/user-management/using-saml": "/enterprise/2.15/admin/user-management/using-saml", + "/enterprise/2.15/articles/3d-file-viewer": "/enterprise/2.15/user/articles/3d-file-viewer", + "/enterprise/2.15/articles/about-archiving-repositories": "/enterprise/2.15/user/articles/about-archiving-repositories", + "/enterprise/2.15/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": "/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters", + "/enterprise/2.15/articles/about-automation-for-project-boards": "/enterprise/2.15/user/articles/about-automation-for-project-boards", + "/enterprise/2.15/articles/about-branch-restrictions": "/enterprise/2.15/user/articles/about-branch-restrictions", + "/enterprise/2.15/articles/about-branches": "/enterprise/2.15/user/articles/about-branches", + "/enterprise/2.15/articles/about-code-owners": "/enterprise/2.15/user/articles/about-code-owners", + "/enterprise/2.15/articles/about-collaborative-development-models": "/enterprise/2.15/user/articles/about-collaborative-development-models", + "/enterprise/2.15/articles/about-commit-signature-verification": "/enterprise/2.15/user/articles/about-commit-signature-verification", + "/enterprise/2.15/articles/about-comparing-branches-in-pull-requests": "/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests", + "/enterprise/2.15/articles/about-conversations-on-github": "/enterprise/2.15/user/articles/about-conversations-on-github", + "/enterprise/2.15/articles/about-duplicate-issues-and-pull-requests": "/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests", + "/enterprise/2.15/articles/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.15/articles/about-email-notifications": "/enterprise/2.15/user/articles/about-email-notifications", + "/enterprise/2.15/articles/about-forks": "/enterprise/2.15/user/articles/about-forks", + "/enterprise/2.15/articles/about-git-large-file-storage": "/enterprise/2.15/user/articles/about-git-large-file-storage", + "/enterprise/2.15/articles/about-git-rebase": "/enterprise/2.15/user/articles/about-git-rebase", + "/enterprise/2.15/articles/about-git-subtree-merges": "/enterprise/2.15/user/articles/about-git-subtree-merges", + "/enterprise/2.15/articles/about-github-pages-and-jekyll": "/enterprise/2.15/user/articles/about-github-pages-and-jekyll", + "/enterprise/2.15/articles/about-github-pages": "/enterprise/2.15/user/articles/about-github-pages", + "/enterprise/2.15/articles/about-issue-and-pull-request-templates": "/enterprise/2.15/user/articles/about-issue-and-pull-request-templates", + "/enterprise/2.15/articles/about-issues": "/enterprise/2.15/user/articles/about-issues", + "/enterprise/2.15/articles/about-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.15/articles/about-labels": "/enterprise/2.15/user/articles/about-labels", + "/enterprise/2.15/articles/about-merge-conflicts": "/enterprise/2.15/user/articles/about-merge-conflicts", + "/enterprise/2.15/articles/about-merge-methods-on-github": "/enterprise/2.15/user/articles/about-merge-methods-on-github", + "/enterprise/2.15/articles/about-milestones": "/enterprise/2.15/user/articles/about-milestones", + "/enterprise/2.15/articles/about-notifications": "/enterprise/2.15/user/articles/about-notifications", + "/enterprise/2.15/articles/about-organization-membership": "/enterprise/2.15/user/articles/about-organization-membership", + "/enterprise/2.15/articles/about-organizations": "/enterprise/2.15/user/articles/about-organizations", + "/enterprise/2.15/articles/about-project-boards": "/enterprise/2.15/user/articles/about-project-boards", + "/enterprise/2.15/articles/about-protected-branches": "/enterprise/2.15/user/articles/about-protected-branches", + "/enterprise/2.15/articles/about-pull-request-merges": "/enterprise/2.15/user/articles/about-pull-request-merges", + "/enterprise/2.15/articles/about-pull-request-reviews": "/enterprise/2.15/user/articles/about-pull-request-reviews", + "/enterprise/2.15/articles/about-pull-requests": "/enterprise/2.15/user/articles/about-pull-requests", + "/enterprise/2.15/articles/about-readmes": "/enterprise/2.15/user/articles/about-readmes", + "/enterprise/2.15/articles/about-releases": "/enterprise/2.15/user/articles/about-releases", + "/enterprise/2.15/articles/about-remote-repositories": "/enterprise/2.15/user/articles/about-remote-repositories", + "/enterprise/2.15/articles/about-repositories": "/enterprise/2.15/user/articles/about-repositories", + "/enterprise/2.15/articles/about-repository-graphs": "/enterprise/2.15/user/articles/about-repository-graphs", + "/enterprise/2.15/articles/about-repository-languages": "/enterprise/2.15/user/articles/about-repository-languages", + "/enterprise/2.15/articles/about-required-commit-signing": "/enterprise/2.15/user/articles/about-required-commit-signing", + "/enterprise/2.15/articles/about-required-reviews-for-pull-requests": "/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests", + "/enterprise/2.15/articles/about-required-status-checks": "/enterprise/2.15/user/articles/about-required-status-checks", + "/enterprise/2.15/articles/about-saved-replies": "/enterprise/2.15/user/articles/about-saved-replies", + "/enterprise/2.15/articles/about-searching-on-github": "/enterprise/2.15/user/articles/about-searching-on-github", + "/enterprise/2.15/articles/about-ssh": "/enterprise/2.15/user/articles/about-ssh", + "/enterprise/2.15/articles/about-status-checks": "/enterprise/2.15/user/articles/about-status-checks", + "/enterprise/2.15/articles/about-task-lists": "/enterprise/2.15/user/articles/about-task-lists", + "/enterprise/2.15/articles/about-team-discussions": "/enterprise/2.15/user/articles/about-team-discussions", + "/enterprise/2.15/articles/about-teams": "/enterprise/2.15/user/articles/about-teams", + "/enterprise/2.15/articles/about-two-factor-authentication": "/enterprise/2.15/user/articles/about-two-factor-authentication", + "/enterprise/2.15/articles/about-web-notifications": "/enterprise/2.15/user/articles/about-web-notifications", + "/enterprise/2.15/articles/about-webhooks": "/enterprise/2.15/user/articles/about-webhooks", + "/enterprise/2.15/articles/about-wikis": "/enterprise/2.15/user/articles/about-wikis", + "/enterprise/2.15/articles/about-writing-and-formatting-on-github": "/enterprise/2.15/user/articles/about-writing-and-formatting-on-github", + "/enterprise/2.15/articles/about-your-organization-dashboard": "/enterprise/2.15/user/articles/about-your-organization-dashboard", + "/enterprise/2.15/articles/about-your-organizations-news-feed": "/enterprise/2.15/user/articles/about-your-organizations-news-feed", + "/enterprise/2.15/articles/about-your-organizations-profile": "/enterprise/2.15/user/articles/about-your-organizations-profile", + "/enterprise/2.15/articles/about-your-personal-dashboard": "/enterprise/2.15/user/articles/about-your-personal-dashboard", + "/enterprise/2.15/articles/about-your-profile": "/enterprise/2.15/user/articles/about-your-profile", + "/enterprise/2.15/articles/access-permissions-on-github": "/enterprise/2.15/user/articles/access-permissions-on-github", + "/enterprise/2.15/articles/accessing-an-organization": "/enterprise/2.15/user/articles/accessing-an-organization", + "/enterprise/2.15/articles/accessing-basic-repository-data": "/enterprise/2.15/user/articles/accessing-basic-repository-data", + "/enterprise/2.15/articles/accessing-github-using-two-factor-authentication": "/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication", + "/enterprise/2.15/articles/accessing-your-notifications": "/enterprise/2.15/user/articles/accessing-your-notifications", + "/enterprise/2.15/articles/accessing-your-organizations-settings": "/enterprise/2.15/user/articles/accessing-your-organizations-settings", + "/enterprise/2.15/articles/adding-a-file-to-a-repository-using-the-command-line": "/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line", + "/enterprise/2.15/articles/adding-a-file-to-a-repository": "/enterprise/2.15/user/articles/adding-a-file-to-a-repository", + "/enterprise/2.15/articles/adding-a-license-to-a-repository": "/enterprise/2.15/user/articles/adding-a-license-to-a-repository", + "/enterprise/2.15/articles/adding-a-new-gpg-key-to-your-github-account": "/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account", + "/enterprise/2.15/articles/adding-a-new-ssh-key-to-your-github-account": "/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account", + "/enterprise/2.15/articles/adding-a-remote": "/enterprise/2.15/user/articles/adding-a-remote", + "/enterprise/2.15/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": "/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll", + "/enterprise/2.15/articles/adding-an-email-address-to-your-github-account": "/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account", + "/enterprise/2.15/articles/adding-an-existing-project-to-github-using-the-command-line": "/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line", + "/enterprise/2.15/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization", + "/enterprise/2.15/articles/adding-content-to-your-github-pages-site-using-jekyll": "/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll", + "/enterprise/2.15/articles/adding-issues-and-pull-requests-to-a-project-board": "/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board", + "/enterprise/2.15/articles/adding-notes-to-a-project-board": "/enterprise/2.15/user/articles/adding-notes-to-a-project-board", + "/enterprise/2.15/articles/adding-or-editing-wiki-pages": "/enterprise/2.15/user/articles/adding-or-editing-wiki-pages", + "/enterprise/2.15/articles/adding-organization-members-to-a-team": "/enterprise/2.15/user/articles/adding-organization-members-to-a-team", + "/enterprise/2.15/articles/adding-outside-collaborators-to-repositories-in-your-organization": "/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization", + "/enterprise/2.15/articles/adding-people-to-your-organization": "/enterprise/2.15/user/articles/adding-people-to-your-organization", + "/enterprise/2.15/articles/adding-support-resources-to-your-project": "/enterprise/2.15/user/articles/adding-support-resources-to-your-project", + "/enterprise/2.15/articles/addressing-merge-conflicts": "/enterprise/2.15/user/articles/addressing-merge-conflicts", + "/enterprise/2.15/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.15/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization", + "/enterprise/2.15/articles/allowing-people-to-fork-private-repositories-in-your-organization": "/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization", + "/enterprise/2.15/articles/analyzing-changes-to-a-repositorys-content": "/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content", + "/enterprise/2.15/articles/applying-labels-to-issues-and-pull-requests": "/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests", + "/enterprise/2.15/articles/approving-a-pull-request-with-required-reviews": "/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews", + "/enterprise/2.15/articles/archiving-a-github-repository": "/enterprise/2.15/user/articles/archiving-a-github-repository", + "/enterprise/2.15/articles/archiving-cards-on-a-project-board": "/enterprise/2.15/user/articles/archiving-cards-on-a-project-board", + "/enterprise/2.15/articles/archiving-repositories": "/enterprise/2.15/user/articles/archiving-repositories", + "/enterprise/2.15/articles/assigning-issues-and-pull-requests-to-other-github-users": "/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users", + "/enterprise/2.15/articles/associating-an-email-with-your-gpg-key": "/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key", + "/enterprise/2.15/articles/associating-milestones-with-issues-and-pull-requests": "/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests", + "/enterprise/2.15/articles/associating-text-editors-with-git": "/enterprise/2.15/user/articles/associating-text-editors-with-git", + "/enterprise/2.15/articles/authorizing-oauth-apps": "/enterprise/2.15/user/articles/authorizing-oauth-apps", + "/enterprise/2.15/articles/autolinked-references-and-urls": "/enterprise/2.15/user/articles/autolinked-references-and-urls", + "/enterprise/2.15/articles/backing-up-a-repository": "/enterprise/2.15/user/articles/backing-up-a-repository", + "/enterprise/2.15/articles/basic-writing-and-formatting-syntax": "/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax", + "/enterprise/2.15/articles/be-social": "/enterprise/2.15/user/articles/be-social", + "/enterprise/2.15/articles/caching-your-github-password-in-git": "/enterprise/2.15/user/articles/caching-your-github-password-in-git", + "/enterprise/2.15/articles/changing-a-commit-message": "/enterprise/2.15/user/articles/changing-a-commit-message", + "/enterprise/2.15/articles/changing-a-persons-role-to-owner": "/enterprise/2.15/user/articles/changing-a-persons-role-to-owner", + "/enterprise/2.15/articles/changing-a-remotes-url": "/enterprise/2.15/user/articles/changing-a-remotes-url", + "/enterprise/2.15/articles/changing-access-permissions-for-wikis": "/enterprise/2.15/user/articles/changing-access-permissions-for-wikis", + "/enterprise/2.15/articles/changing-author-info": "/enterprise/2.15/user/articles/changing-author-info", + "/enterprise/2.15/articles/changing-project-board-visibility": "/enterprise/2.15/user/articles/changing-project-board-visibility", + "/enterprise/2.15/articles/changing-team-visibility": "/enterprise/2.15/user/articles/changing-team-visibility", + "/enterprise/2.15/articles/changing-the-base-branch-of-a-pull-request": "/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request", + "/enterprise/2.15/articles/changing-your-github-username": "/enterprise/2.15/user/articles/changing-your-github-username", + "/enterprise/2.15/articles/changing-your-primary-email-address": "/enterprise/2.15/user/articles/changing-your-primary-email-address", + "/enterprise/2.15/articles/checking-for-existing-gpg-keys": "/enterprise/2.15/user/articles/checking-for-existing-gpg-keys", + "/enterprise/2.15/articles/checking-for-existing-ssh-keys": "/enterprise/2.15/user/articles/checking-for-existing-ssh-keys", + "/enterprise/2.15/articles/checking-out-pull-requests-locally": "/enterprise/2.15/user/articles/checking-out-pull-requests-locally", + "/enterprise/2.15/articles/checking-your-commit-and-tag-signature-verification-status": "/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status", + "/enterprise/2.15/articles/choosing-the-delivery-method-for-your-notifications": "/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications", + "/enterprise/2.15/articles/classifying-your-repository-with-topics": "/enterprise/2.15/user/articles/classifying-your-repository-with-topics", + "/enterprise/2.15/articles/cloning-a-repository-from-github": "/enterprise/2.15/user/articles/cloning-a-repository-from-github", + "/enterprise/2.15/articles/cloning-a-repository": "/enterprise/2.15/user/articles/cloning-a-repository", + "/enterprise/2.15/articles/closing-a-project-board": "/enterprise/2.15/user/articles/closing-a-project-board", + "/enterprise/2.15/articles/closing-a-pull-request": "/enterprise/2.15/user/articles/closing-a-pull-request", + "/enterprise/2.15/articles/closing-issues-using-keywords": "/enterprise/2.15/user/articles/closing-issues-using-keywords", + "/enterprise/2.15/articles/collaborating-on-repositories-with-code-quality-features": "/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features", + "/enterprise/2.15/articles/collaborating-with-groups-in-organizations": "/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations", + "/enterprise/2.15/articles/collaborating-with-your-team": "/enterprise/2.15/user/articles/collaborating-with-your-team", + "/enterprise/2.15/articles/collaboration-with-git-large-file-storage": "/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage", + "/enterprise/2.15/articles/commenting-on-a-pull-request": "/enterprise/2.15/user/articles/commenting-on-a-pull-request", + "/enterprise/2.15/articles/commit-branch-and-tag-labels": "/enterprise/2.15/user/articles/commit-branch-and-tag-labels", + "/enterprise/2.15/articles/commit-exists-on-github-but-not-in-my-local-clone": "/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone", + "/enterprise/2.15/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.15/articles/comparing-commits-across-time": "/enterprise/2.15/user/articles/comparing-commits-across-time", + "/enterprise/2.15/articles/conditions-for-large-files": "/enterprise/2.15/user/articles/conditions-for-large-files", + "/enterprise/2.15/articles/configuring-a-publishing-source-for-your-github-pages-site": "/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site", + "/enterprise/2.15/articles/configuring-a-remote-for-a-fork": "/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork", + "/enterprise/2.15/articles/configuring-automation-for-project-boards": "/enterprise/2.15/user/articles/configuring-automation-for-project-boards", + "/enterprise/2.15/articles/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.15/articles/configuring-commit-squashing-for-pull-requests": "/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.15/articles/configuring-git-large-file-storage": "/enterprise/2.15/user/articles/configuring-git-large-file-storage", + "/enterprise/2.15/articles/configuring-git-to-handle-line-endings": "/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings", + "/enterprise/2.15/articles/configuring-protected-branches": "/enterprise/2.15/user/articles/configuring-protected-branches", + "/enterprise/2.15/articles/configuring-pull-request-merges": "/enterprise/2.15/user/articles/configuring-pull-request-merges", + "/enterprise/2.15/articles/configuring-two-factor-authentication-recovery-methods": "/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods", + "/enterprise/2.15/articles/configuring-two-factor-authentication": "/enterprise/2.15/user/articles/configuring-two-factor-authentication", + "/enterprise/2.15/articles/connecting-to-github-with-ssh": "/enterprise/2.15/user/articles/connecting-to-github-with-ssh", + "/enterprise/2.15/articles/connecting-with-third-party-applications": "/enterprise/2.15/user/articles/connecting-with-third-party-applications", + "/enterprise/2.15/articles/converting-a-user-into-an-organization": "/enterprise/2.15/user/articles/converting-a-user-into-an-organization", + "/enterprise/2.15/articles/converting-an-admin-team-to-improved-organization-permissions": "/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions", + "/enterprise/2.15/articles/converting-an-organization-into-a-user": "/enterprise/2.15/user/articles/converting-an-organization-into-a-user", + "/enterprise/2.15/articles/converting-an-organization-member-to-an-outside-collaborator": "/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator", + "/enterprise/2.15/articles/converting-an-outside-collaborator-to-an-organization-member": "/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member", + "/enterprise/2.15/articles/converting-an-owners-team-to-improved-organization-permissions": "/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions", + "/enterprise/2.15/articles/create-a-repo": "/enterprise/2.15/user/articles/create-a-repo", + "/enterprise/2.15/articles/creating-a-commit-with-multiple-authors": "/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors", + "/enterprise/2.15/articles/creating-a-custom-404-page-for-your-github-pages-site": "/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site", + "/enterprise/2.15/articles/creating-a-footer-or-sidebar-for-your-wiki": "/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki", + "/enterprise/2.15/articles/creating-a-github-pages-site-with-jekyll": "/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll", + "/enterprise/2.15/articles/creating-a-github-pages-site": "/enterprise/2.15/user/articles/creating-a-github-pages-site", + "/enterprise/2.15/articles/creating-a-label": "/enterprise/2.15/user/articles/creating-a-label", + "/enterprise/2.15/articles/creating-a-new-organization-from-scratch": "/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch", + "/enterprise/2.15/articles/creating-a-new-repository": "/enterprise/2.15/user/articles/creating-a-new-repository", + "/enterprise/2.15/articles/creating-a-permanent-link-to-a-code-snippet": "/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet", + "/enterprise/2.15/articles/creating-a-personal-access-token-for-the-command-line": "/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line", + "/enterprise/2.15/articles/creating-a-project-board": "/enterprise/2.15/user/articles/creating-a-project-board", + "/enterprise/2.15/articles/creating-a-pull-request-from-a-fork": "/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork", + "/enterprise/2.15/articles/creating-a-pull-request-template-for-your-repository": "/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository", + "/enterprise/2.15/articles/creating-a-pull-request": "/enterprise/2.15/user/articles/creating-a-pull-request", + "/enterprise/2.15/articles/creating-a-repository-on-github": "/enterprise/2.15/user/articles/creating-a-repository-on-github", + "/enterprise/2.15/articles/creating-a-saved-reply": "/enterprise/2.15/user/articles/creating-a-saved-reply", + "/enterprise/2.15/articles/creating-a-strong-password": "/enterprise/2.15/user/articles/creating-a-strong-password", + "/enterprise/2.15/articles/creating-a-team-discussion": "/enterprise/2.15/user/articles/creating-a-team-discussion", + "/enterprise/2.15/articles/creating-a-team": "/enterprise/2.15/user/articles/creating-a-team", + "/enterprise/2.15/articles/creating-an-issue": "/enterprise/2.15/user/articles/creating-an-issue", + "/enterprise/2.15/articles/creating-an-issues-only-repository": "/enterprise/2.15/user/articles/creating-an-issues-only-repository", + "/enterprise/2.15/articles/creating-and-deleting-branches-within-your-repository": "/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository", + "/enterprise/2.15/articles/creating-and-editing-commits": "/enterprise/2.15/user/articles/creating-and-editing-commits", + "/enterprise/2.15/articles/creating-and-editing-milestones-for-issues-and-pull-requests": "/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests", + "/enterprise/2.15/articles/creating-and-highlighting-code-blocks": "/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks", + "/enterprise/2.15/articles/creating-gists": "/enterprise/2.15/user/articles/creating-gists", + "/enterprise/2.15/articles/creating-issue-templates-for-your-repository": "/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository", + "/enterprise/2.15/articles/creating-new-files": "/enterprise/2.15/user/articles/creating-new-files", + "/enterprise/2.15/articles/creating-releases": "/enterprise/2.15/user/articles/creating-releases", + "/enterprise/2.15/articles/customizing-how-changed-files-appear-on-github": "/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github", + "/enterprise/2.15/articles/customizing-your-profile": "/enterprise/2.15/user/articles/customizing-your-profile", + "/enterprise/2.15/articles/dealing-with-non-fast-forward-errors": "/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors", + "/enterprise/2.15/articles/defining-the-mergeability-of-pull-requests": "/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests", + "/enterprise/2.15/articles/deleting-a-label": "/enterprise/2.15/user/articles/deleting-a-label", + "/enterprise/2.15/articles/deleting-a-project-board": "/enterprise/2.15/user/articles/deleting-a-project-board", + "/enterprise/2.15/articles/deleting-a-repository": "/enterprise/2.15/user/articles/deleting-a-repository", + "/enterprise/2.15/articles/deleting-a-saved-reply": "/enterprise/2.15/user/articles/deleting-a-saved-reply", + "/enterprise/2.15/articles/deleting-a-team": "/enterprise/2.15/user/articles/deleting-a-team", + "/enterprise/2.15/articles/deleting-an-organization-account": "/enterprise/2.15/user/articles/deleting-an-organization-account", + "/enterprise/2.15/articles/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.15/articles/deleting-files": "/enterprise/2.15/user/articles/deleting-files", + "/enterprise/2.15/articles/deleting-your-user-account": "/enterprise/2.15/user/articles/deleting-your-user-account", + "/enterprise/2.15/articles/differences-between-commit-views": "/enterprise/2.15/user/articles/differences-between-commit-views", + "/enterprise/2.15/articles/disabling-issues": "/enterprise/2.15/user/articles/disabling-issues", + "/enterprise/2.15/articles/disabling-project-boards-in-a-repository": "/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository", + "/enterprise/2.15/articles/disabling-project-boards-in-your-organization": "/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization", + "/enterprise/2.15/articles/disabling-team-discussions-for-your-organization": "/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization", + "/enterprise/2.15/articles/disabling-two-factor-authentication-for-your-personal-account": "/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account", + "/enterprise/2.15/articles/disabling-wikis": "/enterprise/2.15/user/articles/disabling-wikis", + "/enterprise/2.15/articles/dismissing-a-pull-request-review": "/enterprise/2.15/user/articles/dismissing-a-pull-request-review", + "/enterprise/2.15/articles/distributing-large-binaries": "/enterprise/2.15/user/articles/distributing-large-binaries", + "/enterprise/2.15/articles/documenting-your-project-with-wikis": "/enterprise/2.15/user/articles/documenting-your-project-with-wikis", + "/enterprise/2.15/articles/duplicating-a-repository": "/enterprise/2.15/user/articles/duplicating-a-repository", + "/enterprise/2.15/articles/editing-a-label": "/enterprise/2.15/user/articles/editing-a-label", + "/enterprise/2.15/articles/editing-a-project-board": "/enterprise/2.15/user/articles/editing-a-project-board", + "/enterprise/2.15/articles/editing-a-saved-reply": "/enterprise/2.15/user/articles/editing-a-saved-reply", + "/enterprise/2.15/articles/editing-and-deleting-releases": "/enterprise/2.15/user/articles/editing-and-deleting-releases", + "/enterprise/2.15/articles/editing-and-sharing-content-with-gists": "/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists", + "/enterprise/2.15/articles/editing-files-in-another-users-repository": "/enterprise/2.15/user/articles/editing-files-in-another-users-repository", + "/enterprise/2.15/articles/editing-files-in-your-repository": "/enterprise/2.15/user/articles/editing-files-in-your-repository", + "/enterprise/2.15/articles/editing-or-deleting-a-team-discussion": "/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion", + "/enterprise/2.15/articles/editing-wiki-content": "/enterprise/2.15/user/articles/editing-wiki-content", + "/enterprise/2.15/articles/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.15/articles/enabling-branch-restrictions": "/enterprise/2.15/user/articles/enabling-branch-restrictions", + "/enterprise/2.15/articles/enabling-githubcom-repository-search-in-github-enterprise-server": "/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server", + "/enterprise/2.15/articles/enabling-required-commit-signing": "/enterprise/2.15/user/articles/enabling-required-commit-signing", + "/enterprise/2.15/articles/enabling-required-reviews-for-pull-requests": "/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests", + "/enterprise/2.15/articles/enabling-required-status-checks": "/enterprise/2.15/user/articles/enabling-required-status-checks", + "/enterprise/2.15/articles/error-agent-admitted-failure-to-sign": "/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign", + "/enterprise/2.15/articles/error-bad-file-number": "/enterprise/2.15/user/articles/error-bad-file-number", + "/enterprise/2.15/articles/error-key-already-in-use": "/enterprise/2.15/user/articles/error-key-already-in-use", + "/enterprise/2.15/articles/error-permission-denied-publickey": "/enterprise/2.15/user/articles/error-permission-denied-publickey", + "/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-other-user": "/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user", + "/enterprise/2.15/articles/error-permission-to-userrepo-denied-to-userother-repo": "/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo", + "/enterprise/2.15/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", + "/enterprise/2.15/articles/error-repository-not-found": "/enterprise/2.15/user/articles/error-repository-not-found", + "/enterprise/2.15/articles/error-ssh-add-illegal-option----k": "/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k", + "/enterprise/2.15/articles/error-were-doing-an-ssh-key-audit": "/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit", + "/enterprise/2.15/articles/exploring-projects-on-github": "/enterprise/2.15/user/articles/exploring-projects-on-github", + "/enterprise/2.15/articles/file-attachments-on-issues-and-pull-requests": "/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests", + "/enterprise/2.15/articles/filtering-cards-on-a-project-board": "/enterprise/2.15/user/articles/filtering-cards-on-a-project-board", + "/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-assignees": "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees", + "/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-labels": "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels", + "/enterprise/2.15/articles/filtering-issues-and-pull-requests-by-milestone": "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone", + "/enterprise/2.15/articles/filtering-issues-and-pull-requests": "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests", + "/enterprise/2.15/articles/filtering-pull-requests-by-review-status": "/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status", + "/enterprise/2.15/articles/finding-changed-methods-and-functions-in-a-pull-request": "/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request", + "/enterprise/2.15/articles/finding-files-on-github": "/enterprise/2.15/user/articles/finding-files-on-github", + "/enterprise/2.15/articles/finding-information-in-a-repository": "/enterprise/2.15/user/articles/finding-information-in-a-repository", + "/enterprise/2.15/articles/following-people": "/enterprise/2.15/user/articles/following-people", + "/enterprise/2.15/articles/fork-a-repo": "/enterprise/2.15/user/articles/fork-a-repo", + "/enterprise/2.15/articles/forking-and-cloning-gists": "/enterprise/2.15/user/articles/forking-and-cloning-gists", + "/enterprise/2.15/articles/generating-a-new-gpg-key": "/enterprise/2.15/user/articles/generating-a-new-gpg-key", + "/enterprise/2.15/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", + "/enterprise/2.15/articles/getting-changes-from-a-remote-repository": "/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository", + "/enterprise/2.15/articles/getting-permanent-links-to-files": "/enterprise/2.15/user/articles/getting-permanent-links-to-files", + "/enterprise/2.15/articles/getting-started-with-git-and-github": "/enterprise/2.15/user/articles/getting-started-with-git-and-github", + "/enterprise/2.15/articles/getting-started-with-github-pages": "/enterprise/2.15/user/articles/getting-started-with-github-pages", + "/enterprise/2.15/articles/getting-started-with-notifications": "/enterprise/2.15/user/articles/getting-started-with-notifications", + "/enterprise/2.15/articles/getting-started-with-searching-on-github": "/enterprise/2.15/user/articles/getting-started-with-searching-on-github", + "/enterprise/2.15/articles/getting-started-with-the-api": "/enterprise/2.15/user/articles/getting-started-with-the-api", + "/enterprise/2.15/articles/getting-started-with-writing-and-formatting-on-github": "/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github", + "/enterprise/2.15/articles/getting-the-download-count-for-your-releases": "/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases", + "/enterprise/2.15/articles/git-and-github-learning-resources": "/enterprise/2.15/user/articles/git-and-github-learning-resources", + "/enterprise/2.15/articles/git-automation-with-oauth-tokens": "/enterprise/2.15/user/articles/git-automation-with-oauth-tokens", + "/enterprise/2.15/articles/git-cheatsheet": "/enterprise/2.15/user/articles/git-cheatsheet", + "/enterprise/2.15/articles/git-workflows": "/enterprise/2.15/user/articles/git-workflows", + "/enterprise/2.15/articles/github-flow": "/enterprise/2.15/user/articles/github-flow", + "/enterprise/2.15/articles/github-glossary": "/enterprise/2.15/user/articles/github-glossary", + "/enterprise/2.15/articles/giving-team-maintainer-permissions-to-an-organization-member": "/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member", + "/enterprise/2.15/articles/https-cloning-errors": "/enterprise/2.15/user/articles/https-cloning-errors", + "/enterprise/2.15/articles/ignoring-files": "/enterprise/2.15/user/articles/ignoring-files", + "/enterprise/2.15/articles/importing-a-git-repository-using-the-command-line": "/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line", + "/enterprise/2.15/articles/importing-source-code-to-github": "/enterprise/2.15/user/articles/importing-source-code-to-github", + "/enterprise/2.15/articles/incorporating-changes-from-a-pull-request": "/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request", + "/enterprise/2.15/articles/initializing-an-empty-repository-with-a-readme": "/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme", + "/enterprise/2.15/articles/installing-git-large-file-storage": "/enterprise/2.15/user/articles/installing-git-large-file-storage", + "/enterprise/2.15/articles/integrating-jira-with-your-organization-project-board": "/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board", + "/enterprise/2.15/articles/integrating-jira-with-your-personal-projects": "/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects", + "/enterprise/2.15/articles/inviting-collaborators-to-a-personal-repository": "/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository", + "/enterprise/2.15/articles/keeping-your-account-and-data-secure": "/enterprise/2.15/user/articles/keeping-your-account-and-data-secure", + "/enterprise/2.15/articles/keeping-your-organization-secure": "/enterprise/2.15/user/articles/keeping-your-organization-secure", + "/enterprise/2.15/articles/keyboard-shortcuts": "/enterprise/2.15/user/articles/keyboard-shortcuts", + "/enterprise/2.15/articles/labeling-issues-and-pull-requests": "/enterprise/2.15/user/articles/labeling-issues-and-pull-requests", + "/enterprise/2.15/articles/learning-about-git": "/enterprise/2.15/user/articles/learning-about-git", + "/enterprise/2.15/articles/learning-about-github": "/enterprise/2.15/user/articles/learning-about-github", + "/enterprise/2.15/articles/licensing-a-repository": "/enterprise/2.15/user/articles/licensing-a-repository", + "/enterprise/2.15/articles/limits-for-viewing-content-and-diffs-in-a-repository": "/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository", + "/enterprise/2.15/articles/linking-a-repository-to-a-project-board": "/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board", + "/enterprise/2.15/articles/linking-to-releases": "/enterprise/2.15/user/articles/linking-to-releases", + "/enterprise/2.15/articles/listing-the-forks-of-a-repository": "/enterprise/2.15/user/articles/listing-the-forks-of-a-repository", + "/enterprise/2.15/articles/listing-the-repositories-youre-watching": "/enterprise/2.15/user/articles/listing-the-repositories-youre-watching", + "/enterprise/2.15/articles/locking-conversations": "/enterprise/2.15/user/articles/locking-conversations", + "/enterprise/2.15/articles/managing-access-to-a-project-board-for-organization-members": "/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members", + "/enterprise/2.15/articles/managing-access-to-your-organizations-project-boards": "/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards", + "/enterprise/2.15/articles/managing-access-to-your-organizations-repositories": "/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories", + "/enterprise/2.15/articles/managing-access-to-your-personal-repositories": "/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories", + "/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-project-board": "/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board", + "/enterprise/2.15/articles/managing-an-individuals-access-to-an-organization-repository": "/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository", + "/enterprise/2.15/articles/managing-branches-in-your-repository": "/enterprise/2.15/user/articles/managing-branches-in-your-repository", + "/enterprise/2.15/articles/managing-commit-signature-verification": "/enterprise/2.15/user/articles/managing-commit-signature-verification", + "/enterprise/2.15/articles/managing-contribution-graphs-on-your-profile": "/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile", + "/enterprise/2.15/articles/managing-disruptive-comments": "/enterprise/2.15/user/articles/managing-disruptive-comments", + "/enterprise/2.15/articles/managing-email-preferences": "/enterprise/2.15/user/articles/managing-email-preferences", + "/enterprise/2.15/articles/managing-files-on-github": "/enterprise/2.15/user/articles/managing-files-on-github", + "/enterprise/2.15/articles/managing-files-using-the-command-line": "/enterprise/2.15/user/articles/managing-files-using-the-command-line", + "/enterprise/2.15/articles/managing-membership-in-your-organization": "/enterprise/2.15/user/articles/managing-membership-in-your-organization", + "/enterprise/2.15/articles/managing-organization-settings": "/enterprise/2.15/user/articles/managing-organization-settings", + "/enterprise/2.15/articles/managing-peoples-access-to-your-organization-with-roles": "/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles", + "/enterprise/2.15/articles/managing-project-boards": "/enterprise/2.15/user/articles/managing-project-boards", + "/enterprise/2.15/articles/managing-releases-in-a-repository": "/enterprise/2.15/user/articles/managing-releases-in-a-repository", + "/enterprise/2.15/articles/managing-remote-repositories": "/enterprise/2.15/user/articles/managing-remote-repositories", + "/enterprise/2.15/articles/managing-repository-settings": "/enterprise/2.15/user/articles/managing-repository-settings", + "/enterprise/2.15/articles/managing-team-access-to-an-organization-project-board": "/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board", + "/enterprise/2.15/articles/managing-team-access-to-an-organization-repository": "/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository", + "/enterprise/2.15/articles/managing-user-account-settings": "/enterprise/2.15/user/articles/managing-user-account-settings", + "/enterprise/2.15/articles/managing-your-membership-in-organizations": "/enterprise/2.15/user/articles/managing-your-membership-in-organizations", + "/enterprise/2.15/articles/managing-your-notifications": "/enterprise/2.15/user/articles/managing-your-notifications", + "/enterprise/2.15/articles/managing-your-work-with-issues": "/enterprise/2.15/user/articles/managing-your-work-with-issues", + "/enterprise/2.15/articles/manually-creating-a-single-issue-template-for-your-repository": "/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository", + "/enterprise/2.15/articles/mapping-geojson-files-on-github": "/enterprise/2.15/user/articles/mapping-geojson-files-on-github", + "/enterprise/2.15/articles/marking-notifications-as-read": "/enterprise/2.15/user/articles/marking-notifications-as-read", + "/enterprise/2.15/articles/merging-a-pull-request": "/enterprise/2.15/user/articles/merging-a-pull-request", + "/enterprise/2.15/articles/merging-an-upstream-repository-into-your-fork": "/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork", + "/enterprise/2.15/articles/migrating-admin-teams-to-improved-organization-permissions": "/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions", + "/enterprise/2.15/articles/migrating-to-improved-organization-permissions": "/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions", + "/enterprise/2.15/articles/moderating-comments-and-conversations": "/enterprise/2.15/user/articles/moderating-comments-and-conversations", + "/enterprise/2.15/articles/moving-a-file-in-your-repository-to-git-large-file-storage": "/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage", + "/enterprise/2.15/articles/moving-a-file-to-a-new-location-using-the-command-line": "/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line", + "/enterprise/2.15/articles/moving-a-file-to-a-new-location": "/enterprise/2.15/user/articles/moving-a-file-to-a-new-location", + "/enterprise/2.15/articles/moving-a-team-in-your-organizations-hierarchy": "/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy", + "/enterprise/2.15/articles/opening-an-issue-from-code": "/enterprise/2.15/user/articles/opening-an-issue-from-code", + "/enterprise/2.15/articles/organizing-information-with-tables": "/enterprise/2.15/user/articles/organizing-information-with-tables", + "/enterprise/2.15/articles/organizing-members-into-teams": "/enterprise/2.15/user/articles/organizing-members-into-teams", + "/enterprise/2.15/articles/permission-levels-for-a-user-account-repository": "/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository", + "/enterprise/2.15/articles/permission-levels-for-an-organization": "/enterprise/2.15/user/articles/permission-levels-for-an-organization", + "/enterprise/2.15/articles/personalizing-your-profile": "/enterprise/2.15/user/articles/personalizing-your-profile", + "/enterprise/2.15/articles/pinning-a-team-discussion": "/enterprise/2.15/user/articles/pinning-a-team-discussion", + "/enterprise/2.15/articles/pinning-items-to-your-profile": "/enterprise/2.15/user/articles/pinning-items-to-your-profile", + "/enterprise/2.15/articles/preparing-to-require-two-factor-authentication-in-your-organization": "/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization", + "/enterprise/2.15/articles/preventing-unauthorized-access": "/enterprise/2.15/user/articles/preventing-unauthorized-access", + "/enterprise/2.15/articles/project-board-permissions-for-an-organization": "/enterprise/2.15/user/articles/project-board-permissions-for-an-organization", + "/enterprise/2.15/articles/proposing-changes-to-your-work-with-pull-requests": "/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests", + "/enterprise/2.15/articles/publicizing-or-hiding-organization-membership": "/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership", + "/enterprise/2.15/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": "/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile", + "/enterprise/2.15/articles/pushing-commits-to-a-remote-repository": "/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository", + "/enterprise/2.15/articles/recovering-your-account-if-you-lose-your-2fa-credentials": "/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials", + "/enterprise/2.15/articles/recovering-your-ssh-key-passphrase": "/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase", + "/enterprise/2.15/articles/reinstating-a-former-member-of-your-organization": "/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization", + "/enterprise/2.15/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": "/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization", + "/enterprise/2.15/articles/remembering-your-github-username-or-email": "/enterprise/2.15/user/articles/remembering-your-github-username-or-email", + "/enterprise/2.15/articles/removing-a-collaborator-from-a-personal-repository": "/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository", + "/enterprise/2.15/articles/removing-a-member-from-your-organization": "/enterprise/2.15/user/articles/removing-a-member-from-your-organization", + "/enterprise/2.15/articles/removing-a-remote": "/enterprise/2.15/user/articles/removing-a-remote", + "/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-project-board": "/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board", + "/enterprise/2.15/articles/removing-an-outside-collaborator-from-an-organization-repository": "/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository", + "/enterprise/2.15/articles/removing-files-from-a-repositorys-history": "/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history", + "/enterprise/2.15/articles/removing-files-from-git-large-file-storage": "/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage", + "/enterprise/2.15/articles/removing-organization-members-from-a-team": "/enterprise/2.15/user/articles/removing-organization-members-from-a-team", + "/enterprise/2.15/articles/removing-sensitive-data-from-a-repository": "/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository", + "/enterprise/2.15/articles/removing-yourself-from-a-collaborators-repository": "/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository", + "/enterprise/2.15/articles/removing-yourself-from-an-organization": "/enterprise/2.15/user/articles/removing-yourself-from-an-organization", + "/enterprise/2.15/articles/renaming-a-file-using-the-command-line": "/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line", + "/enterprise/2.15/articles/renaming-a-file": "/enterprise/2.15/user/articles/renaming-a-file", + "/enterprise/2.15/articles/renaming-a-remote": "/enterprise/2.15/user/articles/renaming-a-remote", + "/enterprise/2.15/articles/renaming-a-repository": "/enterprise/2.15/user/articles/renaming-a-repository", + "/enterprise/2.15/articles/renaming-a-team": "/enterprise/2.15/user/articles/renaming-a-team", + "/enterprise/2.15/articles/renaming-an-organization": "/enterprise/2.15/user/articles/renaming-an-organization", + "/enterprise/2.15/articles/rendering-and-diffing-images": "/enterprise/2.15/user/articles/rendering-and-diffing-images", + "/enterprise/2.15/articles/rendering-csv-and-tsv-data": "/enterprise/2.15/user/articles/rendering-csv-and-tsv-data", + "/enterprise/2.15/articles/rendering-differences-in-prose-documents": "/enterprise/2.15/user/articles/rendering-differences-in-prose-documents", + "/enterprise/2.15/articles/rendering-pdf-documents": "/enterprise/2.15/user/articles/rendering-pdf-documents", + "/enterprise/2.15/articles/reopening-a-closed-project-board": "/enterprise/2.15/user/articles/reopening-a-closed-project-board", + "/enterprise/2.15/articles/repository-permission-levels-for-an-organization": "/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization", + "/enterprise/2.15/articles/requesting-a-pull-request-review": "/enterprise/2.15/user/articles/requesting-a-pull-request-review", + "/enterprise/2.15/articles/requesting-to-add-a-child-team": "/enterprise/2.15/user/articles/requesting-to-add-a-child-team", + "/enterprise/2.15/articles/requesting-to-add-or-change-a-parent-team": "/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team", + "/enterprise/2.15/articles/requiring-two-factor-authentication-in-your-organization": "/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization", + "/enterprise/2.15/articles/resolving-a-merge-conflict-on-github": "/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github", + "/enterprise/2.15/articles/resolving-a-merge-conflict-using-the-command-line": "/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line", + "/enterprise/2.15/articles/resolving-git-large-file-storage-upload-failures": "/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures", + "/enterprise/2.15/articles/resolving-merge-conflicts-after-a-git-rebase": "/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase", + "/enterprise/2.15/articles/restricting-repository-creation-in-your-organization": "/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization", + "/enterprise/2.15/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.15/articles/reverting-a-pull-request": "/enterprise/2.15/user/articles/reverting-a-pull-request", + "/enterprise/2.15/articles/reviewing-changes-in-pull-requests": "/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests", + "/enterprise/2.15/articles/reviewing-proposed-changes-in-a-pull-request": "/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request", + "/enterprise/2.15/articles/reviewing-the-audit-log-for-your-organization": "/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization", + "/enterprise/2.15/articles/reviewing-your-authorized-applications-oauth": "/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth", + "/enterprise/2.15/articles/reviewing-your-authorized-integrations": "/enterprise/2.15/user/articles/reviewing-your-authorized-integrations", + "/enterprise/2.15/articles/reviewing-your-deploy-keys": "/enterprise/2.15/user/articles/reviewing-your-deploy-keys", + "/enterprise/2.15/articles/reviewing-your-organizations-installed-integrations": "/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations", + "/enterprise/2.15/articles/reviewing-your-security-log": "/enterprise/2.15/user/articles/reviewing-your-security-log", + "/enterprise/2.15/articles/reviewing-your-ssh-keys": "/enterprise/2.15/user/articles/reviewing-your-ssh-keys", + "/enterprise/2.15/articles/saving-repositories-with-stars": "/enterprise/2.15/user/articles/saving-repositories-with-stars", + "/enterprise/2.15/articles/searching-code": "/enterprise/2.15/user/articles/searching-code", + "/enterprise/2.15/articles/searching-commits": "/enterprise/2.15/user/articles/searching-commits", + "/enterprise/2.15/articles/searching-for-repositories": "/enterprise/2.15/user/articles/searching-for-repositories", + "/enterprise/2.15/articles/searching-in-forks": "/enterprise/2.15/user/articles/searching-in-forks", + "/enterprise/2.15/articles/searching-issues-and-pull-requests": "/enterprise/2.15/user/articles/searching-issues-and-pull-requests", + "/enterprise/2.15/articles/searching-on-github": "/enterprise/2.15/user/articles/searching-on-github", + "/enterprise/2.15/articles/searching-topics": "/enterprise/2.15/user/articles/searching-topics", + "/enterprise/2.15/articles/searching-users": "/enterprise/2.15/user/articles/searching-users", + "/enterprise/2.15/articles/searching-wikis": "/enterprise/2.15/user/articles/searching-wikis", + "/enterprise/2.15/articles/securing-your-account-with-two-factor-authentication-2fa": "/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa", + "/enterprise/2.15/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", + "/enterprise/2.15/articles/set-up-git": "/enterprise/2.15/user/articles/set-up-git", + "/enterprise/2.15/articles/setting-a-backup-email-address": "/enterprise/2.15/user/articles/setting-a-backup-email-address", + "/enterprise/2.15/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", + "/enterprise/2.15/articles/setting-guidelines-for-repository-contributors": "/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors", + "/enterprise/2.15/articles/setting-permissions-for-deleting-or-transferring-repositories": "/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories", + "/enterprise/2.15/articles/setting-repository-visibility": "/enterprise/2.15/user/articles/setting-repository-visibility", + "/enterprise/2.15/articles/setting-the-default-branch": "/enterprise/2.15/user/articles/setting-the-default-branch", + "/enterprise/2.15/articles/setting-up-a-github-pages-site-with-jekyll": "/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll", + "/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-cloud": "/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud", + "/enterprise/2.15/articles/setting-up-a-trial-of-github-enterprise-server": "/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server", + "/enterprise/2.15/articles/setting-up-your-project-for-healthy-contributions": "/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions", + "/enterprise/2.15/articles/setting-your-commit-email-address": "/enterprise/2.15/user/articles/setting-your-commit-email-address", + "/enterprise/2.15/articles/setting-your-teams-profile-picture": "/enterprise/2.15/user/articles/setting-your-teams-profile-picture", + "/enterprise/2.15/articles/setting-your-username-in-git": "/enterprise/2.15/user/articles/setting-your-username-in-git", + "/enterprise/2.15/articles/sharing-filters": "/enterprise/2.15/user/articles/sharing-filters", + "/enterprise/2.15/articles/showing-an-overview-of-your-activity-on-your-profile": "/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile", + "/enterprise/2.15/articles/signing-commits": "/enterprise/2.15/user/articles/signing-commits", + "/enterprise/2.15/articles/signing-tags": "/enterprise/2.15/user/articles/signing-tags", + "/enterprise/2.15/articles/signing-up-for-github": "/enterprise/2.15/user/articles/signing-up-for-github", + "/enterprise/2.15/articles/sorting-issues-and-pull-requests": "/enterprise/2.15/user/articles/sorting-issues-and-pull-requests", + "/enterprise/2.15/articles/sorting-search-results": "/enterprise/2.15/user/articles/sorting-search-results", + "/enterprise/2.15/articles/source-code-migration-tools": "/enterprise/2.15/user/articles/source-code-migration-tools", + "/enterprise/2.15/articles/splitting-a-subfolder-out-into-a-new-repository": "/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository", + "/enterprise/2.15/articles/subscribing-to-and-unsubscribing-from-notifications": "/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications", + "/enterprise/2.15/articles/subversion-properties-supported-by-github": "/enterprise/2.15/user/articles/subversion-properties-supported-by-github", + "/enterprise/2.15/articles/sudo-mode": "/enterprise/2.15/user/articles/sudo-mode", + "/enterprise/2.15/articles/support-for-subversion-clients": "/enterprise/2.15/user/articles/support-for-subversion-clients", + "/enterprise/2.15/articles/supported-browsers": "/enterprise/2.15/user/articles/supported-browsers", + "/enterprise/2.15/articles/syncing-a-fork": "/enterprise/2.15/user/articles/syncing-a-fork", + "/enterprise/2.15/articles/telling-git-about-your-signing-key": "/enterprise/2.15/user/articles/telling-git-about-your-signing-key", + "/enterprise/2.15/articles/testing-your-github-pages-site-locally-with-jekyll": "/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll", + "/enterprise/2.15/articles/testing-your-ssh-connection": "/enterprise/2.15/user/articles/testing-your-ssh-connection", + "/enterprise/2.15/articles/tracking-changes-in-a-comment": "/enterprise/2.15/user/articles/tracking-changes-in-a-comment", + "/enterprise/2.15/articles/tracking-changes-in-a-file": "/enterprise/2.15/user/articles/tracking-changes-in-a-file", + "/enterprise/2.15/articles/tracking-progress-on-your-project-board": "/enterprise/2.15/user/articles/tracking-progress-on-your-project-board", + "/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-milestones": "/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones", + "/enterprise/2.15/articles/tracking-the-progress-of-your-work-with-project-boards": "/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards", + "/enterprise/2.15/articles/transferring-a-repository": "/enterprise/2.15/user/articles/transferring-a-repository", + "/enterprise/2.15/articles/transferring-organization-ownership": "/enterprise/2.15/user/articles/transferring-organization-ownership", + "/enterprise/2.15/articles/troubleshooting-commit-signature-verification": "/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification", + "/enterprise/2.15/articles/troubleshooting-commits-on-your-timeline": "/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline", + "/enterprise/2.15/articles/troubleshooting-commits": "/enterprise/2.15/user/articles/troubleshooting-commits", + "/enterprise/2.15/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.15/articles/troubleshooting-search-queries": "/enterprise/2.15/user/articles/troubleshooting-search-queries", + "/enterprise/2.15/articles/troubleshooting-ssh": "/enterprise/2.15/user/articles/troubleshooting-ssh", + "/enterprise/2.15/articles/types-of-github-accounts": "/enterprise/2.15/user/articles/types-of-github-accounts", + "/enterprise/2.15/articles/types-of-required-status-checks": "/enterprise/2.15/user/articles/types-of-required-status-checks", + "/enterprise/2.15/articles/understanding-connections-between-repositories": "/enterprise/2.15/user/articles/understanding-connections-between-repositories", + "/enterprise/2.15/articles/understanding-the-search-syntax": "/enterprise/2.15/user/articles/understanding-the-search-syntax", + "/enterprise/2.15/articles/unpublishing-a-github-pages-site": "/enterprise/2.15/user/articles/unpublishing-a-github-pages-site", + "/enterprise/2.15/articles/updating-an-expired-gpg-key": "/enterprise/2.15/user/articles/updating-an-expired-gpg-key", + "/enterprise/2.15/articles/updating-credentials-from-the-osx-keychain": "/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain", + "/enterprise/2.15/articles/updating-your-github-access-credentials": "/enterprise/2.15/user/articles/updating-your-github-access-credentials", + "/enterprise/2.15/articles/using-a-verified-email-address-in-your-gpg-key": "/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key", + "/enterprise/2.15/articles/using-advanced-git-commands": "/enterprise/2.15/user/articles/using-advanced-git-commands", + "/enterprise/2.15/articles/using-common-git-commands": "/enterprise/2.15/user/articles/using-common-git-commands", + "/enterprise/2.15/articles/using-git-rebase-on-the-command-line": "/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line", + "/enterprise/2.15/articles/using-github": "/enterprise/2.15/user/articles/using-github", + "/enterprise/2.15/articles/using-issue-and-pull-request-templates": "/enterprise/2.15/user/articles/using-issue-and-pull-request-templates", + "/enterprise/2.15/articles/using-saved-replies": "/enterprise/2.15/user/articles/using-saved-replies", + "/enterprise/2.15/articles/using-search-to-filter-issues-and-pull-requests": "/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests", + "/enterprise/2.15/articles/versioning-large-files": "/enterprise/2.15/user/articles/versioning-large-files", + "/enterprise/2.15/articles/viewing-a-projects-contributors": "/enterprise/2.15/user/articles/viewing-a-projects-contributors", + "/enterprise/2.15/articles/viewing-a-pull-request-review": "/enterprise/2.15/user/articles/viewing-a-pull-request-review", + "/enterprise/2.15/articles/viewing-a-repositorys-network": "/enterprise/2.15/user/articles/viewing-a-repositorys-network", + "/enterprise/2.15/articles/viewing-a-summary-of-repository-activity": "/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity", + "/enterprise/2.15/articles/viewing-a-wikis-history-of-changes": "/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes", + "/enterprise/2.15/articles/viewing-all-of-your-issues-and-pull-requests": "/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests", + "/enterprise/2.15/articles/viewing-and-comparing-commits": "/enterprise/2.15/user/articles/viewing-and-comparing-commits", + "/enterprise/2.15/articles/viewing-branches-in-your-repository": "/enterprise/2.15/user/articles/viewing-branches-in-your-repository", + "/enterprise/2.15/articles/viewing-contributions-on-your-profile": "/enterprise/2.15/user/articles/viewing-contributions-on-your-profile", + "/enterprise/2.15/articles/viewing-peoples-roles-in-an-organization": "/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization", + "/enterprise/2.15/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": "/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled", + "/enterprise/2.15/articles/viewing-your-milestones-progress": "/enterprise/2.15/user/articles/viewing-your-milestones-progress", + "/enterprise/2.15/articles/viewing-your-repositorys-tags": "/enterprise/2.15/user/articles/viewing-your-repositorys-tags", + "/enterprise/2.15/articles/visualizing-additions-and-deletions-to-content-in-a-repository": "/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository", + "/enterprise/2.15/articles/visualizing-commits-in-a-repository": "/enterprise/2.15/user/articles/visualizing-commits-in-a-repository", + "/enterprise/2.15/articles/watching-and-unwatching-repositories": "/enterprise/2.15/user/articles/watching-and-unwatching-repositories", + "/enterprise/2.15/articles/watching-and-unwatching-team-discussions": "/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions", + "/enterprise/2.15/articles/what-are-the-differences-between-subversion-and-git": "/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git", + "/enterprise/2.15/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", + "/enterprise/2.15/articles/which-remote-url-should-i-use": "/enterprise/2.15/user/articles/which-remote-url-should-i-use", + "/enterprise/2.15/articles/why-are-my-commits-in-the-wrong-order": "/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order", + "/enterprise/2.15/articles/why-are-my-commits-linked-to-the-wrong-user": "/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user", + "/enterprise/2.15/articles/why-are-my-contributions-not-showing-up-on-my-profile": "/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile", + "/enterprise/2.15/articles/why-is-git-always-asking-for-my-password": "/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password", + "/enterprise/2.15/articles/working-with-advanced-formatting": "/enterprise/2.15/user/articles/working-with-advanced-formatting", + "/enterprise/2.15/articles/working-with-forks": "/enterprise/2.15/user/articles/working-with-forks", + "/enterprise/2.15/articles/working-with-jupyter-notebook-files-on-github": "/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github", + "/enterprise/2.15/articles/working-with-large-files": "/enterprise/2.15/user/articles/working-with-large-files", + "/enterprise/2.15/articles/working-with-non-code-files": "/enterprise/2.15/user/articles/working-with-non-code-files", + "/enterprise/2.15/articles/working-with-pre-receive-hooks": "/enterprise/2.15/user/articles/working-with-pre-receive-hooks", + "/enterprise/2.15/articles/working-with-saved-replies": "/enterprise/2.15/user/articles/working-with-saved-replies", + "/enterprise/2.15/articles/working-with-ssh-key-passphrases": "/enterprise/2.15/user/articles/working-with-ssh-key-passphrases", + "/enterprise/2.15/articles/working-with-subversion-on-github": "/enterprise/2.15/user/articles/working-with-subversion-on-github", + "/enterprise/2.15/user/categories/admin/guidesistering-a-repository": "/enterprise/2.15/user/categories/administering-a-repository", + "/enterprise/2.15/categories/administering-a-repository": "/enterprise/2.15/user/categories/administering-a-repository", + "/enterprise/2.15/categories/authenticating-to-github": "/enterprise/2.15/user/categories/authenticating-to-github", + "/enterprise/2.15/categories/building-a-strong-community": "/enterprise/2.15/user/categories/building-a-strong-community", + "/enterprise/2.15/categories/collaborating-with-issues-and-pull-requests": "/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests", + "/enterprise/2.15/categories/committing-changes-to-your-project": "/enterprise/2.15/user/categories/committing-changes-to-your-project", + "/enterprise/2.15/categories/creating-cloning-and-archiving-repositories": "/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories", + "/enterprise/2.15/categories/extending-github": "/enterprise/2.15/user/categories/extending-github", + "/enterprise/2.15/categories/getting-started-with-github": "/enterprise/2.15/user/categories/getting-started-with-github", + "/enterprise/2.15/categories/importing-your-projects-to-github": "/enterprise/2.15/user/categories/importing-your-projects-to-github", + "/enterprise/2.15/categories/managing-files-in-a-repository": "/enterprise/2.15/user/categories/managing-files-in-a-repository", + "/enterprise/2.15/categories/managing-large-files": "/enterprise/2.15/user/categories/managing-large-files", + "/enterprise/2.15/categories/managing-your-work-on-github": "/enterprise/2.15/user/categories/managing-your-work-on-github", + "/enterprise/2.15/categories/receiving-notifications-about-activity-on-github": "/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github", + "/enterprise/2.15/categories/searching-for-information-on-github": "/enterprise/2.15/user/categories/searching-for-information-on-github", + "/enterprise/2.15/categories/setting-up-and-managing-organizations-and-teams": "/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams", + "/enterprise/2.15/categories/setting-up-and-managing-your-github-profile": "/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile", + "/enterprise/2.15/categories/setting-up-and-managing-your-github-user-account": "/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account", + "/enterprise/2.15/categories/using-git": "/enterprise/2.15/user/categories/using-git", + "/enterprise/2.15/categories/visualizing-repository-data-with-graphs": "/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs", + "/enterprise/2.15/categories/working-with-github-pages": "/enterprise/2.15/user/categories/working-with-github-pages", + "/enterprise/2.15/categories/writing-on-github": "/enterprise/2.15/user/categories/writing-on-github", + "/enterprise/2.15/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": null, + "/enterprise/2.15/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": null, + "/enterprise/2.15/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": null, + "/enterprise/2.15/admin/articles/using-github-task-runner": null, + "/enterprise/2.15/admin/clustering/about-cluster-nodes": null, + "/enterprise/2.15/admin/clustering/clustering-overview": null, + "/enterprise/2.15/admin/clustering/differences-between-clustering-and-high-availability-ha": null, + "/enterprise/2.15/admin/clustering/evacuating-a-cluster-node": null, + "/enterprise/2.15/admin/clustering": null, + "/enterprise/2.15/admin/clustering/initializing-the-cluster": null, + "/enterprise/2.15/admin/clustering/managing-a-github-enterprise-server-cluster": null, + "/enterprise/2.15/admin/clustering/monitoring-cluster-nodes": null, + "/enterprise/2.15/admin/clustering/network-configuration": null, + "/enterprise/2.15/admin/clustering/replacing-a-cluster-node": null, + "/enterprise/2.15/admin/clustering/setting-up-the-cluster-instances": null, + "/enterprise/2.15/admin/clustering/upgrading-a-cluster": null, + "/enterprise/2.15/admin/developer-workflow/about-pre-receive-hooks": null, + "/enterprise/2.15/admin/developer-workflow/about-protected-branches-and-required-status-checks": null, + "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-on-your-appliance": null, + "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-a-repository": null, + "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": null, + "/enterprise/2.15/admin/developer-workflow/blocking-force-pushes": null, + "/enterprise/2.15/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": null, + "/enterprise/2.15/admin/developer-workflow/continuous-integration-using-jenkins": null, + "/enterprise/2.15/admin/developer-workflow/continuous-integration-using-travis-ci": null, + "/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-environment": null, + "/enterprise/2.15/admin/developer-workflow/creating-a-pre-receive-hook-script": null, + "/enterprise/2.15/admin/developer-workflow/customizing-your-instance-with-integrations": null, + "/enterprise/2.15/admin/developer-workflow/establishing-pull-request-merge-conditions": null, + "/enterprise/2.15/admin/developer-workflow": null, + "/enterprise/2.15/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": null, + "/enterprise/2.15/admin/developer-workflow/managing-projects-using-jira": null, + "/enterprise/2.15/admin/developer-workflow/troubleshooting-service-hooks": null, + "/enterprise/2.15/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": null, + "/enterprise/2.15/admin/developer-workflow/using-webhooks-for-continuous-integration": null, + "/enterprise/2.15/admin/enterprise-support/about-github-enterprise-support": null, + "/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": null, + "/enterprise/2.15/admin/enterprise-support/about-github-premium-support-for-github-enterprise": null, + "/enterprise/2.15/admin/enterprise-support": null, + "/enterprise/2.15/admin/enterprise-support/preparing-to-submit-a-ticket": null, + "/enterprise/2.15/admin/enterprise-support/providing-data-to-github-support": null, + "/enterprise/2.15/admin/enterprise-support/reaching-github-support": null, + "/enterprise/2.15/admin/enterprise-support/receiving-help-from-github-support": null, + "/enterprise/2.15/admin/enterprise-support/submitting-a-ticket": null, + "/enterprise/2.15/admin": null, + "/enterprise/2.15/admin/installation/about-geo-replication": null, + "/enterprise/2.15/admin/installation/about-high-availability-configuration": null, + "/enterprise/2.15/admin/installation/about-the-github-enterprise-server-api": null, + "/enterprise/2.15/admin/installation/accessing-the-administrative-shell-ssh": null, + "/enterprise/2.15/admin/installation/accessing-the-management-console": null, + "/enterprise/2.15/admin/installation/accessing-the-monitor-dashboard": null, + "/enterprise/2.15/admin/installation/activity-dashboard": null, + "/enterprise/2.15/admin/installation/audit-logging": null, + "/enterprise/2.15/admin/installation/audited-actions": null, + "/enterprise/2.15/admin/installation/command-line-utilities": null, + "/enterprise/2.15/admin/installation/configuring-a-hostname": null, + "/enterprise/2.15/admin/installation/configuring-an-outbound-web-proxy-server": null, + "/enterprise/2.15/admin/installation/configuring-backups-on-your-appliance": null, + "/enterprise/2.15/admin/installation/configuring-built-in-firewall-rules": null, + "/enterprise/2.15/admin/installation/configuring-collectd": null, + "/enterprise/2.15/admin/installation/configuring-dns-nameservers": null, + "/enterprise/2.15/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": null, + "/enterprise/2.15/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": null, + "/enterprise/2.15/admin/installation/configuring-git-large-file-storage": null, + "/enterprise/2.15/admin/installation/configuring-github-enterprise-server-for-high-availability": null, + "/enterprise/2.15/admin/installation/configuring-github-pages-on-your-appliance": null, + "/enterprise/2.15/admin/installation/configuring-rate-limits": null, + "/enterprise/2.15/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": null, + "/enterprise/2.15/admin/installation/configuring-the-github-enterprise-server-appliance": null, + "/enterprise/2.15/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": null, + "/enterprise/2.15/admin/installation/configuring-time-synchronization": null, + "/enterprise/2.15/admin/installation/configuring-tls": null, + "/enterprise/2.15/admin/installation/configuring-your-github-enterprise-server-network-settings": null, + "/enterprise/2.15/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": null, + "/enterprise/2.15/admin/installation/creating-a-high-availability-replica": null, + "/enterprise/2.15/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": null, + "/enterprise/2.15/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": null, + "/enterprise/2.15/admin/installation/enabling-and-scheduling-maintenance-mode": null, + "/enterprise/2.15/admin/installation/enabling-automatic-update-checks": null, + "/enterprise/2.15/admin/installation/enabling-private-mode": null, + "/enterprise/2.15/admin/installation/enabling-subdomain-isolation": null, + "/enterprise/2.15/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.15/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.15/admin/installation/increasing-cpu-or-memory-resources": null, + "/enterprise/2.15/admin/installation/increasing-storage-capacity": null, + "/enterprise/2.15/admin/installation": null, + "/enterprise/2.15/admin/installation/initiating-a-failover-to-your-replica-appliance": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-aws": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-azure": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-hyper-v": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-openstack-kvm": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-vmware": null, + "/enterprise/2.15/admin/installation/installing-github-enterprise-server-on-xenserver": null, + "/enterprise/2.15/admin/installation/log-forwarding": null, + "/enterprise/2.15/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": null, + "/enterprise/2.15/admin/installation/managing-your-github-enterprise-server-license": null, + "/enterprise/2.15/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": null, + "/enterprise/2.15/admin/installation/migrating-from-github-enterprise-1110x-to-2123": null, + "/enterprise/2.15/admin/installation/migrating-to-a-different-git-large-file-storage-server": null, + "/enterprise/2.15/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": null, + "/enterprise/2.15/admin/installation/monitoring-using-snmp": null, + "/enterprise/2.15/admin/installation/monitoring-your-github-enterprise-server-appliance": null, + "/enterprise/2.15/admin/installation/network-ports": null, + "/enterprise/2.15/admin/installation/recommended-alert-thresholds": null, + "/enterprise/2.15/admin/installation/recovering-a-high-availability-configuration": null, + "/enterprise/2.15/admin/installation/removing-a-high-availability-replica": null, + "/enterprise/2.15/admin/installation/searching-the-audit-log": null, + "/enterprise/2.15/admin/installation/setting-git-push-limits": null, + "/enterprise/2.15/admin/installation/setting-up-a-github-enterprise-server-instance": null, + "/enterprise/2.15/admin/installation/setting-up-a-staging-instance": null, + "/enterprise/2.15/admin/installation/setting-up-external-monitoring": null, + "/enterprise/2.15/admin/installation/site-admin-dashboard": null, + "/enterprise/2.15/admin/installation/system-overview": null, + "/enterprise/2.15/admin/installation/troubleshooting-ssl-errors": null, + "/enterprise/2.15/admin/installation/updating-the-virtual-machine-and-physical-resources": null, + "/enterprise/2.15/admin/installation/upgrade-requirements": null, + "/enterprise/2.15/admin/installation/upgrading-github-enterprise-server": null, + "/enterprise/2.15/admin/installation/using-github-enterprise-server-with-a-load-balancer": null, + "/enterprise/2.15/admin/installation/validating-your-domain-settings": null, + "/enterprise/2.15/admin/installation/viewing-push-logs": null, + "/enterprise/2.15/admin/migrations/about-migrations": null, + "/enterprise/2.15/admin/migrations/applying-the-imported-data-on-github-enterprise-server": null, + "/enterprise/2.15/admin/migrations/completing-the-import-on-github-enterprise-server": null, + "/enterprise/2.15/admin/migrations/exporting-migration-data-from-github-enterprise-server": null, + "/enterprise/2.15/admin/migrations/exporting-migration-data-from-githubcom": null, + "/enterprise/2.15/admin/migrations/exporting-the-github-enterprise-server-source-repositories": null, + "/enterprise/2.15/admin/migrations/exporting-the-githubcom-organizations-repositories": null, + "/enterprise/2.15/admin/migrations/generating-a-list-of-migration-conflicts": null, + "/enterprise/2.15/admin/migrations/importing-data-from-third-party-version-control-systems": null, + "/enterprise/2.15/admin/migrations/importing-migration-data-to-github-enterprise-server": null, + "/enterprise/2.15/admin/migrations": null, + "/enterprise/2.15/admin/migrations/preparing-the-github-enterprise-server-source-instance": null, + "/enterprise/2.15/admin/migrations/preparing-the-githubcom-source-organization": null, + "/enterprise/2.15/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": null, + "/enterprise/2.15/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": null, + "/enterprise/2.15/admin/migrations/reviewing-migration-conflicts": null, + "/enterprise/2.15/admin/migrations/reviewing-migration-data": null, + "/enterprise/2.15/admin/user-management/about-global-webhooks": null, + "/enterprise/2.15/admin/user-management/adding-people-to-teams": null, + "/enterprise/2.15/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": null, + "/enterprise/2.15/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": null, + "/enterprise/2.15/admin/user-management/archiving-and-unarchiving-repositories": null, + "/enterprise/2.15/admin/user-management/auditing-ssh-keys": null, + "/enterprise/2.15/admin/user-management/auditing-users-across-your-instance": null, + "/enterprise/2.15/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": null, + "/enterprise/2.15/admin/user-management/basic-account-settings": null, + "/enterprise/2.15/admin/user-management/best-practices-for-user-security": null, + "/enterprise/2.15/admin/user-management/changing-authentication-methods": null, + "/enterprise/2.15/admin/user-management/configuring-email-for-notifications": null, + "/enterprise/2.15/admin/user-management/configuring-visibility-for-organization-membership": null, + "/enterprise/2.15/admin/user-management/creating-organizations": null, + "/enterprise/2.15/admin/user-management/creating-teams": null, + "/enterprise/2.15/admin/user-management/customizing-user-messages-on-your-instance": null, + "/enterprise/2.15/admin/user-management/disabling-unauthenticated-sign-ups": null, + "/enterprise/2.15/admin/user-management": null, + "/enterprise/2.15/admin/user-management/managing-dormant-users": null, + "/enterprise/2.15/admin/user-management/managing-global-webhooks": null, + "/enterprise/2.15/admin/user-management/organizations-and-teams": null, + "/enterprise/2.15/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": null, + "/enterprise/2.15/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": null, + "/enterprise/2.15/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": null, + "/enterprise/2.15/admin/user-management/preventing-users-from-creating-organizations": null, + "/enterprise/2.15/admin/user-management/preventing-users-from-deleting-organization-repositories": null, + "/enterprise/2.15/admin/user-management/promoting-or-demoting-a-site-administrator": null, + "/enterprise/2.15/admin/user-management/rebuilding-contributions-data": null, + "/enterprise/2.15/admin/user-management/removing-users-from-teams-and-organizations": null, + "/enterprise/2.15/admin/user-management/repositories": null, + "/enterprise/2.15/admin/user-management/requiring-two-factor-authentication-for-an-organization": null, + "/enterprise/2.15/admin/user-management/suspending-and-unsuspending-users": null, + "/enterprise/2.15/admin/user-management/user-security": null, + "/enterprise/2.15/admin/user-management/using-built-in-authentication": null, + "/enterprise/2.15/admin/user-management/using-cas": null, + "/enterprise/2.15/admin/user-management/using-ldap": null, + "/enterprise/2.15/admin/user-management/using-saml": null, + "/enterprise/2.15": null, + "/enterprise/2.15/user/articles/3d-file-viewer": null, + "/enterprise/2.15/user/articles/about-archiving-repositories": null, + "/enterprise/2.15/user/articles/about-automation-for-issues-and-pull-requests-with-query-parameters": null, + "/enterprise/2.15/user/articles/about-automation-for-project-boards": null, + "/enterprise/2.15/user/articles/about-branch-restrictions": null, + "/enterprise/2.15/user/articles/about-branches": null, + "/enterprise/2.15/user/articles/about-code-owners": null, + "/enterprise/2.15/user/articles/about-collaborative-development-models": null, + "/enterprise/2.15/user/articles/about-commit-signature-verification": null, + "/enterprise/2.15/user/articles/about-comparing-branches-in-pull-requests": null, + "/enterprise/2.15/user/articles/about-conversations-on-github": null, + "/enterprise/2.15/user/articles/about-duplicate-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/about-email-notifications-for-pushes-to-your-repository": null, + "/enterprise/2.15/user/articles/about-email-notifications": null, + "/enterprise/2.15/user/articles/about-forks": null, + "/enterprise/2.15/user/articles/about-git-large-file-storage": null, + "/enterprise/2.15/user/articles/about-git-rebase": null, + "/enterprise/2.15/user/articles/about-git-subtree-merges": null, + "/enterprise/2.15/user/articles/about-github-pages-and-jekyll": null, + "/enterprise/2.15/user/articles/about-github-pages": null, + "/enterprise/2.15/user/articles/about-issue-and-pull-request-templates": null, + "/enterprise/2.15/user/articles/about-issues": null, + "/enterprise/2.15/user/articles/about-jekyll-build-errors-for-github-pages-sites": null, + "/enterprise/2.15/user/articles/about-labels": null, + "/enterprise/2.15/user/articles/about-merge-conflicts": null, + "/enterprise/2.15/user/articles/about-merge-methods-on-github": null, + "/enterprise/2.15/user/articles/about-milestones": null, + "/enterprise/2.15/user/articles/about-notifications": null, + "/enterprise/2.15/user/articles/about-organization-membership": null, + "/enterprise/2.15/user/articles/about-organizations": null, + "/enterprise/2.15/user/articles/about-project-boards": null, + "/enterprise/2.15/user/articles/about-protected-branches": null, + "/enterprise/2.15/user/articles/about-pull-request-merges": null, + "/enterprise/2.15/user/articles/about-pull-request-reviews": null, + "/enterprise/2.15/user/articles/about-pull-requests": null, + "/enterprise/2.15/user/articles/about-readmes": null, + "/enterprise/2.15/user/articles/about-releases": null, + "/enterprise/2.15/user/articles/about-remote-repositories": null, + "/enterprise/2.15/user/articles/about-repositories": null, + "/enterprise/2.15/user/articles/about-repository-graphs": null, + "/enterprise/2.15/user/articles/about-repository-languages": null, + "/enterprise/2.15/user/articles/about-required-commit-signing": null, + "/enterprise/2.15/user/articles/about-required-reviews-for-pull-requests": null, + "/enterprise/2.15/user/articles/about-required-status-checks": null, + "/enterprise/2.15/user/articles/about-saved-replies": null, + "/enterprise/2.15/user/articles/about-searching-on-github": null, + "/enterprise/2.15/user/articles/about-ssh": null, + "/enterprise/2.15/user/articles/about-status-checks": null, + "/enterprise/2.15/user/articles/about-task-lists": null, + "/enterprise/2.15/user/articles/about-team-discussions": null, + "/enterprise/2.15/user/articles/about-teams": null, + "/enterprise/2.15/user/articles/about-two-factor-authentication": null, + "/enterprise/2.15/user/articles/about-web-notifications": null, + "/enterprise/2.15/user/articles/about-webhooks": null, + "/enterprise/2.15/user/articles/about-wikis": null, + "/enterprise/2.15/user/articles/about-writing-and-formatting-on-github": null, + "/enterprise/2.15/user/articles/about-your-organization-dashboard": null, + "/enterprise/2.15/user/articles/about-your-organizations-news-feed": null, + "/enterprise/2.15/user/articles/about-your-organizations-profile": null, + "/enterprise/2.15/user/articles/about-your-personal-dashboard": null, + "/enterprise/2.15/user/articles/about-your-profile": null, + "/enterprise/2.15/user/articles/access-permissions-on-github": null, + "/enterprise/2.15/user/articles/accessing-an-organization": null, + "/enterprise/2.15/user/articles/accessing-basic-repository-data": null, + "/enterprise/2.15/user/articles/accessing-github-using-two-factor-authentication": null, + "/enterprise/2.15/user/articles/accessing-your-notifications": null, + "/enterprise/2.15/user/articles/accessing-your-organizations-settings": null, + "/enterprise/2.15/user/articles/adding-a-file-to-a-repository-using-the-command-line": null, + "/enterprise/2.15/user/articles/adding-a-file-to-a-repository": null, + "/enterprise/2.15/user/articles/adding-a-license-to-a-repository": null, + "/enterprise/2.15/user/articles/adding-a-new-gpg-key-to-your-github-account": null, + "/enterprise/2.15/user/articles/adding-a-new-ssh-key-to-your-github-account": null, + "/enterprise/2.15/user/articles/adding-a-remote": null, + "/enterprise/2.15/user/articles/adding-a-theme-to-your-github-pages-site-using-jekyll": null, + "/enterprise/2.15/user/articles/adding-an-email-address-to-your-github-account": null, + "/enterprise/2.15/user/articles/adding-an-existing-project-to-github-using-the-command-line": null, + "/enterprise/2.15/user/articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization": null, + "/enterprise/2.15/user/articles/adding-content-to-your-github-pages-site-using-jekyll": null, + "/enterprise/2.15/user/articles/adding-issues-and-pull-requests-to-a-project-board": null, + "/enterprise/2.15/user/articles/adding-notes-to-a-project-board": null, + "/enterprise/2.15/user/articles/adding-or-editing-wiki-pages": null, + "/enterprise/2.15/user/articles/adding-organization-members-to-a-team": null, + "/enterprise/2.15/user/articles/adding-outside-collaborators-to-repositories-in-your-organization": null, + "/enterprise/2.15/user/articles/adding-people-to-your-organization": null, + "/enterprise/2.15/user/articles/adding-support-resources-to-your-project": null, + "/enterprise/2.15/user/articles/addressing-merge-conflicts": null, + "/enterprise/2.15/user/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.15/user/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization": null, + "/enterprise/2.15/user/articles/allowing-people-to-fork-private-repositories-in-your-organization": null, + "/enterprise/2.15/user/articles/analyzing-changes-to-a-repositorys-content": null, + "/enterprise/2.15/user/articles/applying-labels-to-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/approving-a-pull-request-with-required-reviews": null, + "/enterprise/2.15/user/articles/archiving-a-github-repository": null, + "/enterprise/2.15/user/articles/archiving-cards-on-a-project-board": null, + "/enterprise/2.15/user/articles/archiving-repositories": null, + "/enterprise/2.15/user/articles/assigning-issues-and-pull-requests-to-other-github-users": null, + "/enterprise/2.15/user/articles/associating-an-email-with-your-gpg-key": null, + "/enterprise/2.15/user/articles/associating-milestones-with-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/associating-text-editors-with-git": null, + "/enterprise/2.15/user/articles/authorizing-oauth-apps": null, + "/enterprise/2.15/user/articles/autolinked-references-and-urls": null, + "/enterprise/2.15/user/articles/backing-up-a-repository": null, + "/enterprise/2.15/user/articles/basic-writing-and-formatting-syntax": null, + "/enterprise/2.15/user/articles/be-social": null, + "/enterprise/2.15/user/articles/caching-your-github-password-in-git": null, + "/enterprise/2.15/user/articles/changing-a-commit-message": null, + "/enterprise/2.15/user/articles/changing-a-persons-role-to-owner": null, + "/enterprise/2.15/user/articles/changing-a-remotes-url": null, + "/enterprise/2.15/user/articles/changing-access-permissions-for-wikis": null, + "/enterprise/2.15/user/articles/changing-author-info": null, + "/enterprise/2.15/user/articles/changing-project-board-visibility": null, + "/enterprise/2.15/user/articles/changing-team-visibility": null, + "/enterprise/2.15/user/articles/changing-the-base-branch-of-a-pull-request": null, + "/enterprise/2.15/user/articles/changing-your-github-username": null, + "/enterprise/2.15/user/articles/changing-your-primary-email-address": null, + "/enterprise/2.15/user/articles/checking-for-existing-gpg-keys": null, + "/enterprise/2.15/user/articles/checking-for-existing-ssh-keys": null, + "/enterprise/2.15/user/articles/checking-out-pull-requests-locally": null, + "/enterprise/2.15/user/articles/checking-your-commit-and-tag-signature-verification-status": null, + "/enterprise/2.15/user/articles/choosing-the-delivery-method-for-your-notifications": null, + "/enterprise/2.15/user/articles/classifying-your-repository-with-topics": null, + "/enterprise/2.15/user/articles/cloning-a-repository-from-github": null, + "/enterprise/2.15/user/articles/cloning-a-repository": null, + "/enterprise/2.15/user/articles/closing-a-project-board": null, + "/enterprise/2.15/user/articles/closing-a-pull-request": null, + "/enterprise/2.15/user/articles/closing-issues-using-keywords": null, + "/enterprise/2.15/user/articles/collaborating-on-repositories-with-code-quality-features": null, + "/enterprise/2.15/user/articles/collaborating-with-groups-in-organizations": null, + "/enterprise/2.15/user/articles/collaborating-with-your-team": null, + "/enterprise/2.15/user/articles/collaboration-with-git-large-file-storage": null, + "/enterprise/2.15/user/articles/commenting-on-a-pull-request": null, + "/enterprise/2.15/user/articles/commit-branch-and-tag-labels": null, + "/enterprise/2.15/user/articles/commit-exists-on-github-but-not-in-my-local-clone": null, + "/enterprise/2.15/user/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.15/user/articles/comparing-commits-across-time": null, + "/enterprise/2.15/user/articles/conditions-for-large-files": null, + "/enterprise/2.15/user/articles/configuring-a-publishing-source-for-your-github-pages-site": null, + "/enterprise/2.15/user/articles/configuring-a-remote-for-a-fork": null, + "/enterprise/2.15/user/articles/configuring-automation-for-project-boards": null, + "/enterprise/2.15/user/articles/configuring-commit-rebasing-for-pull-requests": null, + "/enterprise/2.15/user/articles/configuring-commit-squashing-for-pull-requests": null, + "/enterprise/2.15/user/articles/configuring-git-large-file-storage": null, + "/enterprise/2.15/user/articles/configuring-git-to-handle-line-endings": null, + "/enterprise/2.15/user/articles/configuring-protected-branches": null, + "/enterprise/2.15/user/articles/configuring-pull-request-merges": null, + "/enterprise/2.15/user/articles/configuring-two-factor-authentication-recovery-methods": null, + "/enterprise/2.15/user/articles/configuring-two-factor-authentication": null, + "/enterprise/2.15/user/articles/connecting-to-github-with-ssh": null, + "/enterprise/2.15/user/articles/connecting-with-third-party-applications": null, + "/enterprise/2.15/user/articles/converting-a-user-into-an-organization": null, + "/enterprise/2.15/user/articles/converting-an-admin-team-to-improved-organization-permissions": null, + "/enterprise/2.15/user/articles/converting-an-organization-into-a-user": null, + "/enterprise/2.15/user/articles/converting-an-organization-member-to-an-outside-collaborator": null, + "/enterprise/2.15/user/articles/converting-an-outside-collaborator-to-an-organization-member": null, + "/enterprise/2.15/user/articles/converting-an-owners-team-to-improved-organization-permissions": null, + "/enterprise/2.15/user/articles/create-a-repo": null, + "/enterprise/2.15/user/articles/creating-a-commit-with-multiple-authors": null, + "/enterprise/2.15/user/articles/creating-a-custom-404-page-for-your-github-pages-site": null, + "/enterprise/2.15/user/articles/creating-a-footer-or-sidebar-for-your-wiki": null, + "/enterprise/2.15/user/articles/creating-a-github-pages-site-with-jekyll": null, + "/enterprise/2.15/user/articles/creating-a-github-pages-site": null, + "/enterprise/2.15/user/articles/creating-a-label": null, + "/enterprise/2.15/user/articles/creating-a-new-organization-from-scratch": null, + "/enterprise/2.15/user/articles/creating-a-new-repository": null, + "/enterprise/2.15/user/articles/creating-a-permanent-link-to-a-code-snippet": null, + "/enterprise/2.15/user/articles/creating-a-personal-access-token-for-the-command-line": null, + "/enterprise/2.15/user/articles/creating-a-project-board": null, + "/enterprise/2.15/user/articles/creating-a-pull-request-from-a-fork": null, + "/enterprise/2.15/user/articles/creating-a-pull-request-template-for-your-repository": null, + "/enterprise/2.15/user/articles/creating-a-pull-request": null, + "/enterprise/2.15/user/articles/creating-a-repository-on-github": null, + "/enterprise/2.15/user/articles/creating-a-saved-reply": null, + "/enterprise/2.15/user/articles/creating-a-strong-password": null, + "/enterprise/2.15/user/articles/creating-a-team-discussion": null, + "/enterprise/2.15/user/articles/creating-a-team": null, + "/enterprise/2.15/user/articles/creating-an-issue": null, + "/enterprise/2.15/user/articles/creating-an-issues-only-repository": null, + "/enterprise/2.15/user/articles/creating-and-deleting-branches-within-your-repository": null, + "/enterprise/2.15/user/articles/creating-and-editing-commits": null, + "/enterprise/2.15/user/articles/creating-and-editing-milestones-for-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/creating-and-highlighting-code-blocks": null, + "/enterprise/2.15/user/articles/creating-gists": null, + "/enterprise/2.15/user/articles/creating-issue-templates-for-your-repository": null, + "/enterprise/2.15/user/articles/creating-new-files": null, + "/enterprise/2.15/user/articles/creating-releases": null, + "/enterprise/2.15/user/articles/customizing-how-changed-files-appear-on-github": null, + "/enterprise/2.15/user/articles/customizing-your-profile": null, + "/enterprise/2.15/user/articles/dealing-with-non-fast-forward-errors": null, + "/enterprise/2.15/user/articles/defining-the-mergeability-of-pull-requests": null, + "/enterprise/2.15/user/articles/deleting-a-label": null, + "/enterprise/2.15/user/articles/deleting-a-project-board": null, + "/enterprise/2.15/user/articles/deleting-a-repository": null, + "/enterprise/2.15/user/articles/deleting-a-saved-reply": null, + "/enterprise/2.15/user/articles/deleting-a-team": null, + "/enterprise/2.15/user/articles/deleting-an-organization-account": null, + "/enterprise/2.15/user/articles/deleting-and-restoring-branches-in-a-pull-request": null, + "/enterprise/2.15/user/articles/deleting-files": null, + "/enterprise/2.15/user/articles/deleting-your-user-account": null, + "/enterprise/2.15/user/articles/differences-between-commit-views": null, + "/enterprise/2.15/user/articles/disabling-issues": null, + "/enterprise/2.15/user/articles/disabling-project-boards-in-a-repository": null, + "/enterprise/2.15/user/articles/disabling-project-boards-in-your-organization": null, + "/enterprise/2.15/user/articles/disabling-team-discussions-for-your-organization": null, + "/enterprise/2.15/user/articles/disabling-two-factor-authentication-for-your-personal-account": null, + "/enterprise/2.15/user/articles/disabling-wikis": null, + "/enterprise/2.15/user/articles/dismissing-a-pull-request-review": null, + "/enterprise/2.15/user/articles/distributing-large-binaries": null, + "/enterprise/2.15/user/articles/documenting-your-project-with-wikis": null, + "/enterprise/2.15/user/articles/duplicating-a-repository": null, + "/enterprise/2.15/user/articles/editing-a-label": null, + "/enterprise/2.15/user/articles/editing-a-project-board": null, + "/enterprise/2.15/user/articles/editing-a-saved-reply": null, + "/enterprise/2.15/user/articles/editing-and-deleting-releases": null, + "/enterprise/2.15/user/articles/editing-and-sharing-content-with-gists": null, + "/enterprise/2.15/user/articles/editing-files-in-another-users-repository": null, + "/enterprise/2.15/user/articles/editing-files-in-your-repository": null, + "/enterprise/2.15/user/articles/editing-or-deleting-a-team-discussion": null, + "/enterprise/2.15/user/articles/editing-wiki-content": null, + "/enterprise/2.15/user/articles/enabling-anonymous-git-read-access-for-a-repository": null, + "/enterprise/2.15/user/articles/enabling-branch-restrictions": null, + "/enterprise/2.15/user/articles/enabling-githubcom-repository-search-in-github-enterprise-server": null, + "/enterprise/2.15/user/articles/enabling-required-commit-signing": null, + "/enterprise/2.15/user/articles/enabling-required-reviews-for-pull-requests": null, + "/enterprise/2.15/user/articles/enabling-required-status-checks": null, + "/enterprise/2.15/user/articles/error-agent-admitted-failure-to-sign": null, + "/enterprise/2.15/user/articles/error-bad-file-number": null, + "/enterprise/2.15/user/articles/error-key-already-in-use": null, + "/enterprise/2.15/user/articles/error-permission-denied-publickey": null, + "/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-other-user": null, + "/enterprise/2.15/user/articles/error-permission-to-userrepo-denied-to-userother-repo": null, + "/enterprise/2.15/user/articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": null, + "/enterprise/2.15/user/articles/error-repository-not-found": null, + "/enterprise/2.15/user/articles/error-ssh-add-illegal-option----k": null, + "/enterprise/2.15/user/articles/error-were-doing-an-ssh-key-audit": null, + "/enterprise/2.15/user/articles/exploring-projects-on-github": null, + "/enterprise/2.15/user/articles/file-attachments-on-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/filtering-cards-on-a-project-board": null, + "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-assignees": null, + "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-labels": null, + "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests-by-milestone": null, + "/enterprise/2.15/user/articles/filtering-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/filtering-pull-requests-by-review-status": null, + "/enterprise/2.15/user/articles/finding-changed-methods-and-functions-in-a-pull-request": null, + "/enterprise/2.15/user/articles/finding-files-on-github": null, + "/enterprise/2.15/user/articles/finding-information-in-a-repository": null, + "/enterprise/2.15/user/articles/following-people": null, + "/enterprise/2.15/user/articles/fork-a-repo": null, + "/enterprise/2.15/user/articles/forking-and-cloning-gists": null, + "/enterprise/2.15/user/articles/generating-a-new-gpg-key": null, + "/enterprise/2.15/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": null, + "/enterprise/2.15/user/articles/getting-changes-from-a-remote-repository": null, + "/enterprise/2.15/user/articles/getting-permanent-links-to-files": null, + "/enterprise/2.15/user/articles/getting-started-with-git-and-github": null, + "/enterprise/2.15/user/articles/getting-started-with-github-pages": null, + "/enterprise/2.15/user/articles/getting-started-with-notifications": null, + "/enterprise/2.15/user/articles/getting-started-with-searching-on-github": null, + "/enterprise/2.15/user/articles/getting-started-with-the-api": null, + "/enterprise/2.15/user/articles/getting-started-with-writing-and-formatting-on-github": null, + "/enterprise/2.15/user/articles/getting-the-download-count-for-your-releases": null, + "/enterprise/2.15/user/articles/git-and-github-learning-resources": null, + "/enterprise/2.15/user/articles/git-automation-with-oauth-tokens": null, + "/enterprise/2.15/user/articles/git-cheatsheet": null, + "/enterprise/2.15/user/articles/git-workflows": null, + "/enterprise/2.15/user/articles/github-flow": null, + "/enterprise/2.15/user/articles/github-glossary": null, + "/enterprise/2.15/user/articles/giving-team-maintainer-permissions-to-an-organization-member": null, + "/enterprise/2.15/user/articles/https-cloning-errors": null, + "/enterprise/2.15/user/articles/ignoring-files": null, + "/enterprise/2.15/user/articles/importing-a-git-repository-using-the-command-line": null, + "/enterprise/2.15/user/articles/importing-source-code-to-github": null, + "/enterprise/2.15/user/articles/incorporating-changes-from-a-pull-request": null, + "/enterprise/2.15/user/articles/initializing-an-empty-repository-with-a-readme": null, + "/enterprise/2.15/user/articles/installing-git-large-file-storage": null, + "/enterprise/2.15/user/articles/integrating-jira-with-your-organization-project-board": null, + "/enterprise/2.15/user/articles/integrating-jira-with-your-personal-projects": null, + "/enterprise/2.15/user/articles/inviting-collaborators-to-a-personal-repository": null, + "/enterprise/2.15/user/articles/keeping-your-account-and-data-secure": null, + "/enterprise/2.15/user/articles/keeping-your-organization-secure": null, + "/enterprise/2.15/user/articles/keyboard-shortcuts": null, + "/enterprise/2.15/user/articles/labeling-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/learning-about-git": null, + "/enterprise/2.15/user/articles/learning-about-github": null, + "/enterprise/2.15/user/articles/licensing-a-repository": null, + "/enterprise/2.15/user/articles/limits-for-viewing-content-and-diffs-in-a-repository": null, + "/enterprise/2.15/user/articles/linking-a-repository-to-a-project-board": null, + "/enterprise/2.15/user/articles/linking-to-releases": null, + "/enterprise/2.15/user/articles/listing-the-forks-of-a-repository": null, + "/enterprise/2.15/user/articles/listing-the-repositories-youre-watching": null, + "/enterprise/2.15/user/articles/locking-conversations": null, + "/enterprise/2.15/user/articles/managing-access-to-a-project-board-for-organization-members": null, + "/enterprise/2.15/user/articles/managing-access-to-your-organizations-project-boards": null, + "/enterprise/2.15/user/articles/managing-access-to-your-organizations-repositories": null, + "/enterprise/2.15/user/articles/managing-access-to-your-personal-repositories": null, + "/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-project-board": null, + "/enterprise/2.15/user/articles/managing-an-individuals-access-to-an-organization-repository": null, + "/enterprise/2.15/user/articles/managing-branches-in-your-repository": null, + "/enterprise/2.15/user/articles/managing-commit-signature-verification": null, + "/enterprise/2.15/user/articles/managing-contribution-graphs-on-your-profile": null, + "/enterprise/2.15/user/articles/managing-disruptive-comments": null, + "/enterprise/2.15/user/articles/managing-email-preferences": null, + "/enterprise/2.15/user/articles/managing-files-on-github": null, + "/enterprise/2.15/user/articles/managing-files-using-the-command-line": null, + "/enterprise/2.15/user/articles/managing-membership-in-your-organization": null, + "/enterprise/2.15/user/articles/managing-organization-settings": null, + "/enterprise/2.15/user/articles/managing-peoples-access-to-your-organization-with-roles": null, + "/enterprise/2.15/user/articles/managing-project-boards": null, + "/enterprise/2.15/user/articles/managing-releases-in-a-repository": null, + "/enterprise/2.15/user/articles/managing-remote-repositories": null, + "/enterprise/2.15/user/articles/managing-repository-settings": null, + "/enterprise/2.15/user/articles/managing-team-access-to-an-organization-project-board": null, + "/enterprise/2.15/user/articles/managing-team-access-to-an-organization-repository": null, + "/enterprise/2.15/user/articles/managing-user-account-settings": null, + "/enterprise/2.15/user/articles/managing-your-membership-in-organizations": null, + "/enterprise/2.15/user/articles/managing-your-notifications": null, + "/enterprise/2.15/user/articles/managing-your-work-with-issues": null, + "/enterprise/2.15/user/articles/manually-creating-a-single-issue-template-for-your-repository": null, + "/enterprise/2.15/user/articles/mapping-geojson-files-on-github": null, + "/enterprise/2.15/user/articles/marking-notifications-as-read": null, + "/enterprise/2.15/user/articles/merging-a-pull-request": null, + "/enterprise/2.15/user/articles/merging-an-upstream-repository-into-your-fork": null, + "/enterprise/2.15/user/articles/migrating-admin-teams-to-improved-organization-permissions": null, + "/enterprise/2.15/user/articles/migrating-to-improved-organization-permissions": null, + "/enterprise/2.15/user/articles/moderating-comments-and-conversations": null, + "/enterprise/2.15/user/articles/moving-a-file-in-your-repository-to-git-large-file-storage": null, + "/enterprise/2.15/user/articles/moving-a-file-to-a-new-location-using-the-command-line": null, + "/enterprise/2.15/user/articles/moving-a-file-to-a-new-location": null, + "/enterprise/2.15/user/articles/moving-a-team-in-your-organizations-hierarchy": null, + "/enterprise/2.15/user/articles/opening-an-issue-from-code": null, + "/enterprise/2.15/user/articles/organizing-information-with-tables": null, + "/enterprise/2.15/user/articles/organizing-members-into-teams": null, + "/enterprise/2.15/user/articles/permission-levels-for-a-user-account-repository": null, + "/enterprise/2.15/user/articles/permission-levels-for-an-organization": null, + "/enterprise/2.15/user/articles/personalizing-your-profile": null, + "/enterprise/2.15/user/articles/pinning-a-team-discussion": null, + "/enterprise/2.15/user/articles/pinning-items-to-your-profile": null, + "/enterprise/2.15/user/articles/preparing-to-require-two-factor-authentication-in-your-organization": null, + "/enterprise/2.15/user/articles/preventing-unauthorized-access": null, + "/enterprise/2.15/user/articles/project-board-permissions-for-an-organization": null, + "/enterprise/2.15/user/articles/proposing-changes-to-your-work-with-pull-requests": null, + "/enterprise/2.15/user/articles/publicizing-or-hiding-organization-membership": null, + "/enterprise/2.15/user/articles/publicizing-or-hiding-your-private-contributions-on-your-profile": null, + "/enterprise/2.15/user/articles/pushing-commits-to-a-remote-repository": null, + "/enterprise/2.15/user/articles/recovering-your-account-if-you-lose-your-2fa-credentials": null, + "/enterprise/2.15/user/articles/recovering-your-ssh-key-passphrase": null, + "/enterprise/2.15/user/articles/reinstating-a-former-member-of-your-organization": null, + "/enterprise/2.15/user/articles/reinstating-a-former-outside-collaborators-access-to-your-organization": null, + "/enterprise/2.15/user/articles/remembering-your-github-username-or-email": null, + "/enterprise/2.15/user/articles/removing-a-collaborator-from-a-personal-repository": null, + "/enterprise/2.15/user/articles/removing-a-member-from-your-organization": null, + "/enterprise/2.15/user/articles/removing-a-remote": null, + "/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-project-board": null, + "/enterprise/2.15/user/articles/removing-an-outside-collaborator-from-an-organization-repository": null, + "/enterprise/2.15/user/articles/removing-files-from-a-repositorys-history": null, + "/enterprise/2.15/user/articles/removing-files-from-git-large-file-storage": null, + "/enterprise/2.15/user/articles/removing-organization-members-from-a-team": null, + "/enterprise/2.15/user/articles/removing-sensitive-data-from-a-repository": null, + "/enterprise/2.15/user/articles/removing-yourself-from-a-collaborators-repository": null, + "/enterprise/2.15/user/articles/removing-yourself-from-an-organization": null, + "/enterprise/2.15/user/articles/renaming-a-file-using-the-command-line": null, + "/enterprise/2.15/user/articles/renaming-a-file": null, + "/enterprise/2.15/user/articles/renaming-a-remote": null, + "/enterprise/2.15/user/articles/renaming-a-repository": null, + "/enterprise/2.15/user/articles/renaming-a-team": null, + "/enterprise/2.15/user/articles/renaming-an-organization": null, + "/enterprise/2.15/user/articles/rendering-and-diffing-images": null, + "/enterprise/2.15/user/articles/rendering-csv-and-tsv-data": null, + "/enterprise/2.15/user/articles/rendering-differences-in-prose-documents": null, + "/enterprise/2.15/user/articles/rendering-pdf-documents": null, + "/enterprise/2.15/user/articles/reopening-a-closed-project-board": null, + "/enterprise/2.15/user/articles/repository-permission-levels-for-an-organization": null, + "/enterprise/2.15/user/articles/requesting-a-pull-request-review": null, + "/enterprise/2.15/user/articles/requesting-to-add-a-child-team": null, + "/enterprise/2.15/user/articles/requesting-to-add-or-change-a-parent-team": null, + "/enterprise/2.15/user/articles/requiring-two-factor-authentication-in-your-organization": null, + "/enterprise/2.15/user/articles/resolving-a-merge-conflict-on-github": null, + "/enterprise/2.15/user/articles/resolving-a-merge-conflict-using-the-command-line": null, + "/enterprise/2.15/user/articles/resolving-git-large-file-storage-upload-failures": null, + "/enterprise/2.15/user/articles/resolving-merge-conflicts-after-a-git-rebase": null, + "/enterprise/2.15/user/articles/restricting-repository-creation-in-your-organization": null, + "/enterprise/2.15/user/articles/restricting-repository-visibility-changes-in-your-organization": null, + "/enterprise/2.15/user/articles/reverting-a-pull-request": null, + "/enterprise/2.15/user/articles/reviewing-changes-in-pull-requests": null, + "/enterprise/2.15/user/articles/reviewing-proposed-changes-in-a-pull-request": null, + "/enterprise/2.15/user/articles/reviewing-the-audit-log-for-your-organization": null, + "/enterprise/2.15/user/articles/reviewing-your-authorized-applications-oauth": null, + "/enterprise/2.15/user/articles/reviewing-your-authorized-integrations": null, + "/enterprise/2.15/user/articles/reviewing-your-deploy-keys": null, + "/enterprise/2.15/user/articles/reviewing-your-organizations-installed-integrations": null, + "/enterprise/2.15/user/articles/reviewing-your-security-log": null, + "/enterprise/2.15/user/articles/reviewing-your-ssh-keys": null, + "/enterprise/2.15/user/articles/saving-repositories-with-stars": null, + "/enterprise/2.15/user/articles/searching-code": null, + "/enterprise/2.15/user/articles/searching-commits": null, + "/enterprise/2.15/user/articles/searching-for-repositories": null, + "/enterprise/2.15/user/articles/searching-in-forks": null, + "/enterprise/2.15/user/articles/searching-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/searching-on-github": null, + "/enterprise/2.15/user/articles/searching-topics": null, + "/enterprise/2.15/user/articles/searching-users": null, + "/enterprise/2.15/user/articles/searching-wikis": null, + "/enterprise/2.15/user/articles/securing-your-account-with-two-factor-authentication-2fa": null, + "/enterprise/2.15/user/articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": null, + "/enterprise/2.15/user/articles/set-up-git": null, + "/enterprise/2.15/user/articles/setting-a-backup-email-address": null, + "/enterprise/2.15/user/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": null, + "/enterprise/2.15/user/articles/setting-guidelines-for-repository-contributors": null, + "/enterprise/2.15/user/articles/setting-permissions-for-deleting-or-transferring-repositories": null, + "/enterprise/2.15/user/articles/setting-repository-visibility": null, + "/enterprise/2.15/user/articles/setting-the-default-branch": null, + "/enterprise/2.15/user/articles/setting-up-a-github-pages-site-with-jekyll": null, + "/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-cloud": null, + "/enterprise/2.15/user/articles/setting-up-a-trial-of-github-enterprise-server": null, + "/enterprise/2.15/user/articles/setting-up-your-project-for-healthy-contributions": null, + "/enterprise/2.15/user/articles/setting-your-commit-email-address": null, + "/enterprise/2.15/user/articles/setting-your-teams-profile-picture": null, + "/enterprise/2.15/user/articles/setting-your-username-in-git": null, + "/enterprise/2.15/user/articles/sharing-filters": null, + "/enterprise/2.15/user/articles/showing-an-overview-of-your-activity-on-your-profile": null, + "/enterprise/2.15/user/articles/signing-commits": null, + "/enterprise/2.15/user/articles/signing-tags": null, + "/enterprise/2.15/user/articles/signing-up-for-github": null, + "/enterprise/2.15/user/articles/sorting-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/sorting-search-results": null, + "/enterprise/2.15/user/articles/source-code-migration-tools": null, + "/enterprise/2.15/user/articles/splitting-a-subfolder-out-into-a-new-repository": null, + "/enterprise/2.15/user/articles/subscribing-to-and-unsubscribing-from-notifications": null, + "/enterprise/2.15/user/articles/subversion-properties-supported-by-github": null, + "/enterprise/2.15/user/articles/sudo-mode": null, + "/enterprise/2.15/user/articles/support-for-subversion-clients": null, + "/enterprise/2.15/user/articles/supported-browsers": null, + "/enterprise/2.15/user/articles/syncing-a-fork": null, + "/enterprise/2.15/user/articles/telling-git-about-your-signing-key": null, + "/enterprise/2.15/user/articles/testing-your-github-pages-site-locally-with-jekyll": null, + "/enterprise/2.15/user/articles/testing-your-ssh-connection": null, + "/enterprise/2.15/user/articles/tracking-changes-in-a-comment": null, + "/enterprise/2.15/user/articles/tracking-changes-in-a-file": null, + "/enterprise/2.15/user/articles/tracking-progress-on-your-project-board": null, + "/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-milestones": null, + "/enterprise/2.15/user/articles/tracking-the-progress-of-your-work-with-project-boards": null, + "/enterprise/2.15/user/articles/transferring-a-repository": null, + "/enterprise/2.15/user/articles/transferring-organization-ownership": null, + "/enterprise/2.15/user/articles/troubleshooting-commit-signature-verification": null, + "/enterprise/2.15/user/articles/troubleshooting-commits-on-your-timeline": null, + "/enterprise/2.15/user/articles/troubleshooting-commits": null, + "/enterprise/2.15/user/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites": null, + "/enterprise/2.15/user/articles/troubleshooting-search-queries": null, + "/enterprise/2.15/user/articles/troubleshooting-ssh": null, + "/enterprise/2.15/user/articles/types-of-github-accounts": null, + "/enterprise/2.15/user/articles/types-of-required-status-checks": null, + "/enterprise/2.15/user/articles/understanding-connections-between-repositories": null, + "/enterprise/2.15/user/articles/understanding-the-search-syntax": null, + "/enterprise/2.15/user/articles/unpublishing-a-github-pages-site": null, + "/enterprise/2.15/user/articles/updating-an-expired-gpg-key": null, + "/enterprise/2.15/user/articles/updating-credentials-from-the-osx-keychain": null, + "/enterprise/2.15/user/articles/updating-your-github-access-credentials": null, + "/enterprise/2.15/user/articles/using-a-verified-email-address-in-your-gpg-key": null, + "/enterprise/2.15/user/articles/using-advanced-git-commands": null, + "/enterprise/2.15/user/articles/using-common-git-commands": null, + "/enterprise/2.15/user/articles/using-git-rebase-on-the-command-line": null, + "/enterprise/2.15/user/articles/using-github": null, + "/enterprise/2.15/user/articles/using-issue-and-pull-request-templates": null, + "/enterprise/2.15/user/articles/using-saved-replies": null, + "/enterprise/2.15/user/articles/using-search-to-filter-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/versioning-large-files": null, + "/enterprise/2.15/user/articles/viewing-a-projects-contributors": null, + "/enterprise/2.15/user/articles/viewing-a-pull-request-review": null, + "/enterprise/2.15/user/articles/viewing-a-repositorys-network": null, + "/enterprise/2.15/user/articles/viewing-a-summary-of-repository-activity": null, + "/enterprise/2.15/user/articles/viewing-a-wikis-history-of-changes": null, + "/enterprise/2.15/user/articles/viewing-all-of-your-issues-and-pull-requests": null, + "/enterprise/2.15/user/articles/viewing-and-comparing-commits": null, + "/enterprise/2.15/user/articles/viewing-branches-in-your-repository": null, + "/enterprise/2.15/user/articles/viewing-contributions-on-your-profile": null, + "/enterprise/2.15/user/articles/viewing-peoples-roles-in-an-organization": null, + "/enterprise/2.15/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled": null, + "/enterprise/2.15/user/articles/viewing-your-milestones-progress": null, + "/enterprise/2.15/user/articles/viewing-your-repositorys-tags": null, + "/enterprise/2.15/user/articles/visualizing-additions-and-deletions-to-content-in-a-repository": null, + "/enterprise/2.15/user/articles/visualizing-commits-in-a-repository": null, + "/enterprise/2.15/user/articles/watching-and-unwatching-repositories": null, + "/enterprise/2.15/user/articles/watching-and-unwatching-team-discussions": null, + "/enterprise/2.15/user/articles/what-are-the-differences-between-subversion-and-git": null, + "/enterprise/2.15/user/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": null, + "/enterprise/2.15/user/articles/which-remote-url-should-i-use": null, + "/enterprise/2.15/user/articles/why-are-my-commits-in-the-wrong-order": null, + "/enterprise/2.15/user/articles/why-are-my-commits-linked-to-the-wrong-user": null, + "/enterprise/2.15/user/articles/why-are-my-contributions-not-showing-up-on-my-profile": null, + "/enterprise/2.15/user/articles/why-is-git-always-asking-for-my-password": null, + "/enterprise/2.15/user/articles/working-with-advanced-formatting": null, + "/enterprise/2.15/user/articles/working-with-forks": null, + "/enterprise/2.15/user/articles/working-with-jupyter-notebook-files-on-github": null, + "/enterprise/2.15/user/articles/working-with-large-files": null, + "/enterprise/2.15/user/articles/working-with-non-code-files": null, + "/enterprise/2.15/user/articles/working-with-pre-receive-hooks": null, + "/enterprise/2.15/user/articles/working-with-saved-replies": null, + "/enterprise/2.15/user/articles/working-with-ssh-key-passphrases": null, + "/enterprise/2.15/user/articles/working-with-subversion-on-github": null, + "/enterprise/2.15/user/categories/administering-a-repository": null, + "/enterprise/2.15/user/categories/authenticating-to-github": null, + "/enterprise/2.15/user/categories/building-a-strong-community": null, + "/enterprise/2.15/user/categories/collaborating-with-issues-and-pull-requests": null, + "/enterprise/2.15/user/categories/committing-changes-to-your-project": null, + "/enterprise/2.15/user/categories/creating-cloning-and-archiving-repositories": null, + "/enterprise/2.15/user/categories/extending-github": null, + "/enterprise/2.15/user/categories/getting-started-with-github": null, + "/enterprise/2.15/user/categories/importing-your-projects-to-github": null, + "/enterprise/2.15/user/categories/managing-files-in-a-repository": null, + "/enterprise/2.15/user/categories/managing-large-files": null, + "/enterprise/2.15/user/categories/managing-your-work-on-github": null, + "/enterprise/2.15/user/categories/receiving-notifications-about-activity-on-github": null, + "/enterprise/2.15/user/categories/searching-for-information-on-github": null, + "/enterprise/2.15/user/categories/setting-up-and-managing-organizations-and-teams": null, + "/enterprise/2.15/user/categories/setting-up-and-managing-your-github-profile": null, + "/enterprise/2.15/user/categories/setting-up-and-managing-your-github-user-account": null, + "/enterprise/2.15/user/categories/using-git": null, + "/enterprise/2.15/user/categories/visualizing-repository-data-with-graphs": null, + "/enterprise/2.15/user/categories/working-with-github-pages": null, + "/enterprise/2.15/user/categories/writing-on-github": null, + "/enterprise/2.15/user": null, + "/enterprise/2.16/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", + "/enterprise/2.16/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", + "/enterprise/2.16/admin/guides/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": "/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise", + "/enterprise/2.16/admin/guides/articles/using-github-task-runner": "/enterprise/2.16/admin/articles/using-github-task-runner", + "/enterprise/2.16/admin/guides/clustering/about-cluster-nodes": "/enterprise/2.16/admin/clustering/about-cluster-nodes", + "/enterprise/2.16/admin/guides/clustering/cluster-network-configuration": "/enterprise/2.16/admin/clustering/cluster-network-configuration", + "/enterprise/2.16/admin/guides/clustering/clustering-overview": "/enterprise/2.16/admin/clustering/clustering-overview", + "/enterprise/2.16/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha", + "/enterprise/2.16/admin/guides/clustering/evacuating-a-cluster-node": "/enterprise/2.16/admin/clustering/evacuating-a-cluster-node", + "/enterprise/2.16/admin/guides/clustering": "/enterprise/2.16/admin/clustering", + "/enterprise/2.16/admin/guides/clustering/initializing-the-cluster": "/enterprise/2.16/admin/clustering/initializing-the-cluster", + "/enterprise/2.16/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster", + "/enterprise/2.16/admin/guides/clustering/monitoring-cluster-nodes": "/enterprise/2.16/admin/clustering/monitoring-cluster-nodes", + "/enterprise/2.16/admin/guides/clustering/replacing-a-cluster-node": "/enterprise/2.16/admin/clustering/replacing-a-cluster-node", + "/enterprise/2.16/admin/guides/clustering/setting-up-the-cluster-instances": "/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances", + "/enterprise/2.16/admin/guides/clustering/upgrading-a-cluster": "/enterprise/2.16/admin/clustering/upgrading-a-cluster", + "/enterprise/2.16/admin/guides/developer-workflow/about-pre-receive-hooks": "/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks", + "/enterprise/2.16/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks", + "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance", + "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository", + "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", + "/enterprise/2.16/admin/guides/developer-workflow/blocking-force-pushes": "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes", + "/enterprise/2.16/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", + "/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins", + "/enterprise/2.16/admin/guides/developer-workflow/continuous-integration-using-travis-ci": "/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci", + "/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment", + "/enterprise/2.16/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script", + "/enterprise/2.16/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations", + "/enterprise/2.16/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions", + "/enterprise/2.16/admin/guides/developer-workflow": "/enterprise/2.16/admin/developer-workflow", + "/enterprise/2.16/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", + "/enterprise/2.16/admin/guides/developer-workflow/managing-projects-using-jira": "/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira", + "/enterprise/2.16/admin/guides/developer-workflow/troubleshooting-service-hooks": "/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks", + "/enterprise/2.16/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", + "/enterprise/2.16/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration", + "/enterprise/2.16/admin/guides/enterprise-support/about-github-enterprise-support": "/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support", + "/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", + "/enterprise/2.16/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise", + "/enterprise/2.16/admin/guides/enterprise-support/about-support-for-advanced-security": "/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security", + "/enterprise/2.16/admin/guides/enterprise-support": "/enterprise/2.16/admin/enterprise-support", + "/enterprise/2.16/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket", + "/enterprise/2.16/admin/guides/enterprise-support/providing-data-to-github-support": "/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support", + "/enterprise/2.16/admin/guides/enterprise-support/reaching-github-support": "/enterprise/2.16/admin/enterprise-support/reaching-github-support", + "/enterprise/2.16/admin/guides/enterprise-support/receiving-help-from-github-support": "/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support", + "/enterprise/2.16/admin/guides/enterprise-support/submitting-a-ticket": "/enterprise/2.16/admin/enterprise-support/submitting-a-ticket", + "/enterprise/2.16/admin/guides": "/enterprise/2.16/admin", + "/enterprise/2.16/admin/guides/installation/about-geo-replication": "/enterprise/2.16/admin/installation/about-geo-replication", + "/enterprise/2.16/admin/guides/installation/about-high-availability-configuration": "/enterprise/2.16/admin/installation/about-high-availability-configuration", + "/enterprise/2.16/admin/guides/installation/about-the-github-enterprise-server-api": "/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api", + "/enterprise/2.16/admin/guides/installation/accessing-the-administrative-shell-ssh": "/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh", + "/enterprise/2.16/admin/guides/installation/accessing-the-management-console": "/enterprise/2.16/admin/installation/accessing-the-management-console", + "/enterprise/2.16/admin/guides/installation/accessing-the-monitor-dashboard": "/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard", + "/enterprise/2.16/admin/guides/installation/activity-dashboard": "/enterprise/2.16/admin/installation/activity-dashboard", + "/enterprise/2.16/admin/guides/installation/audit-logging": "/enterprise/2.16/admin/installation/audit-logging", + "/enterprise/2.16/admin/guides/installation/audited-actions": "/enterprise/2.16/admin/installation/audited-actions", + "/enterprise/2.16/admin/guides/installation/command-line-utilities": "/enterprise/2.16/admin/installation/command-line-utilities", + "/enterprise/2.16/admin/guides/installation/configuring-a-hostname": "/enterprise/2.16/admin/installation/configuring-a-hostname", + "/enterprise/2.16/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server", + "/enterprise/2.16/admin/guides/installation/configuring-applications": "/enterprise/2.16/admin/installation/configuring-applications", + "/enterprise/2.16/admin/guides/installation/configuring-backups-on-your-appliance": "/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance", + "/enterprise/2.16/admin/guides/installation/configuring-built-in-firewall-rules": "/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules", + "/enterprise/2.16/admin/guides/installation/configuring-collectd": "/enterprise/2.16/admin/installation/configuring-collectd", + "/enterprise/2.16/admin/guides/installation/configuring-dns-nameservers": "/enterprise/2.16/admin/installation/configuring-dns-nameservers", + "/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", + "/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", + "/enterprise/2.16/admin/guides/installation/configuring-git-large-file-storage": "/enterprise/2.16/admin/installation/configuring-git-large-file-storage", + "/enterprise/2.16/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability", + "/enterprise/2.16/admin/guides/installation/configuring-github-pages-on-your-appliance": "/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance", + "/enterprise/2.16/admin/guides/installation/configuring-rate-limits": "/enterprise/2.16/admin/installation/configuring-rate-limits", + "/enterprise/2.16/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", + "/enterprise/2.16/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance", + "/enterprise/2.16/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", + "/enterprise/2.16/admin/guides/installation/configuring-time-synchronization": "/enterprise/2.16/admin/installation/configuring-time-synchronization", + "/enterprise/2.16/admin/guides/installation/configuring-tls": "/enterprise/2.16/admin/installation/configuring-tls", + "/enterprise/2.16/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings", + "/enterprise/2.16/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", + "/enterprise/2.16/admin/guides/installation/creating-a-high-availability-replica": "/enterprise/2.16/admin/installation/creating-a-high-availability-replica", + "/enterprise/2.16/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", + "/enterprise/2.16/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", + "/enterprise/2.16/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode", + "/enterprise/2.16/admin/guides/installation/enabling-automatic-update-checks": "/enterprise/2.16/admin/installation/enabling-automatic-update-checks", + "/enterprise/2.16/admin/guides/installation/enabling-private-mode": "/enterprise/2.16/admin/installation/enabling-private-mode", + "/enterprise/2.16/admin/guides/installation/enabling-subdomain-isolation": "/enterprise/2.16/admin/installation/enabling-subdomain-isolation", + "/enterprise/2.16/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", + "/enterprise/2.16/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", + "/enterprise/2.16/admin/guides/installation/increasing-cpu-or-memory-resources": "/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources", + "/enterprise/2.16/admin/guides/installation/increasing-storage-capacity": "/enterprise/2.16/admin/installation/increasing-storage-capacity", + "/enterprise/2.16/admin/guides/installation": "/enterprise/2.16/admin/installation", + "/enterprise/2.16/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-aws": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-azure": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware", + "/enterprise/2.16/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver", + "/enterprise/2.16/admin/guides/installation/log-forwarding": "/enterprise/2.16/admin/installation/log-forwarding", + "/enterprise/2.16/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", + "/enterprise/2.16/admin/guides/installation/managing-your-github-enterprise-server-license": "/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license", + "/enterprise/2.16/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", + "/enterprise/2.16/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123", + "/enterprise/2.16/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server", + "/enterprise/2.16/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", + "/enterprise/2.16/admin/guides/installation/monitoring-using-snmp": "/enterprise/2.16/admin/installation/monitoring-using-snmp", + "/enterprise/2.16/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance", + "/enterprise/2.16/admin/guides/installation/network-ports": "/enterprise/2.16/admin/installation/network-ports", + "/enterprise/2.16/admin/guides/installation/recommended-alert-thresholds": "/enterprise/2.16/admin/installation/recommended-alert-thresholds", + "/enterprise/2.16/admin/guides/installation/recovering-a-high-availability-configuration": "/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration", + "/enterprise/2.16/admin/guides/installation/removing-a-high-availability-replica": "/enterprise/2.16/admin/installation/removing-a-high-availability-replica", + "/enterprise/2.16/admin/guides/installation/searching-the-audit-log": "/enterprise/2.16/admin/installation/searching-the-audit-log", + "/enterprise/2.16/admin/guides/installation/setting-git-push-limits": "/enterprise/2.16/admin/installation/setting-git-push-limits", + "/enterprise/2.16/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance", + "/enterprise/2.16/admin/guides/installation/setting-up-a-staging-instance": "/enterprise/2.16/admin/installation/setting-up-a-staging-instance", + "/enterprise/2.16/admin/guides/installation/setting-up-external-monitoring": "/enterprise/2.16/admin/installation/setting-up-external-monitoring", + "/enterprise/2.16/admin/guides/installation/site-admin-dashboard": "/enterprise/2.16/admin/installation/site-admin-dashboard", + "/enterprise/2.16/admin/guides/installation/system-overview": "/enterprise/2.16/admin/installation/system-overview", + "/enterprise/2.16/admin/guides/installation/troubleshooting-ssl-errors": "/enterprise/2.16/admin/installation/troubleshooting-ssl-errors", + "/enterprise/2.16/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources", + "/enterprise/2.16/admin/guides/installation/upgrade-requirements": "/enterprise/2.16/admin/installation/upgrade-requirements", + "/enterprise/2.16/admin/guides/installation/upgrading-github-enterprise-server": "/enterprise/2.16/admin/installation/upgrading-github-enterprise-server", + "/enterprise/2.16/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer", + "/enterprise/2.16/admin/guides/installation/validating-your-domain-settings": "/enterprise/2.16/admin/installation/validating-your-domain-settings", + "/enterprise/2.16/admin/guides/installation/viewing-push-logs": "/enterprise/2.16/admin/installation/viewing-push-logs", + "/enterprise/2.16/admin/guides/migrations/about-migrations": "/enterprise/2.16/admin/migrations/about-migrations", + "/enterprise/2.16/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server", + "/enterprise/2.16/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server", + "/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server", + "/enterprise/2.16/admin/guides/migrations/exporting-migration-data-from-githubcom": "/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom", + "/enterprise/2.16/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories", + "/enterprise/2.16/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories", + "/enterprise/2.16/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts", + "/enterprise/2.16/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems", + "/enterprise/2.16/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server", + "/enterprise/2.16/admin/guides/migrations": "/enterprise/2.16/admin/migrations", + "/enterprise/2.16/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance", + "/enterprise/2.16/admin/guides/migrations/preparing-the-githubcom-source-organization": "/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization", + "/enterprise/2.16/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", + "/enterprise/2.16/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", + "/enterprise/2.16/admin/guides/migrations/reviewing-migration-conflicts": "/enterprise/2.16/admin/migrations/reviewing-migration-conflicts", + "/enterprise/2.16/admin/guides/migrations/reviewing-migration-data": "/enterprise/2.16/admin/migrations/reviewing-migration-data", + "/enterprise/2.16/admin/guides/user-management/about-global-webhooks": "/enterprise/2.16/admin/user-management/about-global-webhooks", + "/enterprise/2.16/admin/guides/user-management/adding-people-to-teams": "/enterprise/2.16/admin/user-management/adding-people-to-teams", + "/enterprise/2.16/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", + "/enterprise/2.16/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", + "/enterprise/2.16/admin/guides/user-management/archiving-and-unarchiving-repositories": "/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories", + "/enterprise/2.16/admin/guides/user-management/auditing-ssh-keys": "/enterprise/2.16/admin/user-management/auditing-ssh-keys", + "/enterprise/2.16/admin/guides/user-management/auditing-users-across-your-instance": "/enterprise/2.16/admin/user-management/auditing-users-across-your-instance", + "/enterprise/2.16/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", + "/enterprise/2.16/admin/guides/user-management/basic-account-settings": "/enterprise/2.16/admin/user-management/basic-account-settings", + "/enterprise/2.16/admin/guides/user-management/best-practices-for-user-security": "/enterprise/2.16/admin/user-management/best-practices-for-user-security", + "/enterprise/2.16/admin/guides/user-management/changing-authentication-methods": "/enterprise/2.16/admin/user-management/changing-authentication-methods", + "/enterprise/2.16/admin/guides/user-management/configuring-email-for-notifications": "/enterprise/2.16/admin/user-management/configuring-email-for-notifications", + "/enterprise/2.16/admin/guides/user-management/configuring-visibility-for-organization-membership": "/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership", + "/enterprise/2.16/admin/guides/user-management/creating-organizations": "/enterprise/2.16/admin/user-management/creating-organizations", + "/enterprise/2.16/admin/guides/user-management/creating-teams": "/enterprise/2.16/admin/user-management/creating-teams", + "/enterprise/2.16/admin/guides/user-management/customizing-user-messages-on-your-instance": "/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance", + "/enterprise/2.16/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups", + "/enterprise/2.16/admin/guides/user-management": "/enterprise/2.16/admin/user-management", + "/enterprise/2.16/admin/guides/user-management/managing-dormant-users": "/enterprise/2.16/admin/user-management/managing-dormant-users", + "/enterprise/2.16/admin/guides/user-management/managing-global-webhooks": "/enterprise/2.16/admin/user-management/managing-global-webhooks", + "/enterprise/2.16/admin/guides/user-management/organizations-and-teams": "/enterprise/2.16/admin/user-management/organizations-and-teams", + "/enterprise/2.16/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", + "/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", + "/enterprise/2.16/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", + "/enterprise/2.16/admin/guides/user-management/preventing-users-from-creating-organizations": "/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations", + "/enterprise/2.16/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories", + "/enterprise/2.16/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator", + "/enterprise/2.16/admin/guides/user-management/rebuilding-contributions-data": "/enterprise/2.16/admin/user-management/rebuilding-contributions-data", + "/enterprise/2.16/admin/guides/user-management/removing-users-from-teams-and-organizations": "/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations", + "/enterprise/2.16/admin/guides/user-management/repositories": "/enterprise/2.16/admin/user-management/repositories", + "/enterprise/2.16/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization", + "/enterprise/2.16/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance", + "/enterprise/2.16/admin/guides/user-management/suspending-and-unsuspending-users": "/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users", + "/enterprise/2.16/admin/guides/user-management/user-security": "/enterprise/2.16/admin/user-management/user-security", + "/enterprise/2.16/admin/guides/user-management/using-built-in-authentication": "/enterprise/2.16/admin/user-management/using-built-in-authentication", + "/enterprise/2.16/admin/guides/user-management/using-cas": "/enterprise/2.16/admin/user-management/using-cas", + "/enterprise/2.16/admin/guides/user-management/using-ldap": "/enterprise/2.16/admin/user-management/using-ldap", + "/enterprise/2.16/admin/guides/user-management/using-saml": "/enterprise/2.16/admin/user-management/using-saml", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", + "/enterprise/2.16/user/administering-a-repository/about-branch-restrictions": "/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", + "/enterprise/2.16/github/administering-a-repository/about-branch-restrictions": "/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", + "/enterprise/2.16/user/administering-a-repository/about-merge-methods-on-github": "/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", + "/enterprise/2.16/github/administering-a-repository/about-merge-methods-on-github": "/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-protected-branches": "/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", + "/enterprise/2.16/user/administering-a-repository/about-protected-branches": "/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", + "/enterprise/2.16/github/administering-a-repository/about-protected-branches": "/enterprise/2.16/user/github/administering-a-repository/about-protected-branches", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-releases": "/enterprise/2.16/user/github/administering-a-repository/about-releases", + "/enterprise/2.16/user/administering-a-repository/about-releases": "/enterprise/2.16/user/github/administering-a-repository/about-releases", + "/enterprise/2.16/github/administering-a-repository/about-releases": "/enterprise/2.16/user/github/administering-a-repository/about-releases", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", + "/enterprise/2.16/user/administering-a-repository/about-required-commit-signing": "/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", + "/enterprise/2.16/github/administering-a-repository/about-required-commit-signing": "/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", + "/enterprise/2.16/user/administering-a-repository/about-required-reviews-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", + "/enterprise/2.16/github/administering-a-repository/about-required-reviews-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", + "/enterprise/2.16/user/administering-a-repository/about-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", + "/enterprise/2.16/github/administering-a-repository/about-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", + "/enterprise/2.16/user/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", + "/enterprise/2.16/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": "/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", + "/enterprise/2.16/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", + "/enterprise/2.16/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", + "/enterprise/2.16/user/administering-a-repository/classifying-your-repository-with-topics": "/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", + "/enterprise/2.16/github/administering-a-repository/classifying-your-repository-with-topics": "/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.16/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.16/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.16/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.16/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", + "/enterprise/2.16/user/administering-a-repository/configuring-protected-branches": "/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", + "/enterprise/2.16/github/administering-a-repository/configuring-protected-branches": "/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", + "/enterprise/2.16/user/administering-a-repository/configuring-pull-request-merges": "/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", + "/enterprise/2.16/github/administering-a-repository/configuring-pull-request-merges": "/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/creating-releases": "/enterprise/2.16/user/github/administering-a-repository/creating-releases", + "/enterprise/2.16/user/administering-a-repository/creating-releases": "/enterprise/2.16/user/github/administering-a-repository/creating-releases", + "/enterprise/2.16/github/administering-a-repository/creating-releases": "/enterprise/2.16/user/github/administering-a-repository/creating-releases", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", + "/enterprise/2.16/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", + "/enterprise/2.16/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", + "/enterprise/2.16/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", + "/enterprise/2.16/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", + "/enterprise/2.16/user/administering-a-repository/deleting-a-repository": "/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", + "/enterprise/2.16/github/administering-a-repository/deleting-a-repository": "/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.16/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.16/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/editing-and-deleting-releases": "/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", + "/enterprise/2.16/user/administering-a-repository/editing-and-deleting-releases": "/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", + "/enterprise/2.16/github/administering-a-repository/editing-and-deleting-releases": "/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.16/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.16/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", + "/enterprise/2.16/user/administering-a-repository/enabling-branch-restrictions": "/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", + "/enterprise/2.16/github/administering-a-repository/enabling-branch-restrictions": "/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", + "/enterprise/2.16/user/administering-a-repository/enabling-required-commit-signing": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", + "/enterprise/2.16/github/administering-a-repository/enabling-required-commit-signing": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", + "/enterprise/2.16/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", + "/enterprise/2.16/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", + "/enterprise/2.16/user/administering-a-repository/enabling-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", + "/enterprise/2.16/github/administering-a-repository/enabling-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/getting-the-download-count-for-your-releases": "/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", + "/enterprise/2.16/user/administering-a-repository/getting-the-download-count-for-your-releases": "/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", + "/enterprise/2.16/github/administering-a-repository/getting-the-download-count-for-your-releases": "/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository": "/enterprise/2.16/user/github/administering-a-repository", + "/enterprise/2.16/user/administering-a-repository": "/enterprise/2.16/user/github/administering-a-repository", + "/enterprise/2.16/github/administering-a-repository": "/enterprise/2.16/user/github/administering-a-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/linking-to-releases": "/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", + "/enterprise/2.16/user/administering-a-repository/linking-to-releases": "/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", + "/enterprise/2.16/github/administering-a-repository/linking-to-releases": "/enterprise/2.16/user/github/administering-a-repository/linking-to-releases", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", + "/enterprise/2.16/user/administering-a-repository/managing-branches-in-your-repository": "/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", + "/enterprise/2.16/github/administering-a-repository/managing-branches-in-your-repository": "/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", + "/enterprise/2.16/user/administering-a-repository/managing-releases-in-a-repository": "/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", + "/enterprise/2.16/github/administering-a-repository/managing-releases-in-a-repository": "/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", + "/enterprise/2.16/user/administering-a-repository/managing-repository-settings": "/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", + "/enterprise/2.16/github/administering-a-repository/managing-repository-settings": "/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", + "/enterprise/2.16/user/administering-a-repository/renaming-a-repository": "/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", + "/enterprise/2.16/github/administering-a-repository/renaming-a-repository": "/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", + "/enterprise/2.16/user/administering-a-repository/setting-repository-visibility": "/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", + "/enterprise/2.16/github/administering-a-repository/setting-repository-visibility": "/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", + "/enterprise/2.16/user/administering-a-repository/setting-the-default-branch": "/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", + "/enterprise/2.16/github/administering-a-repository/setting-the-default-branch": "/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", + "/enterprise/2.16/user/administering-a-repository/transferring-a-repository": "/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", + "/enterprise/2.16/github/administering-a-repository/transferring-a-repository": "/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", + "/enterprise/2.16/user/administering-a-repository/types-of-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", + "/enterprise/2.16/github/administering-a-repository/types-of-required-status-checks": "/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", + "/enterprise/2.16/user/administering-a-repository/viewing-branches-in-your-repository": "/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", + "/enterprise/2.16/github/administering-a-repository/viewing-branches-in-your-repository": "/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository", + "/enterprise/2.16/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-tags": "/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", + "/enterprise/2.16/user/administering-a-repository/viewing-your-repositorys-tags": "/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", + "/enterprise/2.16/github/administering-a-repository/viewing-your-repositorys-tags": "/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags", + "/enterprise/2.16/user/authenticating-to-github/about-commit-signature-verification": "/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", + "/enterprise/2.16/github/authenticating-to-github/about-commit-signature-verification": "/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification", + "/enterprise/2.16/user/authenticating-to-github/about-ssh": "/enterprise/2.16/user/github/authenticating-to-github/about-ssh", + "/enterprise/2.16/github/authenticating-to-github/about-ssh": "/enterprise/2.16/user/github/authenticating-to-github/about-ssh", + "/enterprise/2.16/user/authenticating-to-github/about-two-factor-authentication": "/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", + "/enterprise/2.16/github/authenticating-to-github/about-two-factor-authentication": "/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication", + "/enterprise/2.16/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", + "/enterprise/2.16/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", + "/enterprise/2.16/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", + "/enterprise/2.16/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", + "/enterprise/2.16/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", + "/enterprise/2.16/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", + "/enterprise/2.16/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", + "/enterprise/2.16/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", + "/enterprise/2.16/user/authenticating-to-github/authorizing-oauth-apps": "/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", + "/enterprise/2.16/github/authenticating-to-github/authorizing-oauth-apps": "/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps", + "/enterprise/2.16/user/authenticating-to-github/checking-for-existing-gpg-keys": "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", + "/enterprise/2.16/github/authenticating-to-github/checking-for-existing-gpg-keys": "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys", + "/enterprise/2.16/user/authenticating-to-github/checking-for-existing-ssh-keys": "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", + "/enterprise/2.16/github/authenticating-to-github/checking-for-existing-ssh-keys": "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys", + "/enterprise/2.16/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", + "/enterprise/2.16/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", + "/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", + "/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", + "/enterprise/2.16/user/authenticating-to-github/configuring-two-factor-authentication": "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", + "/enterprise/2.16/github/authenticating-to-github/configuring-two-factor-authentication": "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication", + "/enterprise/2.16/user/authenticating-to-github/connecting-to-github-with-ssh": "/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", + "/enterprise/2.16/github/authenticating-to-github/connecting-to-github-with-ssh": "/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh", + "/enterprise/2.16/user/authenticating-to-github/connecting-with-third-party-applications": "/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", + "/enterprise/2.16/github/authenticating-to-github/connecting-with-third-party-applications": "/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications", + "/enterprise/2.16/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", + "/enterprise/2.16/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", + "/enterprise/2.16/user/authenticating-to-github/creating-a-strong-password": "/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", + "/enterprise/2.16/github/authenticating-to-github/creating-a-strong-password": "/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password", + "/enterprise/2.16/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", + "/enterprise/2.16/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", + "/enterprise/2.16/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", + "/enterprise/2.16/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", + "/enterprise/2.16/user/authenticating-to-github/error-bad-file-number": "/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", + "/enterprise/2.16/github/authenticating-to-github/error-bad-file-number": "/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number", + "/enterprise/2.16/user/authenticating-to-github/error-key-already-in-use": "/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", + "/enterprise/2.16/github/authenticating-to-github/error-key-already-in-use": "/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use", + "/enterprise/2.16/user/authenticating-to-github/error-permission-denied-publickey": "/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", + "/enterprise/2.16/github/authenticating-to-github/error-permission-denied-publickey": "/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey", + "/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", + "/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", + "/enterprise/2.16/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", + "/enterprise/2.16/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", + "/enterprise/2.16/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", + "/enterprise/2.16/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", + "/enterprise/2.16/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", + "/enterprise/2.16/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", + "/enterprise/2.16/user/authenticating-to-github/generating-a-new-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", + "/enterprise/2.16/github/authenticating-to-github/generating-a-new-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key", + "/enterprise/2.16/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", + "/enterprise/2.16/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", + "/enterprise/2.16/user/authenticating-to-github": "/enterprise/2.16/user/github/authenticating-to-github", + "/enterprise/2.16/github/authenticating-to-github": "/enterprise/2.16/user/github/authenticating-to-github", + "/enterprise/2.16/user/authenticating-to-github/keeping-your-account-and-data-secure": "/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", + "/enterprise/2.16/github/authenticating-to-github/keeping-your-account-and-data-secure": "/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure", + "/enterprise/2.16/user/authenticating-to-github/managing-commit-signature-verification": "/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", + "/enterprise/2.16/github/authenticating-to-github/managing-commit-signature-verification": "/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification", + "/enterprise/2.16/user/authenticating-to-github/preventing-unauthorized-access": "/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", + "/enterprise/2.16/github/authenticating-to-github/preventing-unauthorized-access": "/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access", + "/enterprise/2.16/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", + "/enterprise/2.16/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", + "/enterprise/2.16/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", + "/enterprise/2.16/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", + "/enterprise/2.16/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", + "/enterprise/2.16/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", + "/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", + "/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", + "/enterprise/2.16/user/authenticating-to-github/reviewing-your-authorized-integrations": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", + "/enterprise/2.16/github/authenticating-to-github/reviewing-your-authorized-integrations": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations", + "/enterprise/2.16/user/authenticating-to-github/reviewing-your-deploy-keys": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", + "/enterprise/2.16/github/authenticating-to-github/reviewing-your-deploy-keys": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys", + "/enterprise/2.16/user/authenticating-to-github/reviewing-your-security-log": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", + "/enterprise/2.16/github/authenticating-to-github/reviewing-your-security-log": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log", + "/enterprise/2.16/user/authenticating-to-github/reviewing-your-ssh-keys": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", + "/enterprise/2.16/github/authenticating-to-github/reviewing-your-ssh-keys": "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys", + "/enterprise/2.16/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", + "/enterprise/2.16/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", + "/enterprise/2.16/user/authenticating-to-github/signing-commits": "/enterprise/2.16/user/github/authenticating-to-github/signing-commits", + "/enterprise/2.16/github/authenticating-to-github/signing-commits": "/enterprise/2.16/user/github/authenticating-to-github/signing-commits", + "/enterprise/2.16/user/authenticating-to-github/signing-tags": "/enterprise/2.16/user/github/authenticating-to-github/signing-tags", + "/enterprise/2.16/github/authenticating-to-github/signing-tags": "/enterprise/2.16/user/github/authenticating-to-github/signing-tags", + "/enterprise/2.16/user/authenticating-to-github/sudo-mode": "/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", + "/enterprise/2.16/github/authenticating-to-github/sudo-mode": "/enterprise/2.16/user/github/authenticating-to-github/sudo-mode", + "/enterprise/2.16/user/authenticating-to-github/telling-git-about-your-signing-key": "/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", + "/enterprise/2.16/github/authenticating-to-github/telling-git-about-your-signing-key": "/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key", + "/enterprise/2.16/user/authenticating-to-github/testing-your-ssh-connection": "/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", + "/enterprise/2.16/github/authenticating-to-github/testing-your-ssh-connection": "/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection", + "/enterprise/2.16/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", + "/enterprise/2.16/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", + "/enterprise/2.16/user/authenticating-to-github/troubleshooting-ssh": "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", + "/enterprise/2.16/github/authenticating-to-github/troubleshooting-ssh": "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh", + "/enterprise/2.16/user/authenticating-to-github/updating-an-expired-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", + "/enterprise/2.16/github/authenticating-to-github/updating-an-expired-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key", + "/enterprise/2.16/user/authenticating-to-github/updating-your-github-access-credentials": "/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", + "/enterprise/2.16/github/authenticating-to-github/updating-your-github-access-credentials": "/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials", + "/enterprise/2.16/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", + "/enterprise/2.16/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", + "/enterprise/2.16/user/authenticating-to-github/working-with-ssh-key-passphrases": "/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", + "/enterprise/2.16/github/authenticating-to-github/working-with-ssh-key-passphrases": "/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases", + "/enterprise/2.16/user/building-a-strong-community/about-issue-and-pull-request-templates": "/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", + "/enterprise/2.16/github/building-a-strong-community/about-issue-and-pull-request-templates": "/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates", + "/enterprise/2.16/user/building-a-strong-community/about-team-discussions": "/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", + "/enterprise/2.16/github/building-a-strong-community/about-team-discussions": "/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions", + "/enterprise/2.16/user/building-a-strong-community/about-wikis": "/enterprise/2.16/user/github/building-a-strong-community/about-wikis", + "/enterprise/2.16/github/building-a-strong-community/about-wikis": "/enterprise/2.16/user/github/building-a-strong-community/about-wikis", + "/enterprise/2.16/user/building-a-strong-community/adding-a-license-to-a-repository": "/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", + "/enterprise/2.16/github/building-a-strong-community/adding-a-license-to-a-repository": "/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository", + "/enterprise/2.16/user/building-a-strong-community/adding-or-editing-wiki-pages": "/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", + "/enterprise/2.16/github/building-a-strong-community/adding-or-editing-wiki-pages": "/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages", + "/enterprise/2.16/user/building-a-strong-community/adding-support-resources-to-your-project": "/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", + "/enterprise/2.16/github/building-a-strong-community/adding-support-resources-to-your-project": "/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project", + "/enterprise/2.16/user/building-a-strong-community/changing-access-permissions-for-wikis": "/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", + "/enterprise/2.16/github/building-a-strong-community/changing-access-permissions-for-wikis": "/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis", + "/enterprise/2.16/user/building-a-strong-community/collaborating-with-your-team": "/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", + "/enterprise/2.16/github/building-a-strong-community/collaborating-with-your-team": "/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team", + "/enterprise/2.16/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", + "/enterprise/2.16/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", + "/enterprise/2.16/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", + "/enterprise/2.16/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", + "/enterprise/2.16/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", + "/enterprise/2.16/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", + "/enterprise/2.16/user/building-a-strong-community/creating-a-team-discussion": "/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", + "/enterprise/2.16/github/building-a-strong-community/creating-a-team-discussion": "/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion", + "/enterprise/2.16/user/building-a-strong-community/disabling-wikis": "/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", + "/enterprise/2.16/github/building-a-strong-community/disabling-wikis": "/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis", + "/enterprise/2.16/user/building-a-strong-community/documenting-your-project-with-wikis": "/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", + "/enterprise/2.16/github/building-a-strong-community/documenting-your-project-with-wikis": "/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis", + "/enterprise/2.16/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", + "/enterprise/2.16/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", + "/enterprise/2.16/user/building-a-strong-community/editing-wiki-content": "/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", + "/enterprise/2.16/github/building-a-strong-community/editing-wiki-content": "/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content", + "/enterprise/2.16/user/building-a-strong-community": "/enterprise/2.16/user/github/building-a-strong-community", + "/enterprise/2.16/github/building-a-strong-community": "/enterprise/2.16/user/github/building-a-strong-community", + "/enterprise/2.16/user/building-a-strong-community/locking-conversations": "/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", + "/enterprise/2.16/github/building-a-strong-community/locking-conversations": "/enterprise/2.16/user/github/building-a-strong-community/locking-conversations", + "/enterprise/2.16/user/building-a-strong-community/managing-disruptive-comments": "/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", + "/enterprise/2.16/github/building-a-strong-community/managing-disruptive-comments": "/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments", + "/enterprise/2.16/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", + "/enterprise/2.16/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", + "/enterprise/2.16/user/building-a-strong-community/moderating-comments-and-conversations": "/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", + "/enterprise/2.16/github/building-a-strong-community/moderating-comments-and-conversations": "/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations", + "/enterprise/2.16/user/building-a-strong-community/pinning-a-team-discussion": "/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", + "/enterprise/2.16/github/building-a-strong-community/pinning-a-team-discussion": "/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion", + "/enterprise/2.16/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", + "/enterprise/2.16/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", + "/enterprise/2.16/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", + "/enterprise/2.16/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", + "/enterprise/2.16/user/building-a-strong-community/tracking-changes-in-a-comment": "/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", + "/enterprise/2.16/github/building-a-strong-community/tracking-changes-in-a-comment": "/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment", + "/enterprise/2.16/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", + "/enterprise/2.16/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", + "/enterprise/2.16/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", + "/enterprise/2.16/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-branches": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-branches": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-forks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-forks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/github-flow": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/github-flow": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", + "/enterprise/2.16/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", + "/enterprise/2.16/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", + "/enterprise/2.16/user/committing-changes-to-your-project/changing-a-commit-message": "/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", + "/enterprise/2.16/github/committing-changes-to-your-project/changing-a-commit-message": "/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message", + "/enterprise/2.16/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", + "/enterprise/2.16/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", + "/enterprise/2.16/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", + "/enterprise/2.16/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", + "/enterprise/2.16/user/committing-changes-to-your-project/comparing-commits-across-time": "/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", + "/enterprise/2.16/github/committing-changes-to-your-project/comparing-commits-across-time": "/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time", + "/enterprise/2.16/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", + "/enterprise/2.16/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", + "/enterprise/2.16/user/committing-changes-to-your-project/creating-and-editing-commits": "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", + "/enterprise/2.16/github/committing-changes-to-your-project/creating-and-editing-commits": "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits", + "/enterprise/2.16/user/committing-changes-to-your-project/differences-between-commit-views": "/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", + "/enterprise/2.16/github/committing-changes-to-your-project/differences-between-commit-views": "/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views", + "/enterprise/2.16/user/committing-changes-to-your-project": "/enterprise/2.16/user/github/committing-changes-to-your-project", + "/enterprise/2.16/github/committing-changes-to-your-project": "/enterprise/2.16/user/github/committing-changes-to-your-project", + "/enterprise/2.16/user/committing-changes-to-your-project/troubleshooting-commits": "/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", + "/enterprise/2.16/github/committing-changes-to-your-project/troubleshooting-commits": "/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits", + "/enterprise/2.16/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", + "/enterprise/2.16/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", + "/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", + "/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", + "/enterprise/2.16/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", + "/enterprise/2.16/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-code-owners": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-code-owners": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-readmes": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-readmes": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", + "/enterprise/2.16/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", + "/enterprise/2.16/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", + "/enterprise/2.16/user/extending-github/about-webhooks": "/enterprise/2.16/user/github/extending-github/about-webhooks", + "/enterprise/2.16/github/extending-github/about-webhooks": "/enterprise/2.16/user/github/extending-github/about-webhooks", + "/enterprise/2.16/user/extending-github/getting-started-with-the-api": "/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", + "/enterprise/2.16/github/extending-github/getting-started-with-the-api": "/enterprise/2.16/user/github/extending-github/getting-started-with-the-api", + "/enterprise/2.16/user/extending-github/git-automation-with-oauth-tokens": "/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", + "/enterprise/2.16/github/extending-github/git-automation-with-oauth-tokens": "/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens", + "/enterprise/2.16/user/extending-github": "/enterprise/2.16/user/github/extending-github", + "/enterprise/2.16/github/extending-github": "/enterprise/2.16/user/github/extending-github", + "/enterprise/2.16/user/getting-started-with-github/access-permissions-on-github": "/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", + "/enterprise/2.16/github/getting-started-with-github/access-permissions-on-github": "/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github", + "/enterprise/2.16/user/getting-started-with-github/be-social": "/enterprise/2.16/user/github/getting-started-with-github/be-social", + "/enterprise/2.16/github/getting-started-with-github/be-social": "/enterprise/2.16/user/github/getting-started-with-github/be-social", + "/enterprise/2.16/user/getting-started-with-github/create-a-repo": "/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", + "/enterprise/2.16/github/getting-started-with-github/create-a-repo": "/enterprise/2.16/user/github/getting-started-with-github/create-a-repo", + "/enterprise/2.16/user/getting-started-with-github/exploring-projects-on-github": "/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", + "/enterprise/2.16/github/getting-started-with-github/exploring-projects-on-github": "/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github", + "/enterprise/2.16/user/getting-started-with-github/following-people": "/enterprise/2.16/user/github/getting-started-with-github/following-people", + "/enterprise/2.16/github/getting-started-with-github/following-people": "/enterprise/2.16/user/github/getting-started-with-github/following-people", + "/enterprise/2.16/user/getting-started-with-github/fork-a-repo": "/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", + "/enterprise/2.16/github/getting-started-with-github/fork-a-repo": "/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo", + "/enterprise/2.16/user/getting-started-with-github/git-and-github-learning-resources": "/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", + "/enterprise/2.16/github/getting-started-with-github/git-and-github-learning-resources": "/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources", + "/enterprise/2.16/user/getting-started-with-github/git-cheatsheet": "/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", + "/enterprise/2.16/github/getting-started-with-github/git-cheatsheet": "/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet", + "/enterprise/2.16/user/getting-started-with-github/github-glossary": "/enterprise/2.16/user/github/getting-started-with-github/github-glossary", + "/enterprise/2.16/github/getting-started-with-github/github-glossary": "/enterprise/2.16/user/github/getting-started-with-github/github-glossary", + "/enterprise/2.16/user/getting-started-with-github": "/enterprise/2.16/user/github/getting-started-with-github", + "/enterprise/2.16/github/getting-started-with-github": "/enterprise/2.16/user/github/getting-started-with-github", + "/enterprise/2.16/user/getting-started-with-github/keyboard-shortcuts": "/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", + "/enterprise/2.16/github/getting-started-with-github/keyboard-shortcuts": "/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts", + "/enterprise/2.16/user/getting-started-with-github/learning-about-github": "/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", + "/enterprise/2.16/github/getting-started-with-github/learning-about-github": "/enterprise/2.16/user/github/getting-started-with-github/learning-about-github", + "/enterprise/2.16/user/getting-started-with-github/saving-repositories-with-stars": "/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", + "/enterprise/2.16/github/getting-started-with-github/saving-repositories-with-stars": "/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars", + "/enterprise/2.16/user/getting-started-with-github/set-up-git": "/enterprise/2.16/user/github/getting-started-with-github/set-up-git", + "/enterprise/2.16/github/getting-started-with-github/set-up-git": "/enterprise/2.16/user/github/getting-started-with-github/set-up-git", + "/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", + "/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", + "/enterprise/2.16/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", + "/enterprise/2.16/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", + "/enterprise/2.16/user/getting-started-with-github/signing-up-for-github": "/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", + "/enterprise/2.16/github/getting-started-with-github/signing-up-for-github": "/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github", + "/enterprise/2.16/user/getting-started-with-github/supported-browsers": "/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", + "/enterprise/2.16/github/getting-started-with-github/supported-browsers": "/enterprise/2.16/user/github/getting-started-with-github/supported-browsers", + "/enterprise/2.16/user/getting-started-with-github/types-of-github-accounts": "/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", + "/enterprise/2.16/github/getting-started-with-github/types-of-github-accounts": "/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts", + "/enterprise/2.16/user/getting-started-with-github/using-github": "/enterprise/2.16/user/github/getting-started-with-github/using-github", + "/enterprise/2.16/github/getting-started-with-github/using-github": "/enterprise/2.16/user/github/getting-started-with-github/using-github", + "/enterprise/2.16/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", + "/enterprise/2.16/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", + "/enterprise/2.16/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", + "/enterprise/2.16/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", + "/enterprise/2.16/user/importing-your-projects-to-github/importing-source-code-to-github": "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", + "/enterprise/2.16/github/importing-your-projects-to-github/importing-source-code-to-github": "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github", + "/enterprise/2.16/user/importing-your-projects-to-github": "/enterprise/2.16/user/github/importing-your-projects-to-github", + "/enterprise/2.16/github/importing-your-projects-to-github": "/enterprise/2.16/user/github/importing-your-projects-to-github", + "/enterprise/2.16/user/importing-your-projects-to-github/source-code-migration-tools": "/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", + "/enterprise/2.16/github/importing-your-projects-to-github/source-code-migration-tools": "/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools", + "/enterprise/2.16/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", + "/enterprise/2.16/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", + "/enterprise/2.16/user/importing-your-projects-to-github/support-for-subversion-clients": "/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", + "/enterprise/2.16/github/importing-your-projects-to-github/support-for-subversion-clients": "/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients", + "/enterprise/2.16/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", + "/enterprise/2.16/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", + "/enterprise/2.16/user/importing-your-projects-to-github/working-with-subversion-on-github": "/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", + "/enterprise/2.16/github/importing-your-projects-to-github/working-with-subversion-on-github": "/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github", + "/enterprise/2.16/user": "/enterprise/2.16/user/github", + "/enterprise/2.16/github": "/enterprise/2.16/user/github", + "/enterprise/2.16/user/managing-files-in-a-repository/3d-file-viewer": "/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", + "/enterprise/2.16/github/managing-files-in-a-repository/3d-file-viewer": "/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer", + "/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", + "/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", + "/enterprise/2.16/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", + "/enterprise/2.16/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", + "/enterprise/2.16/user/managing-files-in-a-repository/creating-new-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", + "/enterprise/2.16/github/managing-files-in-a-repository/creating-new-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files", + "/enterprise/2.16/user/managing-files-in-a-repository/deleting-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", + "/enterprise/2.16/github/managing-files-in-a-repository/deleting-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files", + "/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", + "/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", + "/enterprise/2.16/user/managing-files-in-a-repository/editing-files-in-your-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", + "/enterprise/2.16/github/managing-files-in-a-repository/editing-files-in-your-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository", + "/enterprise/2.16/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", + "/enterprise/2.16/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", + "/enterprise/2.16/user/managing-files-in-a-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository", + "/enterprise/2.16/github/managing-files-in-a-repository": "/enterprise/2.16/user/github/managing-files-in-a-repository", + "/enterprise/2.16/user/managing-files-in-a-repository/managing-files-on-github": "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", + "/enterprise/2.16/github/managing-files-in-a-repository/managing-files-on-github": "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github", + "/enterprise/2.16/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", + "/enterprise/2.16/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", + "/enterprise/2.16/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", + "/enterprise/2.16/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", + "/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", + "/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", + "/enterprise/2.16/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", + "/enterprise/2.16/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", + "/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", + "/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", + "/enterprise/2.16/user/managing-files-in-a-repository/renaming-a-file": "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", + "/enterprise/2.16/github/managing-files-in-a-repository/renaming-a-file": "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file", + "/enterprise/2.16/user/managing-files-in-a-repository/rendering-and-diffing-images": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", + "/enterprise/2.16/github/managing-files-in-a-repository/rendering-and-diffing-images": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images", + "/enterprise/2.16/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", + "/enterprise/2.16/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", + "/enterprise/2.16/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", + "/enterprise/2.16/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", + "/enterprise/2.16/user/managing-files-in-a-repository/rendering-pdf-documents": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", + "/enterprise/2.16/github/managing-files-in-a-repository/rendering-pdf-documents": "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents", + "/enterprise/2.16/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", + "/enterprise/2.16/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", + "/enterprise/2.16/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", + "/enterprise/2.16/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", + "/enterprise/2.16/user/managing-files-in-a-repository/working-with-non-code-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", + "/enterprise/2.16/github/managing-files-in-a-repository/working-with-non-code-files": "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files", + "/enterprise/2.16/user/managing-large-files/about-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", + "/enterprise/2.16/github/managing-large-files/about-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage", + "/enterprise/2.16/user/managing-large-files/collaboration-with-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", + "/enterprise/2.16/github/managing-large-files/collaboration-with-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage", + "/enterprise/2.16/user/managing-large-files/conditions-for-large-files": "/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", + "/enterprise/2.16/github/managing-large-files/conditions-for-large-files": "/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files", + "/enterprise/2.16/user/managing-large-files/configuring-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", + "/enterprise/2.16/github/managing-large-files/configuring-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage", + "/enterprise/2.16/user/managing-large-files/distributing-large-binaries": "/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", + "/enterprise/2.16/github/managing-large-files/distributing-large-binaries": "/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries", + "/enterprise/2.16/user/managing-large-files": "/enterprise/2.16/user/github/managing-large-files", + "/enterprise/2.16/github/managing-large-files": "/enterprise/2.16/user/github/managing-large-files", + "/enterprise/2.16/user/managing-large-files/installing-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", + "/enterprise/2.16/github/managing-large-files/installing-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage", + "/enterprise/2.16/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", + "/enterprise/2.16/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", + "/enterprise/2.16/user/managing-large-files/removing-files-from-a-repositorys-history": "/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", + "/enterprise/2.16/github/managing-large-files/removing-files-from-a-repositorys-history": "/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history", + "/enterprise/2.16/user/managing-large-files/removing-files-from-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", + "/enterprise/2.16/github/managing-large-files/removing-files-from-git-large-file-storage": "/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage", + "/enterprise/2.16/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", + "/enterprise/2.16/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", + "/enterprise/2.16/user/managing-large-files/versioning-large-files": "/enterprise/2.16/user/github/managing-large-files/versioning-large-files", + "/enterprise/2.16/github/managing-large-files/versioning-large-files": "/enterprise/2.16/user/github/managing-large-files/versioning-large-files", + "/enterprise/2.16/user/managing-large-files/working-with-large-files": "/enterprise/2.16/user/github/managing-large-files/working-with-large-files", + "/enterprise/2.16/github/managing-large-files/working-with-large-files": "/enterprise/2.16/user/github/managing-large-files/working-with-large-files", + "/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", + "/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", + "/enterprise/2.16/user/managing-your-work-on-github/about-automation-for-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", + "/enterprise/2.16/github/managing-your-work-on-github/about-automation-for-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards", + "/enterprise/2.16/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/about-issues": "/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", + "/enterprise/2.16/github/managing-your-work-on-github/about-issues": "/enterprise/2.16/user/github/managing-your-work-on-github/about-issues", + "/enterprise/2.16/user/managing-your-work-on-github/about-labels": "/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", + "/enterprise/2.16/github/managing-your-work-on-github/about-labels": "/enterprise/2.16/user/github/managing-your-work-on-github/about-labels", + "/enterprise/2.16/user/managing-your-work-on-github/about-milestones": "/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", + "/enterprise/2.16/github/managing-your-work-on-github/about-milestones": "/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones", + "/enterprise/2.16/user/managing-your-work-on-github/about-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", + "/enterprise/2.16/github/managing-your-work-on-github/about-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards", + "/enterprise/2.16/user/managing-your-work-on-github/about-task-lists": "/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", + "/enterprise/2.16/github/managing-your-work-on-github/about-task-lists": "/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists", + "/enterprise/2.16/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", + "/enterprise/2.16/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", + "/enterprise/2.16/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/changing-project-board-visibility": "/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", + "/enterprise/2.16/github/managing-your-work-on-github/changing-project-board-visibility": "/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility", + "/enterprise/2.16/user/managing-your-work-on-github/closing-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/closing-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/closing-issues-using-keywords": "/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", + "/enterprise/2.16/github/managing-your-work-on-github/closing-issues-using-keywords": "/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords", + "/enterprise/2.16/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", + "/enterprise/2.16/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", + "/enterprise/2.16/user/managing-your-work-on-github/creating-a-label": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", + "/enterprise/2.16/github/managing-your-work-on-github/creating-a-label": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label", + "/enterprise/2.16/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", + "/enterprise/2.16/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", + "/enterprise/2.16/user/managing-your-work-on-github/creating-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/creating-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/creating-an-issue": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", + "/enterprise/2.16/github/managing-your-work-on-github/creating-an-issue": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue", + "/enterprise/2.16/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/deleting-a-label": "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", + "/enterprise/2.16/github/managing-your-work-on-github/deleting-a-label": "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label", + "/enterprise/2.16/user/managing-your-work-on-github/deleting-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/deleting-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/deleting-an-issue": "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", + "/enterprise/2.16/github/managing-your-work-on-github/deleting-an-issue": "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue", + "/enterprise/2.16/user/managing-your-work-on-github/disabling-issues": "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", + "/enterprise/2.16/github/managing-your-work-on-github/disabling-issues": "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues", + "/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", + "/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", + "/enterprise/2.16/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", + "/enterprise/2.16/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", + "/enterprise/2.16/user/managing-your-work-on-github/editing-a-label": "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", + "/enterprise/2.16/github/managing-your-work-on-github/editing-a-label": "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label", + "/enterprise/2.16/user/managing-your-work-on-github/editing-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/editing-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", + "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", + "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", + "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", + "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", + "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", + "/enterprise/2.16/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", + "/enterprise/2.16/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", + "/enterprise/2.16/user/managing-your-work-on-github/finding-information-in-a-repository": "/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", + "/enterprise/2.16/github/managing-your-work-on-github/finding-information-in-a-repository": "/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository", + "/enterprise/2.16/user/managing-your-work-on-github": "/enterprise/2.16/user/github/managing-your-work-on-github", + "/enterprise/2.16/github/managing-your-work-on-github": "/enterprise/2.16/user/github/managing-your-work-on-github", + "/enterprise/2.16/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/managing-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", + "/enterprise/2.16/github/managing-your-work-on-github/managing-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards", + "/enterprise/2.16/user/managing-your-work-on-github/managing-your-work-with-issues": "/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", + "/enterprise/2.16/github/managing-your-work-on-github/managing-your-work-with-issues": "/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues", + "/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", + "/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", + "/enterprise/2.16/user/managing-your-work-on-github/opening-an-issue-from-code": "/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", + "/enterprise/2.16/github/managing-your-work-on-github/opening-an-issue-from-code": "/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code", + "/enterprise/2.16/user/managing-your-work-on-github/reopening-a-closed-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/reopening-a-closed-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/sharing-filters": "/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", + "/enterprise/2.16/github/managing-your-work-on-github/sharing-filters": "/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters", + "/enterprise/2.16/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", + "/enterprise/2.16/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", + "/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", + "/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", + "/enterprise/2.16/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", + "/enterprise/2.16/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", + "/enterprise/2.16/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", + "/enterprise/2.16/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", + "/enterprise/2.16/user/managing-your-work-on-github/viewing-your-milestones-progress": "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", + "/enterprise/2.16/github/managing-your-work-on-github/viewing-your-milestones-progress": "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", + "/enterprise/2.16/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", + "/enterprise/2.16/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", + "/enterprise/2.16/user/searching-for-information-on-github/about-searching-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", + "/enterprise/2.16/github/searching-for-information-on-github/about-searching-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github", + "/enterprise/2.16/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", + "/enterprise/2.16/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", + "/enterprise/2.16/user/searching-for-information-on-github/finding-files-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", + "/enterprise/2.16/github/searching-for-information-on-github/finding-files-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github", + "/enterprise/2.16/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", + "/enterprise/2.16/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", + "/enterprise/2.16/user/searching-for-information-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github", + "/enterprise/2.16/github/searching-for-information-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github", + "/enterprise/2.16/user/searching-for-information-on-github/searching-code": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", + "/enterprise/2.16/github/searching-for-information-on-github/searching-code": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-code", + "/enterprise/2.16/user/searching-for-information-on-github/searching-commits": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", + "/enterprise/2.16/github/searching-for-information-on-github/searching-commits": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits", + "/enterprise/2.16/user/searching-for-information-on-github/searching-for-repositories": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", + "/enterprise/2.16/github/searching-for-information-on-github/searching-for-repositories": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories", + "/enterprise/2.16/user/searching-for-information-on-github/searching-in-forks": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", + "/enterprise/2.16/github/searching-for-information-on-github/searching-in-forks": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks", + "/enterprise/2.16/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", + "/enterprise/2.16/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", + "/enterprise/2.16/user/searching-for-information-on-github/searching-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", + "/enterprise/2.16/github/searching-for-information-on-github/searching-on-github": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github", + "/enterprise/2.16/user/searching-for-information-on-github/searching-topics": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", + "/enterprise/2.16/github/searching-for-information-on-github/searching-topics": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics", + "/enterprise/2.16/user/searching-for-information-on-github/searching-users": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", + "/enterprise/2.16/github/searching-for-information-on-github/searching-users": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-users", + "/enterprise/2.16/user/searching-for-information-on-github/searching-wikis": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", + "/enterprise/2.16/github/searching-for-information-on-github/searching-wikis": "/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis", + "/enterprise/2.16/user/searching-for-information-on-github/sorting-search-results": "/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", + "/enterprise/2.16/github/searching-for-information-on-github/sorting-search-results": "/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results", + "/enterprise/2.16/user/searching-for-information-on-github/troubleshooting-search-queries": "/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", + "/enterprise/2.16/github/searching-for-information-on-github/troubleshooting-search-queries": "/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries", + "/enterprise/2.16/user/searching-for-information-on-github/understanding-the-search-syntax": "/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", + "/enterprise/2.16/github/searching-for-information-on-github/understanding-the-search-syntax": "/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-teams": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-teams": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", + "/enterprise/2.16/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", + "/enterprise/2.16/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/about-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/about-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", + "/enterprise/2.16/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", + "/enterprise/2.16/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", + "/enterprise/2.16/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", + "/enterprise/2.16/user/site-policy/github-insights-and-data-protection-for-your-organization": "/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", + "/enterprise/2.16/github/site-policy/github-insights-and-data-protection-for-your-organization": "/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization", + "/enterprise/2.16/user/using-git/about-git-rebase": "/enterprise/2.16/user/github/using-git/about-git-rebase", + "/enterprise/2.16/github/using-git/about-git-rebase": "/enterprise/2.16/user/github/using-git/about-git-rebase", + "/enterprise/2.16/user/using-git/about-git-subtree-merges": "/enterprise/2.16/user/github/using-git/about-git-subtree-merges", + "/enterprise/2.16/github/using-git/about-git-subtree-merges": "/enterprise/2.16/user/github/using-git/about-git-subtree-merges", + "/enterprise/2.16/user/using-git/about-remote-repositories": "/enterprise/2.16/user/github/using-git/about-remote-repositories", + "/enterprise/2.16/github/using-git/about-remote-repositories": "/enterprise/2.16/user/github/using-git/about-remote-repositories", + "/enterprise/2.16/user/using-git/adding-a-remote": "/enterprise/2.16/user/github/using-git/adding-a-remote", + "/enterprise/2.16/github/using-git/adding-a-remote": "/enterprise/2.16/user/github/using-git/adding-a-remote", + "/enterprise/2.16/user/using-git/associating-text-editors-with-git": "/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", + "/enterprise/2.16/github/using-git/associating-text-editors-with-git": "/enterprise/2.16/user/github/using-git/associating-text-editors-with-git", + "/enterprise/2.16/user/using-git/caching-your-github-password-in-git": "/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", + "/enterprise/2.16/github/using-git/caching-your-github-password-in-git": "/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git", + "/enterprise/2.16/user/using-git/changing-a-remotes-url": "/enterprise/2.16/user/github/using-git/changing-a-remotes-url", + "/enterprise/2.16/github/using-git/changing-a-remotes-url": "/enterprise/2.16/user/github/using-git/changing-a-remotes-url", + "/enterprise/2.16/user/using-git/changing-author-info": "/enterprise/2.16/user/github/using-git/changing-author-info", + "/enterprise/2.16/github/using-git/changing-author-info": "/enterprise/2.16/user/github/using-git/changing-author-info", + "/enterprise/2.16/user/using-git/configuring-git-to-handle-line-endings": "/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", + "/enterprise/2.16/github/using-git/configuring-git-to-handle-line-endings": "/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings", + "/enterprise/2.16/user/using-git/dealing-with-non-fast-forward-errors": "/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", + "/enterprise/2.16/github/using-git/dealing-with-non-fast-forward-errors": "/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors", + "/enterprise/2.16/user/using-git/getting-changes-from-a-remote-repository": "/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", + "/enterprise/2.16/github/using-git/getting-changes-from-a-remote-repository": "/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository", + "/enterprise/2.16/user/using-git/getting-started-with-git-and-github": "/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", + "/enterprise/2.16/github/using-git/getting-started-with-git-and-github": "/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github", + "/enterprise/2.16/user/using-git/git-workflows": "/enterprise/2.16/user/github/using-git/git-workflows", + "/enterprise/2.16/github/using-git/git-workflows": "/enterprise/2.16/user/github/using-git/git-workflows", + "/enterprise/2.16/user/using-git/ignoring-files": "/enterprise/2.16/user/github/using-git/ignoring-files", + "/enterprise/2.16/github/using-git/ignoring-files": "/enterprise/2.16/user/github/using-git/ignoring-files", + "/enterprise/2.16/user/using-git": "/enterprise/2.16/user/github/using-git", + "/enterprise/2.16/github/using-git": "/enterprise/2.16/user/github/using-git", + "/enterprise/2.16/user/using-git/learning-about-git": "/enterprise/2.16/user/github/using-git/learning-about-git", + "/enterprise/2.16/github/using-git/learning-about-git": "/enterprise/2.16/user/github/using-git/learning-about-git", + "/enterprise/2.16/user/using-git/managing-remote-repositories": "/enterprise/2.16/user/github/using-git/managing-remote-repositories", + "/enterprise/2.16/github/using-git/managing-remote-repositories": "/enterprise/2.16/user/github/using-git/managing-remote-repositories", + "/enterprise/2.16/user/using-git/pushing-commits-to-a-remote-repository": "/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", + "/enterprise/2.16/github/using-git/pushing-commits-to-a-remote-repository": "/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository", + "/enterprise/2.16/user/using-git/removing-a-remote": "/enterprise/2.16/user/github/using-git/removing-a-remote", + "/enterprise/2.16/github/using-git/removing-a-remote": "/enterprise/2.16/user/github/using-git/removing-a-remote", + "/enterprise/2.16/user/using-git/renaming-a-remote": "/enterprise/2.16/user/github/using-git/renaming-a-remote", + "/enterprise/2.16/github/using-git/renaming-a-remote": "/enterprise/2.16/user/github/using-git/renaming-a-remote", + "/enterprise/2.16/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", + "/enterprise/2.16/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", + "/enterprise/2.16/user/using-git/setting-your-username-in-git": "/enterprise/2.16/user/github/using-git/setting-your-username-in-git", + "/enterprise/2.16/github/using-git/setting-your-username-in-git": "/enterprise/2.16/user/github/using-git/setting-your-username-in-git", + "/enterprise/2.16/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", + "/enterprise/2.16/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", + "/enterprise/2.16/user/using-git/updating-credentials-from-the-osx-keychain": "/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", + "/enterprise/2.16/github/using-git/updating-credentials-from-the-osx-keychain": "/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain", + "/enterprise/2.16/user/using-git/using-advanced-git-commands": "/enterprise/2.16/user/github/using-git/using-advanced-git-commands", + "/enterprise/2.16/github/using-git/using-advanced-git-commands": "/enterprise/2.16/user/github/using-git/using-advanced-git-commands", + "/enterprise/2.16/user/using-git/using-common-git-commands": "/enterprise/2.16/user/github/using-git/using-common-git-commands", + "/enterprise/2.16/github/using-git/using-common-git-commands": "/enterprise/2.16/user/github/using-git/using-common-git-commands", + "/enterprise/2.16/user/using-git/using-git-rebase-on-the-command-line": "/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", + "/enterprise/2.16/github/using-git/using-git-rebase-on-the-command-line": "/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line", + "/enterprise/2.16/user/using-git/which-remote-url-should-i-use": "/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", + "/enterprise/2.16/github/using-git/which-remote-url-should-i-use": "/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use", + "/enterprise/2.16/user/using-git/why-is-git-always-asking-for-my-password": "/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", + "/enterprise/2.16/github/using-git/why-is-git-always-asking-for-my-password": "/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", + "/enterprise/2.16/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", + "/enterprise/2.16/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", + "/enterprise/2.16/user/working-with-github-pages/about-github-pages-and-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", + "/enterprise/2.16/github/working-with-github-pages/about-github-pages-and-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll", + "/enterprise/2.16/user/working-with-github-pages/about-github-pages": "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", + "/enterprise/2.16/github/working-with-github-pages/about-github-pages": "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages", + "/enterprise/2.16/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.16/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.16/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", + "/enterprise/2.16/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", + "/enterprise/2.16/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", + "/enterprise/2.16/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", + "/enterprise/2.16/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", + "/enterprise/2.16/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", + "/enterprise/2.16/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", + "/enterprise/2.16/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", + "/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", + "/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", + "/enterprise/2.16/user/working-with-github-pages/creating-a-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", + "/enterprise/2.16/github/working-with-github-pages/creating-a-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site", + "/enterprise/2.16/user/working-with-github-pages/getting-started-with-github-pages": "/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", + "/enterprise/2.16/github/working-with-github-pages/getting-started-with-github-pages": "/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages", + "/enterprise/2.16/user/working-with-github-pages": "/enterprise/2.16/user/github/working-with-github-pages", + "/enterprise/2.16/github/working-with-github-pages": "/enterprise/2.16/user/github/working-with-github-pages", + "/enterprise/2.16/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", + "/enterprise/2.16/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", + "/enterprise/2.16/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", + "/enterprise/2.16/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", + "/enterprise/2.16/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", + "/enterprise/2.16/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", + "/enterprise/2.16/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.16/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.16/user/working-with-github-pages/unpublishing-a-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", + "/enterprise/2.16/github/working-with-github-pages/unpublishing-a-github-pages-site": "/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site", + "/enterprise/2.16/user/writing-on-github/about-saved-replies": "/enterprise/2.16/user/github/writing-on-github/about-saved-replies", + "/enterprise/2.16/github/writing-on-github/about-saved-replies": "/enterprise/2.16/user/github/writing-on-github/about-saved-replies", + "/enterprise/2.16/user/writing-on-github/about-writing-and-formatting-on-github": "/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", + "/enterprise/2.16/github/writing-on-github/about-writing-and-formatting-on-github": "/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github", + "/enterprise/2.16/user/writing-on-github/autolinked-references-and-urls": "/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", + "/enterprise/2.16/github/writing-on-github/autolinked-references-and-urls": "/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls", + "/enterprise/2.16/user/writing-on-github/basic-writing-and-formatting-syntax": "/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", + "/enterprise/2.16/github/writing-on-github/basic-writing-and-formatting-syntax": "/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax", + "/enterprise/2.16/user/writing-on-github/creating-a-saved-reply": "/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", + "/enterprise/2.16/github/writing-on-github/creating-a-saved-reply": "/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply", + "/enterprise/2.16/user/writing-on-github/creating-and-highlighting-code-blocks": "/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", + "/enterprise/2.16/github/writing-on-github/creating-and-highlighting-code-blocks": "/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks", + "/enterprise/2.16/user/writing-on-github/creating-gists": "/enterprise/2.16/user/github/writing-on-github/creating-gists", + "/enterprise/2.16/github/writing-on-github/creating-gists": "/enterprise/2.16/user/github/writing-on-github/creating-gists", + "/enterprise/2.16/user/writing-on-github/deleting-a-saved-reply": "/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", + "/enterprise/2.16/github/writing-on-github/deleting-a-saved-reply": "/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply", + "/enterprise/2.16/user/writing-on-github/editing-a-saved-reply": "/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", + "/enterprise/2.16/github/writing-on-github/editing-a-saved-reply": "/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply", + "/enterprise/2.16/user/writing-on-github/editing-and-sharing-content-with-gists": "/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", + "/enterprise/2.16/github/writing-on-github/editing-and-sharing-content-with-gists": "/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists", + "/enterprise/2.16/user/writing-on-github/forking-and-cloning-gists": "/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", + "/enterprise/2.16/github/writing-on-github/forking-and-cloning-gists": "/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists", + "/enterprise/2.16/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", + "/enterprise/2.16/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", + "/enterprise/2.16/user/writing-on-github": "/enterprise/2.16/user/github/writing-on-github", + "/enterprise/2.16/github/writing-on-github": "/enterprise/2.16/user/github/writing-on-github", + "/enterprise/2.16/user/writing-on-github/organizing-information-with-tables": "/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", + "/enterprise/2.16/github/writing-on-github/organizing-information-with-tables": "/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables", + "/enterprise/2.16/user/writing-on-github/using-saved-replies": "/enterprise/2.16/user/github/writing-on-github/using-saved-replies", + "/enterprise/2.16/github/writing-on-github/using-saved-replies": "/enterprise/2.16/user/github/writing-on-github/using-saved-replies", + "/enterprise/2.16/user/writing-on-github/working-with-advanced-formatting": "/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", + "/enterprise/2.16/github/writing-on-github/working-with-advanced-formatting": "/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting", + "/enterprise/2.16/user/writing-on-github/working-with-saved-replies": "/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", + "/enterprise/2.16/github/writing-on-github/working-with-saved-replies": "/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies", + "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise": "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise", + "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", + "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", + "/enterprise/2.16/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", + "/enterprise/2.16/insights": "/enterprise/2.16/user/insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/about-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", + "/enterprise/2.16/insights/installing-and-configuring-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/installing-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-events": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-organizations": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/managing-repositories": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", + "/enterprise/2.16/insights/installing-and-configuring-github-insights/updating-github-insights": "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights", + "/enterprise/2.16/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": null, + "/enterprise/2.16/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": null, + "/enterprise/2.16/admin/articles/receiving-security-alerts-for-vulnerable-dependencies-on-github-enterprise": null, + "/enterprise/2.16/admin/articles/using-github-task-runner": null, + "/enterprise/2.16/admin/clustering/about-cluster-nodes": null, + "/enterprise/2.16/admin/clustering/cluster-network-configuration": null, + "/enterprise/2.16/admin/clustering/clustering-overview": null, + "/enterprise/2.16/admin/clustering/differences-between-clustering-and-high-availability-ha": null, + "/enterprise/2.16/admin/clustering/evacuating-a-cluster-node": null, + "/enterprise/2.16/admin/clustering": null, + "/enterprise/2.16/admin/clustering/initializing-the-cluster": null, + "/enterprise/2.16/admin/clustering/managing-a-github-enterprise-server-cluster": null, + "/enterprise/2.16/admin/clustering/monitoring-cluster-nodes": null, + "/enterprise/2.16/admin/clustering/replacing-a-cluster-node": null, + "/enterprise/2.16/admin/clustering/setting-up-the-cluster-instances": null, + "/enterprise/2.16/admin/clustering/upgrading-a-cluster": null, + "/enterprise/2.16/admin/developer-workflow/about-pre-receive-hooks": null, + "/enterprise/2.16/admin/developer-workflow/about-protected-branches-and-required-status-checks": null, + "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-on-your-appliance": null, + "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-a-repository": null, + "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": null, + "/enterprise/2.16/admin/developer-workflow/blocking-force-pushes": null, + "/enterprise/2.16/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": null, + "/enterprise/2.16/admin/developer-workflow/continuous-integration-using-jenkins": null, + "/enterprise/2.16/admin/developer-workflow/continuous-integration-using-travis-ci": null, + "/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-environment": null, + "/enterprise/2.16/admin/developer-workflow/creating-a-pre-receive-hook-script": null, + "/enterprise/2.16/admin/developer-workflow/customizing-your-instance-with-integrations": null, + "/enterprise/2.16/admin/developer-workflow/establishing-pull-request-merge-conditions": null, + "/enterprise/2.16/admin/developer-workflow": null, + "/enterprise/2.16/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": null, + "/enterprise/2.16/admin/developer-workflow/managing-projects-using-jira": null, + "/enterprise/2.16/admin/developer-workflow/troubleshooting-service-hooks": null, + "/enterprise/2.16/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": null, + "/enterprise/2.16/admin/developer-workflow/using-webhooks-for-continuous-integration": null, + "/enterprise/2.16/admin/enterprise-support/about-github-enterprise-support": null, + "/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": null, + "/enterprise/2.16/admin/enterprise-support/about-github-premium-support-for-github-enterprise": null, + "/enterprise/2.16/admin/enterprise-support/about-support-for-advanced-security": null, + "/enterprise/2.16/admin/enterprise-support": null, + "/enterprise/2.16/admin/enterprise-support/preparing-to-submit-a-ticket": null, + "/enterprise/2.16/admin/enterprise-support/providing-data-to-github-support": null, + "/enterprise/2.16/admin/enterprise-support/reaching-github-support": null, + "/enterprise/2.16/admin/enterprise-support/receiving-help-from-github-support": null, + "/enterprise/2.16/admin/enterprise-support/submitting-a-ticket": null, + "/enterprise/2.16/admin": null, + "/enterprise/2.16/admin/installation/about-geo-replication": null, + "/enterprise/2.16/admin/installation/about-high-availability-configuration": null, + "/enterprise/2.16/admin/installation/about-the-github-enterprise-server-api": null, + "/enterprise/2.16/admin/installation/accessing-the-administrative-shell-ssh": null, + "/enterprise/2.16/admin/installation/accessing-the-management-console": null, + "/enterprise/2.16/admin/installation/accessing-the-monitor-dashboard": null, + "/enterprise/2.16/admin/installation/activity-dashboard": null, + "/enterprise/2.16/admin/installation/audit-logging": null, + "/enterprise/2.16/admin/installation/audited-actions": null, + "/enterprise/2.16/admin/installation/command-line-utilities": null, + "/enterprise/2.16/admin/installation/configuring-a-hostname": null, + "/enterprise/2.16/admin/installation/configuring-an-outbound-web-proxy-server": null, + "/enterprise/2.16/admin/installation/configuring-applications": null, + "/enterprise/2.16/admin/installation/configuring-backups-on-your-appliance": null, + "/enterprise/2.16/admin/installation/configuring-built-in-firewall-rules": null, + "/enterprise/2.16/admin/installation/configuring-collectd": null, + "/enterprise/2.16/admin/installation/configuring-dns-nameservers": null, + "/enterprise/2.16/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": null, + "/enterprise/2.16/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": null, + "/enterprise/2.16/admin/installation/configuring-git-large-file-storage": null, + "/enterprise/2.16/admin/installation/configuring-github-enterprise-server-for-high-availability": null, + "/enterprise/2.16/admin/installation/configuring-github-pages-on-your-appliance": null, + "/enterprise/2.16/admin/installation/configuring-rate-limits": null, + "/enterprise/2.16/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": null, + "/enterprise/2.16/admin/installation/configuring-the-github-enterprise-server-appliance": null, + "/enterprise/2.16/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": null, + "/enterprise/2.16/admin/installation/configuring-time-synchronization": null, + "/enterprise/2.16/admin/installation/configuring-tls": null, + "/enterprise/2.16/admin/installation/configuring-your-github-enterprise-server-network-settings": null, + "/enterprise/2.16/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": null, + "/enterprise/2.16/admin/installation/creating-a-high-availability-replica": null, + "/enterprise/2.16/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": null, + "/enterprise/2.16/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": null, + "/enterprise/2.16/admin/installation/enabling-and-scheduling-maintenance-mode": null, + "/enterprise/2.16/admin/installation/enabling-automatic-update-checks": null, + "/enterprise/2.16/admin/installation/enabling-private-mode": null, + "/enterprise/2.16/admin/installation/enabling-subdomain-isolation": null, + "/enterprise/2.16/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.16/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.16/admin/installation/increasing-cpu-or-memory-resources": null, + "/enterprise/2.16/admin/installation/increasing-storage-capacity": null, + "/enterprise/2.16/admin/installation": null, + "/enterprise/2.16/admin/installation/initiating-a-failover-to-your-replica-appliance": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-aws": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-azure": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-hyper-v": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-openstack-kvm": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-vmware": null, + "/enterprise/2.16/admin/installation/installing-github-enterprise-server-on-xenserver": null, + "/enterprise/2.16/admin/installation/log-forwarding": null, + "/enterprise/2.16/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": null, + "/enterprise/2.16/admin/installation/managing-your-github-enterprise-server-license": null, + "/enterprise/2.16/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": null, + "/enterprise/2.16/admin/installation/migrating-from-github-enterprise-1110x-to-2123": null, + "/enterprise/2.16/admin/installation/migrating-to-a-different-git-large-file-storage-server": null, + "/enterprise/2.16/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": null, + "/enterprise/2.16/admin/installation/monitoring-using-snmp": null, + "/enterprise/2.16/admin/installation/monitoring-your-github-enterprise-server-appliance": null, + "/enterprise/2.16/admin/installation/network-ports": null, + "/enterprise/2.16/admin/installation/recommended-alert-thresholds": null, + "/enterprise/2.16/admin/installation/recovering-a-high-availability-configuration": null, + "/enterprise/2.16/admin/installation/removing-a-high-availability-replica": null, + "/enterprise/2.16/admin/installation/searching-the-audit-log": null, + "/enterprise/2.16/admin/installation/setting-git-push-limits": null, + "/enterprise/2.16/admin/installation/setting-up-a-github-enterprise-server-instance": null, + "/enterprise/2.16/admin/installation/setting-up-a-staging-instance": null, + "/enterprise/2.16/admin/installation/setting-up-external-monitoring": null, + "/enterprise/2.16/admin/installation/site-admin-dashboard": null, + "/enterprise/2.16/admin/installation/system-overview": null, + "/enterprise/2.16/admin/installation/troubleshooting-ssl-errors": null, + "/enterprise/2.16/admin/installation/updating-the-virtual-machine-and-physical-resources": null, + "/enterprise/2.16/admin/installation/upgrade-requirements": null, + "/enterprise/2.16/admin/installation/upgrading-github-enterprise-server": null, + "/enterprise/2.16/admin/installation/using-github-enterprise-server-with-a-load-balancer": null, + "/enterprise/2.16/admin/installation/validating-your-domain-settings": null, + "/enterprise/2.16/admin/installation/viewing-push-logs": null, + "/enterprise/2.16/admin/migrations/about-migrations": null, + "/enterprise/2.16/admin/migrations/applying-the-imported-data-on-github-enterprise-server": null, + "/enterprise/2.16/admin/migrations/completing-the-import-on-github-enterprise-server": null, + "/enterprise/2.16/admin/migrations/exporting-migration-data-from-github-enterprise-server": null, + "/enterprise/2.16/admin/migrations/exporting-migration-data-from-githubcom": null, + "/enterprise/2.16/admin/migrations/exporting-the-github-enterprise-server-source-repositories": null, + "/enterprise/2.16/admin/migrations/exporting-the-githubcom-organizations-repositories": null, + "/enterprise/2.16/admin/migrations/generating-a-list-of-migration-conflicts": null, + "/enterprise/2.16/admin/migrations/importing-data-from-third-party-version-control-systems": null, + "/enterprise/2.16/admin/migrations/importing-migration-data-to-github-enterprise-server": null, + "/enterprise/2.16/admin/migrations": null, + "/enterprise/2.16/admin/migrations/preparing-the-github-enterprise-server-source-instance": null, + "/enterprise/2.16/admin/migrations/preparing-the-githubcom-source-organization": null, + "/enterprise/2.16/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": null, + "/enterprise/2.16/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": null, + "/enterprise/2.16/admin/migrations/reviewing-migration-conflicts": null, + "/enterprise/2.16/admin/migrations/reviewing-migration-data": null, + "/enterprise/2.16/admin/user-management/about-global-webhooks": null, + "/enterprise/2.16/admin/user-management/adding-people-to-teams": null, + "/enterprise/2.16/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": null, + "/enterprise/2.16/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": null, + "/enterprise/2.16/admin/user-management/archiving-and-unarchiving-repositories": null, + "/enterprise/2.16/admin/user-management/auditing-ssh-keys": null, + "/enterprise/2.16/admin/user-management/auditing-users-across-your-instance": null, + "/enterprise/2.16/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": null, + "/enterprise/2.16/admin/user-management/basic-account-settings": null, + "/enterprise/2.16/admin/user-management/best-practices-for-user-security": null, + "/enterprise/2.16/admin/user-management/changing-authentication-methods": null, + "/enterprise/2.16/admin/user-management/configuring-email-for-notifications": null, + "/enterprise/2.16/admin/user-management/configuring-visibility-for-organization-membership": null, + "/enterprise/2.16/admin/user-management/creating-organizations": null, + "/enterprise/2.16/admin/user-management/creating-teams": null, + "/enterprise/2.16/admin/user-management/customizing-user-messages-on-your-instance": null, + "/enterprise/2.16/admin/user-management/disabling-unauthenticated-sign-ups": null, + "/enterprise/2.16/admin/user-management": null, + "/enterprise/2.16/admin/user-management/managing-dormant-users": null, + "/enterprise/2.16/admin/user-management/managing-global-webhooks": null, + "/enterprise/2.16/admin/user-management/organizations-and-teams": null, + "/enterprise/2.16/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": null, + "/enterprise/2.16/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": null, + "/enterprise/2.16/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": null, + "/enterprise/2.16/admin/user-management/preventing-users-from-creating-organizations": null, + "/enterprise/2.16/admin/user-management/preventing-users-from-deleting-organization-repositories": null, + "/enterprise/2.16/admin/user-management/promoting-or-demoting-a-site-administrator": null, + "/enterprise/2.16/admin/user-management/rebuilding-contributions-data": null, + "/enterprise/2.16/admin/user-management/removing-users-from-teams-and-organizations": null, + "/enterprise/2.16/admin/user-management/repositories": null, + "/enterprise/2.16/admin/user-management/requiring-two-factor-authentication-for-an-organization": null, + "/enterprise/2.16/admin/user-management/restricting-repository-creation-in-your-instance": null, + "/enterprise/2.16/admin/user-management/suspending-and-unsuspending-users": null, + "/enterprise/2.16/admin/user-management/user-security": null, + "/enterprise/2.16/admin/user-management/using-built-in-authentication": null, + "/enterprise/2.16/admin/user-management/using-cas": null, + "/enterprise/2.16/admin/user-management/using-ldap": null, + "/enterprise/2.16/admin/user-management/using-saml": null, + "/enterprise/2.16": null, + "/enterprise/2.16/user/github/administering-a-repository/about-branch-restrictions": null, + "/enterprise/2.16/user/github/administering-a-repository/about-merge-methods-on-github": null, + "/enterprise/2.16/user/github/administering-a-repository/about-protected-branches": null, + "/enterprise/2.16/user/github/administering-a-repository/about-releases": null, + "/enterprise/2.16/user/github/administering-a-repository/about-required-commit-signing": null, + "/enterprise/2.16/user/github/administering-a-repository/about-required-reviews-for-pull-requests": null, + "/enterprise/2.16/user/github/administering-a-repository/about-required-status-checks": null, + "/enterprise/2.16/user/github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization": null, + "/enterprise/2.16/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters": null, + "/enterprise/2.16/user/github/administering-a-repository/classifying-your-repository-with-topics": null, + "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": null, + "/enterprise/2.16/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": null, + "/enterprise/2.16/user/github/administering-a-repository/configuring-protected-branches": null, + "/enterprise/2.16/user/github/administering-a-repository/configuring-pull-request-merges": null, + "/enterprise/2.16/user/github/administering-a-repository/creating-releases": null, + "/enterprise/2.16/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github": null, + "/enterprise/2.16/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests": null, + "/enterprise/2.16/user/github/administering-a-repository/deleting-a-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": null, + "/enterprise/2.16/user/github/administering-a-repository/editing-and-deleting-releases": null, + "/enterprise/2.16/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/enabling-branch-restrictions": null, + "/enterprise/2.16/user/github/administering-a-repository/enabling-required-commit-signing": null, + "/enterprise/2.16/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests": null, + "/enterprise/2.16/user/github/administering-a-repository/enabling-required-status-checks": null, + "/enterprise/2.16/user/github/administering-a-repository/getting-the-download-count-for-your-releases": null, + "/enterprise/2.16/user/github/administering-a-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/linking-to-releases": null, + "/enterprise/2.16/user/github/administering-a-repository/managing-branches-in-your-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/managing-releases-in-a-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/managing-repository-settings": null, + "/enterprise/2.16/user/github/administering-a-repository/renaming-a-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/setting-repository-visibility": null, + "/enterprise/2.16/user/github/administering-a-repository/setting-the-default-branch": null, + "/enterprise/2.16/user/github/administering-a-repository/transferring-a-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/types-of-required-status-checks": null, + "/enterprise/2.16/user/github/administering-a-repository/viewing-branches-in-your-repository": null, + "/enterprise/2.16/user/github/administering-a-repository/viewing-your-repositorys-tags": null, + "/enterprise/2.16/user/github/authenticating-to-github/about-commit-signature-verification": null, + "/enterprise/2.16/user/github/authenticating-to-github/about-ssh": null, + "/enterprise/2.16/user/github/authenticating-to-github/about-two-factor-authentication": null, + "/enterprise/2.16/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication": null, + "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": null, + "/enterprise/2.16/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": null, + "/enterprise/2.16/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key": null, + "/enterprise/2.16/user/github/authenticating-to-github/authorizing-oauth-apps": null, + "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-gpg-keys": null, + "/enterprise/2.16/user/github/authenticating-to-github/checking-for-existing-ssh-keys": null, + "/enterprise/2.16/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": null, + "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": null, + "/enterprise/2.16/user/github/authenticating-to-github/configuring-two-factor-authentication": null, + "/enterprise/2.16/user/github/authenticating-to-github/connecting-to-github-with-ssh": null, + "/enterprise/2.16/user/github/authenticating-to-github/connecting-with-third-party-applications": null, + "/enterprise/2.16/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": null, + "/enterprise/2.16/user/github/authenticating-to-github/creating-a-strong-password": null, + "/enterprise/2.16/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-bad-file-number": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-key-already-in-use": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-permission-denied-publickey": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-ssh-add-illegal-option----k": null, + "/enterprise/2.16/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": null, + "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key": null, + "/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": null, + "/enterprise/2.16/user/github/authenticating-to-github": null, + "/enterprise/2.16/user/github/authenticating-to-github/keeping-your-account-and-data-secure": null, + "/enterprise/2.16/user/github/authenticating-to-github/managing-commit-signature-verification": null, + "/enterprise/2.16/user/github/authenticating-to-github/preventing-unauthorized-access": null, + "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": null, + "/enterprise/2.16/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase": null, + "/enterprise/2.16/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository": null, + "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": null, + "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-authorized-integrations": null, + "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-deploy-keys": null, + "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-security-log": null, + "/enterprise/2.16/user/github/authenticating-to-github/reviewing-your-ssh-keys": null, + "/enterprise/2.16/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": null, + "/enterprise/2.16/user/github/authenticating-to-github/signing-commits": null, + "/enterprise/2.16/user/github/authenticating-to-github/signing-tags": null, + "/enterprise/2.16/user/github/authenticating-to-github/sudo-mode": null, + "/enterprise/2.16/user/github/authenticating-to-github/telling-git-about-your-signing-key": null, + "/enterprise/2.16/user/github/authenticating-to-github/testing-your-ssh-connection": null, + "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-commit-signature-verification": null, + "/enterprise/2.16/user/github/authenticating-to-github/troubleshooting-ssh": null, + "/enterprise/2.16/user/github/authenticating-to-github/updating-an-expired-gpg-key": null, + "/enterprise/2.16/user/github/authenticating-to-github/updating-your-github-access-credentials": null, + "/enterprise/2.16/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": null, + "/enterprise/2.16/user/github/authenticating-to-github/working-with-ssh-key-passphrases": null, + "/enterprise/2.16/user/github/building-a-strong-community/about-issue-and-pull-request-templates": null, + "/enterprise/2.16/user/github/building-a-strong-community/about-team-discussions": null, + "/enterprise/2.16/user/github/building-a-strong-community/about-wikis": null, + "/enterprise/2.16/user/github/building-a-strong-community/adding-a-license-to-a-repository": null, + "/enterprise/2.16/user/github/building-a-strong-community/adding-or-editing-wiki-pages": null, + "/enterprise/2.16/user/github/building-a-strong-community/adding-support-resources-to-your-project": null, + "/enterprise/2.16/user/github/building-a-strong-community/changing-access-permissions-for-wikis": null, + "/enterprise/2.16/user/github/building-a-strong-community/collaborating-with-your-team": null, + "/enterprise/2.16/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository": null, + "/enterprise/2.16/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": null, + "/enterprise/2.16/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": null, + "/enterprise/2.16/user/github/building-a-strong-community/creating-a-team-discussion": null, + "/enterprise/2.16/user/github/building-a-strong-community/disabling-wikis": null, + "/enterprise/2.16/user/github/building-a-strong-community/documenting-your-project-with-wikis": null, + "/enterprise/2.16/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion": null, + "/enterprise/2.16/user/github/building-a-strong-community/editing-wiki-content": null, + "/enterprise/2.16/user/github/building-a-strong-community": null, + "/enterprise/2.16/user/github/building-a-strong-community/locking-conversations": null, + "/enterprise/2.16/user/github/building-a-strong-community/managing-disruptive-comments": null, + "/enterprise/2.16/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": null, + "/enterprise/2.16/user/github/building-a-strong-community/moderating-comments-and-conversations": null, + "/enterprise/2.16/user/github/building-a-strong-community/pinning-a-team-discussion": null, + "/enterprise/2.16/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors": null, + "/enterprise/2.16/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": null, + "/enterprise/2.16/user/github/building-a-strong-community/tracking-changes-in-a-comment": null, + "/enterprise/2.16/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-branches": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-forks": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/about-status-checks": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/github-flow": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-forks": null, + "/enterprise/2.16/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/changing-a-commit-message": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/comparing-commits-across-time": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/creating-and-editing-commits": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/differences-between-commit-views": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/troubleshooting-commits": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/viewing-and-comparing-commits": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": null, + "/enterprise/2.16/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-code-owners": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-readmes": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repositories": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/about-repository-languages": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/archiving-repositories": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository": null, + "/enterprise/2.16/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": null, + "/enterprise/2.16/user/github/extending-github/about-webhooks": null, + "/enterprise/2.16/user/github/extending-github/getting-started-with-the-api": null, + "/enterprise/2.16/user/github/extending-github/git-automation-with-oauth-tokens": null, + "/enterprise/2.16/user/github/extending-github": null, + "/enterprise/2.16/user/github/getting-started-with-github/access-permissions-on-github": null, + "/enterprise/2.16/user/github/getting-started-with-github/be-social": null, + "/enterprise/2.16/user/github/getting-started-with-github/create-a-repo": null, + "/enterprise/2.16/user/github/getting-started-with-github/exploring-projects-on-github": null, + "/enterprise/2.16/user/github/getting-started-with-github/following-people": null, + "/enterprise/2.16/user/github/getting-started-with-github/fork-a-repo": null, + "/enterprise/2.16/user/github/getting-started-with-github/git-and-github-learning-resources": null, + "/enterprise/2.16/user/github/getting-started-with-github/git-cheatsheet": null, + "/enterprise/2.16/user/github/getting-started-with-github/github-glossary": null, + "/enterprise/2.16/user/github/getting-started-with-github": null, + "/enterprise/2.16/user/github/getting-started-with-github/keyboard-shortcuts": null, + "/enterprise/2.16/user/github/getting-started-with-github/learning-about-github": null, + "/enterprise/2.16/user/github/getting-started-with-github/saving-repositories-with-stars": null, + "/enterprise/2.16/user/github/getting-started-with-github/set-up-git": null, + "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": null, + "/enterprise/2.16/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": null, + "/enterprise/2.16/user/github/getting-started-with-github/signing-up-for-github": null, + "/enterprise/2.16/user/github/getting-started-with-github/supported-browsers": null, + "/enterprise/2.16/user/github/getting-started-with-github/types-of-github-accounts": null, + "/enterprise/2.16/user/github/getting-started-with-github/using-github": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/importing-source-code-to-github": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/source-code-migration-tools": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/support-for-subversion-clients": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": null, + "/enterprise/2.16/user/github/importing-your-projects-to-github/working-with-subversion-on-github": null, + "/enterprise/2.16/user/github": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/3d-file-viewer": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/creating-new-files": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/deleting-files": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/editing-files-in-your-repository": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/getting-permanent-links-to-files": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-on-github": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/managing-files-using-the-command-line": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/renaming-a-file": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-and-diffing-images": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/rendering-pdf-documents": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/tracking-changes-in-a-file": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": null, + "/enterprise/2.16/user/github/managing-files-in-a-repository/working-with-non-code-files": null, + "/enterprise/2.16/user/github/managing-large-files/about-git-large-file-storage": null, + "/enterprise/2.16/user/github/managing-large-files/collaboration-with-git-large-file-storage": null, + "/enterprise/2.16/user/github/managing-large-files/conditions-for-large-files": null, + "/enterprise/2.16/user/github/managing-large-files/configuring-git-large-file-storage": null, + "/enterprise/2.16/user/github/managing-large-files/distributing-large-binaries": null, + "/enterprise/2.16/user/github/managing-large-files": null, + "/enterprise/2.16/user/github/managing-large-files/installing-git-large-file-storage": null, + "/enterprise/2.16/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": null, + "/enterprise/2.16/user/github/managing-large-files/removing-files-from-a-repositorys-history": null, + "/enterprise/2.16/user/github/managing-large-files/removing-files-from-git-large-file-storage": null, + "/enterprise/2.16/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures": null, + "/enterprise/2.16/user/github/managing-large-files/versioning-large-files": null, + "/enterprise/2.16/user/github/managing-large-files/working-with-large-files": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-automation-for-project-boards": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-issues": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-labels": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-milestones": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-project-boards": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/about-task-lists": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/adding-notes-to-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/changing-project-board-visibility": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/closing-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/configuring-automation-for-project-boards": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-label": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/creating-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/creating-an-issue": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-label": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/deleting-an-issue": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-issues": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-label": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/editing-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/finding-information-in-a-repository": null, + "/enterprise/2.16/user/github/managing-your-work-on-github": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/managing-project-boards": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/managing-your-work-with-issues": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/opening-an-issue-from-code": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/reopening-a-closed-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/sharing-filters": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/managing-your-work-on-github/viewing-your-milestones-progress": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-email-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/about-web-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": null, + "/enterprise/2.16/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/about-searching-on-github": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/finding-files-on-github": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/getting-started-with-searching-on-github": null, + "/enterprise/2.16/user/github/searching-for-information-on-github": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-code": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-commits": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-for-repositories": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-in-forks": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-issues-and-pull-requests": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-on-github": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-topics": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-users": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/searching-wikis": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/sorting-search-results": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/troubleshooting-search-queries": null, + "/enterprise/2.16/user/github/searching-for-information-on-github/understanding-the-search-syntax": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-organizations": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-teams": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": null, + "/enterprise/2.16/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/about-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": null, + "/enterprise/2.16/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": null, + "/enterprise/2.16/user/github/site-policy/github-insights-and-data-protection-for-your-organization": null, + "/enterprise/2.16/user/github/using-git/about-git-rebase": null, + "/enterprise/2.16/user/github/using-git/about-git-subtree-merges": null, + "/enterprise/2.16/user/github/using-git/about-remote-repositories": null, + "/enterprise/2.16/user/github/using-git/adding-a-remote": null, + "/enterprise/2.16/user/github/using-git/associating-text-editors-with-git": null, + "/enterprise/2.16/user/github/using-git/caching-your-github-password-in-git": null, + "/enterprise/2.16/user/github/using-git/changing-a-remotes-url": null, + "/enterprise/2.16/user/github/using-git/changing-author-info": null, + "/enterprise/2.16/user/github/using-git/configuring-git-to-handle-line-endings": null, + "/enterprise/2.16/user/github/using-git/dealing-with-non-fast-forward-errors": null, + "/enterprise/2.16/user/github/using-git/getting-changes-from-a-remote-repository": null, + "/enterprise/2.16/user/github/using-git/getting-started-with-git-and-github": null, + "/enterprise/2.16/user/github/using-git/git-workflows": null, + "/enterprise/2.16/user/github/using-git/ignoring-files": null, + "/enterprise/2.16/user/github/using-git": null, + "/enterprise/2.16/user/github/using-git/learning-about-git": null, + "/enterprise/2.16/user/github/using-git/managing-remote-repositories": null, + "/enterprise/2.16/user/github/using-git/pushing-commits-to-a-remote-repository": null, + "/enterprise/2.16/user/github/using-git/removing-a-remote": null, + "/enterprise/2.16/user/github/using-git/renaming-a-remote": null, + "/enterprise/2.16/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase": null, + "/enterprise/2.16/user/github/using-git/setting-your-username-in-git": null, + "/enterprise/2.16/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository": null, + "/enterprise/2.16/user/github/using-git/updating-credentials-from-the-osx-keychain": null, + "/enterprise/2.16/user/github/using-git/using-advanced-git-commands": null, + "/enterprise/2.16/user/github/using-git/using-common-git-commands": null, + "/enterprise/2.16/user/github/using-git/using-git-rebase-on-the-command-line": null, + "/enterprise/2.16/user/github/using-git/which-remote-url-should-i-use": null, + "/enterprise/2.16/user/github/using-git/why-is-git-always-asking-for-my-password": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/about-repository-graphs": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": null, + "/enterprise/2.16/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": null, + "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages-and-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/about-github-pages": null, + "/enterprise/2.16/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": null, + "/enterprise/2.16/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": null, + "/enterprise/2.16/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": null, + "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/creating-a-github-pages-site": null, + "/enterprise/2.16/user/github/working-with-github-pages/getting-started-with-github-pages": null, + "/enterprise/2.16/user/github/working-with-github-pages": null, + "/enterprise/2.16/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": null, + "/enterprise/2.16/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": null, + "/enterprise/2.16/user/github/working-with-github-pages/unpublishing-a-github-pages-site": null, + "/enterprise/2.16/user/github/writing-on-github/about-saved-replies": null, + "/enterprise/2.16/user/github/writing-on-github/about-writing-and-formatting-on-github": null, + "/enterprise/2.16/user/github/writing-on-github/autolinked-references-and-urls": null, + "/enterprise/2.16/user/github/writing-on-github/basic-writing-and-formatting-syntax": null, + "/enterprise/2.16/user/github/writing-on-github/creating-a-saved-reply": null, + "/enterprise/2.16/user/github/writing-on-github/creating-and-highlighting-code-blocks": null, + "/enterprise/2.16/user/github/writing-on-github/creating-gists": null, + "/enterprise/2.16/user/github/writing-on-github/deleting-a-saved-reply": null, + "/enterprise/2.16/user/github/writing-on-github/editing-a-saved-reply": null, + "/enterprise/2.16/user/github/writing-on-github/editing-and-sharing-content-with-gists": null, + "/enterprise/2.16/user/github/writing-on-github/forking-and-cloning-gists": null, + "/enterprise/2.16/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": null, + "/enterprise/2.16/user/github/writing-on-github": null, + "/enterprise/2.16/user/github/writing-on-github/organizing-information-with-tables": null, + "/enterprise/2.16/user/github/writing-on-github/using-saved-replies": null, + "/enterprise/2.16/user/github/writing-on-github/working-with-advanced-formatting": null, + "/enterprise/2.16/user/github/writing-on-github/working-with-saved-replies": null, + "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise": null, + "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": null, + "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": null, + "/enterprise/2.16/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": null, + "/enterprise/2.16/user/insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/about-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/installing-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-events": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-organizations": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/managing-repositories": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": null, + "/enterprise/2.16/user/insights/installing-and-configuring-github-insights/updating-github-insights": null, + "/enterprise/2.17/admin/guides/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": "/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom", + "/enterprise/2.17/admin/guides/articles/including-github-enterprise-contributions-in-your-githubcom-profile": "/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile", + "/enterprise/2.17/admin/guides/articles/using-github-task-runner": "/enterprise/2.17/admin/articles/using-github-task-runner", + "/enterprise/2.17/admin/guides/clustering/about-cluster-nodes": "/enterprise/2.17/admin/clustering/about-cluster-nodes", + "/enterprise/2.17/admin/guides/clustering/about-clustering": "/enterprise/2.17/admin/clustering/about-clustering", + "/enterprise/2.17/admin/guides/clustering/cluster-network-configuration": "/enterprise/2.17/admin/clustering/cluster-network-configuration", + "/enterprise/2.17/admin/guides/clustering/differences-between-clustering-and-high-availability-ha": "/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha", + "/enterprise/2.17/admin/guides/clustering/evacuating-a-cluster-node": "/enterprise/2.17/admin/clustering/evacuating-a-cluster-node", + "/enterprise/2.17/admin/guides/clustering": "/enterprise/2.17/admin/clustering", + "/enterprise/2.17/admin/guides/clustering/initializing-the-cluster": "/enterprise/2.17/admin/clustering/initializing-the-cluster", + "/enterprise/2.17/admin/guides/clustering/managing-a-github-enterprise-server-cluster": "/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster", + "/enterprise/2.17/admin/guides/clustering/monitoring-cluster-nodes": "/enterprise/2.17/admin/clustering/monitoring-cluster-nodes", + "/enterprise/2.17/admin/guides/clustering/overview": "/enterprise/2.17/admin/clustering/overview", + "/enterprise/2.17/admin/guides/clustering/replacing-a-cluster-node": "/enterprise/2.17/admin/clustering/replacing-a-cluster-node", + "/enterprise/2.17/admin/guides/clustering/setting-up-the-cluster-instances": "/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances", + "/enterprise/2.17/admin/guides/clustering/upgrading-a-cluster": "/enterprise/2.17/admin/clustering/upgrading-a-cluster", + "/enterprise/2.17/admin/guides/developer-workflow/about-pre-receive-hooks": "/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks", + "/enterprise/2.17/admin/guides/developer-workflow/about-protected-branches-and-required-status-checks": "/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks", + "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-on-your-appliance": "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance", + "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository": "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository", + "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization", + "/enterprise/2.17/admin/guides/developer-workflow/blocking-force-pushes": "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes", + "/enterprise/2.17/admin/guides/developer-workflow/configuring-protected-branches-and-required-status-checks": "/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks", + "/enterprise/2.17/admin/guides/developer-workflow/continuous-integration-using-jenkins": "/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins", + "/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-environment": "/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment", + "/enterprise/2.17/admin/guides/developer-workflow/creating-a-pre-receive-hook-script": "/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script", + "/enterprise/2.17/admin/guides/developer-workflow/customizing-your-instance-with-integrations": "/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations", + "/enterprise/2.17/admin/guides/developer-workflow/establishing-pull-request-merge-conditions": "/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions", + "/enterprise/2.17/admin/guides/developer-workflow": "/enterprise/2.17/admin/developer-workflow", + "/enterprise/2.17/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": "/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance", + "/enterprise/2.17/admin/guides/developer-workflow/managing-projects-using-jira": "/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira", + "/enterprise/2.17/admin/guides/developer-workflow/troubleshooting-service-hooks": "/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks", + "/enterprise/2.17/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy": "/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy", + "/enterprise/2.17/admin/guides/developer-workflow/using-webhooks-for-continuous-integration": "/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration", + "/enterprise/2.17/admin/guides/enterprise-support/about-github-enterprise-support": "/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support", + "/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server": "/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server", + "/enterprise/2.17/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise": "/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise", + "/enterprise/2.17/admin/guides/enterprise-support/about-support-for-advanced-security": "/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security", + "/enterprise/2.17/admin/guides/enterprise-support": "/enterprise/2.17/admin/enterprise-support", + "/enterprise/2.17/admin/guides/enterprise-support/overview": "/enterprise/2.17/admin/enterprise-support/overview", + "/enterprise/2.17/admin/guides/enterprise-support/preparing-to-submit-a-ticket": "/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket", + "/enterprise/2.17/admin/guides/enterprise-support/providing-data-to-github-support": "/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support", + "/enterprise/2.17/admin/guides/enterprise-support/reaching-github-support": "/enterprise/2.17/admin/enterprise-support/reaching-github-support", + "/enterprise/2.17/admin/guides/enterprise-support/receiving-help-from-github-support": "/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support", + "/enterprise/2.17/admin/guides/enterprise-support/submitting-a-ticket": "/enterprise/2.17/admin/enterprise-support/submitting-a-ticket", + "/enterprise/2.17/admin/guides": "/enterprise/2.17/admin", + "/enterprise/2.17/admin/guides/installation/about-geo-replication": "/enterprise/2.17/admin/installation/about-geo-replication", + "/enterprise/2.17/admin/guides/installation/about-high-availability-configuration": "/enterprise/2.17/admin/installation/about-high-availability-configuration", + "/enterprise/2.17/admin/guides/installation/about-the-github-enterprise-server-api": "/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api", + "/enterprise/2.17/admin/guides/installation/accessing-the-administrative-shell-ssh": "/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh", + "/enterprise/2.17/admin/guides/installation/accessing-the-management-console": "/enterprise/2.17/admin/installation/accessing-the-management-console", + "/enterprise/2.17/admin/guides/installation/accessing-the-monitor-dashboard": "/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard", + "/enterprise/2.17/admin/guides/installation/activity-dashboard": "/enterprise/2.17/admin/installation/activity-dashboard", + "/enterprise/2.17/admin/guides/installation/audit-logging": "/enterprise/2.17/admin/installation/audit-logging", + "/enterprise/2.17/admin/guides/installation/audited-actions": "/enterprise/2.17/admin/installation/audited-actions", + "/enterprise/2.17/admin/guides/installation/command-line-utilities": "/enterprise/2.17/admin/installation/command-line-utilities", + "/enterprise/2.17/admin/guides/installation/configuring-a-hostname": "/enterprise/2.17/admin/installation/configuring-a-hostname", + "/enterprise/2.17/admin/guides/installation/configuring-an-outbound-web-proxy-server": "/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server", + "/enterprise/2.17/admin/guides/installation/configuring-applications": "/enterprise/2.17/admin/installation/configuring-applications", + "/enterprise/2.17/admin/guides/installation/configuring-backups-on-your-appliance": "/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance", + "/enterprise/2.17/admin/guides/installation/configuring-built-in-firewall-rules": "/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules", + "/enterprise/2.17/admin/guides/installation/configuring-collectd": "/enterprise/2.17/admin/installation/configuring-collectd", + "/enterprise/2.17/admin/guides/installation/configuring-dns-nameservers": "/enterprise/2.17/admin/installation/configuring-dns-nameservers", + "/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server": "/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server", + "/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage-to-use-a-third-party-server": "/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server", + "/enterprise/2.17/admin/guides/installation/configuring-git-large-file-storage": "/enterprise/2.17/admin/installation/configuring-git-large-file-storage", + "/enterprise/2.17/admin/guides/installation/configuring-github-enterprise-server-for-high-availability": "/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability", + "/enterprise/2.17/admin/guides/installation/configuring-github-pages-on-your-appliance": "/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance", + "/enterprise/2.17/admin/guides/installation/configuring-rate-limits": "/enterprise/2.17/admin/installation/configuring-rate-limits", + "/enterprise/2.17/admin/guides/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": "/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance", + "/enterprise/2.17/admin/guides/installation/configuring-the-github-enterprise-server-appliance": "/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance", + "/enterprise/2.17/admin/guides/installation/configuring-the-ip-address-using-the-virtual-machine-console": "/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console", + "/enterprise/2.17/admin/guides/installation/configuring-time-synchronization": "/enterprise/2.17/admin/installation/configuring-time-synchronization", + "/enterprise/2.17/admin/guides/installation/configuring-tls": "/enterprise/2.17/admin/installation/configuring-tls", + "/enterprise/2.17/admin/guides/installation/configuring-your-github-enterprise-server-network-settings": "/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings", + "/enterprise/2.17/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": "/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud", + "/enterprise/2.17/admin/guides/installation/creating-a-high-availability-replica": "/enterprise/2.17/admin/installation/creating-a-high-availability-replica", + "/enterprise/2.17/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise-server": "/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server", + "/enterprise/2.17/admin/guides/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": "/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories", + "/enterprise/2.17/admin/guides/installation/enabling-and-scheduling-maintenance-mode": "/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode", + "/enterprise/2.17/admin/guides/installation/enabling-automatic-update-checks": "/enterprise/2.17/admin/installation/enabling-automatic-update-checks", + "/enterprise/2.17/admin/guides/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": "/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud", + "/enterprise/2.17/admin/guides/installation/enabling-private-mode": "/enterprise/2.17/admin/installation/enabling-private-mode", + "/enterprise/2.17/admin/guides/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": "/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server", + "/enterprise/2.17/admin/guides/installation/enabling-subdomain-isolation": "/enterprise/2.17/admin/installation/enabling-subdomain-isolation", + "/enterprise/2.17/admin/guides/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": "/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom", + "/enterprise/2.17/admin/guides/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": "/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom", + "/enterprise/2.17/admin/guides/installation/getting-started-with-github-enterprise-server": "/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server", + "/enterprise/2.17/admin/guides/installation/increasing-cpu-or-memory-resources": "/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources", + "/enterprise/2.17/admin/guides/installation/increasing-storage-capacity": "/enterprise/2.17/admin/installation/increasing-storage-capacity", + "/enterprise/2.17/admin/guides/installation": "/enterprise/2.17/admin/installation", + "/enterprise/2.17/admin/guides/installation/initiating-a-failover-to-your-replica-appliance": "/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-aws": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-azure": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-google-cloud-platform": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-hyper-v": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-openstack-kvm": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-vmware": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware", + "/enterprise/2.17/admin/guides/installation/installing-github-enterprise-server-on-xenserver": "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver", + "/enterprise/2.17/admin/guides/installation/log-forwarding": "/enterprise/2.17/admin/installation/log-forwarding", + "/enterprise/2.17/admin/guides/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": "/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud", + "/enterprise/2.17/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": "/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later", + "/enterprise/2.17/admin/guides/installation/migrating-from-github-enterprise-1110x-to-2123": "/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123", + "/enterprise/2.17/admin/guides/installation/migrating-to-a-different-git-large-file-storage-server": "/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server", + "/enterprise/2.17/admin/guides/installation/monitoring-activity-on-your-github-enterprise-server-instance": "/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance", + "/enterprise/2.17/admin/guides/installation/monitoring-using-snmp": "/enterprise/2.17/admin/installation/monitoring-using-snmp", + "/enterprise/2.17/admin/guides/installation/monitoring-your-github-enterprise-server-appliance": "/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance", + "/enterprise/2.17/admin/guides/installation/network-ports": "/enterprise/2.17/admin/installation/network-ports", + "/enterprise/2.17/admin/guides/installation/recommended-alert-thresholds": "/enterprise/2.17/admin/installation/recommended-alert-thresholds", + "/enterprise/2.17/admin/guides/installation/recovering-a-high-availability-configuration": "/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration", + "/enterprise/2.17/admin/guides/installation/removing-a-high-availability-replica": "/enterprise/2.17/admin/installation/removing-a-high-availability-replica", + "/enterprise/2.17/admin/guides/installation/searching-the-audit-log": "/enterprise/2.17/admin/installation/searching-the-audit-log", + "/enterprise/2.17/admin/guides/installation/setting-git-push-limits": "/enterprise/2.17/admin/installation/setting-git-push-limits", + "/enterprise/2.17/admin/guides/installation/setting-up-a-github-enterprise-server-instance": "/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance", + "/enterprise/2.17/admin/guides/installation/setting-up-a-staging-instance": "/enterprise/2.17/admin/installation/setting-up-a-staging-instance", + "/enterprise/2.17/admin/guides/installation/setting-up-external-monitoring": "/enterprise/2.17/admin/installation/setting-up-external-monitoring", + "/enterprise/2.17/admin/guides/installation/site-admin-dashboard": "/enterprise/2.17/admin/installation/site-admin-dashboard", + "/enterprise/2.17/admin/guides/installation/system-overview": "/enterprise/2.17/admin/installation/system-overview", + "/enterprise/2.17/admin/guides/installation/troubleshooting-ssl-errors": "/enterprise/2.17/admin/installation/troubleshooting-ssl-errors", + "/enterprise/2.17/admin/guides/installation/updating-the-virtual-machine-and-physical-resources": "/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources", + "/enterprise/2.17/admin/guides/installation/upgrade-requirements": "/enterprise/2.17/admin/installation/upgrade-requirements", + "/enterprise/2.17/admin/guides/installation/upgrading-github-enterprise-server": "/enterprise/2.17/admin/installation/upgrading-github-enterprise-server", + "/enterprise/2.17/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer": "/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer", + "/enterprise/2.17/admin/guides/installation/validating-your-domain-settings": "/enterprise/2.17/admin/installation/validating-your-domain-settings", + "/enterprise/2.17/admin/guides/installation/viewing-push-logs": "/enterprise/2.17/admin/installation/viewing-push-logs", + "/enterprise/2.17/admin/guides/migrations/about-migrations": "/enterprise/2.17/admin/migrations/about-migrations", + "/enterprise/2.17/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server": "/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server", + "/enterprise/2.17/admin/guides/migrations/completing-the-import-on-github-enterprise-server": "/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server", + "/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-github-enterprise-server": "/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server", + "/enterprise/2.17/admin/guides/migrations/exporting-migration-data-from-githubcom": "/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom", + "/enterprise/2.17/admin/guides/migrations/exporting-the-github-enterprise-server-source-repositories": "/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories", + "/enterprise/2.17/admin/guides/migrations/exporting-the-githubcom-organizations-repositories": "/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories", + "/enterprise/2.17/admin/guides/migrations/generating-a-list-of-migration-conflicts": "/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts", + "/enterprise/2.17/admin/guides/migrations/importing-data-from-third-party-version-control-systems": "/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems", + "/enterprise/2.17/admin/guides/migrations/importing-migration-data-to-github-enterprise-server": "/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server", + "/enterprise/2.17/admin/guides/migrations": "/enterprise/2.17/admin/migrations", + "/enterprise/2.17/admin/guides/migrations/overview": "/enterprise/2.17/admin/migrations/overview", + "/enterprise/2.17/admin/guides/migrations/preparing-the-github-enterprise-server-source-instance": "/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance", + "/enterprise/2.17/admin/guides/migrations/preparing-the-githubcom-source-organization": "/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization", + "/enterprise/2.17/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": "/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server", + "/enterprise/2.17/admin/guides/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": "/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings", + "/enterprise/2.17/admin/guides/migrations/reviewing-migration-conflicts": "/enterprise/2.17/admin/migrations/reviewing-migration-conflicts", + "/enterprise/2.17/admin/guides/migrations/reviewing-migration-data": "/enterprise/2.17/admin/migrations/reviewing-migration-data", + "/enterprise/2.17/admin/guides/user-management/about-global-webhooks": "/enterprise/2.17/admin/user-management/about-global-webhooks", + "/enterprise/2.17/admin/guides/user-management/adding-people-to-teams": "/enterprise/2.17/admin/user-management/adding-people-to-teams", + "/enterprise/2.17/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": "/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories", + "/enterprise/2.17/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": "/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider", + "/enterprise/2.17/admin/guides/user-management/archiving-and-unarchiving-repositories": "/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories", + "/enterprise/2.17/admin/guides/user-management/auditing-ssh-keys": "/enterprise/2.17/admin/user-management/auditing-ssh-keys", + "/enterprise/2.17/admin/guides/user-management/auditing-users-across-your-instance": "/enterprise/2.17/admin/user-management/auditing-users-across-your-instance", + "/enterprise/2.17/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance": "/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance", + "/enterprise/2.17/admin/guides/user-management/basic-account-settings": "/enterprise/2.17/admin/user-management/basic-account-settings", + "/enterprise/2.17/admin/guides/user-management/best-practices-for-user-security": "/enterprise/2.17/admin/user-management/best-practices-for-user-security", + "/enterprise/2.17/admin/guides/user-management/changing-authentication-methods": "/enterprise/2.17/admin/user-management/changing-authentication-methods", + "/enterprise/2.17/admin/guides/user-management/configuring-email-for-notifications": "/enterprise/2.17/admin/user-management/configuring-email-for-notifications", + "/enterprise/2.17/admin/guides/user-management/configuring-visibility-for-organization-membership": "/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership", + "/enterprise/2.17/admin/guides/user-management/creating-organizations": "/enterprise/2.17/admin/user-management/creating-organizations", + "/enterprise/2.17/admin/guides/user-management/creating-teams": "/enterprise/2.17/admin/user-management/creating-teams", + "/enterprise/2.17/admin/guides/user-management/customizing-user-messages-on-your-instance": "/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance", + "/enterprise/2.17/admin/guides/user-management/disabling-unauthenticated-sign-ups": "/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups", + "/enterprise/2.17/admin/guides/user-management": "/enterprise/2.17/admin/user-management", + "/enterprise/2.17/admin/guides/user-management/managing-dormant-users": "/enterprise/2.17/admin/user-management/managing-dormant-users", + "/enterprise/2.17/admin/guides/user-management/managing-global-webhooks": "/enterprise/2.17/admin/user-management/managing-global-webhooks", + "/enterprise/2.17/admin/guides/user-management/organizations-and-teams": "/enterprise/2.17/admin/user-management/organizations-and-teams", + "/enterprise/2.17/admin/guides/user-management/placing-a-legal-hold-on-a-user-or-organization": "/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization", + "/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-a-repositorys-visibility": "/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility", + "/enterprise/2.17/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access": "/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access", + "/enterprise/2.17/admin/guides/user-management/preventing-users-from-creating-organizations": "/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations", + "/enterprise/2.17/admin/guides/user-management/preventing-users-from-deleting-organization-repositories": "/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories", + "/enterprise/2.17/admin/guides/user-management/promoting-or-demoting-a-site-administrator": "/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator", + "/enterprise/2.17/admin/guides/user-management/rebuilding-contributions-data": "/enterprise/2.17/admin/user-management/rebuilding-contributions-data", + "/enterprise/2.17/admin/guides/user-management/removing-users-from-teams-and-organizations": "/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations", + "/enterprise/2.17/admin/guides/user-management/repositories": "/enterprise/2.17/admin/user-management/repositories", + "/enterprise/2.17/admin/guides/user-management/requiring-two-factor-authentication-for-an-organization": "/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization", + "/enterprise/2.17/admin/guides/user-management/restricting-repository-creation-in-your-instance": "/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance", + "/enterprise/2.17/admin/guides/user-management/suspending-and-unsuspending-users": "/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users", + "/enterprise/2.17/admin/guides/user-management/user-security": "/enterprise/2.17/admin/user-management/user-security", + "/enterprise/2.17/admin/guides/user-management/using-built-in-authentication": "/enterprise/2.17/admin/user-management/using-built-in-authentication", + "/enterprise/2.17/admin/guides/user-management/using-cas": "/enterprise/2.17/admin/user-management/using-cas", + "/enterprise/2.17/admin/guides/user-management/using-ldap": "/enterprise/2.17/admin/user-management/using-ldap", + "/enterprise/2.17/admin/guides/user-management/using-saml": "/enterprise/2.17/admin/user-management/using-saml", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-branch-restrictions": "/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", + "/enterprise/2.17/user/administering-a-repository/about-branch-restrictions": "/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", + "/enterprise/2.17/github/administering-a-repository/about-branch-restrictions": "/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.17/user/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.17/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": "/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-merge-methods-on-github": "/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", + "/enterprise/2.17/user/administering-a-repository/about-merge-methods-on-github": "/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", + "/enterprise/2.17/github/administering-a-repository/about-merge-methods-on-github": "/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-protected-branches": "/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", + "/enterprise/2.17/user/administering-a-repository/about-protected-branches": "/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", + "/enterprise/2.17/github/administering-a-repository/about-protected-branches": "/enterprise/2.17/user/github/administering-a-repository/about-protected-branches", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-releases": "/enterprise/2.17/user/github/administering-a-repository/about-releases", + "/enterprise/2.17/user/administering-a-repository/about-releases": "/enterprise/2.17/user/github/administering-a-repository/about-releases", + "/enterprise/2.17/github/administering-a-repository/about-releases": "/enterprise/2.17/user/github/administering-a-repository/about-releases", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-commit-signing": "/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", + "/enterprise/2.17/user/administering-a-repository/about-required-commit-signing": "/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", + "/enterprise/2.17/github/administering-a-repository/about-required-commit-signing": "/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-reviews-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", + "/enterprise/2.17/user/administering-a-repository/about-required-reviews-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", + "/enterprise/2.17/github/administering-a-repository/about-required-reviews-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/about-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", + "/enterprise/2.17/user/administering-a-repository/about-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", + "/enterprise/2.17/github/administering-a-repository/about-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/automation-for-release-forms-with-query-parameters": "/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", + "/enterprise/2.17/user/administering-a-repository/automation-for-release-forms-with-query-parameters": "/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", + "/enterprise/2.17/github/administering-a-repository/automation-for-release-forms-with-query-parameters": "/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/classifying-your-repository-with-topics": "/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", + "/enterprise/2.17/user/administering-a-repository/classifying-your-repository-with-topics": "/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", + "/enterprise/2.17/github/administering-a-repository/classifying-your-repository-with-topics": "/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.17/user/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.17/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-commit-squashing-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.17/user/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.17/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-protected-branches": "/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", + "/enterprise/2.17/user/administering-a-repository/configuring-protected-branches": "/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", + "/enterprise/2.17/github/administering-a-repository/configuring-protected-branches": "/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/configuring-pull-request-merges": "/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", + "/enterprise/2.17/user/administering-a-repository/configuring-pull-request-merges": "/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", + "/enterprise/2.17/github/administering-a-repository/configuring-pull-request-merges": "/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/customizing-how-changed-files-appear-on-github": "/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", + "/enterprise/2.17/user/administering-a-repository/customizing-how-changed-files-appear-on-github": "/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", + "/enterprise/2.17/github/administering-a-repository/customizing-how-changed-files-appear-on-github": "/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/defining-the-mergeability-of-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", + "/enterprise/2.17/user/administering-a-repository/defining-the-mergeability-of-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", + "/enterprise/2.17/github/administering-a-repository/defining-the-mergeability-of-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-a-repository": "/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", + "/enterprise/2.17/user/administering-a-repository/deleting-a-repository": "/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", + "/enterprise/2.17/github/administering-a-repository/deleting-a-repository": "/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.17/user/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.17/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": "/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.17/user/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.17/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": "/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-branch-restrictions": "/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", + "/enterprise/2.17/user/administering-a-repository/enabling-branch-restrictions": "/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", + "/enterprise/2.17/github/administering-a-repository/enabling-branch-restrictions": "/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-commit-signing": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", + "/enterprise/2.17/user/administering-a-repository/enabling-required-commit-signing": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", + "/enterprise/2.17/github/administering-a-repository/enabling-required-commit-signing": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-reviews-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", + "/enterprise/2.17/user/administering-a-repository/enabling-required-reviews-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", + "/enterprise/2.17/github/administering-a-repository/enabling-required-reviews-for-pull-requests": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/enabling-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", + "/enterprise/2.17/user/administering-a-repository/enabling-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", + "/enterprise/2.17/github/administering-a-repository/enabling-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository": "/enterprise/2.17/user/github/administering-a-repository", + "/enterprise/2.17/user/administering-a-repository": "/enterprise/2.17/user/github/administering-a-repository", + "/enterprise/2.17/github/administering-a-repository": "/enterprise/2.17/user/github/administering-a-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/linking-to-releases": "/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", + "/enterprise/2.17/user/administering-a-repository/linking-to-releases": "/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", + "/enterprise/2.17/github/administering-a-repository/linking-to-releases": "/enterprise/2.17/user/github/administering-a-repository/linking-to-releases", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-branches-in-your-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", + "/enterprise/2.17/user/administering-a-repository/managing-branches-in-your-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", + "/enterprise/2.17/github/administering-a-repository/managing-branches-in-your-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-releases-in-a-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", + "/enterprise/2.17/user/administering-a-repository/managing-releases-in-a-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", + "/enterprise/2.17/github/administering-a-repository/managing-releases-in-a-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-repository-settings": "/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", + "/enterprise/2.17/user/administering-a-repository/managing-repository-settings": "/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", + "/enterprise/2.17/github/administering-a-repository/managing-repository-settings": "/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/managing-the-forking-policy-for-your-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", + "/enterprise/2.17/user/administering-a-repository/managing-the-forking-policy-for-your-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", + "/enterprise/2.17/github/administering-a-repository/managing-the-forking-policy-for-your-repository": "/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/releasing-projects-on-github": "/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", + "/enterprise/2.17/user/administering-a-repository/releasing-projects-on-github": "/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", + "/enterprise/2.17/github/administering-a-repository/releasing-projects-on-github": "/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/renaming-a-repository": "/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", + "/enterprise/2.17/user/administering-a-repository/renaming-a-repository": "/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", + "/enterprise/2.17/github/administering-a-repository/renaming-a-repository": "/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-repository-visibility": "/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", + "/enterprise/2.17/user/administering-a-repository/setting-repository-visibility": "/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", + "/enterprise/2.17/github/administering-a-repository/setting-repository-visibility": "/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/setting-the-default-branch": "/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", + "/enterprise/2.17/user/administering-a-repository/setting-the-default-branch": "/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", + "/enterprise/2.17/github/administering-a-repository/setting-the-default-branch": "/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/transferring-a-repository": "/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", + "/enterprise/2.17/user/administering-a-repository/transferring-a-repository": "/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", + "/enterprise/2.17/github/administering-a-repository/transferring-a-repository": "/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/types-of-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", + "/enterprise/2.17/user/administering-a-repository/types-of-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", + "/enterprise/2.17/github/administering-a-repository/types-of-required-status-checks": "/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-branches-in-your-repository": "/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", + "/enterprise/2.17/user/administering-a-repository/viewing-branches-in-your-repository": "/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", + "/enterprise/2.17/github/administering-a-repository/viewing-branches-in-your-repository": "/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-deployment-activity-for-your-repository": "/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", + "/enterprise/2.17/user/administering-a-repository/viewing-deployment-activity-for-your-repository": "/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", + "/enterprise/2.17/github/administering-a-repository/viewing-deployment-activity-for-your-repository": "/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository", + "/enterprise/2.17/user/github/admin/guidesistering-a-repository/viewing-your-repositorys-releases-and-tags": "/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", + "/enterprise/2.17/user/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", + "/enterprise/2.17/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": "/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags", + "/enterprise/2.17/user/authenticating-to-github/about-commit-signature-verification": "/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", + "/enterprise/2.17/github/authenticating-to-github/about-commit-signature-verification": "/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification", + "/enterprise/2.17/user/authenticating-to-github/about-ssh": "/enterprise/2.17/user/github/authenticating-to-github/about-ssh", + "/enterprise/2.17/github/authenticating-to-github/about-ssh": "/enterprise/2.17/user/github/authenticating-to-github/about-ssh", + "/enterprise/2.17/user/authenticating-to-github/about-two-factor-authentication": "/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", + "/enterprise/2.17/github/authenticating-to-github/about-two-factor-authentication": "/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication", + "/enterprise/2.17/user/authenticating-to-github/accessing-github-using-two-factor-authentication": "/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", + "/enterprise/2.17/github/authenticating-to-github/accessing-github-using-two-factor-authentication": "/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication", + "/enterprise/2.17/user/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", + "/enterprise/2.17/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account", + "/enterprise/2.17/user/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", + "/enterprise/2.17/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account", + "/enterprise/2.17/user/authenticating-to-github/associating-an-email-with-your-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", + "/enterprise/2.17/github/authenticating-to-github/associating-an-email-with-your-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key", + "/enterprise/2.17/user/authenticating-to-github/authorizing-oauth-apps": "/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", + "/enterprise/2.17/github/authenticating-to-github/authorizing-oauth-apps": "/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps", + "/enterprise/2.17/user/authenticating-to-github/checking-for-existing-gpg-keys": "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", + "/enterprise/2.17/github/authenticating-to-github/checking-for-existing-gpg-keys": "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys", + "/enterprise/2.17/user/authenticating-to-github/checking-for-existing-ssh-keys": "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", + "/enterprise/2.17/github/authenticating-to-github/checking-for-existing-ssh-keys": "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys", + "/enterprise/2.17/user/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", + "/enterprise/2.17/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": "/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status", + "/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", + "/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods", + "/enterprise/2.17/user/authenticating-to-github/configuring-two-factor-authentication": "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", + "/enterprise/2.17/github/authenticating-to-github/configuring-two-factor-authentication": "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication", + "/enterprise/2.17/user/authenticating-to-github/connecting-to-github-with-ssh": "/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", + "/enterprise/2.17/github/authenticating-to-github/connecting-to-github-with-ssh": "/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh", + "/enterprise/2.17/user/authenticating-to-github/connecting-with-third-party-applications": "/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", + "/enterprise/2.17/github/authenticating-to-github/connecting-with-third-party-applications": "/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications", + "/enterprise/2.17/user/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", + "/enterprise/2.17/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": "/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line", + "/enterprise/2.17/user/authenticating-to-github/creating-a-strong-password": "/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", + "/enterprise/2.17/github/authenticating-to-github/creating-a-strong-password": "/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password", + "/enterprise/2.17/user/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", + "/enterprise/2.17/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": "/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account", + "/enterprise/2.17/user/authenticating-to-github/error-agent-admitted-failure-to-sign": "/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", + "/enterprise/2.17/github/authenticating-to-github/error-agent-admitted-failure-to-sign": "/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign", + "/enterprise/2.17/user/authenticating-to-github/error-bad-file-number": "/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", + "/enterprise/2.17/github/authenticating-to-github/error-bad-file-number": "/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number", + "/enterprise/2.17/user/authenticating-to-github/error-key-already-in-use": "/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", + "/enterprise/2.17/github/authenticating-to-github/error-key-already-in-use": "/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use", + "/enterprise/2.17/user/authenticating-to-github/error-permission-denied-publickey": "/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", + "/enterprise/2.17/github/authenticating-to-github/error-permission-denied-publickey": "/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey", + "/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", + "/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user", + "/enterprise/2.17/user/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", + "/enterprise/2.17/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo", + "/enterprise/2.17/user/authenticating-to-github/error-ssh-add-illegal-option----k": "/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", + "/enterprise/2.17/github/authenticating-to-github/error-ssh-add-illegal-option----k": "/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k", + "/enterprise/2.17/user/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", + "/enterprise/2.17/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": "/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit", + "/enterprise/2.17/user/authenticating-to-github/generating-a-new-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", + "/enterprise/2.17/github/authenticating-to-github/generating-a-new-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key", + "/enterprise/2.17/user/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", + "/enterprise/2.17/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", + "/enterprise/2.17/user/authenticating-to-github": "/enterprise/2.17/user/github/authenticating-to-github", + "/enterprise/2.17/github/authenticating-to-github": "/enterprise/2.17/user/github/authenticating-to-github", + "/enterprise/2.17/user/authenticating-to-github/keeping-your-account-and-data-secure": "/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", + "/enterprise/2.17/github/authenticating-to-github/keeping-your-account-and-data-secure": "/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure", + "/enterprise/2.17/user/authenticating-to-github/managing-commit-signature-verification": "/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", + "/enterprise/2.17/github/authenticating-to-github/managing-commit-signature-verification": "/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification", + "/enterprise/2.17/user/authenticating-to-github/preventing-unauthorized-access": "/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", + "/enterprise/2.17/github/authenticating-to-github/preventing-unauthorized-access": "/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access", + "/enterprise/2.17/user/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", + "/enterprise/2.17/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials", + "/enterprise/2.17/user/authenticating-to-github/recovering-your-ssh-key-passphrase": "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", + "/enterprise/2.17/github/authenticating-to-github/recovering-your-ssh-key-passphrase": "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase", + "/enterprise/2.17/user/authenticating-to-github/removing-sensitive-data-from-a-repository": "/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", + "/enterprise/2.17/github/authenticating-to-github/removing-sensitive-data-from-a-repository": "/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository", + "/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", + "/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth", + "/enterprise/2.17/user/authenticating-to-github/reviewing-your-authorized-integrations": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", + "/enterprise/2.17/github/authenticating-to-github/reviewing-your-authorized-integrations": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations", + "/enterprise/2.17/user/authenticating-to-github/reviewing-your-deploy-keys": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", + "/enterprise/2.17/github/authenticating-to-github/reviewing-your-deploy-keys": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys", + "/enterprise/2.17/user/authenticating-to-github/reviewing-your-security-log": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", + "/enterprise/2.17/github/authenticating-to-github/reviewing-your-security-log": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log", + "/enterprise/2.17/user/authenticating-to-github/reviewing-your-ssh-keys": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", + "/enterprise/2.17/github/authenticating-to-github/reviewing-your-ssh-keys": "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys", + "/enterprise/2.17/user/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", + "/enterprise/2.17/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": "/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa", + "/enterprise/2.17/user/authenticating-to-github/signing-commits": "/enterprise/2.17/user/github/authenticating-to-github/signing-commits", + "/enterprise/2.17/github/authenticating-to-github/signing-commits": "/enterprise/2.17/user/github/authenticating-to-github/signing-commits", + "/enterprise/2.17/user/authenticating-to-github/signing-tags": "/enterprise/2.17/user/github/authenticating-to-github/signing-tags", + "/enterprise/2.17/github/authenticating-to-github/signing-tags": "/enterprise/2.17/user/github/authenticating-to-github/signing-tags", + "/enterprise/2.17/user/authenticating-to-github/sudo-mode": "/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", + "/enterprise/2.17/github/authenticating-to-github/sudo-mode": "/enterprise/2.17/user/github/authenticating-to-github/sudo-mode", + "/enterprise/2.17/user/authenticating-to-github/telling-git-about-your-signing-key": "/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", + "/enterprise/2.17/github/authenticating-to-github/telling-git-about-your-signing-key": "/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key", + "/enterprise/2.17/user/authenticating-to-github/testing-your-ssh-connection": "/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", + "/enterprise/2.17/github/authenticating-to-github/testing-your-ssh-connection": "/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection", + "/enterprise/2.17/user/authenticating-to-github/troubleshooting-commit-signature-verification": "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", + "/enterprise/2.17/github/authenticating-to-github/troubleshooting-commit-signature-verification": "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification", + "/enterprise/2.17/user/authenticating-to-github/troubleshooting-ssh": "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", + "/enterprise/2.17/github/authenticating-to-github/troubleshooting-ssh": "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh", + "/enterprise/2.17/user/authenticating-to-github/updating-an-expired-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", + "/enterprise/2.17/github/authenticating-to-github/updating-an-expired-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key", + "/enterprise/2.17/user/authenticating-to-github/updating-your-github-access-credentials": "/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", + "/enterprise/2.17/github/authenticating-to-github/updating-your-github-access-credentials": "/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials", + "/enterprise/2.17/user/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", + "/enterprise/2.17/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": "/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key", + "/enterprise/2.17/user/authenticating-to-github/working-with-ssh-key-passphrases": "/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", + "/enterprise/2.17/github/authenticating-to-github/working-with-ssh-key-passphrases": "/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases", + "/enterprise/2.17/user/building-a-strong-community/about-issue-and-pull-request-templates": "/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", + "/enterprise/2.17/github/building-a-strong-community/about-issue-and-pull-request-templates": "/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates", + "/enterprise/2.17/user/building-a-strong-community/about-team-discussions": "/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", + "/enterprise/2.17/github/building-a-strong-community/about-team-discussions": "/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions", + "/enterprise/2.17/user/building-a-strong-community/about-wikis": "/enterprise/2.17/user/github/building-a-strong-community/about-wikis", + "/enterprise/2.17/github/building-a-strong-community/about-wikis": "/enterprise/2.17/user/github/building-a-strong-community/about-wikis", + "/enterprise/2.17/user/building-a-strong-community/adding-a-license-to-a-repository": "/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", + "/enterprise/2.17/github/building-a-strong-community/adding-a-license-to-a-repository": "/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository", + "/enterprise/2.17/user/building-a-strong-community/adding-or-editing-wiki-pages": "/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", + "/enterprise/2.17/github/building-a-strong-community/adding-or-editing-wiki-pages": "/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages", + "/enterprise/2.17/user/building-a-strong-community/adding-support-resources-to-your-project": "/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", + "/enterprise/2.17/github/building-a-strong-community/adding-support-resources-to-your-project": "/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project", + "/enterprise/2.17/user/building-a-strong-community/changing-access-permissions-for-wikis": "/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", + "/enterprise/2.17/github/building-a-strong-community/changing-access-permissions-for-wikis": "/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis", + "/enterprise/2.17/user/building-a-strong-community/collaborating-with-your-team": "/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", + "/enterprise/2.17/github/building-a-strong-community/collaborating-with-your-team": "/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team", + "/enterprise/2.17/user/building-a-strong-community/configuring-issue-templates-for-your-repository": "/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", + "/enterprise/2.17/github/building-a-strong-community/configuring-issue-templates-for-your-repository": "/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository", + "/enterprise/2.17/user/building-a-strong-community/creating-a-default-community-health-file": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", + "/enterprise/2.17/github/building-a-strong-community/creating-a-default-community-health-file": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file", + "/enterprise/2.17/user/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", + "/enterprise/2.17/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki", + "/enterprise/2.17/user/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", + "/enterprise/2.17/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository", + "/enterprise/2.17/user/building-a-strong-community/creating-a-team-discussion": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", + "/enterprise/2.17/github/building-a-strong-community/creating-a-team-discussion": "/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion", + "/enterprise/2.17/user/building-a-strong-community/disabling-wikis": "/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", + "/enterprise/2.17/github/building-a-strong-community/disabling-wikis": "/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis", + "/enterprise/2.17/user/building-a-strong-community/documenting-your-project-with-wikis": "/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", + "/enterprise/2.17/github/building-a-strong-community/documenting-your-project-with-wikis": "/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis", + "/enterprise/2.17/user/building-a-strong-community/editing-or-deleting-a-team-discussion": "/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", + "/enterprise/2.17/github/building-a-strong-community/editing-or-deleting-a-team-discussion": "/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion", + "/enterprise/2.17/user/building-a-strong-community/editing-wiki-content": "/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", + "/enterprise/2.17/github/building-a-strong-community/editing-wiki-content": "/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content", + "/enterprise/2.17/user/building-a-strong-community": "/enterprise/2.17/user/github/building-a-strong-community", + "/enterprise/2.17/github/building-a-strong-community": "/enterprise/2.17/user/github/building-a-strong-community", + "/enterprise/2.17/user/building-a-strong-community/locking-conversations": "/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", + "/enterprise/2.17/github/building-a-strong-community/locking-conversations": "/enterprise/2.17/user/github/building-a-strong-community/locking-conversations", + "/enterprise/2.17/user/building-a-strong-community/managing-disruptive-comments": "/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", + "/enterprise/2.17/github/building-a-strong-community/managing-disruptive-comments": "/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments", + "/enterprise/2.17/user/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", + "/enterprise/2.17/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": "/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository", + "/enterprise/2.17/user/building-a-strong-community/moderating-comments-and-conversations": "/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", + "/enterprise/2.17/github/building-a-strong-community/moderating-comments-and-conversations": "/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations", + "/enterprise/2.17/user/building-a-strong-community/pinning-a-team-discussion": "/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", + "/enterprise/2.17/github/building-a-strong-community/pinning-a-team-discussion": "/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion", + "/enterprise/2.17/user/building-a-strong-community/setting-guidelines-for-repository-contributors": "/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", + "/enterprise/2.17/github/building-a-strong-community/setting-guidelines-for-repository-contributors": "/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors", + "/enterprise/2.17/user/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", + "/enterprise/2.17/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": "/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions", + "/enterprise/2.17/user/building-a-strong-community/tracking-changes-in-a-comment": "/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", + "/enterprise/2.17/github/building-a-strong-community/tracking-changes-in-a-comment": "/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment", + "/enterprise/2.17/user/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", + "/enterprise/2.17/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": "/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests", + "/enterprise/2.17/user/building-a-strong-community/viewing-a-wikis-history-of-changes": "/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", + "/enterprise/2.17/github/building-a-strong-community/viewing-a-wikis-history-of-changes": "/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-branches": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-branches": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-forks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-forks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/about-status-checks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/about-status-checks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/github-flow": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/github-flow": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/overview": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/overview": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-forks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-forks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks", + "/enterprise/2.17/user/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", + "/enterprise/2.17/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks", + "/enterprise/2.17/user/committing-changes-to-your-project/changing-a-commit-message": "/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", + "/enterprise/2.17/github/committing-changes-to-your-project/changing-a-commit-message": "/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message", + "/enterprise/2.17/user/committing-changes-to-your-project/commit-branch-and-tag-labels": "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", + "/enterprise/2.17/github/committing-changes-to-your-project/commit-branch-and-tag-labels": "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels", + "/enterprise/2.17/user/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", + "/enterprise/2.17/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone", + "/enterprise/2.17/user/committing-changes-to-your-project/comparing-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", + "/enterprise/2.17/github/committing-changes-to-your-project/comparing-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits", + "/enterprise/2.17/user/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", + "/enterprise/2.17/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors", + "/enterprise/2.17/user/committing-changes-to-your-project/creating-and-editing-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", + "/enterprise/2.17/github/committing-changes-to-your-project/creating-and-editing-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits", + "/enterprise/2.17/user/committing-changes-to-your-project/differences-between-commit-views": "/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", + "/enterprise/2.17/github/committing-changes-to-your-project/differences-between-commit-views": "/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views", + "/enterprise/2.17/user/committing-changes-to-your-project": "/enterprise/2.17/user/github/committing-changes-to-your-project", + "/enterprise/2.17/github/committing-changes-to-your-project": "/enterprise/2.17/user/github/committing-changes-to-your-project", + "/enterprise/2.17/user/committing-changes-to-your-project/troubleshooting-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", + "/enterprise/2.17/github/committing-changes-to-your-project/troubleshooting-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits", + "/enterprise/2.17/user/committing-changes-to-your-project/viewing-and-comparing-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", + "/enterprise/2.17/github/committing-changes-to-your-project/viewing-and-comparing-commits": "/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits", + "/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", + "/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order", + "/enterprise/2.17/user/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", + "/enterprise/2.17/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-code-owners": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-code-owners": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-readmes": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-readmes": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-languages": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-languages": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/about-repository-visibility": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/about-repository-visibility": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/archiving-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/archiving-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/cloning-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/cloning-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/error-repository-not-found": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/error-repository-not-found": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/https-cloning-errors": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/https-cloning-errors": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/licensing-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/licensing-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository", + "/enterprise/2.17/user/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", + "/enterprise/2.17/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository", + "/enterprise/2.17/user/extending-github/about-webhooks": "/enterprise/2.17/user/github/extending-github/about-webhooks", + "/enterprise/2.17/github/extending-github/about-webhooks": "/enterprise/2.17/user/github/extending-github/about-webhooks", + "/enterprise/2.17/user/extending-github/getting-started-with-the-api": "/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", + "/enterprise/2.17/github/extending-github/getting-started-with-the-api": "/enterprise/2.17/user/github/extending-github/getting-started-with-the-api", + "/enterprise/2.17/user/extending-github/git-automation-with-oauth-tokens": "/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", + "/enterprise/2.17/github/extending-github/git-automation-with-oauth-tokens": "/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens", + "/enterprise/2.17/user/extending-github": "/enterprise/2.17/user/github/extending-github", + "/enterprise/2.17/github/extending-github": "/enterprise/2.17/user/github/extending-github", + "/enterprise/2.17/user/getting-started-with-github/access-permissions-on-github": "/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", + "/enterprise/2.17/github/getting-started-with-github/access-permissions-on-github": "/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github", + "/enterprise/2.17/user/getting-started-with-github/be-social": "/enterprise/2.17/user/github/getting-started-with-github/be-social", + "/enterprise/2.17/github/getting-started-with-github/be-social": "/enterprise/2.17/user/github/getting-started-with-github/be-social", + "/enterprise/2.17/user/getting-started-with-github/create-a-repo": "/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", + "/enterprise/2.17/github/getting-started-with-github/create-a-repo": "/enterprise/2.17/user/github/getting-started-with-github/create-a-repo", + "/enterprise/2.17/user/getting-started-with-github/exploring-projects-on-github": "/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", + "/enterprise/2.17/github/getting-started-with-github/exploring-projects-on-github": "/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github", + "/enterprise/2.17/user/getting-started-with-github/following-people": "/enterprise/2.17/user/github/getting-started-with-github/following-people", + "/enterprise/2.17/github/getting-started-with-github/following-people": "/enterprise/2.17/user/github/getting-started-with-github/following-people", + "/enterprise/2.17/user/getting-started-with-github/fork-a-repo": "/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", + "/enterprise/2.17/github/getting-started-with-github/fork-a-repo": "/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo", + "/enterprise/2.17/user/getting-started-with-github/git-and-github-learning-resources": "/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", + "/enterprise/2.17/github/getting-started-with-github/git-and-github-learning-resources": "/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources", + "/enterprise/2.17/user/getting-started-with-github/git-cheatsheet": "/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", + "/enterprise/2.17/github/getting-started-with-github/git-cheatsheet": "/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet", + "/enterprise/2.17/user/getting-started-with-github/github-desktop": "/enterprise/2.17/user/github/getting-started-with-github/github-desktop", + "/enterprise/2.17/github/getting-started-with-github/github-desktop": "/enterprise/2.17/user/github/getting-started-with-github/github-desktop", + "/enterprise/2.17/user/getting-started-with-github/github-glossary": "/enterprise/2.17/user/github/getting-started-with-github/github-glossary", + "/enterprise/2.17/github/getting-started-with-github/github-glossary": "/enterprise/2.17/user/github/getting-started-with-github/github-glossary", + "/enterprise/2.17/user/getting-started-with-github/githubs-products": "/enterprise/2.17/user/github/getting-started-with-github/githubs-products", + "/enterprise/2.17/github/getting-started-with-github/githubs-products": "/enterprise/2.17/user/github/getting-started-with-github/githubs-products", + "/enterprise/2.17/user/getting-started-with-github": "/enterprise/2.17/user/github/getting-started-with-github", + "/enterprise/2.17/github/getting-started-with-github": "/enterprise/2.17/user/github/getting-started-with-github", + "/enterprise/2.17/user/getting-started-with-github/keyboard-shortcuts": "/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", + "/enterprise/2.17/github/getting-started-with-github/keyboard-shortcuts": "/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts", + "/enterprise/2.17/user/getting-started-with-github/learning-about-github": "/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", + "/enterprise/2.17/github/getting-started-with-github/learning-about-github": "/enterprise/2.17/user/github/getting-started-with-github/learning-about-github", + "/enterprise/2.17/user/getting-started-with-github/quickstart": "/enterprise/2.17/user/github/getting-started-with-github/quickstart", + "/enterprise/2.17/github/getting-started-with-github/quickstart": "/enterprise/2.17/user/github/getting-started-with-github/quickstart", + "/enterprise/2.17/user/getting-started-with-github/saving-repositories-with-stars": "/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", + "/enterprise/2.17/github/getting-started-with-github/saving-repositories-with-stars": "/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars", + "/enterprise/2.17/user/getting-started-with-github/set-up-git": "/enterprise/2.17/user/github/getting-started-with-github/set-up-git", + "/enterprise/2.17/github/getting-started-with-github/set-up-git": "/enterprise/2.17/user/github/getting-started-with-github/set-up-git", + "/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", + "/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud", + "/enterprise/2.17/user/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", + "/enterprise/2.17/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server", + "/enterprise/2.17/user/getting-started-with-github/signing-up-for-github": "/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", + "/enterprise/2.17/github/getting-started-with-github/signing-up-for-github": "/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github", + "/enterprise/2.17/user/getting-started-with-github/supported-browsers": "/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", + "/enterprise/2.17/github/getting-started-with-github/supported-browsers": "/enterprise/2.17/user/github/getting-started-with-github/supported-browsers", + "/enterprise/2.17/user/getting-started-with-github/types-of-github-accounts": "/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", + "/enterprise/2.17/github/getting-started-with-github/types-of-github-accounts": "/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts", + "/enterprise/2.17/user/getting-started-with-github/using-github": "/enterprise/2.17/user/github/getting-started-with-github/using-github", + "/enterprise/2.17/github/getting-started-with-github/using-github": "/enterprise/2.17/user/github/getting-started-with-github/using-github", + "/enterprise/2.17/user/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", + "/enterprise/2.17/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": "/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line", + "/enterprise/2.17/user/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", + "/enterprise/2.17/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line", + "/enterprise/2.17/user/importing-your-projects-to-github/importing-source-code-to-github": "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", + "/enterprise/2.17/github/importing-your-projects-to-github/importing-source-code-to-github": "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github", + "/enterprise/2.17/user/importing-your-projects-to-github": "/enterprise/2.17/user/github/importing-your-projects-to-github", + "/enterprise/2.17/github/importing-your-projects-to-github": "/enterprise/2.17/user/github/importing-your-projects-to-github", + "/enterprise/2.17/user/importing-your-projects-to-github/source-code-migration-tools": "/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", + "/enterprise/2.17/github/importing-your-projects-to-github/source-code-migration-tools": "/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools", + "/enterprise/2.17/user/importing-your-projects-to-github/subversion-properties-supported-by-github": "/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", + "/enterprise/2.17/github/importing-your-projects-to-github/subversion-properties-supported-by-github": "/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github", + "/enterprise/2.17/user/importing-your-projects-to-github/support-for-subversion-clients": "/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", + "/enterprise/2.17/github/importing-your-projects-to-github/support-for-subversion-clients": "/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients", + "/enterprise/2.17/user/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", + "/enterprise/2.17/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": "/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git", + "/enterprise/2.17/user/importing-your-projects-to-github/working-with-subversion-on-github": "/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", + "/enterprise/2.17/github/importing-your-projects-to-github/working-with-subversion-on-github": "/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github", + "/enterprise/2.17/user": "/enterprise/2.17/user/github", + "/enterprise/2.17/github": "/enterprise/2.17/user/github", + "/enterprise/2.17/user/managing-files-in-a-repository/3d-file-viewer": "/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", + "/enterprise/2.17/github/managing-files-in-a-repository/3d-file-viewer": "/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer", + "/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", + "/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line", + "/enterprise/2.17/user/managing-files-in-a-repository/adding-a-file-to-a-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", + "/enterprise/2.17/github/managing-files-in-a-repository/adding-a-file-to-a-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository", + "/enterprise/2.17/user/managing-files-in-a-repository/creating-new-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", + "/enterprise/2.17/github/managing-files-in-a-repository/creating-new-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files", + "/enterprise/2.17/user/managing-files-in-a-repository/deleting-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", + "/enterprise/2.17/github/managing-files-in-a-repository/deleting-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files", + "/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-another-users-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", + "/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-another-users-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository", + "/enterprise/2.17/user/managing-files-in-a-repository/editing-files-in-your-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", + "/enterprise/2.17/github/managing-files-in-a-repository/editing-files-in-your-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository", + "/enterprise/2.17/user/managing-files-in-a-repository/getting-permanent-links-to-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", + "/enterprise/2.17/github/managing-files-in-a-repository/getting-permanent-links-to-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files", + "/enterprise/2.17/user/managing-files-in-a-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository", + "/enterprise/2.17/github/managing-files-in-a-repository": "/enterprise/2.17/user/github/managing-files-in-a-repository", + "/enterprise/2.17/user/managing-files-in-a-repository/managing-files-on-github": "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", + "/enterprise/2.17/github/managing-files-in-a-repository/managing-files-on-github": "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github", + "/enterprise/2.17/user/managing-files-in-a-repository/managing-files-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", + "/enterprise/2.17/github/managing-files-in-a-repository/managing-files-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line", + "/enterprise/2.17/user/managing-files-in-a-repository/mapping-geojson-files-on-github": "/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", + "/enterprise/2.17/github/managing-files-in-a-repository/mapping-geojson-files-on-github": "/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github", + "/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", + "/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line", + "/enterprise/2.17/user/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", + "/enterprise/2.17/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location", + "/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", + "/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line", + "/enterprise/2.17/user/managing-files-in-a-repository/renaming-a-file": "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", + "/enterprise/2.17/github/managing-files-in-a-repository/renaming-a-file": "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file", + "/enterprise/2.17/user/managing-files-in-a-repository/rendering-and-diffing-images": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", + "/enterprise/2.17/github/managing-files-in-a-repository/rendering-and-diffing-images": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images", + "/enterprise/2.17/user/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", + "/enterprise/2.17/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data", + "/enterprise/2.17/user/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", + "/enterprise/2.17/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents", + "/enterprise/2.17/user/managing-files-in-a-repository/rendering-pdf-documents": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", + "/enterprise/2.17/github/managing-files-in-a-repository/rendering-pdf-documents": "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents", + "/enterprise/2.17/user/managing-files-in-a-repository/tracking-changes-in-a-file": "/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", + "/enterprise/2.17/github/managing-files-in-a-repository/tracking-changes-in-a-file": "/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file", + "/enterprise/2.17/user/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", + "/enterprise/2.17/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github", + "/enterprise/2.17/user/managing-files-in-a-repository/working-with-non-code-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", + "/enterprise/2.17/github/managing-files-in-a-repository/working-with-non-code-files": "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files", + "/enterprise/2.17/user/managing-large-files/about-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", + "/enterprise/2.17/github/managing-large-files/about-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage", + "/enterprise/2.17/user/managing-large-files/collaboration-with-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", + "/enterprise/2.17/github/managing-large-files/collaboration-with-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage", + "/enterprise/2.17/user/managing-large-files/conditions-for-large-files": "/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", + "/enterprise/2.17/github/managing-large-files/conditions-for-large-files": "/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files", + "/enterprise/2.17/user/managing-large-files/configuring-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", + "/enterprise/2.17/github/managing-large-files/configuring-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage", + "/enterprise/2.17/user/managing-large-files/distributing-large-binaries": "/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", + "/enterprise/2.17/github/managing-large-files/distributing-large-binaries": "/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries", + "/enterprise/2.17/user/managing-large-files": "/enterprise/2.17/user/github/managing-large-files", + "/enterprise/2.17/github/managing-large-files": "/enterprise/2.17/user/github/managing-large-files", + "/enterprise/2.17/user/managing-large-files/installing-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", + "/enterprise/2.17/github/managing-large-files/installing-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage", + "/enterprise/2.17/user/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", + "/enterprise/2.17/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", + "/enterprise/2.17/user/managing-large-files/removing-files-from-a-repositorys-history": "/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", + "/enterprise/2.17/github/managing-large-files/removing-files-from-a-repositorys-history": "/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history", + "/enterprise/2.17/user/managing-large-files/removing-files-from-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", + "/enterprise/2.17/github/managing-large-files/removing-files-from-git-large-file-storage": "/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage", + "/enterprise/2.17/user/managing-large-files/resolving-git-large-file-storage-upload-failures": "/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", + "/enterprise/2.17/github/managing-large-files/resolving-git-large-file-storage-upload-failures": "/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures", + "/enterprise/2.17/user/managing-large-files/versioning-large-files": "/enterprise/2.17/user/github/managing-large-files/versioning-large-files", + "/enterprise/2.17/github/managing-large-files/versioning-large-files": "/enterprise/2.17/user/github/managing-large-files/versioning-large-files", + "/enterprise/2.17/user/managing-large-files/working-with-large-files": "/enterprise/2.17/user/github/managing-large-files/working-with-large-files", + "/enterprise/2.17/github/managing-large-files/working-with-large-files": "/enterprise/2.17/user/github/managing-large-files/working-with-large-files", + "/enterprise/2.17/user/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", + "/enterprise/2.17/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": "/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies", + "/enterprise/2.17/user/managing-security-vulnerabilities": "/enterprise/2.17/user/github/managing-security-vulnerabilities", + "/enterprise/2.17/github/managing-security-vulnerabilities": "/enterprise/2.17/user/github/managing-security-vulnerabilities", + "/enterprise/2.17/user/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", + "/enterprise/2.17/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": "/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies", + "/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", + "/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters", + "/enterprise/2.17/user/managing-your-work-on-github/about-automation-for-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", + "/enterprise/2.17/github/managing-your-work-on-github/about-automation-for-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards", + "/enterprise/2.17/user/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/about-issues": "/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", + "/enterprise/2.17/github/managing-your-work-on-github/about-issues": "/enterprise/2.17/user/github/managing-your-work-on-github/about-issues", + "/enterprise/2.17/user/managing-your-work-on-github/about-labels": "/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", + "/enterprise/2.17/github/managing-your-work-on-github/about-labels": "/enterprise/2.17/user/github/managing-your-work-on-github/about-labels", + "/enterprise/2.17/user/managing-your-work-on-github/about-milestones": "/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", + "/enterprise/2.17/github/managing-your-work-on-github/about-milestones": "/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones", + "/enterprise/2.17/user/managing-your-work-on-github/about-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", + "/enterprise/2.17/github/managing-your-work-on-github/about-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards", + "/enterprise/2.17/user/managing-your-work-on-github/about-task-lists": "/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", + "/enterprise/2.17/github/managing-your-work-on-github/about-task-lists": "/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists", + "/enterprise/2.17/user/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/adding-notes-to-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/adding-notes-to-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/archiving-cards-on-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/archiving-cards-on-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", + "/enterprise/2.17/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": "/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users", + "/enterprise/2.17/user/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/changing-project-board-visibility": "/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", + "/enterprise/2.17/github/managing-your-work-on-github/changing-project-board-visibility": "/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility", + "/enterprise/2.17/user/managing-your-work-on-github/closing-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/closing-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/configuring-automation-for-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", + "/enterprise/2.17/github/managing-your-work-on-github/configuring-automation-for-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards", + "/enterprise/2.17/user/managing-your-work-on-github/creating-a-label": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", + "/enterprise/2.17/github/managing-your-work-on-github/creating-a-label": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label", + "/enterprise/2.17/user/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", + "/enterprise/2.17/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet", + "/enterprise/2.17/user/managing-your-work-on-github/creating-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/creating-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/creating-an-issue": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", + "/enterprise/2.17/github/managing-your-work-on-github/creating-an-issue": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue", + "/enterprise/2.17/user/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/deleting-a-label": "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", + "/enterprise/2.17/github/managing-your-work-on-github/deleting-a-label": "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label", + "/enterprise/2.17/user/managing-your-work-on-github/deleting-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/deleting-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/deleting-an-issue": "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", + "/enterprise/2.17/github/managing-your-work-on-github/deleting-an-issue": "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue", + "/enterprise/2.17/user/managing-your-work-on-github/disabling-issues": "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", + "/enterprise/2.17/github/managing-your-work-on-github/disabling-issues": "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues", + "/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", + "/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository", + "/enterprise/2.17/user/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", + "/enterprise/2.17/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization", + "/enterprise/2.17/user/managing-your-work-on-github/editing-a-label": "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", + "/enterprise/2.17/github/managing-your-work-on-github/editing-a-label": "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label", + "/enterprise/2.17/user/managing-your-work-on-github/editing-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/editing-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/filtering-cards-on-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/filtering-cards-on-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", + "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees", + "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", + "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels", + "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", + "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone", + "/enterprise/2.17/user/managing-your-work-on-github/filtering-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/filtering-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", + "/enterprise/2.17/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status", + "/enterprise/2.17/user/managing-your-work-on-github/finding-information-in-a-repository": "/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", + "/enterprise/2.17/github/managing-your-work-on-github/finding-information-in-a-repository": "/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository", + "/enterprise/2.17/user/managing-your-work-on-github": "/enterprise/2.17/user/github/managing-your-work-on-github", + "/enterprise/2.17/github/managing-your-work-on-github": "/enterprise/2.17/user/github/managing-your-work-on-github", + "/enterprise/2.17/user/managing-your-work-on-github/labeling-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/labeling-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", + "/enterprise/2.17/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue", + "/enterprise/2.17/user/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/managing-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", + "/enterprise/2.17/github/managing-your-work-on-github/managing-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards", + "/enterprise/2.17/user/managing-your-work-on-github/managing-your-work-with-issues": "/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", + "/enterprise/2.17/github/managing-your-work-on-github/managing-your-work-with-issues": "/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues", + "/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-a-comment": "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", + "/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-a-comment": "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment", + "/enterprise/2.17/user/managing-your-work-on-github/opening-an-issue-from-code": "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", + "/enterprise/2.17/github/managing-your-work-on-github/opening-an-issue-from-code": "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code", + "/enterprise/2.17/user/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", + "/enterprise/2.17/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": "/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository", + "/enterprise/2.17/user/managing-your-work-on-github/reopening-a-closed-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/reopening-a-closed-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/sharing-filters": "/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", + "/enterprise/2.17/github/managing-your-work-on-github/sharing-filters": "/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters", + "/enterprise/2.17/user/managing-your-work-on-github/sorting-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/sorting-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/tracking-progress-on-your-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", + "/enterprise/2.17/github/managing-your-work-on-github/tracking-progress-on-your-project-board": "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board", + "/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", + "/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones", + "/enterprise/2.17/user/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", + "/enterprise/2.17/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards", + "/enterprise/2.17/user/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", + "/enterprise/2.17/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests", + "/enterprise/2.17/user/managing-your-work-on-github/viewing-your-milestones-progress": "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", + "/enterprise/2.17/github/managing-your-work-on-github/viewing-your-milestones-progress": "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-email-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-email-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/about-web-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/about-web-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/managing-your-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/managing-your-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories", + "/enterprise/2.17/user/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", + "/enterprise/2.17/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions", + "/enterprise/2.17/user/searching-for-information-on-github/about-searching-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", + "/enterprise/2.17/github/searching-for-information-on-github/about-searching-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github", + "/enterprise/2.17/user/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", + "/enterprise/2.17/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": "/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server", + "/enterprise/2.17/user/searching-for-information-on-github/finding-files-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", + "/enterprise/2.17/github/searching-for-information-on-github/finding-files-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github", + "/enterprise/2.17/user/searching-for-information-on-github/getting-started-with-searching-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", + "/enterprise/2.17/github/searching-for-information-on-github/getting-started-with-searching-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github", + "/enterprise/2.17/user/searching-for-information-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github", + "/enterprise/2.17/github/searching-for-information-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github", + "/enterprise/2.17/user/searching-for-information-on-github/searching-code": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", + "/enterprise/2.17/github/searching-for-information-on-github/searching-code": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-code", + "/enterprise/2.17/user/searching-for-information-on-github/searching-commits": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", + "/enterprise/2.17/github/searching-for-information-on-github/searching-commits": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits", + "/enterprise/2.17/user/searching-for-information-on-github/searching-for-repositories": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", + "/enterprise/2.17/github/searching-for-information-on-github/searching-for-repositories": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories", + "/enterprise/2.17/user/searching-for-information-on-github/searching-in-forks": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", + "/enterprise/2.17/github/searching-for-information-on-github/searching-in-forks": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks", + "/enterprise/2.17/user/searching-for-information-on-github/searching-issues-and-pull-requests": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", + "/enterprise/2.17/github/searching-for-information-on-github/searching-issues-and-pull-requests": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests", + "/enterprise/2.17/user/searching-for-information-on-github/searching-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", + "/enterprise/2.17/github/searching-for-information-on-github/searching-on-github": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github", + "/enterprise/2.17/user/searching-for-information-on-github/searching-topics": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", + "/enterprise/2.17/github/searching-for-information-on-github/searching-topics": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics", + "/enterprise/2.17/user/searching-for-information-on-github/searching-users": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", + "/enterprise/2.17/github/searching-for-information-on-github/searching-users": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-users", + "/enterprise/2.17/user/searching-for-information-on-github/searching-wikis": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", + "/enterprise/2.17/github/searching-for-information-on-github/searching-wikis": "/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis", + "/enterprise/2.17/user/searching-for-information-on-github/sorting-search-results": "/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", + "/enterprise/2.17/github/searching-for-information-on-github/sorting-search-results": "/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results", + "/enterprise/2.17/user/searching-for-information-on-github/troubleshooting-search-queries": "/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", + "/enterprise/2.17/github/searching-for-information-on-github/troubleshooting-search-queries": "/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries", + "/enterprise/2.17/user/searching-for-information-on-github/understanding-the-search-syntax": "/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", + "/enterprise/2.17/github/searching-for-information-on-github/understanding-the-search-syntax": "/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-organizations": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-organizations": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-teams": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-teams": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/creating-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/creating-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository", + "/enterprise/2.17/user/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", + "/enterprise/2.17/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/about-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/about-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/customizing-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/customizing-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", + "/enterprise/2.17/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-organization-membership": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-organization-membership": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address", + "/enterprise/2.17/user/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", + "/enterprise/2.17/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization", + "/enterprise/2.17/user/site-policy/github-insights-and-data-protection-for-your-organization": "/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", + "/enterprise/2.17/github/site-policy/github-insights-and-data-protection-for-your-organization": "/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization", + "/enterprise/2.17/user/using-git/about-git-rebase": "/enterprise/2.17/user/github/using-git/about-git-rebase", + "/enterprise/2.17/github/using-git/about-git-rebase": "/enterprise/2.17/user/github/using-git/about-git-rebase", + "/enterprise/2.17/user/using-git/about-git-subtree-merges": "/enterprise/2.17/user/github/using-git/about-git-subtree-merges", + "/enterprise/2.17/github/using-git/about-git-subtree-merges": "/enterprise/2.17/user/github/using-git/about-git-subtree-merges", + "/enterprise/2.17/user/using-git/about-remote-repositories": "/enterprise/2.17/user/github/using-git/about-remote-repositories", + "/enterprise/2.17/github/using-git/about-remote-repositories": "/enterprise/2.17/user/github/using-git/about-remote-repositories", + "/enterprise/2.17/user/using-git/adding-a-remote": "/enterprise/2.17/user/github/using-git/adding-a-remote", + "/enterprise/2.17/github/using-git/adding-a-remote": "/enterprise/2.17/user/github/using-git/adding-a-remote", + "/enterprise/2.17/user/using-git/associating-text-editors-with-git": "/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", + "/enterprise/2.17/github/using-git/associating-text-editors-with-git": "/enterprise/2.17/user/github/using-git/associating-text-editors-with-git", + "/enterprise/2.17/user/using-git/caching-your-github-password-in-git": "/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", + "/enterprise/2.17/github/using-git/caching-your-github-password-in-git": "/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git", + "/enterprise/2.17/user/using-git/changing-a-remotes-url": "/enterprise/2.17/user/github/using-git/changing-a-remotes-url", + "/enterprise/2.17/github/using-git/changing-a-remotes-url": "/enterprise/2.17/user/github/using-git/changing-a-remotes-url", + "/enterprise/2.17/user/using-git/changing-author-info": "/enterprise/2.17/user/github/using-git/changing-author-info", + "/enterprise/2.17/github/using-git/changing-author-info": "/enterprise/2.17/user/github/using-git/changing-author-info", + "/enterprise/2.17/user/using-git/configuring-git-to-handle-line-endings": "/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", + "/enterprise/2.17/github/using-git/configuring-git-to-handle-line-endings": "/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings", + "/enterprise/2.17/user/using-git/dealing-with-non-fast-forward-errors": "/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", + "/enterprise/2.17/github/using-git/dealing-with-non-fast-forward-errors": "/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors", + "/enterprise/2.17/user/using-git/getting-changes-from-a-remote-repository": "/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", + "/enterprise/2.17/github/using-git/getting-changes-from-a-remote-repository": "/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository", + "/enterprise/2.17/user/using-git/getting-started-with-git-and-github": "/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", + "/enterprise/2.17/github/using-git/getting-started-with-git-and-github": "/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github", + "/enterprise/2.17/user/using-git/git-workflows": "/enterprise/2.17/user/github/using-git/git-workflows", + "/enterprise/2.17/github/using-git/git-workflows": "/enterprise/2.17/user/github/using-git/git-workflows", + "/enterprise/2.17/user/using-git/ignoring-files": "/enterprise/2.17/user/github/using-git/ignoring-files", + "/enterprise/2.17/github/using-git/ignoring-files": "/enterprise/2.17/user/github/using-git/ignoring-files", + "/enterprise/2.17/user/using-git": "/enterprise/2.17/user/github/using-git", + "/enterprise/2.17/github/using-git": "/enterprise/2.17/user/github/using-git", + "/enterprise/2.17/user/using-git/learning-about-git": "/enterprise/2.17/user/github/using-git/learning-about-git", + "/enterprise/2.17/github/using-git/learning-about-git": "/enterprise/2.17/user/github/using-git/learning-about-git", + "/enterprise/2.17/user/using-git/managing-remote-repositories": "/enterprise/2.17/user/github/using-git/managing-remote-repositories", + "/enterprise/2.17/github/using-git/managing-remote-repositories": "/enterprise/2.17/user/github/using-git/managing-remote-repositories", + "/enterprise/2.17/user/using-git/pushing-commits-to-a-remote-repository": "/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", + "/enterprise/2.17/github/using-git/pushing-commits-to-a-remote-repository": "/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository", + "/enterprise/2.17/user/using-git/removing-a-remote": "/enterprise/2.17/user/github/using-git/removing-a-remote", + "/enterprise/2.17/github/using-git/removing-a-remote": "/enterprise/2.17/user/github/using-git/removing-a-remote", + "/enterprise/2.17/user/using-git/renaming-a-remote": "/enterprise/2.17/user/github/using-git/renaming-a-remote", + "/enterprise/2.17/github/using-git/renaming-a-remote": "/enterprise/2.17/user/github/using-git/renaming-a-remote", + "/enterprise/2.17/user/using-git/resolving-merge-conflicts-after-a-git-rebase": "/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", + "/enterprise/2.17/github/using-git/resolving-merge-conflicts-after-a-git-rebase": "/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase", + "/enterprise/2.17/user/using-git/setting-your-username-in-git": "/enterprise/2.17/user/github/using-git/setting-your-username-in-git", + "/enterprise/2.17/github/using-git/setting-your-username-in-git": "/enterprise/2.17/user/github/using-git/setting-your-username-in-git", + "/enterprise/2.17/user/using-git/splitting-a-subfolder-out-into-a-new-repository": "/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", + "/enterprise/2.17/github/using-git/splitting-a-subfolder-out-into-a-new-repository": "/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository", + "/enterprise/2.17/user/using-git/updating-credentials-from-the-osx-keychain": "/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", + "/enterprise/2.17/github/using-git/updating-credentials-from-the-osx-keychain": "/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain", + "/enterprise/2.17/user/using-git/using-advanced-git-commands": "/enterprise/2.17/user/github/using-git/using-advanced-git-commands", + "/enterprise/2.17/github/using-git/using-advanced-git-commands": "/enterprise/2.17/user/github/using-git/using-advanced-git-commands", + "/enterprise/2.17/user/using-git/using-common-git-commands": "/enterprise/2.17/user/github/using-git/using-common-git-commands", + "/enterprise/2.17/github/using-git/using-common-git-commands": "/enterprise/2.17/user/github/using-git/using-common-git-commands", + "/enterprise/2.17/user/using-git/using-git-rebase-on-the-command-line": "/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", + "/enterprise/2.17/github/using-git/using-git-rebase-on-the-command-line": "/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line", + "/enterprise/2.17/user/using-git/which-remote-url-should-i-use": "/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", + "/enterprise/2.17/github/using-git/which-remote-url-should-i-use": "/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use", + "/enterprise/2.17/user/using-git/why-is-git-always-asking-for-my-password": "/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", + "/enterprise/2.17/github/using-git/why-is-git-always-asking-for-my-password": "/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/about-repository-graphs": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/about-repository-graphs": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository", + "/enterprise/2.17/user/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", + "/enterprise/2.17/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository", + "/enterprise/2.17/user/working-with-github-pages/about-github-pages-and-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", + "/enterprise/2.17/github/working-with-github-pages/about-github-pages-and-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll", + "/enterprise/2.17/user/working-with-github-pages/about-github-pages": "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", + "/enterprise/2.17/github/working-with-github-pages/about-github-pages": "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages", + "/enterprise/2.17/user/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.17/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.17/user/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", + "/enterprise/2.17/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll", + "/enterprise/2.17/user/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", + "/enterprise/2.17/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll", + "/enterprise/2.17/user/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", + "/enterprise/2.17/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", + "/enterprise/2.17/user/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", + "/enterprise/2.17/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", + "/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", + "/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll", + "/enterprise/2.17/user/working-with-github-pages/creating-a-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", + "/enterprise/2.17/github/working-with-github-pages/creating-a-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site", + "/enterprise/2.17/user/working-with-github-pages/getting-started-with-github-pages": "/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", + "/enterprise/2.17/github/working-with-github-pages/getting-started-with-github-pages": "/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages", + "/enterprise/2.17/user/working-with-github-pages": "/enterprise/2.17/user/github/working-with-github-pages", + "/enterprise/2.17/github/working-with-github-pages": "/enterprise/2.17/user/github/working-with-github-pages", + "/enterprise/2.17/user/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", + "/enterprise/2.17/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", + "/enterprise/2.17/user/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", + "/enterprise/2.17/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll", + "/enterprise/2.17/user/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", + "/enterprise/2.17/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": "/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll", + "/enterprise/2.17/user/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.17/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": "/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites", + "/enterprise/2.17/user/working-with-github-pages/unpublishing-a-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", + "/enterprise/2.17/github/working-with-github-pages/unpublishing-a-github-pages-site": "/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site", + "/enterprise/2.17/user/writing-on-github/about-saved-replies": "/enterprise/2.17/user/github/writing-on-github/about-saved-replies", + "/enterprise/2.17/github/writing-on-github/about-saved-replies": "/enterprise/2.17/user/github/writing-on-github/about-saved-replies", + "/enterprise/2.17/user/writing-on-github/about-writing-and-formatting-on-github": "/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", + "/enterprise/2.17/github/writing-on-github/about-writing-and-formatting-on-github": "/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github", + "/enterprise/2.17/user/writing-on-github/autolinked-references-and-urls": "/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", + "/enterprise/2.17/github/writing-on-github/autolinked-references-and-urls": "/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls", + "/enterprise/2.17/user/writing-on-github/basic-writing-and-formatting-syntax": "/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", + "/enterprise/2.17/github/writing-on-github/basic-writing-and-formatting-syntax": "/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax", + "/enterprise/2.17/user/writing-on-github/creating-a-saved-reply": "/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", + "/enterprise/2.17/github/writing-on-github/creating-a-saved-reply": "/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply", + "/enterprise/2.17/user/writing-on-github/creating-and-highlighting-code-blocks": "/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", + "/enterprise/2.17/github/writing-on-github/creating-and-highlighting-code-blocks": "/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks", + "/enterprise/2.17/user/writing-on-github/creating-gists": "/enterprise/2.17/user/github/writing-on-github/creating-gists", + "/enterprise/2.17/github/writing-on-github/creating-gists": "/enterprise/2.17/user/github/writing-on-github/creating-gists", + "/enterprise/2.17/user/writing-on-github/deleting-a-saved-reply": "/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", + "/enterprise/2.17/github/writing-on-github/deleting-a-saved-reply": "/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply", + "/enterprise/2.17/user/writing-on-github/editing-a-saved-reply": "/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", + "/enterprise/2.17/github/writing-on-github/editing-a-saved-reply": "/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply", + "/enterprise/2.17/user/writing-on-github/editing-and-sharing-content-with-gists": "/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", + "/enterprise/2.17/github/writing-on-github/editing-and-sharing-content-with-gists": "/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists", + "/enterprise/2.17/user/writing-on-github/forking-and-cloning-gists": "/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", + "/enterprise/2.17/github/writing-on-github/forking-and-cloning-gists": "/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists", + "/enterprise/2.17/user/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", + "/enterprise/2.17/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": "/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github", + "/enterprise/2.17/user/writing-on-github": "/enterprise/2.17/user/github/writing-on-github", + "/enterprise/2.17/github/writing-on-github": "/enterprise/2.17/user/github/writing-on-github", + "/enterprise/2.17/user/writing-on-github/organizing-information-with-tables": "/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", + "/enterprise/2.17/github/writing-on-github/organizing-information-with-tables": "/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables", + "/enterprise/2.17/user/writing-on-github/using-saved-replies": "/enterprise/2.17/user/github/writing-on-github/using-saved-replies", + "/enterprise/2.17/github/writing-on-github/using-saved-replies": "/enterprise/2.17/user/github/writing-on-github/using-saved-replies", + "/enterprise/2.17/user/writing-on-github/working-with-advanced-formatting": "/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", + "/enterprise/2.17/github/writing-on-github/working-with-advanced-formatting": "/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting", + "/enterprise/2.17/user/writing-on-github/working-with-saved-replies": "/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", + "/enterprise/2.17/github/writing-on-github/working-with-saved-replies": "/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies", + "/enterprise/2.17/graphql/guides/forming-calls-with-graphql": "/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql", + "/enterprise/2.17/graphql/guides": "/enterprise/2.17/user/graphql/guides", + "/enterprise/2.17/graphql/guides/introduction-to-graphql": "/enterprise/2.17/user/graphql/guides/introduction-to-graphql", + "/enterprise/2.17/graphql/guides/migrating-from-rest-to-graphql": "/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/2.17/graphql/guides/using-global-node-ids": "/enterprise/2.17/user/graphql/guides/using-global-node-ids", + "/enterprise/2.17/graphql/guides/using-the-explorer": "/enterprise/2.17/user/graphql/guides/using-the-explorer", + "/enterprise/2.17/graphql": "/enterprise/2.17/user/graphql", + "/enterprise/2.17/graphql/overview/about-the-graphql-api": "/enterprise/2.17/user/graphql/overview/about-the-graphql-api", + "/enterprise/2.17/graphql/overview/breaking-changes": "/enterprise/2.17/user/graphql/overview/breaking-changes", + "/enterprise/2.17/graphql/overview/changelog": "/enterprise/2.17/user/graphql/overview/changelog", + "/enterprise/2.17/graphql/overview/explorer": "/enterprise/2.17/user/graphql/overview/explorer", + "/enterprise/2.17/graphql/overview": "/enterprise/2.17/user/graphql/overview", + "/enterprise/2.17/graphql/overview/resource-limitations": "/enterprise/2.17/user/graphql/overview/resource-limitations", + "/enterprise/2.17/graphql/overview/schema-previews": "/enterprise/2.17/user/graphql/overview/schema-previews", + "/enterprise/2.17/graphql/reference/enums": "/enterprise/2.17/user/graphql/reference/enums", + "/enterprise/2.17/graphql/reference": "/enterprise/2.17/user/graphql/reference", + "/enterprise/2.17/graphql/reference/input-objects": "/enterprise/2.17/user/graphql/reference/input-objects", + "/enterprise/2.17/graphql/reference/interfaces": "/enterprise/2.17/user/graphql/reference/interfaces", + "/enterprise/2.17/graphql/reference/mutations": "/enterprise/2.17/user/graphql/reference/mutations", + "/enterprise/2.17/graphql/reference/objects": "/enterprise/2.17/user/graphql/reference/objects", + "/enterprise/2.17/graphql/reference/queries": "/enterprise/2.17/user/graphql/reference/queries", + "/enterprise/2.17/graphql/reference/scalars": "/enterprise/2.17/user/graphql/reference/scalars", + "/enterprise/2.17/graphql/reference/unions": "/enterprise/2.17/user/graphql/reference/unions", + "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise": "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise", + "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights", + "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights", + "/enterprise/2.17/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports", + "/enterprise/2.17/insights": "/enterprise/2.17/user/insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/about-data-in-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/about-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise", + "/enterprise/2.17/insights/installing-and-configuring-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/installing-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-events": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-goals": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-organizations": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/managing-repositories": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights", + "/enterprise/2.17/insights/installing-and-configuring-github-insights/updating-github-insights": "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights", + "/enterprise/2.17/rest": "/enterprise/2.17/user/rest", + "/enterprise/2.17/rest/reference/actions": "/enterprise/2.17/user/rest/reference/actions", + "/enterprise/2.17/rest/reference/activity": "/enterprise/2.17/user/rest/reference/activity", + "/enterprise/2.17/rest/reference/apps": "/enterprise/2.17/user/rest/reference/apps", + "/enterprise/2.17/rest/reference/checks": "/enterprise/2.17/user/rest/reference/checks", + "/enterprise/2.17/rest/reference/codes-of-conduct": "/enterprise/2.17/user/rest/reference/codes-of-conduct", + "/enterprise/2.17/rest/reference/emojis": "/enterprise/2.17/user/rest/reference/emojis", + "/enterprise/2.17/rest/reference/endpoints-available-for-github-apps": "/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps", + "/enterprise/2.17/rest/reference/enterprise-admin": "/enterprise/2.17/user/rest/reference/enterprise-admin", + "/enterprise/2.17/rest/reference/gists": "/enterprise/2.17/user/rest/reference/gists", + "/enterprise/2.17/rest/reference/git": "/enterprise/2.17/user/rest/reference/git", + "/enterprise/2.17/rest/reference/gitignore": "/enterprise/2.17/user/rest/reference/gitignore", + "/enterprise/2.17/rest/reference": "/enterprise/2.17/user/rest/reference", + "/enterprise/2.17/rest/reference/interactions": "/enterprise/2.17/user/rest/reference/interactions", + "/enterprise/2.17/rest/reference/issues": "/enterprise/2.17/user/rest/reference/issues", + "/enterprise/2.17/rest/reference/licenses": "/enterprise/2.17/user/rest/reference/licenses", + "/enterprise/2.17/rest/reference/markdown": "/enterprise/2.17/user/rest/reference/markdown", + "/enterprise/2.17/rest/reference/meta": "/enterprise/2.17/user/rest/reference/meta", + "/enterprise/2.17/rest/reference/migrations": "/enterprise/2.17/user/rest/reference/migrations", + "/enterprise/2.17/rest/reference/oauth-authorizations": "/enterprise/2.17/user/rest/reference/oauth-authorizations", + "/enterprise/2.17/rest/reference/orgs": "/enterprise/2.17/user/rest/reference/orgs", + "/enterprise/2.17/rest/reference/projects": "/enterprise/2.17/user/rest/reference/projects", + "/enterprise/2.17/rest/reference/pulls": "/enterprise/2.17/user/rest/reference/pulls", + "/enterprise/2.17/rest/reference/rate-limit": "/enterprise/2.17/user/rest/reference/rate-limit", + "/enterprise/2.17/rest/reference/reactions": "/enterprise/2.17/user/rest/reference/reactions", + "/enterprise/2.17/rest/reference/repos": "/enterprise/2.17/user/rest/reference/repos", + "/enterprise/2.17/rest/reference/scim": "/enterprise/2.17/user/rest/reference/scim", + "/enterprise/2.17/rest/reference/search": "/enterprise/2.17/user/rest/reference/search", + "/enterprise/2.17/rest/reference/teams": "/enterprise/2.17/user/rest/reference/teams", + "/enterprise/2.17/rest/reference/users": "/enterprise/2.17/user/rest/reference/users", + "/enterprise/2.17/admin/articles/configuring-unified-contributions-between-github-enterprise-and-githubcom": null, + "/enterprise/2.17/admin/articles/including-github-enterprise-contributions-in-your-githubcom-profile": null, + "/enterprise/2.17/admin/articles/using-github-task-runner": null, + "/enterprise/2.17/admin/clustering/about-cluster-nodes": null, + "/enterprise/2.17/admin/clustering/about-clustering": null, + "/enterprise/2.17/admin/clustering/cluster-network-configuration": null, + "/enterprise/2.17/admin/clustering/differences-between-clustering-and-high-availability-ha": null, + "/enterprise/2.17/admin/clustering/evacuating-a-cluster-node": null, + "/enterprise/2.17/admin/clustering": null, + "/enterprise/2.17/admin/clustering/initializing-the-cluster": null, + "/enterprise/2.17/admin/clustering/managing-a-github-enterprise-server-cluster": null, + "/enterprise/2.17/admin/clustering/monitoring-cluster-nodes": null, + "/enterprise/2.17/admin/clustering/overview": null, + "/enterprise/2.17/admin/clustering/replacing-a-cluster-node": null, + "/enterprise/2.17/admin/clustering/setting-up-the-cluster-instances": null, + "/enterprise/2.17/admin/clustering/upgrading-a-cluster": null, + "/enterprise/2.17/admin/developer-workflow/about-pre-receive-hooks": null, + "/enterprise/2.17/admin/developer-workflow/about-protected-branches-and-required-status-checks": null, + "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-on-your-appliance": null, + "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-a-repository": null, + "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization": null, + "/enterprise/2.17/admin/developer-workflow/blocking-force-pushes": null, + "/enterprise/2.17/admin/developer-workflow/configuring-protected-branches-and-required-status-checks": null, + "/enterprise/2.17/admin/developer-workflow/continuous-integration-using-jenkins": null, + "/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-environment": null, + "/enterprise/2.17/admin/developer-workflow/creating-a-pre-receive-hook-script": null, + "/enterprise/2.17/admin/developer-workflow/customizing-your-instance-with-integrations": null, + "/enterprise/2.17/admin/developer-workflow/establishing-pull-request-merge-conditions": null, + "/enterprise/2.17/admin/developer-workflow": null, + "/enterprise/2.17/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance": null, + "/enterprise/2.17/admin/developer-workflow/managing-projects-using-jira": null, + "/enterprise/2.17/admin/developer-workflow/troubleshooting-service-hooks": null, + "/enterprise/2.17/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy": null, + "/enterprise/2.17/admin/developer-workflow/using-webhooks-for-continuous-integration": null, + "/enterprise/2.17/admin/enterprise-support/about-github-enterprise-support": null, + "/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server": null, + "/enterprise/2.17/admin/enterprise-support/about-github-premium-support-for-github-enterprise": null, + "/enterprise/2.17/admin/enterprise-support/about-support-for-advanced-security": null, + "/enterprise/2.17/admin/enterprise-support": null, + "/enterprise/2.17/admin/enterprise-support/overview": null, + "/enterprise/2.17/admin/enterprise-support/preparing-to-submit-a-ticket": null, + "/enterprise/2.17/admin/enterprise-support/providing-data-to-github-support": null, + "/enterprise/2.17/admin/enterprise-support/reaching-github-support": null, + "/enterprise/2.17/admin/enterprise-support/receiving-help-from-github-support": null, + "/enterprise/2.17/admin/enterprise-support/submitting-a-ticket": null, + "/enterprise/2.17/admin": null, + "/enterprise/2.17/admin/guides/installation/about-enterprise-accounts": null, + "/enterprise/2.17/admin/installation/about-enterprise-accounts": null, + "/enterprise/2.17/admin/installation/about-geo-replication": null, + "/enterprise/2.17/admin/installation/about-high-availability-configuration": null, + "/enterprise/2.17/admin/installation/about-the-github-enterprise-server-api": null, + "/enterprise/2.17/admin/installation/accessing-the-administrative-shell-ssh": null, + "/enterprise/2.17/admin/installation/accessing-the-management-console": null, + "/enterprise/2.17/admin/installation/accessing-the-monitor-dashboard": null, + "/enterprise/2.17/admin/installation/activity-dashboard": null, + "/enterprise/2.17/admin/installation/audit-logging": null, + "/enterprise/2.17/admin/installation/audited-actions": null, + "/enterprise/2.17/admin/installation/command-line-utilities": null, + "/enterprise/2.17/admin/installation/configuring-a-hostname": null, + "/enterprise/2.17/admin/installation/configuring-an-outbound-web-proxy-server": null, + "/enterprise/2.17/admin/installation/configuring-applications": null, + "/enterprise/2.17/admin/installation/configuring-backups-on-your-appliance": null, + "/enterprise/2.17/admin/installation/configuring-built-in-firewall-rules": null, + "/enterprise/2.17/admin/installation/configuring-collectd": null, + "/enterprise/2.17/admin/installation/configuring-dns-nameservers": null, + "/enterprise/2.17/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server": null, + "/enterprise/2.17/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server": null, + "/enterprise/2.17/admin/installation/configuring-git-large-file-storage": null, + "/enterprise/2.17/admin/installation/configuring-github-enterprise-server-for-high-availability": null, + "/enterprise/2.17/admin/installation/configuring-github-pages-on-your-appliance": null, + "/enterprise/2.17/admin/installation/configuring-rate-limits": null, + "/enterprise/2.17/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance": null, + "/enterprise/2.17/admin/installation/configuring-the-github-enterprise-server-appliance": null, + "/enterprise/2.17/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console": null, + "/enterprise/2.17/admin/installation/configuring-time-synchronization": null, + "/enterprise/2.17/admin/installation/configuring-tls": null, + "/enterprise/2.17/admin/installation/configuring-your-github-enterprise-server-network-settings": null, + "/enterprise/2.17/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud": null, + "/enterprise/2.17/admin/installation/creating-a-high-availability-replica": null, + "/enterprise/2.17/admin/installation/disabling-git-ssh-access-on-github-enterprise-server": null, + "/enterprise/2.17/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories": null, + "/enterprise/2.17/admin/installation/enabling-and-scheduling-maintenance-mode": null, + "/enterprise/2.17/admin/installation/enabling-automatic-update-checks": null, + "/enterprise/2.17/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud": null, + "/enterprise/2.17/admin/installation/enabling-private-mode": null, + "/enterprise/2.17/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server": null, + "/enterprise/2.17/admin/installation/enabling-subdomain-isolation": null, + "/enterprise/2.17/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.17/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom": null, + "/enterprise/2.17/admin/installation/getting-started-with-github-enterprise-server": null, + "/enterprise/2.17/admin/installation/increasing-cpu-or-memory-resources": null, + "/enterprise/2.17/admin/installation/increasing-storage-capacity": null, + "/enterprise/2.17/admin/installation": null, + "/enterprise/2.17/admin/installation/initiating-a-failover-to-your-replica-appliance": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-aws": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-azure": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-google-cloud-platform": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-hyper-v": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-openstack-kvm": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-vmware": null, + "/enterprise/2.17/admin/installation/installing-github-enterprise-server-on-xenserver": null, + "/enterprise/2.17/admin/installation/log-forwarding": null, + "/enterprise/2.17/admin/guides/installation/managing-billing-for-github-enterprise": null, + "/enterprise/2.17/admin/installation/managing-billing-for-github-enterprise": null, + "/enterprise/2.17/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud": null, + "/enterprise/2.17/admin/guides/installation/managing-your-github-enterprise-license": null, + "/enterprise/2.17/admin/installation/managing-your-github-enterprise-license": null, + "/enterprise/2.17/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later": null, + "/enterprise/2.17/admin/installation/migrating-from-github-enterprise-1110x-to-2123": null, + "/enterprise/2.17/admin/installation/migrating-to-a-different-git-large-file-storage-server": null, + "/enterprise/2.17/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance": null, + "/enterprise/2.17/admin/installation/monitoring-using-snmp": null, + "/enterprise/2.17/admin/installation/monitoring-your-github-enterprise-server-appliance": null, + "/enterprise/2.17/admin/installation/network-ports": null, + "/enterprise/2.17/admin/installation/recommended-alert-thresholds": null, + "/enterprise/2.17/admin/installation/recovering-a-high-availability-configuration": null, + "/enterprise/2.17/admin/installation/removing-a-high-availability-replica": null, + "/enterprise/2.17/admin/installation/searching-the-audit-log": null, + "/enterprise/2.17/admin/installation/setting-git-push-limits": null, + "/enterprise/2.17/admin/installation/setting-up-a-github-enterprise-server-instance": null, + "/enterprise/2.17/admin/installation/setting-up-a-staging-instance": null, + "/enterprise/2.17/admin/installation/setting-up-external-monitoring": null, + "/enterprise/2.17/admin/installation/site-admin-dashboard": null, + "/enterprise/2.17/admin/installation/system-overview": null, + "/enterprise/2.17/admin/installation/troubleshooting-ssl-errors": null, + "/enterprise/2.17/admin/installation/updating-the-virtual-machine-and-physical-resources": null, + "/enterprise/2.17/admin/installation/upgrade-requirements": null, + "/enterprise/2.17/admin/installation/upgrading-github-enterprise-server": null, + "/enterprise/2.17/admin/installation/using-github-enterprise-server-with-a-load-balancer": null, + "/enterprise/2.17/admin/installation/validating-your-domain-settings": null, + "/enterprise/2.17/admin/installation/viewing-push-logs": null, + "/enterprise/2.17/admin/migrations/about-migrations": null, + "/enterprise/2.17/admin/migrations/applying-the-imported-data-on-github-enterprise-server": null, + "/enterprise/2.17/admin/migrations/completing-the-import-on-github-enterprise-server": null, + "/enterprise/2.17/admin/migrations/exporting-migration-data-from-github-enterprise-server": null, + "/enterprise/2.17/admin/migrations/exporting-migration-data-from-githubcom": null, + "/enterprise/2.17/admin/migrations/exporting-the-github-enterprise-server-source-repositories": null, + "/enterprise/2.17/admin/migrations/exporting-the-githubcom-organizations-repositories": null, + "/enterprise/2.17/admin/migrations/generating-a-list-of-migration-conflicts": null, + "/enterprise/2.17/admin/migrations/importing-data-from-third-party-version-control-systems": null, + "/enterprise/2.17/admin/migrations/importing-migration-data-to-github-enterprise-server": null, + "/enterprise/2.17/admin/migrations": null, + "/enterprise/2.17/admin/migrations/overview": null, + "/enterprise/2.17/admin/migrations/preparing-the-github-enterprise-server-source-instance": null, + "/enterprise/2.17/admin/migrations/preparing-the-githubcom-source-organization": null, + "/enterprise/2.17/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server": null, + "/enterprise/2.17/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings": null, + "/enterprise/2.17/admin/migrations/reviewing-migration-conflicts": null, + "/enterprise/2.17/admin/migrations/reviewing-migration-data": null, + "/enterprise/2.17/admin/user-management/about-global-webhooks": null, + "/enterprise/2.17/admin/user-management/adding-people-to-teams": null, + "/enterprise/2.17/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories": null, + "/enterprise/2.17/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider": null, + "/enterprise/2.17/admin/user-management/archiving-and-unarchiving-repositories": null, + "/enterprise/2.17/admin/user-management/auditing-ssh-keys": null, + "/enterprise/2.17/admin/user-management/auditing-users-across-your-instance": null, + "/enterprise/2.17/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance": null, + "/enterprise/2.17/admin/user-management/basic-account-settings": null, + "/enterprise/2.17/admin/user-management/best-practices-for-user-security": null, + "/enterprise/2.17/admin/user-management/changing-authentication-methods": null, + "/enterprise/2.17/admin/user-management/configuring-email-for-notifications": null, + "/enterprise/2.17/admin/user-management/configuring-visibility-for-organization-membership": null, + "/enterprise/2.17/admin/user-management/creating-organizations": null, + "/enterprise/2.17/admin/user-management/creating-teams": null, + "/enterprise/2.17/admin/user-management/customizing-user-messages-on-your-instance": null, + "/enterprise/2.17/admin/user-management/disabling-unauthenticated-sign-ups": null, + "/enterprise/2.17/admin/user-management": null, + "/enterprise/2.17/admin/user-management/managing-dormant-users": null, + "/enterprise/2.17/admin/user-management/managing-global-webhooks": null, + "/enterprise/2.17/admin/user-management/organizations-and-teams": null, + "/enterprise/2.17/admin/user-management/placing-a-legal-hold-on-a-user-or-organization": null, + "/enterprise/2.17/admin/user-management/preventing-users-from-changing-a-repositorys-visibility": null, + "/enterprise/2.17/admin/user-management/preventing-users-from-changing-anonymous-git-read-access": null, + "/enterprise/2.17/admin/user-management/preventing-users-from-creating-organizations": null, + "/enterprise/2.17/admin/user-management/preventing-users-from-deleting-organization-repositories": null, + "/enterprise/2.17/admin/user-management/promoting-or-demoting-a-site-administrator": null, + "/enterprise/2.17/admin/user-management/rebuilding-contributions-data": null, + "/enterprise/2.17/admin/user-management/removing-users-from-teams-and-organizations": null, + "/enterprise/2.17/admin/user-management/repositories": null, + "/enterprise/2.17/admin/user-management/requiring-two-factor-authentication-for-an-organization": null, + "/enterprise/2.17/admin/user-management/restricting-repository-creation-in-your-instance": null, + "/enterprise/2.17/admin/user-management/suspending-and-unsuspending-users": null, + "/enterprise/2.17/admin/user-management/user-security": null, + "/enterprise/2.17/admin/user-management/using-built-in-authentication": null, + "/enterprise/2.17/admin/user-management/using-cas": null, + "/enterprise/2.17/admin/user-management/using-ldap": null, + "/enterprise/2.17/admin/user-management/using-saml": null, + "/enterprise/2.17": null, + "/enterprise/2.17/user/github/administering-a-repository/about-branch-restrictions": null, + "/enterprise/2.17/user/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/about-merge-methods-on-github": null, + "/enterprise/2.17/user/github/administering-a-repository/about-protected-branches": null, + "/enterprise/2.17/user/github/administering-a-repository/about-releases": null, + "/enterprise/2.17/user/github/administering-a-repository/about-required-commit-signing": null, + "/enterprise/2.17/user/github/administering-a-repository/about-required-reviews-for-pull-requests": null, + "/enterprise/2.17/user/github/administering-a-repository/about-required-status-checks": null, + "/enterprise/2.17/user/github/administering-a-repository/automation-for-release-forms-with-query-parameters": null, + "/enterprise/2.17/user/github/administering-a-repository/classifying-your-repository-with-topics": null, + "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests": null, + "/enterprise/2.17/user/github/administering-a-repository/configuring-commit-squashing-for-pull-requests": null, + "/enterprise/2.17/user/github/administering-a-repository/configuring-protected-branches": null, + "/enterprise/2.17/user/github/administering-a-repository/configuring-pull-request-merges": null, + "/enterprise/2.17/user/github/administering-a-repository/customizing-how-changed-files-appear-on-github": null, + "/enterprise/2.17/user/github/administering-a-repository/defining-the-mergeability-of-pull-requests": null, + "/enterprise/2.17/user/github/administering-a-repository/deleting-a-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request": null, + "/enterprise/2.17/user/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/enabling-branch-restrictions": null, + "/enterprise/2.17/user/github/administering-a-repository/enabling-required-commit-signing": null, + "/enterprise/2.17/user/github/administering-a-repository/enabling-required-reviews-for-pull-requests": null, + "/enterprise/2.17/user/github/administering-a-repository/enabling-required-status-checks": null, + "/enterprise/2.17/user/github/administering-a-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/linking-to-releases": null, + "/enterprise/2.17/user/github/administering-a-repository/managing-branches-in-your-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/managing-releases-in-a-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/managing-repository-settings": null, + "/enterprise/2.17/user/github/administering-a-repository/managing-the-forking-policy-for-your-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/releasing-projects-on-github": null, + "/enterprise/2.17/user/github/administering-a-repository/renaming-a-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/setting-repository-visibility": null, + "/enterprise/2.17/user/github/administering-a-repository/setting-the-default-branch": null, + "/enterprise/2.17/user/github/administering-a-repository/transferring-a-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/types-of-required-status-checks": null, + "/enterprise/2.17/user/github/administering-a-repository/viewing-branches-in-your-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/viewing-deployment-activity-for-your-repository": null, + "/enterprise/2.17/user/github/administering-a-repository/viewing-your-repositorys-releases-and-tags": null, + "/enterprise/2.17/user/github/authenticating-to-github/about-commit-signature-verification": null, + "/enterprise/2.17/user/github/authenticating-to-github/about-ssh": null, + "/enterprise/2.17/user/github/authenticating-to-github/about-two-factor-authentication": null, + "/enterprise/2.17/user/github/authenticating-to-github/accessing-github-using-two-factor-authentication": null, + "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account": null, + "/enterprise/2.17/user/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account": null, + "/enterprise/2.17/user/github/authenticating-to-github/associating-an-email-with-your-gpg-key": null, + "/enterprise/2.17/user/github/authenticating-to-github/authorizing-oauth-apps": null, + "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-gpg-keys": null, + "/enterprise/2.17/user/github/authenticating-to-github/checking-for-existing-ssh-keys": null, + "/enterprise/2.17/user/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status": null, + "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods": null, + "/enterprise/2.17/user/github/authenticating-to-github/configuring-two-factor-authentication": null, + "/enterprise/2.17/user/github/authenticating-to-github/connecting-to-github-with-ssh": null, + "/enterprise/2.17/user/github/authenticating-to-github/connecting-with-third-party-applications": null, + "/enterprise/2.17/user/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line": null, + "/enterprise/2.17/user/github/authenticating-to-github/creating-a-strong-password": null, + "/enterprise/2.17/user/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-agent-admitted-failure-to-sign": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-bad-file-number": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-key-already-in-use": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-permission-denied-publickey": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-ssh-add-illegal-option----k": null, + "/enterprise/2.17/user/github/authenticating-to-github/error-were-doing-an-ssh-key-audit": null, + "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-gpg-key": null, + "/enterprise/2.17/user/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent": null, + "/enterprise/2.17/user/github/authenticating-to-github": null, + "/enterprise/2.17/user/github/authenticating-to-github/keeping-your-account-and-data-secure": null, + "/enterprise/2.17/user/github/authenticating-to-github/managing-commit-signature-verification": null, + "/enterprise/2.17/user/github/authenticating-to-github/preventing-unauthorized-access": null, + "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials": null, + "/enterprise/2.17/user/github/authenticating-to-github/recovering-your-ssh-key-passphrase": null, + "/enterprise/2.17/user/github/authenticating-to-github/removing-sensitive-data-from-a-repository": null, + "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-applications-oauth": null, + "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-authorized-integrations": null, + "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-deploy-keys": null, + "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-security-log": null, + "/enterprise/2.17/user/github/authenticating-to-github/reviewing-your-ssh-keys": null, + "/enterprise/2.17/user/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa": null, + "/enterprise/2.17/user/github/authenticating-to-github/signing-commits": null, + "/enterprise/2.17/user/github/authenticating-to-github/signing-tags": null, + "/enterprise/2.17/user/github/authenticating-to-github/sudo-mode": null, + "/enterprise/2.17/user/github/authenticating-to-github/telling-git-about-your-signing-key": null, + "/enterprise/2.17/user/github/authenticating-to-github/testing-your-ssh-connection": null, + "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-commit-signature-verification": null, + "/enterprise/2.17/user/github/authenticating-to-github/troubleshooting-ssh": null, + "/enterprise/2.17/user/github/authenticating-to-github/updating-an-expired-gpg-key": null, + "/enterprise/2.17/user/github/authenticating-to-github/updating-your-github-access-credentials": null, + "/enterprise/2.17/user/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key": null, + "/enterprise/2.17/user/github/authenticating-to-github/working-with-ssh-key-passphrases": null, + "/enterprise/2.17/user/github/building-a-strong-community/about-issue-and-pull-request-templates": null, + "/enterprise/2.17/user/github/building-a-strong-community/about-team-discussions": null, + "/enterprise/2.17/user/github/building-a-strong-community/about-wikis": null, + "/enterprise/2.17/user/github/building-a-strong-community/adding-a-license-to-a-repository": null, + "/enterprise/2.17/user/github/building-a-strong-community/adding-or-editing-wiki-pages": null, + "/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project": null, + "/enterprise/2.17/user/github/building-a-strong-community/changing-access-permissions-for-wikis": null, + "/enterprise/2.17/user/github/building-a-strong-community/collaborating-with-your-team": null, + "/enterprise/2.17/user/github/building-a-strong-community/configuring-issue-templates-for-your-repository": null, + "/enterprise/2.17/user/github/building-a-strong-community/creating-a-default-community-health-file": null, + "/enterprise/2.17/user/github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki": null, + "/enterprise/2.17/user/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository": null, + "/enterprise/2.17/user/github/building-a-strong-community/creating-a-team-discussion": null, + "/enterprise/2.17/user/github/building-a-strong-community/disabling-wikis": null, + "/enterprise/2.17/user/github/building-a-strong-community/documenting-your-project-with-wikis": null, + "/enterprise/2.17/user/github/building-a-strong-community/editing-or-deleting-a-team-discussion": null, + "/enterprise/2.17/user/github/building-a-strong-community/editing-wiki-content": null, + "/enterprise/2.17/user/github/building-a-strong-community": null, + "/enterprise/2.17/user/github/building-a-strong-community/locking-conversations": null, + "/enterprise/2.17/user/github/building-a-strong-community/managing-disruptive-comments": null, + "/enterprise/2.17/user/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository": null, + "/enterprise/2.17/user/github/building-a-strong-community/moderating-comments-and-conversations": null, + "/enterprise/2.17/user/github/building-a-strong-community/pinning-a-team-discussion": null, + "/enterprise/2.17/user/github/building-a-strong-community/setting-guidelines-for-repository-contributors": null, + "/enterprise/2.17/user/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions": null, + "/enterprise/2.17/user/github/building-a-strong-community/tracking-changes-in-a-comment": null, + "/enterprise/2.17/user/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/building-a-strong-community/viewing-a-wikis-history-of-changes": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-branches": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-forks": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-pull-requests": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/about-status-checks": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/github-flow": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/overview": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/syncing-a-fork": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-forks": null, + "/enterprise/2.17/user/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/changing-a-commit-message": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-branch-and-tag-labels": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/comparing-commits": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/creating-and-editing-commits": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/differences-between-commit-views": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/troubleshooting-commits": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/viewing-and-comparing-commits": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order": null, + "/enterprise/2.17/user/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-archiving-repositories": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-code-owners": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-readmes": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repositories": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-languages": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/about-repository-visibility": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/archiving-repositories": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/backing-up-a-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/cloning-a-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-new-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/duplicating-a-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/error-repository-not-found": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/https-cloning-errors": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/licensing-a-repository": null, + "/enterprise/2.17/user/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository": null, + "/enterprise/2.17/user/github/extending-github/about-webhooks": null, + "/enterprise/2.17/user/github/extending-github/getting-started-with-the-api": null, + "/enterprise/2.17/user/github/extending-github/git-automation-with-oauth-tokens": null, + "/enterprise/2.17/user/github/extending-github": null, + "/enterprise/2.17/user/github/getting-started-with-github/access-permissions-on-github": null, + "/enterprise/2.17/user/github/getting-started-with-github/be-social": null, + "/enterprise/2.17/user/github/getting-started-with-github/create-a-repo": null, + "/enterprise/2.17/user/github/getting-started-with-github/exploring-projects-on-github": null, + "/enterprise/2.17/user/github/getting-started-with-github/following-people": null, + "/enterprise/2.17/user/github/getting-started-with-github/fork-a-repo": null, + "/enterprise/2.17/user/github/getting-started-with-github/git-and-github-learning-resources": null, + "/enterprise/2.17/user/github/getting-started-with-github/git-cheatsheet": null, + "/enterprise/2.17/user/github/getting-started-with-github/github-desktop": null, + "/enterprise/2.17/user/github/getting-started-with-github/github-glossary": null, + "/enterprise/2.17/user/github/getting-started-with-github/githubs-products": null, + "/enterprise/2.17/user/github/getting-started-with-github": null, + "/enterprise/2.17/user/github/getting-started-with-github/keyboard-shortcuts": null, + "/enterprise/2.17/user/github/getting-started-with-github/learning-about-github": null, + "/enterprise/2.17/user/github/getting-started-with-github/quickstart": null, + "/enterprise/2.17/user/github/getting-started-with-github/saving-repositories-with-stars": null, + "/enterprise/2.17/user/github/getting-started-with-github/set-up-git": null, + "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud": null, + "/enterprise/2.17/user/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server": null, + "/enterprise/2.17/user/github/getting-started-with-github/signing-up-for-github": null, + "/enterprise/2.17/user/github/getting-started-with-github/supported-browsers": null, + "/enterprise/2.17/user/github/getting-started-with-github/types-of-github-accounts": null, + "/enterprise/2.17/user/github/getting-started-with-github/using-github": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/importing-source-code-to-github": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/source-code-migration-tools": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/subversion-properties-supported-by-github": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/support-for-subversion-clients": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git": null, + "/enterprise/2.17/user/github/importing-your-projects-to-github/working-with-subversion-on-github": null, + "/enterprise/2.17/user/github": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/3d-file-viewer": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/adding-a-file-to-a-repository": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/creating-new-files": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/deleting-files": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-another-users-repository": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/editing-files-in-your-repository": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/getting-permanent-links-to-files": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-on-github": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/managing-files-using-the-command-line": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/mapping-geojson-files-on-github": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/moving-a-file-to-a-new-location": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/renaming-a-file": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-and-diffing-images": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-csv-and-tsv-data": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-differences-in-prose-documents": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/rendering-pdf-documents": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/tracking-changes-in-a-file": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github": null, + "/enterprise/2.17/user/github/managing-files-in-a-repository/working-with-non-code-files": null, + "/enterprise/2.17/user/github/managing-large-files/about-git-large-file-storage": null, + "/enterprise/2.17/user/github/managing-large-files/collaboration-with-git-large-file-storage": null, + "/enterprise/2.17/user/github/managing-large-files/conditions-for-large-files": null, + "/enterprise/2.17/user/github/managing-large-files/configuring-git-large-file-storage": null, + "/enterprise/2.17/user/github/managing-large-files/distributing-large-binaries": null, + "/enterprise/2.17/user/github/managing-large-files": null, + "/enterprise/2.17/user/github/managing-large-files/installing-git-large-file-storage": null, + "/enterprise/2.17/user/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage": null, + "/enterprise/2.17/user/github/managing-large-files/removing-files-from-a-repositorys-history": null, + "/enterprise/2.17/user/github/managing-large-files/removing-files-from-git-large-file-storage": null, + "/enterprise/2.17/user/github/managing-large-files/resolving-git-large-file-storage-upload-failures": null, + "/enterprise/2.17/user/github/managing-large-files/versioning-large-files": null, + "/enterprise/2.17/user/github/managing-large-files/working-with-large-files": null, + "/enterprise/2.17/user/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies": null, + "/enterprise/2.17/user/github/managing-security-vulnerabilities": null, + "/enterprise/2.17/user/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-automation-for-project-boards": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-issues": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-labels": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-milestones": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-project-boards": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/about-task-lists": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/adding-notes-to-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/archiving-cards-on-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/changing-project-board-visibility": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/closing-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/configuring-automation-for-project-boards": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-label": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/creating-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/creating-an-issue": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-label": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/deleting-an-issue": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-issues": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-a-repository": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/disabling-project-boards-in-your-organization": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-label": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/editing-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-cards-on-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/filtering-pull-requests-by-review-status": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/finding-information-in-a-repository": null, + "/enterprise/2.17/user/github/managing-your-work-on-github": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/labeling-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/linking-a-repository-to-a-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/managing-project-boards": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/managing-your-work-with-issues": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-a-comment": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/opening-an-issue-from-code": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/pinning-an-issue-to-your-repository": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/reopening-a-closed-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/sharing-filters": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/sorting-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-progress-on-your-project-board": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/managing-your-work-on-github/viewing-your-milestones-progress": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-email-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/about-web-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/managing-your-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories": null, + "/enterprise/2.17/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/about-searching-on-github": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/finding-files-on-github": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/getting-started-with-searching-on-github": null, + "/enterprise/2.17/user/github/searching-for-information-on-github": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-code": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-commits": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-for-repositories": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-in-forks": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-issues-and-pull-requests": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-on-github": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-topics": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-users": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/searching-wikis": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/sorting-search-results": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/troubleshooting-search-queries": null, + "/enterprise/2.17/user/github/searching-for-information-on-github/understanding-the-search-syntax": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-organizations": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-teams": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/changing-team-visibility": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/creating-a-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-a-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-a-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account": null, + "/enterprise/2.17/user/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": null, + "/enterprise/2.17/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/about-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/customizing-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/personalizing-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-organization-membership": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/accessing-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-github-username": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-email-preferences": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address": null, + "/enterprise/2.17/user/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization": null, + "/enterprise/2.17/user/github/site-policy/github-insights-and-data-protection-for-your-organization": null, + "/enterprise/2.17/user/github/using-git/about-git-rebase": null, + "/enterprise/2.17/user/github/using-git/about-git-subtree-merges": null, + "/enterprise/2.17/user/github/using-git/about-remote-repositories": null, + "/enterprise/2.17/user/github/using-git/adding-a-remote": null, + "/enterprise/2.17/user/github/using-git/associating-text-editors-with-git": null, + "/enterprise/2.17/user/github/using-git/caching-your-github-password-in-git": null, + "/enterprise/2.17/user/github/using-git/changing-a-remotes-url": null, + "/enterprise/2.17/user/github/using-git/changing-author-info": null, + "/enterprise/2.17/user/github/using-git/configuring-git-to-handle-line-endings": null, + "/enterprise/2.17/user/github/using-git/dealing-with-non-fast-forward-errors": null, + "/enterprise/2.17/user/github/using-git/getting-changes-from-a-remote-repository": null, + "/enterprise/2.17/user/github/using-git/getting-started-with-git-and-github": null, + "/enterprise/2.17/user/github/using-git/git-workflows": null, + "/enterprise/2.17/user/github/using-git/ignoring-files": null, + "/enterprise/2.17/user/github/using-git": null, + "/enterprise/2.17/user/github/using-git/learning-about-git": null, + "/enterprise/2.17/user/github/using-git/managing-remote-repositories": null, + "/enterprise/2.17/user/github/using-git/pushing-commits-to-a-remote-repository": null, + "/enterprise/2.17/user/github/using-git/removing-a-remote": null, + "/enterprise/2.17/user/github/using-git/renaming-a-remote": null, + "/enterprise/2.17/user/github/using-git/resolving-merge-conflicts-after-a-git-rebase": null, + "/enterprise/2.17/user/github/using-git/setting-your-username-in-git": null, + "/enterprise/2.17/user/github/using-git/splitting-a-subfolder-out-into-a-new-repository": null, + "/enterprise/2.17/user/github/using-git/updating-credentials-from-the-osx-keychain": null, + "/enterprise/2.17/user/github/using-git/using-advanced-git-commands": null, + "/enterprise/2.17/user/github/using-git/using-common-git-commands": null, + "/enterprise/2.17/user/github/using-git/using-git-rebase-on-the-command-line": null, + "/enterprise/2.17/user/github/using-git/which-remote-url-should-i-use": null, + "/enterprise/2.17/user/github/using-git/why-is-git-always-asking-for-my-password": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/about-repository-graphs": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository": null, + "/enterprise/2.17/user/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository": null, + "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages-and-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/about-github-pages": null, + "/enterprise/2.17/user/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites": null, + "/enterprise/2.17/user/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site": null, + "/enterprise/2.17/user/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site": null, + "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/creating-a-github-pages-site": null, + "/enterprise/2.17/user/github/working-with-github-pages/getting-started-with-github-pages": null, + "/enterprise/2.17/user/github/working-with-github-pages": null, + "/enterprise/2.17/user/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll": null, + "/enterprise/2.17/user/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites": null, + "/enterprise/2.17/user/github/working-with-github-pages/unpublishing-a-github-pages-site": null, + "/enterprise/2.17/user/github/writing-on-github/about-saved-replies": null, + "/enterprise/2.17/user/github/writing-on-github/about-writing-and-formatting-on-github": null, + "/enterprise/2.17/user/github/writing-on-github/autolinked-references-and-urls": null, + "/enterprise/2.17/user/github/writing-on-github/basic-writing-and-formatting-syntax": null, + "/enterprise/2.17/user/github/writing-on-github/creating-a-saved-reply": null, + "/enterprise/2.17/user/github/writing-on-github/creating-and-highlighting-code-blocks": null, + "/enterprise/2.17/user/github/writing-on-github/creating-gists": null, + "/enterprise/2.17/user/github/writing-on-github/deleting-a-saved-reply": null, + "/enterprise/2.17/user/github/writing-on-github/editing-a-saved-reply": null, + "/enterprise/2.17/user/github/writing-on-github/editing-and-sharing-content-with-gists": null, + "/enterprise/2.17/user/github/writing-on-github/forking-and-cloning-gists": null, + "/enterprise/2.17/user/github/writing-on-github/getting-started-with-writing-and-formatting-on-github": null, + "/enterprise/2.17/user/github/writing-on-github": null, + "/enterprise/2.17/user/github/writing-on-github/organizing-information-with-tables": null, + "/enterprise/2.17/user/github/writing-on-github/using-saved-replies": null, + "/enterprise/2.17/user/github/writing-on-github/working-with-advanced-formatting": null, + "/enterprise/2.17/user/github/writing-on-github/working-with-saved-replies": null, + "/enterprise/2.17/user/graphql/guides/forming-calls-with-graphql": null, + "/enterprise/2.17/user/graphql/guides": null, + "/enterprise/2.17/user/graphql/guides/introduction-to-graphql": null, + "/enterprise/2.17/user/graphql/guides/migrating-from-rest-to-graphql": null, + "/enterprise/2.17/user/graphql/guides/using-global-node-ids": null, + "/enterprise/2.17/user/graphql/guides/using-the-explorer": null, + "/enterprise/2.17/user/graphql": null, + "/enterprise/2.17/user/graphql/overview/about-the-graphql-api": null, + "/enterprise/2.17/user/graphql/overview/breaking-changes": null, + "/enterprise/2.17/user/graphql/overview/changelog": null, + "/enterprise/2.17/user/graphql/overview/explorer": null, + "/enterprise/2.17/user/graphql/overview": null, + "/enterprise/2.17/user/graphql/overview/resource-limitations": null, + "/enterprise/2.17/user/graphql/overview/schema-previews": null, + "/enterprise/2.17/user/graphql/reference/enums": null, + "/enterprise/2.17/user/graphql/reference": null, + "/enterprise/2.17/user/graphql/reference/input-objects": null, + "/enterprise/2.17/user/graphql/reference/interfaces": null, + "/enterprise/2.17/user/graphql/reference/mutations": null, + "/enterprise/2.17/user/graphql/reference/objects": null, + "/enterprise/2.17/user/graphql/reference/queries": null, + "/enterprise/2.17/user/graphql/reference/scalars": null, + "/enterprise/2.17/user/graphql/reference/unions": null, + "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise": null, + "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights": null, + "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights": null, + "/enterprise/2.17/user/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports": null, + "/enterprise/2.17/user/insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-data-in-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/about-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/installing-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-contributors-and-teams": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-data-in-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-events": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-goals": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-organizations": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/managing-repositories": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/system-overview-for-github-insights": null, + "/enterprise/2.17/user/insights/installing-and-configuring-github-insights/updating-github-insights": null, + "/enterprise/2.17/user/rest": null, + "/enterprise/2.17/user/rest/reference/activity": null, + "/enterprise/2.17/user/rest/reference/apps": null, + "/enterprise/2.17/user/rest/reference/checks": null, + "/enterprise/2.17/user/rest/reference/codes-of-conduct": null, + "/enterprise/2.17/user/rest/reference/emojis": null, + "/enterprise/2.17/user/rest/reference/endpoints-available-for-github-apps": null, + "/enterprise/2.17/user/rest/reference/enterprise-admin": null, + "/enterprise/2.17/user/rest/reference/gists": null, + "/enterprise/2.17/user/rest/reference/git": null, + "/enterprise/2.17/user/rest/reference/gitignore": null, + "/enterprise/2.17/user/rest/reference": null, + "/enterprise/2.17/user/rest/reference/issues": null, + "/enterprise/2.17/user/rest/reference/licenses": null, + "/enterprise/2.17/user/rest/reference/markdown": null, + "/enterprise/2.17/user/rest/reference/meta": null, + "/enterprise/2.17/user/rest/reference/oauth-authorizations": null, + "/enterprise/2.17/user/rest/reference/orgs": null, + "/enterprise/2.17/user/rest/reference/projects": null, + "/enterprise/2.17/user/rest/reference/pulls": null, + "/enterprise/2.17/user/rest/reference/rate-limit": null, + "/enterprise/2.17/user/rest/reference/reactions": null, + "/enterprise/2.17/user/rest/reference/repos": null, + "/enterprise/2.17/user/rest/reference/search": null, + "/enterprise/2.17/user/rest/reference/teams": null, + "/enterprise/2.17/user/rest/reference/users": null } \ No newline at end of file diff --git a/lib/redirects/static/developer.json b/lib/redirects/static/developer.json index 01d858d77f..7644cec727 100644 --- a/lib/redirects/static/developer.json +++ b/lib/redirects/static/developer.json @@ -1,13975 +1,4609 @@ { - "/en/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/3.0/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/3.0/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/admin/articles/restoring-github-enterprise": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/3.0/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/3.0/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/admin/articles/restoring-enterprise-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise-server@3.0/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/3.0/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/3.0/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise-server@3.0/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/admin/articles/restoring-repository-data": "/en/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/2.20/admin/articles/restoring-github-enterprise": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/2.20/admin/articles/restoring-github-enterprise": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/2.20/admin/articles/restoring-enterprise-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/2.20/admin/articles/restoring-enterprise-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise-server@2.20/admin/articles/restoring-repository-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise/2.20/admin/articles/restoring-repository-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise/2.20/admin/articles/restoring-repository-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/enterprise-server@2.20/admin/articles/restoring-repository-data": "/en/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/en/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/en/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/en/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/en/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/en/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/en/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/en/github-ae@latest/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/github-ae@latest/admin/configuration/configuring-your-enterprise", - "/github-ae@latest/admin/articles/restricting-ssh-access-to-specific-hosts": "/en/github-ae@latest/admin/configuration/configuring-your-enterprise", - "/github-ae@latest/admin/configuration/restricting-network-traffic-to-your-enterprise": "/en/github-ae@latest/admin/configuration/restricting-network-traffic-to-your-enterprise", - "/en/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/en/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/github-ae@latest/admin/user-management/restricting-repository-creation-in-your-instance": "/en/github-ae@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/github-ae@latest/admin/user-management/restricting-repository-creation-in-your-instance": "/en/github-ae@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/en/v3/oauth": "/en/developers/apps/authorizing-oauth-apps", - "/en/free-pro-team@latest/v3/oauth": "/en/developers/apps/authorizing-oauth-apps", - "/free-pro-team@latest/v3/oauth": "/en/developers/apps/authorizing-oauth-apps", - "/v3/oauth": "/en/developers/apps/authorizing-oauth-apps", - "/en/enterprise-server@3.0/v3/oauth": "/en/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/en/enterprise/3.0/v3/oauth": "/en/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/en/enterprise/v3/oauth": "/en/enterprise-server@latest/developers/apps/authorizing-oauth-apps", - "/enterprise/3.0/v3/oauth": "/en/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/enterprise-server@3.0/v3/oauth": "/en/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/enterprise/v3/oauth": "/en/enterprise-server@latest/developers/apps/authorizing-oauth-apps", - "/en/enterprise-server@2.20/v3/oauth": "/en/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/en/enterprise/2.20/v3/oauth": "/en/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/enterprise/2.20/v3/oauth": "/en/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/enterprise-server@2.20/v3/oauth": "/en/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/en/github-ae@latest/v3/oauth": "/en/github-ae@latest/developers/apps/authorizing-oauth-apps", - "/github-ae@latest/v3/oauth": "/en/github-ae@latest/developers/apps/authorizing-oauth-apps", - "/en/v3/integrations": "/en/developers/apps", - "/en/free-pro-team@latest/v3/integrations": "/en/developers/apps", - "/free-pro-team@latest/v3/integrations": "/en/developers/apps", - "/v3/integrations": "/en/developers/apps", - "/en/enterprise-server@3.0/v3/integrations": "/en/enterprise-server@3.0/developers/apps", - "/en/enterprise/3.0/v3/integrations": "/en/enterprise-server@3.0/developers/apps", - "/en/enterprise/v3/integrations": "/en/enterprise-server@latest/developers/apps", - "/enterprise/3.0/v3/integrations": "/en/enterprise-server@3.0/developers/apps", - "/enterprise-server@3.0/v3/integrations": "/en/enterprise-server@3.0/developers/apps", - "/enterprise/v3/integrations": "/en/enterprise-server@latest/developers/apps", - "/en/enterprise-server@2.20/v3/integrations": "/en/enterprise-server@2.20/developers/apps", - "/en/enterprise/2.20/v3/integrations": "/en/enterprise-server@2.20/developers/apps", - "/enterprise/2.20/v3/integrations": "/en/enterprise-server@2.20/developers/apps", - "/enterprise-server@2.20/v3/integrations": "/en/enterprise-server@2.20/developers/apps", - "/en/github-ae@latest/v3/integrations": "/en/github-ae@latest/developers/apps", - "/github-ae@latest/v3/integrations": "/en/github-ae@latest/developers/apps", - "/en/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/en/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/en/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/en/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/en/v3/versions": "/en/developers/overview/about-githubs-apis", - "/en/free-pro-team@latest/v3/versions": "/en/developers/overview/about-githubs-apis", - "/free-pro-team@latest/v3/versions": "/en/developers/overview/about-githubs-apis", - "/v3/versions": "/en/developers/overview/about-githubs-apis", - "/en/enterprise-server@3.0/v3/versions": "/en/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/en/enterprise/3.0/v3/versions": "/en/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/en/enterprise/v3/versions": "/en/enterprise-server@latest/developers/overview/about-githubs-apis", - "/enterprise/3.0/v3/versions": "/en/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/enterprise-server@3.0/v3/versions": "/en/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/enterprise/v3/versions": "/en/enterprise-server@latest/developers/overview/about-githubs-apis", - "/en/enterprise-server@2.20/v3/versions": "/en/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/en/enterprise/2.20/v3/versions": "/en/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/enterprise/2.20/v3/versions": "/en/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/enterprise-server@2.20/v3/versions": "/en/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/en/github-ae@latest/v3/versions": "/en/github-ae@latest/developers/overview/about-githubs-apis", - "/github-ae@latest/v3/versions": "/en/github-ae@latest/developers/overview/about-githubs-apis", - "/en/v3/guides/managing-deploy-keys": "/en/developers/overview/managing-deploy-keys", - "/en/free-pro-team@latest/v3/guides/managing-deploy-keys": "/en/developers/overview/managing-deploy-keys", - "/free-pro-team@latest/v3/guides/managing-deploy-keys": "/en/developers/overview/managing-deploy-keys", - "/v3/guides/managing-deploy-keys": "/en/developers/overview/managing-deploy-keys", - "/en/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/en/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/en/enterprise/3.0/v3/guides/managing-deploy-keys": "/en/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/en/enterprise/v3/guides/managing-deploy-keys": "/en/enterprise-server@latest/developers/overview/managing-deploy-keys", - "/enterprise/3.0/v3/guides/managing-deploy-keys": "/en/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/en/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/enterprise/v3/guides/managing-deploy-keys": "/en/enterprise-server@latest/developers/overview/managing-deploy-keys", - "/en/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/en/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/en/enterprise/2.20/v3/guides/managing-deploy-keys": "/en/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/enterprise/2.20/v3/guides/managing-deploy-keys": "/en/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/en/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/en/github-ae@latest/v3/guides/managing-deploy-keys": "/en/github-ae@latest/developers/overview/managing-deploy-keys", - "/github-ae@latest/v3/guides/managing-deploy-keys": "/en/github-ae@latest/developers/overview/managing-deploy-keys", - "/en/v3/guides/automating-deployments-to-integrators": "/en/developers/overview/replacing-github-services", - "/en/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/en/developers/overview/replacing-github-services", - "/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/en/developers/overview/replacing-github-services", - "/v3/guides/automating-deployments-to-integrators": "/en/developers/overview/replacing-github-services", - "/en/v3/guides/replacing-github-services": "/en/developers/overview/replacing-github-services", - "/en/free-pro-team@latest/v3/guides/replacing-github-services": "/en/developers/overview/replacing-github-services", - "/free-pro-team@latest/v3/guides/replacing-github-services": "/en/developers/overview/replacing-github-services", - "/v3/guides/replacing-github-services": "/en/developers/overview/replacing-github-services", - "/en/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/en/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/en/enterprise/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@latest/developers/overview/replacing-github-services", - "/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/enterprise/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@latest/developers/overview/replacing-github-services", - "/en/enterprise-server@3.0/v3/guides/replacing-github-services": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/en/enterprise/3.0/v3/guides/replacing-github-services": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/en/enterprise/v3/guides/replacing-github-services": "/en/enterprise-server@latest/developers/overview/replacing-github-services", - "/enterprise/3.0/v3/guides/replacing-github-services": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/enterprise-server@3.0/v3/guides/replacing-github-services": "/en/enterprise-server@3.0/developers/overview/replacing-github-services", - "/enterprise/v3/guides/replacing-github-services": "/en/enterprise-server@latest/developers/overview/replacing-github-services", - "/en/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/en/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/en/enterprise-server@2.20/v3/guides/replacing-github-services": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/en/enterprise/2.20/v3/guides/replacing-github-services": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/enterprise/2.20/v3/guides/replacing-github-services": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/enterprise-server@2.20/v3/guides/replacing-github-services": "/en/enterprise-server@2.20/developers/overview/replacing-github-services", - "/en/v3/guides/using-ssh-agent-forwarding": "/en/developers/overview/using-ssh-agent-forwarding", - "/en/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/en/developers/overview/using-ssh-agent-forwarding", - "/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/en/developers/overview/using-ssh-agent-forwarding", - "/v3/guides/using-ssh-agent-forwarding": "/en/developers/overview/using-ssh-agent-forwarding", - "/en/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/en/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/en/enterprise/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", - "/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/enterprise/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", - "/en/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/en/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/en/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/en/github-ae@latest/v3/guides/using-ssh-agent-forwarding": "/en/github-ae@latest/developers/overview/using-ssh-agent-forwarding", - "/github-ae@latest/v3/guides/using-ssh-agent-forwarding": "/en/github-ae@latest/developers/overview/using-ssh-agent-forwarding", - "/en/v3/activity/event_types": "/en/developers/webhooks-and-events/github-event-types", - "/en/free-pro-team@latest/v3/activity/event_types": "/en/developers/webhooks-and-events/github-event-types", - "/free-pro-team@latest/v3/activity/event_types": "/en/developers/webhooks-and-events/github-event-types", - "/v3/activity/event_types": "/en/developers/webhooks-and-events/github-event-types", - "/en/enterprise-server@3.0/v3/activity/event_types": "/en/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/en/enterprise/3.0/v3/activity/event_types": "/en/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/en/enterprise/v3/activity/event_types": "/en/enterprise-server@latest/developers/webhooks-and-events/github-event-types", - "/enterprise/3.0/v3/activity/event_types": "/en/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/enterprise-server@3.0/v3/activity/event_types": "/en/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/enterprise/v3/activity/event_types": "/en/enterprise-server@latest/developers/webhooks-and-events/github-event-types", - "/en/enterprise-server@2.20/v3/activity/event_types": "/en/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/en/enterprise/2.20/v3/activity/event_types": "/en/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/enterprise/2.20/v3/activity/event_types": "/en/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/enterprise-server@2.20/v3/activity/event_types": "/en/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/en/github-ae@latest/v3/activity/event_types": "/en/github-ae@latest/developers/webhooks-and-events/github-event-types", - "/github-ae@latest/v3/activity/event_types": "/en/github-ae@latest/developers/webhooks-and-events/github-event-types", - "/en/v3/issues/issue-event-types": "/en/developers/webhooks-and-events/issue-event-types", - "/en/free-pro-team@latest/v3/issues/issue-event-types": "/en/developers/webhooks-and-events/issue-event-types", - "/free-pro-team@latest/v3/issues/issue-event-types": "/en/developers/webhooks-and-events/issue-event-types", - "/v3/issues/issue-event-types": "/en/developers/webhooks-and-events/issue-event-types", - "/en/enterprise-server@3.0/v3/issues/issue-event-types": "/en/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/en/enterprise/3.0/v3/issues/issue-event-types": "/en/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/en/enterprise/v3/issues/issue-event-types": "/en/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", - "/enterprise/3.0/v3/issues/issue-event-types": "/en/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/enterprise-server@3.0/v3/issues/issue-event-types": "/en/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/enterprise/v3/issues/issue-event-types": "/en/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", - "/en/enterprise-server@2.20/v3/issues/issue-event-types": "/en/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/en/enterprise/2.20/v3/issues/issue-event-types": "/en/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/enterprise/2.20/v3/issues/issue-event-types": "/en/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/enterprise-server@2.20/v3/issues/issue-event-types": "/en/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/en/github-ae@latest/v3/issues/issue-event-types": "/en/github-ae@latest/developers/webhooks-and-events/issue-event-types", - "/github-ae@latest/v3/issues/issue-event-types": "/en/github-ae@latest/developers/webhooks-and-events/issue-event-types", - "/en/v3/activity/events/types": "/en/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/free-pro-team@latest/v3/activity/events/types": "/en/developers/webhooks-and-events/webhook-events-and-payloads", - "/free-pro-team@latest/v3/activity/events/types": "/en/developers/webhooks-and-events/webhook-events-and-payloads", - "/v3/activity/events/types": "/en/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/enterprise-server@3.0/v3/activity/events/types": "/en/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/enterprise/3.0/v3/activity/events/types": "/en/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/enterprise/v3/activity/events/types": "/en/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/enterprise/3.0/v3/activity/events/types": "/en/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/enterprise-server@3.0/v3/activity/events/types": "/en/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/enterprise/v3/activity/events/types": "/en/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/enterprise-server@2.20/v3/activity/events/types": "/en/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/enterprise/2.20/v3/activity/events/types": "/en/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/enterprise/2.20/v3/activity/events/types": "/en/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/enterprise-server@2.20/v3/activity/events/types": "/en/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/github-ae@latest/v3/activity/events/types": "/en/github-ae@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/github-ae@latest/v3/activity/events/types": "/en/github-ae@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/en/articles/restoring-branches-in-a-pull-request": "/en/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/en/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/en/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/articles/restoring-branches-in-a-pull-request": "/en/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/en/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/github-ae@latest/articles/restoring-branches-in-a-pull-request": "/en/github-ae@latest/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/github-ae@latest/articles/restoring-branches-in-a-pull-request": "/en/github-ae@latest/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/en/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/github/administering-a-repository/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/en/articles/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/en/free-pro-team@latest/articles/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/free-pro-team@latest/articles/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/articles/restoring-a-deleted-repository": "/en/github/administering-a-repository/restoring-a-deleted-repository", - "/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/en/articles/restricting-access-to-your-organization-s-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/en/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/articles/restricting-access-to-your-organization-s-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/en/articles/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/en/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/articles/restricting-access-to-your-organizations-data": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/en/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/en/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/en/articles/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/en/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/articles/restricting-email-notifications-to-an-approved-domain": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/articles/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/articles/restricting-repository-creation-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/github-ae@latest/articles/restricting-repository-creation-in-your-organization": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/github-ae@latest/articles/restricting-repository-creation-in-your-organization": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/articles/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/articles/restricting-repository-visibility-changes-in-your-organization": "/en/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/github-ae@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/github-ae@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/en/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/github-ae@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/github-ae@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/en/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/en/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/en/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", - "/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/en/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", - "/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/en/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", - "/en/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/en/graphql/guides/forming-calls-with-graphql", - "/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/en/graphql/guides/forming-calls-with-graphql", - "/graphql/guides/forming-calls-with-graphql": "/en/graphql/guides/forming-calls-with-graphql", - "/en/v4/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/en/free-pro-team@latest/v4/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/free-pro-team@latest/v4/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/v4/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/en/graphql/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/en/free-pro-team@latest/graphql/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/free-pro-team@latest/graphql/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/graphql/guides/forming-calls": "/en/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/enterprise/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/en/enterprise-server@3.0/v4/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/3.0/v4/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/v4/guides/forming-calls": "/en/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/enterprise/3.0/v4/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/enterprise-server@3.0/v4/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/enterprise/v4/guides/forming-calls": "/en/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/en/enterprise-server@3.0/graphql/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/3.0/graphql/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/graphql/guides/forming-calls": "/en/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/enterprise/3.0/graphql/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/enterprise-server@3.0/graphql/guides/forming-calls": "/en/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/enterprise/graphql/guides/forming-calls": "/en/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/en/enterprise-server@2.20/v4/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/2.20/v4/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/enterprise/2.20/v4/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/enterprise-server@2.20/v4/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/en/enterprise-server@2.20/graphql/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/en/enterprise/2.20/graphql/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/enterprise/2.20/graphql/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/enterprise-server@2.20/graphql/guides/forming-calls": "/en/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/github-ae@latest/graphql/guides/forming-calls-with-graphql": "/en/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/en/github-ae@latest/v4/guides/forming-calls": "/en/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/github-ae@latest/v4/guides/forming-calls": "/en/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/en/github-ae@latest/graphql/guides/forming-calls": "/en/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/github-ae@latest/graphql/guides/forming-calls": "/en/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/en/free-pro-team@latest/graphql/guides": "/en/graphql/guides", - "/free-pro-team@latest/graphql/guides": "/en/graphql/guides", - "/graphql/guides": "/en/graphql/guides", - "/en/v4/guides": "/en/graphql/guides", - "/en/free-pro-team@latest/v4/guides": "/en/graphql/guides", - "/free-pro-team@latest/v4/guides": "/en/graphql/guides", - "/v4/guides": "/en/graphql/guides", - "/en/enterprise/3.0/graphql/guides": "/en/enterprise-server@3.0/graphql/guides", - "/en/enterprise/graphql/guides": "/en/enterprise-server@latest/graphql/guides", - "/enterprise/3.0/graphql/guides": "/en/enterprise-server@3.0/graphql/guides", - "/enterprise-server@3.0/graphql/guides": "/en/enterprise-server@3.0/graphql/guides", - "/enterprise/graphql/guides": "/en/enterprise-server@latest/graphql/guides", - "/en/enterprise-server@3.0/v4/guides": "/en/enterprise-server@3.0/graphql/guides", - "/en/enterprise/3.0/v4/guides": "/en/enterprise-server@3.0/graphql/guides", - "/en/enterprise/v4/guides": "/en/enterprise-server@latest/graphql/guides", - "/enterprise/3.0/v4/guides": "/en/enterprise-server@3.0/graphql/guides", - "/enterprise-server@3.0/v4/guides": "/en/enterprise-server@3.0/graphql/guides", - "/enterprise/v4/guides": "/en/enterprise-server@latest/graphql/guides", - "/en/enterprise/2.20/graphql/guides": "/en/enterprise-server@2.20/graphql/guides", - "/enterprise/2.20/graphql/guides": "/en/enterprise-server@2.20/graphql/guides", - "/enterprise-server@2.20/graphql/guides": "/en/enterprise-server@2.20/graphql/guides", - "/en/enterprise-server@2.20/v4/guides": "/en/enterprise-server@2.20/graphql/guides", - "/en/enterprise/2.20/v4/guides": "/en/enterprise-server@2.20/graphql/guides", - "/enterprise/2.20/v4/guides": "/en/enterprise-server@2.20/graphql/guides", - "/enterprise-server@2.20/v4/guides": "/en/enterprise-server@2.20/graphql/guides", - "/github-ae@latest/graphql/guides": "/en/github-ae@latest/graphql/guides", - "/en/github-ae@latest/v4/guides": "/en/github-ae@latest/graphql/guides", - "/github-ae@latest/v4/guides": "/en/github-ae@latest/graphql/guides", - "/en/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/graphql/guides/introduction-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/en/v4/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/en/free-pro-team@latest/v4/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/free-pro-team@latest/v4/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/v4/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/en/graphql/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/en/free-pro-team@latest/graphql/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/free-pro-team@latest/graphql/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/graphql/guides/intro-to-graphql": "/en/graphql/guides/introduction-to-graphql", - "/en/enterprise/3.0/graphql/guides/introduction-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/en/enterprise/graphql/guides/introduction-to-graphql": "/en/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/enterprise/3.0/graphql/guides/introduction-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/enterprise-server@3.0/graphql/guides/introduction-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/enterprise/graphql/guides/introduction-to-graphql": "/en/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/en/enterprise-server@3.0/v4/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/en/enterprise/3.0/v4/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/en/enterprise/v4/guides/intro-to-graphql": "/en/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/enterprise/3.0/v4/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/enterprise-server@3.0/v4/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/enterprise/v4/guides/intro-to-graphql": "/en/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/en/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/en/enterprise/3.0/graphql/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/en/enterprise/graphql/guides/intro-to-graphql": "/en/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/enterprise/3.0/graphql/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/en/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/enterprise/graphql/guides/intro-to-graphql": "/en/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/en/enterprise/2.20/graphql/guides/introduction-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/enterprise/2.20/graphql/guides/introduction-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/enterprise-server@2.20/graphql/guides/introduction-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/en/enterprise-server@2.20/v4/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/en/enterprise/2.20/v4/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/enterprise/2.20/v4/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/enterprise-server@2.20/v4/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/en/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/en/enterprise/2.20/graphql/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/enterprise/2.20/graphql/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/en/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/github-ae@latest/graphql/guides/introduction-to-graphql": "/en/github-ae@latest/graphql/guides/introduction-to-graphql", - "/en/github-ae@latest/v4/guides/intro-to-graphql": "/en/github-ae@latest/graphql/guides/introduction-to-graphql", - "/github-ae@latest/v4/guides/intro-to-graphql": "/en/github-ae@latest/graphql/guides/introduction-to-graphql", - "/en/github-ae@latest/graphql/guides/intro-to-graphql": "/en/github-ae@latest/graphql/guides/introduction-to-graphql", - "/github-ae@latest/graphql/guides/intro-to-graphql": "/en/github-ae@latest/graphql/guides/introduction-to-graphql", - "/en/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/graphql/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/en/v4/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/en/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/v4/guides/managing-enterprise-accounts": "/en/graphql/guides/managing-enterprise-accounts", - "/en/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/en/enterprise/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/enterprise/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/en/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/en/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/en/enterprise/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/enterprise/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/en/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/en/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/en/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/en/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/github-ae@latest/graphql/guides/managing-enterprise-accounts": "/en/github-ae@latest/graphql/guides/managing-enterprise-accounts", - "/en/github-ae@latest/v4/guides/managing-enterprise-accounts": "/en/github-ae@latest/graphql/guides/managing-enterprise-accounts", - "/github-ae@latest/v4/guides/managing-enterprise-accounts": "/en/github-ae@latest/graphql/guides/managing-enterprise-accounts", - "/en/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/graphql/guides/migrating-from-rest-to-graphql": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/en/v4/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/en/free-pro-team@latest/v4/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/free-pro-team@latest/v4/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/v4/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/en/graphql/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/en/free-pro-team@latest/graphql/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/free-pro-team@latest/graphql/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/graphql/guides/migrating-from-rest": "/en/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise-server@3.0/v4/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/3.0/v4/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/v4/guides/migrating-from-rest": "/en/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/3.0/v4/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise-server@3.0/v4/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/v4/guides/migrating-from-rest": "/en/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/3.0/graphql/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/graphql/guides/migrating-from-rest": "/en/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/3.0/graphql/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/en/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/graphql/guides/migrating-from-rest": "/en/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise-server@2.20/v4/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/2.20/v4/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/2.20/v4/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise-server@2.20/v4/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/en/enterprise/2.20/graphql/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise/2.20/graphql/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/en/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql": "/en/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/en/github-ae@latest/v4/guides/migrating-from-rest": "/en/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/github-ae@latest/v4/guides/migrating-from-rest": "/en/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/en/github-ae@latest/graphql/guides/migrating-from-rest": "/en/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/github-ae@latest/graphql/guides/migrating-from-rest": "/en/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/en/free-pro-team@latest/graphql/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/free-pro-team@latest/graphql/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/graphql/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/en/v4/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/en/free-pro-team@latest/v4/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/free-pro-team@latest/v4/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/v4/guides/using-global-node-ids": "/en/graphql/guides/using-global-node-ids", - "/en/enterprise/3.0/graphql/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/en/enterprise/graphql/guides/using-global-node-ids": "/en/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/enterprise/3.0/graphql/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/enterprise-server@3.0/graphql/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/enterprise/graphql/guides/using-global-node-ids": "/en/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/en/enterprise-server@3.0/v4/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/en/enterprise/3.0/v4/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/en/enterprise/v4/guides/using-global-node-ids": "/en/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/enterprise/3.0/v4/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/enterprise-server@3.0/v4/guides/using-global-node-ids": "/en/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/enterprise/v4/guides/using-global-node-ids": "/en/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/en/enterprise/2.20/graphql/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/enterprise/2.20/graphql/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/enterprise-server@2.20/graphql/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/en/enterprise-server@2.20/v4/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/en/enterprise/2.20/v4/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/enterprise/2.20/v4/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/enterprise-server@2.20/v4/guides/using-global-node-ids": "/en/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/github-ae@latest/graphql/guides/using-global-node-ids": "/en/github-ae@latest/graphql/guides/using-global-node-ids", - "/en/github-ae@latest/v4/guides/using-global-node-ids": "/en/github-ae@latest/graphql/guides/using-global-node-ids", - "/github-ae@latest/v4/guides/using-global-node-ids": "/en/github-ae@latest/graphql/guides/using-global-node-ids", - "/en/free-pro-team@latest/graphql/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/free-pro-team@latest/graphql/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/graphql/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/en/v4/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/en/free-pro-team@latest/v4/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/free-pro-team@latest/v4/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/v4/guides/using-the-explorer": "/en/graphql/guides/using-the-explorer", - "/en/enterprise/3.0/graphql/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/en/enterprise/graphql/guides/using-the-explorer": "/en/enterprise-server@latest/graphql/guides/using-the-explorer", - "/enterprise/3.0/graphql/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/enterprise-server@3.0/graphql/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/enterprise/graphql/guides/using-the-explorer": "/en/enterprise-server@latest/graphql/guides/using-the-explorer", - "/en/enterprise-server@3.0/v4/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/en/enterprise/3.0/v4/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/en/enterprise/v4/guides/using-the-explorer": "/en/enterprise-server@latest/graphql/guides/using-the-explorer", - "/enterprise/3.0/v4/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/enterprise-server@3.0/v4/guides/using-the-explorer": "/en/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/enterprise/v4/guides/using-the-explorer": "/en/enterprise-server@latest/graphql/guides/using-the-explorer", - "/en/enterprise/2.20/graphql/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/enterprise/2.20/graphql/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/enterprise-server@2.20/graphql/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/en/enterprise-server@2.20/v4/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/en/enterprise/2.20/v4/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/enterprise/2.20/v4/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/enterprise-server@2.20/v4/guides/using-the-explorer": "/en/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/github-ae@latest/graphql/guides/using-the-explorer": "/en/github-ae@latest/graphql/guides/using-the-explorer", - "/en/github-ae@latest/v4/guides/using-the-explorer": "/en/github-ae@latest/graphql/guides/using-the-explorer", - "/github-ae@latest/v4/guides/using-the-explorer": "/en/github-ae@latest/graphql/guides/using-the-explorer", - "/en/free-pro-team@latest/graphql": "/en/graphql", - "/free-pro-team@latest/graphql": "/en/graphql", - "/graphql": "/en/graphql", - "/en/v4": "/en/graphql", - "/en/free-pro-team@latest/v4": "/en/graphql", - "/free-pro-team@latest/v4": "/en/graphql", - "/v4": "/en/graphql", - "/en/enterprise/3.0/graphql": "/en/enterprise-server@3.0/graphql", - "/en/enterprise/graphql": "/en/enterprise-server@latest/graphql", - "/enterprise/3.0/graphql": "/en/enterprise-server@3.0/graphql", - "/enterprise-server@3.0/graphql": "/en/enterprise-server@3.0/graphql", - "/enterprise/graphql": "/en/enterprise-server@latest/graphql", - "/en/enterprise-server@3.0/v4": "/en/enterprise-server@3.0/graphql", - "/en/enterprise/3.0/v4": "/en/enterprise-server@3.0/graphql", - "/en/enterprise/v4": "/en/enterprise-server@latest/graphql", - "/enterprise/3.0/v4": "/en/enterprise-server@3.0/graphql", - "/enterprise-server@3.0/v4": "/en/enterprise-server@3.0/graphql", - "/enterprise/v4": "/en/enterprise-server@latest/graphql", - "/en/enterprise/2.20/graphql": "/en/enterprise-server@2.20/graphql", - "/enterprise/2.20/graphql": "/en/enterprise-server@2.20/graphql", - "/enterprise-server@2.20/graphql": "/en/enterprise-server@2.20/graphql", - "/en/enterprise-server@2.20/v4": "/en/enterprise-server@2.20/graphql", - "/en/enterprise/2.20/v4": "/en/enterprise-server@2.20/graphql", - "/enterprise/2.20/v4": "/en/enterprise-server@2.20/graphql", - "/enterprise-server@2.20/v4": "/en/enterprise-server@2.20/graphql", - "/github-ae@latest/graphql": "/en/github-ae@latest/graphql", - "/en/github-ae@latest/v4": "/en/github-ae@latest/graphql", - "/github-ae@latest/v4": "/en/github-ae@latest/graphql", - "/en/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/en/graphql/overview/about-the-graphql-api", - "/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/en/graphql/overview/about-the-graphql-api", - "/graphql/overview/about-the-graphql-api": "/en/graphql/overview/about-the-graphql-api", - "/en/enterprise/3.0/graphql/overview/about-the-graphql-api": "/en/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/en/enterprise/graphql/overview/about-the-graphql-api": "/en/enterprise-server@latest/graphql/overview/about-the-graphql-api", - "/enterprise/3.0/graphql/overview/about-the-graphql-api": "/en/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/enterprise-server@3.0/graphql/overview/about-the-graphql-api": "/en/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/enterprise/graphql/overview/about-the-graphql-api": "/en/enterprise-server@latest/graphql/overview/about-the-graphql-api", - "/en/enterprise/2.20/graphql/overview/about-the-graphql-api": "/en/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/enterprise/2.20/graphql/overview/about-the-graphql-api": "/en/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/enterprise-server@2.20/graphql/overview/about-the-graphql-api": "/en/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/github-ae@latest/graphql/overview/about-the-graphql-api": "/en/github-ae@latest/graphql/overview/about-the-graphql-api", - "/en/free-pro-team@latest/graphql/overview/breaking-changes": "/en/graphql/overview/breaking-changes", - "/free-pro-team@latest/graphql/overview/breaking-changes": "/en/graphql/overview/breaking-changes", - "/graphql/overview/breaking-changes": "/en/graphql/overview/breaking-changes", - "/en/v4/breaking_changes": "/en/graphql/overview/breaking-changes", - "/en/free-pro-team@latest/v4/breaking_changes": "/en/graphql/overview/breaking-changes", - "/free-pro-team@latest/v4/breaking_changes": "/en/graphql/overview/breaking-changes", - "/v4/breaking_changes": "/en/graphql/overview/breaking-changes", - "/en/enterprise/3.0/graphql/overview/breaking-changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/en/enterprise/graphql/overview/breaking-changes": "/en/enterprise-server@latest/graphql/overview/breaking-changes", - "/enterprise/3.0/graphql/overview/breaking-changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/enterprise-server@3.0/graphql/overview/breaking-changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/enterprise/graphql/overview/breaking-changes": "/en/enterprise-server@latest/graphql/overview/breaking-changes", - "/en/enterprise-server@3.0/v4/breaking_changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/en/enterprise/3.0/v4/breaking_changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/en/enterprise/v4/breaking_changes": "/en/enterprise-server@latest/graphql/overview/breaking-changes", - "/enterprise/3.0/v4/breaking_changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/enterprise-server@3.0/v4/breaking_changes": "/en/enterprise-server@3.0/graphql/overview/breaking-changes", - "/enterprise/v4/breaking_changes": "/en/enterprise-server@latest/graphql/overview/breaking-changes", - "/en/enterprise/2.20/graphql/overview/breaking-changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/enterprise/2.20/graphql/overview/breaking-changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/enterprise-server@2.20/graphql/overview/breaking-changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/en/enterprise-server@2.20/v4/breaking_changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/en/enterprise/2.20/v4/breaking_changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/enterprise/2.20/v4/breaking_changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/enterprise-server@2.20/v4/breaking_changes": "/en/enterprise-server@2.20/graphql/overview/breaking-changes", - "/github-ae@latest/graphql/overview/breaking-changes": "/en/github-ae@latest/graphql/overview/breaking-changes", - "/en/github-ae@latest/v4/breaking_changes": "/en/github-ae@latest/graphql/overview/breaking-changes", - "/github-ae@latest/v4/breaking_changes": "/en/github-ae@latest/graphql/overview/breaking-changes", - "/en/free-pro-team@latest/graphql/overview/changelog": "/en/graphql/overview/changelog", - "/free-pro-team@latest/graphql/overview/changelog": "/en/graphql/overview/changelog", - "/graphql/overview/changelog": "/en/graphql/overview/changelog", - "/en/v4/changelog": "/en/graphql/overview/changelog", - "/en/free-pro-team@latest/v4/changelog": "/en/graphql/overview/changelog", - "/free-pro-team@latest/v4/changelog": "/en/graphql/overview/changelog", - "/v4/changelog": "/en/graphql/overview/changelog", - "/en/enterprise/3.0/graphql/overview/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/en/enterprise/graphql/overview/changelog": "/en/enterprise-server@latest/graphql/overview/changelog", - "/enterprise/3.0/graphql/overview/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/enterprise-server@3.0/graphql/overview/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/enterprise/graphql/overview/changelog": "/en/enterprise-server@latest/graphql/overview/changelog", - "/en/enterprise-server@3.0/v4/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/en/enterprise/3.0/v4/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/en/enterprise/v4/changelog": "/en/enterprise-server@latest/graphql/overview/changelog", - "/enterprise/3.0/v4/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/enterprise-server@3.0/v4/changelog": "/en/enterprise-server@3.0/graphql/overview/changelog", - "/enterprise/v4/changelog": "/en/enterprise-server@latest/graphql/overview/changelog", - "/en/enterprise/2.20/graphql/overview/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/enterprise/2.20/graphql/overview/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/enterprise-server@2.20/graphql/overview/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/en/enterprise-server@2.20/v4/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/en/enterprise/2.20/v4/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/enterprise/2.20/v4/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/enterprise-server@2.20/v4/changelog": "/en/enterprise-server@2.20/graphql/overview/changelog", - "/github-ae@latest/graphql/overview/changelog": "/en/github-ae@latest/graphql/overview/changelog", - "/en/github-ae@latest/v4/changelog": "/en/github-ae@latest/graphql/overview/changelog", - "/github-ae@latest/v4/changelog": "/en/github-ae@latest/graphql/overview/changelog", - "/en/free-pro-team@latest/graphql/overview/explorer": "/en/graphql/overview/explorer", - "/free-pro-team@latest/graphql/overview/explorer": "/en/graphql/overview/explorer", - "/graphql/overview/explorer": "/en/graphql/overview/explorer", - "/en/v4/explorer": "/en/graphql/overview/explorer", - "/en/free-pro-team@latest/v4/explorer": "/en/graphql/overview/explorer", - "/free-pro-team@latest/v4/explorer": "/en/graphql/overview/explorer", - "/v4/explorer": "/en/graphql/overview/explorer", - "/en/v4/explorer-new": "/en/graphql/overview/explorer", - "/en/free-pro-team@latest/v4/explorer-new": "/en/graphql/overview/explorer", - "/free-pro-team@latest/v4/explorer-new": "/en/graphql/overview/explorer", - "/v4/explorer-new": "/en/graphql/overview/explorer", - "/en/enterprise/3.0/graphql/overview/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/en/enterprise/graphql/overview/explorer": "/en/enterprise-server@latest/graphql/overview/explorer", - "/enterprise/3.0/graphql/overview/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/enterprise-server@3.0/graphql/overview/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/enterprise/graphql/overview/explorer": "/en/enterprise-server@latest/graphql/overview/explorer", - "/en/enterprise-server@3.0/v4/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/en/enterprise/3.0/v4/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/en/enterprise/v4/explorer": "/en/enterprise-server@latest/graphql/overview/explorer", - "/enterprise/3.0/v4/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/enterprise-server@3.0/v4/explorer": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/enterprise/v4/explorer": "/en/enterprise-server@latest/graphql/overview/explorer", - "/en/enterprise-server@3.0/v4/explorer-new": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/en/enterprise/3.0/v4/explorer-new": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/en/enterprise/v4/explorer-new": "/en/enterprise-server@latest/graphql/overview/explorer", - "/enterprise/3.0/v4/explorer-new": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/enterprise-server@3.0/v4/explorer-new": "/en/enterprise-server@3.0/graphql/overview/explorer", - "/enterprise/v4/explorer-new": "/en/enterprise-server@latest/graphql/overview/explorer", - "/en/enterprise/2.20/graphql/overview/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/enterprise/2.20/graphql/overview/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/enterprise-server@2.20/graphql/overview/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/en/enterprise-server@2.20/v4/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/en/enterprise/2.20/v4/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/enterprise/2.20/v4/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/enterprise-server@2.20/v4/explorer": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/en/enterprise-server@2.20/v4/explorer-new": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/en/enterprise/2.20/v4/explorer-new": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/enterprise/2.20/v4/explorer-new": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/enterprise-server@2.20/v4/explorer-new": "/en/enterprise-server@2.20/graphql/overview/explorer", - "/github-ae@latest/graphql/overview/explorer": "/en/github-ae@latest/graphql/overview/explorer", - "/en/github-ae@latest/v4/explorer": "/en/github-ae@latest/graphql/overview/explorer", - "/github-ae@latest/v4/explorer": "/en/github-ae@latest/graphql/overview/explorer", - "/en/github-ae@latest/v4/explorer-new": "/en/github-ae@latest/graphql/overview/explorer", - "/github-ae@latest/v4/explorer-new": "/en/github-ae@latest/graphql/overview/explorer", - "/en/free-pro-team@latest/graphql/overview": "/en/graphql/overview", - "/free-pro-team@latest/graphql/overview": "/en/graphql/overview", - "/graphql/overview": "/en/graphql/overview", - "/en/enterprise/3.0/graphql/overview": "/en/enterprise-server@3.0/graphql/overview", - "/en/enterprise/graphql/overview": "/en/enterprise-server@latest/graphql/overview", - "/enterprise/3.0/graphql/overview": "/en/enterprise-server@3.0/graphql/overview", - "/enterprise-server@3.0/graphql/overview": "/en/enterprise-server@3.0/graphql/overview", - "/enterprise/graphql/overview": "/en/enterprise-server@latest/graphql/overview", - "/en/enterprise/2.20/graphql/overview": "/en/enterprise-server@2.20/graphql/overview", - "/enterprise/2.20/graphql/overview": "/en/enterprise-server@2.20/graphql/overview", - "/enterprise-server@2.20/graphql/overview": "/en/enterprise-server@2.20/graphql/overview", - "/github-ae@latest/graphql/overview": "/en/github-ae@latest/graphql/overview", - "/en/free-pro-team@latest/graphql/overview/public-schema": "/en/graphql/overview/public-schema", - "/free-pro-team@latest/graphql/overview/public-schema": "/en/graphql/overview/public-schema", - "/graphql/overview/public-schema": "/en/graphql/overview/public-schema", - "/en/v4/public_schema": "/en/graphql/overview/public-schema", - "/en/free-pro-team@latest/v4/public_schema": "/en/graphql/overview/public-schema", - "/free-pro-team@latest/v4/public_schema": "/en/graphql/overview/public-schema", - "/v4/public_schema": "/en/graphql/overview/public-schema", - "/en/enterprise/3.0/graphql/overview/public-schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/en/enterprise/graphql/overview/public-schema": "/en/enterprise-server@latest/graphql/overview/public-schema", - "/enterprise/3.0/graphql/overview/public-schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/enterprise-server@3.0/graphql/overview/public-schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/enterprise/graphql/overview/public-schema": "/en/enterprise-server@latest/graphql/overview/public-schema", - "/en/enterprise-server@3.0/v4/public_schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/en/enterprise/3.0/v4/public_schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/en/enterprise/v4/public_schema": "/en/enterprise-server@latest/graphql/overview/public-schema", - "/enterprise/3.0/v4/public_schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/enterprise-server@3.0/v4/public_schema": "/en/enterprise-server@3.0/graphql/overview/public-schema", - "/enterprise/v4/public_schema": "/en/enterprise-server@latest/graphql/overview/public-schema", - "/en/enterprise/2.20/graphql/overview/public-schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/enterprise/2.20/graphql/overview/public-schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/enterprise-server@2.20/graphql/overview/public-schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/en/enterprise-server@2.20/v4/public_schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/en/enterprise/2.20/v4/public_schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/enterprise/2.20/v4/public_schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/enterprise-server@2.20/v4/public_schema": "/en/enterprise-server@2.20/graphql/overview/public-schema", - "/github-ae@latest/graphql/overview/public-schema": "/en/github-ae@latest/graphql/overview/public-schema", - "/en/github-ae@latest/v4/public_schema": "/en/github-ae@latest/graphql/overview/public-schema", - "/github-ae@latest/v4/public_schema": "/en/github-ae@latest/graphql/overview/public-schema", - "/en/free-pro-team@latest/graphql/overview/resource-limitations": "/en/graphql/overview/resource-limitations", - "/free-pro-team@latest/graphql/overview/resource-limitations": "/en/graphql/overview/resource-limitations", - "/graphql/overview/resource-limitations": "/en/graphql/overview/resource-limitations", - "/en/v4/guides/resource-limitations": "/en/graphql/overview/resource-limitations", - "/en/free-pro-team@latest/v4/guides/resource-limitations": "/en/graphql/overview/resource-limitations", - "/free-pro-team@latest/v4/guides/resource-limitations": "/en/graphql/overview/resource-limitations", - "/v4/guides/resource-limitations": "/en/graphql/overview/resource-limitations", - "/en/enterprise/3.0/graphql/overview/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/en/enterprise/graphql/overview/resource-limitations": "/en/enterprise-server@latest/graphql/overview/resource-limitations", - "/enterprise/3.0/graphql/overview/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/enterprise-server@3.0/graphql/overview/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/enterprise/graphql/overview/resource-limitations": "/en/enterprise-server@latest/graphql/overview/resource-limitations", - "/en/enterprise-server@3.0/v4/guides/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/en/enterprise/3.0/v4/guides/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/en/enterprise/v4/guides/resource-limitations": "/en/enterprise-server@latest/graphql/overview/resource-limitations", - "/enterprise/3.0/v4/guides/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/enterprise-server@3.0/v4/guides/resource-limitations": "/en/enterprise-server@3.0/graphql/overview/resource-limitations", - "/enterprise/v4/guides/resource-limitations": "/en/enterprise-server@latest/graphql/overview/resource-limitations", - "/en/enterprise/2.20/graphql/overview/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/enterprise/2.20/graphql/overview/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/enterprise-server@2.20/graphql/overview/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/en/enterprise-server@2.20/v4/guides/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/en/enterprise/2.20/v4/guides/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/enterprise/2.20/v4/guides/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/enterprise-server@2.20/v4/guides/resource-limitations": "/en/enterprise-server@2.20/graphql/overview/resource-limitations", - "/github-ae@latest/graphql/overview/resource-limitations": "/en/github-ae@latest/graphql/overview/resource-limitations", - "/en/github-ae@latest/v4/guides/resource-limitations": "/en/github-ae@latest/graphql/overview/resource-limitations", - "/github-ae@latest/v4/guides/resource-limitations": "/en/github-ae@latest/graphql/overview/resource-limitations", - "/en/free-pro-team@latest/graphql/overview/schema-previews": "/en/graphql/overview/schema-previews", - "/free-pro-team@latest/graphql/overview/schema-previews": "/en/graphql/overview/schema-previews", - "/graphql/overview/schema-previews": "/en/graphql/overview/schema-previews", - "/en/v4/previews": "/en/graphql/overview/schema-previews", - "/en/free-pro-team@latest/v4/previews": "/en/graphql/overview/schema-previews", - "/free-pro-team@latest/v4/previews": "/en/graphql/overview/schema-previews", - "/v4/previews": "/en/graphql/overview/schema-previews", - "/en/enterprise/3.0/graphql/overview/schema-previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/en/enterprise/graphql/overview/schema-previews": "/en/enterprise-server@latest/graphql/overview/schema-previews", - "/enterprise/3.0/graphql/overview/schema-previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/enterprise-server@3.0/graphql/overview/schema-previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/enterprise/graphql/overview/schema-previews": "/en/enterprise-server@latest/graphql/overview/schema-previews", - "/en/enterprise-server@3.0/v4/previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/en/enterprise/3.0/v4/previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/en/enterprise/v4/previews": "/en/enterprise-server@latest/graphql/overview/schema-previews", - "/enterprise/3.0/v4/previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/enterprise-server@3.0/v4/previews": "/en/enterprise-server@3.0/graphql/overview/schema-previews", - "/enterprise/v4/previews": "/en/enterprise-server@latest/graphql/overview/schema-previews", - "/en/enterprise/2.20/graphql/overview/schema-previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/enterprise/2.20/graphql/overview/schema-previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/enterprise-server@2.20/graphql/overview/schema-previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/en/enterprise-server@2.20/v4/previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/en/enterprise/2.20/v4/previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/enterprise/2.20/v4/previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/enterprise-server@2.20/v4/previews": "/en/enterprise-server@2.20/graphql/overview/schema-previews", - "/github-ae@latest/graphql/overview/schema-previews": "/en/github-ae@latest/graphql/overview/schema-previews", - "/en/github-ae@latest/v4/previews": "/en/github-ae@latest/graphql/overview/schema-previews", - "/github-ae@latest/v4/previews": "/en/github-ae@latest/graphql/overview/schema-previews", - "/en/free-pro-team@latest/graphql/reference/enums": "/en/graphql/reference/enums", - "/free-pro-team@latest/graphql/reference/enums": "/en/graphql/reference/enums", - "/graphql/reference/enums": "/en/graphql/reference/enums", - "/en/v4/enum": "/en/graphql/reference/enums", - "/en/free-pro-team@latest/v4/enum": "/en/graphql/reference/enums", - "/free-pro-team@latest/v4/enum": "/en/graphql/reference/enums", - "/v4/enum": "/en/graphql/reference/enums", - "/en/v4/reference/enum": "/en/graphql/reference/enums", - "/en/free-pro-team@latest/v4/reference/enum": "/en/graphql/reference/enums", - "/free-pro-team@latest/v4/reference/enum": "/en/graphql/reference/enums", - "/v4/reference/enum": "/en/graphql/reference/enums", - "/en/enterprise/3.0/graphql/reference/enums": "/en/enterprise-server@3.0/graphql/reference/enums", - "/en/enterprise/graphql/reference/enums": "/en/enterprise-server@latest/graphql/reference/enums", - "/enterprise/3.0/graphql/reference/enums": "/en/enterprise-server@3.0/graphql/reference/enums", - "/enterprise-server@3.0/graphql/reference/enums": "/en/enterprise-server@3.0/graphql/reference/enums", - "/enterprise/graphql/reference/enums": "/en/enterprise-server@latest/graphql/reference/enums", - "/en/enterprise-server@3.0/v4/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/en/enterprise/3.0/v4/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/en/enterprise/v4/enum": "/en/enterprise-server@latest/graphql/reference/enums", - "/enterprise/3.0/v4/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/enterprise-server@3.0/v4/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/enterprise/v4/enum": "/en/enterprise-server@latest/graphql/reference/enums", - "/en/enterprise-server@3.0/v4/reference/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/en/enterprise/3.0/v4/reference/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/en/enterprise/v4/reference/enum": "/en/enterprise-server@latest/graphql/reference/enums", - "/enterprise/3.0/v4/reference/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/enterprise-server@3.0/v4/reference/enum": "/en/enterprise-server@3.0/graphql/reference/enums", - "/enterprise/v4/reference/enum": "/en/enterprise-server@latest/graphql/reference/enums", - "/en/enterprise/2.20/graphql/reference/enums": "/en/enterprise-server@2.20/graphql/reference/enums", - "/enterprise/2.20/graphql/reference/enums": "/en/enterprise-server@2.20/graphql/reference/enums", - "/enterprise-server@2.20/graphql/reference/enums": "/en/enterprise-server@2.20/graphql/reference/enums", - "/en/enterprise-server@2.20/v4/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/en/enterprise/2.20/v4/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/enterprise/2.20/v4/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/enterprise-server@2.20/v4/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/en/enterprise-server@2.20/v4/reference/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/en/enterprise/2.20/v4/reference/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/enterprise/2.20/v4/reference/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/enterprise-server@2.20/v4/reference/enum": "/en/enterprise-server@2.20/graphql/reference/enums", - "/github-ae@latest/graphql/reference/enums": "/en/github-ae@latest/graphql/reference/enums", - "/en/github-ae@latest/v4/enum": "/en/github-ae@latest/graphql/reference/enums", - "/github-ae@latest/v4/enum": "/en/github-ae@latest/graphql/reference/enums", - "/en/github-ae@latest/v4/reference/enum": "/en/github-ae@latest/graphql/reference/enums", - "/github-ae@latest/v4/reference/enum": "/en/github-ae@latest/graphql/reference/enums", - "/en/free-pro-team@latest/graphql/reference": "/en/graphql/reference", - "/free-pro-team@latest/graphql/reference": "/en/graphql/reference", - "/graphql/reference": "/en/graphql/reference", - "/en/v4/reference": "/en/graphql/reference", - "/en/free-pro-team@latest/v4/reference": "/en/graphql/reference", - "/free-pro-team@latest/v4/reference": "/en/graphql/reference", - "/v4/reference": "/en/graphql/reference", - "/en/enterprise/3.0/graphql/reference": "/en/enterprise-server@3.0/graphql/reference", - "/en/enterprise/graphql/reference": "/en/enterprise-server@latest/graphql/reference", - "/enterprise/3.0/graphql/reference": "/en/enterprise-server@3.0/graphql/reference", - "/enterprise-server@3.0/graphql/reference": "/en/enterprise-server@3.0/graphql/reference", - "/enterprise/graphql/reference": "/en/enterprise-server@latest/graphql/reference", - "/en/enterprise-server@3.0/v4/reference": "/en/enterprise-server@3.0/graphql/reference", - "/en/enterprise/3.0/v4/reference": "/en/enterprise-server@3.0/graphql/reference", - "/en/enterprise/v4/reference": "/en/enterprise-server@latest/graphql/reference", - "/enterprise/3.0/v4/reference": "/en/enterprise-server@3.0/graphql/reference", - "/enterprise-server@3.0/v4/reference": "/en/enterprise-server@3.0/graphql/reference", - "/enterprise/v4/reference": "/en/enterprise-server@latest/graphql/reference", - "/en/enterprise/2.20/graphql/reference": "/en/enterprise-server@2.20/graphql/reference", - "/enterprise/2.20/graphql/reference": "/en/enterprise-server@2.20/graphql/reference", - "/enterprise-server@2.20/graphql/reference": "/en/enterprise-server@2.20/graphql/reference", - "/en/enterprise-server@2.20/v4/reference": "/en/enterprise-server@2.20/graphql/reference", - "/en/enterprise/2.20/v4/reference": "/en/enterprise-server@2.20/graphql/reference", - "/enterprise/2.20/v4/reference": "/en/enterprise-server@2.20/graphql/reference", - "/enterprise-server@2.20/v4/reference": "/en/enterprise-server@2.20/graphql/reference", - "/github-ae@latest/graphql/reference": "/en/github-ae@latest/graphql/reference", - "/en/github-ae@latest/v4/reference": "/en/github-ae@latest/graphql/reference", - "/github-ae@latest/v4/reference": "/en/github-ae@latest/graphql/reference", - "/en/free-pro-team@latest/graphql/reference/input-objects": "/en/graphql/reference/input-objects", - "/free-pro-team@latest/graphql/reference/input-objects": "/en/graphql/reference/input-objects", - "/graphql/reference/input-objects": "/en/graphql/reference/input-objects", - "/en/v4/input_object": "/en/graphql/reference/input-objects", - "/en/free-pro-team@latest/v4/input_object": "/en/graphql/reference/input-objects", - "/free-pro-team@latest/v4/input_object": "/en/graphql/reference/input-objects", - "/v4/input_object": "/en/graphql/reference/input-objects", - "/en/v4/reference/input_object": "/en/graphql/reference/input-objects", - "/en/free-pro-team@latest/v4/reference/input_object": "/en/graphql/reference/input-objects", - "/free-pro-team@latest/v4/reference/input_object": "/en/graphql/reference/input-objects", - "/v4/reference/input_object": "/en/graphql/reference/input-objects", - "/en/enterprise/3.0/graphql/reference/input-objects": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/en/enterprise/graphql/reference/input-objects": "/en/enterprise-server@latest/graphql/reference/input-objects", - "/enterprise/3.0/graphql/reference/input-objects": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/enterprise-server@3.0/graphql/reference/input-objects": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/enterprise/graphql/reference/input-objects": "/en/enterprise-server@latest/graphql/reference/input-objects", - "/en/enterprise-server@3.0/v4/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/en/enterprise/3.0/v4/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/en/enterprise/v4/input_object": "/en/enterprise-server@latest/graphql/reference/input-objects", - "/enterprise/3.0/v4/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/enterprise-server@3.0/v4/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/enterprise/v4/input_object": "/en/enterprise-server@latest/graphql/reference/input-objects", - "/en/enterprise-server@3.0/v4/reference/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/en/enterprise/3.0/v4/reference/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/en/enterprise/v4/reference/input_object": "/en/enterprise-server@latest/graphql/reference/input-objects", - "/enterprise/3.0/v4/reference/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/enterprise-server@3.0/v4/reference/input_object": "/en/enterprise-server@3.0/graphql/reference/input-objects", - "/enterprise/v4/reference/input_object": "/en/enterprise-server@latest/graphql/reference/input-objects", - "/en/enterprise/2.20/graphql/reference/input-objects": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/enterprise/2.20/graphql/reference/input-objects": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/enterprise-server@2.20/graphql/reference/input-objects": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/en/enterprise-server@2.20/v4/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/en/enterprise/2.20/v4/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/enterprise/2.20/v4/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/enterprise-server@2.20/v4/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/en/enterprise-server@2.20/v4/reference/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/en/enterprise/2.20/v4/reference/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/enterprise/2.20/v4/reference/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/enterprise-server@2.20/v4/reference/input_object": "/en/enterprise-server@2.20/graphql/reference/input-objects", - "/github-ae@latest/graphql/reference/input-objects": "/en/github-ae@latest/graphql/reference/input-objects", - "/en/github-ae@latest/v4/input_object": "/en/github-ae@latest/graphql/reference/input-objects", - "/github-ae@latest/v4/input_object": "/en/github-ae@latest/graphql/reference/input-objects", - "/en/github-ae@latest/v4/reference/input_object": "/en/github-ae@latest/graphql/reference/input-objects", - "/github-ae@latest/v4/reference/input_object": "/en/github-ae@latest/graphql/reference/input-objects", - "/en/free-pro-team@latest/graphql/reference/interfaces": "/en/graphql/reference/interfaces", - "/free-pro-team@latest/graphql/reference/interfaces": "/en/graphql/reference/interfaces", - "/graphql/reference/interfaces": "/en/graphql/reference/interfaces", - "/en/v4/interface": "/en/graphql/reference/interfaces", - "/en/free-pro-team@latest/v4/interface": "/en/graphql/reference/interfaces", - "/free-pro-team@latest/v4/interface": "/en/graphql/reference/interfaces", - "/v4/interface": "/en/graphql/reference/interfaces", - "/en/v4/reference/interface": "/en/graphql/reference/interfaces", - "/en/free-pro-team@latest/v4/reference/interface": "/en/graphql/reference/interfaces", - "/free-pro-team@latest/v4/reference/interface": "/en/graphql/reference/interfaces", - "/v4/reference/interface": "/en/graphql/reference/interfaces", - "/en/enterprise/3.0/graphql/reference/interfaces": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/en/enterprise/graphql/reference/interfaces": "/en/enterprise-server@latest/graphql/reference/interfaces", - "/enterprise/3.0/graphql/reference/interfaces": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/enterprise-server@3.0/graphql/reference/interfaces": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/enterprise/graphql/reference/interfaces": "/en/enterprise-server@latest/graphql/reference/interfaces", - "/en/enterprise-server@3.0/v4/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/en/enterprise/3.0/v4/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/en/enterprise/v4/interface": "/en/enterprise-server@latest/graphql/reference/interfaces", - "/enterprise/3.0/v4/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/enterprise-server@3.0/v4/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/enterprise/v4/interface": "/en/enterprise-server@latest/graphql/reference/interfaces", - "/en/enterprise-server@3.0/v4/reference/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/en/enterprise/3.0/v4/reference/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/en/enterprise/v4/reference/interface": "/en/enterprise-server@latest/graphql/reference/interfaces", - "/enterprise/3.0/v4/reference/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/enterprise-server@3.0/v4/reference/interface": "/en/enterprise-server@3.0/graphql/reference/interfaces", - "/enterprise/v4/reference/interface": "/en/enterprise-server@latest/graphql/reference/interfaces", - "/en/enterprise/2.20/graphql/reference/interfaces": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/enterprise/2.20/graphql/reference/interfaces": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/enterprise-server@2.20/graphql/reference/interfaces": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/en/enterprise-server@2.20/v4/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/en/enterprise/2.20/v4/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/enterprise/2.20/v4/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/enterprise-server@2.20/v4/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/en/enterprise-server@2.20/v4/reference/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/en/enterprise/2.20/v4/reference/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/enterprise/2.20/v4/reference/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/enterprise-server@2.20/v4/reference/interface": "/en/enterprise-server@2.20/graphql/reference/interfaces", - "/github-ae@latest/graphql/reference/interfaces": "/en/github-ae@latest/graphql/reference/interfaces", - "/en/github-ae@latest/v4/interface": "/en/github-ae@latest/graphql/reference/interfaces", - "/github-ae@latest/v4/interface": "/en/github-ae@latest/graphql/reference/interfaces", - "/en/github-ae@latest/v4/reference/interface": "/en/github-ae@latest/graphql/reference/interfaces", - "/github-ae@latest/v4/reference/interface": "/en/github-ae@latest/graphql/reference/interfaces", - "/en/free-pro-team@latest/graphql/reference/mutations": "/en/graphql/reference/mutations", - "/free-pro-team@latest/graphql/reference/mutations": "/en/graphql/reference/mutations", - "/graphql/reference/mutations": "/en/graphql/reference/mutations", - "/en/v4/mutation": "/en/graphql/reference/mutations", - "/en/free-pro-team@latest/v4/mutation": "/en/graphql/reference/mutations", - "/free-pro-team@latest/v4/mutation": "/en/graphql/reference/mutations", - "/v4/mutation": "/en/graphql/reference/mutations", - "/en/v4/reference/mutation": "/en/graphql/reference/mutations", - "/en/free-pro-team@latest/v4/reference/mutation": "/en/graphql/reference/mutations", - "/free-pro-team@latest/v4/reference/mutation": "/en/graphql/reference/mutations", - "/v4/reference/mutation": "/en/graphql/reference/mutations", - "/en/enterprise/3.0/graphql/reference/mutations": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/en/enterprise/graphql/reference/mutations": "/en/enterprise-server@latest/graphql/reference/mutations", - "/enterprise/3.0/graphql/reference/mutations": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/enterprise-server@3.0/graphql/reference/mutations": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/enterprise/graphql/reference/mutations": "/en/enterprise-server@latest/graphql/reference/mutations", - "/en/enterprise-server@3.0/v4/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/en/enterprise/3.0/v4/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/en/enterprise/v4/mutation": "/en/enterprise-server@latest/graphql/reference/mutations", - "/enterprise/3.0/v4/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/enterprise-server@3.0/v4/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/enterprise/v4/mutation": "/en/enterprise-server@latest/graphql/reference/mutations", - "/en/enterprise-server@3.0/v4/reference/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/en/enterprise/3.0/v4/reference/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/en/enterprise/v4/reference/mutation": "/en/enterprise-server@latest/graphql/reference/mutations", - "/enterprise/3.0/v4/reference/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/enterprise-server@3.0/v4/reference/mutation": "/en/enterprise-server@3.0/graphql/reference/mutations", - "/enterprise/v4/reference/mutation": "/en/enterprise-server@latest/graphql/reference/mutations", - "/en/enterprise/2.20/graphql/reference/mutations": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/enterprise/2.20/graphql/reference/mutations": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/enterprise-server@2.20/graphql/reference/mutations": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/en/enterprise-server@2.20/v4/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/en/enterprise/2.20/v4/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/enterprise/2.20/v4/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/enterprise-server@2.20/v4/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/en/enterprise-server@2.20/v4/reference/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/en/enterprise/2.20/v4/reference/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/enterprise/2.20/v4/reference/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/enterprise-server@2.20/v4/reference/mutation": "/en/enterprise-server@2.20/graphql/reference/mutations", - "/github-ae@latest/graphql/reference/mutations": "/en/github-ae@latest/graphql/reference/mutations", - "/en/github-ae@latest/v4/mutation": "/en/github-ae@latest/graphql/reference/mutations", - "/github-ae@latest/v4/mutation": "/en/github-ae@latest/graphql/reference/mutations", - "/en/github-ae@latest/v4/reference/mutation": "/en/github-ae@latest/graphql/reference/mutations", - "/github-ae@latest/v4/reference/mutation": "/en/github-ae@latest/graphql/reference/mutations", - "/en/free-pro-team@latest/graphql/reference/objects": "/en/graphql/reference/objects", - "/free-pro-team@latest/graphql/reference/objects": "/en/graphql/reference/objects", - "/graphql/reference/objects": "/en/graphql/reference/objects", - "/en/v4/object": "/en/graphql/reference/objects", - "/en/free-pro-team@latest/v4/object": "/en/graphql/reference/objects", - "/free-pro-team@latest/v4/object": "/en/graphql/reference/objects", - "/v4/object": "/en/graphql/reference/objects", - "/en/v4/reference/object": "/en/graphql/reference/objects", - "/en/free-pro-team@latest/v4/reference/object": "/en/graphql/reference/objects", - "/free-pro-team@latest/v4/reference/object": "/en/graphql/reference/objects", - "/v4/reference/object": "/en/graphql/reference/objects", - "/en/enterprise/3.0/graphql/reference/objects": "/en/enterprise-server@3.0/graphql/reference/objects", - "/en/enterprise/graphql/reference/objects": "/en/enterprise-server@latest/graphql/reference/objects", - "/enterprise/3.0/graphql/reference/objects": "/en/enterprise-server@3.0/graphql/reference/objects", - "/enterprise-server@3.0/graphql/reference/objects": "/en/enterprise-server@3.0/graphql/reference/objects", - "/enterprise/graphql/reference/objects": "/en/enterprise-server@latest/graphql/reference/objects", - "/en/enterprise-server@3.0/v4/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/en/enterprise/3.0/v4/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/en/enterprise/v4/object": "/en/enterprise-server@latest/graphql/reference/objects", - "/enterprise/3.0/v4/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/enterprise-server@3.0/v4/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/enterprise/v4/object": "/en/enterprise-server@latest/graphql/reference/objects", - "/en/enterprise-server@3.0/v4/reference/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/en/enterprise/3.0/v4/reference/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/en/enterprise/v4/reference/object": "/en/enterprise-server@latest/graphql/reference/objects", - "/enterprise/3.0/v4/reference/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/enterprise-server@3.0/v4/reference/object": "/en/enterprise-server@3.0/graphql/reference/objects", - "/enterprise/v4/reference/object": "/en/enterprise-server@latest/graphql/reference/objects", - "/en/enterprise/2.20/graphql/reference/objects": "/en/enterprise-server@2.20/graphql/reference/objects", - "/enterprise/2.20/graphql/reference/objects": "/en/enterprise-server@2.20/graphql/reference/objects", - "/enterprise-server@2.20/graphql/reference/objects": "/en/enterprise-server@2.20/graphql/reference/objects", - "/en/enterprise-server@2.20/v4/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/en/enterprise/2.20/v4/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/enterprise/2.20/v4/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/enterprise-server@2.20/v4/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/en/enterprise-server@2.20/v4/reference/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/en/enterprise/2.20/v4/reference/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/enterprise/2.20/v4/reference/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/enterprise-server@2.20/v4/reference/object": "/en/enterprise-server@2.20/graphql/reference/objects", - "/github-ae@latest/graphql/reference/objects": "/en/github-ae@latest/graphql/reference/objects", - "/en/github-ae@latest/v4/object": "/en/github-ae@latest/graphql/reference/objects", - "/github-ae@latest/v4/object": "/en/github-ae@latest/graphql/reference/objects", - "/en/github-ae@latest/v4/reference/object": "/en/github-ae@latest/graphql/reference/objects", - "/github-ae@latest/v4/reference/object": "/en/github-ae@latest/graphql/reference/objects", - "/en/free-pro-team@latest/graphql/reference/queries": "/en/graphql/reference/queries", - "/free-pro-team@latest/graphql/reference/queries": "/en/graphql/reference/queries", - "/graphql/reference/queries": "/en/graphql/reference/queries", - "/en/v4/query": "/en/graphql/reference/queries", - "/en/free-pro-team@latest/v4/query": "/en/graphql/reference/queries", - "/free-pro-team@latest/v4/query": "/en/graphql/reference/queries", - "/v4/query": "/en/graphql/reference/queries", - "/en/v4/reference/query": "/en/graphql/reference/queries", - "/en/free-pro-team@latest/v4/reference/query": "/en/graphql/reference/queries", - "/free-pro-team@latest/v4/reference/query": "/en/graphql/reference/queries", - "/v4/reference/query": "/en/graphql/reference/queries", - "/en/enterprise/3.0/graphql/reference/queries": "/en/enterprise-server@3.0/graphql/reference/queries", - "/en/enterprise/graphql/reference/queries": "/en/enterprise-server@latest/graphql/reference/queries", - "/enterprise/3.0/graphql/reference/queries": "/en/enterprise-server@3.0/graphql/reference/queries", - "/enterprise-server@3.0/graphql/reference/queries": "/en/enterprise-server@3.0/graphql/reference/queries", - "/enterprise/graphql/reference/queries": "/en/enterprise-server@latest/graphql/reference/queries", - "/en/enterprise-server@3.0/v4/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/en/enterprise/3.0/v4/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/en/enterprise/v4/query": "/en/enterprise-server@latest/graphql/reference/queries", - "/enterprise/3.0/v4/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/enterprise-server@3.0/v4/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/enterprise/v4/query": "/en/enterprise-server@latest/graphql/reference/queries", - "/en/enterprise-server@3.0/v4/reference/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/en/enterprise/3.0/v4/reference/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/en/enterprise/v4/reference/query": "/en/enterprise-server@latest/graphql/reference/queries", - "/enterprise/3.0/v4/reference/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/enterprise-server@3.0/v4/reference/query": "/en/enterprise-server@3.0/graphql/reference/queries", - "/enterprise/v4/reference/query": "/en/enterprise-server@latest/graphql/reference/queries", - "/en/enterprise/2.20/graphql/reference/queries": "/en/enterprise-server@2.20/graphql/reference/queries", - "/enterprise/2.20/graphql/reference/queries": "/en/enterprise-server@2.20/graphql/reference/queries", - "/enterprise-server@2.20/graphql/reference/queries": "/en/enterprise-server@2.20/graphql/reference/queries", - "/en/enterprise-server@2.20/v4/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/en/enterprise/2.20/v4/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/enterprise/2.20/v4/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/enterprise-server@2.20/v4/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/en/enterprise-server@2.20/v4/reference/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/en/enterprise/2.20/v4/reference/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/enterprise/2.20/v4/reference/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/enterprise-server@2.20/v4/reference/query": "/en/enterprise-server@2.20/graphql/reference/queries", - "/github-ae@latest/graphql/reference/queries": "/en/github-ae@latest/graphql/reference/queries", - "/en/github-ae@latest/v4/query": "/en/github-ae@latest/graphql/reference/queries", - "/github-ae@latest/v4/query": "/en/github-ae@latest/graphql/reference/queries", - "/en/github-ae@latest/v4/reference/query": "/en/github-ae@latest/graphql/reference/queries", - "/github-ae@latest/v4/reference/query": "/en/github-ae@latest/graphql/reference/queries", - "/en/free-pro-team@latest/graphql/reference/scalars": "/en/graphql/reference/scalars", - "/free-pro-team@latest/graphql/reference/scalars": "/en/graphql/reference/scalars", - "/graphql/reference/scalars": "/en/graphql/reference/scalars", - "/en/v4/scalar": "/en/graphql/reference/scalars", - "/en/free-pro-team@latest/v4/scalar": "/en/graphql/reference/scalars", - "/free-pro-team@latest/v4/scalar": "/en/graphql/reference/scalars", - "/v4/scalar": "/en/graphql/reference/scalars", - "/en/v4/reference/scalar": "/en/graphql/reference/scalars", - "/en/free-pro-team@latest/v4/reference/scalar": "/en/graphql/reference/scalars", - "/free-pro-team@latest/v4/reference/scalar": "/en/graphql/reference/scalars", - "/v4/reference/scalar": "/en/graphql/reference/scalars", - "/en/enterprise/3.0/graphql/reference/scalars": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/en/enterprise/graphql/reference/scalars": "/en/enterprise-server@latest/graphql/reference/scalars", - "/enterprise/3.0/graphql/reference/scalars": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/enterprise-server@3.0/graphql/reference/scalars": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/enterprise/graphql/reference/scalars": "/en/enterprise-server@latest/graphql/reference/scalars", - "/en/enterprise-server@3.0/v4/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/en/enterprise/3.0/v4/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/en/enterprise/v4/scalar": "/en/enterprise-server@latest/graphql/reference/scalars", - "/enterprise/3.0/v4/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/enterprise-server@3.0/v4/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/enterprise/v4/scalar": "/en/enterprise-server@latest/graphql/reference/scalars", - "/en/enterprise-server@3.0/v4/reference/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/en/enterprise/3.0/v4/reference/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/en/enterprise/v4/reference/scalar": "/en/enterprise-server@latest/graphql/reference/scalars", - "/enterprise/3.0/v4/reference/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/enterprise-server@3.0/v4/reference/scalar": "/en/enterprise-server@3.0/graphql/reference/scalars", - "/enterprise/v4/reference/scalar": "/en/enterprise-server@latest/graphql/reference/scalars", - "/en/enterprise/2.20/graphql/reference/scalars": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/enterprise/2.20/graphql/reference/scalars": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/enterprise-server@2.20/graphql/reference/scalars": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/en/enterprise-server@2.20/v4/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/en/enterprise/2.20/v4/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/enterprise/2.20/v4/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/enterprise-server@2.20/v4/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/en/enterprise-server@2.20/v4/reference/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/en/enterprise/2.20/v4/reference/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/enterprise/2.20/v4/reference/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/enterprise-server@2.20/v4/reference/scalar": "/en/enterprise-server@2.20/graphql/reference/scalars", - "/github-ae@latest/graphql/reference/scalars": "/en/github-ae@latest/graphql/reference/scalars", - "/en/github-ae@latest/v4/scalar": "/en/github-ae@latest/graphql/reference/scalars", - "/github-ae@latest/v4/scalar": "/en/github-ae@latest/graphql/reference/scalars", - "/en/github-ae@latest/v4/reference/scalar": "/en/github-ae@latest/graphql/reference/scalars", - "/github-ae@latest/v4/reference/scalar": "/en/github-ae@latest/graphql/reference/scalars", - "/en/free-pro-team@latest/graphql/reference/unions": "/en/graphql/reference/unions", - "/free-pro-team@latest/graphql/reference/unions": "/en/graphql/reference/unions", - "/graphql/reference/unions": "/en/graphql/reference/unions", - "/en/v4/union": "/en/graphql/reference/unions", - "/en/free-pro-team@latest/v4/union": "/en/graphql/reference/unions", - "/free-pro-team@latest/v4/union": "/en/graphql/reference/unions", - "/v4/union": "/en/graphql/reference/unions", - "/en/v4/reference/union": "/en/graphql/reference/unions", - "/en/free-pro-team@latest/v4/reference/union": "/en/graphql/reference/unions", - "/free-pro-team@latest/v4/reference/union": "/en/graphql/reference/unions", - "/v4/reference/union": "/en/graphql/reference/unions", - "/en/enterprise/3.0/graphql/reference/unions": "/en/enterprise-server@3.0/graphql/reference/unions", - "/en/enterprise/graphql/reference/unions": "/en/enterprise-server@latest/graphql/reference/unions", - "/enterprise/3.0/graphql/reference/unions": "/en/enterprise-server@3.0/graphql/reference/unions", - "/enterprise-server@3.0/graphql/reference/unions": "/en/enterprise-server@3.0/graphql/reference/unions", - "/enterprise/graphql/reference/unions": "/en/enterprise-server@latest/graphql/reference/unions", - "/en/enterprise-server@3.0/v4/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/en/enterprise/3.0/v4/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/en/enterprise/v4/union": "/en/enterprise-server@latest/graphql/reference/unions", - "/enterprise/3.0/v4/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/enterprise-server@3.0/v4/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/enterprise/v4/union": "/en/enterprise-server@latest/graphql/reference/unions", - "/en/enterprise-server@3.0/v4/reference/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/en/enterprise/3.0/v4/reference/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/en/enterprise/v4/reference/union": "/en/enterprise-server@latest/graphql/reference/unions", - "/enterprise/3.0/v4/reference/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/enterprise-server@3.0/v4/reference/union": "/en/enterprise-server@3.0/graphql/reference/unions", - "/enterprise/v4/reference/union": "/en/enterprise-server@latest/graphql/reference/unions", - "/en/enterprise/2.20/graphql/reference/unions": "/en/enterprise-server@2.20/graphql/reference/unions", - "/enterprise/2.20/graphql/reference/unions": "/en/enterprise-server@2.20/graphql/reference/unions", - "/enterprise-server@2.20/graphql/reference/unions": "/en/enterprise-server@2.20/graphql/reference/unions", - "/en/enterprise-server@2.20/v4/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/en/enterprise/2.20/v4/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/enterprise/2.20/v4/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/enterprise-server@2.20/v4/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/en/enterprise-server@2.20/v4/reference/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/en/enterprise/2.20/v4/reference/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/enterprise/2.20/v4/reference/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/enterprise-server@2.20/v4/reference/union": "/en/enterprise-server@2.20/graphql/reference/unions", - "/github-ae@latest/graphql/reference/unions": "/en/github-ae@latest/graphql/reference/unions", - "/en/github-ae@latest/v4/union": "/en/github-ae@latest/graphql/reference/unions", - "/github-ae@latest/v4/union": "/en/github-ae@latest/graphql/reference/unions", - "/en/github-ae@latest/v4/reference/union": "/en/github-ae@latest/graphql/reference/unions", - "/github-ae@latest/v4/reference/union": "/en/github-ae@latest/graphql/reference/unions", - "/en/free-pro-team@latest/rest/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/free-pro-team@latest/rest/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/rest/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/en/v3/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/en/free-pro-team@latest/v3/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/free-pro-team@latest/v3/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/v3/guides/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/en/rest/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/en/free-pro-team@latest/rest/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/free-pro-team@latest/rest/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/rest/basics-of-authentication": "/en/rest/guides/basics-of-authentication", - "/en/enterprise/3.0/rest/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/en/enterprise/rest/guides/basics-of-authentication": "/en/enterprise-server@latest/rest/guides/basics-of-authentication", - "/enterprise/3.0/rest/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/enterprise-server@3.0/rest/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/enterprise/rest/guides/basics-of-authentication": "/en/enterprise-server@latest/rest/guides/basics-of-authentication", - "/en/enterprise-server@3.0/v3/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/en/enterprise/3.0/v3/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/en/enterprise/v3/guides/basics-of-authentication": "/en/enterprise-server@latest/rest/guides/basics-of-authentication", - "/enterprise/3.0/v3/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/enterprise-server@3.0/v3/guides/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/enterprise/v3/guides/basics-of-authentication": "/en/enterprise-server@latest/rest/guides/basics-of-authentication", - "/en/enterprise-server@3.0/rest/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/en/enterprise/3.0/rest/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/en/enterprise/rest/basics-of-authentication": "/en/enterprise-server@latest/rest/guides/basics-of-authentication", - "/enterprise/3.0/rest/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/enterprise-server@3.0/rest/basics-of-authentication": "/en/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/enterprise/rest/basics-of-authentication": "/en/enterprise-server@latest/rest/guides/basics-of-authentication", - "/en/enterprise/2.20/rest/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/enterprise/2.20/rest/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/enterprise-server@2.20/rest/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/en/enterprise-server@2.20/v3/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/en/enterprise/2.20/v3/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/enterprise/2.20/v3/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/enterprise-server@2.20/v3/guides/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/en/enterprise-server@2.20/rest/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/en/enterprise/2.20/rest/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/enterprise/2.20/rest/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/enterprise-server@2.20/rest/basics-of-authentication": "/en/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/github-ae@latest/rest/guides/basics-of-authentication": "/en/github-ae@latest/rest/guides/basics-of-authentication", - "/en/github-ae@latest/v3/guides/basics-of-authentication": "/en/github-ae@latest/rest/guides/basics-of-authentication", - "/github-ae@latest/v3/guides/basics-of-authentication": "/en/github-ae@latest/rest/guides/basics-of-authentication", - "/en/github-ae@latest/rest/basics-of-authentication": "/en/github-ae@latest/rest/guides/basics-of-authentication", - "/github-ae@latest/rest/basics-of-authentication": "/en/github-ae@latest/rest/guides/basics-of-authentication", - "/en/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/rest/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/en/v3/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/en/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/v3/guides/best-practices-for-integrators": "/en/rest/guides/best-practices-for-integrators", - "/en/enterprise/3.0/rest/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/en/enterprise/rest/guides/best-practices-for-integrators": "/en/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/enterprise/3.0/rest/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/enterprise-server@3.0/rest/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/enterprise/rest/guides/best-practices-for-integrators": "/en/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/en/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/en/enterprise/3.0/v3/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/en/enterprise/v3/guides/best-practices-for-integrators": "/en/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/enterprise/3.0/v3/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/en/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/enterprise/v3/guides/best-practices-for-integrators": "/en/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/en/enterprise/2.20/rest/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/enterprise/2.20/rest/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/enterprise-server@2.20/rest/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/en/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/en/enterprise/2.20/v3/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/enterprise/2.20/v3/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/en/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/github-ae@latest/rest/guides/best-practices-for-integrators": "/en/github-ae@latest/rest/guides/best-practices-for-integrators", - "/en/github-ae@latest/v3/guides/best-practices-for-integrators": "/en/github-ae@latest/rest/guides/best-practices-for-integrators", - "/github-ae@latest/v3/guides/best-practices-for-integrators": "/en/github-ae@latest/rest/guides/best-practices-for-integrators", - "/en/free-pro-team@latest/rest/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/free-pro-team@latest/rest/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/rest/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/en/v3/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/en/free-pro-team@latest/v3/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/free-pro-team@latest/v3/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/v3/guides/building-a-ci-server": "/en/rest/guides/building-a-ci-server", - "/en/enterprise/3.0/rest/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/en/enterprise/rest/guides/building-a-ci-server": "/en/enterprise-server@latest/rest/guides/building-a-ci-server", - "/enterprise/3.0/rest/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/enterprise-server@3.0/rest/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/enterprise/rest/guides/building-a-ci-server": "/en/enterprise-server@latest/rest/guides/building-a-ci-server", - "/en/enterprise-server@3.0/v3/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/en/enterprise/3.0/v3/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/en/enterprise/v3/guides/building-a-ci-server": "/en/enterprise-server@latest/rest/guides/building-a-ci-server", - "/enterprise/3.0/v3/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/enterprise-server@3.0/v3/guides/building-a-ci-server": "/en/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/enterprise/v3/guides/building-a-ci-server": "/en/enterprise-server@latest/rest/guides/building-a-ci-server", - "/en/enterprise/2.20/rest/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/enterprise/2.20/rest/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/enterprise-server@2.20/rest/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/en/enterprise-server@2.20/v3/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/en/enterprise/2.20/v3/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/enterprise/2.20/v3/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/enterprise-server@2.20/v3/guides/building-a-ci-server": "/en/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/github-ae@latest/rest/guides/building-a-ci-server": "/en/github-ae@latest/rest/guides/building-a-ci-server", - "/en/github-ae@latest/v3/guides/building-a-ci-server": "/en/github-ae@latest/rest/guides/building-a-ci-server", - "/github-ae@latest/v3/guides/building-a-ci-server": "/en/github-ae@latest/rest/guides/building-a-ci-server", - "/en/free-pro-team@latest/rest/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/free-pro-team@latest/rest/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/rest/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/en/v3/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/en/free-pro-team@latest/v3/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/free-pro-team@latest/v3/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/v3/guides/delivering-deployments": "/en/rest/guides/delivering-deployments", - "/en/enterprise/3.0/rest/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/en/enterprise/rest/guides/delivering-deployments": "/en/enterprise-server@latest/rest/guides/delivering-deployments", - "/enterprise/3.0/rest/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/enterprise-server@3.0/rest/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/enterprise/rest/guides/delivering-deployments": "/en/enterprise-server@latest/rest/guides/delivering-deployments", - "/en/enterprise-server@3.0/v3/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/en/enterprise/3.0/v3/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/en/enterprise/v3/guides/delivering-deployments": "/en/enterprise-server@latest/rest/guides/delivering-deployments", - "/enterprise/3.0/v3/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/enterprise-server@3.0/v3/guides/delivering-deployments": "/en/enterprise-server@3.0/rest/guides/delivering-deployments", - "/enterprise/v3/guides/delivering-deployments": "/en/enterprise-server@latest/rest/guides/delivering-deployments", - "/en/enterprise/2.20/rest/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/enterprise/2.20/rest/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/enterprise-server@2.20/rest/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/en/enterprise-server@2.20/v3/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/en/enterprise/2.20/v3/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/enterprise/2.20/v3/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/enterprise-server@2.20/v3/guides/delivering-deployments": "/en/enterprise-server@2.20/rest/guides/delivering-deployments", - "/github-ae@latest/rest/guides/delivering-deployments": "/en/github-ae@latest/rest/guides/delivering-deployments", - "/en/github-ae@latest/v3/guides/delivering-deployments": "/en/github-ae@latest/rest/guides/delivering-deployments", - "/github-ae@latest/v3/guides/delivering-deployments": "/en/github-ae@latest/rest/guides/delivering-deployments", - "/en/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/rest/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/en/v3/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/en/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/v3/guides/discovering-resources-for-a-user": "/en/rest/guides/discovering-resources-for-a-user", - "/en/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/en/enterprise/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/enterprise/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/en/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/en/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/en/enterprise/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/enterprise/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/en/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/en/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/en/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/en/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/github-ae@latest/rest/guides/discovering-resources-for-a-user": "/en/github-ae@latest/rest/guides/discovering-resources-for-a-user", - "/en/github-ae@latest/v3/guides/discovering-resources-for-a-user": "/en/github-ae@latest/rest/guides/discovering-resources-for-a-user", - "/github-ae@latest/v3/guides/discovering-resources-for-a-user": "/en/github-ae@latest/rest/guides/discovering-resources-for-a-user", - "/en/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/en/rest/guides/getting-started-with-the-checks-api", - "/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/en/rest/guides/getting-started-with-the-checks-api", - "/rest/guides/getting-started-with-the-checks-api": "/en/rest/guides/getting-started-with-the-checks-api", - "/en/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/en/enterprise/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", - "/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/enterprise/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", - "/en/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/github-ae@latest/rest/guides/getting-started-with-the-checks-api": "/en/github-ae@latest/rest/guides/getting-started-with-the-checks-api", - "/en/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/en/rest/guides/getting-started-with-the-git-database-api", - "/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/en/rest/guides/getting-started-with-the-git-database-api", - "/rest/guides/getting-started-with-the-git-database-api": "/en/rest/guides/getting-started-with-the-git-database-api", - "/en/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/en/enterprise/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", - "/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/enterprise/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", - "/en/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/github-ae@latest/rest/guides/getting-started-with-the-git-database-api": "/en/github-ae@latest/rest/guides/getting-started-with-the-git-database-api", - "/en/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/en/rest/guides/getting-started-with-the-rest-api", - "/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/en/rest/guides/getting-started-with-the-rest-api", - "/rest/guides/getting-started-with-the-rest-api": "/en/rest/guides/getting-started-with-the-rest-api", - "/en/v3/guides/getting-started": "/en/rest/guides/getting-started-with-the-rest-api", - "/en/free-pro-team@latest/v3/guides/getting-started": "/en/rest/guides/getting-started-with-the-rest-api", - "/free-pro-team@latest/v3/guides/getting-started": "/en/rest/guides/getting-started-with-the-rest-api", - "/v3/guides/getting-started": "/en/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/enterprise/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise-server@3.0/v3/guides/getting-started": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise/3.0/v3/guides/getting-started": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise/v3/guides/getting-started": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/enterprise/3.0/v3/guides/getting-started": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/enterprise-server@3.0/v3/guides/getting-started": "/en/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/enterprise/v3/guides/getting-started": "/en/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise-server@2.20/v3/guides/getting-started": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/en/enterprise/2.20/v3/guides/getting-started": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/enterprise/2.20/v3/guides/getting-started": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/enterprise-server@2.20/v3/guides/getting-started": "/en/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/github-ae@latest/rest/guides/getting-started-with-the-rest-api": "/en/github-ae@latest/rest/guides/getting-started-with-the-rest-api", - "/en/github-ae@latest/v3/guides/getting-started": "/en/github-ae@latest/rest/guides/getting-started-with-the-rest-api", - "/github-ae@latest/v3/guides/getting-started": "/en/github-ae@latest/rest/guides/getting-started-with-the-rest-api", - "/en/free-pro-team@latest/rest/guides": "/en/rest/guides", - "/free-pro-team@latest/rest/guides": "/en/rest/guides", - "/rest/guides": "/en/rest/guides", - "/en/v3/guides": "/en/rest/guides", - "/en/free-pro-team@latest/v3/guides": "/en/rest/guides", - "/free-pro-team@latest/v3/guides": "/en/rest/guides", - "/v3/guides": "/en/rest/guides", - "/en/enterprise/3.0/rest/guides": "/en/enterprise-server@3.0/rest/guides", - "/en/enterprise/rest/guides": "/en/enterprise-server@latest/rest/guides", - "/enterprise/3.0/rest/guides": "/en/enterprise-server@3.0/rest/guides", - "/enterprise-server@3.0/rest/guides": "/en/enterprise-server@3.0/rest/guides", - "/enterprise/rest/guides": "/en/enterprise-server@latest/rest/guides", - "/en/enterprise-server@3.0/v3/guides": "/en/enterprise-server@3.0/rest/guides", - "/en/enterprise/3.0/v3/guides": "/en/enterprise-server@3.0/rest/guides", - "/en/enterprise/v3/guides": "/en/enterprise-server@latest/rest/guides", - "/enterprise/3.0/v3/guides": "/en/enterprise-server@3.0/rest/guides", - "/enterprise-server@3.0/v3/guides": "/en/enterprise-server@3.0/rest/guides", - "/enterprise/v3/guides": "/en/enterprise-server@latest/rest/guides", - "/en/enterprise/2.20/rest/guides": "/en/enterprise-server@2.20/rest/guides", - "/enterprise/2.20/rest/guides": "/en/enterprise-server@2.20/rest/guides", - "/enterprise-server@2.20/rest/guides": "/en/enterprise-server@2.20/rest/guides", - "/en/enterprise-server@2.20/v3/guides": "/en/enterprise-server@2.20/rest/guides", - "/en/enterprise/2.20/v3/guides": "/en/enterprise-server@2.20/rest/guides", - "/enterprise/2.20/v3/guides": "/en/enterprise-server@2.20/rest/guides", - "/enterprise-server@2.20/v3/guides": "/en/enterprise-server@2.20/rest/guides", - "/github-ae@latest/rest/guides": "/en/github-ae@latest/rest/guides", - "/en/github-ae@latest/v3/guides": "/en/github-ae@latest/rest/guides", - "/github-ae@latest/v3/guides": "/en/github-ae@latest/rest/guides", - "/en/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/rest/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/en/v3/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/en/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/v3/guides/rendering-data-as-graphs": "/en/rest/guides/rendering-data-as-graphs", - "/en/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/en/enterprise/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/enterprise-server@3.0/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/enterprise/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/en/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/en/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/en/enterprise/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/enterprise/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/en/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/enterprise-server@2.20/rest/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/en/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/en/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/en/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/github-ae@latest/rest/guides/rendering-data-as-graphs": "/en/github-ae@latest/rest/guides/rendering-data-as-graphs", - "/en/github-ae@latest/v3/guides/rendering-data-as-graphs": "/en/github-ae@latest/rest/guides/rendering-data-as-graphs", - "/github-ae@latest/v3/guides/rendering-data-as-graphs": "/en/github-ae@latest/rest/guides/rendering-data-as-graphs", - "/en/free-pro-team@latest/rest/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/free-pro-team@latest/rest/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/rest/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/en/v3/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/en/free-pro-team@latest/v3/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/free-pro-team@latest/v3/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/v3/guides/traversing-with-pagination": "/en/rest/guides/traversing-with-pagination", - "/en/enterprise/3.0/rest/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/en/enterprise/rest/guides/traversing-with-pagination": "/en/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/enterprise/3.0/rest/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/enterprise-server@3.0/rest/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/enterprise/rest/guides/traversing-with-pagination": "/en/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/en/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/en/enterprise/3.0/v3/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/en/enterprise/v3/guides/traversing-with-pagination": "/en/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/enterprise/3.0/v3/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/en/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/enterprise/v3/guides/traversing-with-pagination": "/en/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/en/enterprise/2.20/rest/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/enterprise/2.20/rest/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/enterprise-server@2.20/rest/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/en/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/en/enterprise/2.20/v3/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/enterprise/2.20/v3/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/en/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/github-ae@latest/rest/guides/traversing-with-pagination": "/en/github-ae@latest/rest/guides/traversing-with-pagination", - "/en/github-ae@latest/v3/guides/traversing-with-pagination": "/en/github-ae@latest/rest/guides/traversing-with-pagination", - "/github-ae@latest/v3/guides/traversing-with-pagination": "/en/github-ae@latest/rest/guides/traversing-with-pagination", - "/en/free-pro-team@latest/rest/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/free-pro-team@latest/rest/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/rest/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/en/v3/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/en/free-pro-team@latest/v3/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/free-pro-team@latest/v3/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/v3/guides/working-with-comments": "/en/rest/guides/working-with-comments", - "/en/enterprise/3.0/rest/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/en/enterprise/rest/guides/working-with-comments": "/en/enterprise-server@latest/rest/guides/working-with-comments", - "/enterprise/3.0/rest/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/enterprise-server@3.0/rest/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/enterprise/rest/guides/working-with-comments": "/en/enterprise-server@latest/rest/guides/working-with-comments", - "/en/enterprise-server@3.0/v3/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/en/enterprise/3.0/v3/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/en/enterprise/v3/guides/working-with-comments": "/en/enterprise-server@latest/rest/guides/working-with-comments", - "/enterprise/3.0/v3/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/enterprise-server@3.0/v3/guides/working-with-comments": "/en/enterprise-server@3.0/rest/guides/working-with-comments", - "/enterprise/v3/guides/working-with-comments": "/en/enterprise-server@latest/rest/guides/working-with-comments", - "/en/enterprise/2.20/rest/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/enterprise/2.20/rest/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/enterprise-server@2.20/rest/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/en/enterprise-server@2.20/v3/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/en/enterprise/2.20/v3/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/enterprise/2.20/v3/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/enterprise-server@2.20/v3/guides/working-with-comments": "/en/enterprise-server@2.20/rest/guides/working-with-comments", - "/github-ae@latest/rest/guides/working-with-comments": "/en/github-ae@latest/rest/guides/working-with-comments", - "/en/github-ae@latest/v3/guides/working-with-comments": "/en/github-ae@latest/rest/guides/working-with-comments", - "/github-ae@latest/v3/guides/working-with-comments": "/en/github-ae@latest/rest/guides/working-with-comments", - "/en/free-pro-team@latest/rest": "/en/rest", - "/free-pro-team@latest/rest": "/en/rest", - "/rest": "/en/rest", - "/en/v3": "/en/rest", - "/en/free-pro-team@latest/v3": "/en/rest", - "/free-pro-team@latest/v3": "/en/rest", - "/v3": "/en/rest", - "/en/enterprise/3.0/rest": "/en/enterprise-server@3.0/rest", - "/en/enterprise/rest": "/en/enterprise-server@latest/rest", - "/enterprise/3.0/rest": "/en/enterprise-server@3.0/rest", - "/enterprise-server@3.0/rest": "/en/enterprise-server@3.0/rest", - "/enterprise/rest": "/en/enterprise-server@latest/rest", - "/en/enterprise-server@3.0/v3": "/en/enterprise-server@3.0/rest", - "/en/enterprise/3.0/v3": "/en/enterprise-server@3.0/rest", - "/en/enterprise/v3": "/en/enterprise-server@latest/rest", - "/enterprise/3.0/v3": "/en/enterprise-server@3.0/rest", - "/enterprise-server@3.0/v3": "/en/enterprise-server@3.0/rest", - "/enterprise/v3": "/en/enterprise-server@latest/rest", - "/en/enterprise/2.20/rest": "/en/enterprise-server@2.20/rest", - "/enterprise/2.20/rest": "/en/enterprise-server@2.20/rest", - "/enterprise-server@2.20/rest": "/en/enterprise-server@2.20/rest", - "/en/enterprise-server@2.20/v3": "/en/enterprise-server@2.20/rest", - "/en/enterprise/2.20/v3": "/en/enterprise-server@2.20/rest", - "/enterprise/2.20/v3": "/en/enterprise-server@2.20/rest", - "/enterprise-server@2.20/v3": "/en/enterprise-server@2.20/rest", - "/github-ae@latest/rest": "/en/github-ae@latest/rest", - "/en/github-ae@latest/v3": "/en/github-ae@latest/rest", - "/github-ae@latest/v3": "/en/github-ae@latest/rest", - "/en/free-pro-team@latest/rest/overview/api-previews": "/en/rest/overview/api-previews", - "/free-pro-team@latest/rest/overview/api-previews": "/en/rest/overview/api-previews", - "/rest/overview/api-previews": "/en/rest/overview/api-previews", - "/en/v3/previews": "/en/rest/overview/api-previews", - "/en/free-pro-team@latest/v3/previews": "/en/rest/overview/api-previews", - "/free-pro-team@latest/v3/previews": "/en/rest/overview/api-previews", - "/v3/previews": "/en/rest/overview/api-previews", - "/en/enterprise/3.0/rest/overview/api-previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/en/enterprise/rest/overview/api-previews": "/en/enterprise-server@latest/rest/overview/api-previews", - "/enterprise/3.0/rest/overview/api-previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/enterprise-server@3.0/rest/overview/api-previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/enterprise/rest/overview/api-previews": "/en/enterprise-server@latest/rest/overview/api-previews", - "/en/enterprise-server@3.0/v3/previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/en/enterprise/3.0/v3/previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/en/enterprise/v3/previews": "/en/enterprise-server@latest/rest/overview/api-previews", - "/enterprise/3.0/v3/previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/enterprise-server@3.0/v3/previews": "/en/enterprise-server@3.0/rest/overview/api-previews", - "/enterprise/v3/previews": "/en/enterprise-server@latest/rest/overview/api-previews", - "/en/enterprise/2.20/rest/overview/api-previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/enterprise/2.20/rest/overview/api-previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/enterprise-server@2.20/rest/overview/api-previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/en/enterprise-server@2.20/v3/previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/en/enterprise/2.20/v3/previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/enterprise/2.20/v3/previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/enterprise-server@2.20/v3/previews": "/en/enterprise-server@2.20/rest/overview/api-previews", - "/github-ae@latest/rest/overview/api-previews": "/en/github-ae@latest/rest/overview/api-previews", - "/en/github-ae@latest/v3/previews": "/en/github-ae@latest/rest/overview/api-previews", - "/github-ae@latest/v3/previews": "/en/github-ae@latest/rest/overview/api-previews", - "/en/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/rest/overview/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/en/v3/apps/available-endpoints": "/en/rest/overview/endpoints-available-for-github-apps", - "/en/free-pro-team@latest/v3/apps/available-endpoints": "/en/rest/overview/endpoints-available-for-github-apps", - "/free-pro-team@latest/v3/apps/available-endpoints": "/en/rest/overview/endpoints-available-for-github-apps", - "/v3/apps/available-endpoints": "/en/rest/overview/endpoints-available-for-github-apps", - "/en/rest/reference/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/en/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/rest/reference/endpoints-available-for-github-apps": "/en/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/enterprise/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise-server@3.0/v3/apps/available-endpoints": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/3.0/v3/apps/available-endpoints": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/v3/apps/available-endpoints": "/en/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/enterprise/3.0/v3/apps/available-endpoints": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/enterprise-server@3.0/v3/apps/available-endpoints": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/enterprise/v3/apps/available-endpoints": "/en/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/enterprise/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise-server@2.20/v3/apps/available-endpoints": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/2.20/v3/apps/available-endpoints": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/enterprise/2.20/v3/apps/available-endpoints": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/enterprise-server@2.20/v3/apps/available-endpoints": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/en/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/en/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/github-ae@latest/rest/overview/endpoints-available-for-github-apps": "/en/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/en/github-ae@latest/v3/apps/available-endpoints": "/en/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/github-ae@latest/v3/apps/available-endpoints": "/en/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/en/github-ae@latest/rest/reference/endpoints-available-for-github-apps": "/en/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/github-ae@latest/rest/reference/endpoints-available-for-github-apps": "/en/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/en/free-pro-team@latest/rest/overview": "/en/rest/overview", - "/free-pro-team@latest/rest/overview": "/en/rest/overview", - "/rest/overview": "/en/rest/overview", - "/en/enterprise/3.0/rest/overview": "/en/enterprise-server@3.0/rest/overview", - "/en/enterprise/rest/overview": "/en/enterprise-server@latest/rest/overview", - "/enterprise/3.0/rest/overview": "/en/enterprise-server@3.0/rest/overview", - "/enterprise-server@3.0/rest/overview": "/en/enterprise-server@3.0/rest/overview", - "/enterprise/rest/overview": "/en/enterprise-server@latest/rest/overview", - "/en/enterprise/2.20/rest/overview": "/en/enterprise-server@2.20/rest/overview", - "/enterprise/2.20/rest/overview": "/en/enterprise-server@2.20/rest/overview", - "/enterprise-server@2.20/rest/overview": "/en/enterprise-server@2.20/rest/overview", - "/github-ae@latest/rest/overview": "/en/github-ae@latest/rest/overview", - "/en/free-pro-team@latest/rest/overview/libraries": "/en/rest/overview/libraries", - "/free-pro-team@latest/rest/overview/libraries": "/en/rest/overview/libraries", - "/rest/overview/libraries": "/en/rest/overview/libraries", - "/en/v3/libraries": "/en/rest/overview/libraries", - "/en/free-pro-team@latest/v3/libraries": "/en/rest/overview/libraries", - "/free-pro-team@latest/v3/libraries": "/en/rest/overview/libraries", - "/v3/libraries": "/en/rest/overview/libraries", - "/en/enterprise/3.0/rest/overview/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/en/enterprise/rest/overview/libraries": "/en/enterprise-server@latest/rest/overview/libraries", - "/enterprise/3.0/rest/overview/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/enterprise-server@3.0/rest/overview/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/enterprise/rest/overview/libraries": "/en/enterprise-server@latest/rest/overview/libraries", - "/en/enterprise-server@3.0/v3/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/en/enterprise/3.0/v3/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/en/enterprise/v3/libraries": "/en/enterprise-server@latest/rest/overview/libraries", - "/enterprise/3.0/v3/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/enterprise-server@3.0/v3/libraries": "/en/enterprise-server@3.0/rest/overview/libraries", - "/enterprise/v3/libraries": "/en/enterprise-server@latest/rest/overview/libraries", - "/en/enterprise/2.20/rest/overview/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/enterprise/2.20/rest/overview/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/enterprise-server@2.20/rest/overview/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/en/enterprise-server@2.20/v3/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/en/enterprise/2.20/v3/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/enterprise/2.20/v3/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/enterprise-server@2.20/v3/libraries": "/en/enterprise-server@2.20/rest/overview/libraries", - "/github-ae@latest/rest/overview/libraries": "/en/github-ae@latest/rest/overview/libraries", - "/en/github-ae@latest/v3/libraries": "/en/github-ae@latest/rest/overview/libraries", - "/github-ae@latest/v3/libraries": "/en/github-ae@latest/rest/overview/libraries", - "/en/free-pro-team@latest/rest/overview/media-types": "/en/rest/overview/media-types", - "/free-pro-team@latest/rest/overview/media-types": "/en/rest/overview/media-types", - "/rest/overview/media-types": "/en/rest/overview/media-types", - "/en/v3/media": "/en/rest/overview/media-types", - "/en/free-pro-team@latest/v3/media": "/en/rest/overview/media-types", - "/free-pro-team@latest/v3/media": "/en/rest/overview/media-types", - "/v3/media": "/en/rest/overview/media-types", - "/en/enterprise/3.0/rest/overview/media-types": "/en/enterprise-server@3.0/rest/overview/media-types", - "/en/enterprise/rest/overview/media-types": "/en/enterprise-server@latest/rest/overview/media-types", - "/enterprise/3.0/rest/overview/media-types": "/en/enterprise-server@3.0/rest/overview/media-types", - "/enterprise-server@3.0/rest/overview/media-types": "/en/enterprise-server@3.0/rest/overview/media-types", - "/enterprise/rest/overview/media-types": "/en/enterprise-server@latest/rest/overview/media-types", - "/en/enterprise-server@3.0/v3/media": "/en/enterprise-server@3.0/rest/overview/media-types", - "/en/enterprise/3.0/v3/media": "/en/enterprise-server@3.0/rest/overview/media-types", - "/en/enterprise/v3/media": "/en/enterprise-server@latest/rest/overview/media-types", - "/enterprise/3.0/v3/media": "/en/enterprise-server@3.0/rest/overview/media-types", - "/enterprise-server@3.0/v3/media": "/en/enterprise-server@3.0/rest/overview/media-types", - "/enterprise/v3/media": "/en/enterprise-server@latest/rest/overview/media-types", - "/en/enterprise/2.20/rest/overview/media-types": "/en/enterprise-server@2.20/rest/overview/media-types", - "/enterprise/2.20/rest/overview/media-types": "/en/enterprise-server@2.20/rest/overview/media-types", - "/enterprise-server@2.20/rest/overview/media-types": "/en/enterprise-server@2.20/rest/overview/media-types", - "/en/enterprise-server@2.20/v3/media": "/en/enterprise-server@2.20/rest/overview/media-types", - "/en/enterprise/2.20/v3/media": "/en/enterprise-server@2.20/rest/overview/media-types", - "/enterprise/2.20/v3/media": "/en/enterprise-server@2.20/rest/overview/media-types", - "/enterprise-server@2.20/v3/media": "/en/enterprise-server@2.20/rest/overview/media-types", - "/github-ae@latest/rest/overview/media-types": "/en/github-ae@latest/rest/overview/media-types", - "/en/github-ae@latest/v3/media": "/en/github-ae@latest/rest/overview/media-types", - "/github-ae@latest/v3/media": "/en/github-ae@latest/rest/overview/media-types", - "/en/free-pro-team@latest/rest/overview/openapi-description": "/en/rest/overview/openapi-description", - "/free-pro-team@latest/rest/overview/openapi-description": "/en/rest/overview/openapi-description", - "/rest/overview/openapi-description": "/en/rest/overview/openapi-description", - "/en/enterprise/3.0/rest/overview/openapi-description": "/en/enterprise-server@3.0/rest/overview/openapi-description", - "/en/enterprise/rest/overview/openapi-description": "/en/enterprise-server@latest/rest/overview/openapi-description", - "/enterprise/3.0/rest/overview/openapi-description": "/en/enterprise-server@3.0/rest/overview/openapi-description", - "/enterprise-server@3.0/rest/overview/openapi-description": "/en/enterprise-server@3.0/rest/overview/openapi-description", - "/enterprise/rest/overview/openapi-description": "/en/enterprise-server@latest/rest/overview/openapi-description", - "/en/enterprise/2.20/rest/overview/openapi-description": "/en/enterprise-server@2.20/rest/overview/openapi-description", - "/enterprise/2.20/rest/overview/openapi-description": "/en/enterprise-server@2.20/rest/overview/openapi-description", - "/enterprise-server@2.20/rest/overview/openapi-description": "/en/enterprise-server@2.20/rest/overview/openapi-description", - "/en/free-pro-team@latest/rest/overview/other-authentication-methods": "/en/rest/overview/other-authentication-methods", - "/free-pro-team@latest/rest/overview/other-authentication-methods": "/en/rest/overview/other-authentication-methods", - "/rest/overview/other-authentication-methods": "/en/rest/overview/other-authentication-methods", - "/en/v3/auth": "/en/rest/overview/other-authentication-methods", - "/en/free-pro-team@latest/v3/auth": "/en/rest/overview/other-authentication-methods", - "/free-pro-team@latest/v3/auth": "/en/rest/overview/other-authentication-methods", - "/v3/auth": "/en/rest/overview/other-authentication-methods", - "/en/enterprise/3.0/rest/overview/other-authentication-methods": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/en/enterprise/rest/overview/other-authentication-methods": "/en/enterprise-server@latest/rest/overview/other-authentication-methods", - "/enterprise/3.0/rest/overview/other-authentication-methods": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/enterprise-server@3.0/rest/overview/other-authentication-methods": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/enterprise/rest/overview/other-authentication-methods": "/en/enterprise-server@latest/rest/overview/other-authentication-methods", - "/en/enterprise-server@3.0/v3/auth": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/en/enterprise/3.0/v3/auth": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/en/enterprise/v3/auth": "/en/enterprise-server@latest/rest/overview/other-authentication-methods", - "/enterprise/3.0/v3/auth": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/enterprise-server@3.0/v3/auth": "/en/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/enterprise/v3/auth": "/en/enterprise-server@latest/rest/overview/other-authentication-methods", - "/en/enterprise/2.20/rest/overview/other-authentication-methods": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/enterprise/2.20/rest/overview/other-authentication-methods": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/enterprise-server@2.20/rest/overview/other-authentication-methods": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/en/enterprise-server@2.20/v3/auth": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/en/enterprise/2.20/v3/auth": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/enterprise/2.20/v3/auth": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/enterprise-server@2.20/v3/auth": "/en/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/github-ae@latest/rest/overview/other-authentication-methods": "/en/github-ae@latest/rest/overview/other-authentication-methods", - "/en/github-ae@latest/v3/auth": "/en/github-ae@latest/rest/overview/other-authentication-methods", - "/github-ae@latest/v3/auth": "/en/github-ae@latest/rest/overview/other-authentication-methods", - "/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/en/rest/overview/resources-in-the-rest-api", - "/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/en/rest/overview/resources-in-the-rest-api", - "/rest/overview/resources-in-the-rest-api": "/en/rest/overview/resources-in-the-rest-api", - "/en/rest/initialize-the-repo": "/en/rest/overview/resources-in-the-rest-api", - "/en/free-pro-team@latest/rest/initialize-the-repo": "/en/rest/overview/resources-in-the-rest-api", - "/free-pro-team@latest/rest/initialize-the-repo": "/en/rest/overview/resources-in-the-rest-api", - "/rest/initialize-the-repo": "/en/rest/overview/resources-in-the-rest-api", - "/en/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/en/enterprise/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/enterprise-server@3.0/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/enterprise/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/en/enterprise-server@3.0/rest/initialize-the-repo": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/en/enterprise/3.0/rest/initialize-the-repo": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/en/enterprise/rest/initialize-the-repo": "/en/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/enterprise/3.0/rest/initialize-the-repo": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/enterprise-server@3.0/rest/initialize-the-repo": "/en/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/enterprise/rest/initialize-the-repo": "/en/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/en/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/enterprise-server@2.20/rest/overview/resources-in-the-rest-api": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/en/enterprise-server@2.20/rest/initialize-the-repo": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/en/enterprise/2.20/rest/initialize-the-repo": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/enterprise/2.20/rest/initialize-the-repo": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/enterprise-server@2.20/rest/initialize-the-repo": "/en/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/github-ae@latest/rest/overview/resources-in-the-rest-api": "/en/github-ae@latest/rest/overview/resources-in-the-rest-api", - "/en/github-ae@latest/rest/initialize-the-repo": "/en/github-ae@latest/rest/overview/resources-in-the-rest-api", - "/github-ae@latest/rest/initialize-the-repo": "/en/github-ae@latest/rest/overview/resources-in-the-rest-api", - "/en/free-pro-team@latest/rest/overview/troubleshooting": "/en/rest/overview/troubleshooting", - "/free-pro-team@latest/rest/overview/troubleshooting": "/en/rest/overview/troubleshooting", - "/rest/overview/troubleshooting": "/en/rest/overview/troubleshooting", - "/en/v3/troubleshooting": "/en/rest/overview/troubleshooting", - "/en/free-pro-team@latest/v3/troubleshooting": "/en/rest/overview/troubleshooting", - "/free-pro-team@latest/v3/troubleshooting": "/en/rest/overview/troubleshooting", - "/v3/troubleshooting": "/en/rest/overview/troubleshooting", - "/en/enterprise/3.0/rest/overview/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/en/enterprise/rest/overview/troubleshooting": "/en/enterprise-server@latest/rest/overview/troubleshooting", - "/enterprise/3.0/rest/overview/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/enterprise-server@3.0/rest/overview/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/enterprise/rest/overview/troubleshooting": "/en/enterprise-server@latest/rest/overview/troubleshooting", - "/en/enterprise-server@3.0/v3/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/en/enterprise/3.0/v3/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/en/enterprise/v3/troubleshooting": "/en/enterprise-server@latest/rest/overview/troubleshooting", - "/enterprise/3.0/v3/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/enterprise-server@3.0/v3/troubleshooting": "/en/enterprise-server@3.0/rest/overview/troubleshooting", - "/enterprise/v3/troubleshooting": "/en/enterprise-server@latest/rest/overview/troubleshooting", - "/en/enterprise/2.20/rest/overview/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/enterprise/2.20/rest/overview/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/enterprise-server@2.20/rest/overview/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/en/enterprise-server@2.20/v3/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/en/enterprise/2.20/v3/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/enterprise/2.20/v3/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/enterprise-server@2.20/v3/troubleshooting": "/en/enterprise-server@2.20/rest/overview/troubleshooting", - "/github-ae@latest/rest/overview/troubleshooting": "/en/github-ae@latest/rest/overview/troubleshooting", - "/en/github-ae@latest/v3/troubleshooting": "/en/github-ae@latest/rest/overview/troubleshooting", - "/github-ae@latest/v3/troubleshooting": "/en/github-ae@latest/rest/overview/troubleshooting", - "/en/free-pro-team@latest/rest/reference/actions": "/en/rest/reference/actions", - "/free-pro-team@latest/rest/reference/actions": "/en/rest/reference/actions", - "/rest/reference/actions": "/en/rest/reference/actions", - "/en/v3/actions": "/en/rest/reference/actions", - "/en/free-pro-team@latest/v3/actions": "/en/rest/reference/actions", - "/free-pro-team@latest/v3/actions": "/en/rest/reference/actions", - "/v3/actions": "/en/rest/reference/actions", - "/en/enterprise/3.0/rest/reference/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/en/enterprise/rest/reference/actions": "/en/enterprise-server@latest/rest/reference/actions", - "/enterprise/3.0/rest/reference/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/enterprise-server@3.0/rest/reference/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/enterprise/rest/reference/actions": "/en/enterprise-server@latest/rest/reference/actions", - "/en/enterprise-server@3.0/v3/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/en/enterprise/3.0/v3/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/en/enterprise/v3/actions": "/en/enterprise-server@latest/rest/reference/actions", - "/enterprise/3.0/v3/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/enterprise-server@3.0/v3/actions": "/en/enterprise-server@3.0/rest/reference/actions", - "/enterprise/v3/actions": "/en/enterprise-server@latest/rest/reference/actions", - "/en/free-pro-team@latest/rest/reference/activity": "/en/rest/reference/activity", - "/free-pro-team@latest/rest/reference/activity": "/en/rest/reference/activity", - "/rest/reference/activity": "/en/rest/reference/activity", - "/en/v3/activity": "/en/rest/reference/activity", - "/en/free-pro-team@latest/v3/activity": "/en/rest/reference/activity", - "/free-pro-team@latest/v3/activity": "/en/rest/reference/activity", - "/v3/activity": "/en/rest/reference/activity", - "/en/enterprise/3.0/rest/reference/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/en/enterprise/rest/reference/activity": "/en/enterprise-server@latest/rest/reference/activity", - "/enterprise/3.0/rest/reference/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/enterprise-server@3.0/rest/reference/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/enterprise/rest/reference/activity": "/en/enterprise-server@latest/rest/reference/activity", - "/en/enterprise-server@3.0/v3/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/en/enterprise/3.0/v3/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/en/enterprise/v3/activity": "/en/enterprise-server@latest/rest/reference/activity", - "/enterprise/3.0/v3/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/enterprise-server@3.0/v3/activity": "/en/enterprise-server@3.0/rest/reference/activity", - "/enterprise/v3/activity": "/en/enterprise-server@latest/rest/reference/activity", - "/en/enterprise/2.20/rest/reference/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/enterprise/2.20/rest/reference/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/enterprise-server@2.20/rest/reference/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/en/enterprise-server@2.20/v3/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/en/enterprise/2.20/v3/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/enterprise/2.20/v3/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/enterprise-server@2.20/v3/activity": "/en/enterprise-server@2.20/rest/reference/activity", - "/github-ae@latest/rest/reference/activity": "/en/github-ae@latest/rest/reference/activity", - "/en/github-ae@latest/v3/activity": "/en/github-ae@latest/rest/reference/activity", - "/github-ae@latest/v3/activity": "/en/github-ae@latest/rest/reference/activity", - "/en/free-pro-team@latest/rest/reference/apps": "/en/rest/reference/apps", - "/free-pro-team@latest/rest/reference/apps": "/en/rest/reference/apps", - "/rest/reference/apps": "/en/rest/reference/apps", - "/en/v3/apps": "/en/rest/reference/apps", - "/en/free-pro-team@latest/v3/apps": "/en/rest/reference/apps", - "/free-pro-team@latest/v3/apps": "/en/rest/reference/apps", - "/v3/apps": "/en/rest/reference/apps", - "/en/enterprise/3.0/rest/reference/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/en/enterprise/rest/reference/apps": "/en/enterprise-server@latest/rest/reference/apps", - "/enterprise/3.0/rest/reference/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/enterprise-server@3.0/rest/reference/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/enterprise/rest/reference/apps": "/en/enterprise-server@latest/rest/reference/apps", - "/en/enterprise-server@3.0/v3/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/en/enterprise/3.0/v3/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/en/enterprise/v3/apps": "/en/enterprise-server@latest/rest/reference/apps", - "/enterprise/3.0/v3/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/enterprise-server@3.0/v3/apps": "/en/enterprise-server@3.0/rest/reference/apps", - "/enterprise/v3/apps": "/en/enterprise-server@latest/rest/reference/apps", - "/en/enterprise/2.20/rest/reference/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/enterprise/2.20/rest/reference/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/enterprise-server@2.20/rest/reference/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/en/enterprise-server@2.20/v3/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/en/enterprise/2.20/v3/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/enterprise/2.20/v3/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/enterprise-server@2.20/v3/apps": "/en/enterprise-server@2.20/rest/reference/apps", - "/github-ae@latest/rest/reference/apps": "/en/github-ae@latest/rest/reference/apps", - "/en/github-ae@latest/v3/apps": "/en/github-ae@latest/rest/reference/apps", - "/github-ae@latest/v3/apps": "/en/github-ae@latest/rest/reference/apps", - "/en/free-pro-team@latest/rest/reference/billing": "/en/rest/reference/billing", - "/free-pro-team@latest/rest/reference/billing": "/en/rest/reference/billing", - "/rest/reference/billing": "/en/rest/reference/billing", - "/en/free-pro-team@latest/rest/reference/checks": "/en/rest/reference/checks", - "/free-pro-team@latest/rest/reference/checks": "/en/rest/reference/checks", - "/rest/reference/checks": "/en/rest/reference/checks", - "/en/v3/checks": "/en/rest/reference/checks", - "/en/free-pro-team@latest/v3/checks": "/en/rest/reference/checks", - "/free-pro-team@latest/v3/checks": "/en/rest/reference/checks", - "/v3/checks": "/en/rest/reference/checks", - "/en/enterprise/3.0/rest/reference/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/en/enterprise/rest/reference/checks": "/en/enterprise-server@latest/rest/reference/checks", - "/enterprise/3.0/rest/reference/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/enterprise-server@3.0/rest/reference/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/enterprise/rest/reference/checks": "/en/enterprise-server@latest/rest/reference/checks", - "/en/enterprise-server@3.0/v3/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/en/enterprise/3.0/v3/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/en/enterprise/v3/checks": "/en/enterprise-server@latest/rest/reference/checks", - "/enterprise/3.0/v3/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/enterprise-server@3.0/v3/checks": "/en/enterprise-server@3.0/rest/reference/checks", - "/enterprise/v3/checks": "/en/enterprise-server@latest/rest/reference/checks", - "/en/enterprise/2.20/rest/reference/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/enterprise/2.20/rest/reference/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/enterprise-server@2.20/rest/reference/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/en/enterprise-server@2.20/v3/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/en/enterprise/2.20/v3/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/enterprise/2.20/v3/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/enterprise-server@2.20/v3/checks": "/en/enterprise-server@2.20/rest/reference/checks", - "/github-ae@latest/rest/reference/checks": "/en/github-ae@latest/rest/reference/checks", - "/en/github-ae@latest/v3/checks": "/en/github-ae@latest/rest/reference/checks", - "/github-ae@latest/v3/checks": "/en/github-ae@latest/rest/reference/checks", - "/en/free-pro-team@latest/rest/reference/code-scanning": "/en/rest/reference/code-scanning", - "/free-pro-team@latest/rest/reference/code-scanning": "/en/rest/reference/code-scanning", - "/rest/reference/code-scanning": "/en/rest/reference/code-scanning", - "/en/v3/code-scanning": "/en/rest/reference/code-scanning", - "/en/free-pro-team@latest/v3/code-scanning": "/en/rest/reference/code-scanning", - "/free-pro-team@latest/v3/code-scanning": "/en/rest/reference/code-scanning", - "/v3/code-scanning": "/en/rest/reference/code-scanning", - "/en/enterprise/3.0/rest/reference/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/en/enterprise/rest/reference/code-scanning": "/en/enterprise-server@latest/rest/reference/code-scanning", - "/enterprise/3.0/rest/reference/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/enterprise-server@3.0/rest/reference/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/enterprise/rest/reference/code-scanning": "/en/enterprise-server@latest/rest/reference/code-scanning", - "/en/enterprise-server@3.0/v3/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/en/enterprise/3.0/v3/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/en/enterprise/v3/code-scanning": "/en/enterprise-server@latest/rest/reference/code-scanning", - "/enterprise/3.0/v3/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/enterprise-server@3.0/v3/code-scanning": "/en/enterprise-server@3.0/rest/reference/code-scanning", - "/enterprise/v3/code-scanning": "/en/enterprise-server@latest/rest/reference/code-scanning", - "/en/free-pro-team@latest/rest/reference/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/free-pro-team@latest/rest/reference/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/rest/reference/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/en/v3/codes_of_conduct": "/en/rest/reference/codes-of-conduct", - "/en/free-pro-team@latest/v3/codes_of_conduct": "/en/rest/reference/codes-of-conduct", - "/free-pro-team@latest/v3/codes_of_conduct": "/en/rest/reference/codes-of-conduct", - "/v3/codes_of_conduct": "/en/rest/reference/codes-of-conduct", - "/en/v3/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/en/free-pro-team@latest/v3/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/free-pro-team@latest/v3/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/v3/codes-of-conduct": "/en/rest/reference/codes-of-conduct", - "/en/enterprise/3.0/rest/reference/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/en/enterprise/rest/reference/codes-of-conduct": "/en/enterprise-server@latest/rest/reference/codes-of-conduct", - "/enterprise/3.0/rest/reference/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/enterprise-server@3.0/rest/reference/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/enterprise/rest/reference/codes-of-conduct": "/en/enterprise-server@latest/rest/reference/codes-of-conduct", - "/en/enterprise-server@3.0/v3/codes_of_conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/en/enterprise/3.0/v3/codes_of_conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/en/enterprise/v3/codes_of_conduct": "/en/enterprise-server@latest/rest/reference/codes-of-conduct", - "/enterprise/3.0/v3/codes_of_conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/enterprise-server@3.0/v3/codes_of_conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/enterprise/v3/codes_of_conduct": "/en/enterprise-server@latest/rest/reference/codes-of-conduct", - "/en/enterprise-server@3.0/v3/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/en/enterprise/3.0/v3/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/en/enterprise/v3/codes-of-conduct": "/en/enterprise-server@latest/rest/reference/codes-of-conduct", - "/enterprise/3.0/v3/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/enterprise-server@3.0/v3/codes-of-conduct": "/en/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/enterprise/v3/codes-of-conduct": "/en/enterprise-server@latest/rest/reference/codes-of-conduct", - "/en/enterprise/2.20/rest/reference/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/enterprise/2.20/rest/reference/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/enterprise-server@2.20/rest/reference/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/en/enterprise-server@2.20/v3/codes_of_conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/en/enterprise/2.20/v3/codes_of_conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/enterprise/2.20/v3/codes_of_conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/enterprise-server@2.20/v3/codes_of_conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/en/enterprise-server@2.20/v3/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/en/enterprise/2.20/v3/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/enterprise/2.20/v3/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/enterprise-server@2.20/v3/codes-of-conduct": "/en/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/github-ae@latest/rest/reference/codes-of-conduct": "/en/github-ae@latest/rest/reference/codes-of-conduct", - "/en/github-ae@latest/v3/codes_of_conduct": "/en/github-ae@latest/rest/reference/codes-of-conduct", - "/github-ae@latest/v3/codes_of_conduct": "/en/github-ae@latest/rest/reference/codes-of-conduct", - "/en/github-ae@latest/v3/codes-of-conduct": "/en/github-ae@latest/rest/reference/codes-of-conduct", - "/github-ae@latest/v3/codes-of-conduct": "/en/github-ae@latest/rest/reference/codes-of-conduct", - "/en/free-pro-team@latest/rest/reference/emojis": "/en/rest/reference/emojis", - "/free-pro-team@latest/rest/reference/emojis": "/en/rest/reference/emojis", - "/rest/reference/emojis": "/en/rest/reference/emojis", - "/en/v3/emojis": "/en/rest/reference/emojis", - "/en/free-pro-team@latest/v3/emojis": "/en/rest/reference/emojis", - "/free-pro-team@latest/v3/emojis": "/en/rest/reference/emojis", - "/v3/emojis": "/en/rest/reference/emojis", - "/en/v3/misc": "/en/rest/reference/emojis", - "/en/free-pro-team@latest/v3/misc": "/en/rest/reference/emojis", - "/free-pro-team@latest/v3/misc": "/en/rest/reference/emojis", - "/v3/misc": "/en/rest/reference/emojis", - "/en/enterprise/3.0/rest/reference/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/en/enterprise/rest/reference/emojis": "/en/enterprise-server@latest/rest/reference/emojis", - "/enterprise/3.0/rest/reference/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/enterprise-server@3.0/rest/reference/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/enterprise/rest/reference/emojis": "/en/enterprise-server@latest/rest/reference/emojis", - "/en/enterprise-server@3.0/v3/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/en/enterprise/3.0/v3/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/en/enterprise/v3/emojis": "/en/enterprise-server@latest/rest/reference/emojis", - "/enterprise/3.0/v3/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/enterprise-server@3.0/v3/emojis": "/en/enterprise-server@3.0/rest/reference/emojis", - "/enterprise/v3/emojis": "/en/enterprise-server@latest/rest/reference/emojis", - "/en/enterprise-server@3.0/v3/misc": "/en/enterprise-server@3.0/rest/reference/emojis", - "/en/enterprise/3.0/v3/misc": "/en/enterprise-server@3.0/rest/reference/emojis", - "/en/enterprise/v3/misc": "/en/enterprise-server@latest/rest/reference/emojis", - "/enterprise/3.0/v3/misc": "/en/enterprise-server@3.0/rest/reference/emojis", - "/enterprise-server@3.0/v3/misc": "/en/enterprise-server@3.0/rest/reference/emojis", - "/enterprise/v3/misc": "/en/enterprise-server@latest/rest/reference/emojis", - "/en/enterprise/2.20/rest/reference/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/enterprise/2.20/rest/reference/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/enterprise-server@2.20/rest/reference/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/en/enterprise-server@2.20/v3/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/en/enterprise/2.20/v3/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/enterprise/2.20/v3/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/enterprise-server@2.20/v3/emojis": "/en/enterprise-server@2.20/rest/reference/emojis", - "/en/enterprise-server@2.20/v3/misc": "/en/enterprise-server@2.20/rest/reference/emojis", - "/en/enterprise/2.20/v3/misc": "/en/enterprise-server@2.20/rest/reference/emojis", - "/enterprise/2.20/v3/misc": "/en/enterprise-server@2.20/rest/reference/emojis", - "/enterprise-server@2.20/v3/misc": "/en/enterprise-server@2.20/rest/reference/emojis", - "/github-ae@latest/rest/reference/emojis": "/en/github-ae@latest/rest/reference/emojis", - "/en/github-ae@latest/v3/emojis": "/en/github-ae@latest/rest/reference/emojis", - "/github-ae@latest/v3/emojis": "/en/github-ae@latest/rest/reference/emojis", - "/en/github-ae@latest/v3/misc": "/en/github-ae@latest/rest/reference/emojis", - "/github-ae@latest/v3/misc": "/en/github-ae@latest/rest/reference/emojis", - "/en/free-pro-team@latest/rest/reference/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/free-pro-team@latest/rest/reference/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/rest/reference/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/en/v3/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/en/free-pro-team@latest/v3/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/free-pro-team@latest/v3/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/v3/enterprise-admin": "/en/rest/reference/enterprise-admin", - "/en/v3/enterprise": "/en/rest/reference/enterprise-admin", - "/en/free-pro-team@latest/v3/enterprise": "/en/rest/reference/enterprise-admin", - "/free-pro-team@latest/v3/enterprise": "/en/rest/reference/enterprise-admin", - "/v3/enterprise": "/en/rest/reference/enterprise-admin", - "/en/enterprise/3.0/rest/reference/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/en/enterprise/rest/reference/enterprise-admin": "/en/enterprise-server@latest/rest/reference/enterprise-admin", - "/enterprise/3.0/rest/reference/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/enterprise-server@3.0/rest/reference/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/enterprise/rest/reference/enterprise-admin": "/en/enterprise-server@latest/rest/reference/enterprise-admin", - "/en/enterprise-server@3.0/v3/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/en/enterprise/3.0/v3/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/en/enterprise/v3/enterprise-admin": "/en/enterprise-server@latest/rest/reference/enterprise-admin", - "/enterprise/3.0/v3/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/enterprise-server@3.0/v3/enterprise-admin": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/enterprise/v3/enterprise-admin": "/en/enterprise-server@latest/rest/reference/enterprise-admin", - "/en/enterprise-server@3.0/v3/enterprise": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/en/enterprise/3.0/v3/enterprise": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/en/enterprise/v3/enterprise": "/en/enterprise-server@latest/rest/reference/enterprise-admin", - "/enterprise/3.0/v3/enterprise": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/enterprise-server@3.0/v3/enterprise": "/en/enterprise-server@3.0/rest/reference/enterprise-admin", - "/enterprise/v3/enterprise": "/en/enterprise-server@latest/rest/reference/enterprise-admin", - "/en/enterprise/2.20/rest/reference/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/enterprise/2.20/rest/reference/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/enterprise-server@2.20/rest/reference/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/en/enterprise-server@2.20/v3/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/en/enterprise/2.20/v3/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/enterprise/2.20/v3/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/enterprise-server@2.20/v3/enterprise-admin": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/en/enterprise-server@2.20/v3/enterprise": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/en/enterprise/2.20/v3/enterprise": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/enterprise/2.20/v3/enterprise": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/enterprise-server@2.20/v3/enterprise": "/en/enterprise-server@2.20/rest/reference/enterprise-admin", - "/github-ae@latest/rest/reference/enterprise-admin": "/en/github-ae@latest/rest/reference/enterprise-admin", - "/en/github-ae@latest/v3/enterprise-admin": "/en/github-ae@latest/rest/reference/enterprise-admin", - "/github-ae@latest/v3/enterprise-admin": "/en/github-ae@latest/rest/reference/enterprise-admin", - "/en/github-ae@latest/v3/enterprise": "/en/github-ae@latest/rest/reference/enterprise-admin", - "/github-ae@latest/v3/enterprise": "/en/github-ae@latest/rest/reference/enterprise-admin", - "/en/free-pro-team@latest/rest/reference/gists": "/en/rest/reference/gists", - "/free-pro-team@latest/rest/reference/gists": "/en/rest/reference/gists", - "/rest/reference/gists": "/en/rest/reference/gists", - "/en/v3/gists": "/en/rest/reference/gists", - "/en/free-pro-team@latest/v3/gists": "/en/rest/reference/gists", - "/free-pro-team@latest/v3/gists": "/en/rest/reference/gists", - "/v3/gists": "/en/rest/reference/gists", - "/en/enterprise/3.0/rest/reference/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/en/enterprise/rest/reference/gists": "/en/enterprise-server@latest/rest/reference/gists", - "/enterprise/3.0/rest/reference/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/enterprise-server@3.0/rest/reference/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/enterprise/rest/reference/gists": "/en/enterprise-server@latest/rest/reference/gists", - "/en/enterprise-server@3.0/v3/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/en/enterprise/3.0/v3/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/en/enterprise/v3/gists": "/en/enterprise-server@latest/rest/reference/gists", - "/enterprise/3.0/v3/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/enterprise-server@3.0/v3/gists": "/en/enterprise-server@3.0/rest/reference/gists", - "/enterprise/v3/gists": "/en/enterprise-server@latest/rest/reference/gists", - "/en/enterprise/2.20/rest/reference/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/enterprise/2.20/rest/reference/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/enterprise-server@2.20/rest/reference/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/en/enterprise-server@2.20/v3/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/en/enterprise/2.20/v3/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/enterprise/2.20/v3/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/enterprise-server@2.20/v3/gists": "/en/enterprise-server@2.20/rest/reference/gists", - "/github-ae@latest/rest/reference/gists": "/en/github-ae@latest/rest/reference/gists", - "/en/github-ae@latest/v3/gists": "/en/github-ae@latest/rest/reference/gists", - "/github-ae@latest/v3/gists": "/en/github-ae@latest/rest/reference/gists", - "/en/free-pro-team@latest/rest/reference/git": "/en/rest/reference/git", - "/free-pro-team@latest/rest/reference/git": "/en/rest/reference/git", - "/rest/reference/git": "/en/rest/reference/git", - "/en/v3/git": "/en/rest/reference/git", - "/en/free-pro-team@latest/v3/git": "/en/rest/reference/git", - "/free-pro-team@latest/v3/git": "/en/rest/reference/git", - "/v3/git": "/en/rest/reference/git", - "/en/enterprise/3.0/rest/reference/git": "/en/enterprise-server@3.0/rest/reference/git", - "/en/enterprise/rest/reference/git": "/en/enterprise-server@latest/rest/reference/git", - "/enterprise/3.0/rest/reference/git": "/en/enterprise-server@3.0/rest/reference/git", - "/enterprise-server@3.0/rest/reference/git": "/en/enterprise-server@3.0/rest/reference/git", - "/enterprise/rest/reference/git": "/en/enterprise-server@latest/rest/reference/git", - "/en/enterprise-server@3.0/v3/git": "/en/enterprise-server@3.0/rest/reference/git", - "/en/enterprise/3.0/v3/git": "/en/enterprise-server@3.0/rest/reference/git", - "/en/enterprise/v3/git": "/en/enterprise-server@latest/rest/reference/git", - "/enterprise/3.0/v3/git": "/en/enterprise-server@3.0/rest/reference/git", - "/enterprise-server@3.0/v3/git": "/en/enterprise-server@3.0/rest/reference/git", - "/enterprise/v3/git": "/en/enterprise-server@latest/rest/reference/git", - "/en/enterprise/2.20/rest/reference/git": "/en/enterprise-server@2.20/rest/reference/git", - "/enterprise/2.20/rest/reference/git": "/en/enterprise-server@2.20/rest/reference/git", - "/enterprise-server@2.20/rest/reference/git": "/en/enterprise-server@2.20/rest/reference/git", - "/en/enterprise-server@2.20/v3/git": "/en/enterprise-server@2.20/rest/reference/git", - "/en/enterprise/2.20/v3/git": "/en/enterprise-server@2.20/rest/reference/git", - "/enterprise/2.20/v3/git": "/en/enterprise-server@2.20/rest/reference/git", - "/enterprise-server@2.20/v3/git": "/en/enterprise-server@2.20/rest/reference/git", - "/github-ae@latest/rest/reference/git": "/en/github-ae@latest/rest/reference/git", - "/en/github-ae@latest/v3/git": "/en/github-ae@latest/rest/reference/git", - "/github-ae@latest/v3/git": "/en/github-ae@latest/rest/reference/git", - "/en/free-pro-team@latest/rest/reference/gitignore": "/en/rest/reference/gitignore", - "/free-pro-team@latest/rest/reference/gitignore": "/en/rest/reference/gitignore", - "/rest/reference/gitignore": "/en/rest/reference/gitignore", - "/en/v3/gitignore": "/en/rest/reference/gitignore", - "/en/free-pro-team@latest/v3/gitignore": "/en/rest/reference/gitignore", - "/free-pro-team@latest/v3/gitignore": "/en/rest/reference/gitignore", - "/v3/gitignore": "/en/rest/reference/gitignore", - "/en/enterprise/3.0/rest/reference/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/en/enterprise/rest/reference/gitignore": "/en/enterprise-server@latest/rest/reference/gitignore", - "/enterprise/3.0/rest/reference/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/enterprise-server@3.0/rest/reference/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/enterprise/rest/reference/gitignore": "/en/enterprise-server@latest/rest/reference/gitignore", - "/en/enterprise-server@3.0/v3/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/en/enterprise/3.0/v3/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/en/enterprise/v3/gitignore": "/en/enterprise-server@latest/rest/reference/gitignore", - "/enterprise/3.0/v3/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/enterprise-server@3.0/v3/gitignore": "/en/enterprise-server@3.0/rest/reference/gitignore", - "/enterprise/v3/gitignore": "/en/enterprise-server@latest/rest/reference/gitignore", - "/en/enterprise/2.20/rest/reference/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/enterprise/2.20/rest/reference/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/enterprise-server@2.20/rest/reference/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/en/enterprise-server@2.20/v3/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/en/enterprise/2.20/v3/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/enterprise/2.20/v3/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/enterprise-server@2.20/v3/gitignore": "/en/enterprise-server@2.20/rest/reference/gitignore", - "/github-ae@latest/rest/reference/gitignore": "/en/github-ae@latest/rest/reference/gitignore", - "/en/github-ae@latest/v3/gitignore": "/en/github-ae@latest/rest/reference/gitignore", - "/github-ae@latest/v3/gitignore": "/en/github-ae@latest/rest/reference/gitignore", - "/en/free-pro-team@latest/rest/reference": "/en/rest/reference", - "/free-pro-team@latest/rest/reference": "/en/rest/reference", - "/rest/reference": "/en/rest/reference", - "/en/enterprise/3.0/rest/reference": "/en/enterprise-server@3.0/rest/reference", - "/en/enterprise/rest/reference": "/en/enterprise-server@latest/rest/reference", - "/enterprise/3.0/rest/reference": "/en/enterprise-server@3.0/rest/reference", - "/enterprise-server@3.0/rest/reference": "/en/enterprise-server@3.0/rest/reference", - "/enterprise/rest/reference": "/en/enterprise-server@latest/rest/reference", - "/en/enterprise/2.20/rest/reference": "/en/enterprise-server@2.20/rest/reference", - "/enterprise/2.20/rest/reference": "/en/enterprise-server@2.20/rest/reference", - "/enterprise-server@2.20/rest/reference": "/en/enterprise-server@2.20/rest/reference", - "/github-ae@latest/rest/reference": "/en/github-ae@latest/rest/reference", - "/en/free-pro-team@latest/rest/reference/interactions": "/en/rest/reference/interactions", - "/free-pro-team@latest/rest/reference/interactions": "/en/rest/reference/interactions", - "/rest/reference/interactions": "/en/rest/reference/interactions", - "/en/v3/interactions": "/en/rest/reference/interactions", - "/en/free-pro-team@latest/v3/interactions": "/en/rest/reference/interactions", - "/free-pro-team@latest/v3/interactions": "/en/rest/reference/interactions", - "/v3/interactions": "/en/rest/reference/interactions", - "/en/free-pro-team@latest/rest/reference/issues": "/en/rest/reference/issues", - "/free-pro-team@latest/rest/reference/issues": "/en/rest/reference/issues", - "/rest/reference/issues": "/en/rest/reference/issues", - "/en/v3/issues": "/en/rest/reference/issues", - "/en/free-pro-team@latest/v3/issues": "/en/rest/reference/issues", - "/free-pro-team@latest/v3/issues": "/en/rest/reference/issues", - "/v3/issues": "/en/rest/reference/issues", - "/en/enterprise/3.0/rest/reference/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/en/enterprise/rest/reference/issues": "/en/enterprise-server@latest/rest/reference/issues", - "/enterprise/3.0/rest/reference/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/enterprise-server@3.0/rest/reference/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/enterprise/rest/reference/issues": "/en/enterprise-server@latest/rest/reference/issues", - "/en/enterprise-server@3.0/v3/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/en/enterprise/3.0/v3/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/en/enterprise/v3/issues": "/en/enterprise-server@latest/rest/reference/issues", - "/enterprise/3.0/v3/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/enterprise-server@3.0/v3/issues": "/en/enterprise-server@3.0/rest/reference/issues", - "/enterprise/v3/issues": "/en/enterprise-server@latest/rest/reference/issues", - "/en/enterprise/2.20/rest/reference/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/enterprise/2.20/rest/reference/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/enterprise-server@2.20/rest/reference/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/en/enterprise-server@2.20/v3/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/en/enterprise/2.20/v3/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/enterprise/2.20/v3/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/enterprise-server@2.20/v3/issues": "/en/enterprise-server@2.20/rest/reference/issues", - "/github-ae@latest/rest/reference/issues": "/en/github-ae@latest/rest/reference/issues", - "/en/github-ae@latest/v3/issues": "/en/github-ae@latest/rest/reference/issues", - "/github-ae@latest/v3/issues": "/en/github-ae@latest/rest/reference/issues", - "/en/free-pro-team@latest/rest/reference/licenses": "/en/rest/reference/licenses", - "/free-pro-team@latest/rest/reference/licenses": "/en/rest/reference/licenses", - "/rest/reference/licenses": "/en/rest/reference/licenses", - "/en/v3/licenses": "/en/rest/reference/licenses", - "/en/free-pro-team@latest/v3/licenses": "/en/rest/reference/licenses", - "/free-pro-team@latest/v3/licenses": "/en/rest/reference/licenses", - "/v3/licenses": "/en/rest/reference/licenses", - "/en/enterprise/3.0/rest/reference/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/en/enterprise/rest/reference/licenses": "/en/enterprise-server@latest/rest/reference/licenses", - "/enterprise/3.0/rest/reference/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/enterprise-server@3.0/rest/reference/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/enterprise/rest/reference/licenses": "/en/enterprise-server@latest/rest/reference/licenses", - "/en/enterprise-server@3.0/v3/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/en/enterprise/3.0/v3/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/en/enterprise/v3/licenses": "/en/enterprise-server@latest/rest/reference/licenses", - "/enterprise/3.0/v3/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/enterprise-server@3.0/v3/licenses": "/en/enterprise-server@3.0/rest/reference/licenses", - "/enterprise/v3/licenses": "/en/enterprise-server@latest/rest/reference/licenses", - "/en/enterprise/2.20/rest/reference/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/enterprise/2.20/rest/reference/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/enterprise-server@2.20/rest/reference/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/en/enterprise-server@2.20/v3/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/en/enterprise/2.20/v3/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/enterprise/2.20/v3/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/enterprise-server@2.20/v3/licenses": "/en/enterprise-server@2.20/rest/reference/licenses", - "/github-ae@latest/rest/reference/licenses": "/en/github-ae@latest/rest/reference/licenses", - "/en/github-ae@latest/v3/licenses": "/en/github-ae@latest/rest/reference/licenses", - "/github-ae@latest/v3/licenses": "/en/github-ae@latest/rest/reference/licenses", - "/en/free-pro-team@latest/rest/reference/markdown": "/en/rest/reference/markdown", - "/free-pro-team@latest/rest/reference/markdown": "/en/rest/reference/markdown", - "/rest/reference/markdown": "/en/rest/reference/markdown", - "/en/v3/markdown": "/en/rest/reference/markdown", - "/en/free-pro-team@latest/v3/markdown": "/en/rest/reference/markdown", - "/free-pro-team@latest/v3/markdown": "/en/rest/reference/markdown", - "/v3/markdown": "/en/rest/reference/markdown", - "/en/enterprise/3.0/rest/reference/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/en/enterprise/rest/reference/markdown": "/en/enterprise-server@latest/rest/reference/markdown", - "/enterprise/3.0/rest/reference/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/enterprise-server@3.0/rest/reference/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/enterprise/rest/reference/markdown": "/en/enterprise-server@latest/rest/reference/markdown", - "/en/enterprise-server@3.0/v3/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/en/enterprise/3.0/v3/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/en/enterprise/v3/markdown": "/en/enterprise-server@latest/rest/reference/markdown", - "/enterprise/3.0/v3/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/enterprise-server@3.0/v3/markdown": "/en/enterprise-server@3.0/rest/reference/markdown", - "/enterprise/v3/markdown": "/en/enterprise-server@latest/rest/reference/markdown", - "/en/enterprise/2.20/rest/reference/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/enterprise/2.20/rest/reference/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/enterprise-server@2.20/rest/reference/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/en/enterprise-server@2.20/v3/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/en/enterprise/2.20/v3/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/enterprise/2.20/v3/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/enterprise-server@2.20/v3/markdown": "/en/enterprise-server@2.20/rest/reference/markdown", - "/github-ae@latest/rest/reference/markdown": "/en/github-ae@latest/rest/reference/markdown", - "/en/github-ae@latest/v3/markdown": "/en/github-ae@latest/rest/reference/markdown", - "/github-ae@latest/v3/markdown": "/en/github-ae@latest/rest/reference/markdown", - "/en/free-pro-team@latest/rest/reference/meta": "/en/rest/reference/meta", - "/free-pro-team@latest/rest/reference/meta": "/en/rest/reference/meta", - "/rest/reference/meta": "/en/rest/reference/meta", - "/en/v3/meta": "/en/rest/reference/meta", - "/en/free-pro-team@latest/v3/meta": "/en/rest/reference/meta", - "/free-pro-team@latest/v3/meta": "/en/rest/reference/meta", - "/v3/meta": "/en/rest/reference/meta", - "/en/enterprise/3.0/rest/reference/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/en/enterprise/rest/reference/meta": "/en/enterprise-server@latest/rest/reference/meta", - "/enterprise/3.0/rest/reference/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/enterprise-server@3.0/rest/reference/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/enterprise/rest/reference/meta": "/en/enterprise-server@latest/rest/reference/meta", - "/en/enterprise-server@3.0/v3/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/en/enterprise/3.0/v3/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/en/enterprise/v3/meta": "/en/enterprise-server@latest/rest/reference/meta", - "/enterprise/3.0/v3/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/enterprise-server@3.0/v3/meta": "/en/enterprise-server@3.0/rest/reference/meta", - "/enterprise/v3/meta": "/en/enterprise-server@latest/rest/reference/meta", - "/en/enterprise/2.20/rest/reference/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/enterprise/2.20/rest/reference/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/enterprise-server@2.20/rest/reference/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/en/enterprise-server@2.20/v3/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/en/enterprise/2.20/v3/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/enterprise/2.20/v3/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/enterprise-server@2.20/v3/meta": "/en/enterprise-server@2.20/rest/reference/meta", - "/github-ae@latest/rest/reference/meta": "/en/github-ae@latest/rest/reference/meta", - "/en/github-ae@latest/v3/meta": "/en/github-ae@latest/rest/reference/meta", - "/github-ae@latest/v3/meta": "/en/github-ae@latest/rest/reference/meta", - "/en/free-pro-team@latest/rest/reference/migrations": "/en/rest/reference/migrations", - "/free-pro-team@latest/rest/reference/migrations": "/en/rest/reference/migrations", - "/rest/reference/migrations": "/en/rest/reference/migrations", - "/en/v3/migrations": "/en/rest/reference/migrations", - "/en/free-pro-team@latest/v3/migrations": "/en/rest/reference/migrations", - "/free-pro-team@latest/v3/migrations": "/en/rest/reference/migrations", - "/v3/migrations": "/en/rest/reference/migrations", - "/en/v3/migration": "/en/rest/reference/migrations", - "/en/free-pro-team@latest/v3/migration": "/en/rest/reference/migrations", - "/free-pro-team@latest/v3/migration": "/en/rest/reference/migrations", - "/v3/migration": "/en/rest/reference/migrations", - "/en/v3/migration/migrations": "/en/rest/reference/migrations", - "/en/free-pro-team@latest/v3/migration/migrations": "/en/rest/reference/migrations", - "/free-pro-team@latest/v3/migration/migrations": "/en/rest/reference/migrations", - "/v3/migration/migrations": "/en/rest/reference/migrations", - "/en/enterprise/3.0/rest/reference/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/en/enterprise/rest/reference/oauth-authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/enterprise/3.0/rest/reference/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/enterprise-server@3.0/rest/reference/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/enterprise/rest/reference/oauth-authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/en/enterprise-server@3.0/v3/oauth_authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/en/enterprise/3.0/v3/oauth_authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/en/enterprise/v3/oauth_authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/enterprise/3.0/v3/oauth_authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/enterprise-server@3.0/v3/oauth_authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/enterprise/v3/oauth_authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/en/enterprise-server@3.0/v3/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/en/enterprise/3.0/v3/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/en/enterprise/v3/oauth-authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/enterprise/3.0/v3/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/enterprise-server@3.0/v3/oauth-authorizations": "/en/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/enterprise/v3/oauth-authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/en/enterprise/2.20/rest/reference/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/enterprise/2.20/rest/reference/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/enterprise-server@2.20/rest/reference/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/en/enterprise-server@2.20/v3/oauth_authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/en/enterprise/2.20/v3/oauth_authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/enterprise/2.20/v3/oauth_authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/enterprise-server@2.20/v3/oauth_authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/en/enterprise-server@2.20/v3/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/en/enterprise/2.20/v3/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/enterprise/2.20/v3/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/enterprise-server@2.20/v3/oauth-authorizations": "/en/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/en/free-pro-team@latest/rest/reference/orgs": "/en/rest/reference/orgs", - "/free-pro-team@latest/rest/reference/orgs": "/en/rest/reference/orgs", - "/rest/reference/orgs": "/en/rest/reference/orgs", - "/en/v3/orgs": "/en/rest/reference/orgs", - "/en/free-pro-team@latest/v3/orgs": "/en/rest/reference/orgs", - "/free-pro-team@latest/v3/orgs": "/en/rest/reference/orgs", - "/v3/orgs": "/en/rest/reference/orgs", - "/en/enterprise/3.0/rest/reference/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/en/enterprise/rest/reference/orgs": "/en/enterprise-server@latest/rest/reference/orgs", - "/enterprise/3.0/rest/reference/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/enterprise-server@3.0/rest/reference/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/enterprise/rest/reference/orgs": "/en/enterprise-server@latest/rest/reference/orgs", - "/en/enterprise-server@3.0/v3/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/en/enterprise/3.0/v3/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/en/enterprise/v3/orgs": "/en/enterprise-server@latest/rest/reference/orgs", - "/enterprise/3.0/v3/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/enterprise-server@3.0/v3/orgs": "/en/enterprise-server@3.0/rest/reference/orgs", - "/enterprise/v3/orgs": "/en/enterprise-server@latest/rest/reference/orgs", - "/en/enterprise/2.20/rest/reference/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/enterprise/2.20/rest/reference/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/enterprise-server@2.20/rest/reference/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/en/enterprise-server@2.20/v3/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/en/enterprise/2.20/v3/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/enterprise/2.20/v3/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/enterprise-server@2.20/v3/orgs": "/en/enterprise-server@2.20/rest/reference/orgs", - "/github-ae@latest/rest/reference/orgs": "/en/github-ae@latest/rest/reference/orgs", - "/en/github-ae@latest/v3/orgs": "/en/github-ae@latest/rest/reference/orgs", - "/github-ae@latest/v3/orgs": "/en/github-ae@latest/rest/reference/orgs", - "/en/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/en/rest/reference/permissions-required-for-github-apps", - "/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/en/rest/reference/permissions-required-for-github-apps", - "/rest/reference/permissions-required-for-github-apps": "/en/rest/reference/permissions-required-for-github-apps", - "/en/v3/apps/permissions": "/en/rest/reference/permissions-required-for-github-apps", - "/en/free-pro-team@latest/v3/apps/permissions": "/en/rest/reference/permissions-required-for-github-apps", - "/free-pro-team@latest/v3/apps/permissions": "/en/rest/reference/permissions-required-for-github-apps", - "/v3/apps/permissions": "/en/rest/reference/permissions-required-for-github-apps", - "/en/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/en/enterprise/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/enterprise/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/en/enterprise-server@3.0/v3/apps/permissions": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/en/enterprise/3.0/v3/apps/permissions": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/en/enterprise/v3/apps/permissions": "/en/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/enterprise/3.0/v3/apps/permissions": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/enterprise-server@3.0/v3/apps/permissions": "/en/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/enterprise/v3/apps/permissions": "/en/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/en/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/en/enterprise-server@2.20/v3/apps/permissions": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/en/enterprise/2.20/v3/apps/permissions": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/enterprise/2.20/v3/apps/permissions": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/enterprise-server@2.20/v3/apps/permissions": "/en/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/github-ae@latest/rest/reference/permissions-required-for-github-apps": "/en/github-ae@latest/rest/reference/permissions-required-for-github-apps", - "/en/github-ae@latest/v3/apps/permissions": "/en/github-ae@latest/rest/reference/permissions-required-for-github-apps", - "/github-ae@latest/v3/apps/permissions": "/en/github-ae@latest/rest/reference/permissions-required-for-github-apps", - "/en/free-pro-team@latest/rest/reference/projects": "/en/rest/reference/projects", - "/free-pro-team@latest/rest/reference/projects": "/en/rest/reference/projects", - "/rest/reference/projects": "/en/rest/reference/projects", - "/en/v3/projects": "/en/rest/reference/projects", - "/en/free-pro-team@latest/v3/projects": "/en/rest/reference/projects", - "/free-pro-team@latest/v3/projects": "/en/rest/reference/projects", - "/v3/projects": "/en/rest/reference/projects", - "/en/enterprise/3.0/rest/reference/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/en/enterprise/rest/reference/projects": "/en/enterprise-server@latest/rest/reference/projects", - "/enterprise/3.0/rest/reference/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/enterprise-server@3.0/rest/reference/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/enterprise/rest/reference/projects": "/en/enterprise-server@latest/rest/reference/projects", - "/en/enterprise-server@3.0/v3/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/en/enterprise/3.0/v3/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/en/enterprise/v3/projects": "/en/enterprise-server@latest/rest/reference/projects", - "/enterprise/3.0/v3/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/enterprise-server@3.0/v3/projects": "/en/enterprise-server@3.0/rest/reference/projects", - "/enterprise/v3/projects": "/en/enterprise-server@latest/rest/reference/projects", - "/en/enterprise/2.20/rest/reference/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/enterprise/2.20/rest/reference/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/enterprise-server@2.20/rest/reference/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/en/enterprise-server@2.20/v3/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/en/enterprise/2.20/v3/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/enterprise/2.20/v3/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/enterprise-server@2.20/v3/projects": "/en/enterprise-server@2.20/rest/reference/projects", - "/github-ae@latest/rest/reference/projects": "/en/github-ae@latest/rest/reference/projects", - "/en/github-ae@latest/v3/projects": "/en/github-ae@latest/rest/reference/projects", - "/github-ae@latest/v3/projects": "/en/github-ae@latest/rest/reference/projects", - "/en/free-pro-team@latest/rest/reference/pulls": "/en/rest/reference/pulls", - "/free-pro-team@latest/rest/reference/pulls": "/en/rest/reference/pulls", - "/rest/reference/pulls": "/en/rest/reference/pulls", - "/en/v3/pulls": "/en/rest/reference/pulls", - "/en/free-pro-team@latest/v3/pulls": "/en/rest/reference/pulls", - "/free-pro-team@latest/v3/pulls": "/en/rest/reference/pulls", - "/v3/pulls": "/en/rest/reference/pulls", - "/en/enterprise/3.0/rest/reference/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/en/enterprise/rest/reference/pulls": "/en/enterprise-server@latest/rest/reference/pulls", - "/enterprise/3.0/rest/reference/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/enterprise-server@3.0/rest/reference/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/enterprise/rest/reference/pulls": "/en/enterprise-server@latest/rest/reference/pulls", - "/en/enterprise-server@3.0/v3/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/en/enterprise/3.0/v3/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/en/enterprise/v3/pulls": "/en/enterprise-server@latest/rest/reference/pulls", - "/enterprise/3.0/v3/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/enterprise-server@3.0/v3/pulls": "/en/enterprise-server@3.0/rest/reference/pulls", - "/enterprise/v3/pulls": "/en/enterprise-server@latest/rest/reference/pulls", - "/en/enterprise/2.20/rest/reference/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/enterprise/2.20/rest/reference/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/enterprise-server@2.20/rest/reference/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/en/enterprise-server@2.20/v3/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/en/enterprise/2.20/v3/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/enterprise/2.20/v3/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/enterprise-server@2.20/v3/pulls": "/en/enterprise-server@2.20/rest/reference/pulls", - "/github-ae@latest/rest/reference/pulls": "/en/github-ae@latest/rest/reference/pulls", - "/en/github-ae@latest/v3/pulls": "/en/github-ae@latest/rest/reference/pulls", - "/github-ae@latest/v3/pulls": "/en/github-ae@latest/rest/reference/pulls", - "/en/free-pro-team@latest/rest/reference/rate-limit": "/en/rest/reference/rate-limit", - "/free-pro-team@latest/rest/reference/rate-limit": "/en/rest/reference/rate-limit", - "/rest/reference/rate-limit": "/en/rest/reference/rate-limit", - "/en/v3/rate_limit": "/en/rest/reference/rate-limit", - "/en/free-pro-team@latest/v3/rate_limit": "/en/rest/reference/rate-limit", - "/free-pro-team@latest/v3/rate_limit": "/en/rest/reference/rate-limit", - "/v3/rate_limit": "/en/rest/reference/rate-limit", - "/en/v3/rate-limit": "/en/rest/reference/rate-limit", - "/en/free-pro-team@latest/v3/rate-limit": "/en/rest/reference/rate-limit", - "/free-pro-team@latest/v3/rate-limit": "/en/rest/reference/rate-limit", - "/v3/rate-limit": "/en/rest/reference/rate-limit", - "/en/enterprise/3.0/rest/reference/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/en/enterprise/rest/reference/rate-limit": "/en/enterprise-server@latest/rest/reference/rate-limit", - "/enterprise/3.0/rest/reference/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/enterprise-server@3.0/rest/reference/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/enterprise/rest/reference/rate-limit": "/en/enterprise-server@latest/rest/reference/rate-limit", - "/en/enterprise-server@3.0/v3/rate_limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/en/enterprise/3.0/v3/rate_limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/en/enterprise/v3/rate_limit": "/en/enterprise-server@latest/rest/reference/rate-limit", - "/enterprise/3.0/v3/rate_limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/enterprise-server@3.0/v3/rate_limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/enterprise/v3/rate_limit": "/en/enterprise-server@latest/rest/reference/rate-limit", - "/en/enterprise-server@3.0/v3/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/en/enterprise/3.0/v3/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/en/enterprise/v3/rate-limit": "/en/enterprise-server@latest/rest/reference/rate-limit", - "/enterprise/3.0/v3/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/enterprise-server@3.0/v3/rate-limit": "/en/enterprise-server@3.0/rest/reference/rate-limit", - "/enterprise/v3/rate-limit": "/en/enterprise-server@latest/rest/reference/rate-limit", - "/en/enterprise/2.20/rest/reference/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/enterprise/2.20/rest/reference/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/enterprise-server@2.20/rest/reference/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/en/enterprise-server@2.20/v3/rate_limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/en/enterprise/2.20/v3/rate_limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/enterprise/2.20/v3/rate_limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/enterprise-server@2.20/v3/rate_limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/en/enterprise-server@2.20/v3/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/en/enterprise/2.20/v3/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/enterprise/2.20/v3/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/enterprise-server@2.20/v3/rate-limit": "/en/enterprise-server@2.20/rest/reference/rate-limit", - "/github-ae@latest/rest/reference/rate-limit": "/en/github-ae@latest/rest/reference/rate-limit", - "/en/github-ae@latest/v3/rate_limit": "/en/github-ae@latest/rest/reference/rate-limit", - "/github-ae@latest/v3/rate_limit": "/en/github-ae@latest/rest/reference/rate-limit", - "/en/github-ae@latest/v3/rate-limit": "/en/github-ae@latest/rest/reference/rate-limit", - "/github-ae@latest/v3/rate-limit": "/en/github-ae@latest/rest/reference/rate-limit", - "/en/free-pro-team@latest/rest/reference/reactions": "/en/rest/reference/reactions", - "/free-pro-team@latest/rest/reference/reactions": "/en/rest/reference/reactions", - "/rest/reference/reactions": "/en/rest/reference/reactions", - "/en/v3/reactions": "/en/rest/reference/reactions", - "/en/free-pro-team@latest/v3/reactions": "/en/rest/reference/reactions", - "/free-pro-team@latest/v3/reactions": "/en/rest/reference/reactions", - "/v3/reactions": "/en/rest/reference/reactions", - "/en/enterprise/3.0/rest/reference/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/en/enterprise/rest/reference/reactions": "/en/enterprise-server@latest/rest/reference/reactions", - "/enterprise/3.0/rest/reference/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/enterprise-server@3.0/rest/reference/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/enterprise/rest/reference/reactions": "/en/enterprise-server@latest/rest/reference/reactions", - "/en/enterprise-server@3.0/v3/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/en/enterprise/3.0/v3/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/en/enterprise/v3/reactions": "/en/enterprise-server@latest/rest/reference/reactions", - "/enterprise/3.0/v3/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/enterprise-server@3.0/v3/reactions": "/en/enterprise-server@3.0/rest/reference/reactions", - "/enterprise/v3/reactions": "/en/enterprise-server@latest/rest/reference/reactions", - "/en/enterprise/2.20/rest/reference/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/enterprise/2.20/rest/reference/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/enterprise-server@2.20/rest/reference/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/en/enterprise-server@2.20/v3/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/en/enterprise/2.20/v3/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/enterprise/2.20/v3/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/enterprise-server@2.20/v3/reactions": "/en/enterprise-server@2.20/rest/reference/reactions", - "/github-ae@latest/rest/reference/reactions": "/en/github-ae@latest/rest/reference/reactions", - "/en/github-ae@latest/v3/reactions": "/en/github-ae@latest/rest/reference/reactions", - "/github-ae@latest/v3/reactions": "/en/github-ae@latest/rest/reference/reactions", - "/en/free-pro-team@latest/rest/reference/repos": "/en/rest/reference/repos", - "/free-pro-team@latest/rest/reference/repos": "/en/rest/reference/repos", - "/rest/reference/repos": "/en/rest/reference/repos", - "/en/v3/repos": "/en/rest/reference/repos", - "/en/free-pro-team@latest/v3/repos": "/en/rest/reference/repos", - "/free-pro-team@latest/v3/repos": "/en/rest/reference/repos", - "/v3/repos": "/en/rest/reference/repos", - "/en/enterprise/3.0/rest/reference/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/en/enterprise/rest/reference/repos": "/en/enterprise-server@latest/rest/reference/repos", - "/enterprise/3.0/rest/reference/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/enterprise-server@3.0/rest/reference/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/enterprise/rest/reference/repos": "/en/enterprise-server@latest/rest/reference/repos", - "/en/enterprise-server@3.0/v3/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/en/enterprise/3.0/v3/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/en/enterprise/v3/repos": "/en/enterprise-server@latest/rest/reference/repos", - "/enterprise/3.0/v3/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/enterprise-server@3.0/v3/repos": "/en/enterprise-server@3.0/rest/reference/repos", - "/enterprise/v3/repos": "/en/enterprise-server@latest/rest/reference/repos", - "/en/enterprise/2.20/rest/reference/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/enterprise/2.20/rest/reference/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/enterprise-server@2.20/rest/reference/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/en/enterprise-server@2.20/v3/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/en/enterprise/2.20/v3/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/enterprise/2.20/v3/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/enterprise-server@2.20/v3/repos": "/en/enterprise-server@2.20/rest/reference/repos", - "/github-ae@latest/rest/reference/repos": "/en/github-ae@latest/rest/reference/repos", - "/en/github-ae@latest/v3/repos": "/en/github-ae@latest/rest/reference/repos", - "/github-ae@latest/v3/repos": "/en/github-ae@latest/rest/reference/repos", - "/en/free-pro-team@latest/rest/reference/scim": "/en/rest/reference/scim", - "/free-pro-team@latest/rest/reference/scim": "/en/rest/reference/scim", - "/rest/reference/scim": "/en/rest/reference/scim", - "/en/v3/scim": "/en/rest/reference/scim", - "/en/free-pro-team@latest/v3/scim": "/en/rest/reference/scim", - "/free-pro-team@latest/v3/scim": "/en/rest/reference/scim", - "/v3/scim": "/en/rest/reference/scim", - "/en/free-pro-team@latest/rest/reference/search": "/en/rest/reference/search", - "/free-pro-team@latest/rest/reference/search": "/en/rest/reference/search", - "/rest/reference/search": "/en/rest/reference/search", - "/en/v3/search": "/en/rest/reference/search", - "/en/free-pro-team@latest/v3/search": "/en/rest/reference/search", - "/free-pro-team@latest/v3/search": "/en/rest/reference/search", - "/v3/search": "/en/rest/reference/search", - "/en/enterprise/3.0/rest/reference/search": "/en/enterprise-server@3.0/rest/reference/search", - "/en/enterprise/rest/reference/search": "/en/enterprise-server@latest/rest/reference/search", - "/enterprise/3.0/rest/reference/search": "/en/enterprise-server@3.0/rest/reference/search", - "/enterprise-server@3.0/rest/reference/search": "/en/enterprise-server@3.0/rest/reference/search", - "/enterprise/rest/reference/search": "/en/enterprise-server@latest/rest/reference/search", - "/en/enterprise-server@3.0/v3/search": "/en/enterprise-server@3.0/rest/reference/search", - "/en/enterprise/3.0/v3/search": "/en/enterprise-server@3.0/rest/reference/search", - "/en/enterprise/v3/search": "/en/enterprise-server@latest/rest/reference/search", - "/enterprise/3.0/v3/search": "/en/enterprise-server@3.0/rest/reference/search", - "/enterprise-server@3.0/v3/search": "/en/enterprise-server@3.0/rest/reference/search", - "/enterprise/v3/search": "/en/enterprise-server@latest/rest/reference/search", - "/en/enterprise/2.20/rest/reference/search": "/en/enterprise-server@2.20/rest/reference/search", - "/enterprise/2.20/rest/reference/search": "/en/enterprise-server@2.20/rest/reference/search", - "/enterprise-server@2.20/rest/reference/search": "/en/enterprise-server@2.20/rest/reference/search", - "/en/enterprise-server@2.20/v3/search": "/en/enterprise-server@2.20/rest/reference/search", - "/en/enterprise/2.20/v3/search": "/en/enterprise-server@2.20/rest/reference/search", - "/enterprise/2.20/v3/search": "/en/enterprise-server@2.20/rest/reference/search", - "/enterprise-server@2.20/v3/search": "/en/enterprise-server@2.20/rest/reference/search", - "/github-ae@latest/rest/reference/search": "/en/github-ae@latest/rest/reference/search", - "/en/github-ae@latest/v3/search": "/en/github-ae@latest/rest/reference/search", - "/github-ae@latest/v3/search": "/en/github-ae@latest/rest/reference/search", - "/en/free-pro-team@latest/rest/reference/secret-scanning": "/en/rest/reference/secret-scanning", - "/free-pro-team@latest/rest/reference/secret-scanning": "/en/rest/reference/secret-scanning", - "/rest/reference/secret-scanning": "/en/rest/reference/secret-scanning", - "/en/free-pro-team@latest/rest/reference/teams": "/en/rest/reference/teams", - "/free-pro-team@latest/rest/reference/teams": "/en/rest/reference/teams", - "/rest/reference/teams": "/en/rest/reference/teams", - "/en/v3/teams": "/en/rest/reference/teams", - "/en/free-pro-team@latest/v3/teams": "/en/rest/reference/teams", - "/free-pro-team@latest/v3/teams": "/en/rest/reference/teams", - "/v3/teams": "/en/rest/reference/teams", - "/en/enterprise/3.0/rest/reference/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/en/enterprise/rest/reference/teams": "/en/enterprise-server@latest/rest/reference/teams", - "/enterprise/3.0/rest/reference/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/enterprise-server@3.0/rest/reference/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/enterprise/rest/reference/teams": "/en/enterprise-server@latest/rest/reference/teams", - "/en/enterprise-server@3.0/v3/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/en/enterprise/3.0/v3/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/en/enterprise/v3/teams": "/en/enterprise-server@latest/rest/reference/teams", - "/enterprise/3.0/v3/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/enterprise-server@3.0/v3/teams": "/en/enterprise-server@3.0/rest/reference/teams", - "/enterprise/v3/teams": "/en/enterprise-server@latest/rest/reference/teams", - "/en/enterprise/2.20/rest/reference/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/enterprise/2.20/rest/reference/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/enterprise-server@2.20/rest/reference/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/en/enterprise-server@2.20/v3/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/en/enterprise/2.20/v3/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/enterprise/2.20/v3/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/enterprise-server@2.20/v3/teams": "/en/enterprise-server@2.20/rest/reference/teams", - "/github-ae@latest/rest/reference/teams": "/en/github-ae@latest/rest/reference/teams", - "/en/github-ae@latest/v3/teams": "/en/github-ae@latest/rest/reference/teams", - "/github-ae@latest/v3/teams": "/en/github-ae@latest/rest/reference/teams", - "/en/free-pro-team@latest/rest/reference/users": "/en/rest/reference/users", - "/free-pro-team@latest/rest/reference/users": "/en/rest/reference/users", - "/rest/reference/users": "/en/rest/reference/users", - "/en/v3/users": "/en/rest/reference/users", - "/en/free-pro-team@latest/v3/users": "/en/rest/reference/users", - "/free-pro-team@latest/v3/users": "/en/rest/reference/users", - "/v3/users": "/en/rest/reference/users", - "/en/enterprise/3.0/rest/reference/users": "/en/enterprise-server@3.0/rest/reference/users", - "/en/enterprise/rest/reference/users": "/en/enterprise-server@latest/rest/reference/users", - "/enterprise/3.0/rest/reference/users": "/en/enterprise-server@3.0/rest/reference/users", - "/enterprise-server@3.0/rest/reference/users": "/en/enterprise-server@3.0/rest/reference/users", - "/enterprise/rest/reference/users": "/en/enterprise-server@latest/rest/reference/users", - "/en/enterprise-server@3.0/v3/users": "/en/enterprise-server@3.0/rest/reference/users", - "/en/enterprise/3.0/v3/users": "/en/enterprise-server@3.0/rest/reference/users", - "/en/enterprise/v3/users": "/en/enterprise-server@latest/rest/reference/users", - "/enterprise/3.0/v3/users": "/en/enterprise-server@3.0/rest/reference/users", - "/enterprise-server@3.0/v3/users": "/en/enterprise-server@3.0/rest/reference/users", - "/enterprise/v3/users": "/en/enterprise-server@latest/rest/reference/users", - "/en/enterprise/2.20/rest/reference/users": "/en/enterprise-server@2.20/rest/reference/users", - "/enterprise/2.20/rest/reference/users": "/en/enterprise-server@2.20/rest/reference/users", - "/enterprise-server@2.20/rest/reference/users": "/en/enterprise-server@2.20/rest/reference/users", - "/en/enterprise-server@2.20/v3/users": "/en/enterprise-server@2.20/rest/reference/users", - "/en/enterprise/2.20/v3/users": "/en/enterprise-server@2.20/rest/reference/users", - "/enterprise/2.20/v3/users": "/en/enterprise-server@2.20/rest/reference/users", - "/enterprise-server@2.20/v3/users": "/en/enterprise-server@2.20/rest/reference/users", - "/github-ae@latest/rest/reference/users": "/en/github-ae@latest/rest/reference/users", - "/en/github-ae@latest/v3/users": "/en/github-ae@latest/rest/reference/users", - "/github-ae@latest/v3/users": "/en/github-ae@latest/rest/reference/users", - "/cn/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/3.0/admin/articles/restoring-github-enterprise": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/admin/articles/restoring-github-enterprise": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/admin/articles/restoring-github-enterprise": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/3.0/admin/articles/restoring-enterprise-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/admin/articles/restoring-enterprise-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/admin/articles/restoring-enterprise-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise-server@3.0/admin/articles/restoring-repository-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/3.0/admin/articles/restoring-repository-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/admin/articles/restoring-repository-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/admin/articles/restoring-repository-data": "/cn/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/cn/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/2.20/admin/articles/restoring-github-enterprise": "/cn/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/cn/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/2.20/admin/articles/restoring-enterprise-data": "/cn/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise-server@2.20/admin/articles/restoring-repository-data": "/cn/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise/2.20/admin/articles/restoring-repository-data": "/cn/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/cn/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/cn/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/cn/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/cn/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/cn/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/cn/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/cn/github-ae@latest/admin/articles/restricting-ssh-access-to-specific-hosts": "/cn/github-ae@latest/admin/configuration/configuring-your-enterprise", - "/cn/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/github-ae@latest/admin/user-management/restricting-repository-creation-in-your-instance": "/cn/github-ae@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/cn/v3/oauth": "/cn/developers/apps/authorizing-oauth-apps", - "/cn/free-pro-team@latest/v3/oauth": "/cn/developers/apps/authorizing-oauth-apps", - "/cn/enterprise-server@3.0/v3/oauth": "/cn/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/cn/enterprise/3.0/v3/oauth": "/cn/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/cn/enterprise/v3/oauth": "/cn/enterprise-server@latest/developers/apps/authorizing-oauth-apps", - "/cn/enterprise-server@2.20/v3/oauth": "/cn/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/cn/enterprise/2.20/v3/oauth": "/cn/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/cn/github-ae@latest/v3/oauth": "/cn/github-ae@latest/developers/apps/authorizing-oauth-apps", - "/cn/v3/integrations": "/cn/developers/apps", - "/cn/free-pro-team@latest/v3/integrations": "/cn/developers/apps", - "/cn/enterprise-server@3.0/v3/integrations": "/cn/enterprise-server@3.0/developers/apps", - "/cn/enterprise/3.0/v3/integrations": "/cn/enterprise-server@3.0/developers/apps", - "/cn/enterprise/v3/integrations": "/cn/enterprise-server@latest/developers/apps", - "/cn/enterprise-server@2.20/v3/integrations": "/cn/enterprise-server@2.20/developers/apps", - "/cn/enterprise/2.20/v3/integrations": "/cn/enterprise-server@2.20/developers/apps", - "/cn/github-ae@latest/v3/integrations": "/cn/github-ae@latest/developers/apps", - "/cn/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/cn/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/cn/v3/versions": "/cn/developers/overview/about-githubs-apis", - "/cn/free-pro-team@latest/v3/versions": "/cn/developers/overview/about-githubs-apis", - "/cn/enterprise-server@3.0/v3/versions": "/cn/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/cn/enterprise/3.0/v3/versions": "/cn/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/cn/enterprise/v3/versions": "/cn/enterprise-server@latest/developers/overview/about-githubs-apis", - "/cn/enterprise-server@2.20/v3/versions": "/cn/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/cn/enterprise/2.20/v3/versions": "/cn/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/cn/github-ae@latest/v3/versions": "/cn/github-ae@latest/developers/overview/about-githubs-apis", - "/cn/v3/guides/managing-deploy-keys": "/cn/developers/overview/managing-deploy-keys", - "/cn/free-pro-team@latest/v3/guides/managing-deploy-keys": "/cn/developers/overview/managing-deploy-keys", - "/cn/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/cn/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/cn/enterprise/3.0/v3/guides/managing-deploy-keys": "/cn/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/cn/enterprise/v3/guides/managing-deploy-keys": "/cn/enterprise-server@latest/developers/overview/managing-deploy-keys", - "/cn/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/cn/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/cn/enterprise/2.20/v3/guides/managing-deploy-keys": "/cn/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/cn/github-ae@latest/v3/guides/managing-deploy-keys": "/cn/github-ae@latest/developers/overview/managing-deploy-keys", - "/cn/v3/guides/automating-deployments-to-integrators": "/cn/developers/overview/replacing-github-services", - "/cn/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/cn/developers/overview/replacing-github-services", - "/cn/v3/guides/replacing-github-services": "/cn/developers/overview/replacing-github-services", - "/cn/free-pro-team@latest/v3/guides/replacing-github-services": "/cn/developers/overview/replacing-github-services", - "/cn/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/cn/enterprise-server@3.0/developers/overview/replacing-github-services", - "/cn/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/cn/enterprise-server@3.0/developers/overview/replacing-github-services", - "/cn/enterprise/v3/guides/automating-deployments-to-integrators": "/cn/enterprise-server@latest/developers/overview/replacing-github-services", - "/cn/enterprise-server@3.0/v3/guides/replacing-github-services": "/cn/enterprise-server@3.0/developers/overview/replacing-github-services", - "/cn/enterprise/3.0/v3/guides/replacing-github-services": "/cn/enterprise-server@3.0/developers/overview/replacing-github-services", - "/cn/enterprise/v3/guides/replacing-github-services": "/cn/enterprise-server@latest/developers/overview/replacing-github-services", - "/cn/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/cn/enterprise-server@2.20/developers/overview/replacing-github-services", - "/cn/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/cn/enterprise-server@2.20/developers/overview/replacing-github-services", - "/cn/enterprise-server@2.20/v3/guides/replacing-github-services": "/cn/enterprise-server@2.20/developers/overview/replacing-github-services", - "/cn/enterprise/2.20/v3/guides/replacing-github-services": "/cn/enterprise-server@2.20/developers/overview/replacing-github-services", - "/cn/v3/guides/using-ssh-agent-forwarding": "/cn/developers/overview/using-ssh-agent-forwarding", - "/cn/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/cn/developers/overview/using-ssh-agent-forwarding", - "/cn/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/cn/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/cn/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/cn/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/cn/enterprise/v3/guides/using-ssh-agent-forwarding": "/cn/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", - "/cn/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/cn/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/cn/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/cn/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/cn/github-ae@latest/v3/guides/using-ssh-agent-forwarding": "/cn/github-ae@latest/developers/overview/using-ssh-agent-forwarding", - "/cn/v3/activity/event_types": "/cn/developers/webhooks-and-events/github-event-types", - "/cn/free-pro-team@latest/v3/activity/event_types": "/cn/developers/webhooks-and-events/github-event-types", - "/cn/enterprise-server@3.0/v3/activity/event_types": "/cn/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/cn/enterprise/3.0/v3/activity/event_types": "/cn/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/cn/enterprise/v3/activity/event_types": "/cn/enterprise-server@latest/developers/webhooks-and-events/github-event-types", - "/cn/enterprise-server@2.20/v3/activity/event_types": "/cn/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/cn/enterprise/2.20/v3/activity/event_types": "/cn/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/cn/github-ae@latest/v3/activity/event_types": "/cn/github-ae@latest/developers/webhooks-and-events/github-event-types", - "/cn/v3/issues/issue-event-types": "/cn/developers/webhooks-and-events/issue-event-types", - "/cn/free-pro-team@latest/v3/issues/issue-event-types": "/cn/developers/webhooks-and-events/issue-event-types", - "/cn/enterprise-server@3.0/v3/issues/issue-event-types": "/cn/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/cn/enterprise/3.0/v3/issues/issue-event-types": "/cn/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/cn/enterprise/v3/issues/issue-event-types": "/cn/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", - "/cn/enterprise-server@2.20/v3/issues/issue-event-types": "/cn/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/cn/enterprise/2.20/v3/issues/issue-event-types": "/cn/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/cn/github-ae@latest/v3/issues/issue-event-types": "/cn/github-ae@latest/developers/webhooks-and-events/issue-event-types", - "/cn/v3/activity/events/types": "/cn/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/free-pro-team@latest/v3/activity/events/types": "/cn/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/enterprise-server@3.0/v3/activity/events/types": "/cn/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/enterprise/3.0/v3/activity/events/types": "/cn/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/enterprise/v3/activity/events/types": "/cn/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/enterprise-server@2.20/v3/activity/events/types": "/cn/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/enterprise/2.20/v3/activity/events/types": "/cn/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/github-ae@latest/v3/activity/events/types": "/cn/github-ae@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/cn/articles/restoring-branches-in-a-pull-request": "/cn/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/cn/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/cn/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/cn/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/articles/restoring-branches-in-a-pull-request": "/cn/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/cn/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/cn/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/github-ae@latest/articles/restoring-branches-in-a-pull-request": "/cn/github-ae@latest/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/cn/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/cn/github/administering-a-repository/restoring-a-deleted-repository", - "/cn/articles/restoring-a-deleted-repository": "/cn/github/administering-a-repository/restoring-a-deleted-repository", - "/cn/free-pro-team@latest/articles/restoring-a-deleted-repository": "/cn/github/administering-a-repository/restoring-a-deleted-repository", - "/cn/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/cn/articles/restricting-access-to-your-organization-s-data": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/cn/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/cn/articles/restricting-access-to-your-organizations-data": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/cn/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/cn/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/cn/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/cn/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/cn/articles/restricting-email-notifications-to-an-approved-domain": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/cn/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/cn/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/articles/restricting-repository-creation-in-your-organization": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/github-ae@latest/articles/restricting-repository-creation-in-your-organization": "/cn/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/cn/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/github-ae@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/cn/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/cn/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/github-ae@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/cn/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/cn/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/cn/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", - "/cn/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/cn/graphql/guides/forming-calls-with-graphql", - "/cn/v4/guides/forming-calls": "/cn/graphql/guides/forming-calls-with-graphql", - "/cn/free-pro-team@latest/v4/guides/forming-calls": "/cn/graphql/guides/forming-calls-with-graphql", - "/cn/graphql/guides/forming-calls": "/cn/graphql/guides/forming-calls-with-graphql", - "/cn/free-pro-team@latest/graphql/guides/forming-calls": "/cn/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/cn/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/graphql/guides/forming-calls-with-graphql": "/cn/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise-server@3.0/v4/guides/forming-calls": "/cn/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/3.0/v4/guides/forming-calls": "/cn/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/v4/guides/forming-calls": "/cn/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise-server@3.0/graphql/guides/forming-calls": "/cn/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/3.0/graphql/guides/forming-calls": "/cn/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/graphql/guides/forming-calls": "/cn/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/cn/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise-server@2.20/v4/guides/forming-calls": "/cn/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/2.20/v4/guides/forming-calls": "/cn/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise-server@2.20/graphql/guides/forming-calls": "/cn/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/cn/enterprise/2.20/graphql/guides/forming-calls": "/cn/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/cn/github-ae@latest/v4/guides/forming-calls": "/cn/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/cn/github-ae@latest/graphql/guides/forming-calls": "/cn/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/cn/free-pro-team@latest/graphql/guides": "/cn/graphql/guides", - "/cn/v4/guides": "/cn/graphql/guides", - "/cn/free-pro-team@latest/v4/guides": "/cn/graphql/guides", - "/cn/enterprise/3.0/graphql/guides": "/cn/enterprise-server@3.0/graphql/guides", - "/cn/enterprise/graphql/guides": "/cn/enterprise-server@latest/graphql/guides", - "/cn/enterprise-server@3.0/v4/guides": "/cn/enterprise-server@3.0/graphql/guides", - "/cn/enterprise/3.0/v4/guides": "/cn/enterprise-server@3.0/graphql/guides", - "/cn/enterprise/v4/guides": "/cn/enterprise-server@latest/graphql/guides", - "/cn/enterprise/2.20/graphql/guides": "/cn/enterprise-server@2.20/graphql/guides", - "/cn/enterprise-server@2.20/v4/guides": "/cn/enterprise-server@2.20/graphql/guides", - "/cn/enterprise/2.20/v4/guides": "/cn/enterprise-server@2.20/graphql/guides", - "/cn/github-ae@latest/v4/guides": "/cn/github-ae@latest/graphql/guides", - "/cn/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/cn/graphql/guides/introduction-to-graphql", - "/cn/v4/guides/intro-to-graphql": "/cn/graphql/guides/introduction-to-graphql", - "/cn/free-pro-team@latest/v4/guides/intro-to-graphql": "/cn/graphql/guides/introduction-to-graphql", - "/cn/graphql/guides/intro-to-graphql": "/cn/graphql/guides/introduction-to-graphql", - "/cn/free-pro-team@latest/graphql/guides/intro-to-graphql": "/cn/graphql/guides/introduction-to-graphql", - "/cn/enterprise/3.0/graphql/guides/introduction-to-graphql": "/cn/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/cn/enterprise/graphql/guides/introduction-to-graphql": "/cn/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/cn/enterprise-server@3.0/v4/guides/intro-to-graphql": "/cn/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/cn/enterprise/3.0/v4/guides/intro-to-graphql": "/cn/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/cn/enterprise/v4/guides/intro-to-graphql": "/cn/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/cn/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/cn/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/cn/enterprise/3.0/graphql/guides/intro-to-graphql": "/cn/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/cn/enterprise/graphql/guides/intro-to-graphql": "/cn/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/cn/enterprise/2.20/graphql/guides/introduction-to-graphql": "/cn/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/cn/enterprise-server@2.20/v4/guides/intro-to-graphql": "/cn/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/cn/enterprise/2.20/v4/guides/intro-to-graphql": "/cn/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/cn/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/cn/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/cn/enterprise/2.20/graphql/guides/intro-to-graphql": "/cn/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/cn/github-ae@latest/v4/guides/intro-to-graphql": "/cn/github-ae@latest/graphql/guides/introduction-to-graphql", - "/cn/github-ae@latest/graphql/guides/intro-to-graphql": "/cn/github-ae@latest/graphql/guides/introduction-to-graphql", - "/cn/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/cn/graphql/guides/managing-enterprise-accounts", - "/cn/v4/guides/managing-enterprise-accounts": "/cn/graphql/guides/managing-enterprise-accounts", - "/cn/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/cn/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/cn/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise/graphql/guides/managing-enterprise-accounts": "/cn/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/cn/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/cn/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise/v4/guides/managing-enterprise-accounts": "/cn/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/cn/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/cn/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/cn/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/cn/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/cn/github-ae@latest/v4/guides/managing-enterprise-accounts": "/cn/github-ae@latest/graphql/guides/managing-enterprise-accounts", - "/cn/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/cn/graphql/guides/migrating-from-rest-to-graphql", - "/cn/v4/guides/migrating-from-rest": "/cn/graphql/guides/migrating-from-rest-to-graphql", - "/cn/free-pro-team@latest/v4/guides/migrating-from-rest": "/cn/graphql/guides/migrating-from-rest-to-graphql", - "/cn/graphql/guides/migrating-from-rest": "/cn/graphql/guides/migrating-from-rest-to-graphql", - "/cn/free-pro-team@latest/graphql/guides/migrating-from-rest": "/cn/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/cn/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/cn/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise-server@3.0/v4/guides/migrating-from-rest": "/cn/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/3.0/v4/guides/migrating-from-rest": "/cn/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/v4/guides/migrating-from-rest": "/cn/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/cn/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/3.0/graphql/guides/migrating-from-rest": "/cn/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/graphql/guides/migrating-from-rest": "/cn/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/cn/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise-server@2.20/v4/guides/migrating-from-rest": "/cn/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/2.20/v4/guides/migrating-from-rest": "/cn/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/cn/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/cn/enterprise/2.20/graphql/guides/migrating-from-rest": "/cn/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/cn/github-ae@latest/v4/guides/migrating-from-rest": "/cn/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/cn/github-ae@latest/graphql/guides/migrating-from-rest": "/cn/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/cn/free-pro-team@latest/graphql/guides/using-global-node-ids": "/cn/graphql/guides/using-global-node-ids", - "/cn/v4/guides/using-global-node-ids": "/cn/graphql/guides/using-global-node-ids", - "/cn/free-pro-team@latest/v4/guides/using-global-node-ids": "/cn/graphql/guides/using-global-node-ids", - "/cn/enterprise/3.0/graphql/guides/using-global-node-ids": "/cn/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/cn/enterprise/graphql/guides/using-global-node-ids": "/cn/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/cn/enterprise-server@3.0/v4/guides/using-global-node-ids": "/cn/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/cn/enterprise/3.0/v4/guides/using-global-node-ids": "/cn/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/cn/enterprise/v4/guides/using-global-node-ids": "/cn/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/cn/enterprise/2.20/graphql/guides/using-global-node-ids": "/cn/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/cn/enterprise-server@2.20/v4/guides/using-global-node-ids": "/cn/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/cn/enterprise/2.20/v4/guides/using-global-node-ids": "/cn/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/cn/github-ae@latest/v4/guides/using-global-node-ids": "/cn/github-ae@latest/graphql/guides/using-global-node-ids", - "/cn/free-pro-team@latest/graphql/guides/using-the-explorer": "/cn/graphql/guides/using-the-explorer", - "/cn/v4/guides/using-the-explorer": "/cn/graphql/guides/using-the-explorer", - "/cn/free-pro-team@latest/v4/guides/using-the-explorer": "/cn/graphql/guides/using-the-explorer", - "/cn/enterprise/3.0/graphql/guides/using-the-explorer": "/cn/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/cn/enterprise/graphql/guides/using-the-explorer": "/cn/enterprise-server@latest/graphql/guides/using-the-explorer", - "/cn/enterprise-server@3.0/v4/guides/using-the-explorer": "/cn/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/cn/enterprise/3.0/v4/guides/using-the-explorer": "/cn/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/cn/enterprise/v4/guides/using-the-explorer": "/cn/enterprise-server@latest/graphql/guides/using-the-explorer", - "/cn/enterprise/2.20/graphql/guides/using-the-explorer": "/cn/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/cn/enterprise-server@2.20/v4/guides/using-the-explorer": "/cn/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/cn/enterprise/2.20/v4/guides/using-the-explorer": "/cn/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/cn/github-ae@latest/v4/guides/using-the-explorer": "/cn/github-ae@latest/graphql/guides/using-the-explorer", - "/cn/free-pro-team@latest/graphql": "/cn/graphql", - "/cn/v4": "/cn/graphql", - "/cn/free-pro-team@latest/v4": "/cn/graphql", - "/cn/enterprise/3.0/graphql": "/cn/enterprise-server@3.0/graphql", - "/cn/enterprise/graphql": "/cn/enterprise-server@latest/graphql", - "/cn/enterprise-server@3.0/v4": "/cn/enterprise-server@3.0/graphql", - "/cn/enterprise/3.0/v4": "/cn/enterprise-server@3.0/graphql", - "/cn/enterprise/v4": "/cn/enterprise-server@latest/graphql", - "/cn/enterprise/2.20/graphql": "/cn/enterprise-server@2.20/graphql", - "/cn/enterprise-server@2.20/v4": "/cn/enterprise-server@2.20/graphql", - "/cn/enterprise/2.20/v4": "/cn/enterprise-server@2.20/graphql", - "/cn/github-ae@latest/v4": "/cn/github-ae@latest/graphql", - "/cn/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/cn/graphql/overview/about-the-graphql-api", - "/cn/enterprise/3.0/graphql/overview/about-the-graphql-api": "/cn/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/cn/enterprise/graphql/overview/about-the-graphql-api": "/cn/enterprise-server@latest/graphql/overview/about-the-graphql-api", - "/cn/enterprise/2.20/graphql/overview/about-the-graphql-api": "/cn/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/cn/free-pro-team@latest/graphql/overview/breaking-changes": "/cn/graphql/overview/breaking-changes", - "/cn/v4/breaking_changes": "/cn/graphql/overview/breaking-changes", - "/cn/free-pro-team@latest/v4/breaking_changes": "/cn/graphql/overview/breaking-changes", - "/cn/enterprise/3.0/graphql/overview/breaking-changes": "/cn/enterprise-server@3.0/graphql/overview/breaking-changes", - "/cn/enterprise/graphql/overview/breaking-changes": "/cn/enterprise-server@latest/graphql/overview/breaking-changes", - "/cn/enterprise-server@3.0/v4/breaking_changes": "/cn/enterprise-server@3.0/graphql/overview/breaking-changes", - "/cn/enterprise/3.0/v4/breaking_changes": "/cn/enterprise-server@3.0/graphql/overview/breaking-changes", - "/cn/enterprise/v4/breaking_changes": "/cn/enterprise-server@latest/graphql/overview/breaking-changes", - "/cn/enterprise/2.20/graphql/overview/breaking-changes": "/cn/enterprise-server@2.20/graphql/overview/breaking-changes", - "/cn/enterprise-server@2.20/v4/breaking_changes": "/cn/enterprise-server@2.20/graphql/overview/breaking-changes", - "/cn/enterprise/2.20/v4/breaking_changes": "/cn/enterprise-server@2.20/graphql/overview/breaking-changes", - "/cn/github-ae@latest/v4/breaking_changes": "/cn/github-ae@latest/graphql/overview/breaking-changes", - "/cn/free-pro-team@latest/graphql/overview/changelog": "/cn/graphql/overview/changelog", - "/cn/v4/changelog": "/cn/graphql/overview/changelog", - "/cn/free-pro-team@latest/v4/changelog": "/cn/graphql/overview/changelog", - "/cn/enterprise/3.0/graphql/overview/changelog": "/cn/enterprise-server@3.0/graphql/overview/changelog", - "/cn/enterprise/graphql/overview/changelog": "/cn/enterprise-server@latest/graphql/overview/changelog", - "/cn/enterprise-server@3.0/v4/changelog": "/cn/enterprise-server@3.0/graphql/overview/changelog", - "/cn/enterprise/3.0/v4/changelog": "/cn/enterprise-server@3.0/graphql/overview/changelog", - "/cn/enterprise/v4/changelog": "/cn/enterprise-server@latest/graphql/overview/changelog", - "/cn/enterprise/2.20/graphql/overview/changelog": "/cn/enterprise-server@2.20/graphql/overview/changelog", - "/cn/enterprise-server@2.20/v4/changelog": "/cn/enterprise-server@2.20/graphql/overview/changelog", - "/cn/enterprise/2.20/v4/changelog": "/cn/enterprise-server@2.20/graphql/overview/changelog", - "/cn/github-ae@latest/v4/changelog": "/cn/github-ae@latest/graphql/overview/changelog", - "/cn/free-pro-team@latest/graphql/overview/explorer": "/cn/graphql/overview/explorer", - "/cn/v4/explorer": "/cn/graphql/overview/explorer", - "/cn/free-pro-team@latest/v4/explorer": "/cn/graphql/overview/explorer", - "/cn/v4/explorer-new": "/cn/graphql/overview/explorer", - "/cn/free-pro-team@latest/v4/explorer-new": "/cn/graphql/overview/explorer", - "/cn/enterprise/3.0/graphql/overview/explorer": "/cn/enterprise-server@3.0/graphql/overview/explorer", - "/cn/enterprise/graphql/overview/explorer": "/cn/enterprise-server@latest/graphql/overview/explorer", - "/cn/enterprise-server@3.0/v4/explorer": "/cn/enterprise-server@3.0/graphql/overview/explorer", - "/cn/enterprise/3.0/v4/explorer": "/cn/enterprise-server@3.0/graphql/overview/explorer", - "/cn/enterprise/v4/explorer": "/cn/enterprise-server@latest/graphql/overview/explorer", - "/cn/enterprise-server@3.0/v4/explorer-new": "/cn/enterprise-server@3.0/graphql/overview/explorer", - "/cn/enterprise/3.0/v4/explorer-new": "/cn/enterprise-server@3.0/graphql/overview/explorer", - "/cn/enterprise/v4/explorer-new": "/cn/enterprise-server@latest/graphql/overview/explorer", - "/cn/enterprise/2.20/graphql/overview/explorer": "/cn/enterprise-server@2.20/graphql/overview/explorer", - "/cn/enterprise-server@2.20/v4/explorer": "/cn/enterprise-server@2.20/graphql/overview/explorer", - "/cn/enterprise/2.20/v4/explorer": "/cn/enterprise-server@2.20/graphql/overview/explorer", - "/cn/enterprise-server@2.20/v4/explorer-new": "/cn/enterprise-server@2.20/graphql/overview/explorer", - "/cn/enterprise/2.20/v4/explorer-new": "/cn/enterprise-server@2.20/graphql/overview/explorer", - "/cn/github-ae@latest/v4/explorer": "/cn/github-ae@latest/graphql/overview/explorer", - "/cn/github-ae@latest/v4/explorer-new": "/cn/github-ae@latest/graphql/overview/explorer", - "/cn/free-pro-team@latest/graphql/overview": "/cn/graphql/overview", - "/cn/enterprise/3.0/graphql/overview": "/cn/enterprise-server@3.0/graphql/overview", - "/cn/enterprise/graphql/overview": "/cn/enterprise-server@latest/graphql/overview", - "/cn/enterprise/2.20/graphql/overview": "/cn/enterprise-server@2.20/graphql/overview", - "/cn/free-pro-team@latest/graphql/overview/public-schema": "/cn/graphql/overview/public-schema", - "/cn/v4/public_schema": "/cn/graphql/overview/public-schema", - "/cn/free-pro-team@latest/v4/public_schema": "/cn/graphql/overview/public-schema", - "/cn/enterprise/3.0/graphql/overview/public-schema": "/cn/enterprise-server@3.0/graphql/overview/public-schema", - "/cn/enterprise/graphql/overview/public-schema": "/cn/enterprise-server@latest/graphql/overview/public-schema", - "/cn/enterprise-server@3.0/v4/public_schema": "/cn/enterprise-server@3.0/graphql/overview/public-schema", - "/cn/enterprise/3.0/v4/public_schema": "/cn/enterprise-server@3.0/graphql/overview/public-schema", - "/cn/enterprise/v4/public_schema": "/cn/enterprise-server@latest/graphql/overview/public-schema", - "/cn/enterprise/2.20/graphql/overview/public-schema": "/cn/enterprise-server@2.20/graphql/overview/public-schema", - "/cn/enterprise-server@2.20/v4/public_schema": "/cn/enterprise-server@2.20/graphql/overview/public-schema", - "/cn/enterprise/2.20/v4/public_schema": "/cn/enterprise-server@2.20/graphql/overview/public-schema", - "/cn/github-ae@latest/v4/public_schema": "/cn/github-ae@latest/graphql/overview/public-schema", - "/cn/free-pro-team@latest/graphql/overview/resource-limitations": "/cn/graphql/overview/resource-limitations", - "/cn/v4/guides/resource-limitations": "/cn/graphql/overview/resource-limitations", - "/cn/free-pro-team@latest/v4/guides/resource-limitations": "/cn/graphql/overview/resource-limitations", - "/cn/enterprise/3.0/graphql/overview/resource-limitations": "/cn/enterprise-server@3.0/graphql/overview/resource-limitations", - "/cn/enterprise/graphql/overview/resource-limitations": "/cn/enterprise-server@latest/graphql/overview/resource-limitations", - "/cn/enterprise-server@3.0/v4/guides/resource-limitations": "/cn/enterprise-server@3.0/graphql/overview/resource-limitations", - "/cn/enterprise/3.0/v4/guides/resource-limitations": "/cn/enterprise-server@3.0/graphql/overview/resource-limitations", - "/cn/enterprise/v4/guides/resource-limitations": "/cn/enterprise-server@latest/graphql/overview/resource-limitations", - "/cn/enterprise/2.20/graphql/overview/resource-limitations": "/cn/enterprise-server@2.20/graphql/overview/resource-limitations", - "/cn/enterprise-server@2.20/v4/guides/resource-limitations": "/cn/enterprise-server@2.20/graphql/overview/resource-limitations", - "/cn/enterprise/2.20/v4/guides/resource-limitations": "/cn/enterprise-server@2.20/graphql/overview/resource-limitations", - "/cn/github-ae@latest/v4/guides/resource-limitations": "/cn/github-ae@latest/graphql/overview/resource-limitations", - "/cn/free-pro-team@latest/graphql/overview/schema-previews": "/cn/graphql/overview/schema-previews", - "/cn/v4/previews": "/cn/graphql/overview/schema-previews", - "/cn/free-pro-team@latest/v4/previews": "/cn/graphql/overview/schema-previews", - "/cn/enterprise/3.0/graphql/overview/schema-previews": "/cn/enterprise-server@3.0/graphql/overview/schema-previews", - "/cn/enterprise/graphql/overview/schema-previews": "/cn/enterprise-server@latest/graphql/overview/schema-previews", - "/cn/enterprise-server@3.0/v4/previews": "/cn/enterprise-server@3.0/graphql/overview/schema-previews", - "/cn/enterprise/3.0/v4/previews": "/cn/enterprise-server@3.0/graphql/overview/schema-previews", - "/cn/enterprise/v4/previews": "/cn/enterprise-server@latest/graphql/overview/schema-previews", - "/cn/enterprise/2.20/graphql/overview/schema-previews": "/cn/enterprise-server@2.20/graphql/overview/schema-previews", - "/cn/enterprise-server@2.20/v4/previews": "/cn/enterprise-server@2.20/graphql/overview/schema-previews", - "/cn/enterprise/2.20/v4/previews": "/cn/enterprise-server@2.20/graphql/overview/schema-previews", - "/cn/github-ae@latest/v4/previews": "/cn/github-ae@latest/graphql/overview/schema-previews", - "/cn/free-pro-team@latest/graphql/reference/enums": "/cn/graphql/reference/enums", - "/cn/v4/enum": "/cn/graphql/reference/enums", - "/cn/free-pro-team@latest/v4/enum": "/cn/graphql/reference/enums", - "/cn/v4/reference/enum": "/cn/graphql/reference/enums", - "/cn/free-pro-team@latest/v4/reference/enum": "/cn/graphql/reference/enums", - "/cn/enterprise/3.0/graphql/reference/enums": "/cn/enterprise-server@3.0/graphql/reference/enums", - "/cn/enterprise/graphql/reference/enums": "/cn/enterprise-server@latest/graphql/reference/enums", - "/cn/enterprise-server@3.0/v4/enum": "/cn/enterprise-server@3.0/graphql/reference/enums", - "/cn/enterprise/3.0/v4/enum": "/cn/enterprise-server@3.0/graphql/reference/enums", - "/cn/enterprise/v4/enum": "/cn/enterprise-server@latest/graphql/reference/enums", - "/cn/enterprise-server@3.0/v4/reference/enum": "/cn/enterprise-server@3.0/graphql/reference/enums", - "/cn/enterprise/3.0/v4/reference/enum": "/cn/enterprise-server@3.0/graphql/reference/enums", - "/cn/enterprise/v4/reference/enum": "/cn/enterprise-server@latest/graphql/reference/enums", - "/cn/enterprise/2.20/graphql/reference/enums": "/cn/enterprise-server@2.20/graphql/reference/enums", - "/cn/enterprise-server@2.20/v4/enum": "/cn/enterprise-server@2.20/graphql/reference/enums", - "/cn/enterprise/2.20/v4/enum": "/cn/enterprise-server@2.20/graphql/reference/enums", - "/cn/enterprise-server@2.20/v4/reference/enum": "/cn/enterprise-server@2.20/graphql/reference/enums", - "/cn/enterprise/2.20/v4/reference/enum": "/cn/enterprise-server@2.20/graphql/reference/enums", - "/cn/github-ae@latest/v4/enum": "/cn/github-ae@latest/graphql/reference/enums", - "/cn/github-ae@latest/v4/reference/enum": "/cn/github-ae@latest/graphql/reference/enums", - "/cn/free-pro-team@latest/graphql/reference": "/cn/graphql/reference", - "/cn/v4/reference": "/cn/graphql/reference", - "/cn/free-pro-team@latest/v4/reference": "/cn/graphql/reference", - "/cn/enterprise/3.0/graphql/reference": "/cn/enterprise-server@3.0/graphql/reference", - "/cn/enterprise/graphql/reference": "/cn/enterprise-server@latest/graphql/reference", - "/cn/enterprise-server@3.0/v4/reference": "/cn/enterprise-server@3.0/graphql/reference", - "/cn/enterprise/3.0/v4/reference": "/cn/enterprise-server@3.0/graphql/reference", - "/cn/enterprise/v4/reference": "/cn/enterprise-server@latest/graphql/reference", - "/cn/enterprise/2.20/graphql/reference": "/cn/enterprise-server@2.20/graphql/reference", - "/cn/enterprise-server@2.20/v4/reference": "/cn/enterprise-server@2.20/graphql/reference", - "/cn/enterprise/2.20/v4/reference": "/cn/enterprise-server@2.20/graphql/reference", - "/cn/github-ae@latest/v4/reference": "/cn/github-ae@latest/graphql/reference", - "/cn/free-pro-team@latest/graphql/reference/input-objects": "/cn/graphql/reference/input-objects", - "/cn/v4/input_object": "/cn/graphql/reference/input-objects", - "/cn/free-pro-team@latest/v4/input_object": "/cn/graphql/reference/input-objects", - "/cn/v4/reference/input_object": "/cn/graphql/reference/input-objects", - "/cn/free-pro-team@latest/v4/reference/input_object": "/cn/graphql/reference/input-objects", - "/cn/enterprise/3.0/graphql/reference/input-objects": "/cn/enterprise-server@3.0/graphql/reference/input-objects", - "/cn/enterprise/graphql/reference/input-objects": "/cn/enterprise-server@latest/graphql/reference/input-objects", - "/cn/enterprise-server@3.0/v4/input_object": "/cn/enterprise-server@3.0/graphql/reference/input-objects", - "/cn/enterprise/3.0/v4/input_object": "/cn/enterprise-server@3.0/graphql/reference/input-objects", - "/cn/enterprise/v4/input_object": "/cn/enterprise-server@latest/graphql/reference/input-objects", - "/cn/enterprise-server@3.0/v4/reference/input_object": "/cn/enterprise-server@3.0/graphql/reference/input-objects", - "/cn/enterprise/3.0/v4/reference/input_object": "/cn/enterprise-server@3.0/graphql/reference/input-objects", - "/cn/enterprise/v4/reference/input_object": "/cn/enterprise-server@latest/graphql/reference/input-objects", - "/cn/enterprise/2.20/graphql/reference/input-objects": "/cn/enterprise-server@2.20/graphql/reference/input-objects", - "/cn/enterprise-server@2.20/v4/input_object": "/cn/enterprise-server@2.20/graphql/reference/input-objects", - "/cn/enterprise/2.20/v4/input_object": "/cn/enterprise-server@2.20/graphql/reference/input-objects", - "/cn/enterprise-server@2.20/v4/reference/input_object": "/cn/enterprise-server@2.20/graphql/reference/input-objects", - "/cn/enterprise/2.20/v4/reference/input_object": "/cn/enterprise-server@2.20/graphql/reference/input-objects", - "/cn/github-ae@latest/v4/input_object": "/cn/github-ae@latest/graphql/reference/input-objects", - "/cn/github-ae@latest/v4/reference/input_object": "/cn/github-ae@latest/graphql/reference/input-objects", - "/cn/free-pro-team@latest/graphql/reference/interfaces": "/cn/graphql/reference/interfaces", - "/cn/v4/interface": "/cn/graphql/reference/interfaces", - "/cn/free-pro-team@latest/v4/interface": "/cn/graphql/reference/interfaces", - "/cn/v4/reference/interface": "/cn/graphql/reference/interfaces", - "/cn/free-pro-team@latest/v4/reference/interface": "/cn/graphql/reference/interfaces", - "/cn/enterprise/3.0/graphql/reference/interfaces": "/cn/enterprise-server@3.0/graphql/reference/interfaces", - "/cn/enterprise/graphql/reference/interfaces": "/cn/enterprise-server@latest/graphql/reference/interfaces", - "/cn/enterprise-server@3.0/v4/interface": "/cn/enterprise-server@3.0/graphql/reference/interfaces", - "/cn/enterprise/3.0/v4/interface": "/cn/enterprise-server@3.0/graphql/reference/interfaces", - "/cn/enterprise/v4/interface": "/cn/enterprise-server@latest/graphql/reference/interfaces", - "/cn/enterprise-server@3.0/v4/reference/interface": "/cn/enterprise-server@3.0/graphql/reference/interfaces", - "/cn/enterprise/3.0/v4/reference/interface": "/cn/enterprise-server@3.0/graphql/reference/interfaces", - "/cn/enterprise/v4/reference/interface": "/cn/enterprise-server@latest/graphql/reference/interfaces", - "/cn/enterprise/2.20/graphql/reference/interfaces": "/cn/enterprise-server@2.20/graphql/reference/interfaces", - "/cn/enterprise-server@2.20/v4/interface": "/cn/enterprise-server@2.20/graphql/reference/interfaces", - "/cn/enterprise/2.20/v4/interface": "/cn/enterprise-server@2.20/graphql/reference/interfaces", - "/cn/enterprise-server@2.20/v4/reference/interface": "/cn/enterprise-server@2.20/graphql/reference/interfaces", - "/cn/enterprise/2.20/v4/reference/interface": "/cn/enterprise-server@2.20/graphql/reference/interfaces", - "/cn/github-ae@latest/v4/interface": "/cn/github-ae@latest/graphql/reference/interfaces", - "/cn/github-ae@latest/v4/reference/interface": "/cn/github-ae@latest/graphql/reference/interfaces", - "/cn/free-pro-team@latest/graphql/reference/mutations": "/cn/graphql/reference/mutations", - "/cn/v4/mutation": "/cn/graphql/reference/mutations", - "/cn/free-pro-team@latest/v4/mutation": "/cn/graphql/reference/mutations", - "/cn/v4/reference/mutation": "/cn/graphql/reference/mutations", - "/cn/free-pro-team@latest/v4/reference/mutation": "/cn/graphql/reference/mutations", - "/cn/enterprise/3.0/graphql/reference/mutations": "/cn/enterprise-server@3.0/graphql/reference/mutations", - "/cn/enterprise/graphql/reference/mutations": "/cn/enterprise-server@latest/graphql/reference/mutations", - "/cn/enterprise-server@3.0/v4/mutation": "/cn/enterprise-server@3.0/graphql/reference/mutations", - "/cn/enterprise/3.0/v4/mutation": "/cn/enterprise-server@3.0/graphql/reference/mutations", - "/cn/enterprise/v4/mutation": "/cn/enterprise-server@latest/graphql/reference/mutations", - "/cn/enterprise-server@3.0/v4/reference/mutation": "/cn/enterprise-server@3.0/graphql/reference/mutations", - "/cn/enterprise/3.0/v4/reference/mutation": "/cn/enterprise-server@3.0/graphql/reference/mutations", - "/cn/enterprise/v4/reference/mutation": "/cn/enterprise-server@latest/graphql/reference/mutations", - "/cn/enterprise/2.20/graphql/reference/mutations": "/cn/enterprise-server@2.20/graphql/reference/mutations", - "/cn/enterprise-server@2.20/v4/mutation": "/cn/enterprise-server@2.20/graphql/reference/mutations", - "/cn/enterprise/2.20/v4/mutation": "/cn/enterprise-server@2.20/graphql/reference/mutations", - "/cn/enterprise-server@2.20/v4/reference/mutation": "/cn/enterprise-server@2.20/graphql/reference/mutations", - "/cn/enterprise/2.20/v4/reference/mutation": "/cn/enterprise-server@2.20/graphql/reference/mutations", - "/cn/github-ae@latest/v4/mutation": "/cn/github-ae@latest/graphql/reference/mutations", - "/cn/github-ae@latest/v4/reference/mutation": "/cn/github-ae@latest/graphql/reference/mutations", - "/cn/free-pro-team@latest/graphql/reference/objects": "/cn/graphql/reference/objects", - "/cn/v4/object": "/cn/graphql/reference/objects", - "/cn/free-pro-team@latest/v4/object": "/cn/graphql/reference/objects", - "/cn/v4/reference/object": "/cn/graphql/reference/objects", - "/cn/free-pro-team@latest/v4/reference/object": "/cn/graphql/reference/objects", - "/cn/enterprise/3.0/graphql/reference/objects": "/cn/enterprise-server@3.0/graphql/reference/objects", - "/cn/enterprise/graphql/reference/objects": "/cn/enterprise-server@latest/graphql/reference/objects", - "/cn/enterprise-server@3.0/v4/object": "/cn/enterprise-server@3.0/graphql/reference/objects", - "/cn/enterprise/3.0/v4/object": "/cn/enterprise-server@3.0/graphql/reference/objects", - "/cn/enterprise/v4/object": "/cn/enterprise-server@latest/graphql/reference/objects", - "/cn/enterprise-server@3.0/v4/reference/object": "/cn/enterprise-server@3.0/graphql/reference/objects", - "/cn/enterprise/3.0/v4/reference/object": "/cn/enterprise-server@3.0/graphql/reference/objects", - "/cn/enterprise/v4/reference/object": "/cn/enterprise-server@latest/graphql/reference/objects", - "/cn/enterprise/2.20/graphql/reference/objects": "/cn/enterprise-server@2.20/graphql/reference/objects", - "/cn/enterprise-server@2.20/v4/object": "/cn/enterprise-server@2.20/graphql/reference/objects", - "/cn/enterprise/2.20/v4/object": "/cn/enterprise-server@2.20/graphql/reference/objects", - "/cn/enterprise-server@2.20/v4/reference/object": "/cn/enterprise-server@2.20/graphql/reference/objects", - "/cn/enterprise/2.20/v4/reference/object": "/cn/enterprise-server@2.20/graphql/reference/objects", - "/cn/github-ae@latest/v4/object": "/cn/github-ae@latest/graphql/reference/objects", - "/cn/github-ae@latest/v4/reference/object": "/cn/github-ae@latest/graphql/reference/objects", - "/cn/free-pro-team@latest/graphql/reference/queries": "/cn/graphql/reference/queries", - "/cn/v4/query": "/cn/graphql/reference/queries", - "/cn/free-pro-team@latest/v4/query": "/cn/graphql/reference/queries", - "/cn/v4/reference/query": "/cn/graphql/reference/queries", - "/cn/free-pro-team@latest/v4/reference/query": "/cn/graphql/reference/queries", - "/cn/enterprise/3.0/graphql/reference/queries": "/cn/enterprise-server@3.0/graphql/reference/queries", - "/cn/enterprise/graphql/reference/queries": "/cn/enterprise-server@latest/graphql/reference/queries", - "/cn/enterprise-server@3.0/v4/query": "/cn/enterprise-server@3.0/graphql/reference/queries", - "/cn/enterprise/3.0/v4/query": "/cn/enterprise-server@3.0/graphql/reference/queries", - "/cn/enterprise/v4/query": "/cn/enterprise-server@latest/graphql/reference/queries", - "/cn/enterprise-server@3.0/v4/reference/query": "/cn/enterprise-server@3.0/graphql/reference/queries", - "/cn/enterprise/3.0/v4/reference/query": "/cn/enterprise-server@3.0/graphql/reference/queries", - "/cn/enterprise/v4/reference/query": "/cn/enterprise-server@latest/graphql/reference/queries", - "/cn/enterprise/2.20/graphql/reference/queries": "/cn/enterprise-server@2.20/graphql/reference/queries", - "/cn/enterprise-server@2.20/v4/query": "/cn/enterprise-server@2.20/graphql/reference/queries", - "/cn/enterprise/2.20/v4/query": "/cn/enterprise-server@2.20/graphql/reference/queries", - "/cn/enterprise-server@2.20/v4/reference/query": "/cn/enterprise-server@2.20/graphql/reference/queries", - "/cn/enterprise/2.20/v4/reference/query": "/cn/enterprise-server@2.20/graphql/reference/queries", - "/cn/github-ae@latest/v4/query": "/cn/github-ae@latest/graphql/reference/queries", - "/cn/github-ae@latest/v4/reference/query": "/cn/github-ae@latest/graphql/reference/queries", - "/cn/free-pro-team@latest/graphql/reference/scalars": "/cn/graphql/reference/scalars", - "/cn/v4/scalar": "/cn/graphql/reference/scalars", - "/cn/free-pro-team@latest/v4/scalar": "/cn/graphql/reference/scalars", - "/cn/v4/reference/scalar": "/cn/graphql/reference/scalars", - "/cn/free-pro-team@latest/v4/reference/scalar": "/cn/graphql/reference/scalars", - "/cn/enterprise/3.0/graphql/reference/scalars": "/cn/enterprise-server@3.0/graphql/reference/scalars", - "/cn/enterprise/graphql/reference/scalars": "/cn/enterprise-server@latest/graphql/reference/scalars", - "/cn/enterprise-server@3.0/v4/scalar": "/cn/enterprise-server@3.0/graphql/reference/scalars", - "/cn/enterprise/3.0/v4/scalar": "/cn/enterprise-server@3.0/graphql/reference/scalars", - "/cn/enterprise/v4/scalar": "/cn/enterprise-server@latest/graphql/reference/scalars", - "/cn/enterprise-server@3.0/v4/reference/scalar": "/cn/enterprise-server@3.0/graphql/reference/scalars", - "/cn/enterprise/3.0/v4/reference/scalar": "/cn/enterprise-server@3.0/graphql/reference/scalars", - "/cn/enterprise/v4/reference/scalar": "/cn/enterprise-server@latest/graphql/reference/scalars", - "/cn/enterprise/2.20/graphql/reference/scalars": "/cn/enterprise-server@2.20/graphql/reference/scalars", - "/cn/enterprise-server@2.20/v4/scalar": "/cn/enterprise-server@2.20/graphql/reference/scalars", - "/cn/enterprise/2.20/v4/scalar": "/cn/enterprise-server@2.20/graphql/reference/scalars", - "/cn/enterprise-server@2.20/v4/reference/scalar": "/cn/enterprise-server@2.20/graphql/reference/scalars", - "/cn/enterprise/2.20/v4/reference/scalar": "/cn/enterprise-server@2.20/graphql/reference/scalars", - "/cn/github-ae@latest/v4/scalar": "/cn/github-ae@latest/graphql/reference/scalars", - "/cn/github-ae@latest/v4/reference/scalar": "/cn/github-ae@latest/graphql/reference/scalars", - "/cn/free-pro-team@latest/graphql/reference/unions": "/cn/graphql/reference/unions", - "/cn/v4/union": "/cn/graphql/reference/unions", - "/cn/free-pro-team@latest/v4/union": "/cn/graphql/reference/unions", - "/cn/v4/reference/union": "/cn/graphql/reference/unions", - "/cn/free-pro-team@latest/v4/reference/union": "/cn/graphql/reference/unions", - "/cn/enterprise/3.0/graphql/reference/unions": "/cn/enterprise-server@3.0/graphql/reference/unions", - "/cn/enterprise/graphql/reference/unions": "/cn/enterprise-server@latest/graphql/reference/unions", - "/cn/enterprise-server@3.0/v4/union": "/cn/enterprise-server@3.0/graphql/reference/unions", - "/cn/enterprise/3.0/v4/union": "/cn/enterprise-server@3.0/graphql/reference/unions", - "/cn/enterprise/v4/union": "/cn/enterprise-server@latest/graphql/reference/unions", - "/cn/enterprise-server@3.0/v4/reference/union": "/cn/enterprise-server@3.0/graphql/reference/unions", - "/cn/enterprise/3.0/v4/reference/union": "/cn/enterprise-server@3.0/graphql/reference/unions", - "/cn/enterprise/v4/reference/union": "/cn/enterprise-server@latest/graphql/reference/unions", - "/cn/enterprise/2.20/graphql/reference/unions": "/cn/enterprise-server@2.20/graphql/reference/unions", - "/cn/enterprise-server@2.20/v4/union": "/cn/enterprise-server@2.20/graphql/reference/unions", - "/cn/enterprise/2.20/v4/union": "/cn/enterprise-server@2.20/graphql/reference/unions", - "/cn/enterprise-server@2.20/v4/reference/union": "/cn/enterprise-server@2.20/graphql/reference/unions", - "/cn/enterprise/2.20/v4/reference/union": "/cn/enterprise-server@2.20/graphql/reference/unions", - "/cn/github-ae@latest/v4/union": "/cn/github-ae@latest/graphql/reference/unions", - "/cn/github-ae@latest/v4/reference/union": "/cn/github-ae@latest/graphql/reference/unions", - "/cn/free-pro-team@latest/rest/guides/basics-of-authentication": "/cn/rest/guides/basics-of-authentication", - "/cn/v3/guides/basics-of-authentication": "/cn/rest/guides/basics-of-authentication", - "/cn/free-pro-team@latest/v3/guides/basics-of-authentication": "/cn/rest/guides/basics-of-authentication", - "/cn/rest/basics-of-authentication": "/cn/rest/guides/basics-of-authentication", - "/cn/free-pro-team@latest/rest/basics-of-authentication": "/cn/rest/guides/basics-of-authentication", - "/cn/enterprise/3.0/rest/guides/basics-of-authentication": "/cn/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/cn/enterprise/rest/guides/basics-of-authentication": "/cn/enterprise-server@latest/rest/guides/basics-of-authentication", - "/cn/enterprise-server@3.0/v3/guides/basics-of-authentication": "/cn/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/cn/enterprise/3.0/v3/guides/basics-of-authentication": "/cn/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/cn/enterprise/v3/guides/basics-of-authentication": "/cn/enterprise-server@latest/rest/guides/basics-of-authentication", - "/cn/enterprise-server@3.0/rest/basics-of-authentication": "/cn/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/cn/enterprise/3.0/rest/basics-of-authentication": "/cn/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/cn/enterprise/rest/basics-of-authentication": "/cn/enterprise-server@latest/rest/guides/basics-of-authentication", - "/cn/enterprise/2.20/rest/guides/basics-of-authentication": "/cn/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/cn/enterprise-server@2.20/v3/guides/basics-of-authentication": "/cn/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/cn/enterprise/2.20/v3/guides/basics-of-authentication": "/cn/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/cn/enterprise-server@2.20/rest/basics-of-authentication": "/cn/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/cn/enterprise/2.20/rest/basics-of-authentication": "/cn/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/cn/github-ae@latest/v3/guides/basics-of-authentication": "/cn/github-ae@latest/rest/guides/basics-of-authentication", - "/cn/github-ae@latest/rest/basics-of-authentication": "/cn/github-ae@latest/rest/guides/basics-of-authentication", - "/cn/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/cn/rest/guides/best-practices-for-integrators", - "/cn/v3/guides/best-practices-for-integrators": "/cn/rest/guides/best-practices-for-integrators", - "/cn/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/cn/rest/guides/best-practices-for-integrators", - "/cn/enterprise/3.0/rest/guides/best-practices-for-integrators": "/cn/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/cn/enterprise/rest/guides/best-practices-for-integrators": "/cn/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/cn/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/cn/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/cn/enterprise/3.0/v3/guides/best-practices-for-integrators": "/cn/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/cn/enterprise/v3/guides/best-practices-for-integrators": "/cn/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/cn/enterprise/2.20/rest/guides/best-practices-for-integrators": "/cn/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/cn/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/cn/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/cn/enterprise/2.20/v3/guides/best-practices-for-integrators": "/cn/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/cn/github-ae@latest/v3/guides/best-practices-for-integrators": "/cn/github-ae@latest/rest/guides/best-practices-for-integrators", - "/cn/free-pro-team@latest/rest/guides/building-a-ci-server": "/cn/rest/guides/building-a-ci-server", - "/cn/v3/guides/building-a-ci-server": "/cn/rest/guides/building-a-ci-server", - "/cn/free-pro-team@latest/v3/guides/building-a-ci-server": "/cn/rest/guides/building-a-ci-server", - "/cn/enterprise/3.0/rest/guides/building-a-ci-server": "/cn/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/cn/enterprise/rest/guides/building-a-ci-server": "/cn/enterprise-server@latest/rest/guides/building-a-ci-server", - "/cn/enterprise-server@3.0/v3/guides/building-a-ci-server": "/cn/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/cn/enterprise/3.0/v3/guides/building-a-ci-server": "/cn/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/cn/enterprise/v3/guides/building-a-ci-server": "/cn/enterprise-server@latest/rest/guides/building-a-ci-server", - "/cn/enterprise/2.20/rest/guides/building-a-ci-server": "/cn/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/cn/enterprise-server@2.20/v3/guides/building-a-ci-server": "/cn/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/cn/enterprise/2.20/v3/guides/building-a-ci-server": "/cn/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/cn/github-ae@latest/v3/guides/building-a-ci-server": "/cn/github-ae@latest/rest/guides/building-a-ci-server", - "/cn/free-pro-team@latest/rest/guides/delivering-deployments": "/cn/rest/guides/delivering-deployments", - "/cn/v3/guides/delivering-deployments": "/cn/rest/guides/delivering-deployments", - "/cn/free-pro-team@latest/v3/guides/delivering-deployments": "/cn/rest/guides/delivering-deployments", - "/cn/enterprise/3.0/rest/guides/delivering-deployments": "/cn/enterprise-server@3.0/rest/guides/delivering-deployments", - "/cn/enterprise/rest/guides/delivering-deployments": "/cn/enterprise-server@latest/rest/guides/delivering-deployments", - "/cn/enterprise-server@3.0/v3/guides/delivering-deployments": "/cn/enterprise-server@3.0/rest/guides/delivering-deployments", - "/cn/enterprise/3.0/v3/guides/delivering-deployments": "/cn/enterprise-server@3.0/rest/guides/delivering-deployments", - "/cn/enterprise/v3/guides/delivering-deployments": "/cn/enterprise-server@latest/rest/guides/delivering-deployments", - "/cn/enterprise/2.20/rest/guides/delivering-deployments": "/cn/enterprise-server@2.20/rest/guides/delivering-deployments", - "/cn/enterprise-server@2.20/v3/guides/delivering-deployments": "/cn/enterprise-server@2.20/rest/guides/delivering-deployments", - "/cn/enterprise/2.20/v3/guides/delivering-deployments": "/cn/enterprise-server@2.20/rest/guides/delivering-deployments", - "/cn/github-ae@latest/v3/guides/delivering-deployments": "/cn/github-ae@latest/rest/guides/delivering-deployments", - "/cn/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/cn/rest/guides/discovering-resources-for-a-user", - "/cn/v3/guides/discovering-resources-for-a-user": "/cn/rest/guides/discovering-resources-for-a-user", - "/cn/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/cn/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/cn/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise/rest/guides/discovering-resources-for-a-user": "/cn/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/cn/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/cn/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise/v3/guides/discovering-resources-for-a-user": "/cn/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/cn/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/cn/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/cn/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/cn/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/cn/github-ae@latest/v3/guides/discovering-resources-for-a-user": "/cn/github-ae@latest/rest/guides/discovering-resources-for-a-user", - "/cn/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/cn/rest/guides/getting-started-with-the-checks-api", - "/cn/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/cn/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/cn/enterprise/rest/guides/getting-started-with-the-checks-api": "/cn/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", - "/cn/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/cn/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/cn/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/cn/rest/guides/getting-started-with-the-git-database-api", - "/cn/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/cn/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/cn/enterprise/rest/guides/getting-started-with-the-git-database-api": "/cn/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", - "/cn/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/cn/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/cn/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/cn/rest/guides/getting-started-with-the-rest-api", - "/cn/v3/guides/getting-started": "/cn/rest/guides/getting-started-with-the-rest-api", - "/cn/free-pro-team@latest/v3/guides/getting-started": "/cn/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/cn/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise/rest/guides/getting-started-with-the-rest-api": "/cn/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise-server@3.0/v3/guides/getting-started": "/cn/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise/3.0/v3/guides/getting-started": "/cn/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise/v3/guides/getting-started": "/cn/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/cn/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise-server@2.20/v3/guides/getting-started": "/cn/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/cn/enterprise/2.20/v3/guides/getting-started": "/cn/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/cn/github-ae@latest/v3/guides/getting-started": "/cn/github-ae@latest/rest/guides/getting-started-with-the-rest-api", - "/cn/free-pro-team@latest/rest/guides": "/cn/rest/guides", - "/cn/v3/guides": "/cn/rest/guides", - "/cn/free-pro-team@latest/v3/guides": "/cn/rest/guides", - "/cn/enterprise/3.0/rest/guides": "/cn/enterprise-server@3.0/rest/guides", - "/cn/enterprise/rest/guides": "/cn/enterprise-server@latest/rest/guides", - "/cn/enterprise-server@3.0/v3/guides": "/cn/enterprise-server@3.0/rest/guides", - "/cn/enterprise/3.0/v3/guides": "/cn/enterprise-server@3.0/rest/guides", - "/cn/enterprise/v3/guides": "/cn/enterprise-server@latest/rest/guides", - "/cn/enterprise/2.20/rest/guides": "/cn/enterprise-server@2.20/rest/guides", - "/cn/enterprise-server@2.20/v3/guides": "/cn/enterprise-server@2.20/rest/guides", - "/cn/enterprise/2.20/v3/guides": "/cn/enterprise-server@2.20/rest/guides", - "/cn/github-ae@latest/v3/guides": "/cn/github-ae@latest/rest/guides", - "/cn/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/cn/rest/guides/rendering-data-as-graphs", - "/cn/v3/guides/rendering-data-as-graphs": "/cn/rest/guides/rendering-data-as-graphs", - "/cn/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/cn/rest/guides/rendering-data-as-graphs", - "/cn/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/cn/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/cn/enterprise/rest/guides/rendering-data-as-graphs": "/cn/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/cn/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/cn/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/cn/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/cn/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/cn/enterprise/v3/guides/rendering-data-as-graphs": "/cn/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/cn/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/cn/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/cn/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/cn/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/cn/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/cn/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/cn/github-ae@latest/v3/guides/rendering-data-as-graphs": "/cn/github-ae@latest/rest/guides/rendering-data-as-graphs", - "/cn/free-pro-team@latest/rest/guides/traversing-with-pagination": "/cn/rest/guides/traversing-with-pagination", - "/cn/v3/guides/traversing-with-pagination": "/cn/rest/guides/traversing-with-pagination", - "/cn/free-pro-team@latest/v3/guides/traversing-with-pagination": "/cn/rest/guides/traversing-with-pagination", - "/cn/enterprise/3.0/rest/guides/traversing-with-pagination": "/cn/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/cn/enterprise/rest/guides/traversing-with-pagination": "/cn/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/cn/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/cn/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/cn/enterprise/3.0/v3/guides/traversing-with-pagination": "/cn/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/cn/enterprise/v3/guides/traversing-with-pagination": "/cn/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/cn/enterprise/2.20/rest/guides/traversing-with-pagination": "/cn/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/cn/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/cn/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/cn/enterprise/2.20/v3/guides/traversing-with-pagination": "/cn/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/cn/github-ae@latest/v3/guides/traversing-with-pagination": "/cn/github-ae@latest/rest/guides/traversing-with-pagination", - "/cn/free-pro-team@latest/rest/guides/working-with-comments": "/cn/rest/guides/working-with-comments", - "/cn/v3/guides/working-with-comments": "/cn/rest/guides/working-with-comments", - "/cn/free-pro-team@latest/v3/guides/working-with-comments": "/cn/rest/guides/working-with-comments", - "/cn/enterprise/3.0/rest/guides/working-with-comments": "/cn/enterprise-server@3.0/rest/guides/working-with-comments", - "/cn/enterprise/rest/guides/working-with-comments": "/cn/enterprise-server@latest/rest/guides/working-with-comments", - "/cn/enterprise-server@3.0/v3/guides/working-with-comments": "/cn/enterprise-server@3.0/rest/guides/working-with-comments", - "/cn/enterprise/3.0/v3/guides/working-with-comments": "/cn/enterprise-server@3.0/rest/guides/working-with-comments", - "/cn/enterprise/v3/guides/working-with-comments": "/cn/enterprise-server@latest/rest/guides/working-with-comments", - "/cn/enterprise/2.20/rest/guides/working-with-comments": "/cn/enterprise-server@2.20/rest/guides/working-with-comments", - "/cn/enterprise-server@2.20/v3/guides/working-with-comments": "/cn/enterprise-server@2.20/rest/guides/working-with-comments", - "/cn/enterprise/2.20/v3/guides/working-with-comments": "/cn/enterprise-server@2.20/rest/guides/working-with-comments", - "/cn/github-ae@latest/v3/guides/working-with-comments": "/cn/github-ae@latest/rest/guides/working-with-comments", - "/cn/free-pro-team@latest/rest": "/cn/rest", - "/cn/v3": "/cn/rest", - "/cn/free-pro-team@latest/v3": "/cn/rest", - "/cn/enterprise/3.0/rest": "/cn/enterprise-server@3.0/rest", - "/cn/enterprise/rest": "/cn/enterprise-server@latest/rest", - "/cn/enterprise-server@3.0/v3": "/cn/enterprise-server@3.0/rest", - "/cn/enterprise/3.0/v3": "/cn/enterprise-server@3.0/rest", - "/cn/enterprise/v3": "/cn/enterprise-server@latest/rest", - "/cn/enterprise/2.20/rest": "/cn/enterprise-server@2.20/rest", - "/cn/enterprise-server@2.20/v3": "/cn/enterprise-server@2.20/rest", - "/cn/enterprise/2.20/v3": "/cn/enterprise-server@2.20/rest", - "/cn/github-ae@latest/v3": "/cn/github-ae@latest/rest", - "/cn/free-pro-team@latest/rest/overview/api-previews": "/cn/rest/overview/api-previews", - "/cn/v3/previews": "/cn/rest/overview/api-previews", - "/cn/free-pro-team@latest/v3/previews": "/cn/rest/overview/api-previews", - "/cn/enterprise/3.0/rest/overview/api-previews": "/cn/enterprise-server@3.0/rest/overview/api-previews", - "/cn/enterprise/rest/overview/api-previews": "/cn/enterprise-server@latest/rest/overview/api-previews", - "/cn/enterprise-server@3.0/v3/previews": "/cn/enterprise-server@3.0/rest/overview/api-previews", - "/cn/enterprise/3.0/v3/previews": "/cn/enterprise-server@3.0/rest/overview/api-previews", - "/cn/enterprise/v3/previews": "/cn/enterprise-server@latest/rest/overview/api-previews", - "/cn/enterprise/2.20/rest/overview/api-previews": "/cn/enterprise-server@2.20/rest/overview/api-previews", - "/cn/enterprise-server@2.20/v3/previews": "/cn/enterprise-server@2.20/rest/overview/api-previews", - "/cn/enterprise/2.20/v3/previews": "/cn/enterprise-server@2.20/rest/overview/api-previews", - "/cn/github-ae@latest/v3/previews": "/cn/github-ae@latest/rest/overview/api-previews", - "/cn/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/cn/rest/overview/endpoints-available-for-github-apps", - "/cn/v3/apps/available-endpoints": "/cn/rest/overview/endpoints-available-for-github-apps", - "/cn/free-pro-team@latest/v3/apps/available-endpoints": "/cn/rest/overview/endpoints-available-for-github-apps", - "/cn/rest/reference/endpoints-available-for-github-apps": "/cn/rest/overview/endpoints-available-for-github-apps", - "/cn/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/cn/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/cn/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/rest/overview/endpoints-available-for-github-apps": "/cn/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise-server@3.0/v3/apps/available-endpoints": "/cn/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/3.0/v3/apps/available-endpoints": "/cn/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/v3/apps/available-endpoints": "/cn/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/cn/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/cn/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/rest/reference/endpoints-available-for-github-apps": "/cn/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/cn/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise-server@2.20/v3/apps/available-endpoints": "/cn/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/2.20/v3/apps/available-endpoints": "/cn/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/cn/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/cn/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/cn/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/cn/github-ae@latest/v3/apps/available-endpoints": "/cn/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/cn/github-ae@latest/rest/reference/endpoints-available-for-github-apps": "/cn/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/cn/free-pro-team@latest/rest/overview": "/cn/rest/overview", - "/cn/enterprise/3.0/rest/overview": "/cn/enterprise-server@3.0/rest/overview", - "/cn/enterprise/rest/overview": "/cn/enterprise-server@latest/rest/overview", - "/cn/enterprise/2.20/rest/overview": "/cn/enterprise-server@2.20/rest/overview", - "/cn/free-pro-team@latest/rest/overview/libraries": "/cn/rest/overview/libraries", - "/cn/v3/libraries": "/cn/rest/overview/libraries", - "/cn/free-pro-team@latest/v3/libraries": "/cn/rest/overview/libraries", - "/cn/enterprise/3.0/rest/overview/libraries": "/cn/enterprise-server@3.0/rest/overview/libraries", - "/cn/enterprise/rest/overview/libraries": "/cn/enterprise-server@latest/rest/overview/libraries", - "/cn/enterprise-server@3.0/v3/libraries": "/cn/enterprise-server@3.0/rest/overview/libraries", - "/cn/enterprise/3.0/v3/libraries": "/cn/enterprise-server@3.0/rest/overview/libraries", - "/cn/enterprise/v3/libraries": "/cn/enterprise-server@latest/rest/overview/libraries", - "/cn/enterprise/2.20/rest/overview/libraries": "/cn/enterprise-server@2.20/rest/overview/libraries", - "/cn/enterprise-server@2.20/v3/libraries": "/cn/enterprise-server@2.20/rest/overview/libraries", - "/cn/enterprise/2.20/v3/libraries": "/cn/enterprise-server@2.20/rest/overview/libraries", - "/cn/github-ae@latest/v3/libraries": "/cn/github-ae@latest/rest/overview/libraries", - "/cn/free-pro-team@latest/rest/overview/media-types": "/cn/rest/overview/media-types", - "/cn/v3/media": "/cn/rest/overview/media-types", - "/cn/free-pro-team@latest/v3/media": "/cn/rest/overview/media-types", - "/cn/enterprise/3.0/rest/overview/media-types": "/cn/enterprise-server@3.0/rest/overview/media-types", - "/cn/enterprise/rest/overview/media-types": "/cn/enterprise-server@latest/rest/overview/media-types", - "/cn/enterprise-server@3.0/v3/media": "/cn/enterprise-server@3.0/rest/overview/media-types", - "/cn/enterprise/3.0/v3/media": "/cn/enterprise-server@3.0/rest/overview/media-types", - "/cn/enterprise/v3/media": "/cn/enterprise-server@latest/rest/overview/media-types", - "/cn/enterprise/2.20/rest/overview/media-types": "/cn/enterprise-server@2.20/rest/overview/media-types", - "/cn/enterprise-server@2.20/v3/media": "/cn/enterprise-server@2.20/rest/overview/media-types", - "/cn/enterprise/2.20/v3/media": "/cn/enterprise-server@2.20/rest/overview/media-types", - "/cn/github-ae@latest/v3/media": "/cn/github-ae@latest/rest/overview/media-types", - "/cn/free-pro-team@latest/rest/overview/openapi-description": "/cn/rest/overview/openapi-description", - "/cn/enterprise/3.0/rest/overview/openapi-description": "/cn/enterprise-server@3.0/rest/overview/openapi-description", - "/cn/enterprise/rest/overview/openapi-description": "/cn/enterprise-server@latest/rest/overview/openapi-description", - "/cn/enterprise/2.20/rest/overview/openapi-description": "/cn/enterprise-server@2.20/rest/overview/openapi-description", - "/cn/free-pro-team@latest/rest/overview/other-authentication-methods": "/cn/rest/overview/other-authentication-methods", - "/cn/v3/auth": "/cn/rest/overview/other-authentication-methods", - "/cn/free-pro-team@latest/v3/auth": "/cn/rest/overview/other-authentication-methods", - "/cn/enterprise/3.0/rest/overview/other-authentication-methods": "/cn/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/cn/enterprise/rest/overview/other-authentication-methods": "/cn/enterprise-server@latest/rest/overview/other-authentication-methods", - "/cn/enterprise-server@3.0/v3/auth": "/cn/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/cn/enterprise/3.0/v3/auth": "/cn/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/cn/enterprise/v3/auth": "/cn/enterprise-server@latest/rest/overview/other-authentication-methods", - "/cn/enterprise/2.20/rest/overview/other-authentication-methods": "/cn/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/cn/enterprise-server@2.20/v3/auth": "/cn/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/cn/enterprise/2.20/v3/auth": "/cn/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/cn/github-ae@latest/v3/auth": "/cn/github-ae@latest/rest/overview/other-authentication-methods", - "/cn/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/cn/rest/overview/resources-in-the-rest-api", - "/cn/rest/initialize-the-repo": "/cn/rest/overview/resources-in-the-rest-api", - "/cn/free-pro-team@latest/rest/initialize-the-repo": "/cn/rest/overview/resources-in-the-rest-api", - "/cn/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/cn/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/cn/enterprise/rest/overview/resources-in-the-rest-api": "/cn/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/cn/enterprise-server@3.0/rest/initialize-the-repo": "/cn/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/cn/enterprise/3.0/rest/initialize-the-repo": "/cn/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/cn/enterprise/rest/initialize-the-repo": "/cn/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/cn/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/cn/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/cn/enterprise-server@2.20/rest/initialize-the-repo": "/cn/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/cn/enterprise/2.20/rest/initialize-the-repo": "/cn/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/cn/github-ae@latest/rest/initialize-the-repo": "/cn/github-ae@latest/rest/overview/resources-in-the-rest-api", - "/cn/free-pro-team@latest/rest/overview/troubleshooting": "/cn/rest/overview/troubleshooting", - "/cn/v3/troubleshooting": "/cn/rest/overview/troubleshooting", - "/cn/free-pro-team@latest/v3/troubleshooting": "/cn/rest/overview/troubleshooting", - "/cn/enterprise/3.0/rest/overview/troubleshooting": "/cn/enterprise-server@3.0/rest/overview/troubleshooting", - "/cn/enterprise/rest/overview/troubleshooting": "/cn/enterprise-server@latest/rest/overview/troubleshooting", - "/cn/enterprise-server@3.0/v3/troubleshooting": "/cn/enterprise-server@3.0/rest/overview/troubleshooting", - "/cn/enterprise/3.0/v3/troubleshooting": "/cn/enterprise-server@3.0/rest/overview/troubleshooting", - "/cn/enterprise/v3/troubleshooting": "/cn/enterprise-server@latest/rest/overview/troubleshooting", - "/cn/enterprise/2.20/rest/overview/troubleshooting": "/cn/enterprise-server@2.20/rest/overview/troubleshooting", - "/cn/enterprise-server@2.20/v3/troubleshooting": "/cn/enterprise-server@2.20/rest/overview/troubleshooting", - "/cn/enterprise/2.20/v3/troubleshooting": "/cn/enterprise-server@2.20/rest/overview/troubleshooting", - "/cn/github-ae@latest/v3/troubleshooting": "/cn/github-ae@latest/rest/overview/troubleshooting", - "/cn/free-pro-team@latest/rest/reference/actions": "/cn/rest/reference/actions", - "/cn/v3/actions": "/cn/rest/reference/actions", - "/cn/free-pro-team@latest/v3/actions": "/cn/rest/reference/actions", - "/cn/enterprise/3.0/rest/reference/actions": "/cn/enterprise-server@3.0/rest/reference/actions", - "/cn/enterprise/rest/reference/actions": "/cn/enterprise-server@latest/rest/reference/actions", - "/cn/enterprise-server@3.0/v3/actions": "/cn/enterprise-server@3.0/rest/reference/actions", - "/cn/enterprise/3.0/v3/actions": "/cn/enterprise-server@3.0/rest/reference/actions", - "/cn/enterprise/v3/actions": "/cn/enterprise-server@latest/rest/reference/actions", - "/cn/free-pro-team@latest/rest/reference/activity": "/cn/rest/reference/activity", - "/cn/v3/activity": "/cn/rest/reference/activity", - "/cn/free-pro-team@latest/v3/activity": "/cn/rest/reference/activity", - "/cn/enterprise/3.0/rest/reference/activity": "/cn/enterprise-server@3.0/rest/reference/activity", - "/cn/enterprise/rest/reference/activity": "/cn/enterprise-server@latest/rest/reference/activity", - "/cn/enterprise-server@3.0/v3/activity": "/cn/enterprise-server@3.0/rest/reference/activity", - "/cn/enterprise/3.0/v3/activity": "/cn/enterprise-server@3.0/rest/reference/activity", - "/cn/enterprise/v3/activity": "/cn/enterprise-server@latest/rest/reference/activity", - "/cn/enterprise/2.20/rest/reference/activity": "/cn/enterprise-server@2.20/rest/reference/activity", - "/cn/enterprise-server@2.20/v3/activity": "/cn/enterprise-server@2.20/rest/reference/activity", - "/cn/enterprise/2.20/v3/activity": "/cn/enterprise-server@2.20/rest/reference/activity", - "/cn/github-ae@latest/v3/activity": "/cn/github-ae@latest/rest/reference/activity", - "/cn/free-pro-team@latest/rest/reference/apps": "/cn/rest/reference/apps", - "/cn/v3/apps": "/cn/rest/reference/apps", - "/cn/free-pro-team@latest/v3/apps": "/cn/rest/reference/apps", - "/cn/enterprise/3.0/rest/reference/apps": "/cn/enterprise-server@3.0/rest/reference/apps", - "/cn/enterprise/rest/reference/apps": "/cn/enterprise-server@latest/rest/reference/apps", - "/cn/enterprise-server@3.0/v3/apps": "/cn/enterprise-server@3.0/rest/reference/apps", - "/cn/enterprise/3.0/v3/apps": "/cn/enterprise-server@3.0/rest/reference/apps", - "/cn/enterprise/v3/apps": "/cn/enterprise-server@latest/rest/reference/apps", - "/cn/enterprise/2.20/rest/reference/apps": "/cn/enterprise-server@2.20/rest/reference/apps", - "/cn/enterprise-server@2.20/v3/apps": "/cn/enterprise-server@2.20/rest/reference/apps", - "/cn/enterprise/2.20/v3/apps": "/cn/enterprise-server@2.20/rest/reference/apps", - "/cn/github-ae@latest/v3/apps": "/cn/github-ae@latest/rest/reference/apps", - "/cn/free-pro-team@latest/rest/reference/billing": "/cn/rest/reference/billing", - "/cn/free-pro-team@latest/rest/reference/checks": "/cn/rest/reference/checks", - "/cn/v3/checks": "/cn/rest/reference/checks", - "/cn/free-pro-team@latest/v3/checks": "/cn/rest/reference/checks", - "/cn/enterprise/3.0/rest/reference/checks": "/cn/enterprise-server@3.0/rest/reference/checks", - "/cn/enterprise/rest/reference/checks": "/cn/enterprise-server@latest/rest/reference/checks", - "/cn/enterprise-server@3.0/v3/checks": "/cn/enterprise-server@3.0/rest/reference/checks", - "/cn/enterprise/3.0/v3/checks": "/cn/enterprise-server@3.0/rest/reference/checks", - "/cn/enterprise/v3/checks": "/cn/enterprise-server@latest/rest/reference/checks", - "/cn/enterprise/2.20/rest/reference/checks": "/cn/enterprise-server@2.20/rest/reference/checks", - "/cn/enterprise-server@2.20/v3/checks": "/cn/enterprise-server@2.20/rest/reference/checks", - "/cn/enterprise/2.20/v3/checks": "/cn/enterprise-server@2.20/rest/reference/checks", - "/cn/github-ae@latest/v3/checks": "/cn/github-ae@latest/rest/reference/checks", - "/cn/free-pro-team@latest/rest/reference/code-scanning": "/cn/rest/reference/code-scanning", - "/cn/v3/code-scanning": "/cn/rest/reference/code-scanning", - "/cn/free-pro-team@latest/v3/code-scanning": "/cn/rest/reference/code-scanning", - "/cn/enterprise/3.0/rest/reference/code-scanning": "/cn/enterprise-server@3.0/rest/reference/code-scanning", - "/cn/enterprise/rest/reference/code-scanning": "/cn/enterprise-server@latest/rest/reference/code-scanning", - "/cn/enterprise-server@3.0/v3/code-scanning": "/cn/enterprise-server@3.0/rest/reference/code-scanning", - "/cn/enterprise/3.0/v3/code-scanning": "/cn/enterprise-server@3.0/rest/reference/code-scanning", - "/cn/enterprise/v3/code-scanning": "/cn/enterprise-server@latest/rest/reference/code-scanning", - "/cn/free-pro-team@latest/rest/reference/codes-of-conduct": "/cn/rest/reference/codes-of-conduct", - "/cn/v3/codes_of_conduct": "/cn/rest/reference/codes-of-conduct", - "/cn/free-pro-team@latest/v3/codes_of_conduct": "/cn/rest/reference/codes-of-conduct", - "/cn/v3/codes-of-conduct": "/cn/rest/reference/codes-of-conduct", - "/cn/free-pro-team@latest/v3/codes-of-conduct": "/cn/rest/reference/codes-of-conduct", - "/cn/enterprise/3.0/rest/reference/codes-of-conduct": "/cn/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/cn/enterprise/rest/reference/codes-of-conduct": "/cn/enterprise-server@latest/rest/reference/codes-of-conduct", - "/cn/enterprise-server@3.0/v3/codes_of_conduct": "/cn/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/cn/enterprise/3.0/v3/codes_of_conduct": "/cn/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/cn/enterprise/v3/codes_of_conduct": "/cn/enterprise-server@latest/rest/reference/codes-of-conduct", - "/cn/enterprise-server@3.0/v3/codes-of-conduct": "/cn/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/cn/enterprise/3.0/v3/codes-of-conduct": "/cn/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/cn/enterprise/v3/codes-of-conduct": "/cn/enterprise-server@latest/rest/reference/codes-of-conduct", - "/cn/enterprise/2.20/rest/reference/codes-of-conduct": "/cn/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/cn/enterprise-server@2.20/v3/codes_of_conduct": "/cn/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/cn/enterprise/2.20/v3/codes_of_conduct": "/cn/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/cn/enterprise-server@2.20/v3/codes-of-conduct": "/cn/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/cn/enterprise/2.20/v3/codes-of-conduct": "/cn/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/cn/github-ae@latest/v3/codes_of_conduct": "/cn/github-ae@latest/rest/reference/codes-of-conduct", - "/cn/github-ae@latest/v3/codes-of-conduct": "/cn/github-ae@latest/rest/reference/codes-of-conduct", - "/cn/free-pro-team@latest/rest/reference/emojis": "/cn/rest/reference/emojis", - "/cn/v3/emojis": "/cn/rest/reference/emojis", - "/cn/free-pro-team@latest/v3/emojis": "/cn/rest/reference/emojis", - "/cn/v3/misc": "/cn/rest/reference/emojis", - "/cn/free-pro-team@latest/v3/misc": "/cn/rest/reference/emojis", - "/cn/enterprise/3.0/rest/reference/emojis": "/cn/enterprise-server@3.0/rest/reference/emojis", - "/cn/enterprise/rest/reference/emojis": "/cn/enterprise-server@latest/rest/reference/emojis", - "/cn/enterprise-server@3.0/v3/emojis": "/cn/enterprise-server@3.0/rest/reference/emojis", - "/cn/enterprise/3.0/v3/emojis": "/cn/enterprise-server@3.0/rest/reference/emojis", - "/cn/enterprise/v3/emojis": "/cn/enterprise-server@latest/rest/reference/emojis", - "/cn/enterprise-server@3.0/v3/misc": "/cn/enterprise-server@3.0/rest/reference/emojis", - "/cn/enterprise/3.0/v3/misc": "/cn/enterprise-server@3.0/rest/reference/emojis", - "/cn/enterprise/v3/misc": "/cn/enterprise-server@latest/rest/reference/emojis", - "/cn/enterprise/2.20/rest/reference/emojis": "/cn/enterprise-server@2.20/rest/reference/emojis", - "/cn/enterprise-server@2.20/v3/emojis": "/cn/enterprise-server@2.20/rest/reference/emojis", - "/cn/enterprise/2.20/v3/emojis": "/cn/enterprise-server@2.20/rest/reference/emojis", - "/cn/enterprise-server@2.20/v3/misc": "/cn/enterprise-server@2.20/rest/reference/emojis", - "/cn/enterprise/2.20/v3/misc": "/cn/enterprise-server@2.20/rest/reference/emojis", - "/cn/github-ae@latest/v3/emojis": "/cn/github-ae@latest/rest/reference/emojis", - "/cn/github-ae@latest/v3/misc": "/cn/github-ae@latest/rest/reference/emojis", - "/cn/free-pro-team@latest/rest/reference/enterprise-admin": "/cn/rest/reference/enterprise-admin", - "/cn/v3/enterprise-admin": "/cn/rest/reference/enterprise-admin", - "/cn/free-pro-team@latest/v3/enterprise-admin": "/cn/rest/reference/enterprise-admin", - "/cn/v3/enterprise": "/cn/rest/reference/enterprise-admin", - "/cn/free-pro-team@latest/v3/enterprise": "/cn/rest/reference/enterprise-admin", - "/cn/enterprise/3.0/rest/reference/enterprise-admin": "/cn/enterprise-server@3.0/rest/reference/enterprise-admin", - "/cn/enterprise/rest/reference/enterprise-admin": "/cn/enterprise-server@latest/rest/reference/enterprise-admin", - "/cn/enterprise-server@3.0/v3/enterprise-admin": "/cn/enterprise-server@3.0/rest/reference/enterprise-admin", - "/cn/enterprise/3.0/v3/enterprise-admin": "/cn/enterprise-server@3.0/rest/reference/enterprise-admin", - "/cn/enterprise/v3/enterprise-admin": "/cn/enterprise-server@latest/rest/reference/enterprise-admin", - "/cn/enterprise-server@3.0/v3/enterprise": "/cn/enterprise-server@3.0/rest/reference/enterprise-admin", - "/cn/enterprise/3.0/v3/enterprise": "/cn/enterprise-server@3.0/rest/reference/enterprise-admin", - "/cn/enterprise/v3/enterprise": "/cn/enterprise-server@latest/rest/reference/enterprise-admin", - "/cn/enterprise/2.20/rest/reference/enterprise-admin": "/cn/enterprise-server@2.20/rest/reference/enterprise-admin", - "/cn/enterprise-server@2.20/v3/enterprise-admin": "/cn/enterprise-server@2.20/rest/reference/enterprise-admin", - "/cn/enterprise/2.20/v3/enterprise-admin": "/cn/enterprise-server@2.20/rest/reference/enterprise-admin", - "/cn/enterprise-server@2.20/v3/enterprise": "/cn/enterprise-server@2.20/rest/reference/enterprise-admin", - "/cn/enterprise/2.20/v3/enterprise": "/cn/enterprise-server@2.20/rest/reference/enterprise-admin", - "/cn/github-ae@latest/v3/enterprise-admin": "/cn/github-ae@latest/rest/reference/enterprise-admin", - "/cn/github-ae@latest/v3/enterprise": "/cn/github-ae@latest/rest/reference/enterprise-admin", - "/cn/free-pro-team@latest/rest/reference/gists": "/cn/rest/reference/gists", - "/cn/v3/gists": "/cn/rest/reference/gists", - "/cn/free-pro-team@latest/v3/gists": "/cn/rest/reference/gists", - "/cn/enterprise/3.0/rest/reference/gists": "/cn/enterprise-server@3.0/rest/reference/gists", - "/cn/enterprise/rest/reference/gists": "/cn/enterprise-server@latest/rest/reference/gists", - "/cn/enterprise-server@3.0/v3/gists": "/cn/enterprise-server@3.0/rest/reference/gists", - "/cn/enterprise/3.0/v3/gists": "/cn/enterprise-server@3.0/rest/reference/gists", - "/cn/enterprise/v3/gists": "/cn/enterprise-server@latest/rest/reference/gists", - "/cn/enterprise/2.20/rest/reference/gists": "/cn/enterprise-server@2.20/rest/reference/gists", - "/cn/enterprise-server@2.20/v3/gists": "/cn/enterprise-server@2.20/rest/reference/gists", - "/cn/enterprise/2.20/v3/gists": "/cn/enterprise-server@2.20/rest/reference/gists", - "/cn/github-ae@latest/v3/gists": "/cn/github-ae@latest/rest/reference/gists", - "/cn/free-pro-team@latest/rest/reference/git": "/cn/rest/reference/git", - "/cn/v3/git": "/cn/rest/reference/git", - "/cn/free-pro-team@latest/v3/git": "/cn/rest/reference/git", - "/cn/enterprise/3.0/rest/reference/git": "/cn/enterprise-server@3.0/rest/reference/git", - "/cn/enterprise/rest/reference/git": "/cn/enterprise-server@latest/rest/reference/git", - "/cn/enterprise-server@3.0/v3/git": "/cn/enterprise-server@3.0/rest/reference/git", - "/cn/enterprise/3.0/v3/git": "/cn/enterprise-server@3.0/rest/reference/git", - "/cn/enterprise/v3/git": "/cn/enterprise-server@latest/rest/reference/git", - "/cn/enterprise/2.20/rest/reference/git": "/cn/enterprise-server@2.20/rest/reference/git", - "/cn/enterprise-server@2.20/v3/git": "/cn/enterprise-server@2.20/rest/reference/git", - "/cn/enterprise/2.20/v3/git": "/cn/enterprise-server@2.20/rest/reference/git", - "/cn/github-ae@latest/v3/git": "/cn/github-ae@latest/rest/reference/git", - "/cn/free-pro-team@latest/rest/reference/gitignore": "/cn/rest/reference/gitignore", - "/cn/v3/gitignore": "/cn/rest/reference/gitignore", - "/cn/free-pro-team@latest/v3/gitignore": "/cn/rest/reference/gitignore", - "/cn/enterprise/3.0/rest/reference/gitignore": "/cn/enterprise-server@3.0/rest/reference/gitignore", - "/cn/enterprise/rest/reference/gitignore": "/cn/enterprise-server@latest/rest/reference/gitignore", - "/cn/enterprise-server@3.0/v3/gitignore": "/cn/enterprise-server@3.0/rest/reference/gitignore", - "/cn/enterprise/3.0/v3/gitignore": "/cn/enterprise-server@3.0/rest/reference/gitignore", - "/cn/enterprise/v3/gitignore": "/cn/enterprise-server@latest/rest/reference/gitignore", - "/cn/enterprise/2.20/rest/reference/gitignore": "/cn/enterprise-server@2.20/rest/reference/gitignore", - "/cn/enterprise-server@2.20/v3/gitignore": "/cn/enterprise-server@2.20/rest/reference/gitignore", - "/cn/enterprise/2.20/v3/gitignore": "/cn/enterprise-server@2.20/rest/reference/gitignore", - "/cn/github-ae@latest/v3/gitignore": "/cn/github-ae@latest/rest/reference/gitignore", - "/cn/free-pro-team@latest/rest/reference": "/cn/rest/reference", - "/cn/enterprise/3.0/rest/reference": "/cn/enterprise-server@3.0/rest/reference", - "/cn/enterprise/rest/reference": "/cn/enterprise-server@latest/rest/reference", - "/cn/enterprise/2.20/rest/reference": "/cn/enterprise-server@2.20/rest/reference", - "/cn/free-pro-team@latest/rest/reference/interactions": "/cn/rest/reference/interactions", - "/cn/v3/interactions": "/cn/rest/reference/interactions", - "/cn/free-pro-team@latest/v3/interactions": "/cn/rest/reference/interactions", - "/cn/free-pro-team@latest/rest/reference/issues": "/cn/rest/reference/issues", - "/cn/v3/issues": "/cn/rest/reference/issues", - "/cn/free-pro-team@latest/v3/issues": "/cn/rest/reference/issues", - "/cn/enterprise/3.0/rest/reference/issues": "/cn/enterprise-server@3.0/rest/reference/issues", - "/cn/enterprise/rest/reference/issues": "/cn/enterprise-server@latest/rest/reference/issues", - "/cn/enterprise-server@3.0/v3/issues": "/cn/enterprise-server@3.0/rest/reference/issues", - "/cn/enterprise/3.0/v3/issues": "/cn/enterprise-server@3.0/rest/reference/issues", - "/cn/enterprise/v3/issues": "/cn/enterprise-server@latest/rest/reference/issues", - "/cn/enterprise/2.20/rest/reference/issues": "/cn/enterprise-server@2.20/rest/reference/issues", - "/cn/enterprise-server@2.20/v3/issues": "/cn/enterprise-server@2.20/rest/reference/issues", - "/cn/enterprise/2.20/v3/issues": "/cn/enterprise-server@2.20/rest/reference/issues", - "/cn/github-ae@latest/v3/issues": "/cn/github-ae@latest/rest/reference/issues", - "/cn/free-pro-team@latest/rest/reference/licenses": "/cn/rest/reference/licenses", - "/cn/v3/licenses": "/cn/rest/reference/licenses", - "/cn/free-pro-team@latest/v3/licenses": "/cn/rest/reference/licenses", - "/cn/enterprise/3.0/rest/reference/licenses": "/cn/enterprise-server@3.0/rest/reference/licenses", - "/cn/enterprise/rest/reference/licenses": "/cn/enterprise-server@latest/rest/reference/licenses", - "/cn/enterprise-server@3.0/v3/licenses": "/cn/enterprise-server@3.0/rest/reference/licenses", - "/cn/enterprise/3.0/v3/licenses": "/cn/enterprise-server@3.0/rest/reference/licenses", - "/cn/enterprise/v3/licenses": "/cn/enterprise-server@latest/rest/reference/licenses", - "/cn/enterprise/2.20/rest/reference/licenses": "/cn/enterprise-server@2.20/rest/reference/licenses", - "/cn/enterprise-server@2.20/v3/licenses": "/cn/enterprise-server@2.20/rest/reference/licenses", - "/cn/enterprise/2.20/v3/licenses": "/cn/enterprise-server@2.20/rest/reference/licenses", - "/cn/github-ae@latest/v3/licenses": "/cn/github-ae@latest/rest/reference/licenses", - "/cn/free-pro-team@latest/rest/reference/markdown": "/cn/rest/reference/markdown", - "/cn/v3/markdown": "/cn/rest/reference/markdown", - "/cn/free-pro-team@latest/v3/markdown": "/cn/rest/reference/markdown", - "/cn/enterprise/3.0/rest/reference/markdown": "/cn/enterprise-server@3.0/rest/reference/markdown", - "/cn/enterprise/rest/reference/markdown": "/cn/enterprise-server@latest/rest/reference/markdown", - "/cn/enterprise-server@3.0/v3/markdown": "/cn/enterprise-server@3.0/rest/reference/markdown", - "/cn/enterprise/3.0/v3/markdown": "/cn/enterprise-server@3.0/rest/reference/markdown", - "/cn/enterprise/v3/markdown": "/cn/enterprise-server@latest/rest/reference/markdown", - "/cn/enterprise/2.20/rest/reference/markdown": "/cn/enterprise-server@2.20/rest/reference/markdown", - "/cn/enterprise-server@2.20/v3/markdown": "/cn/enterprise-server@2.20/rest/reference/markdown", - "/cn/enterprise/2.20/v3/markdown": "/cn/enterprise-server@2.20/rest/reference/markdown", - "/cn/github-ae@latest/v3/markdown": "/cn/github-ae@latest/rest/reference/markdown", - "/cn/free-pro-team@latest/rest/reference/meta": "/cn/rest/reference/meta", - "/cn/v3/meta": "/cn/rest/reference/meta", - "/cn/free-pro-team@latest/v3/meta": "/cn/rest/reference/meta", - "/cn/enterprise/3.0/rest/reference/meta": "/cn/enterprise-server@3.0/rest/reference/meta", - "/cn/enterprise/rest/reference/meta": "/cn/enterprise-server@latest/rest/reference/meta", - "/cn/enterprise-server@3.0/v3/meta": "/cn/enterprise-server@3.0/rest/reference/meta", - "/cn/enterprise/3.0/v3/meta": "/cn/enterprise-server@3.0/rest/reference/meta", - "/cn/enterprise/v3/meta": "/cn/enterprise-server@latest/rest/reference/meta", - "/cn/enterprise/2.20/rest/reference/meta": "/cn/enterprise-server@2.20/rest/reference/meta", - "/cn/enterprise-server@2.20/v3/meta": "/cn/enterprise-server@2.20/rest/reference/meta", - "/cn/enterprise/2.20/v3/meta": "/cn/enterprise-server@2.20/rest/reference/meta", - "/cn/github-ae@latest/v3/meta": "/cn/github-ae@latest/rest/reference/meta", - "/cn/free-pro-team@latest/rest/reference/migrations": "/cn/rest/reference/migrations", - "/cn/v3/migrations": "/cn/rest/reference/migrations", - "/cn/free-pro-team@latest/v3/migrations": "/cn/rest/reference/migrations", - "/cn/v3/migration": "/cn/rest/reference/migrations", - "/cn/free-pro-team@latest/v3/migration": "/cn/rest/reference/migrations", - "/cn/v3/migration/migrations": "/cn/rest/reference/migrations", - "/cn/free-pro-team@latest/v3/migration/migrations": "/cn/rest/reference/migrations", - "/cn/enterprise/3.0/rest/reference/oauth-authorizations": "/cn/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/cn/enterprise/rest/reference/oauth-authorizations": "/cn/enterprise-server@latest/rest/reference/oauth-authorizations", - "/cn/enterprise-server@3.0/v3/oauth_authorizations": "/cn/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/cn/enterprise/3.0/v3/oauth_authorizations": "/cn/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/cn/enterprise/v3/oauth_authorizations": "/cn/enterprise-server@latest/rest/reference/oauth-authorizations", - "/cn/enterprise-server@3.0/v3/oauth-authorizations": "/cn/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/cn/enterprise/3.0/v3/oauth-authorizations": "/cn/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/cn/enterprise/v3/oauth-authorizations": "/cn/enterprise-server@latest/rest/reference/oauth-authorizations", - "/cn/enterprise/2.20/rest/reference/oauth-authorizations": "/cn/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/cn/enterprise-server@2.20/v3/oauth_authorizations": "/cn/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/cn/enterprise/2.20/v3/oauth_authorizations": "/cn/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/cn/enterprise-server@2.20/v3/oauth-authorizations": "/cn/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/cn/enterprise/2.20/v3/oauth-authorizations": "/cn/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/cn/free-pro-team@latest/rest/reference/orgs": "/cn/rest/reference/orgs", - "/cn/v3/orgs": "/cn/rest/reference/orgs", - "/cn/free-pro-team@latest/v3/orgs": "/cn/rest/reference/orgs", - "/cn/enterprise/3.0/rest/reference/orgs": "/cn/enterprise-server@3.0/rest/reference/orgs", - "/cn/enterprise/rest/reference/orgs": "/cn/enterprise-server@latest/rest/reference/orgs", - "/cn/enterprise-server@3.0/v3/orgs": "/cn/enterprise-server@3.0/rest/reference/orgs", - "/cn/enterprise/3.0/v3/orgs": "/cn/enterprise-server@3.0/rest/reference/orgs", - "/cn/enterprise/v3/orgs": "/cn/enterprise-server@latest/rest/reference/orgs", - "/cn/enterprise/2.20/rest/reference/orgs": "/cn/enterprise-server@2.20/rest/reference/orgs", - "/cn/enterprise-server@2.20/v3/orgs": "/cn/enterprise-server@2.20/rest/reference/orgs", - "/cn/enterprise/2.20/v3/orgs": "/cn/enterprise-server@2.20/rest/reference/orgs", - "/cn/github-ae@latest/v3/orgs": "/cn/github-ae@latest/rest/reference/orgs", - "/cn/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/cn/rest/reference/permissions-required-for-github-apps", - "/cn/v3/apps/permissions": "/cn/rest/reference/permissions-required-for-github-apps", - "/cn/free-pro-team@latest/v3/apps/permissions": "/cn/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/cn/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise/rest/reference/permissions-required-for-github-apps": "/cn/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise-server@3.0/v3/apps/permissions": "/cn/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise/3.0/v3/apps/permissions": "/cn/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise/v3/apps/permissions": "/cn/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/cn/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise-server@2.20/v3/apps/permissions": "/cn/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/cn/enterprise/2.20/v3/apps/permissions": "/cn/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/cn/github-ae@latest/v3/apps/permissions": "/cn/github-ae@latest/rest/reference/permissions-required-for-github-apps", - "/cn/free-pro-team@latest/rest/reference/projects": "/cn/rest/reference/projects", - "/cn/v3/projects": "/cn/rest/reference/projects", - "/cn/free-pro-team@latest/v3/projects": "/cn/rest/reference/projects", - "/cn/enterprise/3.0/rest/reference/projects": "/cn/enterprise-server@3.0/rest/reference/projects", - "/cn/enterprise/rest/reference/projects": "/cn/enterprise-server@latest/rest/reference/projects", - "/cn/enterprise-server@3.0/v3/projects": "/cn/enterprise-server@3.0/rest/reference/projects", - "/cn/enterprise/3.0/v3/projects": "/cn/enterprise-server@3.0/rest/reference/projects", - "/cn/enterprise/v3/projects": "/cn/enterprise-server@latest/rest/reference/projects", - "/cn/enterprise/2.20/rest/reference/projects": "/cn/enterprise-server@2.20/rest/reference/projects", - "/cn/enterprise-server@2.20/v3/projects": "/cn/enterprise-server@2.20/rest/reference/projects", - "/cn/enterprise/2.20/v3/projects": "/cn/enterprise-server@2.20/rest/reference/projects", - "/cn/github-ae@latest/v3/projects": "/cn/github-ae@latest/rest/reference/projects", - "/cn/free-pro-team@latest/rest/reference/pulls": "/cn/rest/reference/pulls", - "/cn/v3/pulls": "/cn/rest/reference/pulls", - "/cn/free-pro-team@latest/v3/pulls": "/cn/rest/reference/pulls", - "/cn/enterprise/3.0/rest/reference/pulls": "/cn/enterprise-server@3.0/rest/reference/pulls", - "/cn/enterprise/rest/reference/pulls": "/cn/enterprise-server@latest/rest/reference/pulls", - "/cn/enterprise-server@3.0/v3/pulls": "/cn/enterprise-server@3.0/rest/reference/pulls", - "/cn/enterprise/3.0/v3/pulls": "/cn/enterprise-server@3.0/rest/reference/pulls", - "/cn/enterprise/v3/pulls": "/cn/enterprise-server@latest/rest/reference/pulls", - "/cn/enterprise/2.20/rest/reference/pulls": "/cn/enterprise-server@2.20/rest/reference/pulls", - "/cn/enterprise-server@2.20/v3/pulls": "/cn/enterprise-server@2.20/rest/reference/pulls", - "/cn/enterprise/2.20/v3/pulls": "/cn/enterprise-server@2.20/rest/reference/pulls", - "/cn/github-ae@latest/v3/pulls": "/cn/github-ae@latest/rest/reference/pulls", - "/cn/free-pro-team@latest/rest/reference/rate-limit": "/cn/rest/reference/rate-limit", - "/cn/v3/rate_limit": "/cn/rest/reference/rate-limit", - "/cn/free-pro-team@latest/v3/rate_limit": "/cn/rest/reference/rate-limit", - "/cn/v3/rate-limit": "/cn/rest/reference/rate-limit", - "/cn/free-pro-team@latest/v3/rate-limit": "/cn/rest/reference/rate-limit", - "/cn/enterprise/3.0/rest/reference/rate-limit": "/cn/enterprise-server@3.0/rest/reference/rate-limit", - "/cn/enterprise/rest/reference/rate-limit": "/cn/enterprise-server@latest/rest/reference/rate-limit", - "/cn/enterprise-server@3.0/v3/rate_limit": "/cn/enterprise-server@3.0/rest/reference/rate-limit", - "/cn/enterprise/3.0/v3/rate_limit": "/cn/enterprise-server@3.0/rest/reference/rate-limit", - "/cn/enterprise/v3/rate_limit": "/cn/enterprise-server@latest/rest/reference/rate-limit", - "/cn/enterprise-server@3.0/v3/rate-limit": "/cn/enterprise-server@3.0/rest/reference/rate-limit", - "/cn/enterprise/3.0/v3/rate-limit": "/cn/enterprise-server@3.0/rest/reference/rate-limit", - "/cn/enterprise/v3/rate-limit": "/cn/enterprise-server@latest/rest/reference/rate-limit", - "/cn/enterprise/2.20/rest/reference/rate-limit": "/cn/enterprise-server@2.20/rest/reference/rate-limit", - "/cn/enterprise-server@2.20/v3/rate_limit": "/cn/enterprise-server@2.20/rest/reference/rate-limit", - "/cn/enterprise/2.20/v3/rate_limit": "/cn/enterprise-server@2.20/rest/reference/rate-limit", - "/cn/enterprise-server@2.20/v3/rate-limit": "/cn/enterprise-server@2.20/rest/reference/rate-limit", - "/cn/enterprise/2.20/v3/rate-limit": "/cn/enterprise-server@2.20/rest/reference/rate-limit", - "/cn/github-ae@latest/v3/rate_limit": "/cn/github-ae@latest/rest/reference/rate-limit", - "/cn/github-ae@latest/v3/rate-limit": "/cn/github-ae@latest/rest/reference/rate-limit", - "/cn/free-pro-team@latest/rest/reference/reactions": "/cn/rest/reference/reactions", - "/cn/v3/reactions": "/cn/rest/reference/reactions", - "/cn/free-pro-team@latest/v3/reactions": "/cn/rest/reference/reactions", - "/cn/enterprise/3.0/rest/reference/reactions": "/cn/enterprise-server@3.0/rest/reference/reactions", - "/cn/enterprise/rest/reference/reactions": "/cn/enterprise-server@latest/rest/reference/reactions", - "/cn/enterprise-server@3.0/v3/reactions": "/cn/enterprise-server@3.0/rest/reference/reactions", - "/cn/enterprise/3.0/v3/reactions": "/cn/enterprise-server@3.0/rest/reference/reactions", - "/cn/enterprise/v3/reactions": "/cn/enterprise-server@latest/rest/reference/reactions", - "/cn/enterprise/2.20/rest/reference/reactions": "/cn/enterprise-server@2.20/rest/reference/reactions", - "/cn/enterprise-server@2.20/v3/reactions": "/cn/enterprise-server@2.20/rest/reference/reactions", - "/cn/enterprise/2.20/v3/reactions": "/cn/enterprise-server@2.20/rest/reference/reactions", - "/cn/github-ae@latest/v3/reactions": "/cn/github-ae@latest/rest/reference/reactions", - "/cn/free-pro-team@latest/rest/reference/repos": "/cn/rest/reference/repos", - "/cn/v3/repos": "/cn/rest/reference/repos", - "/cn/free-pro-team@latest/v3/repos": "/cn/rest/reference/repos", - "/cn/enterprise/3.0/rest/reference/repos": "/cn/enterprise-server@3.0/rest/reference/repos", - "/cn/enterprise/rest/reference/repos": "/cn/enterprise-server@latest/rest/reference/repos", - "/cn/enterprise-server@3.0/v3/repos": "/cn/enterprise-server@3.0/rest/reference/repos", - "/cn/enterprise/3.0/v3/repos": "/cn/enterprise-server@3.0/rest/reference/repos", - "/cn/enterprise/v3/repos": "/cn/enterprise-server@latest/rest/reference/repos", - "/cn/enterprise/2.20/rest/reference/repos": "/cn/enterprise-server@2.20/rest/reference/repos", - "/cn/enterprise-server@2.20/v3/repos": "/cn/enterprise-server@2.20/rest/reference/repos", - "/cn/enterprise/2.20/v3/repos": "/cn/enterprise-server@2.20/rest/reference/repos", - "/cn/github-ae@latest/v3/repos": "/cn/github-ae@latest/rest/reference/repos", - "/cn/free-pro-team@latest/rest/reference/scim": "/cn/rest/reference/scim", - "/cn/v3/scim": "/cn/rest/reference/scim", - "/cn/free-pro-team@latest/v3/scim": "/cn/rest/reference/scim", - "/cn/free-pro-team@latest/rest/reference/search": "/cn/rest/reference/search", - "/cn/v3/search": "/cn/rest/reference/search", - "/cn/free-pro-team@latest/v3/search": "/cn/rest/reference/search", - "/cn/enterprise/3.0/rest/reference/search": "/cn/enterprise-server@3.0/rest/reference/search", - "/cn/enterprise/rest/reference/search": "/cn/enterprise-server@latest/rest/reference/search", - "/cn/enterprise-server@3.0/v3/search": "/cn/enterprise-server@3.0/rest/reference/search", - "/cn/enterprise/3.0/v3/search": "/cn/enterprise-server@3.0/rest/reference/search", - "/cn/enterprise/v3/search": "/cn/enterprise-server@latest/rest/reference/search", - "/cn/enterprise/2.20/rest/reference/search": "/cn/enterprise-server@2.20/rest/reference/search", - "/cn/enterprise-server@2.20/v3/search": "/cn/enterprise-server@2.20/rest/reference/search", - "/cn/enterprise/2.20/v3/search": "/cn/enterprise-server@2.20/rest/reference/search", - "/cn/github-ae@latest/v3/search": "/cn/github-ae@latest/rest/reference/search", - "/cn/free-pro-team@latest/rest/reference/secret-scanning": "/cn/rest/reference/secret-scanning", - "/cn/free-pro-team@latest/rest/reference/teams": "/cn/rest/reference/teams", - "/cn/v3/teams": "/cn/rest/reference/teams", - "/cn/free-pro-team@latest/v3/teams": "/cn/rest/reference/teams", - "/cn/enterprise/3.0/rest/reference/teams": "/cn/enterprise-server@3.0/rest/reference/teams", - "/cn/enterprise/rest/reference/teams": "/cn/enterprise-server@latest/rest/reference/teams", - "/cn/enterprise-server@3.0/v3/teams": "/cn/enterprise-server@3.0/rest/reference/teams", - "/cn/enterprise/3.0/v3/teams": "/cn/enterprise-server@3.0/rest/reference/teams", - "/cn/enterprise/v3/teams": "/cn/enterprise-server@latest/rest/reference/teams", - "/cn/enterprise/2.20/rest/reference/teams": "/cn/enterprise-server@2.20/rest/reference/teams", - "/cn/enterprise-server@2.20/v3/teams": "/cn/enterprise-server@2.20/rest/reference/teams", - "/cn/enterprise/2.20/v3/teams": "/cn/enterprise-server@2.20/rest/reference/teams", - "/cn/github-ae@latest/v3/teams": "/cn/github-ae@latest/rest/reference/teams", - "/cn/free-pro-team@latest/rest/reference/users": "/cn/rest/reference/users", - "/cn/v3/users": "/cn/rest/reference/users", - "/cn/free-pro-team@latest/v3/users": "/cn/rest/reference/users", - "/cn/enterprise/3.0/rest/reference/users": "/cn/enterprise-server@3.0/rest/reference/users", - "/cn/enterprise/rest/reference/users": "/cn/enterprise-server@latest/rest/reference/users", - "/cn/enterprise-server@3.0/v3/users": "/cn/enterprise-server@3.0/rest/reference/users", - "/cn/enterprise/3.0/v3/users": "/cn/enterprise-server@3.0/rest/reference/users", - "/cn/enterprise/v3/users": "/cn/enterprise-server@latest/rest/reference/users", - "/cn/enterprise/2.20/rest/reference/users": "/cn/enterprise-server@2.20/rest/reference/users", - "/cn/enterprise-server@2.20/v3/users": "/cn/enterprise-server@2.20/rest/reference/users", - "/cn/enterprise/2.20/v3/users": "/cn/enterprise-server@2.20/rest/reference/users", - "/cn/github-ae@latest/v3/users": "/cn/github-ae@latest/rest/reference/users", - "/ja/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/3.0/admin/articles/restoring-github-enterprise": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/admin/articles/restoring-github-enterprise": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/admin/articles/restoring-github-enterprise": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/3.0/admin/articles/restoring-enterprise-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/admin/articles/restoring-enterprise-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/admin/articles/restoring-enterprise-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise-server@3.0/admin/articles/restoring-repository-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/3.0/admin/articles/restoring-repository-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/admin/articles/restoring-repository-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/admin/articles/restoring-repository-data": "/ja/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/ja/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/2.20/admin/articles/restoring-github-enterprise": "/ja/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/ja/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/2.20/admin/articles/restoring-enterprise-data": "/ja/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise-server@2.20/admin/articles/restoring-repository-data": "/ja/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise/2.20/admin/articles/restoring-repository-data": "/ja/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/ja/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/ja/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/ja/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/ja/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/ja/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/ja/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/ja/github-ae@latest/admin/articles/restricting-ssh-access-to-specific-hosts": "/ja/github-ae@latest/admin/configuration/configuring-your-enterprise", - "/ja/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/github-ae@latest/admin/user-management/restricting-repository-creation-in-your-instance": "/ja/github-ae@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/ja/v3/oauth": "/ja/developers/apps/authorizing-oauth-apps", - "/ja/free-pro-team@latest/v3/oauth": "/ja/developers/apps/authorizing-oauth-apps", - "/ja/enterprise-server@3.0/v3/oauth": "/ja/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/ja/enterprise/3.0/v3/oauth": "/ja/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/ja/enterprise/v3/oauth": "/ja/enterprise-server@latest/developers/apps/authorizing-oauth-apps", - "/ja/enterprise-server@2.20/v3/oauth": "/ja/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/ja/enterprise/2.20/v3/oauth": "/ja/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/ja/github-ae@latest/v3/oauth": "/ja/github-ae@latest/developers/apps/authorizing-oauth-apps", - "/ja/v3/integrations": "/ja/developers/apps", - "/ja/free-pro-team@latest/v3/integrations": "/ja/developers/apps", - "/ja/enterprise-server@3.0/v3/integrations": "/ja/enterprise-server@3.0/developers/apps", - "/ja/enterprise/3.0/v3/integrations": "/ja/enterprise-server@3.0/developers/apps", - "/ja/enterprise/v3/integrations": "/ja/enterprise-server@latest/developers/apps", - "/ja/enterprise-server@2.20/v3/integrations": "/ja/enterprise-server@2.20/developers/apps", - "/ja/enterprise/2.20/v3/integrations": "/ja/enterprise-server@2.20/developers/apps", - "/ja/github-ae@latest/v3/integrations": "/ja/github-ae@latest/developers/apps", - "/ja/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/ja/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/ja/v3/versions": "/ja/developers/overview/about-githubs-apis", - "/ja/free-pro-team@latest/v3/versions": "/ja/developers/overview/about-githubs-apis", - "/ja/enterprise-server@3.0/v3/versions": "/ja/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/ja/enterprise/3.0/v3/versions": "/ja/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/ja/enterprise/v3/versions": "/ja/enterprise-server@latest/developers/overview/about-githubs-apis", - "/ja/enterprise-server@2.20/v3/versions": "/ja/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/ja/enterprise/2.20/v3/versions": "/ja/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/ja/github-ae@latest/v3/versions": "/ja/github-ae@latest/developers/overview/about-githubs-apis", - "/ja/v3/guides/managing-deploy-keys": "/ja/developers/overview/managing-deploy-keys", - "/ja/free-pro-team@latest/v3/guides/managing-deploy-keys": "/ja/developers/overview/managing-deploy-keys", - "/ja/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/ja/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/ja/enterprise/3.0/v3/guides/managing-deploy-keys": "/ja/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/ja/enterprise/v3/guides/managing-deploy-keys": "/ja/enterprise-server@latest/developers/overview/managing-deploy-keys", - "/ja/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/ja/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/ja/enterprise/2.20/v3/guides/managing-deploy-keys": "/ja/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/ja/github-ae@latest/v3/guides/managing-deploy-keys": "/ja/github-ae@latest/developers/overview/managing-deploy-keys", - "/ja/v3/guides/automating-deployments-to-integrators": "/ja/developers/overview/replacing-github-services", - "/ja/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/ja/developers/overview/replacing-github-services", - "/ja/v3/guides/replacing-github-services": "/ja/developers/overview/replacing-github-services", - "/ja/free-pro-team@latest/v3/guides/replacing-github-services": "/ja/developers/overview/replacing-github-services", - "/ja/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/ja/enterprise-server@3.0/developers/overview/replacing-github-services", - "/ja/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/ja/enterprise-server@3.0/developers/overview/replacing-github-services", - "/ja/enterprise/v3/guides/automating-deployments-to-integrators": "/ja/enterprise-server@latest/developers/overview/replacing-github-services", - "/ja/enterprise-server@3.0/v3/guides/replacing-github-services": "/ja/enterprise-server@3.0/developers/overview/replacing-github-services", - "/ja/enterprise/3.0/v3/guides/replacing-github-services": "/ja/enterprise-server@3.0/developers/overview/replacing-github-services", - "/ja/enterprise/v3/guides/replacing-github-services": "/ja/enterprise-server@latest/developers/overview/replacing-github-services", - "/ja/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/ja/enterprise-server@2.20/developers/overview/replacing-github-services", - "/ja/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/ja/enterprise-server@2.20/developers/overview/replacing-github-services", - "/ja/enterprise-server@2.20/v3/guides/replacing-github-services": "/ja/enterprise-server@2.20/developers/overview/replacing-github-services", - "/ja/enterprise/2.20/v3/guides/replacing-github-services": "/ja/enterprise-server@2.20/developers/overview/replacing-github-services", - "/ja/v3/guides/using-ssh-agent-forwarding": "/ja/developers/overview/using-ssh-agent-forwarding", - "/ja/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/ja/developers/overview/using-ssh-agent-forwarding", - "/ja/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/ja/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/ja/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/ja/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/ja/enterprise/v3/guides/using-ssh-agent-forwarding": "/ja/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", - "/ja/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/ja/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/ja/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/ja/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/ja/github-ae@latest/v3/guides/using-ssh-agent-forwarding": "/ja/github-ae@latest/developers/overview/using-ssh-agent-forwarding", - "/ja/v3/activity/event_types": "/ja/developers/webhooks-and-events/github-event-types", - "/ja/free-pro-team@latest/v3/activity/event_types": "/ja/developers/webhooks-and-events/github-event-types", - "/ja/enterprise-server@3.0/v3/activity/event_types": "/ja/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/ja/enterprise/3.0/v3/activity/event_types": "/ja/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/ja/enterprise/v3/activity/event_types": "/ja/enterprise-server@latest/developers/webhooks-and-events/github-event-types", - "/ja/enterprise-server@2.20/v3/activity/event_types": "/ja/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/ja/enterprise/2.20/v3/activity/event_types": "/ja/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/ja/github-ae@latest/v3/activity/event_types": "/ja/github-ae@latest/developers/webhooks-and-events/github-event-types", - "/ja/v3/issues/issue-event-types": "/ja/developers/webhooks-and-events/issue-event-types", - "/ja/free-pro-team@latest/v3/issues/issue-event-types": "/ja/developers/webhooks-and-events/issue-event-types", - "/ja/enterprise-server@3.0/v3/issues/issue-event-types": "/ja/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/ja/enterprise/3.0/v3/issues/issue-event-types": "/ja/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/ja/enterprise/v3/issues/issue-event-types": "/ja/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", - "/ja/enterprise-server@2.20/v3/issues/issue-event-types": "/ja/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/ja/enterprise/2.20/v3/issues/issue-event-types": "/ja/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/ja/github-ae@latest/v3/issues/issue-event-types": "/ja/github-ae@latest/developers/webhooks-and-events/issue-event-types", - "/ja/v3/activity/events/types": "/ja/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/free-pro-team@latest/v3/activity/events/types": "/ja/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/enterprise-server@3.0/v3/activity/events/types": "/ja/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/enterprise/3.0/v3/activity/events/types": "/ja/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/enterprise/v3/activity/events/types": "/ja/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/enterprise-server@2.20/v3/activity/events/types": "/ja/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/enterprise/2.20/v3/activity/events/types": "/ja/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/github-ae@latest/v3/activity/events/types": "/ja/github-ae@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/ja/articles/restoring-branches-in-a-pull-request": "/ja/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/ja/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/ja/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/ja/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/articles/restoring-branches-in-a-pull-request": "/ja/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/ja/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/ja/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/github-ae@latest/articles/restoring-branches-in-a-pull-request": "/ja/github-ae@latest/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/ja/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/ja/github/administering-a-repository/restoring-a-deleted-repository", - "/ja/articles/restoring-a-deleted-repository": "/ja/github/administering-a-repository/restoring-a-deleted-repository", - "/ja/free-pro-team@latest/articles/restoring-a-deleted-repository": "/ja/github/administering-a-repository/restoring-a-deleted-repository", - "/ja/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/ja/articles/restricting-access-to-your-organization-s-data": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/ja/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/ja/articles/restricting-access-to-your-organizations-data": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/ja/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/ja/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/ja/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/ja/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/ja/articles/restricting-email-notifications-to-an-approved-domain": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/ja/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/ja/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/articles/restricting-repository-creation-in-your-organization": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/github-ae@latest/articles/restricting-repository-creation-in-your-organization": "/ja/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/ja/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/github-ae@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/ja/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/ja/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/github-ae@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/ja/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/ja/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/ja/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", - "/ja/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/ja/graphql/guides/forming-calls-with-graphql", - "/ja/v4/guides/forming-calls": "/ja/graphql/guides/forming-calls-with-graphql", - "/ja/free-pro-team@latest/v4/guides/forming-calls": "/ja/graphql/guides/forming-calls-with-graphql", - "/ja/graphql/guides/forming-calls": "/ja/graphql/guides/forming-calls-with-graphql", - "/ja/free-pro-team@latest/graphql/guides/forming-calls": "/ja/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/ja/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/graphql/guides/forming-calls-with-graphql": "/ja/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise-server@3.0/v4/guides/forming-calls": "/ja/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/3.0/v4/guides/forming-calls": "/ja/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/v4/guides/forming-calls": "/ja/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise-server@3.0/graphql/guides/forming-calls": "/ja/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/3.0/graphql/guides/forming-calls": "/ja/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/graphql/guides/forming-calls": "/ja/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/ja/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise-server@2.20/v4/guides/forming-calls": "/ja/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/2.20/v4/guides/forming-calls": "/ja/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise-server@2.20/graphql/guides/forming-calls": "/ja/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/ja/enterprise/2.20/graphql/guides/forming-calls": "/ja/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/ja/github-ae@latest/v4/guides/forming-calls": "/ja/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/ja/github-ae@latest/graphql/guides/forming-calls": "/ja/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/ja/free-pro-team@latest/graphql/guides": "/ja/graphql/guides", - "/ja/v4/guides": "/ja/graphql/guides", - "/ja/free-pro-team@latest/v4/guides": "/ja/graphql/guides", - "/ja/enterprise/3.0/graphql/guides": "/ja/enterprise-server@3.0/graphql/guides", - "/ja/enterprise/graphql/guides": "/ja/enterprise-server@latest/graphql/guides", - "/ja/enterprise-server@3.0/v4/guides": "/ja/enterprise-server@3.0/graphql/guides", - "/ja/enterprise/3.0/v4/guides": "/ja/enterprise-server@3.0/graphql/guides", - "/ja/enterprise/v4/guides": "/ja/enterprise-server@latest/graphql/guides", - "/ja/enterprise/2.20/graphql/guides": "/ja/enterprise-server@2.20/graphql/guides", - "/ja/enterprise-server@2.20/v4/guides": "/ja/enterprise-server@2.20/graphql/guides", - "/ja/enterprise/2.20/v4/guides": "/ja/enterprise-server@2.20/graphql/guides", - "/ja/github-ae@latest/v4/guides": "/ja/github-ae@latest/graphql/guides", - "/ja/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/ja/graphql/guides/introduction-to-graphql", - "/ja/v4/guides/intro-to-graphql": "/ja/graphql/guides/introduction-to-graphql", - "/ja/free-pro-team@latest/v4/guides/intro-to-graphql": "/ja/graphql/guides/introduction-to-graphql", - "/ja/graphql/guides/intro-to-graphql": "/ja/graphql/guides/introduction-to-graphql", - "/ja/free-pro-team@latest/graphql/guides/intro-to-graphql": "/ja/graphql/guides/introduction-to-graphql", - "/ja/enterprise/3.0/graphql/guides/introduction-to-graphql": "/ja/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/ja/enterprise/graphql/guides/introduction-to-graphql": "/ja/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/ja/enterprise-server@3.0/v4/guides/intro-to-graphql": "/ja/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/ja/enterprise/3.0/v4/guides/intro-to-graphql": "/ja/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/ja/enterprise/v4/guides/intro-to-graphql": "/ja/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/ja/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/ja/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/ja/enterprise/3.0/graphql/guides/intro-to-graphql": "/ja/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/ja/enterprise/graphql/guides/intro-to-graphql": "/ja/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/ja/enterprise/2.20/graphql/guides/introduction-to-graphql": "/ja/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/ja/enterprise-server@2.20/v4/guides/intro-to-graphql": "/ja/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/ja/enterprise/2.20/v4/guides/intro-to-graphql": "/ja/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/ja/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/ja/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/ja/enterprise/2.20/graphql/guides/intro-to-graphql": "/ja/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/ja/github-ae@latest/v4/guides/intro-to-graphql": "/ja/github-ae@latest/graphql/guides/introduction-to-graphql", - "/ja/github-ae@latest/graphql/guides/intro-to-graphql": "/ja/github-ae@latest/graphql/guides/introduction-to-graphql", - "/ja/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/ja/graphql/guides/managing-enterprise-accounts", - "/ja/v4/guides/managing-enterprise-accounts": "/ja/graphql/guides/managing-enterprise-accounts", - "/ja/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/ja/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/ja/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise/graphql/guides/managing-enterprise-accounts": "/ja/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/ja/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/ja/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise/v4/guides/managing-enterprise-accounts": "/ja/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/ja/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/ja/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/ja/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/ja/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/ja/github-ae@latest/v4/guides/managing-enterprise-accounts": "/ja/github-ae@latest/graphql/guides/managing-enterprise-accounts", - "/ja/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/ja/graphql/guides/migrating-from-rest-to-graphql", - "/ja/v4/guides/migrating-from-rest": "/ja/graphql/guides/migrating-from-rest-to-graphql", - "/ja/free-pro-team@latest/v4/guides/migrating-from-rest": "/ja/graphql/guides/migrating-from-rest-to-graphql", - "/ja/graphql/guides/migrating-from-rest": "/ja/graphql/guides/migrating-from-rest-to-graphql", - "/ja/free-pro-team@latest/graphql/guides/migrating-from-rest": "/ja/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/ja/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/ja/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise-server@3.0/v4/guides/migrating-from-rest": "/ja/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/3.0/v4/guides/migrating-from-rest": "/ja/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/v4/guides/migrating-from-rest": "/ja/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/ja/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/3.0/graphql/guides/migrating-from-rest": "/ja/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/graphql/guides/migrating-from-rest": "/ja/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/ja/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise-server@2.20/v4/guides/migrating-from-rest": "/ja/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/2.20/v4/guides/migrating-from-rest": "/ja/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/ja/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/ja/enterprise/2.20/graphql/guides/migrating-from-rest": "/ja/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/ja/github-ae@latest/v4/guides/migrating-from-rest": "/ja/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/ja/github-ae@latest/graphql/guides/migrating-from-rest": "/ja/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/ja/free-pro-team@latest/graphql/guides/using-global-node-ids": "/ja/graphql/guides/using-global-node-ids", - "/ja/v4/guides/using-global-node-ids": "/ja/graphql/guides/using-global-node-ids", - "/ja/free-pro-team@latest/v4/guides/using-global-node-ids": "/ja/graphql/guides/using-global-node-ids", - "/ja/enterprise/3.0/graphql/guides/using-global-node-ids": "/ja/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/ja/enterprise/graphql/guides/using-global-node-ids": "/ja/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/ja/enterprise-server@3.0/v4/guides/using-global-node-ids": "/ja/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/ja/enterprise/3.0/v4/guides/using-global-node-ids": "/ja/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/ja/enterprise/v4/guides/using-global-node-ids": "/ja/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/ja/enterprise/2.20/graphql/guides/using-global-node-ids": "/ja/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/ja/enterprise-server@2.20/v4/guides/using-global-node-ids": "/ja/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/ja/enterprise/2.20/v4/guides/using-global-node-ids": "/ja/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/ja/github-ae@latest/v4/guides/using-global-node-ids": "/ja/github-ae@latest/graphql/guides/using-global-node-ids", - "/ja/free-pro-team@latest/graphql/guides/using-the-explorer": "/ja/graphql/guides/using-the-explorer", - "/ja/v4/guides/using-the-explorer": "/ja/graphql/guides/using-the-explorer", - "/ja/free-pro-team@latest/v4/guides/using-the-explorer": "/ja/graphql/guides/using-the-explorer", - "/ja/enterprise/3.0/graphql/guides/using-the-explorer": "/ja/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/ja/enterprise/graphql/guides/using-the-explorer": "/ja/enterprise-server@latest/graphql/guides/using-the-explorer", - "/ja/enterprise-server@3.0/v4/guides/using-the-explorer": "/ja/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/ja/enterprise/3.0/v4/guides/using-the-explorer": "/ja/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/ja/enterprise/v4/guides/using-the-explorer": "/ja/enterprise-server@latest/graphql/guides/using-the-explorer", - "/ja/enterprise/2.20/graphql/guides/using-the-explorer": "/ja/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/ja/enterprise-server@2.20/v4/guides/using-the-explorer": "/ja/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/ja/enterprise/2.20/v4/guides/using-the-explorer": "/ja/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/ja/github-ae@latest/v4/guides/using-the-explorer": "/ja/github-ae@latest/graphql/guides/using-the-explorer", - "/ja/free-pro-team@latest/graphql": "/ja/graphql", - "/ja/v4": "/ja/graphql", - "/ja/free-pro-team@latest/v4": "/ja/graphql", - "/ja/enterprise/3.0/graphql": "/ja/enterprise-server@3.0/graphql", - "/ja/enterprise/graphql": "/ja/enterprise-server@latest/graphql", - "/ja/enterprise-server@3.0/v4": "/ja/enterprise-server@3.0/graphql", - "/ja/enterprise/3.0/v4": "/ja/enterprise-server@3.0/graphql", - "/ja/enterprise/v4": "/ja/enterprise-server@latest/graphql", - "/ja/enterprise/2.20/graphql": "/ja/enterprise-server@2.20/graphql", - "/ja/enterprise-server@2.20/v4": "/ja/enterprise-server@2.20/graphql", - "/ja/enterprise/2.20/v4": "/ja/enterprise-server@2.20/graphql", - "/ja/github-ae@latest/v4": "/ja/github-ae@latest/graphql", - "/ja/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/ja/graphql/overview/about-the-graphql-api", - "/ja/enterprise/3.0/graphql/overview/about-the-graphql-api": "/ja/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/ja/enterprise/graphql/overview/about-the-graphql-api": "/ja/enterprise-server@latest/graphql/overview/about-the-graphql-api", - "/ja/enterprise/2.20/graphql/overview/about-the-graphql-api": "/ja/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/ja/free-pro-team@latest/graphql/overview/breaking-changes": "/ja/graphql/overview/breaking-changes", - "/ja/v4/breaking_changes": "/ja/graphql/overview/breaking-changes", - "/ja/free-pro-team@latest/v4/breaking_changes": "/ja/graphql/overview/breaking-changes", - "/ja/enterprise/3.0/graphql/overview/breaking-changes": "/ja/enterprise-server@3.0/graphql/overview/breaking-changes", - "/ja/enterprise/graphql/overview/breaking-changes": "/ja/enterprise-server@latest/graphql/overview/breaking-changes", - "/ja/enterprise-server@3.0/v4/breaking_changes": "/ja/enterprise-server@3.0/graphql/overview/breaking-changes", - "/ja/enterprise/3.0/v4/breaking_changes": "/ja/enterprise-server@3.0/graphql/overview/breaking-changes", - "/ja/enterprise/v4/breaking_changes": "/ja/enterprise-server@latest/graphql/overview/breaking-changes", - "/ja/enterprise/2.20/graphql/overview/breaking-changes": "/ja/enterprise-server@2.20/graphql/overview/breaking-changes", - "/ja/enterprise-server@2.20/v4/breaking_changes": "/ja/enterprise-server@2.20/graphql/overview/breaking-changes", - "/ja/enterprise/2.20/v4/breaking_changes": "/ja/enterprise-server@2.20/graphql/overview/breaking-changes", - "/ja/github-ae@latest/v4/breaking_changes": "/ja/github-ae@latest/graphql/overview/breaking-changes", - "/ja/free-pro-team@latest/graphql/overview/changelog": "/ja/graphql/overview/changelog", - "/ja/v4/changelog": "/ja/graphql/overview/changelog", - "/ja/free-pro-team@latest/v4/changelog": "/ja/graphql/overview/changelog", - "/ja/enterprise/3.0/graphql/overview/changelog": "/ja/enterprise-server@3.0/graphql/overview/changelog", - "/ja/enterprise/graphql/overview/changelog": "/ja/enterprise-server@latest/graphql/overview/changelog", - "/ja/enterprise-server@3.0/v4/changelog": "/ja/enterprise-server@3.0/graphql/overview/changelog", - "/ja/enterprise/3.0/v4/changelog": "/ja/enterprise-server@3.0/graphql/overview/changelog", - "/ja/enterprise/v4/changelog": "/ja/enterprise-server@latest/graphql/overview/changelog", - "/ja/enterprise/2.20/graphql/overview/changelog": "/ja/enterprise-server@2.20/graphql/overview/changelog", - "/ja/enterprise-server@2.20/v4/changelog": "/ja/enterprise-server@2.20/graphql/overview/changelog", - "/ja/enterprise/2.20/v4/changelog": "/ja/enterprise-server@2.20/graphql/overview/changelog", - "/ja/github-ae@latest/v4/changelog": "/ja/github-ae@latest/graphql/overview/changelog", - "/ja/free-pro-team@latest/graphql/overview/explorer": "/ja/graphql/overview/explorer", - "/ja/v4/explorer": "/ja/graphql/overview/explorer", - "/ja/free-pro-team@latest/v4/explorer": "/ja/graphql/overview/explorer", - "/ja/v4/explorer-new": "/ja/graphql/overview/explorer", - "/ja/free-pro-team@latest/v4/explorer-new": "/ja/graphql/overview/explorer", - "/ja/enterprise/3.0/graphql/overview/explorer": "/ja/enterprise-server@3.0/graphql/overview/explorer", - "/ja/enterprise/graphql/overview/explorer": "/ja/enterprise-server@latest/graphql/overview/explorer", - "/ja/enterprise-server@3.0/v4/explorer": "/ja/enterprise-server@3.0/graphql/overview/explorer", - "/ja/enterprise/3.0/v4/explorer": "/ja/enterprise-server@3.0/graphql/overview/explorer", - "/ja/enterprise/v4/explorer": "/ja/enterprise-server@latest/graphql/overview/explorer", - "/ja/enterprise-server@3.0/v4/explorer-new": "/ja/enterprise-server@3.0/graphql/overview/explorer", - "/ja/enterprise/3.0/v4/explorer-new": "/ja/enterprise-server@3.0/graphql/overview/explorer", - "/ja/enterprise/v4/explorer-new": "/ja/enterprise-server@latest/graphql/overview/explorer", - "/ja/enterprise/2.20/graphql/overview/explorer": "/ja/enterprise-server@2.20/graphql/overview/explorer", - "/ja/enterprise-server@2.20/v4/explorer": "/ja/enterprise-server@2.20/graphql/overview/explorer", - "/ja/enterprise/2.20/v4/explorer": "/ja/enterprise-server@2.20/graphql/overview/explorer", - "/ja/enterprise-server@2.20/v4/explorer-new": "/ja/enterprise-server@2.20/graphql/overview/explorer", - "/ja/enterprise/2.20/v4/explorer-new": "/ja/enterprise-server@2.20/graphql/overview/explorer", - "/ja/github-ae@latest/v4/explorer": "/ja/github-ae@latest/graphql/overview/explorer", - "/ja/github-ae@latest/v4/explorer-new": "/ja/github-ae@latest/graphql/overview/explorer", - "/ja/free-pro-team@latest/graphql/overview": "/ja/graphql/overview", - "/ja/enterprise/3.0/graphql/overview": "/ja/enterprise-server@3.0/graphql/overview", - "/ja/enterprise/graphql/overview": "/ja/enterprise-server@latest/graphql/overview", - "/ja/enterprise/2.20/graphql/overview": "/ja/enterprise-server@2.20/graphql/overview", - "/ja/free-pro-team@latest/graphql/overview/public-schema": "/ja/graphql/overview/public-schema", - "/ja/v4/public_schema": "/ja/graphql/overview/public-schema", - "/ja/free-pro-team@latest/v4/public_schema": "/ja/graphql/overview/public-schema", - "/ja/enterprise/3.0/graphql/overview/public-schema": "/ja/enterprise-server@3.0/graphql/overview/public-schema", - "/ja/enterprise/graphql/overview/public-schema": "/ja/enterprise-server@latest/graphql/overview/public-schema", - "/ja/enterprise-server@3.0/v4/public_schema": "/ja/enterprise-server@3.0/graphql/overview/public-schema", - "/ja/enterprise/3.0/v4/public_schema": "/ja/enterprise-server@3.0/graphql/overview/public-schema", - "/ja/enterprise/v4/public_schema": "/ja/enterprise-server@latest/graphql/overview/public-schema", - "/ja/enterprise/2.20/graphql/overview/public-schema": "/ja/enterprise-server@2.20/graphql/overview/public-schema", - "/ja/enterprise-server@2.20/v4/public_schema": "/ja/enterprise-server@2.20/graphql/overview/public-schema", - "/ja/enterprise/2.20/v4/public_schema": "/ja/enterprise-server@2.20/graphql/overview/public-schema", - "/ja/github-ae@latest/v4/public_schema": "/ja/github-ae@latest/graphql/overview/public-schema", - "/ja/free-pro-team@latest/graphql/overview/resource-limitations": "/ja/graphql/overview/resource-limitations", - "/ja/v4/guides/resource-limitations": "/ja/graphql/overview/resource-limitations", - "/ja/free-pro-team@latest/v4/guides/resource-limitations": "/ja/graphql/overview/resource-limitations", - "/ja/enterprise/3.0/graphql/overview/resource-limitations": "/ja/enterprise-server@3.0/graphql/overview/resource-limitations", - "/ja/enterprise/graphql/overview/resource-limitations": "/ja/enterprise-server@latest/graphql/overview/resource-limitations", - "/ja/enterprise-server@3.0/v4/guides/resource-limitations": "/ja/enterprise-server@3.0/graphql/overview/resource-limitations", - "/ja/enterprise/3.0/v4/guides/resource-limitations": "/ja/enterprise-server@3.0/graphql/overview/resource-limitations", - "/ja/enterprise/v4/guides/resource-limitations": "/ja/enterprise-server@latest/graphql/overview/resource-limitations", - "/ja/enterprise/2.20/graphql/overview/resource-limitations": "/ja/enterprise-server@2.20/graphql/overview/resource-limitations", - "/ja/enterprise-server@2.20/v4/guides/resource-limitations": "/ja/enterprise-server@2.20/graphql/overview/resource-limitations", - "/ja/enterprise/2.20/v4/guides/resource-limitations": "/ja/enterprise-server@2.20/graphql/overview/resource-limitations", - "/ja/github-ae@latest/v4/guides/resource-limitations": "/ja/github-ae@latest/graphql/overview/resource-limitations", - "/ja/free-pro-team@latest/graphql/overview/schema-previews": "/ja/graphql/overview/schema-previews", - "/ja/v4/previews": "/ja/graphql/overview/schema-previews", - "/ja/free-pro-team@latest/v4/previews": "/ja/graphql/overview/schema-previews", - "/ja/enterprise/3.0/graphql/overview/schema-previews": "/ja/enterprise-server@3.0/graphql/overview/schema-previews", - "/ja/enterprise/graphql/overview/schema-previews": "/ja/enterprise-server@latest/graphql/overview/schema-previews", - "/ja/enterprise-server@3.0/v4/previews": "/ja/enterprise-server@3.0/graphql/overview/schema-previews", - "/ja/enterprise/3.0/v4/previews": "/ja/enterprise-server@3.0/graphql/overview/schema-previews", - "/ja/enterprise/v4/previews": "/ja/enterprise-server@latest/graphql/overview/schema-previews", - "/ja/enterprise/2.20/graphql/overview/schema-previews": "/ja/enterprise-server@2.20/graphql/overview/schema-previews", - "/ja/enterprise-server@2.20/v4/previews": "/ja/enterprise-server@2.20/graphql/overview/schema-previews", - "/ja/enterprise/2.20/v4/previews": "/ja/enterprise-server@2.20/graphql/overview/schema-previews", - "/ja/github-ae@latest/v4/previews": "/ja/github-ae@latest/graphql/overview/schema-previews", - "/ja/free-pro-team@latest/graphql/reference/enums": "/ja/graphql/reference/enums", - "/ja/v4/enum": "/ja/graphql/reference/enums", - "/ja/free-pro-team@latest/v4/enum": "/ja/graphql/reference/enums", - "/ja/v4/reference/enum": "/ja/graphql/reference/enums", - "/ja/free-pro-team@latest/v4/reference/enum": "/ja/graphql/reference/enums", - "/ja/enterprise/3.0/graphql/reference/enums": "/ja/enterprise-server@3.0/graphql/reference/enums", - "/ja/enterprise/graphql/reference/enums": "/ja/enterprise-server@latest/graphql/reference/enums", - "/ja/enterprise-server@3.0/v4/enum": "/ja/enterprise-server@3.0/graphql/reference/enums", - "/ja/enterprise/3.0/v4/enum": "/ja/enterprise-server@3.0/graphql/reference/enums", - "/ja/enterprise/v4/enum": "/ja/enterprise-server@latest/graphql/reference/enums", - "/ja/enterprise-server@3.0/v4/reference/enum": "/ja/enterprise-server@3.0/graphql/reference/enums", - "/ja/enterprise/3.0/v4/reference/enum": "/ja/enterprise-server@3.0/graphql/reference/enums", - "/ja/enterprise/v4/reference/enum": "/ja/enterprise-server@latest/graphql/reference/enums", - "/ja/enterprise/2.20/graphql/reference/enums": "/ja/enterprise-server@2.20/graphql/reference/enums", - "/ja/enterprise-server@2.20/v4/enum": "/ja/enterprise-server@2.20/graphql/reference/enums", - "/ja/enterprise/2.20/v4/enum": "/ja/enterprise-server@2.20/graphql/reference/enums", - "/ja/enterprise-server@2.20/v4/reference/enum": "/ja/enterprise-server@2.20/graphql/reference/enums", - "/ja/enterprise/2.20/v4/reference/enum": "/ja/enterprise-server@2.20/graphql/reference/enums", - "/ja/github-ae@latest/v4/enum": "/ja/github-ae@latest/graphql/reference/enums", - "/ja/github-ae@latest/v4/reference/enum": "/ja/github-ae@latest/graphql/reference/enums", - "/ja/free-pro-team@latest/graphql/reference": "/ja/graphql/reference", - "/ja/v4/reference": "/ja/graphql/reference", - "/ja/free-pro-team@latest/v4/reference": "/ja/graphql/reference", - "/ja/enterprise/3.0/graphql/reference": "/ja/enterprise-server@3.0/graphql/reference", - "/ja/enterprise/graphql/reference": "/ja/enterprise-server@latest/graphql/reference", - "/ja/enterprise-server@3.0/v4/reference": "/ja/enterprise-server@3.0/graphql/reference", - "/ja/enterprise/3.0/v4/reference": "/ja/enterprise-server@3.0/graphql/reference", - "/ja/enterprise/v4/reference": "/ja/enterprise-server@latest/graphql/reference", - "/ja/enterprise/2.20/graphql/reference": "/ja/enterprise-server@2.20/graphql/reference", - "/ja/enterprise-server@2.20/v4/reference": "/ja/enterprise-server@2.20/graphql/reference", - "/ja/enterprise/2.20/v4/reference": "/ja/enterprise-server@2.20/graphql/reference", - "/ja/github-ae@latest/v4/reference": "/ja/github-ae@latest/graphql/reference", - "/ja/free-pro-team@latest/graphql/reference/input-objects": "/ja/graphql/reference/input-objects", - "/ja/v4/input_object": "/ja/graphql/reference/input-objects", - "/ja/free-pro-team@latest/v4/input_object": "/ja/graphql/reference/input-objects", - "/ja/v4/reference/input_object": "/ja/graphql/reference/input-objects", - "/ja/free-pro-team@latest/v4/reference/input_object": "/ja/graphql/reference/input-objects", - "/ja/enterprise/3.0/graphql/reference/input-objects": "/ja/enterprise-server@3.0/graphql/reference/input-objects", - "/ja/enterprise/graphql/reference/input-objects": "/ja/enterprise-server@latest/graphql/reference/input-objects", - "/ja/enterprise-server@3.0/v4/input_object": "/ja/enterprise-server@3.0/graphql/reference/input-objects", - "/ja/enterprise/3.0/v4/input_object": "/ja/enterprise-server@3.0/graphql/reference/input-objects", - "/ja/enterprise/v4/input_object": "/ja/enterprise-server@latest/graphql/reference/input-objects", - "/ja/enterprise-server@3.0/v4/reference/input_object": "/ja/enterprise-server@3.0/graphql/reference/input-objects", - "/ja/enterprise/3.0/v4/reference/input_object": "/ja/enterprise-server@3.0/graphql/reference/input-objects", - "/ja/enterprise/v4/reference/input_object": "/ja/enterprise-server@latest/graphql/reference/input-objects", - "/ja/enterprise/2.20/graphql/reference/input-objects": "/ja/enterprise-server@2.20/graphql/reference/input-objects", - "/ja/enterprise-server@2.20/v4/input_object": "/ja/enterprise-server@2.20/graphql/reference/input-objects", - "/ja/enterprise/2.20/v4/input_object": "/ja/enterprise-server@2.20/graphql/reference/input-objects", - "/ja/enterprise-server@2.20/v4/reference/input_object": "/ja/enterprise-server@2.20/graphql/reference/input-objects", - "/ja/enterprise/2.20/v4/reference/input_object": "/ja/enterprise-server@2.20/graphql/reference/input-objects", - "/ja/github-ae@latest/v4/input_object": "/ja/github-ae@latest/graphql/reference/input-objects", - "/ja/github-ae@latest/v4/reference/input_object": "/ja/github-ae@latest/graphql/reference/input-objects", - "/ja/free-pro-team@latest/graphql/reference/interfaces": "/ja/graphql/reference/interfaces", - "/ja/v4/interface": "/ja/graphql/reference/interfaces", - "/ja/free-pro-team@latest/v4/interface": "/ja/graphql/reference/interfaces", - "/ja/v4/reference/interface": "/ja/graphql/reference/interfaces", - "/ja/free-pro-team@latest/v4/reference/interface": "/ja/graphql/reference/interfaces", - "/ja/enterprise/3.0/graphql/reference/interfaces": "/ja/enterprise-server@3.0/graphql/reference/interfaces", - "/ja/enterprise/graphql/reference/interfaces": "/ja/enterprise-server@latest/graphql/reference/interfaces", - "/ja/enterprise-server@3.0/v4/interface": "/ja/enterprise-server@3.0/graphql/reference/interfaces", - "/ja/enterprise/3.0/v4/interface": "/ja/enterprise-server@3.0/graphql/reference/interfaces", - "/ja/enterprise/v4/interface": "/ja/enterprise-server@latest/graphql/reference/interfaces", - "/ja/enterprise-server@3.0/v4/reference/interface": "/ja/enterprise-server@3.0/graphql/reference/interfaces", - "/ja/enterprise/3.0/v4/reference/interface": "/ja/enterprise-server@3.0/graphql/reference/interfaces", - "/ja/enterprise/v4/reference/interface": "/ja/enterprise-server@latest/graphql/reference/interfaces", - "/ja/enterprise/2.20/graphql/reference/interfaces": "/ja/enterprise-server@2.20/graphql/reference/interfaces", - "/ja/enterprise-server@2.20/v4/interface": "/ja/enterprise-server@2.20/graphql/reference/interfaces", - "/ja/enterprise/2.20/v4/interface": "/ja/enterprise-server@2.20/graphql/reference/interfaces", - "/ja/enterprise-server@2.20/v4/reference/interface": "/ja/enterprise-server@2.20/graphql/reference/interfaces", - "/ja/enterprise/2.20/v4/reference/interface": "/ja/enterprise-server@2.20/graphql/reference/interfaces", - "/ja/github-ae@latest/v4/interface": "/ja/github-ae@latest/graphql/reference/interfaces", - "/ja/github-ae@latest/v4/reference/interface": "/ja/github-ae@latest/graphql/reference/interfaces", - "/ja/free-pro-team@latest/graphql/reference/mutations": "/ja/graphql/reference/mutations", - "/ja/v4/mutation": "/ja/graphql/reference/mutations", - "/ja/free-pro-team@latest/v4/mutation": "/ja/graphql/reference/mutations", - "/ja/v4/reference/mutation": "/ja/graphql/reference/mutations", - "/ja/free-pro-team@latest/v4/reference/mutation": "/ja/graphql/reference/mutations", - "/ja/enterprise/3.0/graphql/reference/mutations": "/ja/enterprise-server@3.0/graphql/reference/mutations", - "/ja/enterprise/graphql/reference/mutations": "/ja/enterprise-server@latest/graphql/reference/mutations", - "/ja/enterprise-server@3.0/v4/mutation": "/ja/enterprise-server@3.0/graphql/reference/mutations", - "/ja/enterprise/3.0/v4/mutation": "/ja/enterprise-server@3.0/graphql/reference/mutations", - "/ja/enterprise/v4/mutation": "/ja/enterprise-server@latest/graphql/reference/mutations", - "/ja/enterprise-server@3.0/v4/reference/mutation": "/ja/enterprise-server@3.0/graphql/reference/mutations", - "/ja/enterprise/3.0/v4/reference/mutation": "/ja/enterprise-server@3.0/graphql/reference/mutations", - "/ja/enterprise/v4/reference/mutation": "/ja/enterprise-server@latest/graphql/reference/mutations", - "/ja/enterprise/2.20/graphql/reference/mutations": "/ja/enterprise-server@2.20/graphql/reference/mutations", - "/ja/enterprise-server@2.20/v4/mutation": "/ja/enterprise-server@2.20/graphql/reference/mutations", - "/ja/enterprise/2.20/v4/mutation": "/ja/enterprise-server@2.20/graphql/reference/mutations", - "/ja/enterprise-server@2.20/v4/reference/mutation": "/ja/enterprise-server@2.20/graphql/reference/mutations", - "/ja/enterprise/2.20/v4/reference/mutation": "/ja/enterprise-server@2.20/graphql/reference/mutations", - "/ja/github-ae@latest/v4/mutation": "/ja/github-ae@latest/graphql/reference/mutations", - "/ja/github-ae@latest/v4/reference/mutation": "/ja/github-ae@latest/graphql/reference/mutations", - "/ja/free-pro-team@latest/graphql/reference/objects": "/ja/graphql/reference/objects", - "/ja/v4/object": "/ja/graphql/reference/objects", - "/ja/free-pro-team@latest/v4/object": "/ja/graphql/reference/objects", - "/ja/v4/reference/object": "/ja/graphql/reference/objects", - "/ja/free-pro-team@latest/v4/reference/object": "/ja/graphql/reference/objects", - "/ja/enterprise/3.0/graphql/reference/objects": "/ja/enterprise-server@3.0/graphql/reference/objects", - "/ja/enterprise/graphql/reference/objects": "/ja/enterprise-server@latest/graphql/reference/objects", - "/ja/enterprise-server@3.0/v4/object": "/ja/enterprise-server@3.0/graphql/reference/objects", - "/ja/enterprise/3.0/v4/object": "/ja/enterprise-server@3.0/graphql/reference/objects", - "/ja/enterprise/v4/object": "/ja/enterprise-server@latest/graphql/reference/objects", - "/ja/enterprise-server@3.0/v4/reference/object": "/ja/enterprise-server@3.0/graphql/reference/objects", - "/ja/enterprise/3.0/v4/reference/object": "/ja/enterprise-server@3.0/graphql/reference/objects", - "/ja/enterprise/v4/reference/object": "/ja/enterprise-server@latest/graphql/reference/objects", - "/ja/enterprise/2.20/graphql/reference/objects": "/ja/enterprise-server@2.20/graphql/reference/objects", - "/ja/enterprise-server@2.20/v4/object": "/ja/enterprise-server@2.20/graphql/reference/objects", - "/ja/enterprise/2.20/v4/object": "/ja/enterprise-server@2.20/graphql/reference/objects", - "/ja/enterprise-server@2.20/v4/reference/object": "/ja/enterprise-server@2.20/graphql/reference/objects", - "/ja/enterprise/2.20/v4/reference/object": "/ja/enterprise-server@2.20/graphql/reference/objects", - "/ja/github-ae@latest/v4/object": "/ja/github-ae@latest/graphql/reference/objects", - "/ja/github-ae@latest/v4/reference/object": "/ja/github-ae@latest/graphql/reference/objects", - "/ja/free-pro-team@latest/graphql/reference/queries": "/ja/graphql/reference/queries", - "/ja/v4/query": "/ja/graphql/reference/queries", - "/ja/free-pro-team@latest/v4/query": "/ja/graphql/reference/queries", - "/ja/v4/reference/query": "/ja/graphql/reference/queries", - "/ja/free-pro-team@latest/v4/reference/query": "/ja/graphql/reference/queries", - "/ja/enterprise/3.0/graphql/reference/queries": "/ja/enterprise-server@3.0/graphql/reference/queries", - "/ja/enterprise/graphql/reference/queries": "/ja/enterprise-server@latest/graphql/reference/queries", - "/ja/enterprise-server@3.0/v4/query": "/ja/enterprise-server@3.0/graphql/reference/queries", - "/ja/enterprise/3.0/v4/query": "/ja/enterprise-server@3.0/graphql/reference/queries", - "/ja/enterprise/v4/query": "/ja/enterprise-server@latest/graphql/reference/queries", - "/ja/enterprise-server@3.0/v4/reference/query": "/ja/enterprise-server@3.0/graphql/reference/queries", - "/ja/enterprise/3.0/v4/reference/query": "/ja/enterprise-server@3.0/graphql/reference/queries", - "/ja/enterprise/v4/reference/query": "/ja/enterprise-server@latest/graphql/reference/queries", - "/ja/enterprise/2.20/graphql/reference/queries": "/ja/enterprise-server@2.20/graphql/reference/queries", - "/ja/enterprise-server@2.20/v4/query": "/ja/enterprise-server@2.20/graphql/reference/queries", - "/ja/enterprise/2.20/v4/query": "/ja/enterprise-server@2.20/graphql/reference/queries", - "/ja/enterprise-server@2.20/v4/reference/query": "/ja/enterprise-server@2.20/graphql/reference/queries", - "/ja/enterprise/2.20/v4/reference/query": "/ja/enterprise-server@2.20/graphql/reference/queries", - "/ja/github-ae@latest/v4/query": "/ja/github-ae@latest/graphql/reference/queries", - "/ja/github-ae@latest/v4/reference/query": "/ja/github-ae@latest/graphql/reference/queries", - "/ja/free-pro-team@latest/graphql/reference/scalars": "/ja/graphql/reference/scalars", - "/ja/v4/scalar": "/ja/graphql/reference/scalars", - "/ja/free-pro-team@latest/v4/scalar": "/ja/graphql/reference/scalars", - "/ja/v4/reference/scalar": "/ja/graphql/reference/scalars", - "/ja/free-pro-team@latest/v4/reference/scalar": "/ja/graphql/reference/scalars", - "/ja/enterprise/3.0/graphql/reference/scalars": "/ja/enterprise-server@3.0/graphql/reference/scalars", - "/ja/enterprise/graphql/reference/scalars": "/ja/enterprise-server@latest/graphql/reference/scalars", - "/ja/enterprise-server@3.0/v4/scalar": "/ja/enterprise-server@3.0/graphql/reference/scalars", - "/ja/enterprise/3.0/v4/scalar": "/ja/enterprise-server@3.0/graphql/reference/scalars", - "/ja/enterprise/v4/scalar": "/ja/enterprise-server@latest/graphql/reference/scalars", - "/ja/enterprise-server@3.0/v4/reference/scalar": "/ja/enterprise-server@3.0/graphql/reference/scalars", - "/ja/enterprise/3.0/v4/reference/scalar": "/ja/enterprise-server@3.0/graphql/reference/scalars", - "/ja/enterprise/v4/reference/scalar": "/ja/enterprise-server@latest/graphql/reference/scalars", - "/ja/enterprise/2.20/graphql/reference/scalars": "/ja/enterprise-server@2.20/graphql/reference/scalars", - "/ja/enterprise-server@2.20/v4/scalar": "/ja/enterprise-server@2.20/graphql/reference/scalars", - "/ja/enterprise/2.20/v4/scalar": "/ja/enterprise-server@2.20/graphql/reference/scalars", - "/ja/enterprise-server@2.20/v4/reference/scalar": "/ja/enterprise-server@2.20/graphql/reference/scalars", - "/ja/enterprise/2.20/v4/reference/scalar": "/ja/enterprise-server@2.20/graphql/reference/scalars", - "/ja/github-ae@latest/v4/scalar": "/ja/github-ae@latest/graphql/reference/scalars", - "/ja/github-ae@latest/v4/reference/scalar": "/ja/github-ae@latest/graphql/reference/scalars", - "/ja/free-pro-team@latest/graphql/reference/unions": "/ja/graphql/reference/unions", - "/ja/v4/union": "/ja/graphql/reference/unions", - "/ja/free-pro-team@latest/v4/union": "/ja/graphql/reference/unions", - "/ja/v4/reference/union": "/ja/graphql/reference/unions", - "/ja/free-pro-team@latest/v4/reference/union": "/ja/graphql/reference/unions", - "/ja/enterprise/3.0/graphql/reference/unions": "/ja/enterprise-server@3.0/graphql/reference/unions", - "/ja/enterprise/graphql/reference/unions": "/ja/enterprise-server@latest/graphql/reference/unions", - "/ja/enterprise-server@3.0/v4/union": "/ja/enterprise-server@3.0/graphql/reference/unions", - "/ja/enterprise/3.0/v4/union": "/ja/enterprise-server@3.0/graphql/reference/unions", - "/ja/enterprise/v4/union": "/ja/enterprise-server@latest/graphql/reference/unions", - "/ja/enterprise-server@3.0/v4/reference/union": "/ja/enterprise-server@3.0/graphql/reference/unions", - "/ja/enterprise/3.0/v4/reference/union": "/ja/enterprise-server@3.0/graphql/reference/unions", - "/ja/enterprise/v4/reference/union": "/ja/enterprise-server@latest/graphql/reference/unions", - "/ja/enterprise/2.20/graphql/reference/unions": "/ja/enterprise-server@2.20/graphql/reference/unions", - "/ja/enterprise-server@2.20/v4/union": "/ja/enterprise-server@2.20/graphql/reference/unions", - "/ja/enterprise/2.20/v4/union": "/ja/enterprise-server@2.20/graphql/reference/unions", - "/ja/enterprise-server@2.20/v4/reference/union": "/ja/enterprise-server@2.20/graphql/reference/unions", - "/ja/enterprise/2.20/v4/reference/union": "/ja/enterprise-server@2.20/graphql/reference/unions", - "/ja/github-ae@latest/v4/union": "/ja/github-ae@latest/graphql/reference/unions", - "/ja/github-ae@latest/v4/reference/union": "/ja/github-ae@latest/graphql/reference/unions", - "/ja/free-pro-team@latest/rest/guides/basics-of-authentication": "/ja/rest/guides/basics-of-authentication", - "/ja/v3/guides/basics-of-authentication": "/ja/rest/guides/basics-of-authentication", - "/ja/free-pro-team@latest/v3/guides/basics-of-authentication": "/ja/rest/guides/basics-of-authentication", - "/ja/rest/basics-of-authentication": "/ja/rest/guides/basics-of-authentication", - "/ja/free-pro-team@latest/rest/basics-of-authentication": "/ja/rest/guides/basics-of-authentication", - "/ja/enterprise/3.0/rest/guides/basics-of-authentication": "/ja/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/ja/enterprise/rest/guides/basics-of-authentication": "/ja/enterprise-server@latest/rest/guides/basics-of-authentication", - "/ja/enterprise-server@3.0/v3/guides/basics-of-authentication": "/ja/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/ja/enterprise/3.0/v3/guides/basics-of-authentication": "/ja/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/ja/enterprise/v3/guides/basics-of-authentication": "/ja/enterprise-server@latest/rest/guides/basics-of-authentication", - "/ja/enterprise-server@3.0/rest/basics-of-authentication": "/ja/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/ja/enterprise/3.0/rest/basics-of-authentication": "/ja/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/ja/enterprise/rest/basics-of-authentication": "/ja/enterprise-server@latest/rest/guides/basics-of-authentication", - "/ja/enterprise/2.20/rest/guides/basics-of-authentication": "/ja/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/ja/enterprise-server@2.20/v3/guides/basics-of-authentication": "/ja/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/ja/enterprise/2.20/v3/guides/basics-of-authentication": "/ja/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/ja/enterprise-server@2.20/rest/basics-of-authentication": "/ja/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/ja/enterprise/2.20/rest/basics-of-authentication": "/ja/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/ja/github-ae@latest/v3/guides/basics-of-authentication": "/ja/github-ae@latest/rest/guides/basics-of-authentication", - "/ja/github-ae@latest/rest/basics-of-authentication": "/ja/github-ae@latest/rest/guides/basics-of-authentication", - "/ja/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/ja/rest/guides/best-practices-for-integrators", - "/ja/v3/guides/best-practices-for-integrators": "/ja/rest/guides/best-practices-for-integrators", - "/ja/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/ja/rest/guides/best-practices-for-integrators", - "/ja/enterprise/3.0/rest/guides/best-practices-for-integrators": "/ja/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/ja/enterprise/rest/guides/best-practices-for-integrators": "/ja/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/ja/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/ja/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/ja/enterprise/3.0/v3/guides/best-practices-for-integrators": "/ja/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/ja/enterprise/v3/guides/best-practices-for-integrators": "/ja/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/ja/enterprise/2.20/rest/guides/best-practices-for-integrators": "/ja/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/ja/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/ja/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/ja/enterprise/2.20/v3/guides/best-practices-for-integrators": "/ja/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/ja/github-ae@latest/v3/guides/best-practices-for-integrators": "/ja/github-ae@latest/rest/guides/best-practices-for-integrators", - "/ja/free-pro-team@latest/rest/guides/building-a-ci-server": "/ja/rest/guides/building-a-ci-server", - "/ja/v3/guides/building-a-ci-server": "/ja/rest/guides/building-a-ci-server", - "/ja/free-pro-team@latest/v3/guides/building-a-ci-server": "/ja/rest/guides/building-a-ci-server", - "/ja/enterprise/3.0/rest/guides/building-a-ci-server": "/ja/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/ja/enterprise/rest/guides/building-a-ci-server": "/ja/enterprise-server@latest/rest/guides/building-a-ci-server", - "/ja/enterprise-server@3.0/v3/guides/building-a-ci-server": "/ja/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/ja/enterprise/3.0/v3/guides/building-a-ci-server": "/ja/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/ja/enterprise/v3/guides/building-a-ci-server": "/ja/enterprise-server@latest/rest/guides/building-a-ci-server", - "/ja/enterprise/2.20/rest/guides/building-a-ci-server": "/ja/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/ja/enterprise-server@2.20/v3/guides/building-a-ci-server": "/ja/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/ja/enterprise/2.20/v3/guides/building-a-ci-server": "/ja/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/ja/github-ae@latest/v3/guides/building-a-ci-server": "/ja/github-ae@latest/rest/guides/building-a-ci-server", - "/ja/free-pro-team@latest/rest/guides/delivering-deployments": "/ja/rest/guides/delivering-deployments", - "/ja/v3/guides/delivering-deployments": "/ja/rest/guides/delivering-deployments", - "/ja/free-pro-team@latest/v3/guides/delivering-deployments": "/ja/rest/guides/delivering-deployments", - "/ja/enterprise/3.0/rest/guides/delivering-deployments": "/ja/enterprise-server@3.0/rest/guides/delivering-deployments", - "/ja/enterprise/rest/guides/delivering-deployments": "/ja/enterprise-server@latest/rest/guides/delivering-deployments", - "/ja/enterprise-server@3.0/v3/guides/delivering-deployments": "/ja/enterprise-server@3.0/rest/guides/delivering-deployments", - "/ja/enterprise/3.0/v3/guides/delivering-deployments": "/ja/enterprise-server@3.0/rest/guides/delivering-deployments", - "/ja/enterprise/v3/guides/delivering-deployments": "/ja/enterprise-server@latest/rest/guides/delivering-deployments", - "/ja/enterprise/2.20/rest/guides/delivering-deployments": "/ja/enterprise-server@2.20/rest/guides/delivering-deployments", - "/ja/enterprise-server@2.20/v3/guides/delivering-deployments": "/ja/enterprise-server@2.20/rest/guides/delivering-deployments", - "/ja/enterprise/2.20/v3/guides/delivering-deployments": "/ja/enterprise-server@2.20/rest/guides/delivering-deployments", - "/ja/github-ae@latest/v3/guides/delivering-deployments": "/ja/github-ae@latest/rest/guides/delivering-deployments", - "/ja/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/ja/rest/guides/discovering-resources-for-a-user", - "/ja/v3/guides/discovering-resources-for-a-user": "/ja/rest/guides/discovering-resources-for-a-user", - "/ja/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/ja/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/ja/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise/rest/guides/discovering-resources-for-a-user": "/ja/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/ja/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/ja/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise/v3/guides/discovering-resources-for-a-user": "/ja/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/ja/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/ja/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/ja/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/ja/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/ja/github-ae@latest/v3/guides/discovering-resources-for-a-user": "/ja/github-ae@latest/rest/guides/discovering-resources-for-a-user", - "/ja/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/ja/rest/guides/getting-started-with-the-checks-api", - "/ja/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/ja/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/ja/enterprise/rest/guides/getting-started-with-the-checks-api": "/ja/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", - "/ja/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/ja/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/ja/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/ja/rest/guides/getting-started-with-the-git-database-api", - "/ja/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/ja/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/ja/enterprise/rest/guides/getting-started-with-the-git-database-api": "/ja/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", - "/ja/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/ja/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/ja/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/ja/rest/guides/getting-started-with-the-rest-api", - "/ja/v3/guides/getting-started": "/ja/rest/guides/getting-started-with-the-rest-api", - "/ja/free-pro-team@latest/v3/guides/getting-started": "/ja/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/ja/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise/rest/guides/getting-started-with-the-rest-api": "/ja/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise-server@3.0/v3/guides/getting-started": "/ja/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise/3.0/v3/guides/getting-started": "/ja/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise/v3/guides/getting-started": "/ja/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/ja/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise-server@2.20/v3/guides/getting-started": "/ja/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/ja/enterprise/2.20/v3/guides/getting-started": "/ja/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/ja/github-ae@latest/v3/guides/getting-started": "/ja/github-ae@latest/rest/guides/getting-started-with-the-rest-api", - "/ja/free-pro-team@latest/rest/guides": "/ja/rest/guides", - "/ja/v3/guides": "/ja/rest/guides", - "/ja/free-pro-team@latest/v3/guides": "/ja/rest/guides", - "/ja/enterprise/3.0/rest/guides": "/ja/enterprise-server@3.0/rest/guides", - "/ja/enterprise/rest/guides": "/ja/enterprise-server@latest/rest/guides", - "/ja/enterprise-server@3.0/v3/guides": "/ja/enterprise-server@3.0/rest/guides", - "/ja/enterprise/3.0/v3/guides": "/ja/enterprise-server@3.0/rest/guides", - "/ja/enterprise/v3/guides": "/ja/enterprise-server@latest/rest/guides", - "/ja/enterprise/2.20/rest/guides": "/ja/enterprise-server@2.20/rest/guides", - "/ja/enterprise-server@2.20/v3/guides": "/ja/enterprise-server@2.20/rest/guides", - "/ja/enterprise/2.20/v3/guides": "/ja/enterprise-server@2.20/rest/guides", - "/ja/github-ae@latest/v3/guides": "/ja/github-ae@latest/rest/guides", - "/ja/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/ja/rest/guides/rendering-data-as-graphs", - "/ja/v3/guides/rendering-data-as-graphs": "/ja/rest/guides/rendering-data-as-graphs", - "/ja/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/ja/rest/guides/rendering-data-as-graphs", - "/ja/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/ja/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/ja/enterprise/rest/guides/rendering-data-as-graphs": "/ja/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/ja/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/ja/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/ja/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/ja/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/ja/enterprise/v3/guides/rendering-data-as-graphs": "/ja/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/ja/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/ja/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/ja/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/ja/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/ja/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/ja/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/ja/github-ae@latest/v3/guides/rendering-data-as-graphs": "/ja/github-ae@latest/rest/guides/rendering-data-as-graphs", - "/ja/free-pro-team@latest/rest/guides/traversing-with-pagination": "/ja/rest/guides/traversing-with-pagination", - "/ja/v3/guides/traversing-with-pagination": "/ja/rest/guides/traversing-with-pagination", - "/ja/free-pro-team@latest/v3/guides/traversing-with-pagination": "/ja/rest/guides/traversing-with-pagination", - "/ja/enterprise/3.0/rest/guides/traversing-with-pagination": "/ja/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/ja/enterprise/rest/guides/traversing-with-pagination": "/ja/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/ja/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/ja/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/ja/enterprise/3.0/v3/guides/traversing-with-pagination": "/ja/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/ja/enterprise/v3/guides/traversing-with-pagination": "/ja/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/ja/enterprise/2.20/rest/guides/traversing-with-pagination": "/ja/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/ja/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/ja/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/ja/enterprise/2.20/v3/guides/traversing-with-pagination": "/ja/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/ja/github-ae@latest/v3/guides/traversing-with-pagination": "/ja/github-ae@latest/rest/guides/traversing-with-pagination", - "/ja/free-pro-team@latest/rest/guides/working-with-comments": "/ja/rest/guides/working-with-comments", - "/ja/v3/guides/working-with-comments": "/ja/rest/guides/working-with-comments", - "/ja/free-pro-team@latest/v3/guides/working-with-comments": "/ja/rest/guides/working-with-comments", - "/ja/enterprise/3.0/rest/guides/working-with-comments": "/ja/enterprise-server@3.0/rest/guides/working-with-comments", - "/ja/enterprise/rest/guides/working-with-comments": "/ja/enterprise-server@latest/rest/guides/working-with-comments", - "/ja/enterprise-server@3.0/v3/guides/working-with-comments": "/ja/enterprise-server@3.0/rest/guides/working-with-comments", - "/ja/enterprise/3.0/v3/guides/working-with-comments": "/ja/enterprise-server@3.0/rest/guides/working-with-comments", - "/ja/enterprise/v3/guides/working-with-comments": "/ja/enterprise-server@latest/rest/guides/working-with-comments", - "/ja/enterprise/2.20/rest/guides/working-with-comments": "/ja/enterprise-server@2.20/rest/guides/working-with-comments", - "/ja/enterprise-server@2.20/v3/guides/working-with-comments": "/ja/enterprise-server@2.20/rest/guides/working-with-comments", - "/ja/enterprise/2.20/v3/guides/working-with-comments": "/ja/enterprise-server@2.20/rest/guides/working-with-comments", - "/ja/github-ae@latest/v3/guides/working-with-comments": "/ja/github-ae@latest/rest/guides/working-with-comments", - "/ja/free-pro-team@latest/rest": "/ja/rest", - "/ja/v3": "/ja/rest", - "/ja/free-pro-team@latest/v3": "/ja/rest", - "/ja/enterprise/3.0/rest": "/ja/enterprise-server@3.0/rest", - "/ja/enterprise/rest": "/ja/enterprise-server@latest/rest", - "/ja/enterprise-server@3.0/v3": "/ja/enterprise-server@3.0/rest", - "/ja/enterprise/3.0/v3": "/ja/enterprise-server@3.0/rest", - "/ja/enterprise/v3": "/ja/enterprise-server@latest/rest", - "/ja/enterprise/2.20/rest": "/ja/enterprise-server@2.20/rest", - "/ja/enterprise-server@2.20/v3": "/ja/enterprise-server@2.20/rest", - "/ja/enterprise/2.20/v3": "/ja/enterprise-server@2.20/rest", - "/ja/github-ae@latest/v3": "/ja/github-ae@latest/rest", - "/ja/free-pro-team@latest/rest/overview/api-previews": "/ja/rest/overview/api-previews", - "/ja/v3/previews": "/ja/rest/overview/api-previews", - "/ja/free-pro-team@latest/v3/previews": "/ja/rest/overview/api-previews", - "/ja/enterprise/3.0/rest/overview/api-previews": "/ja/enterprise-server@3.0/rest/overview/api-previews", - "/ja/enterprise/rest/overview/api-previews": "/ja/enterprise-server@latest/rest/overview/api-previews", - "/ja/enterprise-server@3.0/v3/previews": "/ja/enterprise-server@3.0/rest/overview/api-previews", - "/ja/enterprise/3.0/v3/previews": "/ja/enterprise-server@3.0/rest/overview/api-previews", - "/ja/enterprise/v3/previews": "/ja/enterprise-server@latest/rest/overview/api-previews", - "/ja/enterprise/2.20/rest/overview/api-previews": "/ja/enterprise-server@2.20/rest/overview/api-previews", - "/ja/enterprise-server@2.20/v3/previews": "/ja/enterprise-server@2.20/rest/overview/api-previews", - "/ja/enterprise/2.20/v3/previews": "/ja/enterprise-server@2.20/rest/overview/api-previews", - "/ja/github-ae@latest/v3/previews": "/ja/github-ae@latest/rest/overview/api-previews", - "/ja/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/ja/rest/overview/endpoints-available-for-github-apps", - "/ja/v3/apps/available-endpoints": "/ja/rest/overview/endpoints-available-for-github-apps", - "/ja/free-pro-team@latest/v3/apps/available-endpoints": "/ja/rest/overview/endpoints-available-for-github-apps", - "/ja/rest/reference/endpoints-available-for-github-apps": "/ja/rest/overview/endpoints-available-for-github-apps", - "/ja/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/ja/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/ja/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/rest/overview/endpoints-available-for-github-apps": "/ja/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise-server@3.0/v3/apps/available-endpoints": "/ja/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/3.0/v3/apps/available-endpoints": "/ja/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/v3/apps/available-endpoints": "/ja/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/ja/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/ja/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/rest/reference/endpoints-available-for-github-apps": "/ja/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/ja/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise-server@2.20/v3/apps/available-endpoints": "/ja/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/2.20/v3/apps/available-endpoints": "/ja/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/ja/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/ja/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/ja/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/ja/github-ae@latest/v3/apps/available-endpoints": "/ja/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/ja/github-ae@latest/rest/reference/endpoints-available-for-github-apps": "/ja/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/ja/free-pro-team@latest/rest/overview": "/ja/rest/overview", - "/ja/enterprise/3.0/rest/overview": "/ja/enterprise-server@3.0/rest/overview", - "/ja/enterprise/rest/overview": "/ja/enterprise-server@latest/rest/overview", - "/ja/enterprise/2.20/rest/overview": "/ja/enterprise-server@2.20/rest/overview", - "/ja/free-pro-team@latest/rest/overview/libraries": "/ja/rest/overview/libraries", - "/ja/v3/libraries": "/ja/rest/overview/libraries", - "/ja/free-pro-team@latest/v3/libraries": "/ja/rest/overview/libraries", - "/ja/enterprise/3.0/rest/overview/libraries": "/ja/enterprise-server@3.0/rest/overview/libraries", - "/ja/enterprise/rest/overview/libraries": "/ja/enterprise-server@latest/rest/overview/libraries", - "/ja/enterprise-server@3.0/v3/libraries": "/ja/enterprise-server@3.0/rest/overview/libraries", - "/ja/enterprise/3.0/v3/libraries": "/ja/enterprise-server@3.0/rest/overview/libraries", - "/ja/enterprise/v3/libraries": "/ja/enterprise-server@latest/rest/overview/libraries", - "/ja/enterprise/2.20/rest/overview/libraries": "/ja/enterprise-server@2.20/rest/overview/libraries", - "/ja/enterprise-server@2.20/v3/libraries": "/ja/enterprise-server@2.20/rest/overview/libraries", - "/ja/enterprise/2.20/v3/libraries": "/ja/enterprise-server@2.20/rest/overview/libraries", - "/ja/github-ae@latest/v3/libraries": "/ja/github-ae@latest/rest/overview/libraries", - "/ja/free-pro-team@latest/rest/overview/media-types": "/ja/rest/overview/media-types", - "/ja/v3/media": "/ja/rest/overview/media-types", - "/ja/free-pro-team@latest/v3/media": "/ja/rest/overview/media-types", - "/ja/enterprise/3.0/rest/overview/media-types": "/ja/enterprise-server@3.0/rest/overview/media-types", - "/ja/enterprise/rest/overview/media-types": "/ja/enterprise-server@latest/rest/overview/media-types", - "/ja/enterprise-server@3.0/v3/media": "/ja/enterprise-server@3.0/rest/overview/media-types", - "/ja/enterprise/3.0/v3/media": "/ja/enterprise-server@3.0/rest/overview/media-types", - "/ja/enterprise/v3/media": "/ja/enterprise-server@latest/rest/overview/media-types", - "/ja/enterprise/2.20/rest/overview/media-types": "/ja/enterprise-server@2.20/rest/overview/media-types", - "/ja/enterprise-server@2.20/v3/media": "/ja/enterprise-server@2.20/rest/overview/media-types", - "/ja/enterprise/2.20/v3/media": "/ja/enterprise-server@2.20/rest/overview/media-types", - "/ja/github-ae@latest/v3/media": "/ja/github-ae@latest/rest/overview/media-types", - "/ja/free-pro-team@latest/rest/overview/openapi-description": "/ja/rest/overview/openapi-description", - "/ja/enterprise/3.0/rest/overview/openapi-description": "/ja/enterprise-server@3.0/rest/overview/openapi-description", - "/ja/enterprise/rest/overview/openapi-description": "/ja/enterprise-server@latest/rest/overview/openapi-description", - "/ja/enterprise/2.20/rest/overview/openapi-description": "/ja/enterprise-server@2.20/rest/overview/openapi-description", - "/ja/free-pro-team@latest/rest/overview/other-authentication-methods": "/ja/rest/overview/other-authentication-methods", - "/ja/v3/auth": "/ja/rest/overview/other-authentication-methods", - "/ja/free-pro-team@latest/v3/auth": "/ja/rest/overview/other-authentication-methods", - "/ja/enterprise/3.0/rest/overview/other-authentication-methods": "/ja/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/ja/enterprise/rest/overview/other-authentication-methods": "/ja/enterprise-server@latest/rest/overview/other-authentication-methods", - "/ja/enterprise-server@3.0/v3/auth": "/ja/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/ja/enterprise/3.0/v3/auth": "/ja/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/ja/enterprise/v3/auth": "/ja/enterprise-server@latest/rest/overview/other-authentication-methods", - "/ja/enterprise/2.20/rest/overview/other-authentication-methods": "/ja/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/ja/enterprise-server@2.20/v3/auth": "/ja/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/ja/enterprise/2.20/v3/auth": "/ja/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/ja/github-ae@latest/v3/auth": "/ja/github-ae@latest/rest/overview/other-authentication-methods", - "/ja/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/ja/rest/overview/resources-in-the-rest-api", - "/ja/rest/initialize-the-repo": "/ja/rest/overview/resources-in-the-rest-api", - "/ja/free-pro-team@latest/rest/initialize-the-repo": "/ja/rest/overview/resources-in-the-rest-api", - "/ja/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/ja/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/ja/enterprise/rest/overview/resources-in-the-rest-api": "/ja/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/ja/enterprise-server@3.0/rest/initialize-the-repo": "/ja/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/ja/enterprise/3.0/rest/initialize-the-repo": "/ja/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/ja/enterprise/rest/initialize-the-repo": "/ja/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/ja/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/ja/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/ja/enterprise-server@2.20/rest/initialize-the-repo": "/ja/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/ja/enterprise/2.20/rest/initialize-the-repo": "/ja/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/ja/github-ae@latest/rest/initialize-the-repo": "/ja/github-ae@latest/rest/overview/resources-in-the-rest-api", - "/ja/free-pro-team@latest/rest/overview/troubleshooting": "/ja/rest/overview/troubleshooting", - "/ja/v3/troubleshooting": "/ja/rest/overview/troubleshooting", - "/ja/free-pro-team@latest/v3/troubleshooting": "/ja/rest/overview/troubleshooting", - "/ja/enterprise/3.0/rest/overview/troubleshooting": "/ja/enterprise-server@3.0/rest/overview/troubleshooting", - "/ja/enterprise/rest/overview/troubleshooting": "/ja/enterprise-server@latest/rest/overview/troubleshooting", - "/ja/enterprise-server@3.0/v3/troubleshooting": "/ja/enterprise-server@3.0/rest/overview/troubleshooting", - "/ja/enterprise/3.0/v3/troubleshooting": "/ja/enterprise-server@3.0/rest/overview/troubleshooting", - "/ja/enterprise/v3/troubleshooting": "/ja/enterprise-server@latest/rest/overview/troubleshooting", - "/ja/enterprise/2.20/rest/overview/troubleshooting": "/ja/enterprise-server@2.20/rest/overview/troubleshooting", - "/ja/enterprise-server@2.20/v3/troubleshooting": "/ja/enterprise-server@2.20/rest/overview/troubleshooting", - "/ja/enterprise/2.20/v3/troubleshooting": "/ja/enterprise-server@2.20/rest/overview/troubleshooting", - "/ja/github-ae@latest/v3/troubleshooting": "/ja/github-ae@latest/rest/overview/troubleshooting", - "/ja/free-pro-team@latest/rest/reference/actions": "/ja/rest/reference/actions", - "/ja/v3/actions": "/ja/rest/reference/actions", - "/ja/free-pro-team@latest/v3/actions": "/ja/rest/reference/actions", - "/ja/enterprise/3.0/rest/reference/actions": "/ja/enterprise-server@3.0/rest/reference/actions", - "/ja/enterprise/rest/reference/actions": "/ja/enterprise-server@latest/rest/reference/actions", - "/ja/enterprise-server@3.0/v3/actions": "/ja/enterprise-server@3.0/rest/reference/actions", - "/ja/enterprise/3.0/v3/actions": "/ja/enterprise-server@3.0/rest/reference/actions", - "/ja/enterprise/v3/actions": "/ja/enterprise-server@latest/rest/reference/actions", - "/ja/free-pro-team@latest/rest/reference/activity": "/ja/rest/reference/activity", - "/ja/v3/activity": "/ja/rest/reference/activity", - "/ja/free-pro-team@latest/v3/activity": "/ja/rest/reference/activity", - "/ja/enterprise/3.0/rest/reference/activity": "/ja/enterprise-server@3.0/rest/reference/activity", - "/ja/enterprise/rest/reference/activity": "/ja/enterprise-server@latest/rest/reference/activity", - "/ja/enterprise-server@3.0/v3/activity": "/ja/enterprise-server@3.0/rest/reference/activity", - "/ja/enterprise/3.0/v3/activity": "/ja/enterprise-server@3.0/rest/reference/activity", - "/ja/enterprise/v3/activity": "/ja/enterprise-server@latest/rest/reference/activity", - "/ja/enterprise/2.20/rest/reference/activity": "/ja/enterprise-server@2.20/rest/reference/activity", - "/ja/enterprise-server@2.20/v3/activity": "/ja/enterprise-server@2.20/rest/reference/activity", - "/ja/enterprise/2.20/v3/activity": "/ja/enterprise-server@2.20/rest/reference/activity", - "/ja/github-ae@latest/v3/activity": "/ja/github-ae@latest/rest/reference/activity", - "/ja/free-pro-team@latest/rest/reference/apps": "/ja/rest/reference/apps", - "/ja/v3/apps": "/ja/rest/reference/apps", - "/ja/free-pro-team@latest/v3/apps": "/ja/rest/reference/apps", - "/ja/enterprise/3.0/rest/reference/apps": "/ja/enterprise-server@3.0/rest/reference/apps", - "/ja/enterprise/rest/reference/apps": "/ja/enterprise-server@latest/rest/reference/apps", - "/ja/enterprise-server@3.0/v3/apps": "/ja/enterprise-server@3.0/rest/reference/apps", - "/ja/enterprise/3.0/v3/apps": "/ja/enterprise-server@3.0/rest/reference/apps", - "/ja/enterprise/v3/apps": "/ja/enterprise-server@latest/rest/reference/apps", - "/ja/enterprise/2.20/rest/reference/apps": "/ja/enterprise-server@2.20/rest/reference/apps", - "/ja/enterprise-server@2.20/v3/apps": "/ja/enterprise-server@2.20/rest/reference/apps", - "/ja/enterprise/2.20/v3/apps": "/ja/enterprise-server@2.20/rest/reference/apps", - "/ja/github-ae@latest/v3/apps": "/ja/github-ae@latest/rest/reference/apps", - "/ja/free-pro-team@latest/rest/reference/billing": "/ja/rest/reference/billing", - "/ja/free-pro-team@latest/rest/reference/checks": "/ja/rest/reference/checks", - "/ja/v3/checks": "/ja/rest/reference/checks", - "/ja/free-pro-team@latest/v3/checks": "/ja/rest/reference/checks", - "/ja/enterprise/3.0/rest/reference/checks": "/ja/enterprise-server@3.0/rest/reference/checks", - "/ja/enterprise/rest/reference/checks": "/ja/enterprise-server@latest/rest/reference/checks", - "/ja/enterprise-server@3.0/v3/checks": "/ja/enterprise-server@3.0/rest/reference/checks", - "/ja/enterprise/3.0/v3/checks": "/ja/enterprise-server@3.0/rest/reference/checks", - "/ja/enterprise/v3/checks": "/ja/enterprise-server@latest/rest/reference/checks", - "/ja/enterprise/2.20/rest/reference/checks": "/ja/enterprise-server@2.20/rest/reference/checks", - "/ja/enterprise-server@2.20/v3/checks": "/ja/enterprise-server@2.20/rest/reference/checks", - "/ja/enterprise/2.20/v3/checks": "/ja/enterprise-server@2.20/rest/reference/checks", - "/ja/github-ae@latest/v3/checks": "/ja/github-ae@latest/rest/reference/checks", - "/ja/free-pro-team@latest/rest/reference/code-scanning": "/ja/rest/reference/code-scanning", - "/ja/v3/code-scanning": "/ja/rest/reference/code-scanning", - "/ja/free-pro-team@latest/v3/code-scanning": "/ja/rest/reference/code-scanning", - "/ja/enterprise/3.0/rest/reference/code-scanning": "/ja/enterprise-server@3.0/rest/reference/code-scanning", - "/ja/enterprise/rest/reference/code-scanning": "/ja/enterprise-server@latest/rest/reference/code-scanning", - "/ja/enterprise-server@3.0/v3/code-scanning": "/ja/enterprise-server@3.0/rest/reference/code-scanning", - "/ja/enterprise/3.0/v3/code-scanning": "/ja/enterprise-server@3.0/rest/reference/code-scanning", - "/ja/enterprise/v3/code-scanning": "/ja/enterprise-server@latest/rest/reference/code-scanning", - "/ja/free-pro-team@latest/rest/reference/codes-of-conduct": "/ja/rest/reference/codes-of-conduct", - "/ja/v3/codes_of_conduct": "/ja/rest/reference/codes-of-conduct", - "/ja/free-pro-team@latest/v3/codes_of_conduct": "/ja/rest/reference/codes-of-conduct", - "/ja/v3/codes-of-conduct": "/ja/rest/reference/codes-of-conduct", - "/ja/free-pro-team@latest/v3/codes-of-conduct": "/ja/rest/reference/codes-of-conduct", - "/ja/enterprise/3.0/rest/reference/codes-of-conduct": "/ja/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/ja/enterprise/rest/reference/codes-of-conduct": "/ja/enterprise-server@latest/rest/reference/codes-of-conduct", - "/ja/enterprise-server@3.0/v3/codes_of_conduct": "/ja/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/ja/enterprise/3.0/v3/codes_of_conduct": "/ja/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/ja/enterprise/v3/codes_of_conduct": "/ja/enterprise-server@latest/rest/reference/codes-of-conduct", - "/ja/enterprise-server@3.0/v3/codes-of-conduct": "/ja/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/ja/enterprise/3.0/v3/codes-of-conduct": "/ja/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/ja/enterprise/v3/codes-of-conduct": "/ja/enterprise-server@latest/rest/reference/codes-of-conduct", - "/ja/enterprise/2.20/rest/reference/codes-of-conduct": "/ja/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/ja/enterprise-server@2.20/v3/codes_of_conduct": "/ja/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/ja/enterprise/2.20/v3/codes_of_conduct": "/ja/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/ja/enterprise-server@2.20/v3/codes-of-conduct": "/ja/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/ja/enterprise/2.20/v3/codes-of-conduct": "/ja/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/ja/github-ae@latest/v3/codes_of_conduct": "/ja/github-ae@latest/rest/reference/codes-of-conduct", - "/ja/github-ae@latest/v3/codes-of-conduct": "/ja/github-ae@latest/rest/reference/codes-of-conduct", - "/ja/free-pro-team@latest/rest/reference/emojis": "/ja/rest/reference/emojis", - "/ja/v3/emojis": "/ja/rest/reference/emojis", - "/ja/free-pro-team@latest/v3/emojis": "/ja/rest/reference/emojis", - "/ja/v3/misc": "/ja/rest/reference/emojis", - "/ja/free-pro-team@latest/v3/misc": "/ja/rest/reference/emojis", - "/ja/enterprise/3.0/rest/reference/emojis": "/ja/enterprise-server@3.0/rest/reference/emojis", - "/ja/enterprise/rest/reference/emojis": "/ja/enterprise-server@latest/rest/reference/emojis", - "/ja/enterprise-server@3.0/v3/emojis": "/ja/enterprise-server@3.0/rest/reference/emojis", - "/ja/enterprise/3.0/v3/emojis": "/ja/enterprise-server@3.0/rest/reference/emojis", - "/ja/enterprise/v3/emojis": "/ja/enterprise-server@latest/rest/reference/emojis", - "/ja/enterprise-server@3.0/v3/misc": "/ja/enterprise-server@3.0/rest/reference/emojis", - "/ja/enterprise/3.0/v3/misc": "/ja/enterprise-server@3.0/rest/reference/emojis", - "/ja/enterprise/v3/misc": "/ja/enterprise-server@latest/rest/reference/emojis", - "/ja/enterprise/2.20/rest/reference/emojis": "/ja/enterprise-server@2.20/rest/reference/emojis", - "/ja/enterprise-server@2.20/v3/emojis": "/ja/enterprise-server@2.20/rest/reference/emojis", - "/ja/enterprise/2.20/v3/emojis": "/ja/enterprise-server@2.20/rest/reference/emojis", - "/ja/enterprise-server@2.20/v3/misc": "/ja/enterprise-server@2.20/rest/reference/emojis", - "/ja/enterprise/2.20/v3/misc": "/ja/enterprise-server@2.20/rest/reference/emojis", - "/ja/github-ae@latest/v3/emojis": "/ja/github-ae@latest/rest/reference/emojis", - "/ja/github-ae@latest/v3/misc": "/ja/github-ae@latest/rest/reference/emojis", - "/ja/free-pro-team@latest/rest/reference/enterprise-admin": "/ja/rest/reference/enterprise-admin", - "/ja/v3/enterprise-admin": "/ja/rest/reference/enterprise-admin", - "/ja/free-pro-team@latest/v3/enterprise-admin": "/ja/rest/reference/enterprise-admin", - "/ja/v3/enterprise": "/ja/rest/reference/enterprise-admin", - "/ja/free-pro-team@latest/v3/enterprise": "/ja/rest/reference/enterprise-admin", - "/ja/enterprise/3.0/rest/reference/enterprise-admin": "/ja/enterprise-server@3.0/rest/reference/enterprise-admin", - "/ja/enterprise/rest/reference/enterprise-admin": "/ja/enterprise-server@latest/rest/reference/enterprise-admin", - "/ja/enterprise-server@3.0/v3/enterprise-admin": "/ja/enterprise-server@3.0/rest/reference/enterprise-admin", - "/ja/enterprise/3.0/v3/enterprise-admin": "/ja/enterprise-server@3.0/rest/reference/enterprise-admin", - "/ja/enterprise/v3/enterprise-admin": "/ja/enterprise-server@latest/rest/reference/enterprise-admin", - "/ja/enterprise-server@3.0/v3/enterprise": "/ja/enterprise-server@3.0/rest/reference/enterprise-admin", - "/ja/enterprise/3.0/v3/enterprise": "/ja/enterprise-server@3.0/rest/reference/enterprise-admin", - "/ja/enterprise/v3/enterprise": "/ja/enterprise-server@latest/rest/reference/enterprise-admin", - "/ja/enterprise/2.20/rest/reference/enterprise-admin": "/ja/enterprise-server@2.20/rest/reference/enterprise-admin", - "/ja/enterprise-server@2.20/v3/enterprise-admin": "/ja/enterprise-server@2.20/rest/reference/enterprise-admin", - "/ja/enterprise/2.20/v3/enterprise-admin": "/ja/enterprise-server@2.20/rest/reference/enterprise-admin", - "/ja/enterprise-server@2.20/v3/enterprise": "/ja/enterprise-server@2.20/rest/reference/enterprise-admin", - "/ja/enterprise/2.20/v3/enterprise": "/ja/enterprise-server@2.20/rest/reference/enterprise-admin", - "/ja/github-ae@latest/v3/enterprise-admin": "/ja/github-ae@latest/rest/reference/enterprise-admin", - "/ja/github-ae@latest/v3/enterprise": "/ja/github-ae@latest/rest/reference/enterprise-admin", - "/ja/free-pro-team@latest/rest/reference/gists": "/ja/rest/reference/gists", - "/ja/v3/gists": "/ja/rest/reference/gists", - "/ja/free-pro-team@latest/v3/gists": "/ja/rest/reference/gists", - "/ja/enterprise/3.0/rest/reference/gists": "/ja/enterprise-server@3.0/rest/reference/gists", - "/ja/enterprise/rest/reference/gists": "/ja/enterprise-server@latest/rest/reference/gists", - "/ja/enterprise-server@3.0/v3/gists": "/ja/enterprise-server@3.0/rest/reference/gists", - "/ja/enterprise/3.0/v3/gists": "/ja/enterprise-server@3.0/rest/reference/gists", - "/ja/enterprise/v3/gists": "/ja/enterprise-server@latest/rest/reference/gists", - "/ja/enterprise/2.20/rest/reference/gists": "/ja/enterprise-server@2.20/rest/reference/gists", - "/ja/enterprise-server@2.20/v3/gists": "/ja/enterprise-server@2.20/rest/reference/gists", - "/ja/enterprise/2.20/v3/gists": "/ja/enterprise-server@2.20/rest/reference/gists", - "/ja/github-ae@latest/v3/gists": "/ja/github-ae@latest/rest/reference/gists", - "/ja/free-pro-team@latest/rest/reference/git": "/ja/rest/reference/git", - "/ja/v3/git": "/ja/rest/reference/git", - "/ja/free-pro-team@latest/v3/git": "/ja/rest/reference/git", - "/ja/enterprise/3.0/rest/reference/git": "/ja/enterprise-server@3.0/rest/reference/git", - "/ja/enterprise/rest/reference/git": "/ja/enterprise-server@latest/rest/reference/git", - "/ja/enterprise-server@3.0/v3/git": "/ja/enterprise-server@3.0/rest/reference/git", - "/ja/enterprise/3.0/v3/git": "/ja/enterprise-server@3.0/rest/reference/git", - "/ja/enterprise/v3/git": "/ja/enterprise-server@latest/rest/reference/git", - "/ja/enterprise/2.20/rest/reference/git": "/ja/enterprise-server@2.20/rest/reference/git", - "/ja/enterprise-server@2.20/v3/git": "/ja/enterprise-server@2.20/rest/reference/git", - "/ja/enterprise/2.20/v3/git": "/ja/enterprise-server@2.20/rest/reference/git", - "/ja/github-ae@latest/v3/git": "/ja/github-ae@latest/rest/reference/git", - "/ja/free-pro-team@latest/rest/reference/gitignore": "/ja/rest/reference/gitignore", - "/ja/v3/gitignore": "/ja/rest/reference/gitignore", - "/ja/free-pro-team@latest/v3/gitignore": "/ja/rest/reference/gitignore", - "/ja/enterprise/3.0/rest/reference/gitignore": "/ja/enterprise-server@3.0/rest/reference/gitignore", - "/ja/enterprise/rest/reference/gitignore": "/ja/enterprise-server@latest/rest/reference/gitignore", - "/ja/enterprise-server@3.0/v3/gitignore": "/ja/enterprise-server@3.0/rest/reference/gitignore", - "/ja/enterprise/3.0/v3/gitignore": "/ja/enterprise-server@3.0/rest/reference/gitignore", - "/ja/enterprise/v3/gitignore": "/ja/enterprise-server@latest/rest/reference/gitignore", - "/ja/enterprise/2.20/rest/reference/gitignore": "/ja/enterprise-server@2.20/rest/reference/gitignore", - "/ja/enterprise-server@2.20/v3/gitignore": "/ja/enterprise-server@2.20/rest/reference/gitignore", - "/ja/enterprise/2.20/v3/gitignore": "/ja/enterprise-server@2.20/rest/reference/gitignore", - "/ja/github-ae@latest/v3/gitignore": "/ja/github-ae@latest/rest/reference/gitignore", - "/ja/free-pro-team@latest/rest/reference": "/ja/rest/reference", - "/ja/enterprise/3.0/rest/reference": "/ja/enterprise-server@3.0/rest/reference", - "/ja/enterprise/rest/reference": "/ja/enterprise-server@latest/rest/reference", - "/ja/enterprise/2.20/rest/reference": "/ja/enterprise-server@2.20/rest/reference", - "/ja/free-pro-team@latest/rest/reference/interactions": "/ja/rest/reference/interactions", - "/ja/v3/interactions": "/ja/rest/reference/interactions", - "/ja/free-pro-team@latest/v3/interactions": "/ja/rest/reference/interactions", - "/ja/free-pro-team@latest/rest/reference/issues": "/ja/rest/reference/issues", - "/ja/v3/issues": "/ja/rest/reference/issues", - "/ja/free-pro-team@latest/v3/issues": "/ja/rest/reference/issues", - "/ja/enterprise/3.0/rest/reference/issues": "/ja/enterprise-server@3.0/rest/reference/issues", - "/ja/enterprise/rest/reference/issues": "/ja/enterprise-server@latest/rest/reference/issues", - "/ja/enterprise-server@3.0/v3/issues": "/ja/enterprise-server@3.0/rest/reference/issues", - "/ja/enterprise/3.0/v3/issues": "/ja/enterprise-server@3.0/rest/reference/issues", - "/ja/enterprise/v3/issues": "/ja/enterprise-server@latest/rest/reference/issues", - "/ja/enterprise/2.20/rest/reference/issues": "/ja/enterprise-server@2.20/rest/reference/issues", - "/ja/enterprise-server@2.20/v3/issues": "/ja/enterprise-server@2.20/rest/reference/issues", - "/ja/enterprise/2.20/v3/issues": "/ja/enterprise-server@2.20/rest/reference/issues", - "/ja/github-ae@latest/v3/issues": "/ja/github-ae@latest/rest/reference/issues", - "/ja/free-pro-team@latest/rest/reference/licenses": "/ja/rest/reference/licenses", - "/ja/v3/licenses": "/ja/rest/reference/licenses", - "/ja/free-pro-team@latest/v3/licenses": "/ja/rest/reference/licenses", - "/ja/enterprise/3.0/rest/reference/licenses": "/ja/enterprise-server@3.0/rest/reference/licenses", - "/ja/enterprise/rest/reference/licenses": "/ja/enterprise-server@latest/rest/reference/licenses", - "/ja/enterprise-server@3.0/v3/licenses": "/ja/enterprise-server@3.0/rest/reference/licenses", - "/ja/enterprise/3.0/v3/licenses": "/ja/enterprise-server@3.0/rest/reference/licenses", - "/ja/enterprise/v3/licenses": "/ja/enterprise-server@latest/rest/reference/licenses", - "/ja/enterprise/2.20/rest/reference/licenses": "/ja/enterprise-server@2.20/rest/reference/licenses", - "/ja/enterprise-server@2.20/v3/licenses": "/ja/enterprise-server@2.20/rest/reference/licenses", - "/ja/enterprise/2.20/v3/licenses": "/ja/enterprise-server@2.20/rest/reference/licenses", - "/ja/github-ae@latest/v3/licenses": "/ja/github-ae@latest/rest/reference/licenses", - "/ja/free-pro-team@latest/rest/reference/markdown": "/ja/rest/reference/markdown", - "/ja/v3/markdown": "/ja/rest/reference/markdown", - "/ja/free-pro-team@latest/v3/markdown": "/ja/rest/reference/markdown", - "/ja/enterprise/3.0/rest/reference/markdown": "/ja/enterprise-server@3.0/rest/reference/markdown", - "/ja/enterprise/rest/reference/markdown": "/ja/enterprise-server@latest/rest/reference/markdown", - "/ja/enterprise-server@3.0/v3/markdown": "/ja/enterprise-server@3.0/rest/reference/markdown", - "/ja/enterprise/3.0/v3/markdown": "/ja/enterprise-server@3.0/rest/reference/markdown", - "/ja/enterprise/v3/markdown": "/ja/enterprise-server@latest/rest/reference/markdown", - "/ja/enterprise/2.20/rest/reference/markdown": "/ja/enterprise-server@2.20/rest/reference/markdown", - "/ja/enterprise-server@2.20/v3/markdown": "/ja/enterprise-server@2.20/rest/reference/markdown", - "/ja/enterprise/2.20/v3/markdown": "/ja/enterprise-server@2.20/rest/reference/markdown", - "/ja/github-ae@latest/v3/markdown": "/ja/github-ae@latest/rest/reference/markdown", - "/ja/free-pro-team@latest/rest/reference/meta": "/ja/rest/reference/meta", - "/ja/v3/meta": "/ja/rest/reference/meta", - "/ja/free-pro-team@latest/v3/meta": "/ja/rest/reference/meta", - "/ja/enterprise/3.0/rest/reference/meta": "/ja/enterprise-server@3.0/rest/reference/meta", - "/ja/enterprise/rest/reference/meta": "/ja/enterprise-server@latest/rest/reference/meta", - "/ja/enterprise-server@3.0/v3/meta": "/ja/enterprise-server@3.0/rest/reference/meta", - "/ja/enterprise/3.0/v3/meta": "/ja/enterprise-server@3.0/rest/reference/meta", - "/ja/enterprise/v3/meta": "/ja/enterprise-server@latest/rest/reference/meta", - "/ja/enterprise/2.20/rest/reference/meta": "/ja/enterprise-server@2.20/rest/reference/meta", - "/ja/enterprise-server@2.20/v3/meta": "/ja/enterprise-server@2.20/rest/reference/meta", - "/ja/enterprise/2.20/v3/meta": "/ja/enterprise-server@2.20/rest/reference/meta", - "/ja/github-ae@latest/v3/meta": "/ja/github-ae@latest/rest/reference/meta", - "/ja/free-pro-team@latest/rest/reference/migrations": "/ja/rest/reference/migrations", - "/ja/v3/migrations": "/ja/rest/reference/migrations", - "/ja/free-pro-team@latest/v3/migrations": "/ja/rest/reference/migrations", - "/ja/v3/migration": "/ja/rest/reference/migrations", - "/ja/free-pro-team@latest/v3/migration": "/ja/rest/reference/migrations", - "/ja/v3/migration/migrations": "/ja/rest/reference/migrations", - "/ja/free-pro-team@latest/v3/migration/migrations": "/ja/rest/reference/migrations", - "/ja/enterprise/3.0/rest/reference/oauth-authorizations": "/ja/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/ja/enterprise/rest/reference/oauth-authorizations": "/ja/enterprise-server@latest/rest/reference/oauth-authorizations", - "/ja/enterprise-server@3.0/v3/oauth_authorizations": "/ja/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/ja/enterprise/3.0/v3/oauth_authorizations": "/ja/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/ja/enterprise/v3/oauth_authorizations": "/ja/enterprise-server@latest/rest/reference/oauth-authorizations", - "/ja/enterprise-server@3.0/v3/oauth-authorizations": "/ja/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/ja/enterprise/3.0/v3/oauth-authorizations": "/ja/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/ja/enterprise/v3/oauth-authorizations": "/ja/enterprise-server@latest/rest/reference/oauth-authorizations", - "/ja/enterprise/2.20/rest/reference/oauth-authorizations": "/ja/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/ja/enterprise-server@2.20/v3/oauth_authorizations": "/ja/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/ja/enterprise/2.20/v3/oauth_authorizations": "/ja/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/ja/enterprise-server@2.20/v3/oauth-authorizations": "/ja/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/ja/enterprise/2.20/v3/oauth-authorizations": "/ja/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/ja/free-pro-team@latest/rest/reference/orgs": "/ja/rest/reference/orgs", - "/ja/v3/orgs": "/ja/rest/reference/orgs", - "/ja/free-pro-team@latest/v3/orgs": "/ja/rest/reference/orgs", - "/ja/enterprise/3.0/rest/reference/orgs": "/ja/enterprise-server@3.0/rest/reference/orgs", - "/ja/enterprise/rest/reference/orgs": "/ja/enterprise-server@latest/rest/reference/orgs", - "/ja/enterprise-server@3.0/v3/orgs": "/ja/enterprise-server@3.0/rest/reference/orgs", - "/ja/enterprise/3.0/v3/orgs": "/ja/enterprise-server@3.0/rest/reference/orgs", - "/ja/enterprise/v3/orgs": "/ja/enterprise-server@latest/rest/reference/orgs", - "/ja/enterprise/2.20/rest/reference/orgs": "/ja/enterprise-server@2.20/rest/reference/orgs", - "/ja/enterprise-server@2.20/v3/orgs": "/ja/enterprise-server@2.20/rest/reference/orgs", - "/ja/enterprise/2.20/v3/orgs": "/ja/enterprise-server@2.20/rest/reference/orgs", - "/ja/github-ae@latest/v3/orgs": "/ja/github-ae@latest/rest/reference/orgs", - "/ja/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/ja/rest/reference/permissions-required-for-github-apps", - "/ja/v3/apps/permissions": "/ja/rest/reference/permissions-required-for-github-apps", - "/ja/free-pro-team@latest/v3/apps/permissions": "/ja/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/ja/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise/rest/reference/permissions-required-for-github-apps": "/ja/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise-server@3.0/v3/apps/permissions": "/ja/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise/3.0/v3/apps/permissions": "/ja/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise/v3/apps/permissions": "/ja/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/ja/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise-server@2.20/v3/apps/permissions": "/ja/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/ja/enterprise/2.20/v3/apps/permissions": "/ja/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/ja/github-ae@latest/v3/apps/permissions": "/ja/github-ae@latest/rest/reference/permissions-required-for-github-apps", - "/ja/free-pro-team@latest/rest/reference/projects": "/ja/rest/reference/projects", - "/ja/v3/projects": "/ja/rest/reference/projects", - "/ja/free-pro-team@latest/v3/projects": "/ja/rest/reference/projects", - "/ja/enterprise/3.0/rest/reference/projects": "/ja/enterprise-server@3.0/rest/reference/projects", - "/ja/enterprise/rest/reference/projects": "/ja/enterprise-server@latest/rest/reference/projects", - "/ja/enterprise-server@3.0/v3/projects": "/ja/enterprise-server@3.0/rest/reference/projects", - "/ja/enterprise/3.0/v3/projects": "/ja/enterprise-server@3.0/rest/reference/projects", - "/ja/enterprise/v3/projects": "/ja/enterprise-server@latest/rest/reference/projects", - "/ja/enterprise/2.20/rest/reference/projects": "/ja/enterprise-server@2.20/rest/reference/projects", - "/ja/enterprise-server@2.20/v3/projects": "/ja/enterprise-server@2.20/rest/reference/projects", - "/ja/enterprise/2.20/v3/projects": "/ja/enterprise-server@2.20/rest/reference/projects", - "/ja/github-ae@latest/v3/projects": "/ja/github-ae@latest/rest/reference/projects", - "/ja/free-pro-team@latest/rest/reference/pulls": "/ja/rest/reference/pulls", - "/ja/v3/pulls": "/ja/rest/reference/pulls", - "/ja/free-pro-team@latest/v3/pulls": "/ja/rest/reference/pulls", - "/ja/enterprise/3.0/rest/reference/pulls": "/ja/enterprise-server@3.0/rest/reference/pulls", - "/ja/enterprise/rest/reference/pulls": "/ja/enterprise-server@latest/rest/reference/pulls", - "/ja/enterprise-server@3.0/v3/pulls": "/ja/enterprise-server@3.0/rest/reference/pulls", - "/ja/enterprise/3.0/v3/pulls": "/ja/enterprise-server@3.0/rest/reference/pulls", - "/ja/enterprise/v3/pulls": "/ja/enterprise-server@latest/rest/reference/pulls", - "/ja/enterprise/2.20/rest/reference/pulls": "/ja/enterprise-server@2.20/rest/reference/pulls", - "/ja/enterprise-server@2.20/v3/pulls": "/ja/enterprise-server@2.20/rest/reference/pulls", - "/ja/enterprise/2.20/v3/pulls": "/ja/enterprise-server@2.20/rest/reference/pulls", - "/ja/github-ae@latest/v3/pulls": "/ja/github-ae@latest/rest/reference/pulls", - "/ja/free-pro-team@latest/rest/reference/rate-limit": "/ja/rest/reference/rate-limit", - "/ja/v3/rate_limit": "/ja/rest/reference/rate-limit", - "/ja/free-pro-team@latest/v3/rate_limit": "/ja/rest/reference/rate-limit", - "/ja/v3/rate-limit": "/ja/rest/reference/rate-limit", - "/ja/free-pro-team@latest/v3/rate-limit": "/ja/rest/reference/rate-limit", - "/ja/enterprise/3.0/rest/reference/rate-limit": "/ja/enterprise-server@3.0/rest/reference/rate-limit", - "/ja/enterprise/rest/reference/rate-limit": "/ja/enterprise-server@latest/rest/reference/rate-limit", - "/ja/enterprise-server@3.0/v3/rate_limit": "/ja/enterprise-server@3.0/rest/reference/rate-limit", - "/ja/enterprise/3.0/v3/rate_limit": "/ja/enterprise-server@3.0/rest/reference/rate-limit", - "/ja/enterprise/v3/rate_limit": "/ja/enterprise-server@latest/rest/reference/rate-limit", - "/ja/enterprise-server@3.0/v3/rate-limit": "/ja/enterprise-server@3.0/rest/reference/rate-limit", - "/ja/enterprise/3.0/v3/rate-limit": "/ja/enterprise-server@3.0/rest/reference/rate-limit", - "/ja/enterprise/v3/rate-limit": "/ja/enterprise-server@latest/rest/reference/rate-limit", - "/ja/enterprise/2.20/rest/reference/rate-limit": "/ja/enterprise-server@2.20/rest/reference/rate-limit", - "/ja/enterprise-server@2.20/v3/rate_limit": "/ja/enterprise-server@2.20/rest/reference/rate-limit", - "/ja/enterprise/2.20/v3/rate_limit": "/ja/enterprise-server@2.20/rest/reference/rate-limit", - "/ja/enterprise-server@2.20/v3/rate-limit": "/ja/enterprise-server@2.20/rest/reference/rate-limit", - "/ja/enterprise/2.20/v3/rate-limit": "/ja/enterprise-server@2.20/rest/reference/rate-limit", - "/ja/github-ae@latest/v3/rate_limit": "/ja/github-ae@latest/rest/reference/rate-limit", - "/ja/github-ae@latest/v3/rate-limit": "/ja/github-ae@latest/rest/reference/rate-limit", - "/ja/free-pro-team@latest/rest/reference/reactions": "/ja/rest/reference/reactions", - "/ja/v3/reactions": "/ja/rest/reference/reactions", - "/ja/free-pro-team@latest/v3/reactions": "/ja/rest/reference/reactions", - "/ja/enterprise/3.0/rest/reference/reactions": "/ja/enterprise-server@3.0/rest/reference/reactions", - "/ja/enterprise/rest/reference/reactions": "/ja/enterprise-server@latest/rest/reference/reactions", - "/ja/enterprise-server@3.0/v3/reactions": "/ja/enterprise-server@3.0/rest/reference/reactions", - "/ja/enterprise/3.0/v3/reactions": "/ja/enterprise-server@3.0/rest/reference/reactions", - "/ja/enterprise/v3/reactions": "/ja/enterprise-server@latest/rest/reference/reactions", - "/ja/enterprise/2.20/rest/reference/reactions": "/ja/enterprise-server@2.20/rest/reference/reactions", - "/ja/enterprise-server@2.20/v3/reactions": "/ja/enterprise-server@2.20/rest/reference/reactions", - "/ja/enterprise/2.20/v3/reactions": "/ja/enterprise-server@2.20/rest/reference/reactions", - "/ja/github-ae@latest/v3/reactions": "/ja/github-ae@latest/rest/reference/reactions", - "/ja/free-pro-team@latest/rest/reference/repos": "/ja/rest/reference/repos", - "/ja/v3/repos": "/ja/rest/reference/repos", - "/ja/free-pro-team@latest/v3/repos": "/ja/rest/reference/repos", - "/ja/enterprise/3.0/rest/reference/repos": "/ja/enterprise-server@3.0/rest/reference/repos", - "/ja/enterprise/rest/reference/repos": "/ja/enterprise-server@latest/rest/reference/repos", - "/ja/enterprise-server@3.0/v3/repos": "/ja/enterprise-server@3.0/rest/reference/repos", - "/ja/enterprise/3.0/v3/repos": "/ja/enterprise-server@3.0/rest/reference/repos", - "/ja/enterprise/v3/repos": "/ja/enterprise-server@latest/rest/reference/repos", - "/ja/enterprise/2.20/rest/reference/repos": "/ja/enterprise-server@2.20/rest/reference/repos", - "/ja/enterprise-server@2.20/v3/repos": "/ja/enterprise-server@2.20/rest/reference/repos", - "/ja/enterprise/2.20/v3/repos": "/ja/enterprise-server@2.20/rest/reference/repos", - "/ja/github-ae@latest/v3/repos": "/ja/github-ae@latest/rest/reference/repos", - "/ja/free-pro-team@latest/rest/reference/scim": "/ja/rest/reference/scim", - "/ja/v3/scim": "/ja/rest/reference/scim", - "/ja/free-pro-team@latest/v3/scim": "/ja/rest/reference/scim", - "/ja/free-pro-team@latest/rest/reference/search": "/ja/rest/reference/search", - "/ja/v3/search": "/ja/rest/reference/search", - "/ja/free-pro-team@latest/v3/search": "/ja/rest/reference/search", - "/ja/enterprise/3.0/rest/reference/search": "/ja/enterprise-server@3.0/rest/reference/search", - "/ja/enterprise/rest/reference/search": "/ja/enterprise-server@latest/rest/reference/search", - "/ja/enterprise-server@3.0/v3/search": "/ja/enterprise-server@3.0/rest/reference/search", - "/ja/enterprise/3.0/v3/search": "/ja/enterprise-server@3.0/rest/reference/search", - "/ja/enterprise/v3/search": "/ja/enterprise-server@latest/rest/reference/search", - "/ja/enterprise/2.20/rest/reference/search": "/ja/enterprise-server@2.20/rest/reference/search", - "/ja/enterprise-server@2.20/v3/search": "/ja/enterprise-server@2.20/rest/reference/search", - "/ja/enterprise/2.20/v3/search": "/ja/enterprise-server@2.20/rest/reference/search", - "/ja/github-ae@latest/v3/search": "/ja/github-ae@latest/rest/reference/search", - "/ja/free-pro-team@latest/rest/reference/secret-scanning": "/ja/rest/reference/secret-scanning", - "/ja/free-pro-team@latest/rest/reference/teams": "/ja/rest/reference/teams", - "/ja/v3/teams": "/ja/rest/reference/teams", - "/ja/free-pro-team@latest/v3/teams": "/ja/rest/reference/teams", - "/ja/enterprise/3.0/rest/reference/teams": "/ja/enterprise-server@3.0/rest/reference/teams", - "/ja/enterprise/rest/reference/teams": "/ja/enterprise-server@latest/rest/reference/teams", - "/ja/enterprise-server@3.0/v3/teams": "/ja/enterprise-server@3.0/rest/reference/teams", - "/ja/enterprise/3.0/v3/teams": "/ja/enterprise-server@3.0/rest/reference/teams", - "/ja/enterprise/v3/teams": "/ja/enterprise-server@latest/rest/reference/teams", - "/ja/enterprise/2.20/rest/reference/teams": "/ja/enterprise-server@2.20/rest/reference/teams", - "/ja/enterprise-server@2.20/v3/teams": "/ja/enterprise-server@2.20/rest/reference/teams", - "/ja/enterprise/2.20/v3/teams": "/ja/enterprise-server@2.20/rest/reference/teams", - "/ja/github-ae@latest/v3/teams": "/ja/github-ae@latest/rest/reference/teams", - "/ja/free-pro-team@latest/rest/reference/users": "/ja/rest/reference/users", - "/ja/v3/users": "/ja/rest/reference/users", - "/ja/free-pro-team@latest/v3/users": "/ja/rest/reference/users", - "/ja/enterprise/3.0/rest/reference/users": "/ja/enterprise-server@3.0/rest/reference/users", - "/ja/enterprise/rest/reference/users": "/ja/enterprise-server@latest/rest/reference/users", - "/ja/enterprise-server@3.0/v3/users": "/ja/enterprise-server@3.0/rest/reference/users", - "/ja/enterprise/3.0/v3/users": "/ja/enterprise-server@3.0/rest/reference/users", - "/ja/enterprise/v3/users": "/ja/enterprise-server@latest/rest/reference/users", - "/ja/enterprise/2.20/rest/reference/users": "/ja/enterprise-server@2.20/rest/reference/users", - "/ja/enterprise-server@2.20/v3/users": "/ja/enterprise-server@2.20/rest/reference/users", - "/ja/enterprise/2.20/v3/users": "/ja/enterprise-server@2.20/rest/reference/users", - "/ja/github-ae@latest/v3/users": "/ja/github-ae@latest/rest/reference/users", - "/es/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/3.0/admin/articles/restoring-github-enterprise": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/admin/articles/restoring-github-enterprise": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/admin/articles/restoring-github-enterprise": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/3.0/admin/articles/restoring-enterprise-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/admin/articles/restoring-enterprise-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/admin/articles/restoring-enterprise-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise-server@3.0/admin/articles/restoring-repository-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/3.0/admin/articles/restoring-repository-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/admin/articles/restoring-repository-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/admin/articles/restoring-repository-data": "/es/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/es/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/2.20/admin/articles/restoring-github-enterprise": "/es/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/es/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/2.20/admin/articles/restoring-enterprise-data": "/es/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise-server@2.20/admin/articles/restoring-repository-data": "/es/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise/2.20/admin/articles/restoring-repository-data": "/es/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/es/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/es/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/es/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/es/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/es/admin/articles/restricting-ssh-access-to-specific-hosts": "/es/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/es/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/es/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/es/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/es/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/es/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/es/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/es/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/es/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/es/admin/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/es/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/es/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/es/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/es/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/es/v3/oauth": "/es/developers/apps/authorizing-oauth-apps", - "/es/free-pro-team@latest/v3/oauth": "/es/developers/apps/authorizing-oauth-apps", - "/es/enterprise-server@3.0/v3/oauth": "/es/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/es/enterprise/3.0/v3/oauth": "/es/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/es/enterprise/v3/oauth": "/es/enterprise-server@latest/developers/apps/authorizing-oauth-apps", - "/es/enterprise-server@2.20/v3/oauth": "/es/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/es/enterprise/2.20/v3/oauth": "/es/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/es/v3/integrations": "/es/developers/apps", - "/es/free-pro-team@latest/v3/integrations": "/es/developers/apps", - "/es/enterprise-server@3.0/v3/integrations": "/es/enterprise-server@3.0/developers/apps", - "/es/enterprise/3.0/v3/integrations": "/es/enterprise-server@3.0/developers/apps", - "/es/enterprise/v3/integrations": "/es/enterprise-server@latest/developers/apps", - "/es/enterprise-server@2.20/v3/integrations": "/es/enterprise-server@2.20/developers/apps", - "/es/enterprise/2.20/v3/integrations": "/es/enterprise-server@2.20/developers/apps", - "/es/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/es/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/es/v3/versions": "/es/developers/overview/about-githubs-apis", - "/es/free-pro-team@latest/v3/versions": "/es/developers/overview/about-githubs-apis", - "/es/enterprise-server@3.0/v3/versions": "/es/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/es/enterprise/3.0/v3/versions": "/es/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/es/enterprise/v3/versions": "/es/enterprise-server@latest/developers/overview/about-githubs-apis", - "/es/enterprise-server@2.20/v3/versions": "/es/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/es/enterprise/2.20/v3/versions": "/es/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/es/v3/guides/managing-deploy-keys": "/es/developers/overview/managing-deploy-keys", - "/es/free-pro-team@latest/v3/guides/managing-deploy-keys": "/es/developers/overview/managing-deploy-keys", - "/es/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/es/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/es/enterprise/3.0/v3/guides/managing-deploy-keys": "/es/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/es/enterprise/v3/guides/managing-deploy-keys": "/es/enterprise-server@latest/developers/overview/managing-deploy-keys", - "/es/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/es/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/es/enterprise/2.20/v3/guides/managing-deploy-keys": "/es/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/es/v3/guides/automating-deployments-to-integrators": "/es/developers/overview/replacing-github-services", - "/es/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/es/developers/overview/replacing-github-services", - "/es/v3/guides/replacing-github-services": "/es/developers/overview/replacing-github-services", - "/es/free-pro-team@latest/v3/guides/replacing-github-services": "/es/developers/overview/replacing-github-services", - "/es/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/es/enterprise-server@3.0/developers/overview/replacing-github-services", - "/es/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/es/enterprise-server@3.0/developers/overview/replacing-github-services", - "/es/enterprise/v3/guides/automating-deployments-to-integrators": "/es/enterprise-server@latest/developers/overview/replacing-github-services", - "/es/enterprise-server@3.0/v3/guides/replacing-github-services": "/es/enterprise-server@3.0/developers/overview/replacing-github-services", - "/es/enterprise/3.0/v3/guides/replacing-github-services": "/es/enterprise-server@3.0/developers/overview/replacing-github-services", - "/es/enterprise/v3/guides/replacing-github-services": "/es/enterprise-server@latest/developers/overview/replacing-github-services", - "/es/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/es/enterprise-server@2.20/developers/overview/replacing-github-services", - "/es/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/es/enterprise-server@2.20/developers/overview/replacing-github-services", - "/es/enterprise-server@2.20/v3/guides/replacing-github-services": "/es/enterprise-server@2.20/developers/overview/replacing-github-services", - "/es/enterprise/2.20/v3/guides/replacing-github-services": "/es/enterprise-server@2.20/developers/overview/replacing-github-services", - "/es/v3/guides/using-ssh-agent-forwarding": "/es/developers/overview/using-ssh-agent-forwarding", - "/es/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/es/developers/overview/using-ssh-agent-forwarding", - "/es/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/es/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/es/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/es/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/es/enterprise/v3/guides/using-ssh-agent-forwarding": "/es/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", - "/es/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/es/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/es/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/es/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/es/v3/activity/event_types": "/es/developers/webhooks-and-events/github-event-types", - "/es/free-pro-team@latest/v3/activity/event_types": "/es/developers/webhooks-and-events/github-event-types", - "/es/enterprise-server@3.0/v3/activity/event_types": "/es/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/es/enterprise/3.0/v3/activity/event_types": "/es/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/es/enterprise/v3/activity/event_types": "/es/enterprise-server@latest/developers/webhooks-and-events/github-event-types", - "/es/enterprise-server@2.20/v3/activity/event_types": "/es/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/es/enterprise/2.20/v3/activity/event_types": "/es/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/es/v3/issues/issue-event-types": "/es/developers/webhooks-and-events/issue-event-types", - "/es/free-pro-team@latest/v3/issues/issue-event-types": "/es/developers/webhooks-and-events/issue-event-types", - "/es/enterprise-server@3.0/v3/issues/issue-event-types": "/es/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/es/enterprise/3.0/v3/issues/issue-event-types": "/es/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/es/enterprise/v3/issues/issue-event-types": "/es/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", - "/es/enterprise-server@2.20/v3/issues/issue-event-types": "/es/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/es/enterprise/2.20/v3/issues/issue-event-types": "/es/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/es/v3/activity/events/types": "/es/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/free-pro-team@latest/v3/activity/events/types": "/es/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/enterprise-server@3.0/v3/activity/events/types": "/es/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/enterprise/3.0/v3/activity/events/types": "/es/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/enterprise/v3/activity/events/types": "/es/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/enterprise-server@2.20/v3/activity/events/types": "/es/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/enterprise/2.20/v3/activity/events/types": "/es/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/es/articles/restoring-branches-in-a-pull-request": "/es/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/es/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/es/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/es/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/articles/restoring-branches-in-a-pull-request": "/es/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/es/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/es/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/es/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/es/github/administering-a-repository/restoring-a-deleted-repository", - "/es/articles/restoring-a-deleted-repository": "/es/github/administering-a-repository/restoring-a-deleted-repository", - "/es/free-pro-team@latest/articles/restoring-a-deleted-repository": "/es/github/administering-a-repository/restoring-a-deleted-repository", - "/es/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/es/articles/restricting-access-to-your-organization-s-data": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/es/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/es/articles/restricting-access-to-your-organizations-data": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/es/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/es/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/es/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/es/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/es/articles/restricting-email-notifications-to-an-approved-domain": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/es/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/es/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/articles/restricting-repository-creation-in-your-organization": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/articles/restricting-repository-creation-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/es/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/articles/restricting-repository-visibility-changes-in-your-organization": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/es/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/es/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/es/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/es/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/es/graphql/guides/forming-calls-with-graphql", - "/es/v4/guides/forming-calls": "/es/graphql/guides/forming-calls-with-graphql", - "/es/free-pro-team@latest/v4/guides/forming-calls": "/es/graphql/guides/forming-calls-with-graphql", - "/es/graphql/guides/forming-calls": "/es/graphql/guides/forming-calls-with-graphql", - "/es/free-pro-team@latest/graphql/guides/forming-calls": "/es/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/es/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/graphql/guides/forming-calls-with-graphql": "/es/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/es/enterprise-server@3.0/v4/guides/forming-calls": "/es/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/3.0/v4/guides/forming-calls": "/es/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/v4/guides/forming-calls": "/es/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/es/enterprise-server@3.0/graphql/guides/forming-calls": "/es/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/3.0/graphql/guides/forming-calls": "/es/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/graphql/guides/forming-calls": "/es/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/es/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/es/enterprise-server@2.20/v4/guides/forming-calls": "/es/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/2.20/v4/guides/forming-calls": "/es/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/es/enterprise-server@2.20/graphql/guides/forming-calls": "/es/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/es/enterprise/2.20/graphql/guides/forming-calls": "/es/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/es/free-pro-team@latest/graphql/guides": "/es/graphql/guides", - "/es/v4/guides": "/es/graphql/guides", - "/es/free-pro-team@latest/v4/guides": "/es/graphql/guides", - "/es/enterprise/3.0/graphql/guides": "/es/enterprise-server@3.0/graphql/guides", - "/es/enterprise/graphql/guides": "/es/enterprise-server@latest/graphql/guides", - "/es/enterprise-server@3.0/v4/guides": "/es/enterprise-server@3.0/graphql/guides", - "/es/enterprise/3.0/v4/guides": "/es/enterprise-server@3.0/graphql/guides", - "/es/enterprise/v4/guides": "/es/enterprise-server@latest/graphql/guides", - "/es/enterprise/2.20/graphql/guides": "/es/enterprise-server@2.20/graphql/guides", - "/es/enterprise-server@2.20/v4/guides": "/es/enterprise-server@2.20/graphql/guides", - "/es/enterprise/2.20/v4/guides": "/es/enterprise-server@2.20/graphql/guides", - "/es/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/es/graphql/guides/introduction-to-graphql", - "/es/v4/guides/intro-to-graphql": "/es/graphql/guides/introduction-to-graphql", - "/es/free-pro-team@latest/v4/guides/intro-to-graphql": "/es/graphql/guides/introduction-to-graphql", - "/es/graphql/guides/intro-to-graphql": "/es/graphql/guides/introduction-to-graphql", - "/es/free-pro-team@latest/graphql/guides/intro-to-graphql": "/es/graphql/guides/introduction-to-graphql", - "/es/enterprise/3.0/graphql/guides/introduction-to-graphql": "/es/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/es/enterprise/graphql/guides/introduction-to-graphql": "/es/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/es/enterprise-server@3.0/v4/guides/intro-to-graphql": "/es/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/es/enterprise/3.0/v4/guides/intro-to-graphql": "/es/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/es/enterprise/v4/guides/intro-to-graphql": "/es/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/es/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/es/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/es/enterprise/3.0/graphql/guides/intro-to-graphql": "/es/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/es/enterprise/graphql/guides/intro-to-graphql": "/es/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/es/enterprise/2.20/graphql/guides/introduction-to-graphql": "/es/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/es/enterprise-server@2.20/v4/guides/intro-to-graphql": "/es/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/es/enterprise/2.20/v4/guides/intro-to-graphql": "/es/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/es/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/es/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/es/enterprise/2.20/graphql/guides/intro-to-graphql": "/es/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/es/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/es/graphql/guides/managing-enterprise-accounts", - "/es/v4/guides/managing-enterprise-accounts": "/es/graphql/guides/managing-enterprise-accounts", - "/es/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/es/graphql/guides/managing-enterprise-accounts", - "/es/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/es/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/es/enterprise/graphql/guides/managing-enterprise-accounts": "/es/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/es/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/es/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/es/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/es/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/es/enterprise/v4/guides/managing-enterprise-accounts": "/es/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/es/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/es/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/es/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/es/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/es/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/es/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/es/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/es/graphql/guides/migrating-from-rest-to-graphql", - "/es/v4/guides/migrating-from-rest": "/es/graphql/guides/migrating-from-rest-to-graphql", - "/es/free-pro-team@latest/v4/guides/migrating-from-rest": "/es/graphql/guides/migrating-from-rest-to-graphql", - "/es/graphql/guides/migrating-from-rest": "/es/graphql/guides/migrating-from-rest-to-graphql", - "/es/free-pro-team@latest/graphql/guides/migrating-from-rest": "/es/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/es/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/es/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise-server@3.0/v4/guides/migrating-from-rest": "/es/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/3.0/v4/guides/migrating-from-rest": "/es/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/v4/guides/migrating-from-rest": "/es/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/es/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/3.0/graphql/guides/migrating-from-rest": "/es/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/graphql/guides/migrating-from-rest": "/es/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/es/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise-server@2.20/v4/guides/migrating-from-rest": "/es/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/2.20/v4/guides/migrating-from-rest": "/es/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/es/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/es/enterprise/2.20/graphql/guides/migrating-from-rest": "/es/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/es/free-pro-team@latest/graphql/guides/using-global-node-ids": "/es/graphql/guides/using-global-node-ids", - "/es/v4/guides/using-global-node-ids": "/es/graphql/guides/using-global-node-ids", - "/es/free-pro-team@latest/v4/guides/using-global-node-ids": "/es/graphql/guides/using-global-node-ids", - "/es/enterprise/3.0/graphql/guides/using-global-node-ids": "/es/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/es/enterprise/graphql/guides/using-global-node-ids": "/es/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/es/enterprise-server@3.0/v4/guides/using-global-node-ids": "/es/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/es/enterprise/3.0/v4/guides/using-global-node-ids": "/es/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/es/enterprise/v4/guides/using-global-node-ids": "/es/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/es/enterprise/2.20/graphql/guides/using-global-node-ids": "/es/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/es/enterprise-server@2.20/v4/guides/using-global-node-ids": "/es/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/es/enterprise/2.20/v4/guides/using-global-node-ids": "/es/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/es/free-pro-team@latest/graphql/guides/using-the-explorer": "/es/graphql/guides/using-the-explorer", - "/es/v4/guides/using-the-explorer": "/es/graphql/guides/using-the-explorer", - "/es/free-pro-team@latest/v4/guides/using-the-explorer": "/es/graphql/guides/using-the-explorer", - "/es/enterprise/3.0/graphql/guides/using-the-explorer": "/es/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/es/enterprise/graphql/guides/using-the-explorer": "/es/enterprise-server@latest/graphql/guides/using-the-explorer", - "/es/enterprise-server@3.0/v4/guides/using-the-explorer": "/es/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/es/enterprise/3.0/v4/guides/using-the-explorer": "/es/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/es/enterprise/v4/guides/using-the-explorer": "/es/enterprise-server@latest/graphql/guides/using-the-explorer", - "/es/enterprise/2.20/graphql/guides/using-the-explorer": "/es/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/es/enterprise-server@2.20/v4/guides/using-the-explorer": "/es/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/es/enterprise/2.20/v4/guides/using-the-explorer": "/es/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/es/free-pro-team@latest/graphql": "/es/graphql", - "/es/v4": "/es/graphql", - "/es/free-pro-team@latest/v4": "/es/graphql", - "/es/enterprise/3.0/graphql": "/es/enterprise-server@3.0/graphql", - "/es/enterprise/graphql": "/es/enterprise-server@latest/graphql", - "/es/enterprise-server@3.0/v4": "/es/enterprise-server@3.0/graphql", - "/es/enterprise/3.0/v4": "/es/enterprise-server@3.0/graphql", - "/es/enterprise/v4": "/es/enterprise-server@latest/graphql", - "/es/enterprise/2.20/graphql": "/es/enterprise-server@2.20/graphql", - "/es/enterprise-server@2.20/v4": "/es/enterprise-server@2.20/graphql", - "/es/enterprise/2.20/v4": "/es/enterprise-server@2.20/graphql", - "/es/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/es/graphql/overview/about-the-graphql-api", - "/es/enterprise/3.0/graphql/overview/about-the-graphql-api": "/es/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/es/enterprise/graphql/overview/about-the-graphql-api": "/es/enterprise-server@latest/graphql/overview/about-the-graphql-api", - "/es/enterprise/2.20/graphql/overview/about-the-graphql-api": "/es/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/es/free-pro-team@latest/graphql/overview/breaking-changes": "/es/graphql/overview/breaking-changes", - "/es/v4/breaking_changes": "/es/graphql/overview/breaking-changes", - "/es/free-pro-team@latest/v4/breaking_changes": "/es/graphql/overview/breaking-changes", - "/es/enterprise/3.0/graphql/overview/breaking-changes": "/es/enterprise-server@3.0/graphql/overview/breaking-changes", - "/es/enterprise/graphql/overview/breaking-changes": "/es/enterprise-server@latest/graphql/overview/breaking-changes", - "/es/enterprise-server@3.0/v4/breaking_changes": "/es/enterprise-server@3.0/graphql/overview/breaking-changes", - "/es/enterprise/3.0/v4/breaking_changes": "/es/enterprise-server@3.0/graphql/overview/breaking-changes", - "/es/enterprise/v4/breaking_changes": "/es/enterprise-server@latest/graphql/overview/breaking-changes", - "/es/enterprise/2.20/graphql/overview/breaking-changes": "/es/enterprise-server@2.20/graphql/overview/breaking-changes", - "/es/enterprise-server@2.20/v4/breaking_changes": "/es/enterprise-server@2.20/graphql/overview/breaking-changes", - "/es/enterprise/2.20/v4/breaking_changes": "/es/enterprise-server@2.20/graphql/overview/breaking-changes", - "/es/free-pro-team@latest/graphql/overview/changelog": "/es/graphql/overview/changelog", - "/es/v4/changelog": "/es/graphql/overview/changelog", - "/es/free-pro-team@latest/v4/changelog": "/es/graphql/overview/changelog", - "/es/enterprise/3.0/graphql/overview/changelog": "/es/enterprise-server@3.0/graphql/overview/changelog", - "/es/enterprise/graphql/overview/changelog": "/es/enterprise-server@latest/graphql/overview/changelog", - "/es/enterprise-server@3.0/v4/changelog": "/es/enterprise-server@3.0/graphql/overview/changelog", - "/es/enterprise/3.0/v4/changelog": "/es/enterprise-server@3.0/graphql/overview/changelog", - "/es/enterprise/v4/changelog": "/es/enterprise-server@latest/graphql/overview/changelog", - "/es/enterprise/2.20/graphql/overview/changelog": "/es/enterprise-server@2.20/graphql/overview/changelog", - "/es/enterprise-server@2.20/v4/changelog": "/es/enterprise-server@2.20/graphql/overview/changelog", - "/es/enterprise/2.20/v4/changelog": "/es/enterprise-server@2.20/graphql/overview/changelog", - "/es/free-pro-team@latest/graphql/overview/explorer": "/es/graphql/overview/explorer", - "/es/v4/explorer": "/es/graphql/overview/explorer", - "/es/free-pro-team@latest/v4/explorer": "/es/graphql/overview/explorer", - "/es/v4/explorer-new": "/es/graphql/overview/explorer", - "/es/free-pro-team@latest/v4/explorer-new": "/es/graphql/overview/explorer", - "/es/enterprise/3.0/graphql/overview/explorer": "/es/enterprise-server@3.0/graphql/overview/explorer", - "/es/enterprise/graphql/overview/explorer": "/es/enterprise-server@latest/graphql/overview/explorer", - "/es/enterprise-server@3.0/v4/explorer": "/es/enterprise-server@3.0/graphql/overview/explorer", - "/es/enterprise/3.0/v4/explorer": "/es/enterprise-server@3.0/graphql/overview/explorer", - "/es/enterprise/v4/explorer": "/es/enterprise-server@latest/graphql/overview/explorer", - "/es/enterprise-server@3.0/v4/explorer-new": "/es/enterprise-server@3.0/graphql/overview/explorer", - "/es/enterprise/3.0/v4/explorer-new": "/es/enterprise-server@3.0/graphql/overview/explorer", - "/es/enterprise/v4/explorer-new": "/es/enterprise-server@latest/graphql/overview/explorer", - "/es/enterprise/2.20/graphql/overview/explorer": "/es/enterprise-server@2.20/graphql/overview/explorer", - "/es/enterprise-server@2.20/v4/explorer": "/es/enterprise-server@2.20/graphql/overview/explorer", - "/es/enterprise/2.20/v4/explorer": "/es/enterprise-server@2.20/graphql/overview/explorer", - "/es/enterprise-server@2.20/v4/explorer-new": "/es/enterprise-server@2.20/graphql/overview/explorer", - "/es/enterprise/2.20/v4/explorer-new": "/es/enterprise-server@2.20/graphql/overview/explorer", - "/es/free-pro-team@latest/graphql/overview": "/es/graphql/overview", - "/es/enterprise/3.0/graphql/overview": "/es/enterprise-server@3.0/graphql/overview", - "/es/enterprise/graphql/overview": "/es/enterprise-server@latest/graphql/overview", - "/es/enterprise/2.20/graphql/overview": "/es/enterprise-server@2.20/graphql/overview", - "/es/free-pro-team@latest/graphql/overview/public-schema": "/es/graphql/overview/public-schema", - "/es/v4/public_schema": "/es/graphql/overview/public-schema", - "/es/free-pro-team@latest/v4/public_schema": "/es/graphql/overview/public-schema", - "/es/enterprise/3.0/graphql/overview/public-schema": "/es/enterprise-server@3.0/graphql/overview/public-schema", - "/es/enterprise/graphql/overview/public-schema": "/es/enterprise-server@latest/graphql/overview/public-schema", - "/es/enterprise-server@3.0/v4/public_schema": "/es/enterprise-server@3.0/graphql/overview/public-schema", - "/es/enterprise/3.0/v4/public_schema": "/es/enterprise-server@3.0/graphql/overview/public-schema", - "/es/enterprise/v4/public_schema": "/es/enterprise-server@latest/graphql/overview/public-schema", - "/es/enterprise/2.20/graphql/overview/public-schema": "/es/enterprise-server@2.20/graphql/overview/public-schema", - "/es/enterprise-server@2.20/v4/public_schema": "/es/enterprise-server@2.20/graphql/overview/public-schema", - "/es/enterprise/2.20/v4/public_schema": "/es/enterprise-server@2.20/graphql/overview/public-schema", - "/es/free-pro-team@latest/graphql/overview/resource-limitations": "/es/graphql/overview/resource-limitations", - "/es/v4/guides/resource-limitations": "/es/graphql/overview/resource-limitations", - "/es/free-pro-team@latest/v4/guides/resource-limitations": "/es/graphql/overview/resource-limitations", - "/es/enterprise/3.0/graphql/overview/resource-limitations": "/es/enterprise-server@3.0/graphql/overview/resource-limitations", - "/es/enterprise/graphql/overview/resource-limitations": "/es/enterprise-server@latest/graphql/overview/resource-limitations", - "/es/enterprise-server@3.0/v4/guides/resource-limitations": "/es/enterprise-server@3.0/graphql/overview/resource-limitations", - "/es/enterprise/3.0/v4/guides/resource-limitations": "/es/enterprise-server@3.0/graphql/overview/resource-limitations", - "/es/enterprise/v4/guides/resource-limitations": "/es/enterprise-server@latest/graphql/overview/resource-limitations", - "/es/enterprise/2.20/graphql/overview/resource-limitations": "/es/enterprise-server@2.20/graphql/overview/resource-limitations", - "/es/enterprise-server@2.20/v4/guides/resource-limitations": "/es/enterprise-server@2.20/graphql/overview/resource-limitations", - "/es/enterprise/2.20/v4/guides/resource-limitations": "/es/enterprise-server@2.20/graphql/overview/resource-limitations", - "/es/free-pro-team@latest/graphql/overview/schema-previews": "/es/graphql/overview/schema-previews", - "/es/v4/previews": "/es/graphql/overview/schema-previews", - "/es/free-pro-team@latest/v4/previews": "/es/graphql/overview/schema-previews", - "/es/enterprise/3.0/graphql/overview/schema-previews": "/es/enterprise-server@3.0/graphql/overview/schema-previews", - "/es/enterprise/graphql/overview/schema-previews": "/es/enterprise-server@latest/graphql/overview/schema-previews", - "/es/enterprise-server@3.0/v4/previews": "/es/enterprise-server@3.0/graphql/overview/schema-previews", - "/es/enterprise/3.0/v4/previews": "/es/enterprise-server@3.0/graphql/overview/schema-previews", - "/es/enterprise/v4/previews": "/es/enterprise-server@latest/graphql/overview/schema-previews", - "/es/enterprise/2.20/graphql/overview/schema-previews": "/es/enterprise-server@2.20/graphql/overview/schema-previews", - "/es/enterprise-server@2.20/v4/previews": "/es/enterprise-server@2.20/graphql/overview/schema-previews", - "/es/enterprise/2.20/v4/previews": "/es/enterprise-server@2.20/graphql/overview/schema-previews", - "/es/free-pro-team@latest/graphql/reference/enums": "/es/graphql/reference/enums", - "/es/v4/enum": "/es/graphql/reference/enums", - "/es/free-pro-team@latest/v4/enum": "/es/graphql/reference/enums", - "/es/enterprise/3.0/graphql/reference/enums": "/es/enterprise-server@3.0/graphql/reference/enums", - "/es/enterprise/graphql/reference/enums": "/es/enterprise-server@latest/graphql/reference/enums", - "/es/enterprise-server@3.0/v4/enum": "/es/enterprise-server@3.0/graphql/reference/enums", - "/es/enterprise/3.0/v4/enum": "/es/enterprise-server@3.0/graphql/reference/enums", - "/es/enterprise/v4/enum": "/es/enterprise-server@latest/graphql/reference/enums", - "/es/enterprise/2.20/graphql/reference/enums": "/es/enterprise-server@2.20/graphql/reference/enums", - "/es/enterprise-server@2.20/v4/enum": "/es/enterprise-server@2.20/graphql/reference/enums", - "/es/enterprise/2.20/v4/enum": "/es/enterprise-server@2.20/graphql/reference/enums", - "/es/free-pro-team@latest/graphql/reference": "/es/graphql/reference", - "/es/v4/reference": "/es/graphql/reference", - "/es/free-pro-team@latest/v4/reference": "/es/graphql/reference", - "/es/enterprise/3.0/graphql/reference": "/es/enterprise-server@3.0/graphql/reference", - "/es/enterprise/graphql/reference": "/es/enterprise-server@latest/graphql/reference", - "/es/enterprise-server@3.0/v4/reference": "/es/enterprise-server@3.0/graphql/reference", - "/es/enterprise/3.0/v4/reference": "/es/enterprise-server@3.0/graphql/reference", - "/es/enterprise/v4/reference": "/es/enterprise-server@latest/graphql/reference", - "/es/enterprise/2.20/graphql/reference": "/es/enterprise-server@2.20/graphql/reference", - "/es/enterprise-server@2.20/v4/reference": "/es/enterprise-server@2.20/graphql/reference", - "/es/enterprise/2.20/v4/reference": "/es/enterprise-server@2.20/graphql/reference", - "/es/free-pro-team@latest/graphql/reference/input-objects": "/es/graphql/reference/input-objects", - "/es/v4/input_object": "/es/graphql/reference/input-objects", - "/es/free-pro-team@latest/v4/input_object": "/es/graphql/reference/input-objects", - "/es/enterprise/3.0/graphql/reference/input-objects": "/es/enterprise-server@3.0/graphql/reference/input-objects", - "/es/enterprise/graphql/reference/input-objects": "/es/enterprise-server@latest/graphql/reference/input-objects", - "/es/enterprise-server@3.0/v4/input_object": "/es/enterprise-server@3.0/graphql/reference/input-objects", - "/es/enterprise/3.0/v4/input_object": "/es/enterprise-server@3.0/graphql/reference/input-objects", - "/es/enterprise/v4/input_object": "/es/enterprise-server@latest/graphql/reference/input-objects", - "/es/enterprise/2.20/graphql/reference/input-objects": "/es/enterprise-server@2.20/graphql/reference/input-objects", - "/es/enterprise-server@2.20/v4/input_object": "/es/enterprise-server@2.20/graphql/reference/input-objects", - "/es/enterprise/2.20/v4/input_object": "/es/enterprise-server@2.20/graphql/reference/input-objects", - "/es/free-pro-team@latest/graphql/reference/interfaces": "/es/graphql/reference/interfaces", - "/es/v4/interface": "/es/graphql/reference/interfaces", - "/es/free-pro-team@latest/v4/interface": "/es/graphql/reference/interfaces", - "/es/enterprise/3.0/graphql/reference/interfaces": "/es/enterprise-server@3.0/graphql/reference/interfaces", - "/es/enterprise/graphql/reference/interfaces": "/es/enterprise-server@latest/graphql/reference/interfaces", - "/es/enterprise-server@3.0/v4/interface": "/es/enterprise-server@3.0/graphql/reference/interfaces", - "/es/enterprise/3.0/v4/interface": "/es/enterprise-server@3.0/graphql/reference/interfaces", - "/es/enterprise/v4/interface": "/es/enterprise-server@latest/graphql/reference/interfaces", - "/es/enterprise/2.20/graphql/reference/interfaces": "/es/enterprise-server@2.20/graphql/reference/interfaces", - "/es/enterprise-server@2.20/v4/interface": "/es/enterprise-server@2.20/graphql/reference/interfaces", - "/es/enterprise/2.20/v4/interface": "/es/enterprise-server@2.20/graphql/reference/interfaces", - "/es/free-pro-team@latest/graphql/reference/mutations": "/es/graphql/reference/mutations", - "/es/v4/mutation": "/es/graphql/reference/mutations", - "/es/free-pro-team@latest/v4/mutation": "/es/graphql/reference/mutations", - "/es/enterprise/3.0/graphql/reference/mutations": "/es/enterprise-server@3.0/graphql/reference/mutations", - "/es/enterprise/graphql/reference/mutations": "/es/enterprise-server@latest/graphql/reference/mutations", - "/es/enterprise-server@3.0/v4/mutation": "/es/enterprise-server@3.0/graphql/reference/mutations", - "/es/enterprise/3.0/v4/mutation": "/es/enterprise-server@3.0/graphql/reference/mutations", - "/es/enterprise/v4/mutation": "/es/enterprise-server@latest/graphql/reference/mutations", - "/es/enterprise/2.20/graphql/reference/mutations": "/es/enterprise-server@2.20/graphql/reference/mutations", - "/es/enterprise-server@2.20/v4/mutation": "/es/enterprise-server@2.20/graphql/reference/mutations", - "/es/enterprise/2.20/v4/mutation": "/es/enterprise-server@2.20/graphql/reference/mutations", - "/es/free-pro-team@latest/graphql/reference/objects": "/es/graphql/reference/objects", - "/es/v4/object": "/es/graphql/reference/objects", - "/es/free-pro-team@latest/v4/object": "/es/graphql/reference/objects", - "/es/enterprise/3.0/graphql/reference/objects": "/es/enterprise-server@3.0/graphql/reference/objects", - "/es/enterprise/graphql/reference/objects": "/es/enterprise-server@latest/graphql/reference/objects", - "/es/enterprise-server@3.0/v4/object": "/es/enterprise-server@3.0/graphql/reference/objects", - "/es/enterprise/3.0/v4/object": "/es/enterprise-server@3.0/graphql/reference/objects", - "/es/enterprise/v4/object": "/es/enterprise-server@latest/graphql/reference/objects", - "/es/enterprise/2.20/graphql/reference/objects": "/es/enterprise-server@2.20/graphql/reference/objects", - "/es/enterprise-server@2.20/v4/object": "/es/enterprise-server@2.20/graphql/reference/objects", - "/es/enterprise/2.20/v4/object": "/es/enterprise-server@2.20/graphql/reference/objects", - "/es/free-pro-team@latest/graphql/reference/queries": "/es/graphql/reference/queries", - "/es/v4/query": "/es/graphql/reference/queries", - "/es/free-pro-team@latest/v4/query": "/es/graphql/reference/queries", - "/es/enterprise/3.0/graphql/reference/queries": "/es/enterprise-server@3.0/graphql/reference/queries", - "/es/enterprise/graphql/reference/queries": "/es/enterprise-server@latest/graphql/reference/queries", - "/es/enterprise-server@3.0/v4/query": "/es/enterprise-server@3.0/graphql/reference/queries", - "/es/enterprise/3.0/v4/query": "/es/enterprise-server@3.0/graphql/reference/queries", - "/es/enterprise/v4/query": "/es/enterprise-server@latest/graphql/reference/queries", - "/es/enterprise/2.20/graphql/reference/queries": "/es/enterprise-server@2.20/graphql/reference/queries", - "/es/enterprise-server@2.20/v4/query": "/es/enterprise-server@2.20/graphql/reference/queries", - "/es/enterprise/2.20/v4/query": "/es/enterprise-server@2.20/graphql/reference/queries", - "/es/free-pro-team@latest/graphql/reference/scalars": "/es/graphql/reference/scalars", - "/es/v4/scalar": "/es/graphql/reference/scalars", - "/es/free-pro-team@latest/v4/scalar": "/es/graphql/reference/scalars", - "/es/enterprise/3.0/graphql/reference/scalars": "/es/enterprise-server@3.0/graphql/reference/scalars", - "/es/enterprise/graphql/reference/scalars": "/es/enterprise-server@latest/graphql/reference/scalars", - "/es/enterprise-server@3.0/v4/scalar": "/es/enterprise-server@3.0/graphql/reference/scalars", - "/es/enterprise/3.0/v4/scalar": "/es/enterprise-server@3.0/graphql/reference/scalars", - "/es/enterprise/v4/scalar": "/es/enterprise-server@latest/graphql/reference/scalars", - "/es/enterprise/2.20/graphql/reference/scalars": "/es/enterprise-server@2.20/graphql/reference/scalars", - "/es/enterprise-server@2.20/v4/scalar": "/es/enterprise-server@2.20/graphql/reference/scalars", - "/es/enterprise/2.20/v4/scalar": "/es/enterprise-server@2.20/graphql/reference/scalars", - "/es/free-pro-team@latest/graphql/reference/unions": "/es/graphql/reference/unions", - "/es/v4/union": "/es/graphql/reference/unions", - "/es/free-pro-team@latest/v4/union": "/es/graphql/reference/unions", - "/es/enterprise/3.0/graphql/reference/unions": "/es/enterprise-server@3.0/graphql/reference/unions", - "/es/enterprise/graphql/reference/unions": "/es/enterprise-server@latest/graphql/reference/unions", - "/es/enterprise-server@3.0/v4/union": "/es/enterprise-server@3.0/graphql/reference/unions", - "/es/enterprise/3.0/v4/union": "/es/enterprise-server@3.0/graphql/reference/unions", - "/es/enterprise/v4/union": "/es/enterprise-server@latest/graphql/reference/unions", - "/es/enterprise/2.20/graphql/reference/unions": "/es/enterprise-server@2.20/graphql/reference/unions", - "/es/enterprise-server@2.20/v4/union": "/es/enterprise-server@2.20/graphql/reference/unions", - "/es/enterprise/2.20/v4/union": "/es/enterprise-server@2.20/graphql/reference/unions", - "/es/free-pro-team@latest/rest/guides/basics-of-authentication": "/es/rest/guides/basics-of-authentication", - "/es/v3/guides/basics-of-authentication": "/es/rest/guides/basics-of-authentication", - "/es/free-pro-team@latest/v3/guides/basics-of-authentication": "/es/rest/guides/basics-of-authentication", - "/es/rest/basics-of-authentication": "/es/rest/guides/basics-of-authentication", - "/es/free-pro-team@latest/rest/basics-of-authentication": "/es/rest/guides/basics-of-authentication", - "/es/enterprise/3.0/rest/guides/basics-of-authentication": "/es/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/es/enterprise/rest/guides/basics-of-authentication": "/es/enterprise-server@latest/rest/guides/basics-of-authentication", - "/es/enterprise-server@3.0/v3/guides/basics-of-authentication": "/es/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/es/enterprise/3.0/v3/guides/basics-of-authentication": "/es/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/es/enterprise/v3/guides/basics-of-authentication": "/es/enterprise-server@latest/rest/guides/basics-of-authentication", - "/es/enterprise-server@3.0/rest/basics-of-authentication": "/es/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/es/enterprise/3.0/rest/basics-of-authentication": "/es/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/es/enterprise/rest/basics-of-authentication": "/es/enterprise-server@latest/rest/guides/basics-of-authentication", - "/es/enterprise/2.20/rest/guides/basics-of-authentication": "/es/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/es/enterprise-server@2.20/v3/guides/basics-of-authentication": "/es/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/es/enterprise/2.20/v3/guides/basics-of-authentication": "/es/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/es/enterprise-server@2.20/rest/basics-of-authentication": "/es/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/es/enterprise/2.20/rest/basics-of-authentication": "/es/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/es/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/es/rest/guides/best-practices-for-integrators", - "/es/v3/guides/best-practices-for-integrators": "/es/rest/guides/best-practices-for-integrators", - "/es/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/es/rest/guides/best-practices-for-integrators", - "/es/enterprise/3.0/rest/guides/best-practices-for-integrators": "/es/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/es/enterprise/rest/guides/best-practices-for-integrators": "/es/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/es/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/es/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/es/enterprise/3.0/v3/guides/best-practices-for-integrators": "/es/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/es/enterprise/v3/guides/best-practices-for-integrators": "/es/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/es/enterprise/2.20/rest/guides/best-practices-for-integrators": "/es/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/es/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/es/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/es/enterprise/2.20/v3/guides/best-practices-for-integrators": "/es/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/es/free-pro-team@latest/rest/guides/building-a-ci-server": "/es/rest/guides/building-a-ci-server", - "/es/v3/guides/building-a-ci-server": "/es/rest/guides/building-a-ci-server", - "/es/free-pro-team@latest/v3/guides/building-a-ci-server": "/es/rest/guides/building-a-ci-server", - "/es/enterprise/3.0/rest/guides/building-a-ci-server": "/es/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/es/enterprise/rest/guides/building-a-ci-server": "/es/enterprise-server@latest/rest/guides/building-a-ci-server", - "/es/enterprise-server@3.0/v3/guides/building-a-ci-server": "/es/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/es/enterprise/3.0/v3/guides/building-a-ci-server": "/es/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/es/enterprise/v3/guides/building-a-ci-server": "/es/enterprise-server@latest/rest/guides/building-a-ci-server", - "/es/enterprise/2.20/rest/guides/building-a-ci-server": "/es/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/es/enterprise-server@2.20/v3/guides/building-a-ci-server": "/es/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/es/enterprise/2.20/v3/guides/building-a-ci-server": "/es/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/es/free-pro-team@latest/rest/guides/delivering-deployments": "/es/rest/guides/delivering-deployments", - "/es/v3/guides/delivering-deployments": "/es/rest/guides/delivering-deployments", - "/es/free-pro-team@latest/v3/guides/delivering-deployments": "/es/rest/guides/delivering-deployments", - "/es/enterprise/3.0/rest/guides/delivering-deployments": "/es/enterprise-server@3.0/rest/guides/delivering-deployments", - "/es/enterprise/rest/guides/delivering-deployments": "/es/enterprise-server@latest/rest/guides/delivering-deployments", - "/es/enterprise-server@3.0/v3/guides/delivering-deployments": "/es/enterprise-server@3.0/rest/guides/delivering-deployments", - "/es/enterprise/3.0/v3/guides/delivering-deployments": "/es/enterprise-server@3.0/rest/guides/delivering-deployments", - "/es/enterprise/v3/guides/delivering-deployments": "/es/enterprise-server@latest/rest/guides/delivering-deployments", - "/es/enterprise/2.20/rest/guides/delivering-deployments": "/es/enterprise-server@2.20/rest/guides/delivering-deployments", - "/es/enterprise-server@2.20/v3/guides/delivering-deployments": "/es/enterprise-server@2.20/rest/guides/delivering-deployments", - "/es/enterprise/2.20/v3/guides/delivering-deployments": "/es/enterprise-server@2.20/rest/guides/delivering-deployments", - "/es/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/es/rest/guides/discovering-resources-for-a-user", - "/es/v3/guides/discovering-resources-for-a-user": "/es/rest/guides/discovering-resources-for-a-user", - "/es/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/es/rest/guides/discovering-resources-for-a-user", - "/es/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/es/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/es/enterprise/rest/guides/discovering-resources-for-a-user": "/es/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/es/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/es/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/es/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/es/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/es/enterprise/v3/guides/discovering-resources-for-a-user": "/es/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/es/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/es/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/es/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/es/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/es/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/es/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/es/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/es/rest/guides/getting-started-with-the-checks-api", - "/es/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/es/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/es/enterprise/rest/guides/getting-started-with-the-checks-api": "/es/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", - "/es/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/es/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/es/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/es/rest/guides/getting-started-with-the-git-database-api", - "/es/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/es/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/es/enterprise/rest/guides/getting-started-with-the-git-database-api": "/es/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", - "/es/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/es/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/es/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/es/rest/guides/getting-started-with-the-rest-api", - "/es/v3/guides/getting-started": "/es/rest/guides/getting-started-with-the-rest-api", - "/es/free-pro-team@latest/v3/guides/getting-started": "/es/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/es/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise/rest/guides/getting-started-with-the-rest-api": "/es/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise-server@3.0/v3/guides/getting-started": "/es/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise/3.0/v3/guides/getting-started": "/es/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise/v3/guides/getting-started": "/es/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/es/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise-server@2.20/v3/guides/getting-started": "/es/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/es/enterprise/2.20/v3/guides/getting-started": "/es/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/es/free-pro-team@latest/rest/guides": "/es/rest/guides", - "/es/v3/guides": "/es/rest/guides", - "/es/free-pro-team@latest/v3/guides": "/es/rest/guides", - "/es/enterprise/3.0/rest/guides": "/es/enterprise-server@3.0/rest/guides", - "/es/enterprise/rest/guides": "/es/enterprise-server@latest/rest/guides", - "/es/enterprise-server@3.0/v3/guides": "/es/enterprise-server@3.0/rest/guides", - "/es/enterprise/3.0/v3/guides": "/es/enterprise-server@3.0/rest/guides", - "/es/enterprise/v3/guides": "/es/enterprise-server@latest/rest/guides", - "/es/enterprise/2.20/rest/guides": "/es/enterprise-server@2.20/rest/guides", - "/es/enterprise-server@2.20/v3/guides": "/es/enterprise-server@2.20/rest/guides", - "/es/enterprise/2.20/v3/guides": "/es/enterprise-server@2.20/rest/guides", - "/es/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/es/rest/guides/rendering-data-as-graphs", - "/es/v3/guides/rendering-data-as-graphs": "/es/rest/guides/rendering-data-as-graphs", - "/es/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/es/rest/guides/rendering-data-as-graphs", - "/es/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/es/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/es/enterprise/rest/guides/rendering-data-as-graphs": "/es/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/es/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/es/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/es/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/es/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/es/enterprise/v3/guides/rendering-data-as-graphs": "/es/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/es/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/es/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/es/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/es/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/es/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/es/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/es/free-pro-team@latest/rest/guides/traversing-with-pagination": "/es/rest/guides/traversing-with-pagination", - "/es/v3/guides/traversing-with-pagination": "/es/rest/guides/traversing-with-pagination", - "/es/free-pro-team@latest/v3/guides/traversing-with-pagination": "/es/rest/guides/traversing-with-pagination", - "/es/enterprise/3.0/rest/guides/traversing-with-pagination": "/es/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/es/enterprise/rest/guides/traversing-with-pagination": "/es/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/es/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/es/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/es/enterprise/3.0/v3/guides/traversing-with-pagination": "/es/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/es/enterprise/v3/guides/traversing-with-pagination": "/es/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/es/enterprise/2.20/rest/guides/traversing-with-pagination": "/es/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/es/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/es/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/es/enterprise/2.20/v3/guides/traversing-with-pagination": "/es/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/es/free-pro-team@latest/rest/guides/working-with-comments": "/es/rest/guides/working-with-comments", - "/es/v3/guides/working-with-comments": "/es/rest/guides/working-with-comments", - "/es/free-pro-team@latest/v3/guides/working-with-comments": "/es/rest/guides/working-with-comments", - "/es/enterprise/3.0/rest/guides/working-with-comments": "/es/enterprise-server@3.0/rest/guides/working-with-comments", - "/es/enterprise/rest/guides/working-with-comments": "/es/enterprise-server@latest/rest/guides/working-with-comments", - "/es/enterprise-server@3.0/v3/guides/working-with-comments": "/es/enterprise-server@3.0/rest/guides/working-with-comments", - "/es/enterprise/3.0/v3/guides/working-with-comments": "/es/enterprise-server@3.0/rest/guides/working-with-comments", - "/es/enterprise/v3/guides/working-with-comments": "/es/enterprise-server@latest/rest/guides/working-with-comments", - "/es/enterprise/2.20/rest/guides/working-with-comments": "/es/enterprise-server@2.20/rest/guides/working-with-comments", - "/es/enterprise-server@2.20/v3/guides/working-with-comments": "/es/enterprise-server@2.20/rest/guides/working-with-comments", - "/es/enterprise/2.20/v3/guides/working-with-comments": "/es/enterprise-server@2.20/rest/guides/working-with-comments", - "/es/free-pro-team@latest/rest": "/es/rest", - "/es/v3": "/es/rest", - "/es/free-pro-team@latest/v3": "/es/rest", - "/es/enterprise/3.0/rest": "/es/enterprise-server@3.0/rest", - "/es/enterprise/rest": "/es/enterprise-server@latest/rest", - "/es/enterprise-server@3.0/v3": "/es/enterprise-server@3.0/rest", - "/es/enterprise/3.0/v3": "/es/enterprise-server@3.0/rest", - "/es/enterprise/v3": "/es/enterprise-server@latest/rest", - "/es/enterprise/2.20/rest": "/es/enterprise-server@2.20/rest", - "/es/enterprise-server@2.20/v3": "/es/enterprise-server@2.20/rest", - "/es/enterprise/2.20/v3": "/es/enterprise-server@2.20/rest", - "/es/free-pro-team@latest/rest/overview/api-previews": "/es/rest/overview/api-previews", - "/es/v3/previews": "/es/rest/overview/api-previews", - "/es/free-pro-team@latest/v3/previews": "/es/rest/overview/api-previews", - "/es/enterprise/3.0/rest/overview/api-previews": "/es/enterprise-server@3.0/rest/overview/api-previews", - "/es/enterprise/rest/overview/api-previews": "/es/enterprise-server@latest/rest/overview/api-previews", - "/es/enterprise-server@3.0/v3/previews": "/es/enterprise-server@3.0/rest/overview/api-previews", - "/es/enterprise/3.0/v3/previews": "/es/enterprise-server@3.0/rest/overview/api-previews", - "/es/enterprise/v3/previews": "/es/enterprise-server@latest/rest/overview/api-previews", - "/es/enterprise/2.20/rest/overview/api-previews": "/es/enterprise-server@2.20/rest/overview/api-previews", - "/es/enterprise-server@2.20/v3/previews": "/es/enterprise-server@2.20/rest/overview/api-previews", - "/es/enterprise/2.20/v3/previews": "/es/enterprise-server@2.20/rest/overview/api-previews", - "/es/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/es/rest/overview/endpoints-available-for-github-apps", - "/es/v3/apps/available-endpoints": "/es/rest/overview/endpoints-available-for-github-apps", - "/es/free-pro-team@latest/v3/apps/available-endpoints": "/es/rest/overview/endpoints-available-for-github-apps", - "/es/rest/reference/endpoints-available-for-github-apps": "/es/rest/overview/endpoints-available-for-github-apps", - "/es/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/es/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/es/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/rest/overview/endpoints-available-for-github-apps": "/es/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise-server@3.0/v3/apps/available-endpoints": "/es/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/3.0/v3/apps/available-endpoints": "/es/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/v3/apps/available-endpoints": "/es/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/es/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/es/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/rest/reference/endpoints-available-for-github-apps": "/es/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/es/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise-server@2.20/v3/apps/available-endpoints": "/es/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/2.20/v3/apps/available-endpoints": "/es/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/es/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/es/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/es/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/es/free-pro-team@latest/rest/overview": "/es/rest/overview", - "/es/enterprise/3.0/rest/overview": "/es/enterprise-server@3.0/rest/overview", - "/es/enterprise/rest/overview": "/es/enterprise-server@latest/rest/overview", - "/es/enterprise/2.20/rest/overview": "/es/enterprise-server@2.20/rest/overview", - "/es/free-pro-team@latest/rest/overview/libraries": "/es/rest/overview/libraries", - "/es/v3/libraries": "/es/rest/overview/libraries", - "/es/free-pro-team@latest/v3/libraries": "/es/rest/overview/libraries", - "/es/enterprise/3.0/rest/overview/libraries": "/es/enterprise-server@3.0/rest/overview/libraries", - "/es/enterprise/rest/overview/libraries": "/es/enterprise-server@latest/rest/overview/libraries", - "/es/enterprise-server@3.0/v3/libraries": "/es/enterprise-server@3.0/rest/overview/libraries", - "/es/enterprise/3.0/v3/libraries": "/es/enterprise-server@3.0/rest/overview/libraries", - "/es/enterprise/v3/libraries": "/es/enterprise-server@latest/rest/overview/libraries", - "/es/enterprise/2.20/rest/overview/libraries": "/es/enterprise-server@2.20/rest/overview/libraries", - "/es/enterprise-server@2.20/v3/libraries": "/es/enterprise-server@2.20/rest/overview/libraries", - "/es/enterprise/2.20/v3/libraries": "/es/enterprise-server@2.20/rest/overview/libraries", - "/es/free-pro-team@latest/rest/overview/media-types": "/es/rest/overview/media-types", - "/es/v3/media": "/es/rest/overview/media-types", - "/es/free-pro-team@latest/v3/media": "/es/rest/overview/media-types", - "/es/enterprise/3.0/rest/overview/media-types": "/es/enterprise-server@3.0/rest/overview/media-types", - "/es/enterprise/rest/overview/media-types": "/es/enterprise-server@latest/rest/overview/media-types", - "/es/enterprise-server@3.0/v3/media": "/es/enterprise-server@3.0/rest/overview/media-types", - "/es/enterprise/3.0/v3/media": "/es/enterprise-server@3.0/rest/overview/media-types", - "/es/enterprise/v3/media": "/es/enterprise-server@latest/rest/overview/media-types", - "/es/enterprise/2.20/rest/overview/media-types": "/es/enterprise-server@2.20/rest/overview/media-types", - "/es/enterprise-server@2.20/v3/media": "/es/enterprise-server@2.20/rest/overview/media-types", - "/es/enterprise/2.20/v3/media": "/es/enterprise-server@2.20/rest/overview/media-types", - "/es/free-pro-team@latest/rest/overview/other-authentication-methods": "/es/rest/overview/other-authentication-methods", - "/es/v3/auth": "/es/rest/overview/other-authentication-methods", - "/es/free-pro-team@latest/v3/auth": "/es/rest/overview/other-authentication-methods", - "/es/enterprise/3.0/rest/overview/other-authentication-methods": "/es/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/es/enterprise/rest/overview/other-authentication-methods": "/es/enterprise-server@latest/rest/overview/other-authentication-methods", - "/es/enterprise-server@3.0/v3/auth": "/es/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/es/enterprise/3.0/v3/auth": "/es/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/es/enterprise/v3/auth": "/es/enterprise-server@latest/rest/overview/other-authentication-methods", - "/es/enterprise/2.20/rest/overview/other-authentication-methods": "/es/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/es/enterprise-server@2.20/v3/auth": "/es/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/es/enterprise/2.20/v3/auth": "/es/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/es/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/es/rest/overview/resources-in-the-rest-api", - "/es/rest/initialize-the-repo": "/es/rest/overview/resources-in-the-rest-api", - "/es/free-pro-team@latest/rest/initialize-the-repo": "/es/rest/overview/resources-in-the-rest-api", - "/es/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/es/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/es/enterprise/rest/overview/resources-in-the-rest-api": "/es/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/es/enterprise-server@3.0/rest/initialize-the-repo": "/es/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/es/enterprise/3.0/rest/initialize-the-repo": "/es/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/es/enterprise/rest/initialize-the-repo": "/es/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/es/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/es/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/es/enterprise-server@2.20/rest/initialize-the-repo": "/es/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/es/enterprise/2.20/rest/initialize-the-repo": "/es/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/es/free-pro-team@latest/rest/overview/troubleshooting": "/es/rest/overview/troubleshooting", - "/es/v3/troubleshooting": "/es/rest/overview/troubleshooting", - "/es/free-pro-team@latest/v3/troubleshooting": "/es/rest/overview/troubleshooting", - "/es/enterprise/3.0/rest/overview/troubleshooting": "/es/enterprise-server@3.0/rest/overview/troubleshooting", - "/es/enterprise/rest/overview/troubleshooting": "/es/enterprise-server@latest/rest/overview/troubleshooting", - "/es/enterprise-server@3.0/v3/troubleshooting": "/es/enterprise-server@3.0/rest/overview/troubleshooting", - "/es/enterprise/3.0/v3/troubleshooting": "/es/enterprise-server@3.0/rest/overview/troubleshooting", - "/es/enterprise/v3/troubleshooting": "/es/enterprise-server@latest/rest/overview/troubleshooting", - "/es/enterprise/2.20/rest/overview/troubleshooting": "/es/enterprise-server@2.20/rest/overview/troubleshooting", - "/es/enterprise-server@2.20/v3/troubleshooting": "/es/enterprise-server@2.20/rest/overview/troubleshooting", - "/es/enterprise/2.20/v3/troubleshooting": "/es/enterprise-server@2.20/rest/overview/troubleshooting", - "/es/free-pro-team@latest/rest/reference/actions": "/es/rest/reference/actions", - "/es/v3/actions": "/es/rest/reference/actions", - "/es/free-pro-team@latest/v3/actions": "/es/rest/reference/actions", - "/es/enterprise/3.0/rest/reference/actions": "/es/enterprise-server@3.0/rest/reference/actions", - "/es/enterprise/rest/reference/actions": "/es/enterprise-server@latest/rest/reference/actions", - "/es/enterprise-server@3.0/v3/actions": "/es/enterprise-server@3.0/rest/reference/actions", - "/es/enterprise/3.0/v3/actions": "/es/enterprise-server@3.0/rest/reference/actions", - "/es/enterprise/v3/actions": "/es/enterprise-server@latest/rest/reference/actions", - "/es/free-pro-team@latest/rest/reference/activity": "/es/rest/reference/activity", - "/es/v3/activity": "/es/rest/reference/activity", - "/es/free-pro-team@latest/v3/activity": "/es/rest/reference/activity", - "/es/enterprise/3.0/rest/reference/activity": "/es/enterprise-server@3.0/rest/reference/activity", - "/es/enterprise/rest/reference/activity": "/es/enterprise-server@latest/rest/reference/activity", - "/es/enterprise-server@3.0/v3/activity": "/es/enterprise-server@3.0/rest/reference/activity", - "/es/enterprise/3.0/v3/activity": "/es/enterprise-server@3.0/rest/reference/activity", - "/es/enterprise/v3/activity": "/es/enterprise-server@latest/rest/reference/activity", - "/es/enterprise/2.20/rest/reference/activity": "/es/enterprise-server@2.20/rest/reference/activity", - "/es/enterprise-server@2.20/v3/activity": "/es/enterprise-server@2.20/rest/reference/activity", - "/es/enterprise/2.20/v3/activity": "/es/enterprise-server@2.20/rest/reference/activity", - "/es/free-pro-team@latest/rest/reference/apps": "/es/rest/reference/apps", - "/es/v3/apps": "/es/rest/reference/apps", - "/es/free-pro-team@latest/v3/apps": "/es/rest/reference/apps", - "/es/enterprise/3.0/rest/reference/apps": "/es/enterprise-server@3.0/rest/reference/apps", - "/es/enterprise/rest/reference/apps": "/es/enterprise-server@latest/rest/reference/apps", - "/es/enterprise-server@3.0/v3/apps": "/es/enterprise-server@3.0/rest/reference/apps", - "/es/enterprise/3.0/v3/apps": "/es/enterprise-server@3.0/rest/reference/apps", - "/es/enterprise/v3/apps": "/es/enterprise-server@latest/rest/reference/apps", - "/es/enterprise/2.20/rest/reference/apps": "/es/enterprise-server@2.20/rest/reference/apps", - "/es/enterprise-server@2.20/v3/apps": "/es/enterprise-server@2.20/rest/reference/apps", - "/es/enterprise/2.20/v3/apps": "/es/enterprise-server@2.20/rest/reference/apps", - "/es/free-pro-team@latest/rest/reference/billing": "/es/rest/reference/billing", - "/es/free-pro-team@latest/rest/reference/checks": "/es/rest/reference/checks", - "/es/v3/checks": "/es/rest/reference/checks", - "/es/free-pro-team@latest/v3/checks": "/es/rest/reference/checks", - "/es/enterprise/3.0/rest/reference/checks": "/es/enterprise-server@3.0/rest/reference/checks", - "/es/enterprise/rest/reference/checks": "/es/enterprise-server@latest/rest/reference/checks", - "/es/enterprise-server@3.0/v3/checks": "/es/enterprise-server@3.0/rest/reference/checks", - "/es/enterprise/3.0/v3/checks": "/es/enterprise-server@3.0/rest/reference/checks", - "/es/enterprise/v3/checks": "/es/enterprise-server@latest/rest/reference/checks", - "/es/enterprise/2.20/rest/reference/checks": "/es/enterprise-server@2.20/rest/reference/checks", - "/es/enterprise-server@2.20/v3/checks": "/es/enterprise-server@2.20/rest/reference/checks", - "/es/enterprise/2.20/v3/checks": "/es/enterprise-server@2.20/rest/reference/checks", - "/es/free-pro-team@latest/rest/reference/codes-of-conduct": "/es/rest/reference/codes-of-conduct", - "/es/v3/codes_of_conduct": "/es/rest/reference/codes-of-conduct", - "/es/free-pro-team@latest/v3/codes_of_conduct": "/es/rest/reference/codes-of-conduct", - "/es/v3/codes-of-conduct": "/es/rest/reference/codes-of-conduct", - "/es/free-pro-team@latest/v3/codes-of-conduct": "/es/rest/reference/codes-of-conduct", - "/es/enterprise/3.0/rest/reference/codes-of-conduct": "/es/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/es/enterprise/rest/reference/codes-of-conduct": "/es/enterprise-server@latest/rest/reference/codes-of-conduct", - "/es/enterprise-server@3.0/v3/codes_of_conduct": "/es/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/es/enterprise/3.0/v3/codes_of_conduct": "/es/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/es/enterprise/v3/codes_of_conduct": "/es/enterprise-server@latest/rest/reference/codes-of-conduct", - "/es/enterprise-server@3.0/v3/codes-of-conduct": "/es/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/es/enterprise/3.0/v3/codes-of-conduct": "/es/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/es/enterprise/v3/codes-of-conduct": "/es/enterprise-server@latest/rest/reference/codes-of-conduct", - "/es/enterprise/2.20/rest/reference/codes-of-conduct": "/es/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/es/enterprise-server@2.20/v3/codes_of_conduct": "/es/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/es/enterprise/2.20/v3/codes_of_conduct": "/es/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/es/enterprise-server@2.20/v3/codes-of-conduct": "/es/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/es/enterprise/2.20/v3/codes-of-conduct": "/es/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/es/free-pro-team@latest/rest/reference/emojis": "/es/rest/reference/emojis", - "/es/v3/emojis": "/es/rest/reference/emojis", - "/es/free-pro-team@latest/v3/emojis": "/es/rest/reference/emojis", - "/es/v3/misc": "/es/rest/reference/emojis", - "/es/free-pro-team@latest/v3/misc": "/es/rest/reference/emojis", - "/es/enterprise/3.0/rest/reference/emojis": "/es/enterprise-server@3.0/rest/reference/emojis", - "/es/enterprise/rest/reference/emojis": "/es/enterprise-server@latest/rest/reference/emojis", - "/es/enterprise-server@3.0/v3/emojis": "/es/enterprise-server@3.0/rest/reference/emojis", - "/es/enterprise/3.0/v3/emojis": "/es/enterprise-server@3.0/rest/reference/emojis", - "/es/enterprise/v3/emojis": "/es/enterprise-server@latest/rest/reference/emojis", - "/es/enterprise-server@3.0/v3/misc": "/es/enterprise-server@3.0/rest/reference/emojis", - "/es/enterprise/3.0/v3/misc": "/es/enterprise-server@3.0/rest/reference/emojis", - "/es/enterprise/v3/misc": "/es/enterprise-server@latest/rest/reference/emojis", - "/es/enterprise/2.20/rest/reference/emojis": "/es/enterprise-server@2.20/rest/reference/emojis", - "/es/enterprise-server@2.20/v3/emojis": "/es/enterprise-server@2.20/rest/reference/emojis", - "/es/enterprise/2.20/v3/emojis": "/es/enterprise-server@2.20/rest/reference/emojis", - "/es/enterprise-server@2.20/v3/misc": "/es/enterprise-server@2.20/rest/reference/emojis", - "/es/enterprise/2.20/v3/misc": "/es/enterprise-server@2.20/rest/reference/emojis", - "/es/free-pro-team@latest/rest/reference/enterprise-admin": "/es/rest/reference/enterprise-admin", - "/es/v3/enterprise-admin": "/es/rest/reference/enterprise-admin", - "/es/free-pro-team@latest/v3/enterprise-admin": "/es/rest/reference/enterprise-admin", - "/es/v3/enterprise": "/es/rest/reference/enterprise-admin", - "/es/free-pro-team@latest/v3/enterprise": "/es/rest/reference/enterprise-admin", - "/es/enterprise/3.0/rest/reference/enterprise-admin": "/es/enterprise-server@3.0/rest/reference/enterprise-admin", - "/es/enterprise/rest/reference/enterprise-admin": "/es/enterprise-server@latest/rest/reference/enterprise-admin", - "/es/enterprise-server@3.0/v3/enterprise-admin": "/es/enterprise-server@3.0/rest/reference/enterprise-admin", - "/es/enterprise/3.0/v3/enterprise-admin": "/es/enterprise-server@3.0/rest/reference/enterprise-admin", - "/es/enterprise/v3/enterprise-admin": "/es/enterprise-server@latest/rest/reference/enterprise-admin", - "/es/enterprise-server@3.0/v3/enterprise": "/es/enterprise-server@3.0/rest/reference/enterprise-admin", - "/es/enterprise/3.0/v3/enterprise": "/es/enterprise-server@3.0/rest/reference/enterprise-admin", - "/es/enterprise/v3/enterprise": "/es/enterprise-server@latest/rest/reference/enterprise-admin", - "/es/enterprise/2.20/rest/reference/enterprise-admin": "/es/enterprise-server@2.20/rest/reference/enterprise-admin", - "/es/enterprise-server@2.20/v3/enterprise-admin": "/es/enterprise-server@2.20/rest/reference/enterprise-admin", - "/es/enterprise/2.20/v3/enterprise-admin": "/es/enterprise-server@2.20/rest/reference/enterprise-admin", - "/es/enterprise-server@2.20/v3/enterprise": "/es/enterprise-server@2.20/rest/reference/enterprise-admin", - "/es/enterprise/2.20/v3/enterprise": "/es/enterprise-server@2.20/rest/reference/enterprise-admin", - "/es/free-pro-team@latest/rest/reference/gists": "/es/rest/reference/gists", - "/es/v3/gists": "/es/rest/reference/gists", - "/es/free-pro-team@latest/v3/gists": "/es/rest/reference/gists", - "/es/enterprise/3.0/rest/reference/gists": "/es/enterprise-server@3.0/rest/reference/gists", - "/es/enterprise/rest/reference/gists": "/es/enterprise-server@latest/rest/reference/gists", - "/es/enterprise-server@3.0/v3/gists": "/es/enterprise-server@3.0/rest/reference/gists", - "/es/enterprise/3.0/v3/gists": "/es/enterprise-server@3.0/rest/reference/gists", - "/es/enterprise/v3/gists": "/es/enterprise-server@latest/rest/reference/gists", - "/es/enterprise/2.20/rest/reference/gists": "/es/enterprise-server@2.20/rest/reference/gists", - "/es/enterprise-server@2.20/v3/gists": "/es/enterprise-server@2.20/rest/reference/gists", - "/es/enterprise/2.20/v3/gists": "/es/enterprise-server@2.20/rest/reference/gists", - "/es/free-pro-team@latest/rest/reference/git": "/es/rest/reference/git", - "/es/v3/git": "/es/rest/reference/git", - "/es/free-pro-team@latest/v3/git": "/es/rest/reference/git", - "/es/enterprise/3.0/rest/reference/git": "/es/enterprise-server@3.0/rest/reference/git", - "/es/enterprise/rest/reference/git": "/es/enterprise-server@latest/rest/reference/git", - "/es/enterprise-server@3.0/v3/git": "/es/enterprise-server@3.0/rest/reference/git", - "/es/enterprise/3.0/v3/git": "/es/enterprise-server@3.0/rest/reference/git", - "/es/enterprise/v3/git": "/es/enterprise-server@latest/rest/reference/git", - "/es/enterprise/2.20/rest/reference/git": "/es/enterprise-server@2.20/rest/reference/git", - "/es/enterprise-server@2.20/v3/git": "/es/enterprise-server@2.20/rest/reference/git", - "/es/enterprise/2.20/v3/git": "/es/enterprise-server@2.20/rest/reference/git", - "/es/free-pro-team@latest/rest/reference/gitignore": "/es/rest/reference/gitignore", - "/es/v3/gitignore": "/es/rest/reference/gitignore", - "/es/free-pro-team@latest/v3/gitignore": "/es/rest/reference/gitignore", - "/es/enterprise/3.0/rest/reference/gitignore": "/es/enterprise-server@3.0/rest/reference/gitignore", - "/es/enterprise/rest/reference/gitignore": "/es/enterprise-server@latest/rest/reference/gitignore", - "/es/enterprise-server@3.0/v3/gitignore": "/es/enterprise-server@3.0/rest/reference/gitignore", - "/es/enterprise/3.0/v3/gitignore": "/es/enterprise-server@3.0/rest/reference/gitignore", - "/es/enterprise/v3/gitignore": "/es/enterprise-server@latest/rest/reference/gitignore", - "/es/enterprise/2.20/rest/reference/gitignore": "/es/enterprise-server@2.20/rest/reference/gitignore", - "/es/enterprise-server@2.20/v3/gitignore": "/es/enterprise-server@2.20/rest/reference/gitignore", - "/es/enterprise/2.20/v3/gitignore": "/es/enterprise-server@2.20/rest/reference/gitignore", - "/es/free-pro-team@latest/rest/reference": "/es/rest/reference", - "/es/enterprise/3.0/rest/reference": "/es/enterprise-server@3.0/rest/reference", - "/es/enterprise/rest/reference": "/es/enterprise-server@latest/rest/reference", - "/es/enterprise/2.20/rest/reference": "/es/enterprise-server@2.20/rest/reference", - "/es/free-pro-team@latest/rest/reference/interactions": "/es/rest/reference/interactions", - "/es/v3/interactions": "/es/rest/reference/interactions", - "/es/free-pro-team@latest/v3/interactions": "/es/rest/reference/interactions", - "/es/free-pro-team@latest/rest/reference/issues": "/es/rest/reference/issues", - "/es/v3/issues": "/es/rest/reference/issues", - "/es/free-pro-team@latest/v3/issues": "/es/rest/reference/issues", - "/es/enterprise/3.0/rest/reference/issues": "/es/enterprise-server@3.0/rest/reference/issues", - "/es/enterprise/rest/reference/issues": "/es/enterprise-server@latest/rest/reference/issues", - "/es/enterprise-server@3.0/v3/issues": "/es/enterprise-server@3.0/rest/reference/issues", - "/es/enterprise/3.0/v3/issues": "/es/enterprise-server@3.0/rest/reference/issues", - "/es/enterprise/v3/issues": "/es/enterprise-server@latest/rest/reference/issues", - "/es/enterprise/2.20/rest/reference/issues": "/es/enterprise-server@2.20/rest/reference/issues", - "/es/enterprise-server@2.20/v3/issues": "/es/enterprise-server@2.20/rest/reference/issues", - "/es/enterprise/2.20/v3/issues": "/es/enterprise-server@2.20/rest/reference/issues", - "/es/free-pro-team@latest/rest/reference/licenses": "/es/rest/reference/licenses", - "/es/v3/licenses": "/es/rest/reference/licenses", - "/es/free-pro-team@latest/v3/licenses": "/es/rest/reference/licenses", - "/es/enterprise/3.0/rest/reference/licenses": "/es/enterprise-server@3.0/rest/reference/licenses", - "/es/enterprise/rest/reference/licenses": "/es/enterprise-server@latest/rest/reference/licenses", - "/es/enterprise-server@3.0/v3/licenses": "/es/enterprise-server@3.0/rest/reference/licenses", - "/es/enterprise/3.0/v3/licenses": "/es/enterprise-server@3.0/rest/reference/licenses", - "/es/enterprise/v3/licenses": "/es/enterprise-server@latest/rest/reference/licenses", - "/es/enterprise/2.20/rest/reference/licenses": "/es/enterprise-server@2.20/rest/reference/licenses", - "/es/enterprise-server@2.20/v3/licenses": "/es/enterprise-server@2.20/rest/reference/licenses", - "/es/enterprise/2.20/v3/licenses": "/es/enterprise-server@2.20/rest/reference/licenses", - "/es/free-pro-team@latest/rest/reference/markdown": "/es/rest/reference/markdown", - "/es/v3/markdown": "/es/rest/reference/markdown", - "/es/free-pro-team@latest/v3/markdown": "/es/rest/reference/markdown", - "/es/enterprise/3.0/rest/reference/markdown": "/es/enterprise-server@3.0/rest/reference/markdown", - "/es/enterprise/rest/reference/markdown": "/es/enterprise-server@latest/rest/reference/markdown", - "/es/enterprise-server@3.0/v3/markdown": "/es/enterprise-server@3.0/rest/reference/markdown", - "/es/enterprise/3.0/v3/markdown": "/es/enterprise-server@3.0/rest/reference/markdown", - "/es/enterprise/v3/markdown": "/es/enterprise-server@latest/rest/reference/markdown", - "/es/enterprise/2.20/rest/reference/markdown": "/es/enterprise-server@2.20/rest/reference/markdown", - "/es/enterprise-server@2.20/v3/markdown": "/es/enterprise-server@2.20/rest/reference/markdown", - "/es/enterprise/2.20/v3/markdown": "/es/enterprise-server@2.20/rest/reference/markdown", - "/es/free-pro-team@latest/rest/reference/meta": "/es/rest/reference/meta", - "/es/v3/meta": "/es/rest/reference/meta", - "/es/free-pro-team@latest/v3/meta": "/es/rest/reference/meta", - "/es/enterprise/3.0/rest/reference/meta": "/es/enterprise-server@3.0/rest/reference/meta", - "/es/enterprise/rest/reference/meta": "/es/enterprise-server@latest/rest/reference/meta", - "/es/enterprise-server@3.0/v3/meta": "/es/enterprise-server@3.0/rest/reference/meta", - "/es/enterprise/3.0/v3/meta": "/es/enterprise-server@3.0/rest/reference/meta", - "/es/enterprise/v3/meta": "/es/enterprise-server@latest/rest/reference/meta", - "/es/enterprise/2.20/rest/reference/meta": "/es/enterprise-server@2.20/rest/reference/meta", - "/es/enterprise-server@2.20/v3/meta": "/es/enterprise-server@2.20/rest/reference/meta", - "/es/enterprise/2.20/v3/meta": "/es/enterprise-server@2.20/rest/reference/meta", - "/es/free-pro-team@latest/rest/reference/migrations": "/es/rest/reference/migrations", - "/es/v3/migrations": "/es/rest/reference/migrations", - "/es/free-pro-team@latest/v3/migrations": "/es/rest/reference/migrations", - "/es/v3/migration": "/es/rest/reference/migrations", - "/es/free-pro-team@latest/v3/migration": "/es/rest/reference/migrations", - "/es/v3/migration/migrations": "/es/rest/reference/migrations", - "/es/free-pro-team@latest/v3/migration/migrations": "/es/rest/reference/migrations", - "/es/free-pro-team@latest/rest/reference/oauth-authorizations": "/es/rest/reference/oauth-authorizations", - "/es/v3/oauth_authorizations": "/es/rest/reference/oauth-authorizations", - "/es/free-pro-team@latest/v3/oauth_authorizations": "/es/rest/reference/oauth-authorizations", - "/es/v3/oauth-authorizations": "/es/rest/reference/oauth-authorizations", - "/es/free-pro-team@latest/v3/oauth-authorizations": "/es/rest/reference/oauth-authorizations", - "/es/enterprise/3.0/rest/reference/oauth-authorizations": "/es/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/es/enterprise/rest/reference/oauth-authorizations": "/es/enterprise-server@latest/rest/reference/oauth-authorizations", - "/es/enterprise-server@3.0/v3/oauth_authorizations": "/es/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/es/enterprise/3.0/v3/oauth_authorizations": "/es/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/es/enterprise/v3/oauth_authorizations": "/es/enterprise-server@latest/rest/reference/oauth-authorizations", - "/es/enterprise-server@3.0/v3/oauth-authorizations": "/es/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/es/enterprise/3.0/v3/oauth-authorizations": "/es/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/es/enterprise/v3/oauth-authorizations": "/es/enterprise-server@latest/rest/reference/oauth-authorizations", - "/es/enterprise/2.20/rest/reference/oauth-authorizations": "/es/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/es/enterprise-server@2.20/v3/oauth_authorizations": "/es/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/es/enterprise/2.20/v3/oauth_authorizations": "/es/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/es/enterprise-server@2.20/v3/oauth-authorizations": "/es/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/es/enterprise/2.20/v3/oauth-authorizations": "/es/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/es/free-pro-team@latest/rest/reference/orgs": "/es/rest/reference/orgs", - "/es/v3/orgs": "/es/rest/reference/orgs", - "/es/free-pro-team@latest/v3/orgs": "/es/rest/reference/orgs", - "/es/enterprise/3.0/rest/reference/orgs": "/es/enterprise-server@3.0/rest/reference/orgs", - "/es/enterprise/rest/reference/orgs": "/es/enterprise-server@latest/rest/reference/orgs", - "/es/enterprise-server@3.0/v3/orgs": "/es/enterprise-server@3.0/rest/reference/orgs", - "/es/enterprise/3.0/v3/orgs": "/es/enterprise-server@3.0/rest/reference/orgs", - "/es/enterprise/v3/orgs": "/es/enterprise-server@latest/rest/reference/orgs", - "/es/enterprise/2.20/rest/reference/orgs": "/es/enterprise-server@2.20/rest/reference/orgs", - "/es/enterprise-server@2.20/v3/orgs": "/es/enterprise-server@2.20/rest/reference/orgs", - "/es/enterprise/2.20/v3/orgs": "/es/enterprise-server@2.20/rest/reference/orgs", - "/es/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/es/rest/reference/permissions-required-for-github-apps", - "/es/v3/apps/permissions ---": "/es/rest/reference/permissions-required-for-github-apps", - "/es/free-pro-team@latest/v3/apps/permissions ---": "/es/rest/reference/permissions-required-for-github-apps", - "/es/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/es/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/es/enterprise/rest/reference/permissions-required-for-github-apps": "/es/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/es/enterprise-server@3.0/v3/apps/permissions ---": "/es/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/es/enterprise/3.0/v3/apps/permissions ---": "/es/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/es/enterprise/v3/apps/permissions ---": "/es/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/es/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/es/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/es/enterprise-server@2.20/v3/apps/permissions ---": "/es/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/es/enterprise/2.20/v3/apps/permissions ---": "/es/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/es/free-pro-team@latest/rest/reference/projects": "/es/rest/reference/projects", - "/es/v3/projects": "/es/rest/reference/projects", - "/es/free-pro-team@latest/v3/projects": "/es/rest/reference/projects", - "/es/enterprise/3.0/rest/reference/projects": "/es/enterprise-server@3.0/rest/reference/projects", - "/es/enterprise/rest/reference/projects": "/es/enterprise-server@latest/rest/reference/projects", - "/es/enterprise-server@3.0/v3/projects": "/es/enterprise-server@3.0/rest/reference/projects", - "/es/enterprise/3.0/v3/projects": "/es/enterprise-server@3.0/rest/reference/projects", - "/es/enterprise/v3/projects": "/es/enterprise-server@latest/rest/reference/projects", - "/es/enterprise/2.20/rest/reference/projects": "/es/enterprise-server@2.20/rest/reference/projects", - "/es/enterprise-server@2.20/v3/projects": "/es/enterprise-server@2.20/rest/reference/projects", - "/es/enterprise/2.20/v3/projects": "/es/enterprise-server@2.20/rest/reference/projects", - "/es/free-pro-team@latest/rest/reference/pulls": "/es/rest/reference/pulls", - "/es/v3/pulls": "/es/rest/reference/pulls", - "/es/free-pro-team@latest/v3/pulls": "/es/rest/reference/pulls", - "/es/enterprise/3.0/rest/reference/pulls": "/es/enterprise-server@3.0/rest/reference/pulls", - "/es/enterprise/rest/reference/pulls": "/es/enterprise-server@latest/rest/reference/pulls", - "/es/enterprise-server@3.0/v3/pulls": "/es/enterprise-server@3.0/rest/reference/pulls", - "/es/enterprise/3.0/v3/pulls": "/es/enterprise-server@3.0/rest/reference/pulls", - "/es/enterprise/v3/pulls": "/es/enterprise-server@latest/rest/reference/pulls", - "/es/enterprise/2.20/rest/reference/pulls": "/es/enterprise-server@2.20/rest/reference/pulls", - "/es/enterprise-server@2.20/v3/pulls": "/es/enterprise-server@2.20/rest/reference/pulls", - "/es/enterprise/2.20/v3/pulls": "/es/enterprise-server@2.20/rest/reference/pulls", - "/es/free-pro-team@latest/rest/reference/rate-limit": "/es/rest/reference/rate-limit", - "/es/v3/rate_limit": "/es/rest/reference/rate-limit", - "/es/free-pro-team@latest/v3/rate_limit": "/es/rest/reference/rate-limit", - "/es/v3/rate-limit": "/es/rest/reference/rate-limit", - "/es/free-pro-team@latest/v3/rate-limit": "/es/rest/reference/rate-limit", - "/es/enterprise/3.0/rest/reference/rate-limit": "/es/enterprise-server@3.0/rest/reference/rate-limit", - "/es/enterprise/rest/reference/rate-limit": "/es/enterprise-server@latest/rest/reference/rate-limit", - "/es/enterprise-server@3.0/v3/rate_limit": "/es/enterprise-server@3.0/rest/reference/rate-limit", - "/es/enterprise/3.0/v3/rate_limit": "/es/enterprise-server@3.0/rest/reference/rate-limit", - "/es/enterprise/v3/rate_limit": "/es/enterprise-server@latest/rest/reference/rate-limit", - "/es/enterprise-server@3.0/v3/rate-limit": "/es/enterprise-server@3.0/rest/reference/rate-limit", - "/es/enterprise/3.0/v3/rate-limit": "/es/enterprise-server@3.0/rest/reference/rate-limit", - "/es/enterprise/v3/rate-limit": "/es/enterprise-server@latest/rest/reference/rate-limit", - "/es/enterprise/2.20/rest/reference/rate-limit": "/es/enterprise-server@2.20/rest/reference/rate-limit", - "/es/enterprise-server@2.20/v3/rate_limit": "/es/enterprise-server@2.20/rest/reference/rate-limit", - "/es/enterprise/2.20/v3/rate_limit": "/es/enterprise-server@2.20/rest/reference/rate-limit", - "/es/enterprise-server@2.20/v3/rate-limit": "/es/enterprise-server@2.20/rest/reference/rate-limit", - "/es/enterprise/2.20/v3/rate-limit": "/es/enterprise-server@2.20/rest/reference/rate-limit", - "/es/free-pro-team@latest/rest/reference/reactions": "/es/rest/reference/reactions", - "/es/v3/reactions": "/es/rest/reference/reactions", - "/es/free-pro-team@latest/v3/reactions": "/es/rest/reference/reactions", - "/es/enterprise/3.0/rest/reference/reactions": "/es/enterprise-server@3.0/rest/reference/reactions", - "/es/enterprise/rest/reference/reactions": "/es/enterprise-server@latest/rest/reference/reactions", - "/es/enterprise-server@3.0/v3/reactions": "/es/enterprise-server@3.0/rest/reference/reactions", - "/es/enterprise/3.0/v3/reactions": "/es/enterprise-server@3.0/rest/reference/reactions", - "/es/enterprise/v3/reactions": "/es/enterprise-server@latest/rest/reference/reactions", - "/es/enterprise/2.20/rest/reference/reactions": "/es/enterprise-server@2.20/rest/reference/reactions", - "/es/enterprise-server@2.20/v3/reactions": "/es/enterprise-server@2.20/rest/reference/reactions", - "/es/enterprise/2.20/v3/reactions": "/es/enterprise-server@2.20/rest/reference/reactions", - "/es/free-pro-team@latest/rest/reference/repos": "/es/rest/reference/repos", - "/es/v3/repos": "/es/rest/reference/repos", - "/es/free-pro-team@latest/v3/repos": "/es/rest/reference/repos", - "/es/enterprise/3.0/rest/reference/repos": "/es/enterprise-server@3.0/rest/reference/repos", - "/es/enterprise/rest/reference/repos": "/es/enterprise-server@latest/rest/reference/repos", - "/es/enterprise-server@3.0/v3/repos": "/es/enterprise-server@3.0/rest/reference/repos", - "/es/enterprise/3.0/v3/repos": "/es/enterprise-server@3.0/rest/reference/repos", - "/es/enterprise/v3/repos": "/es/enterprise-server@latest/rest/reference/repos", - "/es/enterprise/2.20/rest/reference/repos": "/es/enterprise-server@2.20/rest/reference/repos", - "/es/enterprise-server@2.20/v3/repos": "/es/enterprise-server@2.20/rest/reference/repos", - "/es/enterprise/2.20/v3/repos": "/es/enterprise-server@2.20/rest/reference/repos", - "/es/free-pro-team@latest/rest/reference/scim": "/es/rest/reference/scim", - "/es/v3/scim": "/es/rest/reference/scim", - "/es/free-pro-team@latest/v3/scim": "/es/rest/reference/scim", - "/es/free-pro-team@latest/rest/reference/search": "/es/rest/reference/search", - "/es/v3/search": "/es/rest/reference/search", - "/es/free-pro-team@latest/v3/search": "/es/rest/reference/search", - "/es/enterprise/3.0/rest/reference/search": "/es/enterprise-server@3.0/rest/reference/search", - "/es/enterprise/rest/reference/search": "/es/enterprise-server@latest/rest/reference/search", - "/es/enterprise-server@3.0/v3/search": "/es/enterprise-server@3.0/rest/reference/search", - "/es/enterprise/3.0/v3/search": "/es/enterprise-server@3.0/rest/reference/search", - "/es/enterprise/v3/search": "/es/enterprise-server@latest/rest/reference/search", - "/es/enterprise/2.20/rest/reference/search": "/es/enterprise-server@2.20/rest/reference/search", - "/es/enterprise-server@2.20/v3/search": "/es/enterprise-server@2.20/rest/reference/search", - "/es/enterprise/2.20/v3/search": "/es/enterprise-server@2.20/rest/reference/search", - "/es/free-pro-team@latest/rest/reference/teams": "/es/rest/reference/teams", - "/es/v3/teams": "/es/rest/reference/teams", - "/es/free-pro-team@latest/v3/teams": "/es/rest/reference/teams", - "/es/enterprise/3.0/rest/reference/teams": "/es/enterprise-server@3.0/rest/reference/teams", - "/es/enterprise/rest/reference/teams": "/es/enterprise-server@latest/rest/reference/teams", - "/es/enterprise-server@3.0/v3/teams": "/es/enterprise-server@3.0/rest/reference/teams", - "/es/enterprise/3.0/v3/teams": "/es/enterprise-server@3.0/rest/reference/teams", - "/es/enterprise/v3/teams": "/es/enterprise-server@latest/rest/reference/teams", - "/es/enterprise/2.20/rest/reference/teams": "/es/enterprise-server@2.20/rest/reference/teams", - "/es/enterprise-server@2.20/v3/teams": "/es/enterprise-server@2.20/rest/reference/teams", - "/es/enterprise/2.20/v3/teams": "/es/enterprise-server@2.20/rest/reference/teams", - "/es/free-pro-team@latest/rest/reference/users": "/es/rest/reference/users", - "/es/v3/users": "/es/rest/reference/users", - "/es/free-pro-team@latest/v3/users": "/es/rest/reference/users", - "/es/enterprise/3.0/rest/reference/users": "/es/enterprise-server@3.0/rest/reference/users", - "/es/enterprise/rest/reference/users": "/es/enterprise-server@latest/rest/reference/users", - "/es/enterprise-server@3.0/v3/users": "/es/enterprise-server@3.0/rest/reference/users", - "/es/enterprise/3.0/v3/users": "/es/enterprise-server@3.0/rest/reference/users", - "/es/enterprise/v3/users": "/es/enterprise-server@latest/rest/reference/users", - "/es/enterprise/2.20/rest/reference/users": "/es/enterprise-server@2.20/rest/reference/users", - "/es/enterprise-server@2.20/v3/users": "/es/enterprise-server@2.20/rest/reference/users", - "/es/enterprise/2.20/v3/users": "/es/enterprise-server@2.20/rest/reference/users", - "/pt/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/3.0/admin/articles/restoring-github-enterprise": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/admin/articles/restoring-github-enterprise": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/admin/articles/restoring-github-enterprise": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/3.0/admin/articles/restoring-enterprise-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/admin/articles/restoring-enterprise-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/admin/articles/restoring-enterprise-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise-server@3.0/admin/articles/restoring-repository-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/3.0/admin/articles/restoring-repository-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/admin/articles/restoring-repository-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/admin/articles/restoring-repository-data": "/pt/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/pt/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/2.20/admin/articles/restoring-github-enterprise": "/pt/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/pt/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/2.20/admin/articles/restoring-enterprise-data": "/pt/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise-server@2.20/admin/articles/restoring-repository-data": "/pt/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise/2.20/admin/articles/restoring-repository-data": "/pt/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", - "/pt/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/pt/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/pt/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/pt/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", - "/pt/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/pt/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", - "/pt/github-ae@latest/admin/articles/restricting-ssh-access-to-specific-hosts": "/pt/github-ae@latest/admin/configuration/configuring-your-enterprise", - "/pt/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/github-ae@latest/admin/user-management/restricting-repository-creation-in-your-instance": "/pt/github-ae@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise", - "/pt/v3/oauth": "/pt/developers/apps/authorizing-oauth-apps", - "/pt/free-pro-team@latest/v3/oauth": "/pt/developers/apps/authorizing-oauth-apps", - "/pt/enterprise-server@3.0/v3/oauth": "/pt/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/pt/enterprise/3.0/v3/oauth": "/pt/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", - "/pt/enterprise/v3/oauth": "/pt/enterprise-server@latest/developers/apps/authorizing-oauth-apps", - "/pt/enterprise-server@2.20/v3/oauth": "/pt/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/pt/enterprise/2.20/v3/oauth": "/pt/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", - "/pt/github-ae@latest/v3/oauth": "/pt/github-ae@latest/developers/apps/authorizing-oauth-apps", - "/pt/v3/integrations": "/pt/developers/apps", - "/pt/free-pro-team@latest/v3/integrations": "/pt/developers/apps", - "/pt/enterprise-server@3.0/v3/integrations": "/pt/enterprise-server@3.0/developers/apps", - "/pt/enterprise/3.0/v3/integrations": "/pt/enterprise-server@3.0/developers/apps", - "/pt/enterprise/v3/integrations": "/pt/enterprise-server@latest/developers/apps", - "/pt/enterprise-server@2.20/v3/integrations": "/pt/enterprise-server@2.20/developers/apps", - "/pt/enterprise/2.20/v3/integrations": "/pt/enterprise-server@2.20/developers/apps", - "/pt/github-ae@latest/v3/integrations": "/pt/github-ae@latest/developers/apps", - "/pt/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/pt/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", - "/pt/v3/versions": "/pt/developers/overview/about-githubs-apis", - "/pt/free-pro-team@latest/v3/versions": "/pt/developers/overview/about-githubs-apis", - "/pt/enterprise-server@3.0/v3/versions": "/pt/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/pt/enterprise/3.0/v3/versions": "/pt/enterprise-server@3.0/developers/overview/about-githubs-apis", - "/pt/enterprise/v3/versions": "/pt/enterprise-server@latest/developers/overview/about-githubs-apis", - "/pt/enterprise-server@2.20/v3/versions": "/pt/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/pt/enterprise/2.20/v3/versions": "/pt/enterprise-server@2.20/developers/overview/about-githubs-apis", - "/pt/github-ae@latest/v3/versions": "/pt/github-ae@latest/developers/overview/about-githubs-apis", - "/pt/v3/guides/managing-deploy-keys": "/pt/developers/overview/managing-deploy-keys", - "/pt/free-pro-team@latest/v3/guides/managing-deploy-keys": "/pt/developers/overview/managing-deploy-keys", - "/pt/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/pt/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/pt/enterprise/3.0/v3/guides/managing-deploy-keys": "/pt/enterprise-server@3.0/developers/overview/managing-deploy-keys", - "/pt/enterprise/v3/guides/managing-deploy-keys": "/pt/enterprise-server@latest/developers/overview/managing-deploy-keys", - "/pt/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/pt/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/pt/enterprise/2.20/v3/guides/managing-deploy-keys": "/pt/enterprise-server@2.20/developers/overview/managing-deploy-keys", - "/pt/github-ae@latest/v3/guides/managing-deploy-keys": "/pt/github-ae@latest/developers/overview/managing-deploy-keys", - "/pt/v3/guides/automating-deployments-to-integrators": "/pt/developers/overview/replacing-github-services", - "/pt/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/pt/developers/overview/replacing-github-services", - "/pt/v3/guides/replacing-github-services": "/pt/developers/overview/replacing-github-services", - "/pt/free-pro-team@latest/v3/guides/replacing-github-services": "/pt/developers/overview/replacing-github-services", - "/pt/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/pt/enterprise-server@3.0/developers/overview/replacing-github-services", - "/pt/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/pt/enterprise-server@3.0/developers/overview/replacing-github-services", - "/pt/enterprise/v3/guides/automating-deployments-to-integrators": "/pt/enterprise-server@latest/developers/overview/replacing-github-services", - "/pt/enterprise-server@3.0/v3/guides/replacing-github-services": "/pt/enterprise-server@3.0/developers/overview/replacing-github-services", - "/pt/enterprise/3.0/v3/guides/replacing-github-services": "/pt/enterprise-server@3.0/developers/overview/replacing-github-services", - "/pt/enterprise/v3/guides/replacing-github-services": "/pt/enterprise-server@latest/developers/overview/replacing-github-services", - "/pt/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/pt/enterprise-server@2.20/developers/overview/replacing-github-services", - "/pt/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/pt/enterprise-server@2.20/developers/overview/replacing-github-services", - "/pt/enterprise-server@2.20/v3/guides/replacing-github-services": "/pt/enterprise-server@2.20/developers/overview/replacing-github-services", - "/pt/enterprise/2.20/v3/guides/replacing-github-services": "/pt/enterprise-server@2.20/developers/overview/replacing-github-services", - "/pt/v3/guides/using-ssh-agent-forwarding": "/pt/developers/overview/using-ssh-agent-forwarding", - "/pt/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/pt/developers/overview/using-ssh-agent-forwarding", - "/pt/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/pt/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/pt/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/pt/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", - "/pt/enterprise/v3/guides/using-ssh-agent-forwarding": "/pt/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", - "/pt/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/pt/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/pt/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/pt/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", - "/pt/github-ae@latest/v3/guides/using-ssh-agent-forwarding": "/pt/github-ae@latest/developers/overview/using-ssh-agent-forwarding", - "/pt/v3/activity/event_types": "/pt/developers/webhooks-and-events/github-event-types", - "/pt/free-pro-team@latest/v3/activity/event_types": "/pt/developers/webhooks-and-events/github-event-types", - "/pt/enterprise-server@3.0/v3/activity/event_types": "/pt/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/pt/enterprise/3.0/v3/activity/event_types": "/pt/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", - "/pt/enterprise/v3/activity/event_types": "/pt/enterprise-server@latest/developers/webhooks-and-events/github-event-types", - "/pt/enterprise-server@2.20/v3/activity/event_types": "/pt/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/pt/enterprise/2.20/v3/activity/event_types": "/pt/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", - "/pt/github-ae@latest/v3/activity/event_types": "/pt/github-ae@latest/developers/webhooks-and-events/github-event-types", - "/pt/v3/issues/issue-event-types": "/pt/developers/webhooks-and-events/issue-event-types", - "/pt/free-pro-team@latest/v3/issues/issue-event-types": "/pt/developers/webhooks-and-events/issue-event-types", - "/pt/enterprise-server@3.0/v3/issues/issue-event-types": "/pt/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/pt/enterprise/3.0/v3/issues/issue-event-types": "/pt/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", - "/pt/enterprise/v3/issues/issue-event-types": "/pt/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", - "/pt/enterprise-server@2.20/v3/issues/issue-event-types": "/pt/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/pt/enterprise/2.20/v3/issues/issue-event-types": "/pt/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", - "/pt/github-ae@latest/v3/issues/issue-event-types": "/pt/github-ae@latest/developers/webhooks-and-events/issue-event-types", - "/pt/v3/activity/events/types": "/pt/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/free-pro-team@latest/v3/activity/events/types": "/pt/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/enterprise-server@3.0/v3/activity/events/types": "/pt/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/enterprise/3.0/v3/activity/events/types": "/pt/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/enterprise/v3/activity/events/types": "/pt/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/enterprise-server@2.20/v3/activity/events/types": "/pt/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/enterprise/2.20/v3/activity/events/types": "/pt/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/github-ae@latest/v3/activity/events/types": "/pt/github-ae@latest/developers/webhooks-and-events/webhook-events-and-payloads", - "/pt/articles/restoring-branches-in-a-pull-request": "/pt/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/pt/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/pt/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/pt/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/articles/restoring-branches-in-a-pull-request": "/pt/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/pt/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/pt/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/github-ae@latest/articles/restoring-branches-in-a-pull-request": "/pt/github-ae@latest/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", - "/pt/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/pt/github/administering-a-repository/restoring-a-deleted-repository", - "/pt/articles/restoring-a-deleted-repository": "/pt/github/administering-a-repository/restoring-a-deleted-repository", - "/pt/free-pro-team@latest/articles/restoring-a-deleted-repository": "/pt/github/administering-a-repository/restoring-a-deleted-repository", - "/pt/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/pt/articles/restricting-access-to-your-organization-s-data": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/pt/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/pt/articles/restricting-access-to-your-organizations-data": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/pt/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", - "/pt/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/pt/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/pt/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/pt/articles/restricting-email-notifications-to-an-approved-domain": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/pt/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", - "/pt/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/articles/restricting-repository-creation-in-your-organization": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/articles/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/github-ae@latest/articles/restricting-repository-creation-in-your-organization": "/pt/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", - "/pt/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/github-ae@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/pt/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", - "/pt/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/github-ae@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/pt/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", - "/pt/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/pt/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", - "/pt/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/pt/graphql/guides/forming-calls-with-graphql", - "/pt/v4/guides/forming-calls": "/pt/graphql/guides/forming-calls-with-graphql", - "/pt/free-pro-team@latest/v4/guides/forming-calls": "/pt/graphql/guides/forming-calls-with-graphql", - "/pt/graphql/guides/forming-calls": "/pt/graphql/guides/forming-calls-with-graphql", - "/pt/free-pro-team@latest/graphql/guides/forming-calls": "/pt/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/pt/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/graphql/guides/forming-calls-with-graphql": "/pt/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise-server@3.0/v4/guides/forming-calls": "/pt/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/3.0/v4/guides/forming-calls": "/pt/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/v4/guides/forming-calls": "/pt/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise-server@3.0/graphql/guides/forming-calls": "/pt/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/3.0/graphql/guides/forming-calls": "/pt/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/graphql/guides/forming-calls": "/pt/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/pt/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise-server@2.20/v4/guides/forming-calls": "/pt/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/2.20/v4/guides/forming-calls": "/pt/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise-server@2.20/graphql/guides/forming-calls": "/pt/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/pt/enterprise/2.20/graphql/guides/forming-calls": "/pt/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", - "/pt/github-ae@latest/v4/guides/forming-calls": "/pt/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/pt/github-ae@latest/graphql/guides/forming-calls": "/pt/github-ae@latest/graphql/guides/forming-calls-with-graphql", - "/pt/free-pro-team@latest/graphql/guides": "/pt/graphql/guides", - "/pt/v4/guides": "/pt/graphql/guides", - "/pt/free-pro-team@latest/v4/guides": "/pt/graphql/guides", - "/pt/enterprise/3.0/graphql/guides": "/pt/enterprise-server@3.0/graphql/guides", - "/pt/enterprise/graphql/guides": "/pt/enterprise-server@latest/graphql/guides", - "/pt/enterprise-server@3.0/v4/guides": "/pt/enterprise-server@3.0/graphql/guides", - "/pt/enterprise/3.0/v4/guides": "/pt/enterprise-server@3.0/graphql/guides", - "/pt/enterprise/v4/guides": "/pt/enterprise-server@latest/graphql/guides", - "/pt/enterprise/2.20/graphql/guides": "/pt/enterprise-server@2.20/graphql/guides", - "/pt/enterprise-server@2.20/v4/guides": "/pt/enterprise-server@2.20/graphql/guides", - "/pt/enterprise/2.20/v4/guides": "/pt/enterprise-server@2.20/graphql/guides", - "/pt/github-ae@latest/v4/guides": "/pt/github-ae@latest/graphql/guides", - "/pt/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/pt/graphql/guides/introduction-to-graphql", - "/pt/v4/guides/intro-to-graphql": "/pt/graphql/guides/introduction-to-graphql", - "/pt/free-pro-team@latest/v4/guides/intro-to-graphql": "/pt/graphql/guides/introduction-to-graphql", - "/pt/graphql/guides/intro-to-graphql": "/pt/graphql/guides/introduction-to-graphql", - "/pt/free-pro-team@latest/graphql/guides/intro-to-graphql": "/pt/graphql/guides/introduction-to-graphql", - "/pt/enterprise/3.0/graphql/guides/introduction-to-graphql": "/pt/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/pt/enterprise/graphql/guides/introduction-to-graphql": "/pt/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/pt/enterprise-server@3.0/v4/guides/intro-to-graphql": "/pt/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/pt/enterprise/3.0/v4/guides/intro-to-graphql": "/pt/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/pt/enterprise/v4/guides/intro-to-graphql": "/pt/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/pt/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/pt/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/pt/enterprise/3.0/graphql/guides/intro-to-graphql": "/pt/enterprise-server@3.0/graphql/guides/introduction-to-graphql", - "/pt/enterprise/graphql/guides/intro-to-graphql": "/pt/enterprise-server@latest/graphql/guides/introduction-to-graphql", - "/pt/enterprise/2.20/graphql/guides/introduction-to-graphql": "/pt/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/pt/enterprise-server@2.20/v4/guides/intro-to-graphql": "/pt/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/pt/enterprise/2.20/v4/guides/intro-to-graphql": "/pt/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/pt/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/pt/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/pt/enterprise/2.20/graphql/guides/intro-to-graphql": "/pt/enterprise-server@2.20/graphql/guides/introduction-to-graphql", - "/pt/github-ae@latest/v4/guides/intro-to-graphql": "/pt/github-ae@latest/graphql/guides/introduction-to-graphql", - "/pt/github-ae@latest/graphql/guides/intro-to-graphql": "/pt/github-ae@latest/graphql/guides/introduction-to-graphql", - "/pt/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/pt/graphql/guides/managing-enterprise-accounts", - "/pt/v4/guides/managing-enterprise-accounts": "/pt/graphql/guides/managing-enterprise-accounts", - "/pt/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/pt/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/pt/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise/graphql/guides/managing-enterprise-accounts": "/pt/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/pt/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/pt/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise/v4/guides/managing-enterprise-accounts": "/pt/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/pt/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/pt/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/pt/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/pt/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", - "/pt/github-ae@latest/v4/guides/managing-enterprise-accounts": "/pt/github-ae@latest/graphql/guides/managing-enterprise-accounts", - "/pt/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/pt/graphql/guides/migrating-from-rest-to-graphql", - "/pt/v4/guides/migrating-from-rest": "/pt/graphql/guides/migrating-from-rest-to-graphql", - "/pt/free-pro-team@latest/v4/guides/migrating-from-rest": "/pt/graphql/guides/migrating-from-rest-to-graphql", - "/pt/graphql/guides/migrating-from-rest": "/pt/graphql/guides/migrating-from-rest-to-graphql", - "/pt/free-pro-team@latest/graphql/guides/migrating-from-rest": "/pt/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/pt/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/pt/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise-server@3.0/v4/guides/migrating-from-rest": "/pt/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/3.0/v4/guides/migrating-from-rest": "/pt/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/v4/guides/migrating-from-rest": "/pt/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/pt/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/3.0/graphql/guides/migrating-from-rest": "/pt/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/graphql/guides/migrating-from-rest": "/pt/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/pt/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise-server@2.20/v4/guides/migrating-from-rest": "/pt/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/2.20/v4/guides/migrating-from-rest": "/pt/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/pt/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/pt/enterprise/2.20/graphql/guides/migrating-from-rest": "/pt/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", - "/pt/github-ae@latest/v4/guides/migrating-from-rest": "/pt/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/pt/github-ae@latest/graphql/guides/migrating-from-rest": "/pt/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", - "/pt/free-pro-team@latest/graphql/guides/using-global-node-ids": "/pt/graphql/guides/using-global-node-ids", - "/pt/v4/guides/using-global-node-ids": "/pt/graphql/guides/using-global-node-ids", - "/pt/free-pro-team@latest/v4/guides/using-global-node-ids": "/pt/graphql/guides/using-global-node-ids", - "/pt/enterprise/3.0/graphql/guides/using-global-node-ids": "/pt/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/pt/enterprise/graphql/guides/using-global-node-ids": "/pt/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/pt/enterprise-server@3.0/v4/guides/using-global-node-ids": "/pt/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/pt/enterprise/3.0/v4/guides/using-global-node-ids": "/pt/enterprise-server@3.0/graphql/guides/using-global-node-ids", - "/pt/enterprise/v4/guides/using-global-node-ids": "/pt/enterprise-server@latest/graphql/guides/using-global-node-ids", - "/pt/enterprise/2.20/graphql/guides/using-global-node-ids": "/pt/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/pt/enterprise-server@2.20/v4/guides/using-global-node-ids": "/pt/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/pt/enterprise/2.20/v4/guides/using-global-node-ids": "/pt/enterprise-server@2.20/graphql/guides/using-global-node-ids", - "/pt/github-ae@latest/v4/guides/using-global-node-ids": "/pt/github-ae@latest/graphql/guides/using-global-node-ids", - "/pt/free-pro-team@latest/graphql/guides/using-the-explorer": "/pt/graphql/guides/using-the-explorer", - "/pt/v4/guides/using-the-explorer": "/pt/graphql/guides/using-the-explorer", - "/pt/free-pro-team@latest/v4/guides/using-the-explorer": "/pt/graphql/guides/using-the-explorer", - "/pt/enterprise/3.0/graphql/guides/using-the-explorer": "/pt/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/pt/enterprise/graphql/guides/using-the-explorer": "/pt/enterprise-server@latest/graphql/guides/using-the-explorer", - "/pt/enterprise-server@3.0/v4/guides/using-the-explorer": "/pt/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/pt/enterprise/3.0/v4/guides/using-the-explorer": "/pt/enterprise-server@3.0/graphql/guides/using-the-explorer", - "/pt/enterprise/v4/guides/using-the-explorer": "/pt/enterprise-server@latest/graphql/guides/using-the-explorer", - "/pt/enterprise/2.20/graphql/guides/using-the-explorer": "/pt/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/pt/enterprise-server@2.20/v4/guides/using-the-explorer": "/pt/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/pt/enterprise/2.20/v4/guides/using-the-explorer": "/pt/enterprise-server@2.20/graphql/guides/using-the-explorer", - "/pt/github-ae@latest/v4/guides/using-the-explorer": "/pt/github-ae@latest/graphql/guides/using-the-explorer", - "/pt/free-pro-team@latest/graphql": "/pt/graphql", - "/pt/v4": "/pt/graphql", - "/pt/free-pro-team@latest/v4": "/pt/graphql", - "/pt/enterprise/3.0/graphql": "/pt/enterprise-server@3.0/graphql", - "/pt/enterprise/graphql": "/pt/enterprise-server@latest/graphql", - "/pt/enterprise-server@3.0/v4": "/pt/enterprise-server@3.0/graphql", - "/pt/enterprise/3.0/v4": "/pt/enterprise-server@3.0/graphql", - "/pt/enterprise/v4": "/pt/enterprise-server@latest/graphql", - "/pt/enterprise/2.20/graphql": "/pt/enterprise-server@2.20/graphql", - "/pt/enterprise-server@2.20/v4": "/pt/enterprise-server@2.20/graphql", - "/pt/enterprise/2.20/v4": "/pt/enterprise-server@2.20/graphql", - "/pt/github-ae@latest/v4": "/pt/github-ae@latest/graphql", - "/pt/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/pt/graphql/overview/about-the-graphql-api", - "/pt/enterprise/3.0/graphql/overview/about-the-graphql-api": "/pt/enterprise-server@3.0/graphql/overview/about-the-graphql-api", - "/pt/enterprise/graphql/overview/about-the-graphql-api": "/pt/enterprise-server@latest/graphql/overview/about-the-graphql-api", - "/pt/enterprise/2.20/graphql/overview/about-the-graphql-api": "/pt/enterprise-server@2.20/graphql/overview/about-the-graphql-api", - "/pt/free-pro-team@latest/graphql/overview/breaking-changes": "/pt/graphql/overview/breaking-changes", - "/pt/v4/breaking_changes": "/pt/graphql/overview/breaking-changes", - "/pt/free-pro-team@latest/v4/breaking_changes": "/pt/graphql/overview/breaking-changes", - "/pt/enterprise/3.0/graphql/overview/breaking-changes": "/pt/enterprise-server@3.0/graphql/overview/breaking-changes", - "/pt/enterprise/graphql/overview/breaking-changes": "/pt/enterprise-server@latest/graphql/overview/breaking-changes", - "/pt/enterprise-server@3.0/v4/breaking_changes": "/pt/enterprise-server@3.0/graphql/overview/breaking-changes", - "/pt/enterprise/3.0/v4/breaking_changes": "/pt/enterprise-server@3.0/graphql/overview/breaking-changes", - "/pt/enterprise/v4/breaking_changes": "/pt/enterprise-server@latest/graphql/overview/breaking-changes", - "/pt/enterprise/2.20/graphql/overview/breaking-changes": "/pt/enterprise-server@2.20/graphql/overview/breaking-changes", - "/pt/enterprise-server@2.20/v4/breaking_changes": "/pt/enterprise-server@2.20/graphql/overview/breaking-changes", - "/pt/enterprise/2.20/v4/breaking_changes": "/pt/enterprise-server@2.20/graphql/overview/breaking-changes", - "/pt/github-ae@latest/v4/breaking_changes": "/pt/github-ae@latest/graphql/overview/breaking-changes", - "/pt/free-pro-team@latest/graphql/overview/changelog": "/pt/graphql/overview/changelog", - "/pt/v4/changelog": "/pt/graphql/overview/changelog", - "/pt/free-pro-team@latest/v4/changelog": "/pt/graphql/overview/changelog", - "/pt/enterprise/3.0/graphql/overview/changelog": "/pt/enterprise-server@3.0/graphql/overview/changelog", - "/pt/enterprise/graphql/overview/changelog": "/pt/enterprise-server@latest/graphql/overview/changelog", - "/pt/enterprise-server@3.0/v4/changelog": "/pt/enterprise-server@3.0/graphql/overview/changelog", - "/pt/enterprise/3.0/v4/changelog": "/pt/enterprise-server@3.0/graphql/overview/changelog", - "/pt/enterprise/v4/changelog": "/pt/enterprise-server@latest/graphql/overview/changelog", - "/pt/enterprise/2.20/graphql/overview/changelog": "/pt/enterprise-server@2.20/graphql/overview/changelog", - "/pt/enterprise-server@2.20/v4/changelog": "/pt/enterprise-server@2.20/graphql/overview/changelog", - "/pt/enterprise/2.20/v4/changelog": "/pt/enterprise-server@2.20/graphql/overview/changelog", - "/pt/github-ae@latest/v4/changelog": "/pt/github-ae@latest/graphql/overview/changelog", - "/pt/free-pro-team@latest/graphql/overview/explorer": "/pt/graphql/overview/explorer", - "/pt/v4/explorer": "/pt/graphql/overview/explorer", - "/pt/free-pro-team@latest/v4/explorer": "/pt/graphql/overview/explorer", - "/pt/v4/explorer-new": "/pt/graphql/overview/explorer", - "/pt/free-pro-team@latest/v4/explorer-new": "/pt/graphql/overview/explorer", - "/pt/enterprise/3.0/graphql/overview/explorer": "/pt/enterprise-server@3.0/graphql/overview/explorer", - "/pt/enterprise/graphql/overview/explorer": "/pt/enterprise-server@latest/graphql/overview/explorer", - "/pt/enterprise-server@3.0/v4/explorer": "/pt/enterprise-server@3.0/graphql/overview/explorer", - "/pt/enterprise/3.0/v4/explorer": "/pt/enterprise-server@3.0/graphql/overview/explorer", - "/pt/enterprise/v4/explorer": "/pt/enterprise-server@latest/graphql/overview/explorer", - "/pt/enterprise-server@3.0/v4/explorer-new": "/pt/enterprise-server@3.0/graphql/overview/explorer", - "/pt/enterprise/3.0/v4/explorer-new": "/pt/enterprise-server@3.0/graphql/overview/explorer", - "/pt/enterprise/v4/explorer-new": "/pt/enterprise-server@latest/graphql/overview/explorer", - "/pt/enterprise/2.20/graphql/overview/explorer": "/pt/enterprise-server@2.20/graphql/overview/explorer", - "/pt/enterprise-server@2.20/v4/explorer": "/pt/enterprise-server@2.20/graphql/overview/explorer", - "/pt/enterprise/2.20/v4/explorer": "/pt/enterprise-server@2.20/graphql/overview/explorer", - "/pt/enterprise-server@2.20/v4/explorer-new": "/pt/enterprise-server@2.20/graphql/overview/explorer", - "/pt/enterprise/2.20/v4/explorer-new": "/pt/enterprise-server@2.20/graphql/overview/explorer", - "/pt/github-ae@latest/v4/explorer": "/pt/github-ae@latest/graphql/overview/explorer", - "/pt/github-ae@latest/v4/explorer-new": "/pt/github-ae@latest/graphql/overview/explorer", - "/pt/free-pro-team@latest/graphql/overview": "/pt/graphql/overview", - "/pt/enterprise/3.0/graphql/overview": "/pt/enterprise-server@3.0/graphql/overview", - "/pt/enterprise/graphql/overview": "/pt/enterprise-server@latest/graphql/overview", - "/pt/enterprise/2.20/graphql/overview": "/pt/enterprise-server@2.20/graphql/overview", - "/pt/free-pro-team@latest/graphql/overview/public-schema": "/pt/graphql/overview/public-schema", - "/pt/v4/public_schema": "/pt/graphql/overview/public-schema", - "/pt/free-pro-team@latest/v4/public_schema": "/pt/graphql/overview/public-schema", - "/pt/enterprise/3.0/graphql/overview/public-schema": "/pt/enterprise-server@3.0/graphql/overview/public-schema", - "/pt/enterprise/graphql/overview/public-schema": "/pt/enterprise-server@latest/graphql/overview/public-schema", - "/pt/enterprise-server@3.0/v4/public_schema": "/pt/enterprise-server@3.0/graphql/overview/public-schema", - "/pt/enterprise/3.0/v4/public_schema": "/pt/enterprise-server@3.0/graphql/overview/public-schema", - "/pt/enterprise/v4/public_schema": "/pt/enterprise-server@latest/graphql/overview/public-schema", - "/pt/enterprise/2.20/graphql/overview/public-schema": "/pt/enterprise-server@2.20/graphql/overview/public-schema", - "/pt/enterprise-server@2.20/v4/public_schema": "/pt/enterprise-server@2.20/graphql/overview/public-schema", - "/pt/enterprise/2.20/v4/public_schema": "/pt/enterprise-server@2.20/graphql/overview/public-schema", - "/pt/github-ae@latest/v4/public_schema": "/pt/github-ae@latest/graphql/overview/public-schema", - "/pt/free-pro-team@latest/graphql/overview/resource-limitations": "/pt/graphql/overview/resource-limitations", - "/pt/v4/guides/resource-limitations": "/pt/graphql/overview/resource-limitations", - "/pt/free-pro-team@latest/v4/guides/resource-limitations": "/pt/graphql/overview/resource-limitations", - "/pt/enterprise/3.0/graphql/overview/resource-limitations": "/pt/enterprise-server@3.0/graphql/overview/resource-limitations", - "/pt/enterprise/graphql/overview/resource-limitations": "/pt/enterprise-server@latest/graphql/overview/resource-limitations", - "/pt/enterprise-server@3.0/v4/guides/resource-limitations": "/pt/enterprise-server@3.0/graphql/overview/resource-limitations", - "/pt/enterprise/3.0/v4/guides/resource-limitations": "/pt/enterprise-server@3.0/graphql/overview/resource-limitations", - "/pt/enterprise/v4/guides/resource-limitations": "/pt/enterprise-server@latest/graphql/overview/resource-limitations", - "/pt/enterprise/2.20/graphql/overview/resource-limitations": "/pt/enterprise-server@2.20/graphql/overview/resource-limitations", - "/pt/enterprise-server@2.20/v4/guides/resource-limitations": "/pt/enterprise-server@2.20/graphql/overview/resource-limitations", - "/pt/enterprise/2.20/v4/guides/resource-limitations": "/pt/enterprise-server@2.20/graphql/overview/resource-limitations", - "/pt/github-ae@latest/v4/guides/resource-limitations": "/pt/github-ae@latest/graphql/overview/resource-limitations", - "/pt/free-pro-team@latest/graphql/overview/schema-previews": "/pt/graphql/overview/schema-previews", - "/pt/v4/previews": "/pt/graphql/overview/schema-previews", - "/pt/free-pro-team@latest/v4/previews": "/pt/graphql/overview/schema-previews", - "/pt/enterprise/3.0/graphql/overview/schema-previews": "/pt/enterprise-server@3.0/graphql/overview/schema-previews", - "/pt/enterprise/graphql/overview/schema-previews": "/pt/enterprise-server@latest/graphql/overview/schema-previews", - "/pt/enterprise-server@3.0/v4/previews": "/pt/enterprise-server@3.0/graphql/overview/schema-previews", - "/pt/enterprise/3.0/v4/previews": "/pt/enterprise-server@3.0/graphql/overview/schema-previews", - "/pt/enterprise/v4/previews": "/pt/enterprise-server@latest/graphql/overview/schema-previews", - "/pt/enterprise/2.20/graphql/overview/schema-previews": "/pt/enterprise-server@2.20/graphql/overview/schema-previews", - "/pt/enterprise-server@2.20/v4/previews": "/pt/enterprise-server@2.20/graphql/overview/schema-previews", - "/pt/enterprise/2.20/v4/previews": "/pt/enterprise-server@2.20/graphql/overview/schema-previews", - "/pt/github-ae@latest/v4/previews": "/pt/github-ae@latest/graphql/overview/schema-previews", - "/pt/free-pro-team@latest/graphql/reference/enums": "/pt/graphql/reference/enums", - "/pt/v4/enum": "/pt/graphql/reference/enums", - "/pt/free-pro-team@latest/v4/enum": "/pt/graphql/reference/enums", - "/pt/v4/reference/enum": "/pt/graphql/reference/enums", - "/pt/free-pro-team@latest/v4/reference/enum": "/pt/graphql/reference/enums", - "/pt/enterprise/3.0/graphql/reference/enums": "/pt/enterprise-server@3.0/graphql/reference/enums", - "/pt/enterprise/graphql/reference/enums": "/pt/enterprise-server@latest/graphql/reference/enums", - "/pt/enterprise-server@3.0/v4/enum": "/pt/enterprise-server@3.0/graphql/reference/enums", - "/pt/enterprise/3.0/v4/enum": "/pt/enterprise-server@3.0/graphql/reference/enums", - "/pt/enterprise/v4/enum": "/pt/enterprise-server@latest/graphql/reference/enums", - "/pt/enterprise-server@3.0/v4/reference/enum": "/pt/enterprise-server@3.0/graphql/reference/enums", - "/pt/enterprise/3.0/v4/reference/enum": "/pt/enterprise-server@3.0/graphql/reference/enums", - "/pt/enterprise/v4/reference/enum": "/pt/enterprise-server@latest/graphql/reference/enums", - "/pt/enterprise/2.20/graphql/reference/enums": "/pt/enterprise-server@2.20/graphql/reference/enums", - "/pt/enterprise-server@2.20/v4/enum": "/pt/enterprise-server@2.20/graphql/reference/enums", - "/pt/enterprise/2.20/v4/enum": "/pt/enterprise-server@2.20/graphql/reference/enums", - "/pt/enterprise-server@2.20/v4/reference/enum": "/pt/enterprise-server@2.20/graphql/reference/enums", - "/pt/enterprise/2.20/v4/reference/enum": "/pt/enterprise-server@2.20/graphql/reference/enums", - "/pt/github-ae@latest/v4/enum": "/pt/github-ae@latest/graphql/reference/enums", - "/pt/github-ae@latest/v4/reference/enum": "/pt/github-ae@latest/graphql/reference/enums", - "/pt/free-pro-team@latest/graphql/reference": "/pt/graphql/reference", - "/pt/v4/reference": "/pt/graphql/reference", - "/pt/free-pro-team@latest/v4/reference": "/pt/graphql/reference", - "/pt/enterprise/3.0/graphql/reference": "/pt/enterprise-server@3.0/graphql/reference", - "/pt/enterprise/graphql/reference": "/pt/enterprise-server@latest/graphql/reference", - "/pt/enterprise-server@3.0/v4/reference": "/pt/enterprise-server@3.0/graphql/reference", - "/pt/enterprise/3.0/v4/reference": "/pt/enterprise-server@3.0/graphql/reference", - "/pt/enterprise/v4/reference": "/pt/enterprise-server@latest/graphql/reference", - "/pt/enterprise/2.20/graphql/reference": "/pt/enterprise-server@2.20/graphql/reference", - "/pt/enterprise-server@2.20/v4/reference": "/pt/enterprise-server@2.20/graphql/reference", - "/pt/enterprise/2.20/v4/reference": "/pt/enterprise-server@2.20/graphql/reference", - "/pt/github-ae@latest/v4/reference": "/pt/github-ae@latest/graphql/reference", - "/pt/free-pro-team@latest/graphql/reference/input-objects": "/pt/graphql/reference/input-objects", - "/pt/v4/input_object": "/pt/graphql/reference/input-objects", - "/pt/free-pro-team@latest/v4/input_object": "/pt/graphql/reference/input-objects", - "/pt/v4/reference/input_object": "/pt/graphql/reference/input-objects", - "/pt/free-pro-team@latest/v4/reference/input_object": "/pt/graphql/reference/input-objects", - "/pt/enterprise/3.0/graphql/reference/input-objects": "/pt/enterprise-server@3.0/graphql/reference/input-objects", - "/pt/enterprise/graphql/reference/input-objects": "/pt/enterprise-server@latest/graphql/reference/input-objects", - "/pt/enterprise-server@3.0/v4/input_object": "/pt/enterprise-server@3.0/graphql/reference/input-objects", - "/pt/enterprise/3.0/v4/input_object": "/pt/enterprise-server@3.0/graphql/reference/input-objects", - "/pt/enterprise/v4/input_object": "/pt/enterprise-server@latest/graphql/reference/input-objects", - "/pt/enterprise-server@3.0/v4/reference/input_object": "/pt/enterprise-server@3.0/graphql/reference/input-objects", - "/pt/enterprise/3.0/v4/reference/input_object": "/pt/enterprise-server@3.0/graphql/reference/input-objects", - "/pt/enterprise/v4/reference/input_object": "/pt/enterprise-server@latest/graphql/reference/input-objects", - "/pt/enterprise/2.20/graphql/reference/input-objects": "/pt/enterprise-server@2.20/graphql/reference/input-objects", - "/pt/enterprise-server@2.20/v4/input_object": "/pt/enterprise-server@2.20/graphql/reference/input-objects", - "/pt/enterprise/2.20/v4/input_object": "/pt/enterprise-server@2.20/graphql/reference/input-objects", - "/pt/enterprise-server@2.20/v4/reference/input_object": "/pt/enterprise-server@2.20/graphql/reference/input-objects", - "/pt/enterprise/2.20/v4/reference/input_object": "/pt/enterprise-server@2.20/graphql/reference/input-objects", - "/pt/github-ae@latest/v4/input_object": "/pt/github-ae@latest/graphql/reference/input-objects", - "/pt/github-ae@latest/v4/reference/input_object": "/pt/github-ae@latest/graphql/reference/input-objects", - "/pt/free-pro-team@latest/graphql/reference/interfaces": "/pt/graphql/reference/interfaces", - "/pt/v4/interface": "/pt/graphql/reference/interfaces", - "/pt/free-pro-team@latest/v4/interface": "/pt/graphql/reference/interfaces", - "/pt/v4/reference/interface": "/pt/graphql/reference/interfaces", - "/pt/free-pro-team@latest/v4/reference/interface": "/pt/graphql/reference/interfaces", - "/pt/enterprise/3.0/graphql/reference/interfaces": "/pt/enterprise-server@3.0/graphql/reference/interfaces", - "/pt/enterprise/graphql/reference/interfaces": "/pt/enterprise-server@latest/graphql/reference/interfaces", - "/pt/enterprise-server@3.0/v4/interface": "/pt/enterprise-server@3.0/graphql/reference/interfaces", - "/pt/enterprise/3.0/v4/interface": "/pt/enterprise-server@3.0/graphql/reference/interfaces", - "/pt/enterprise/v4/interface": "/pt/enterprise-server@latest/graphql/reference/interfaces", - "/pt/enterprise-server@3.0/v4/reference/interface": "/pt/enterprise-server@3.0/graphql/reference/interfaces", - "/pt/enterprise/3.0/v4/reference/interface": "/pt/enterprise-server@3.0/graphql/reference/interfaces", - "/pt/enterprise/v4/reference/interface": "/pt/enterprise-server@latest/graphql/reference/interfaces", - "/pt/enterprise/2.20/graphql/reference/interfaces": "/pt/enterprise-server@2.20/graphql/reference/interfaces", - "/pt/enterprise-server@2.20/v4/interface": "/pt/enterprise-server@2.20/graphql/reference/interfaces", - "/pt/enterprise/2.20/v4/interface": "/pt/enterprise-server@2.20/graphql/reference/interfaces", - "/pt/enterprise-server@2.20/v4/reference/interface": "/pt/enterprise-server@2.20/graphql/reference/interfaces", - "/pt/enterprise/2.20/v4/reference/interface": "/pt/enterprise-server@2.20/graphql/reference/interfaces", - "/pt/github-ae@latest/v4/interface": "/pt/github-ae@latest/graphql/reference/interfaces", - "/pt/github-ae@latest/v4/reference/interface": "/pt/github-ae@latest/graphql/reference/interfaces", - "/pt/free-pro-team@latest/graphql/reference/mutations": "/pt/graphql/reference/mutations", - "/pt/v4/mutation": "/pt/graphql/reference/mutations", - "/pt/free-pro-team@latest/v4/mutation": "/pt/graphql/reference/mutations", - "/pt/v4/reference/mutation": "/pt/graphql/reference/mutations", - "/pt/free-pro-team@latest/v4/reference/mutation": "/pt/graphql/reference/mutations", - "/pt/enterprise/3.0/graphql/reference/mutations": "/pt/enterprise-server@3.0/graphql/reference/mutations", - "/pt/enterprise/graphql/reference/mutations": "/pt/enterprise-server@latest/graphql/reference/mutations", - "/pt/enterprise-server@3.0/v4/mutation": "/pt/enterprise-server@3.0/graphql/reference/mutations", - "/pt/enterprise/3.0/v4/mutation": "/pt/enterprise-server@3.0/graphql/reference/mutations", - "/pt/enterprise/v4/mutation": "/pt/enterprise-server@latest/graphql/reference/mutations", - "/pt/enterprise-server@3.0/v4/reference/mutation": "/pt/enterprise-server@3.0/graphql/reference/mutations", - "/pt/enterprise/3.0/v4/reference/mutation": "/pt/enterprise-server@3.0/graphql/reference/mutations", - "/pt/enterprise/v4/reference/mutation": "/pt/enterprise-server@latest/graphql/reference/mutations", - "/pt/enterprise/2.20/graphql/reference/mutations": "/pt/enterprise-server@2.20/graphql/reference/mutations", - "/pt/enterprise-server@2.20/v4/mutation": "/pt/enterprise-server@2.20/graphql/reference/mutations", - "/pt/enterprise/2.20/v4/mutation": "/pt/enterprise-server@2.20/graphql/reference/mutations", - "/pt/enterprise-server@2.20/v4/reference/mutation": "/pt/enterprise-server@2.20/graphql/reference/mutations", - "/pt/enterprise/2.20/v4/reference/mutation": "/pt/enterprise-server@2.20/graphql/reference/mutations", - "/pt/github-ae@latest/v4/mutation": "/pt/github-ae@latest/graphql/reference/mutations", - "/pt/github-ae@latest/v4/reference/mutation": "/pt/github-ae@latest/graphql/reference/mutations", - "/pt/free-pro-team@latest/graphql/reference/objects": "/pt/graphql/reference/objects", - "/pt/v4/object": "/pt/graphql/reference/objects", - "/pt/free-pro-team@latest/v4/object": "/pt/graphql/reference/objects", - "/pt/v4/reference/object": "/pt/graphql/reference/objects", - "/pt/free-pro-team@latest/v4/reference/object": "/pt/graphql/reference/objects", - "/pt/enterprise/3.0/graphql/reference/objects": "/pt/enterprise-server@3.0/graphql/reference/objects", - "/pt/enterprise/graphql/reference/objects": "/pt/enterprise-server@latest/graphql/reference/objects", - "/pt/enterprise-server@3.0/v4/object": "/pt/enterprise-server@3.0/graphql/reference/objects", - "/pt/enterprise/3.0/v4/object": "/pt/enterprise-server@3.0/graphql/reference/objects", - "/pt/enterprise/v4/object": "/pt/enterprise-server@latest/graphql/reference/objects", - "/pt/enterprise-server@3.0/v4/reference/object": "/pt/enterprise-server@3.0/graphql/reference/objects", - "/pt/enterprise/3.0/v4/reference/object": "/pt/enterprise-server@3.0/graphql/reference/objects", - "/pt/enterprise/v4/reference/object": "/pt/enterprise-server@latest/graphql/reference/objects", - "/pt/enterprise/2.20/graphql/reference/objects": "/pt/enterprise-server@2.20/graphql/reference/objects", - "/pt/enterprise-server@2.20/v4/object": "/pt/enterprise-server@2.20/graphql/reference/objects", - "/pt/enterprise/2.20/v4/object": "/pt/enterprise-server@2.20/graphql/reference/objects", - "/pt/enterprise-server@2.20/v4/reference/object": "/pt/enterprise-server@2.20/graphql/reference/objects", - "/pt/enterprise/2.20/v4/reference/object": "/pt/enterprise-server@2.20/graphql/reference/objects", - "/pt/github-ae@latest/v4/object": "/pt/github-ae@latest/graphql/reference/objects", - "/pt/github-ae@latest/v4/reference/object": "/pt/github-ae@latest/graphql/reference/objects", - "/pt/free-pro-team@latest/graphql/reference/queries": "/pt/graphql/reference/queries", - "/pt/v4/query": "/pt/graphql/reference/queries", - "/pt/free-pro-team@latest/v4/query": "/pt/graphql/reference/queries", - "/pt/v4/reference/query": "/pt/graphql/reference/queries", - "/pt/free-pro-team@latest/v4/reference/query": "/pt/graphql/reference/queries", - "/pt/enterprise/3.0/graphql/reference/queries": "/pt/enterprise-server@3.0/graphql/reference/queries", - "/pt/enterprise/graphql/reference/queries": "/pt/enterprise-server@latest/graphql/reference/queries", - "/pt/enterprise-server@3.0/v4/query": "/pt/enterprise-server@3.0/graphql/reference/queries", - "/pt/enterprise/3.0/v4/query": "/pt/enterprise-server@3.0/graphql/reference/queries", - "/pt/enterprise/v4/query": "/pt/enterprise-server@latest/graphql/reference/queries", - "/pt/enterprise-server@3.0/v4/reference/query": "/pt/enterprise-server@3.0/graphql/reference/queries", - "/pt/enterprise/3.0/v4/reference/query": "/pt/enterprise-server@3.0/graphql/reference/queries", - "/pt/enterprise/v4/reference/query": "/pt/enterprise-server@latest/graphql/reference/queries", - "/pt/enterprise/2.20/graphql/reference/queries": "/pt/enterprise-server@2.20/graphql/reference/queries", - "/pt/enterprise-server@2.20/v4/query": "/pt/enterprise-server@2.20/graphql/reference/queries", - "/pt/enterprise/2.20/v4/query": "/pt/enterprise-server@2.20/graphql/reference/queries", - "/pt/enterprise-server@2.20/v4/reference/query": "/pt/enterprise-server@2.20/graphql/reference/queries", - "/pt/enterprise/2.20/v4/reference/query": "/pt/enterprise-server@2.20/graphql/reference/queries", - "/pt/github-ae@latest/v4/query": "/pt/github-ae@latest/graphql/reference/queries", - "/pt/github-ae@latest/v4/reference/query": "/pt/github-ae@latest/graphql/reference/queries", - "/pt/free-pro-team@latest/graphql/reference/scalars": "/pt/graphql/reference/scalars", - "/pt/v4/scalar": "/pt/graphql/reference/scalars", - "/pt/free-pro-team@latest/v4/scalar": "/pt/graphql/reference/scalars", - "/pt/v4/reference/scalar": "/pt/graphql/reference/scalars", - "/pt/free-pro-team@latest/v4/reference/scalar": "/pt/graphql/reference/scalars", - "/pt/enterprise/3.0/graphql/reference/scalars": "/pt/enterprise-server@3.0/graphql/reference/scalars", - "/pt/enterprise/graphql/reference/scalars": "/pt/enterprise-server@latest/graphql/reference/scalars", - "/pt/enterprise-server@3.0/v4/scalar": "/pt/enterprise-server@3.0/graphql/reference/scalars", - "/pt/enterprise/3.0/v4/scalar": "/pt/enterprise-server@3.0/graphql/reference/scalars", - "/pt/enterprise/v4/scalar": "/pt/enterprise-server@latest/graphql/reference/scalars", - "/pt/enterprise-server@3.0/v4/reference/scalar": "/pt/enterprise-server@3.0/graphql/reference/scalars", - "/pt/enterprise/3.0/v4/reference/scalar": "/pt/enterprise-server@3.0/graphql/reference/scalars", - "/pt/enterprise/v4/reference/scalar": "/pt/enterprise-server@latest/graphql/reference/scalars", - "/pt/enterprise/2.20/graphql/reference/scalars": "/pt/enterprise-server@2.20/graphql/reference/scalars", - "/pt/enterprise-server@2.20/v4/scalar": "/pt/enterprise-server@2.20/graphql/reference/scalars", - "/pt/enterprise/2.20/v4/scalar": "/pt/enterprise-server@2.20/graphql/reference/scalars", - "/pt/enterprise-server@2.20/v4/reference/scalar": "/pt/enterprise-server@2.20/graphql/reference/scalars", - "/pt/enterprise/2.20/v4/reference/scalar": "/pt/enterprise-server@2.20/graphql/reference/scalars", - "/pt/github-ae@latest/v4/scalar": "/pt/github-ae@latest/graphql/reference/scalars", - "/pt/github-ae@latest/v4/reference/scalar": "/pt/github-ae@latest/graphql/reference/scalars", - "/pt/free-pro-team@latest/graphql/reference/unions": "/pt/graphql/reference/unions", - "/pt/v4/union": "/pt/graphql/reference/unions", - "/pt/free-pro-team@latest/v4/union": "/pt/graphql/reference/unions", - "/pt/v4/reference/union": "/pt/graphql/reference/unions", - "/pt/free-pro-team@latest/v4/reference/union": "/pt/graphql/reference/unions", - "/pt/enterprise/3.0/graphql/reference/unions": "/pt/enterprise-server@3.0/graphql/reference/unions", - "/pt/enterprise/graphql/reference/unions": "/pt/enterprise-server@latest/graphql/reference/unions", - "/pt/enterprise-server@3.0/v4/union": "/pt/enterprise-server@3.0/graphql/reference/unions", - "/pt/enterprise/3.0/v4/union": "/pt/enterprise-server@3.0/graphql/reference/unions", - "/pt/enterprise/v4/union": "/pt/enterprise-server@latest/graphql/reference/unions", - "/pt/enterprise-server@3.0/v4/reference/union": "/pt/enterprise-server@3.0/graphql/reference/unions", - "/pt/enterprise/3.0/v4/reference/union": "/pt/enterprise-server@3.0/graphql/reference/unions", - "/pt/enterprise/v4/reference/union": "/pt/enterprise-server@latest/graphql/reference/unions", - "/pt/enterprise/2.20/graphql/reference/unions": "/pt/enterprise-server@2.20/graphql/reference/unions", - "/pt/enterprise-server@2.20/v4/union": "/pt/enterprise-server@2.20/graphql/reference/unions", - "/pt/enterprise/2.20/v4/union": "/pt/enterprise-server@2.20/graphql/reference/unions", - "/pt/enterprise-server@2.20/v4/reference/union": "/pt/enterprise-server@2.20/graphql/reference/unions", - "/pt/enterprise/2.20/v4/reference/union": "/pt/enterprise-server@2.20/graphql/reference/unions", - "/pt/github-ae@latest/v4/union": "/pt/github-ae@latest/graphql/reference/unions", - "/pt/github-ae@latest/v4/reference/union": "/pt/github-ae@latest/graphql/reference/unions", - "/pt/free-pro-team@latest/rest/guides/basics-of-authentication": "/pt/rest/guides/basics-of-authentication", - "/pt/v3/guides/basics-of-authentication": "/pt/rest/guides/basics-of-authentication", - "/pt/free-pro-team@latest/v3/guides/basics-of-authentication": "/pt/rest/guides/basics-of-authentication", - "/pt/rest/basics-of-authentication": "/pt/rest/guides/basics-of-authentication", - "/pt/free-pro-team@latest/rest/basics-of-authentication": "/pt/rest/guides/basics-of-authentication", - "/pt/enterprise/3.0/rest/guides/basics-of-authentication": "/pt/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/pt/enterprise/rest/guides/basics-of-authentication": "/pt/enterprise-server@latest/rest/guides/basics-of-authentication", - "/pt/enterprise-server@3.0/v3/guides/basics-of-authentication": "/pt/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/pt/enterprise/3.0/v3/guides/basics-of-authentication": "/pt/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/pt/enterprise/v3/guides/basics-of-authentication": "/pt/enterprise-server@latest/rest/guides/basics-of-authentication", - "/pt/enterprise-server@3.0/rest/basics-of-authentication": "/pt/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/pt/enterprise/3.0/rest/basics-of-authentication": "/pt/enterprise-server@3.0/rest/guides/basics-of-authentication", - "/pt/enterprise/rest/basics-of-authentication": "/pt/enterprise-server@latest/rest/guides/basics-of-authentication", - "/pt/enterprise/2.20/rest/guides/basics-of-authentication": "/pt/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/pt/enterprise-server@2.20/v3/guides/basics-of-authentication": "/pt/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/pt/enterprise/2.20/v3/guides/basics-of-authentication": "/pt/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/pt/enterprise-server@2.20/rest/basics-of-authentication": "/pt/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/pt/enterprise/2.20/rest/basics-of-authentication": "/pt/enterprise-server@2.20/rest/guides/basics-of-authentication", - "/pt/github-ae@latest/v3/guides/basics-of-authentication": "/pt/github-ae@latest/rest/guides/basics-of-authentication", - "/pt/github-ae@latest/rest/basics-of-authentication": "/pt/github-ae@latest/rest/guides/basics-of-authentication", - "/pt/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/pt/rest/guides/best-practices-for-integrators", - "/pt/v3/guides/best-practices-for-integrators": "/pt/rest/guides/best-practices-for-integrators", - "/pt/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/pt/rest/guides/best-practices-for-integrators", - "/pt/enterprise/3.0/rest/guides/best-practices-for-integrators": "/pt/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/pt/enterprise/rest/guides/best-practices-for-integrators": "/pt/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/pt/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/pt/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/pt/enterprise/3.0/v3/guides/best-practices-for-integrators": "/pt/enterprise-server@3.0/rest/guides/best-practices-for-integrators", - "/pt/enterprise/v3/guides/best-practices-for-integrators": "/pt/enterprise-server@latest/rest/guides/best-practices-for-integrators", - "/pt/enterprise/2.20/rest/guides/best-practices-for-integrators": "/pt/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/pt/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/pt/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/pt/enterprise/2.20/v3/guides/best-practices-for-integrators": "/pt/enterprise-server@2.20/rest/guides/best-practices-for-integrators", - "/pt/github-ae@latest/v3/guides/best-practices-for-integrators": "/pt/github-ae@latest/rest/guides/best-practices-for-integrators", - "/pt/free-pro-team@latest/rest/guides/building-a-ci-server": "/pt/rest/guides/building-a-ci-server", - "/pt/v3/guides/building-a-ci-server": "/pt/rest/guides/building-a-ci-server", - "/pt/free-pro-team@latest/v3/guides/building-a-ci-server": "/pt/rest/guides/building-a-ci-server", - "/pt/enterprise/3.0/rest/guides/building-a-ci-server": "/pt/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/pt/enterprise/rest/guides/building-a-ci-server": "/pt/enterprise-server@latest/rest/guides/building-a-ci-server", - "/pt/enterprise-server@3.0/v3/guides/building-a-ci-server": "/pt/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/pt/enterprise/3.0/v3/guides/building-a-ci-server": "/pt/enterprise-server@3.0/rest/guides/building-a-ci-server", - "/pt/enterprise/v3/guides/building-a-ci-server": "/pt/enterprise-server@latest/rest/guides/building-a-ci-server", - "/pt/enterprise/2.20/rest/guides/building-a-ci-server": "/pt/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/pt/enterprise-server@2.20/v3/guides/building-a-ci-server": "/pt/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/pt/enterprise/2.20/v3/guides/building-a-ci-server": "/pt/enterprise-server@2.20/rest/guides/building-a-ci-server", - "/pt/github-ae@latest/v3/guides/building-a-ci-server": "/pt/github-ae@latest/rest/guides/building-a-ci-server", - "/pt/free-pro-team@latest/rest/guides/delivering-deployments": "/pt/rest/guides/delivering-deployments", - "/pt/v3/guides/delivering-deployments": "/pt/rest/guides/delivering-deployments", - "/pt/free-pro-team@latest/v3/guides/delivering-deployments": "/pt/rest/guides/delivering-deployments", - "/pt/enterprise/3.0/rest/guides/delivering-deployments": "/pt/enterprise-server@3.0/rest/guides/delivering-deployments", - "/pt/enterprise/rest/guides/delivering-deployments": "/pt/enterprise-server@latest/rest/guides/delivering-deployments", - "/pt/enterprise-server@3.0/v3/guides/delivering-deployments": "/pt/enterprise-server@3.0/rest/guides/delivering-deployments", - "/pt/enterprise/3.0/v3/guides/delivering-deployments": "/pt/enterprise-server@3.0/rest/guides/delivering-deployments", - "/pt/enterprise/v3/guides/delivering-deployments": "/pt/enterprise-server@latest/rest/guides/delivering-deployments", - "/pt/enterprise/2.20/rest/guides/delivering-deployments": "/pt/enterprise-server@2.20/rest/guides/delivering-deployments", - "/pt/enterprise-server@2.20/v3/guides/delivering-deployments": "/pt/enterprise-server@2.20/rest/guides/delivering-deployments", - "/pt/enterprise/2.20/v3/guides/delivering-deployments": "/pt/enterprise-server@2.20/rest/guides/delivering-deployments", - "/pt/github-ae@latest/v3/guides/delivering-deployments": "/pt/github-ae@latest/rest/guides/delivering-deployments", - "/pt/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/pt/rest/guides/discovering-resources-for-a-user", - "/pt/v3/guides/discovering-resources-for-a-user": "/pt/rest/guides/discovering-resources-for-a-user", - "/pt/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/pt/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/pt/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise/rest/guides/discovering-resources-for-a-user": "/pt/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/pt/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/pt/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise/v3/guides/discovering-resources-for-a-user": "/pt/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/pt/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/pt/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/pt/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/pt/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", - "/pt/github-ae@latest/v3/guides/discovering-resources-for-a-user": "/pt/github-ae@latest/rest/guides/discovering-resources-for-a-user", - "/pt/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/pt/rest/guides/getting-started-with-the-checks-api", - "/pt/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/pt/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", - "/pt/enterprise/rest/guides/getting-started-with-the-checks-api": "/pt/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", - "/pt/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/pt/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", - "/pt/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/pt/rest/guides/getting-started-with-the-git-database-api", - "/pt/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/pt/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", - "/pt/enterprise/rest/guides/getting-started-with-the-git-database-api": "/pt/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", - "/pt/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/pt/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", - "/pt/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/pt/rest/guides/getting-started-with-the-rest-api", - "/pt/v3/guides/getting-started": "/pt/rest/guides/getting-started-with-the-rest-api", - "/pt/free-pro-team@latest/v3/guides/getting-started": "/pt/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/pt/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise/rest/guides/getting-started-with-the-rest-api": "/pt/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise-server@3.0/v3/guides/getting-started": "/pt/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise/3.0/v3/guides/getting-started": "/pt/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise/v3/guides/getting-started": "/pt/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/pt/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise-server@2.20/v3/guides/getting-started": "/pt/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/pt/enterprise/2.20/v3/guides/getting-started": "/pt/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", - "/pt/github-ae@latest/v3/guides/getting-started": "/pt/github-ae@latest/rest/guides/getting-started-with-the-rest-api", - "/pt/free-pro-team@latest/rest/guides": "/pt/rest/guides", - "/pt/v3/guides": "/pt/rest/guides", - "/pt/free-pro-team@latest/v3/guides": "/pt/rest/guides", - "/pt/enterprise/3.0/rest/guides": "/pt/enterprise-server@3.0/rest/guides", - "/pt/enterprise/rest/guides": "/pt/enterprise-server@latest/rest/guides", - "/pt/enterprise-server@3.0/v3/guides": "/pt/enterprise-server@3.0/rest/guides", - "/pt/enterprise/3.0/v3/guides": "/pt/enterprise-server@3.0/rest/guides", - "/pt/enterprise/v3/guides": "/pt/enterprise-server@latest/rest/guides", - "/pt/enterprise/2.20/rest/guides": "/pt/enterprise-server@2.20/rest/guides", - "/pt/enterprise-server@2.20/v3/guides": "/pt/enterprise-server@2.20/rest/guides", - "/pt/enterprise/2.20/v3/guides": "/pt/enterprise-server@2.20/rest/guides", - "/pt/github-ae@latest/v3/guides": "/pt/github-ae@latest/rest/guides", - "/pt/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/pt/rest/guides/rendering-data-as-graphs", - "/pt/v3/guides/rendering-data-as-graphs": "/pt/rest/guides/rendering-data-as-graphs", - "/pt/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/pt/rest/guides/rendering-data-as-graphs", - "/pt/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/pt/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/pt/enterprise/rest/guides/rendering-data-as-graphs": "/pt/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/pt/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/pt/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/pt/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/pt/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", - "/pt/enterprise/v3/guides/rendering-data-as-graphs": "/pt/enterprise-server@latest/rest/guides/rendering-data-as-graphs", - "/pt/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/pt/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/pt/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/pt/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/pt/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/pt/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", - "/pt/github-ae@latest/v3/guides/rendering-data-as-graphs": "/pt/github-ae@latest/rest/guides/rendering-data-as-graphs", - "/pt/free-pro-team@latest/rest/guides/traversing-with-pagination": "/pt/rest/guides/traversing-with-pagination", - "/pt/v3/guides/traversing-with-pagination": "/pt/rest/guides/traversing-with-pagination", - "/pt/free-pro-team@latest/v3/guides/traversing-with-pagination": "/pt/rest/guides/traversing-with-pagination", - "/pt/enterprise/3.0/rest/guides/traversing-with-pagination": "/pt/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/pt/enterprise/rest/guides/traversing-with-pagination": "/pt/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/pt/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/pt/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/pt/enterprise/3.0/v3/guides/traversing-with-pagination": "/pt/enterprise-server@3.0/rest/guides/traversing-with-pagination", - "/pt/enterprise/v3/guides/traversing-with-pagination": "/pt/enterprise-server@latest/rest/guides/traversing-with-pagination", - "/pt/enterprise/2.20/rest/guides/traversing-with-pagination": "/pt/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/pt/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/pt/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/pt/enterprise/2.20/v3/guides/traversing-with-pagination": "/pt/enterprise-server@2.20/rest/guides/traversing-with-pagination", - "/pt/github-ae@latest/v3/guides/traversing-with-pagination": "/pt/github-ae@latest/rest/guides/traversing-with-pagination", - "/pt/free-pro-team@latest/rest/guides/working-with-comments": "/pt/rest/guides/working-with-comments", - "/pt/v3/guides/working-with-comments": "/pt/rest/guides/working-with-comments", - "/pt/free-pro-team@latest/v3/guides/working-with-comments": "/pt/rest/guides/working-with-comments", - "/pt/enterprise/3.0/rest/guides/working-with-comments": "/pt/enterprise-server@3.0/rest/guides/working-with-comments", - "/pt/enterprise/rest/guides/working-with-comments": "/pt/enterprise-server@latest/rest/guides/working-with-comments", - "/pt/enterprise-server@3.0/v3/guides/working-with-comments": "/pt/enterprise-server@3.0/rest/guides/working-with-comments", - "/pt/enterprise/3.0/v3/guides/working-with-comments": "/pt/enterprise-server@3.0/rest/guides/working-with-comments", - "/pt/enterprise/v3/guides/working-with-comments": "/pt/enterprise-server@latest/rest/guides/working-with-comments", - "/pt/enterprise/2.20/rest/guides/working-with-comments": "/pt/enterprise-server@2.20/rest/guides/working-with-comments", - "/pt/enterprise-server@2.20/v3/guides/working-with-comments": "/pt/enterprise-server@2.20/rest/guides/working-with-comments", - "/pt/enterprise/2.20/v3/guides/working-with-comments": "/pt/enterprise-server@2.20/rest/guides/working-with-comments", - "/pt/github-ae@latest/v3/guides/working-with-comments": "/pt/github-ae@latest/rest/guides/working-with-comments", - "/pt/free-pro-team@latest/rest": "/pt/rest", - "/pt/v3": "/pt/rest", - "/pt/free-pro-team@latest/v3": "/pt/rest", - "/pt/enterprise/3.0/rest": "/pt/enterprise-server@3.0/rest", - "/pt/enterprise/rest": "/pt/enterprise-server@latest/rest", - "/pt/enterprise-server@3.0/v3": "/pt/enterprise-server@3.0/rest", - "/pt/enterprise/3.0/v3": "/pt/enterprise-server@3.0/rest", - "/pt/enterprise/v3": "/pt/enterprise-server@latest/rest", - "/pt/enterprise/2.20/rest": "/pt/enterprise-server@2.20/rest", - "/pt/enterprise-server@2.20/v3": "/pt/enterprise-server@2.20/rest", - "/pt/enterprise/2.20/v3": "/pt/enterprise-server@2.20/rest", - "/pt/github-ae@latest/v3": "/pt/github-ae@latest/rest", - "/pt/free-pro-team@latest/rest/overview/api-previews": "/pt/rest/overview/api-previews", - "/pt/v3/previews": "/pt/rest/overview/api-previews", - "/pt/free-pro-team@latest/v3/previews": "/pt/rest/overview/api-previews", - "/pt/enterprise/3.0/rest/overview/api-previews": "/pt/enterprise-server@3.0/rest/overview/api-previews", - "/pt/enterprise/rest/overview/api-previews": "/pt/enterprise-server@latest/rest/overview/api-previews", - "/pt/enterprise-server@3.0/v3/previews": "/pt/enterprise-server@3.0/rest/overview/api-previews", - "/pt/enterprise/3.0/v3/previews": "/pt/enterprise-server@3.0/rest/overview/api-previews", - "/pt/enterprise/v3/previews": "/pt/enterprise-server@latest/rest/overview/api-previews", - "/pt/enterprise/2.20/rest/overview/api-previews": "/pt/enterprise-server@2.20/rest/overview/api-previews", - "/pt/enterprise-server@2.20/v3/previews": "/pt/enterprise-server@2.20/rest/overview/api-previews", - "/pt/enterprise/2.20/v3/previews": "/pt/enterprise-server@2.20/rest/overview/api-previews", - "/pt/github-ae@latest/v3/previews": "/pt/github-ae@latest/rest/overview/api-previews", - "/pt/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/pt/rest/overview/endpoints-available-for-github-apps", - "/pt/v3/apps/available-endpoints": "/pt/rest/overview/endpoints-available-for-github-apps", - "/pt/free-pro-team@latest/v3/apps/available-endpoints": "/pt/rest/overview/endpoints-available-for-github-apps", - "/pt/rest/reference/endpoints-available-for-github-apps": "/pt/rest/overview/endpoints-available-for-github-apps", - "/pt/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/pt/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/pt/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/rest/overview/endpoints-available-for-github-apps": "/pt/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise-server@3.0/v3/apps/available-endpoints": "/pt/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/3.0/v3/apps/available-endpoints": "/pt/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/v3/apps/available-endpoints": "/pt/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/pt/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/pt/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/rest/reference/endpoints-available-for-github-apps": "/pt/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/pt/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise-server@2.20/v3/apps/available-endpoints": "/pt/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/2.20/v3/apps/available-endpoints": "/pt/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/pt/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/pt/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/pt/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", - "/pt/github-ae@latest/v3/apps/available-endpoints": "/pt/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/pt/github-ae@latest/rest/reference/endpoints-available-for-github-apps": "/pt/github-ae@latest/rest/overview/endpoints-available-for-github-apps", - "/pt/free-pro-team@latest/rest/overview": "/pt/rest/overview", - "/pt/enterprise/3.0/rest/overview": "/pt/enterprise-server@3.0/rest/overview", - "/pt/enterprise/rest/overview": "/pt/enterprise-server@latest/rest/overview", - "/pt/enterprise/2.20/rest/overview": "/pt/enterprise-server@2.20/rest/overview", - "/pt/free-pro-team@latest/rest/overview/libraries": "/pt/rest/overview/libraries", - "/pt/v3/libraries": "/pt/rest/overview/libraries", - "/pt/free-pro-team@latest/v3/libraries": "/pt/rest/overview/libraries", - "/pt/enterprise/3.0/rest/overview/libraries": "/pt/enterprise-server@3.0/rest/overview/libraries", - "/pt/enterprise/rest/overview/libraries": "/pt/enterprise-server@latest/rest/overview/libraries", - "/pt/enterprise-server@3.0/v3/libraries": "/pt/enterprise-server@3.0/rest/overview/libraries", - "/pt/enterprise/3.0/v3/libraries": "/pt/enterprise-server@3.0/rest/overview/libraries", - "/pt/enterprise/v3/libraries": "/pt/enterprise-server@latest/rest/overview/libraries", - "/pt/enterprise/2.20/rest/overview/libraries": "/pt/enterprise-server@2.20/rest/overview/libraries", - "/pt/enterprise-server@2.20/v3/libraries": "/pt/enterprise-server@2.20/rest/overview/libraries", - "/pt/enterprise/2.20/v3/libraries": "/pt/enterprise-server@2.20/rest/overview/libraries", - "/pt/github-ae@latest/v3/libraries": "/pt/github-ae@latest/rest/overview/libraries", - "/pt/free-pro-team@latest/rest/overview/media-types": "/pt/rest/overview/media-types", - "/pt/v3/media": "/pt/rest/overview/media-types", - "/pt/free-pro-team@latest/v3/media": "/pt/rest/overview/media-types", - "/pt/enterprise/3.0/rest/overview/media-types": "/pt/enterprise-server@3.0/rest/overview/media-types", - "/pt/enterprise/rest/overview/media-types": "/pt/enterprise-server@latest/rest/overview/media-types", - "/pt/enterprise-server@3.0/v3/media": "/pt/enterprise-server@3.0/rest/overview/media-types", - "/pt/enterprise/3.0/v3/media": "/pt/enterprise-server@3.0/rest/overview/media-types", - "/pt/enterprise/v3/media": "/pt/enterprise-server@latest/rest/overview/media-types", - "/pt/enterprise/2.20/rest/overview/media-types": "/pt/enterprise-server@2.20/rest/overview/media-types", - "/pt/enterprise-server@2.20/v3/media": "/pt/enterprise-server@2.20/rest/overview/media-types", - "/pt/enterprise/2.20/v3/media": "/pt/enterprise-server@2.20/rest/overview/media-types", - "/pt/github-ae@latest/v3/media": "/pt/github-ae@latest/rest/overview/media-types", - "/pt/free-pro-team@latest/rest/overview/openapi-description": "/pt/rest/overview/openapi-description", - "/pt/enterprise/3.0/rest/overview/openapi-description": "/pt/enterprise-server@3.0/rest/overview/openapi-description", - "/pt/enterprise/rest/overview/openapi-description": "/pt/enterprise-server@latest/rest/overview/openapi-description", - "/pt/enterprise/2.20/rest/overview/openapi-description": "/pt/enterprise-server@2.20/rest/overview/openapi-description", - "/pt/free-pro-team@latest/rest/overview/other-authentication-methods": "/pt/rest/overview/other-authentication-methods", - "/pt/v3/auth": "/pt/rest/overview/other-authentication-methods", - "/pt/free-pro-team@latest/v3/auth": "/pt/rest/overview/other-authentication-methods", - "/pt/enterprise/3.0/rest/overview/other-authentication-methods": "/pt/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/pt/enterprise/rest/overview/other-authentication-methods": "/pt/enterprise-server@latest/rest/overview/other-authentication-methods", - "/pt/enterprise-server@3.0/v3/auth": "/pt/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/pt/enterprise/3.0/v3/auth": "/pt/enterprise-server@3.0/rest/overview/other-authentication-methods", - "/pt/enterprise/v3/auth": "/pt/enterprise-server@latest/rest/overview/other-authentication-methods", - "/pt/enterprise/2.20/rest/overview/other-authentication-methods": "/pt/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/pt/enterprise-server@2.20/v3/auth": "/pt/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/pt/enterprise/2.20/v3/auth": "/pt/enterprise-server@2.20/rest/overview/other-authentication-methods", - "/pt/github-ae@latest/v3/auth": "/pt/github-ae@latest/rest/overview/other-authentication-methods", - "/pt/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/pt/rest/overview/resources-in-the-rest-api", - "/pt/rest/initialize-the-repo": "/pt/rest/overview/resources-in-the-rest-api", - "/pt/free-pro-team@latest/rest/initialize-the-repo": "/pt/rest/overview/resources-in-the-rest-api", - "/pt/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/pt/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/pt/enterprise/rest/overview/resources-in-the-rest-api": "/pt/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/pt/enterprise-server@3.0/rest/initialize-the-repo": "/pt/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/pt/enterprise/3.0/rest/initialize-the-repo": "/pt/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", - "/pt/enterprise/rest/initialize-the-repo": "/pt/enterprise-server@latest/rest/overview/resources-in-the-rest-api", - "/pt/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/pt/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/pt/enterprise-server@2.20/rest/initialize-the-repo": "/pt/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/pt/enterprise/2.20/rest/initialize-the-repo": "/pt/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", - "/pt/github-ae@latest/rest/initialize-the-repo": "/pt/github-ae@latest/rest/overview/resources-in-the-rest-api", - "/pt/free-pro-team@latest/rest/overview/troubleshooting": "/pt/rest/overview/troubleshooting", - "/pt/v3/troubleshooting": "/pt/rest/overview/troubleshooting", - "/pt/free-pro-team@latest/v3/troubleshooting": "/pt/rest/overview/troubleshooting", - "/pt/enterprise/3.0/rest/overview/troubleshooting": "/pt/enterprise-server@3.0/rest/overview/troubleshooting", - "/pt/enterprise/rest/overview/troubleshooting": "/pt/enterprise-server@latest/rest/overview/troubleshooting", - "/pt/enterprise-server@3.0/v3/troubleshooting": "/pt/enterprise-server@3.0/rest/overview/troubleshooting", - "/pt/enterprise/3.0/v3/troubleshooting": "/pt/enterprise-server@3.0/rest/overview/troubleshooting", - "/pt/enterprise/v3/troubleshooting": "/pt/enterprise-server@latest/rest/overview/troubleshooting", - "/pt/enterprise/2.20/rest/overview/troubleshooting": "/pt/enterprise-server@2.20/rest/overview/troubleshooting", - "/pt/enterprise-server@2.20/v3/troubleshooting": "/pt/enterprise-server@2.20/rest/overview/troubleshooting", - "/pt/enterprise/2.20/v3/troubleshooting": "/pt/enterprise-server@2.20/rest/overview/troubleshooting", - "/pt/github-ae@latest/v3/troubleshooting": "/pt/github-ae@latest/rest/overview/troubleshooting", - "/pt/free-pro-team@latest/rest/reference/actions": "/pt/rest/reference/actions", - "/pt/v3/actions": "/pt/rest/reference/actions", - "/pt/free-pro-team@latest/v3/actions": "/pt/rest/reference/actions", - "/pt/enterprise/3.0/rest/reference/actions": "/pt/enterprise-server@3.0/rest/reference/actions", - "/pt/enterprise/rest/reference/actions": "/pt/enterprise-server@latest/rest/reference/actions", - "/pt/enterprise-server@3.0/v3/actions": "/pt/enterprise-server@3.0/rest/reference/actions", - "/pt/enterprise/3.0/v3/actions": "/pt/enterprise-server@3.0/rest/reference/actions", - "/pt/enterprise/v3/actions": "/pt/enterprise-server@latest/rest/reference/actions", - "/pt/free-pro-team@latest/rest/reference/activity": "/pt/rest/reference/activity", - "/pt/v3/activity": "/pt/rest/reference/activity", - "/pt/free-pro-team@latest/v3/activity": "/pt/rest/reference/activity", - "/pt/enterprise/3.0/rest/reference/activity": "/pt/enterprise-server@3.0/rest/reference/activity", - "/pt/enterprise/rest/reference/activity": "/pt/enterprise-server@latest/rest/reference/activity", - "/pt/enterprise-server@3.0/v3/activity": "/pt/enterprise-server@3.0/rest/reference/activity", - "/pt/enterprise/3.0/v3/activity": "/pt/enterprise-server@3.0/rest/reference/activity", - "/pt/enterprise/v3/activity": "/pt/enterprise-server@latest/rest/reference/activity", - "/pt/enterprise/2.20/rest/reference/activity": "/pt/enterprise-server@2.20/rest/reference/activity", - "/pt/enterprise-server@2.20/v3/activity": "/pt/enterprise-server@2.20/rest/reference/activity", - "/pt/enterprise/2.20/v3/activity": "/pt/enterprise-server@2.20/rest/reference/activity", - "/pt/github-ae@latest/v3/activity": "/pt/github-ae@latest/rest/reference/activity", - "/pt/free-pro-team@latest/rest/reference/apps": "/pt/rest/reference/apps", - "/pt/v3/apps": "/pt/rest/reference/apps", - "/pt/free-pro-team@latest/v3/apps": "/pt/rest/reference/apps", - "/pt/enterprise/3.0/rest/reference/apps": "/pt/enterprise-server@3.0/rest/reference/apps", - "/pt/enterprise/rest/reference/apps": "/pt/enterprise-server@latest/rest/reference/apps", - "/pt/enterprise-server@3.0/v3/apps": "/pt/enterprise-server@3.0/rest/reference/apps", - "/pt/enterprise/3.0/v3/apps": "/pt/enterprise-server@3.0/rest/reference/apps", - "/pt/enterprise/v3/apps": "/pt/enterprise-server@latest/rest/reference/apps", - "/pt/enterprise/2.20/rest/reference/apps": "/pt/enterprise-server@2.20/rest/reference/apps", - "/pt/enterprise-server@2.20/v3/apps": "/pt/enterprise-server@2.20/rest/reference/apps", - "/pt/enterprise/2.20/v3/apps": "/pt/enterprise-server@2.20/rest/reference/apps", - "/pt/github-ae@latest/v3/apps": "/pt/github-ae@latest/rest/reference/apps", - "/pt/free-pro-team@latest/rest/reference/billing": "/pt/rest/reference/billing", - "/pt/free-pro-team@latest/rest/reference/checks": "/pt/rest/reference/checks", - "/pt/v3/checks": "/pt/rest/reference/checks", - "/pt/free-pro-team@latest/v3/checks": "/pt/rest/reference/checks", - "/pt/enterprise/3.0/rest/reference/checks": "/pt/enterprise-server@3.0/rest/reference/checks", - "/pt/enterprise/rest/reference/checks": "/pt/enterprise-server@latest/rest/reference/checks", - "/pt/enterprise-server@3.0/v3/checks": "/pt/enterprise-server@3.0/rest/reference/checks", - "/pt/enterprise/3.0/v3/checks": "/pt/enterprise-server@3.0/rest/reference/checks", - "/pt/enterprise/v3/checks": "/pt/enterprise-server@latest/rest/reference/checks", - "/pt/enterprise/2.20/rest/reference/checks": "/pt/enterprise-server@2.20/rest/reference/checks", - "/pt/enterprise-server@2.20/v3/checks": "/pt/enterprise-server@2.20/rest/reference/checks", - "/pt/enterprise/2.20/v3/checks": "/pt/enterprise-server@2.20/rest/reference/checks", - "/pt/github-ae@latest/v3/checks": "/pt/github-ae@latest/rest/reference/checks", - "/pt/free-pro-team@latest/rest/reference/code-scanning": "/pt/rest/reference/code-scanning", - "/pt/v3/code-scanning": "/pt/rest/reference/code-scanning", - "/pt/free-pro-team@latest/v3/code-scanning": "/pt/rest/reference/code-scanning", - "/pt/enterprise/3.0/rest/reference/code-scanning": "/pt/enterprise-server@3.0/rest/reference/code-scanning", - "/pt/enterprise/rest/reference/code-scanning": "/pt/enterprise-server@latest/rest/reference/code-scanning", - "/pt/enterprise-server@3.0/v3/code-scanning": "/pt/enterprise-server@3.0/rest/reference/code-scanning", - "/pt/enterprise/3.0/v3/code-scanning": "/pt/enterprise-server@3.0/rest/reference/code-scanning", - "/pt/enterprise/v3/code-scanning": "/pt/enterprise-server@latest/rest/reference/code-scanning", - "/pt/free-pro-team@latest/rest/reference/codes-of-conduct": "/pt/rest/reference/codes-of-conduct", - "/pt/v3/codes_of_conduct": "/pt/rest/reference/codes-of-conduct", - "/pt/free-pro-team@latest/v3/codes_of_conduct": "/pt/rest/reference/codes-of-conduct", - "/pt/v3/codes-of-conduct": "/pt/rest/reference/codes-of-conduct", - "/pt/free-pro-team@latest/v3/codes-of-conduct": "/pt/rest/reference/codes-of-conduct", - "/pt/enterprise/3.0/rest/reference/codes-of-conduct": "/pt/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/pt/enterprise/rest/reference/codes-of-conduct": "/pt/enterprise-server@latest/rest/reference/codes-of-conduct", - "/pt/enterprise-server@3.0/v3/codes_of_conduct": "/pt/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/pt/enterprise/3.0/v3/codes_of_conduct": "/pt/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/pt/enterprise/v3/codes_of_conduct": "/pt/enterprise-server@latest/rest/reference/codes-of-conduct", - "/pt/enterprise-server@3.0/v3/codes-of-conduct": "/pt/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/pt/enterprise/3.0/v3/codes-of-conduct": "/pt/enterprise-server@3.0/rest/reference/codes-of-conduct", - "/pt/enterprise/v3/codes-of-conduct": "/pt/enterprise-server@latest/rest/reference/codes-of-conduct", - "/pt/enterprise/2.20/rest/reference/codes-of-conduct": "/pt/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/pt/enterprise-server@2.20/v3/codes_of_conduct": "/pt/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/pt/enterprise/2.20/v3/codes_of_conduct": "/pt/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/pt/enterprise-server@2.20/v3/codes-of-conduct": "/pt/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/pt/enterprise/2.20/v3/codes-of-conduct": "/pt/enterprise-server@2.20/rest/reference/codes-of-conduct", - "/pt/github-ae@latest/v3/codes_of_conduct": "/pt/github-ae@latest/rest/reference/codes-of-conduct", - "/pt/github-ae@latest/v3/codes-of-conduct": "/pt/github-ae@latest/rest/reference/codes-of-conduct", - "/pt/free-pro-team@latest/rest/reference/emojis": "/pt/rest/reference/emojis", - "/pt/v3/emojis": "/pt/rest/reference/emojis", - "/pt/free-pro-team@latest/v3/emojis": "/pt/rest/reference/emojis", - "/pt/v3/misc": "/pt/rest/reference/emojis", - "/pt/free-pro-team@latest/v3/misc": "/pt/rest/reference/emojis", - "/pt/enterprise/3.0/rest/reference/emojis": "/pt/enterprise-server@3.0/rest/reference/emojis", - "/pt/enterprise/rest/reference/emojis": "/pt/enterprise-server@latest/rest/reference/emojis", - "/pt/enterprise-server@3.0/v3/emojis": "/pt/enterprise-server@3.0/rest/reference/emojis", - "/pt/enterprise/3.0/v3/emojis": "/pt/enterprise-server@3.0/rest/reference/emojis", - "/pt/enterprise/v3/emojis": "/pt/enterprise-server@latest/rest/reference/emojis", - "/pt/enterprise-server@3.0/v3/misc": "/pt/enterprise-server@3.0/rest/reference/emojis", - "/pt/enterprise/3.0/v3/misc": "/pt/enterprise-server@3.0/rest/reference/emojis", - "/pt/enterprise/v3/misc": "/pt/enterprise-server@latest/rest/reference/emojis", - "/pt/enterprise/2.20/rest/reference/emojis": "/pt/enterprise-server@2.20/rest/reference/emojis", - "/pt/enterprise-server@2.20/v3/emojis": "/pt/enterprise-server@2.20/rest/reference/emojis", - "/pt/enterprise/2.20/v3/emojis": "/pt/enterprise-server@2.20/rest/reference/emojis", - "/pt/enterprise-server@2.20/v3/misc": "/pt/enterprise-server@2.20/rest/reference/emojis", - "/pt/enterprise/2.20/v3/misc": "/pt/enterprise-server@2.20/rest/reference/emojis", - "/pt/github-ae@latest/v3/emojis": "/pt/github-ae@latest/rest/reference/emojis", - "/pt/github-ae@latest/v3/misc": "/pt/github-ae@latest/rest/reference/emojis", - "/pt/free-pro-team@latest/rest/reference/enterprise-admin": "/pt/rest/reference/enterprise-admin", - "/pt/v3/enterprise-admin": "/pt/rest/reference/enterprise-admin", - "/pt/free-pro-team@latest/v3/enterprise-admin": "/pt/rest/reference/enterprise-admin", - "/pt/v3/enterprise": "/pt/rest/reference/enterprise-admin", - "/pt/free-pro-team@latest/v3/enterprise": "/pt/rest/reference/enterprise-admin", - "/pt/enterprise/3.0/rest/reference/enterprise-admin": "/pt/enterprise-server@3.0/rest/reference/enterprise-admin", - "/pt/enterprise/rest/reference/enterprise-admin": "/pt/enterprise-server@latest/rest/reference/enterprise-admin", - "/pt/enterprise-server@3.0/v3/enterprise-admin": "/pt/enterprise-server@3.0/rest/reference/enterprise-admin", - "/pt/enterprise/3.0/v3/enterprise-admin": "/pt/enterprise-server@3.0/rest/reference/enterprise-admin", - "/pt/enterprise/v3/enterprise-admin": "/pt/enterprise-server@latest/rest/reference/enterprise-admin", - "/pt/enterprise-server@3.0/v3/enterprise": "/pt/enterprise-server@3.0/rest/reference/enterprise-admin", - "/pt/enterprise/3.0/v3/enterprise": "/pt/enterprise-server@3.0/rest/reference/enterprise-admin", - "/pt/enterprise/v3/enterprise": "/pt/enterprise-server@latest/rest/reference/enterprise-admin", - "/pt/enterprise/2.20/rest/reference/enterprise-admin": "/pt/enterprise-server@2.20/rest/reference/enterprise-admin", - "/pt/enterprise-server@2.20/v3/enterprise-admin": "/pt/enterprise-server@2.20/rest/reference/enterprise-admin", - "/pt/enterprise/2.20/v3/enterprise-admin": "/pt/enterprise-server@2.20/rest/reference/enterprise-admin", - "/pt/enterprise-server@2.20/v3/enterprise": "/pt/enterprise-server@2.20/rest/reference/enterprise-admin", - "/pt/enterprise/2.20/v3/enterprise": "/pt/enterprise-server@2.20/rest/reference/enterprise-admin", - "/pt/github-ae@latest/v3/enterprise-admin": "/pt/github-ae@latest/rest/reference/enterprise-admin", - "/pt/github-ae@latest/v3/enterprise": "/pt/github-ae@latest/rest/reference/enterprise-admin", - "/pt/free-pro-team@latest/rest/reference/gists": "/pt/rest/reference/gists", - "/pt/v3/gists": "/pt/rest/reference/gists", - "/pt/free-pro-team@latest/v3/gists": "/pt/rest/reference/gists", - "/pt/enterprise/3.0/rest/reference/gists": "/pt/enterprise-server@3.0/rest/reference/gists", - "/pt/enterprise/rest/reference/gists": "/pt/enterprise-server@latest/rest/reference/gists", - "/pt/enterprise-server@3.0/v3/gists": "/pt/enterprise-server@3.0/rest/reference/gists", - "/pt/enterprise/3.0/v3/gists": "/pt/enterprise-server@3.0/rest/reference/gists", - "/pt/enterprise/v3/gists": "/pt/enterprise-server@latest/rest/reference/gists", - "/pt/enterprise/2.20/rest/reference/gists": "/pt/enterprise-server@2.20/rest/reference/gists", - "/pt/enterprise-server@2.20/v3/gists": "/pt/enterprise-server@2.20/rest/reference/gists", - "/pt/enterprise/2.20/v3/gists": "/pt/enterprise-server@2.20/rest/reference/gists", - "/pt/github-ae@latest/v3/gists": "/pt/github-ae@latest/rest/reference/gists", - "/pt/free-pro-team@latest/rest/reference/git": "/pt/rest/reference/git", - "/pt/v3/git": "/pt/rest/reference/git", - "/pt/free-pro-team@latest/v3/git": "/pt/rest/reference/git", - "/pt/enterprise/3.0/rest/reference/git": "/pt/enterprise-server@3.0/rest/reference/git", - "/pt/enterprise/rest/reference/git": "/pt/enterprise-server@latest/rest/reference/git", - "/pt/enterprise-server@3.0/v3/git": "/pt/enterprise-server@3.0/rest/reference/git", - "/pt/enterprise/3.0/v3/git": "/pt/enterprise-server@3.0/rest/reference/git", - "/pt/enterprise/v3/git": "/pt/enterprise-server@latest/rest/reference/git", - "/pt/enterprise/2.20/rest/reference/git": "/pt/enterprise-server@2.20/rest/reference/git", - "/pt/enterprise-server@2.20/v3/git": "/pt/enterprise-server@2.20/rest/reference/git", - "/pt/enterprise/2.20/v3/git": "/pt/enterprise-server@2.20/rest/reference/git", - "/pt/github-ae@latest/v3/git": "/pt/github-ae@latest/rest/reference/git", - "/pt/free-pro-team@latest/rest/reference/gitignore": "/pt/rest/reference/gitignore", - "/pt/v3/gitignore": "/pt/rest/reference/gitignore", - "/pt/free-pro-team@latest/v3/gitignore": "/pt/rest/reference/gitignore", - "/pt/enterprise/3.0/rest/reference/gitignore": "/pt/enterprise-server@3.0/rest/reference/gitignore", - "/pt/enterprise/rest/reference/gitignore": "/pt/enterprise-server@latest/rest/reference/gitignore", - "/pt/enterprise-server@3.0/v3/gitignore": "/pt/enterprise-server@3.0/rest/reference/gitignore", - "/pt/enterprise/3.0/v3/gitignore": "/pt/enterprise-server@3.0/rest/reference/gitignore", - "/pt/enterprise/v3/gitignore": "/pt/enterprise-server@latest/rest/reference/gitignore", - "/pt/enterprise/2.20/rest/reference/gitignore": "/pt/enterprise-server@2.20/rest/reference/gitignore", - "/pt/enterprise-server@2.20/v3/gitignore": "/pt/enterprise-server@2.20/rest/reference/gitignore", - "/pt/enterprise/2.20/v3/gitignore": "/pt/enterprise-server@2.20/rest/reference/gitignore", - "/pt/github-ae@latest/v3/gitignore": "/pt/github-ae@latest/rest/reference/gitignore", - "/pt/free-pro-team@latest/rest/reference": "/pt/rest/reference", - "/pt/enterprise/3.0/rest/reference": "/pt/enterprise-server@3.0/rest/reference", - "/pt/enterprise/rest/reference": "/pt/enterprise-server@latest/rest/reference", - "/pt/enterprise/2.20/rest/reference": "/pt/enterprise-server@2.20/rest/reference", - "/pt/free-pro-team@latest/rest/reference/interactions": "/pt/rest/reference/interactions", - "/pt/v3/interactions": "/pt/rest/reference/interactions", - "/pt/free-pro-team@latest/v3/interactions": "/pt/rest/reference/interactions", - "/pt/free-pro-team@latest/rest/reference/issues": "/pt/rest/reference/issues", - "/pt/v3/issues": "/pt/rest/reference/issues", - "/pt/free-pro-team@latest/v3/issues": "/pt/rest/reference/issues", - "/pt/enterprise/3.0/rest/reference/issues": "/pt/enterprise-server@3.0/rest/reference/issues", - "/pt/enterprise/rest/reference/issues": "/pt/enterprise-server@latest/rest/reference/issues", - "/pt/enterprise-server@3.0/v3/issues": "/pt/enterprise-server@3.0/rest/reference/issues", - "/pt/enterprise/3.0/v3/issues": "/pt/enterprise-server@3.0/rest/reference/issues", - "/pt/enterprise/v3/issues": "/pt/enterprise-server@latest/rest/reference/issues", - "/pt/enterprise/2.20/rest/reference/issues": "/pt/enterprise-server@2.20/rest/reference/issues", - "/pt/enterprise-server@2.20/v3/issues": "/pt/enterprise-server@2.20/rest/reference/issues", - "/pt/enterprise/2.20/v3/issues": "/pt/enterprise-server@2.20/rest/reference/issues", - "/pt/github-ae@latest/v3/issues": "/pt/github-ae@latest/rest/reference/issues", - "/pt/free-pro-team@latest/rest/reference/licenses": "/pt/rest/reference/licenses", - "/pt/v3/licenses": "/pt/rest/reference/licenses", - "/pt/free-pro-team@latest/v3/licenses": "/pt/rest/reference/licenses", - "/pt/enterprise/3.0/rest/reference/licenses": "/pt/enterprise-server@3.0/rest/reference/licenses", - "/pt/enterprise/rest/reference/licenses": "/pt/enterprise-server@latest/rest/reference/licenses", - "/pt/enterprise-server@3.0/v3/licenses": "/pt/enterprise-server@3.0/rest/reference/licenses", - "/pt/enterprise/3.0/v3/licenses": "/pt/enterprise-server@3.0/rest/reference/licenses", - "/pt/enterprise/v3/licenses": "/pt/enterprise-server@latest/rest/reference/licenses", - "/pt/enterprise/2.20/rest/reference/licenses": "/pt/enterprise-server@2.20/rest/reference/licenses", - "/pt/enterprise-server@2.20/v3/licenses": "/pt/enterprise-server@2.20/rest/reference/licenses", - "/pt/enterprise/2.20/v3/licenses": "/pt/enterprise-server@2.20/rest/reference/licenses", - "/pt/github-ae@latest/v3/licenses": "/pt/github-ae@latest/rest/reference/licenses", - "/pt/free-pro-team@latest/rest/reference/markdown": "/pt/rest/reference/markdown", - "/pt/v3/markdown": "/pt/rest/reference/markdown", - "/pt/free-pro-team@latest/v3/markdown": "/pt/rest/reference/markdown", - "/pt/enterprise/3.0/rest/reference/markdown": "/pt/enterprise-server@3.0/rest/reference/markdown", - "/pt/enterprise/rest/reference/markdown": "/pt/enterprise-server@latest/rest/reference/markdown", - "/pt/enterprise-server@3.0/v3/markdown": "/pt/enterprise-server@3.0/rest/reference/markdown", - "/pt/enterprise/3.0/v3/markdown": "/pt/enterprise-server@3.0/rest/reference/markdown", - "/pt/enterprise/v3/markdown": "/pt/enterprise-server@latest/rest/reference/markdown", - "/pt/enterprise/2.20/rest/reference/markdown": "/pt/enterprise-server@2.20/rest/reference/markdown", - "/pt/enterprise-server@2.20/v3/markdown": "/pt/enterprise-server@2.20/rest/reference/markdown", - "/pt/enterprise/2.20/v3/markdown": "/pt/enterprise-server@2.20/rest/reference/markdown", - "/pt/github-ae@latest/v3/markdown": "/pt/github-ae@latest/rest/reference/markdown", - "/pt/free-pro-team@latest/rest/reference/meta": "/pt/rest/reference/meta", - "/pt/v3/meta": "/pt/rest/reference/meta", - "/pt/free-pro-team@latest/v3/meta": "/pt/rest/reference/meta", - "/pt/enterprise/3.0/rest/reference/meta": "/pt/enterprise-server@3.0/rest/reference/meta", - "/pt/enterprise/rest/reference/meta": "/pt/enterprise-server@latest/rest/reference/meta", - "/pt/enterprise-server@3.0/v3/meta": "/pt/enterprise-server@3.0/rest/reference/meta", - "/pt/enterprise/3.0/v3/meta": "/pt/enterprise-server@3.0/rest/reference/meta", - "/pt/enterprise/v3/meta": "/pt/enterprise-server@latest/rest/reference/meta", - "/pt/enterprise/2.20/rest/reference/meta": "/pt/enterprise-server@2.20/rest/reference/meta", - "/pt/enterprise-server@2.20/v3/meta": "/pt/enterprise-server@2.20/rest/reference/meta", - "/pt/enterprise/2.20/v3/meta": "/pt/enterprise-server@2.20/rest/reference/meta", - "/pt/github-ae@latest/v3/meta": "/pt/github-ae@latest/rest/reference/meta", - "/pt/free-pro-team@latest/rest/reference/migrations": "/pt/rest/reference/migrations", - "/pt/v3/migrations": "/pt/rest/reference/migrations", - "/pt/free-pro-team@latest/v3/migrations": "/pt/rest/reference/migrations", - "/pt/v3/migration": "/pt/rest/reference/migrations", - "/pt/free-pro-team@latest/v3/migration": "/pt/rest/reference/migrations", - "/pt/v3/migration/migrations": "/pt/rest/reference/migrations", - "/pt/free-pro-team@latest/v3/migration/migrations": "/pt/rest/reference/migrations", - "/pt/enterprise/3.0/rest/reference/oauth-authorizations": "/pt/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/pt/enterprise/rest/reference/oauth-authorizations": "/pt/enterprise-server@latest/rest/reference/oauth-authorizations", - "/pt/enterprise-server@3.0/v3/oauth_authorizations": "/pt/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/pt/enterprise/3.0/v3/oauth_authorizations": "/pt/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/pt/enterprise/v3/oauth_authorizations": "/pt/enterprise-server@latest/rest/reference/oauth-authorizations", - "/pt/enterprise-server@3.0/v3/oauth-authorizations": "/pt/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/pt/enterprise/3.0/v3/oauth-authorizations": "/pt/enterprise-server@3.0/rest/reference/oauth-authorizations", - "/pt/enterprise/v3/oauth-authorizations": "/pt/enterprise-server@latest/rest/reference/oauth-authorizations", - "/pt/enterprise/2.20/rest/reference/oauth-authorizations": "/pt/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/pt/enterprise-server@2.20/v3/oauth_authorizations": "/pt/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/pt/enterprise/2.20/v3/oauth_authorizations": "/pt/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/pt/enterprise-server@2.20/v3/oauth-authorizations": "/pt/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/pt/enterprise/2.20/v3/oauth-authorizations": "/pt/enterprise-server@2.20/rest/reference/oauth-authorizations", - "/pt/free-pro-team@latest/rest/reference/orgs": "/pt/rest/reference/orgs", - "/pt/v3/orgs": "/pt/rest/reference/orgs", - "/pt/free-pro-team@latest/v3/orgs": "/pt/rest/reference/orgs", - "/pt/enterprise/3.0/rest/reference/orgs": "/pt/enterprise-server@3.0/rest/reference/orgs", - "/pt/enterprise/rest/reference/orgs": "/pt/enterprise-server@latest/rest/reference/orgs", - "/pt/enterprise-server@3.0/v3/orgs": "/pt/enterprise-server@3.0/rest/reference/orgs", - "/pt/enterprise/3.0/v3/orgs": "/pt/enterprise-server@3.0/rest/reference/orgs", - "/pt/enterprise/v3/orgs": "/pt/enterprise-server@latest/rest/reference/orgs", - "/pt/enterprise/2.20/rest/reference/orgs": "/pt/enterprise-server@2.20/rest/reference/orgs", - "/pt/enterprise-server@2.20/v3/orgs": "/pt/enterprise-server@2.20/rest/reference/orgs", - "/pt/enterprise/2.20/v3/orgs": "/pt/enterprise-server@2.20/rest/reference/orgs", - "/pt/github-ae@latest/v3/orgs": "/pt/github-ae@latest/rest/reference/orgs", - "/pt/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/pt/rest/reference/permissions-required-for-github-apps", - "/pt/v3/apps/permissions": "/pt/rest/reference/permissions-required-for-github-apps", - "/pt/free-pro-team@latest/v3/apps/permissions": "/pt/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/pt/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise/rest/reference/permissions-required-for-github-apps": "/pt/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise-server@3.0/v3/apps/permissions": "/pt/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise/3.0/v3/apps/permissions": "/pt/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise/v3/apps/permissions": "/pt/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/pt/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise-server@2.20/v3/apps/permissions": "/pt/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/pt/enterprise/2.20/v3/apps/permissions": "/pt/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", - "/pt/github-ae@latest/v3/apps/permissions": "/pt/github-ae@latest/rest/reference/permissions-required-for-github-apps", - "/pt/free-pro-team@latest/rest/reference/projects": "/pt/rest/reference/projects", - "/pt/v3/projects": "/pt/rest/reference/projects", - "/pt/free-pro-team@latest/v3/projects": "/pt/rest/reference/projects", - "/pt/enterprise/3.0/rest/reference/projects": "/pt/enterprise-server@3.0/rest/reference/projects", - "/pt/enterprise/rest/reference/projects": "/pt/enterprise-server@latest/rest/reference/projects", - "/pt/enterprise-server@3.0/v3/projects": "/pt/enterprise-server@3.0/rest/reference/projects", - "/pt/enterprise/3.0/v3/projects": "/pt/enterprise-server@3.0/rest/reference/projects", - "/pt/enterprise/v3/projects": "/pt/enterprise-server@latest/rest/reference/projects", - "/pt/enterprise/2.20/rest/reference/projects": "/pt/enterprise-server@2.20/rest/reference/projects", - "/pt/enterprise-server@2.20/v3/projects": "/pt/enterprise-server@2.20/rest/reference/projects", - "/pt/enterprise/2.20/v3/projects": "/pt/enterprise-server@2.20/rest/reference/projects", - "/pt/github-ae@latest/v3/projects": "/pt/github-ae@latest/rest/reference/projects", - "/pt/free-pro-team@latest/rest/reference/pulls": "/pt/rest/reference/pulls", - "/pt/v3/pulls": "/pt/rest/reference/pulls", - "/pt/free-pro-team@latest/v3/pulls": "/pt/rest/reference/pulls", - "/pt/enterprise/3.0/rest/reference/pulls": "/pt/enterprise-server@3.0/rest/reference/pulls", - "/pt/enterprise/rest/reference/pulls": "/pt/enterprise-server@latest/rest/reference/pulls", - "/pt/enterprise-server@3.0/v3/pulls": "/pt/enterprise-server@3.0/rest/reference/pulls", - "/pt/enterprise/3.0/v3/pulls": "/pt/enterprise-server@3.0/rest/reference/pulls", - "/pt/enterprise/v3/pulls": "/pt/enterprise-server@latest/rest/reference/pulls", - "/pt/enterprise/2.20/rest/reference/pulls": "/pt/enterprise-server@2.20/rest/reference/pulls", - "/pt/enterprise-server@2.20/v3/pulls": "/pt/enterprise-server@2.20/rest/reference/pulls", - "/pt/enterprise/2.20/v3/pulls": "/pt/enterprise-server@2.20/rest/reference/pulls", - "/pt/github-ae@latest/v3/pulls": "/pt/github-ae@latest/rest/reference/pulls", - "/pt/free-pro-team@latest/rest/reference/rate-limit": "/pt/rest/reference/rate-limit", - "/pt/v3/rate_limit": "/pt/rest/reference/rate-limit", - "/pt/free-pro-team@latest/v3/rate_limit": "/pt/rest/reference/rate-limit", - "/pt/v3/rate-limit": "/pt/rest/reference/rate-limit", - "/pt/free-pro-team@latest/v3/rate-limit": "/pt/rest/reference/rate-limit", - "/pt/enterprise/3.0/rest/reference/rate-limit": "/pt/enterprise-server@3.0/rest/reference/rate-limit", - "/pt/enterprise/rest/reference/rate-limit": "/pt/enterprise-server@latest/rest/reference/rate-limit", - "/pt/enterprise-server@3.0/v3/rate_limit": "/pt/enterprise-server@3.0/rest/reference/rate-limit", - "/pt/enterprise/3.0/v3/rate_limit": "/pt/enterprise-server@3.0/rest/reference/rate-limit", - "/pt/enterprise/v3/rate_limit": "/pt/enterprise-server@latest/rest/reference/rate-limit", - "/pt/enterprise-server@3.0/v3/rate-limit": "/pt/enterprise-server@3.0/rest/reference/rate-limit", - "/pt/enterprise/3.0/v3/rate-limit": "/pt/enterprise-server@3.0/rest/reference/rate-limit", - "/pt/enterprise/v3/rate-limit": "/pt/enterprise-server@latest/rest/reference/rate-limit", - "/pt/enterprise/2.20/rest/reference/rate-limit": "/pt/enterprise-server@2.20/rest/reference/rate-limit", - "/pt/enterprise-server@2.20/v3/rate_limit": "/pt/enterprise-server@2.20/rest/reference/rate-limit", - "/pt/enterprise/2.20/v3/rate_limit": "/pt/enterprise-server@2.20/rest/reference/rate-limit", - "/pt/enterprise-server@2.20/v3/rate-limit": "/pt/enterprise-server@2.20/rest/reference/rate-limit", - "/pt/enterprise/2.20/v3/rate-limit": "/pt/enterprise-server@2.20/rest/reference/rate-limit", - "/pt/github-ae@latest/v3/rate_limit": "/pt/github-ae@latest/rest/reference/rate-limit", - "/pt/github-ae@latest/v3/rate-limit": "/pt/github-ae@latest/rest/reference/rate-limit", - "/pt/free-pro-team@latest/rest/reference/reactions": "/pt/rest/reference/reactions", - "/pt/v3/reactions": "/pt/rest/reference/reactions", - "/pt/free-pro-team@latest/v3/reactions": "/pt/rest/reference/reactions", - "/pt/enterprise/3.0/rest/reference/reactions": "/pt/enterprise-server@3.0/rest/reference/reactions", - "/pt/enterprise/rest/reference/reactions": "/pt/enterprise-server@latest/rest/reference/reactions", - "/pt/enterprise-server@3.0/v3/reactions": "/pt/enterprise-server@3.0/rest/reference/reactions", - "/pt/enterprise/3.0/v3/reactions": "/pt/enterprise-server@3.0/rest/reference/reactions", - "/pt/enterprise/v3/reactions": "/pt/enterprise-server@latest/rest/reference/reactions", - "/pt/enterprise/2.20/rest/reference/reactions": "/pt/enterprise-server@2.20/rest/reference/reactions", - "/pt/enterprise-server@2.20/v3/reactions": "/pt/enterprise-server@2.20/rest/reference/reactions", - "/pt/enterprise/2.20/v3/reactions": "/pt/enterprise-server@2.20/rest/reference/reactions", - "/pt/github-ae@latest/v3/reactions": "/pt/github-ae@latest/rest/reference/reactions", - "/pt/free-pro-team@latest/rest/reference/repos": "/pt/rest/reference/repos", - "/pt/v3/repos": "/pt/rest/reference/repos", - "/pt/free-pro-team@latest/v3/repos": "/pt/rest/reference/repos", - "/pt/enterprise/3.0/rest/reference/repos": "/pt/enterprise-server@3.0/rest/reference/repos", - "/pt/enterprise/rest/reference/repos": "/pt/enterprise-server@latest/rest/reference/repos", - "/pt/enterprise-server@3.0/v3/repos": "/pt/enterprise-server@3.0/rest/reference/repos", - "/pt/enterprise/3.0/v3/repos": "/pt/enterprise-server@3.0/rest/reference/repos", - "/pt/enterprise/v3/repos": "/pt/enterprise-server@latest/rest/reference/repos", - "/pt/enterprise/2.20/rest/reference/repos": "/pt/enterprise-server@2.20/rest/reference/repos", - "/pt/enterprise-server@2.20/v3/repos": "/pt/enterprise-server@2.20/rest/reference/repos", - "/pt/enterprise/2.20/v3/repos": "/pt/enterprise-server@2.20/rest/reference/repos", - "/pt/github-ae@latest/v3/repos": "/pt/github-ae@latest/rest/reference/repos", - "/pt/free-pro-team@latest/rest/reference/scim": "/pt/rest/reference/scim", - "/pt/v3/scim": "/pt/rest/reference/scim", - "/pt/free-pro-team@latest/v3/scim": "/pt/rest/reference/scim", - "/pt/free-pro-team@latest/rest/reference/search": "/pt/rest/reference/search", - "/pt/v3/search": "/pt/rest/reference/search", - "/pt/free-pro-team@latest/v3/search": "/pt/rest/reference/search", - "/pt/enterprise/3.0/rest/reference/search": "/pt/enterprise-server@3.0/rest/reference/search", - "/pt/enterprise/rest/reference/search": "/pt/enterprise-server@latest/rest/reference/search", - "/pt/enterprise-server@3.0/v3/search": "/pt/enterprise-server@3.0/rest/reference/search", - "/pt/enterprise/3.0/v3/search": "/pt/enterprise-server@3.0/rest/reference/search", - "/pt/enterprise/v3/search": "/pt/enterprise-server@latest/rest/reference/search", - "/pt/enterprise/2.20/rest/reference/search": "/pt/enterprise-server@2.20/rest/reference/search", - "/pt/enterprise-server@2.20/v3/search": "/pt/enterprise-server@2.20/rest/reference/search", - "/pt/enterprise/2.20/v3/search": "/pt/enterprise-server@2.20/rest/reference/search", - "/pt/github-ae@latest/v3/search": "/pt/github-ae@latest/rest/reference/search", - "/pt/free-pro-team@latest/rest/reference/secret-scanning": "/pt/rest/reference/secret-scanning", - "/pt/free-pro-team@latest/rest/reference/teams": "/pt/rest/reference/teams", - "/pt/v3/teams": "/pt/rest/reference/teams", - "/pt/free-pro-team@latest/v3/teams": "/pt/rest/reference/teams", - "/pt/enterprise/3.0/rest/reference/teams": "/pt/enterprise-server@3.0/rest/reference/teams", - "/pt/enterprise/rest/reference/teams": "/pt/enterprise-server@latest/rest/reference/teams", - "/pt/enterprise-server@3.0/v3/teams": "/pt/enterprise-server@3.0/rest/reference/teams", - "/pt/enterprise/3.0/v3/teams": "/pt/enterprise-server@3.0/rest/reference/teams", - "/pt/enterprise/v3/teams": "/pt/enterprise-server@latest/rest/reference/teams", - "/pt/enterprise/2.20/rest/reference/teams": "/pt/enterprise-server@2.20/rest/reference/teams", - "/pt/enterprise-server@2.20/v3/teams": "/pt/enterprise-server@2.20/rest/reference/teams", - "/pt/enterprise/2.20/v3/teams": "/pt/enterprise-server@2.20/rest/reference/teams", - "/pt/github-ae@latest/v3/teams": "/pt/github-ae@latest/rest/reference/teams", - "/pt/free-pro-team@latest/rest/reference/users": "/pt/rest/reference/users", - "/pt/v3/users": "/pt/rest/reference/users", - "/pt/free-pro-team@latest/v3/users": "/pt/rest/reference/users", - "/pt/enterprise/3.0/rest/reference/users": "/pt/enterprise-server@3.0/rest/reference/users", - "/pt/enterprise/rest/reference/users": "/pt/enterprise-server@latest/rest/reference/users", - "/pt/enterprise-server@3.0/v3/users": "/pt/enterprise-server@3.0/rest/reference/users", - "/pt/enterprise/3.0/v3/users": "/pt/enterprise-server@3.0/rest/reference/users", - "/pt/enterprise/v3/users": "/pt/enterprise-server@latest/rest/reference/users", - "/pt/enterprise/2.20/rest/reference/users": "/pt/enterprise-server@2.20/rest/reference/users", - "/pt/enterprise-server@2.20/v3/users": "/pt/enterprise-server@2.20/rest/reference/users", - "/pt/enterprise/2.20/v3/users": "/pt/enterprise-server@2.20/rest/reference/users", - "/pt/github-ae@latest/v3/users": "/pt/github-ae@latest/rest/reference/users", - "/enterprise/2.20/v3/activity/events": "/en/enterprise-server@2.20/rest/reference/activity#events", - "/en/enterprise/2.20/v3/activity/events": "/en/enterprise-server@2.20/rest/reference/activity#events", - "/enterprise/2.20/v3/activity/feeds": "/en/enterprise-server@2.20/rest/reference/activity#feeds", - "/en/enterprise/2.20/v3/activity/feeds": "/en/enterprise-server@2.20/rest/reference/activity#feeds", - "/enterprise/2.20/v3/activity/notifications": "/en/enterprise-server@2.20/rest/reference/activity#notifications", - "/en/enterprise/2.20/v3/activity/notifications": "/en/enterprise-server@2.20/rest/reference/activity#notifications", - "/enterprise/2.20/v3/activity/starring": "/en/enterprise-server@2.20/rest/reference/activity#starring", - "/en/enterprise/2.20/v3/activity/starring": "/en/enterprise-server@2.20/rest/reference/activity#starring", - "/enterprise/2.20/v3/activity/watching": "/en/enterprise-server@2.20/rest/reference/activity#watching", - "/en/enterprise/2.20/v3/activity/watching": "/en/enterprise-server@2.20/rest/reference/activity#watching", - "/enterprise/2.20/v3/apps/installations": "/en/enterprise-server@2.20/rest/reference/apps#installations", - "/en/enterprise/2.20/v3/apps/installations": "/en/enterprise-server@2.20/rest/reference/apps#installations", - "/enterprise/2.20/v3/apps/oauth_applications": "/en/enterprise-server@2.20/rest/reference/apps#oauth-applications", - "/en/enterprise/2.20/v3/apps/oauth_applications": "/en/enterprise-server@2.20/rest/reference/apps#oauth-applications", - "/enterprise/2.20/v3/checks/runs": "/en/enterprise-server@2.20/rest/reference/checks#runs", - "/en/enterprise/2.20/v3/checks/runs": "/en/enterprise-server@2.20/rest/reference/checks#runs", - "/enterprise/2.20/v3/checks/suites": "/en/enterprise-server@2.20/rest/reference/checks#suites", - "/en/enterprise/2.20/v3/checks/suites": "/en/enterprise-server@2.20/rest/reference/checks#suites", - "/enterprise/2.20/v3/enterprise-admin/admin_stats": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#admin-stats", - "/en/enterprise/2.20/v3/enterprise-admin/admin_stats": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#admin-stats", - "/enterprise/2.20/v3/enterprise-admin/global_webhooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#global-webhooks", - "/en/enterprise/2.20/v3/enterprise-admin/global_webhooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#global-webhooks", - "/enterprise/2.20/v3/enterprise-admin/ldap": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#ldap", - "/en/enterprise/2.20/v3/enterprise-admin/ldap": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#ldap", - "/enterprise/2.20/v3/enterprise-admin/license": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#license", - "/en/enterprise/2.20/v3/enterprise-admin/license": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#license", - "/enterprise/2.20/v3/enterprise-admin/management_console": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#management-console", - "/en/enterprise/2.20/v3/enterprise-admin/management_console": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#management-console", - "/enterprise/2.20/v3/enterprise-admin/org_pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/en/enterprise/2.20/v3/enterprise-admin/org_pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/enterprise/2.20/v3/enterprise-admin/orgs": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#orgs", - "/en/enterprise/2.20/v3/enterprise-admin/orgs": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#orgs", - "/enterprise/2.20/v3/enterprise-admin/pre_receive_environments": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-environments", - "/en/enterprise/2.20/v3/enterprise-admin/pre_receive_environments": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-environments", - "/enterprise/2.20/v3/enterprise-admin/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-hooks", - "/en/enterprise/2.20/v3/enterprise-admin/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-hooks", - "/enterprise/2.20/v3/enterprise-admin/repo_pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/en/enterprise/2.20/v3/enterprise-admin/repo_pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/enterprise/2.20/v3/enterprise-admin/search_indexing": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#search-indexing", - "/en/enterprise/2.20/v3/enterprise-admin/search_indexing": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#search-indexing", - "/enterprise/2.20/v3/enterprise-admin/users": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#users", - "/en/enterprise/2.20/v3/enterprise-admin/users": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#users", - "/enterprise/2.20/v3/enterprise/admin_stats": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#admin-stats", - "/en/enterprise/2.20/v3/enterprise/admin_stats": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#admin-stats", - "/enterprise/2.20/v3/enterprise/ldap": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#ldap", - "/en/enterprise/2.20/v3/enterprise/ldap": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#ldap", - "/enterprise/2.20/v3/enterprise/license": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#license", - "/en/enterprise/2.20/v3/enterprise/license": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#license", - "/enterprise/2.20/v3/enterprise/management_console": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#management-console", - "/en/enterprise/2.20/v3/enterprise/management_console": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#management-console", - "/enterprise/2.20/v3/enterprise/orgs": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#orgs", - "/en/enterprise/2.20/v3/enterprise/orgs": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#orgs", - "/enterprise/2.20/v3/enterprise/pre_receive_environments": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-environments", - "/en/enterprise/2.20/v3/enterprise/pre_receive_environments": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-environments", - "/enterprise/2.20/v3/enterprise/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-hooks", - "/en/enterprise/2.20/v3/enterprise/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-hooks", - "/enterprise/2.20/v3/enterprise/search_indexing": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#search-indexing", - "/en/enterprise/2.20/v3/enterprise/search_indexing": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#search-indexing", - "/enterprise/2.20/v3/gists/comments": "/en/enterprise-server@2.20/rest/reference/gists#comments", - "/en/enterprise/2.20/v3/gists/comments": "/en/enterprise-server@2.20/rest/reference/gists#comments", - "/enterprise/2.20/v3/git/blobs": "/en/enterprise-server@2.20/rest/reference/git#blobs", - "/en/enterprise/2.20/v3/git/blobs": "/en/enterprise-server@2.20/rest/reference/git#blobs", - "/enterprise/2.20/v3/git/commits": "/en/enterprise-server@2.20/rest/reference/git#commits", - "/en/enterprise/2.20/v3/git/commits": "/en/enterprise-server@2.20/rest/reference/git#commits", - "/enterprise/2.20/v3/git/refs": "/en/enterprise-server@2.20/rest/reference/git#refs", - "/en/enterprise/2.20/v3/git/refs": "/en/enterprise-server@2.20/rest/reference/git#refs", - "/enterprise/2.20/v3/git/tags": "/en/enterprise-server@2.20/rest/reference/git#tags", - "/en/enterprise/2.20/v3/git/tags": "/en/enterprise-server@2.20/rest/reference/git#tags", - "/enterprise/2.20/v3/git/trees": "/en/enterprise-server@2.20/rest/reference/git#trees", - "/en/enterprise/2.20/v3/git/trees": "/en/enterprise-server@2.20/rest/reference/git#trees", - "/enterprise/2.20/v3/integrations/installations": "/en/enterprise-server@2.20/developers/apps#installations", - "/en/enterprise/2.20/v3/integrations/installations": "/en/enterprise-server@2.20/developers/apps#installations", - "/enterprise/2.20/v3/issues/assignees": "/en/enterprise-server@2.20/rest/reference/issues#assignees", - "/en/enterprise/2.20/v3/issues/assignees": "/en/enterprise-server@2.20/rest/reference/issues#assignees", - "/enterprise/2.20/v3/issues/comments": "/en/enterprise-server@2.20/rest/reference/issues#comments", - "/en/enterprise/2.20/v3/issues/comments": "/en/enterprise-server@2.20/rest/reference/issues#comments", - "/enterprise/2.20/v3/issues/events": "/en/enterprise-server@2.20/rest/reference/issues#events", - "/en/enterprise/2.20/v3/issues/events": "/en/enterprise-server@2.20/rest/reference/issues#events", - "/enterprise/2.20/v3/issues/labels": "/en/enterprise-server@2.20/rest/reference/issues#labels", - "/en/enterprise/2.20/v3/issues/labels": "/en/enterprise-server@2.20/rest/reference/issues#labels", - "/enterprise/2.20/v3/issues/milestones": "/en/enterprise-server@2.20/rest/reference/issues#milestones", - "/en/enterprise/2.20/v3/issues/milestones": "/en/enterprise-server@2.20/rest/reference/issues#milestones", - "/enterprise/2.20/v3/issues/timeline": "/en/enterprise-server@2.20/rest/reference/issues#timeline", - "/en/enterprise/2.20/v3/issues/timeline": "/en/enterprise-server@2.20/rest/reference/issues#timeline", - "/enterprise/2.20/v3/orgs/hooks": "/en/enterprise-server@2.20/rest/reference/orgs#webhooks", - "/en/enterprise/2.20/v3/orgs/hooks": "/en/enterprise-server@2.20/rest/reference/orgs#webhooks", - "/enterprise/2.20/v3/orgs/members": "/en/enterprise-server@2.20/rest/reference/orgs#members", - "/en/enterprise/2.20/v3/orgs/members": "/en/enterprise-server@2.20/rest/reference/orgs#members", - "/enterprise/2.20/v3/orgs/outside_collaborators": "/en/enterprise-server@2.20/rest/reference/orgs#outside-collaborators", - "/en/enterprise/2.20/v3/orgs/outside_collaborators": "/en/enterprise-server@2.20/rest/reference/orgs#outside-collaborators", - "/enterprise/2.20/v3/orgs/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/en/enterprise/2.20/v3/orgs/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/enterprise/2.20/v3/orgs/teams": "/en/enterprise-server@2.20/rest/reference/orgs#teams", - "/en/enterprise/2.20/v3/orgs/teams": "/en/enterprise-server@2.20/rest/reference/orgs#teams", - "/enterprise/2.20/v3/projects/cards": "/en/enterprise-server@2.20/rest/reference/projects#cards", - "/en/enterprise/2.20/v3/projects/cards": "/en/enterprise-server@2.20/rest/reference/projects#cards", - "/enterprise/2.20/v3/projects/collaborators": "/en/enterprise-server@2.20/rest/reference/projects#collaborators", - "/en/enterprise/2.20/v3/projects/collaborators": "/en/enterprise-server@2.20/rest/reference/projects#collaborators", - "/enterprise/2.20/v3/projects/columns": "/en/enterprise-server@2.20/rest/reference/projects#columns", - "/en/enterprise/2.20/v3/projects/columns": "/en/enterprise-server@2.20/rest/reference/projects#columns", - "/enterprise/2.20/v3/pulls/comments": "/en/enterprise-server@2.20/rest/reference/pulls#comments", - "/en/enterprise/2.20/v3/pulls/comments": "/en/enterprise-server@2.20/rest/reference/pulls#comments", - "/enterprise/2.20/v3/pulls/review_requests": "/en/enterprise-server@2.20/rest/reference/pulls#review-requests", - "/en/enterprise/2.20/v3/pulls/review_requests": "/en/enterprise-server@2.20/rest/reference/pulls#review-requests", - "/enterprise/2.20/v3/pulls/reviews": "/en/enterprise-server@2.20/rest/reference/pulls#reviews", - "/en/enterprise/2.20/v3/pulls/reviews": "/en/enterprise-server@2.20/rest/reference/pulls#reviews", - "/enterprise/2.20/v3/repos/branches": "/en/enterprise-server@2.20/rest/reference/repos#branches", - "/en/enterprise/2.20/v3/repos/branches": "/en/enterprise-server@2.20/rest/reference/repos#branches", - "/enterprise/2.20/v3/repos/collaborators": "/en/enterprise-server@2.20/rest/reference/repos#collaborators", - "/en/enterprise/2.20/v3/repos/collaborators": "/en/enterprise-server@2.20/rest/reference/repos#collaborators", - "/enterprise/2.20/v3/repos/comments": "/en/enterprise-server@2.20/rest/reference/repos#comments", - "/en/enterprise/2.20/v3/repos/comments": "/en/enterprise-server@2.20/rest/reference/repos#comments", - "/enterprise/2.20/v3/repos/commits": "/en/enterprise-server@2.20/rest/reference/repos#commits", - "/en/enterprise/2.20/v3/repos/commits": "/en/enterprise-server@2.20/rest/reference/repos#commits", - "/enterprise/2.20/v3/repos/contents": "/en/enterprise-server@2.20/rest/reference/repos#contents", - "/en/enterprise/2.20/v3/repos/contents": "/en/enterprise-server@2.20/rest/reference/repos#contents", - "/enterprise/2.20/v3/repos/deployments": "/en/enterprise-server@2.20/rest/reference/repos#deployments", - "/en/enterprise/2.20/v3/repos/deployments": "/en/enterprise-server@2.20/rest/reference/repos#deployments", - "/enterprise/2.20/v3/repos/downloads": "/en/enterprise-server@2.20/rest/reference/repos#downloads", - "/en/enterprise/2.20/v3/repos/downloads": "/en/enterprise-server@2.20/rest/reference/repos#downloads", - "/enterprise/2.20/v3/repos/forks": "/en/enterprise-server@2.20/rest/reference/repos#forks", - "/en/enterprise/2.20/v3/repos/forks": "/en/enterprise-server@2.20/rest/reference/repos#forks", - "/enterprise/2.20/v3/repos/hooks": "/en/enterprise-server@2.20/rest/reference/repos#webhooks", - "/en/enterprise/2.20/v3/repos/hooks": "/en/enterprise-server@2.20/rest/reference/repos#webhooks", - "/enterprise/2.20/v3/repos/invitations": "/en/enterprise-server@2.20/rest/reference/repos#invitations", - "/en/enterprise/2.20/v3/repos/invitations": "/en/enterprise-server@2.20/rest/reference/repos#invitations", - "/enterprise/2.20/v3/repos/keys": "/en/enterprise-server@2.20/rest/reference/repos#keys", - "/en/enterprise/2.20/v3/repos/keys": "/en/enterprise-server@2.20/rest/reference/repos#keys", - "/enterprise/2.20/v3/repos/merging": "/en/enterprise-server@2.20/rest/reference/repos#merging", - "/en/enterprise/2.20/v3/repos/merging": "/en/enterprise-server@2.20/rest/reference/repos#merging", - "/enterprise/2.20/v3/repos/pages": "/en/enterprise-server@2.20/rest/reference/repos#pages", - "/en/enterprise/2.20/v3/repos/pages": "/en/enterprise-server@2.20/rest/reference/repos#pages", - "/enterprise/2.20/v3/repos/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/en/enterprise/2.20/v3/repos/pre_receive_hooks": "/en/enterprise-server@2.20/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/enterprise/2.20/v3/repos/releases": "/en/enterprise-server@2.20/rest/reference/repos#releases", - "/en/enterprise/2.20/v3/repos/releases": "/en/enterprise-server@2.20/rest/reference/repos#releases", - "/enterprise/2.20/v3/repos/statistics": "/en/enterprise-server@2.20/rest/reference/repos#statistics", - "/en/enterprise/2.20/v3/repos/statistics": "/en/enterprise-server@2.20/rest/reference/repos#statistics", - "/enterprise/2.20/v3/repos/statuses": "/en/enterprise-server@2.20/rest/reference/repos#statuses", - "/en/enterprise/2.20/v3/repos/statuses": "/en/enterprise-server@2.20/rest/reference/repos#statuses", - "/enterprise/2.20/v3/teams/discussion_comments": "/en/enterprise-server@2.20/rest/reference/teams#discussion-comments", - "/en/enterprise/2.20/v3/teams/discussion_comments": "/en/enterprise-server@2.20/rest/reference/teams#discussion-comments", - "/enterprise/2.20/v3/teams/discussions": "/en/enterprise-server@2.20/rest/reference/teams#discussions", - "/en/enterprise/2.20/v3/teams/discussions": "/en/enterprise-server@2.20/rest/reference/teams#discussions", - "/enterprise/2.20/v3/teams/members": "/en/enterprise-server@2.20/rest/reference/teams#members", - "/en/enterprise/2.20/v3/teams/members": "/en/enterprise-server@2.20/rest/reference/teams#members", - "/enterprise/2.20/v3/users/administration": "/en/enterprise-server@2.20/rest/reference/users#administration", - "/en/enterprise/2.20/v3/users/administration": "/en/enterprise-server@2.20/rest/reference/users#administration", - "/enterprise/2.20/v3/users/emails": "/en/enterprise-server@2.20/rest/reference/users#emails", - "/en/enterprise/2.20/v3/users/emails": "/en/enterprise-server@2.20/rest/reference/users#emails", - "/enterprise/2.20/v3/users/followers": "/en/enterprise-server@2.20/rest/reference/users#followers", - "/en/enterprise/2.20/v3/users/followers": "/en/enterprise-server@2.20/rest/reference/users#followers", - "/enterprise/2.20/v3/users/gpg_keys": "/en/enterprise-server@2.20/rest/reference/users#gpg-keys", - "/en/enterprise/2.20/v3/users/gpg_keys": "/en/enterprise-server@2.20/rest/reference/users#gpg-keys", - "/enterprise/2.20/v3/users/keys": "/en/enterprise-server@2.20/rest/reference/users#keys", - "/en/enterprise/2.20/v3/users/keys": "/en/enterprise-server@2.20/rest/reference/users#keys", - "/enterprise/2.20/v4/enum/__directivelocation": "/en/enterprise-server@2.20/graphql/reference/enums#__directivelocation", - "/en/enterprise/2.20/v4/enum/__directivelocation": "/en/enterprise-server@2.20/graphql/reference/enums#__directivelocation", - "/enterprise/2.20/v4/enum/__typekind": "/en/enterprise-server@2.20/graphql/reference/enums#__typekind", - "/en/enterprise/2.20/v4/enum/__typekind": "/en/enterprise-server@2.20/graphql/reference/enums#__typekind", - "/enterprise/2.20/v4/enum/actionexecutioncapabilitysetting": "/en/enterprise-server@2.20/graphql/reference/enums#actionexecutioncapabilitysetting", - "/en/enterprise/2.20/v4/enum/actionexecutioncapabilitysetting": "/en/enterprise-server@2.20/graphql/reference/enums#actionexecutioncapabilitysetting", - "/enterprise/2.20/v4/enum/auditlogorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#auditlogorderfield", - "/en/enterprise/2.20/v4/enum/auditlogorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#auditlogorderfield", - "/enterprise/2.20/v4/enum/checkannotationlevel": "/en/enterprise-server@2.20/graphql/reference/enums#checkannotationlevel", - "/en/enterprise/2.20/v4/enum/checkannotationlevel": "/en/enterprise-server@2.20/graphql/reference/enums#checkannotationlevel", - "/enterprise/2.20/v4/enum/checkconclusionstate": "/en/enterprise-server@2.20/graphql/reference/enums#checkconclusionstate", - "/en/enterprise/2.20/v4/enum/checkconclusionstate": "/en/enterprise-server@2.20/graphql/reference/enums#checkconclusionstate", - "/enterprise/2.20/v4/enum/checkruntype": "/en/enterprise-server@2.20/graphql/reference/enums#checkruntype", - "/en/enterprise/2.20/v4/enum/checkruntype": "/en/enterprise-server@2.20/graphql/reference/enums#checkruntype", - "/enterprise/2.20/v4/enum/checkstatusstate": "/en/enterprise-server@2.20/graphql/reference/enums#checkstatusstate", - "/en/enterprise/2.20/v4/enum/checkstatusstate": "/en/enterprise-server@2.20/graphql/reference/enums#checkstatusstate", - "/enterprise/2.20/v4/enum/collaboratoraffiliation": "/en/enterprise-server@2.20/graphql/reference/enums#collaboratoraffiliation", - "/en/enterprise/2.20/v4/enum/collaboratoraffiliation": "/en/enterprise-server@2.20/graphql/reference/enums#collaboratoraffiliation", - "/enterprise/2.20/v4/enum/commentauthorassociation": "/en/enterprise-server@2.20/graphql/reference/enums#commentauthorassociation", - "/en/enterprise/2.20/v4/enum/commentauthorassociation": "/en/enterprise-server@2.20/graphql/reference/enums#commentauthorassociation", - "/enterprise/2.20/v4/enum/commentcannotupdatereason": "/en/enterprise-server@2.20/graphql/reference/enums#commentcannotupdatereason", - "/en/enterprise/2.20/v4/enum/commentcannotupdatereason": "/en/enterprise-server@2.20/graphql/reference/enums#commentcannotupdatereason", - "/enterprise/2.20/v4/enum/commitcontributionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#commitcontributionorderfield", - "/en/enterprise/2.20/v4/enum/commitcontributionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#commitcontributionorderfield", - "/enterprise/2.20/v4/enum/contributionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#contributionorderfield", - "/en/enterprise/2.20/v4/enum/contributionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#contributionorderfield", - "/enterprise/2.20/v4/enum/defaultrepositorypermissionfield": "/en/enterprise-server@2.20/graphql/reference/enums#defaultrepositorypermissionfield", - "/en/enterprise/2.20/v4/enum/defaultrepositorypermissionfield": "/en/enterprise-server@2.20/graphql/reference/enums#defaultrepositorypermissionfield", - "/enterprise/2.20/v4/enum/deploymentorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#deploymentorderfield", - "/en/enterprise/2.20/v4/enum/deploymentorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#deploymentorderfield", - "/enterprise/2.20/v4/enum/deploymentstate": "/en/enterprise-server@2.20/graphql/reference/enums#deploymentstate", - "/en/enterprise/2.20/v4/enum/deploymentstate": "/en/enterprise-server@2.20/graphql/reference/enums#deploymentstate", - "/enterprise/2.20/v4/enum/deploymentstatusstate": "/en/enterprise-server@2.20/graphql/reference/enums#deploymentstatusstate", - "/en/enterprise/2.20/v4/enum/deploymentstatusstate": "/en/enterprise-server@2.20/graphql/reference/enums#deploymentstatusstate", - "/enterprise/2.20/v4/enum/diffside": "/en/enterprise-server@2.20/graphql/reference/enums#diffside", - "/en/enterprise/2.20/v4/enum/diffside": "/en/enterprise-server@2.20/graphql/reference/enums#diffside", - "/enterprise/2.20/v4/enum/enterpriseadministratorinvitationorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseadministratorinvitationorderfield", - "/en/enterprise/2.20/v4/enum/enterpriseadministratorinvitationorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseadministratorinvitationorderfield", - "/enterprise/2.20/v4/enum/enterpriseadministratorrole": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseadministratorrole", - "/en/enterprise/2.20/v4/enum/enterpriseadministratorrole": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseadministratorrole", - "/enterprise/2.20/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", - "/en/enterprise/2.20/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", - "/enterprise/2.20/v4/enum/enterpriseenableddisabledsettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseenableddisabledsettingvalue", - "/en/enterprise/2.20/v4/enum/enterpriseenableddisabledsettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseenableddisabledsettingvalue", - "/enterprise/2.20/v4/enum/enterpriseenabledsettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseenabledsettingvalue", - "/en/enterprise/2.20/v4/enum/enterpriseenabledsettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseenabledsettingvalue", - "/enterprise/2.20/v4/enum/enterprisememberorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisememberorderfield", - "/en/enterprise/2.20/v4/enum/enterprisememberorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisememberorderfield", - "/enterprise/2.20/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", - "/en/enterprise/2.20/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", - "/enterprise/2.20/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", - "/en/enterprise/2.20/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", - "/enterprise/2.20/v4/enum/enterpriseserveruseraccountemailorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", - "/en/enterprise/2.20/v4/enum/enterpriseserveruseraccountemailorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", - "/enterprise/2.20/v4/enum/enterpriseserveruseraccountorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountorderfield", - "/en/enterprise/2.20/v4/enum/enterpriseserveruseraccountorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountorderfield", - "/enterprise/2.20/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", - "/en/enterprise/2.20/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", - "/enterprise/2.20/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", - "/en/enterprise/2.20/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", - "/enterprise/2.20/v4/enum/enterpriseuseraccountmembershiprole": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseuseraccountmembershiprole", - "/en/enterprise/2.20/v4/enum/enterpriseuseraccountmembershiprole": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseuseraccountmembershiprole", - "/enterprise/2.20/v4/enum/enterpriseuserdeployment": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseuserdeployment", - "/en/enterprise/2.20/v4/enum/enterpriseuserdeployment": "/en/enterprise-server@2.20/graphql/reference/enums#enterpriseuserdeployment", - "/enterprise/2.20/v4/enum/gistorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#gistorderfield", - "/en/enterprise/2.20/v4/enum/gistorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#gistorderfield", - "/enterprise/2.20/v4/enum/gistprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#gistprivacy", - "/en/enterprise/2.20/v4/enum/gistprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#gistprivacy", - "/enterprise/2.20/v4/enum/gitsignaturestate": "/en/enterprise-server@2.20/graphql/reference/enums#gitsignaturestate", - "/en/enterprise/2.20/v4/enum/gitsignaturestate": "/en/enterprise-server@2.20/graphql/reference/enums#gitsignaturestate", - "/enterprise/2.20/v4/enum/identityproviderconfigurationstate": "/en/enterprise-server@2.20/graphql/reference/enums#identityproviderconfigurationstate", - "/en/enterprise/2.20/v4/enum/identityproviderconfigurationstate": "/en/enterprise-server@2.20/graphql/reference/enums#identityproviderconfigurationstate", - "/enterprise/2.20/v4/enum/issueorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#issueorderfield", - "/en/enterprise/2.20/v4/enum/issueorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#issueorderfield", - "/enterprise/2.20/v4/enum/issuestate": "/en/enterprise-server@2.20/graphql/reference/enums#issuestate", - "/en/enterprise/2.20/v4/enum/issuestate": "/en/enterprise-server@2.20/graphql/reference/enums#issuestate", - "/enterprise/2.20/v4/enum/issuetimelineitemsitemtype": "/en/enterprise-server@2.20/graphql/reference/enums#issuetimelineitemsitemtype", - "/en/enterprise/2.20/v4/enum/issuetimelineitemsitemtype": "/en/enterprise-server@2.20/graphql/reference/enums#issuetimelineitemsitemtype", - "/enterprise/2.20/v4/enum/labelorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#labelorderfield", - "/en/enterprise/2.20/v4/enum/labelorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#labelorderfield", - "/enterprise/2.20/v4/enum/languageorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#languageorderfield", - "/en/enterprise/2.20/v4/enum/languageorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#languageorderfield", - "/enterprise/2.20/v4/enum/lockreason": "/en/enterprise-server@2.20/graphql/reference/enums#lockreason", - "/en/enterprise/2.20/v4/enum/lockreason": "/en/enterprise-server@2.20/graphql/reference/enums#lockreason", - "/enterprise/2.20/v4/enum/mergeablestate": "/en/enterprise-server@2.20/graphql/reference/enums#mergeablestate", - "/en/enterprise/2.20/v4/enum/mergeablestate": "/en/enterprise-server@2.20/graphql/reference/enums#mergeablestate", - "/enterprise/2.20/v4/enum/mergestatestatus": "/en/enterprise-server@2.20/graphql/reference/enums#mergestatestatus", - "/en/enterprise/2.20/v4/enum/mergestatestatus": "/en/enterprise-server@2.20/graphql/reference/enums#mergestatestatus", - "/enterprise/2.20/v4/enum/milestoneorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#milestoneorderfield", - "/en/enterprise/2.20/v4/enum/milestoneorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#milestoneorderfield", - "/enterprise/2.20/v4/enum/milestonestate": "/en/enterprise-server@2.20/graphql/reference/enums#milestonestate", - "/en/enterprise/2.20/v4/enum/milestonestate": "/en/enterprise-server@2.20/graphql/reference/enums#milestonestate", - "/enterprise/2.20/v4/enum/oauthapplicationcreateauditentrystate": "/en/enterprise-server@2.20/graphql/reference/enums#oauthapplicationcreateauditentrystate", - "/en/enterprise/2.20/v4/enum/oauthapplicationcreateauditentrystate": "/en/enterprise-server@2.20/graphql/reference/enums#oauthapplicationcreateauditentrystate", - "/enterprise/2.20/v4/enum/operationtype": "/en/enterprise-server@2.20/graphql/reference/enums#operationtype", - "/en/enterprise/2.20/v4/enum/operationtype": "/en/enterprise-server@2.20/graphql/reference/enums#operationtype", - "/enterprise/2.20/v4/enum/orderdirection": "/en/enterprise-server@2.20/graphql/reference/enums#orderdirection", - "/en/enterprise/2.20/v4/enum/orderdirection": "/en/enterprise-server@2.20/graphql/reference/enums#orderdirection", - "/enterprise/2.20/v4/enum/orgaddmemberauditentrypermission": "/en/enterprise-server@2.20/graphql/reference/enums#orgaddmemberauditentrypermission", - "/en/enterprise/2.20/v4/enum/orgaddmemberauditentrypermission": "/en/enterprise-server@2.20/graphql/reference/enums#orgaddmemberauditentrypermission", - "/enterprise/2.20/v4/enum/organizationinvitationrole": "/en/enterprise-server@2.20/graphql/reference/enums#organizationinvitationrole", - "/en/enterprise/2.20/v4/enum/organizationinvitationrole": "/en/enterprise-server@2.20/graphql/reference/enums#organizationinvitationrole", - "/enterprise/2.20/v4/enum/organizationinvitationtype": "/en/enterprise-server@2.20/graphql/reference/enums#organizationinvitationtype", - "/en/enterprise/2.20/v4/enum/organizationinvitationtype": "/en/enterprise-server@2.20/graphql/reference/enums#organizationinvitationtype", - "/enterprise/2.20/v4/enum/organizationmemberrole": "/en/enterprise-server@2.20/graphql/reference/enums#organizationmemberrole", - "/en/enterprise/2.20/v4/enum/organizationmemberrole": "/en/enterprise-server@2.20/graphql/reference/enums#organizationmemberrole", - "/enterprise/2.20/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", - "/en/enterprise/2.20/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/en/enterprise-server@2.20/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", - "/enterprise/2.20/v4/enum/organizationorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#organizationorderfield", - "/en/enterprise/2.20/v4/enum/organizationorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#organizationorderfield", - "/enterprise/2.20/v4/enum/orgcreateauditentrybillingplan": "/en/enterprise-server@2.20/graphql/reference/enums#orgcreateauditentrybillingplan", - "/en/enterprise/2.20/v4/enum/orgcreateauditentrybillingplan": "/en/enterprise-server@2.20/graphql/reference/enums#orgcreateauditentrybillingplan", - "/enterprise/2.20/v4/enum/orgremovebillingmanagerauditentryreason": "/en/enterprise-server@2.20/graphql/reference/enums#orgremovebillingmanagerauditentryreason", - "/en/enterprise/2.20/v4/enum/orgremovebillingmanagerauditentryreason": "/en/enterprise-server@2.20/graphql/reference/enums#orgremovebillingmanagerauditentryreason", - "/enterprise/2.20/v4/enum/orgremovememberauditentrymembershiptype": "/en/enterprise-server@2.20/graphql/reference/enums#orgremovememberauditentrymembershiptype", - "/en/enterprise/2.20/v4/enum/orgremovememberauditentrymembershiptype": "/en/enterprise-server@2.20/graphql/reference/enums#orgremovememberauditentrymembershiptype", - "/enterprise/2.20/v4/enum/orgremovememberauditentryreason": "/en/enterprise-server@2.20/graphql/reference/enums#orgremovememberauditentryreason", - "/en/enterprise/2.20/v4/enum/orgremovememberauditentryreason": "/en/enterprise-server@2.20/graphql/reference/enums#orgremovememberauditentryreason", - "/enterprise/2.20/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/en/enterprise-server@2.20/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", - "/en/enterprise/2.20/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/en/enterprise-server@2.20/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", - "/enterprise/2.20/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/en/enterprise-server@2.20/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", - "/en/enterprise/2.20/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/en/enterprise-server@2.20/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", - "/enterprise/2.20/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/en/enterprise-server@2.20/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", - "/en/enterprise/2.20/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/en/enterprise-server@2.20/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", - "/enterprise/2.20/v4/enum/orgupdatememberauditentrypermission": "/en/enterprise-server@2.20/graphql/reference/enums#orgupdatememberauditentrypermission", - "/en/enterprise/2.20/v4/enum/orgupdatememberauditentrypermission": "/en/enterprise-server@2.20/graphql/reference/enums#orgupdatememberauditentrypermission", - "/enterprise/2.20/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", - "/en/enterprise/2.20/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", - "/enterprise/2.20/v4/enum/packagefileorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#packagefileorderfield", - "/en/enterprise/2.20/v4/enum/packagefileorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#packagefileorderfield", - "/enterprise/2.20/v4/enum/packageorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#packageorderfield", - "/en/enterprise/2.20/v4/enum/packageorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#packageorderfield", - "/enterprise/2.20/v4/enum/packageversionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#packageversionorderfield", - "/en/enterprise/2.20/v4/enum/packageversionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#packageversionorderfield", - "/enterprise/2.20/v4/enum/pinnableitemtype": "/en/enterprise-server@2.20/graphql/reference/enums#pinnableitemtype", - "/en/enterprise/2.20/v4/enum/pinnableitemtype": "/en/enterprise-server@2.20/graphql/reference/enums#pinnableitemtype", - "/enterprise/2.20/v4/enum/projectcardarchivedstate": "/en/enterprise-server@2.20/graphql/reference/enums#projectcardarchivedstate", - "/en/enterprise/2.20/v4/enum/projectcardarchivedstate": "/en/enterprise-server@2.20/graphql/reference/enums#projectcardarchivedstate", - "/enterprise/2.20/v4/enum/projectcardstate": "/en/enterprise-server@2.20/graphql/reference/enums#projectcardstate", - "/en/enterprise/2.20/v4/enum/projectcardstate": "/en/enterprise-server@2.20/graphql/reference/enums#projectcardstate", - "/enterprise/2.20/v4/enum/projectcolumnpurpose": "/en/enterprise-server@2.20/graphql/reference/enums#projectcolumnpurpose", - "/en/enterprise/2.20/v4/enum/projectcolumnpurpose": "/en/enterprise-server@2.20/graphql/reference/enums#projectcolumnpurpose", - "/enterprise/2.20/v4/enum/projectorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#projectorderfield", - "/en/enterprise/2.20/v4/enum/projectorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#projectorderfield", - "/enterprise/2.20/v4/enum/projectstate": "/en/enterprise-server@2.20/graphql/reference/enums#projectstate", - "/en/enterprise/2.20/v4/enum/projectstate": "/en/enterprise-server@2.20/graphql/reference/enums#projectstate", - "/enterprise/2.20/v4/enum/projecttemplate": "/en/enterprise-server@2.20/graphql/reference/enums#projecttemplate", - "/en/enterprise/2.20/v4/enum/projecttemplate": "/en/enterprise-server@2.20/graphql/reference/enums#projecttemplate", - "/enterprise/2.20/v4/enum/pullrequestmergemethod": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestmergemethod", - "/en/enterprise/2.20/v4/enum/pullrequestmergemethod": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestmergemethod", - "/enterprise/2.20/v4/enum/pullrequestorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestorderfield", - "/en/enterprise/2.20/v4/enum/pullrequestorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestorderfield", - "/enterprise/2.20/v4/enum/pullrequestreviewcommentstate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewcommentstate", - "/en/enterprise/2.20/v4/enum/pullrequestreviewcommentstate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewcommentstate", - "/enterprise/2.20/v4/enum/pullrequestreviewevent": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewevent", - "/en/enterprise/2.20/v4/enum/pullrequestreviewevent": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewevent", - "/enterprise/2.20/v4/enum/pullrequestreviewstate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewstate", - "/en/enterprise/2.20/v4/enum/pullrequestreviewstate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewstate", - "/enterprise/2.20/v4/enum/pullrequeststate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequeststate", - "/en/enterprise/2.20/v4/enum/pullrequeststate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequeststate", - "/enterprise/2.20/v4/enum/pullrequesttimelineitemsitemtype": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequesttimelineitemsitemtype", - "/en/enterprise/2.20/v4/enum/pullrequesttimelineitemsitemtype": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequesttimelineitemsitemtype", - "/enterprise/2.20/v4/enum/pullrequestupdatestate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestupdatestate", - "/en/enterprise/2.20/v4/enum/pullrequestupdatestate": "/en/enterprise-server@2.20/graphql/reference/enums#pullrequestupdatestate", - "/enterprise/2.20/v4/enum/reactioncontent": "/en/enterprise-server@2.20/graphql/reference/enums#reactioncontent", - "/en/enterprise/2.20/v4/enum/reactioncontent": "/en/enterprise-server@2.20/graphql/reference/enums#reactioncontent", - "/enterprise/2.20/v4/enum/reactionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#reactionorderfield", - "/en/enterprise/2.20/v4/enum/reactionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#reactionorderfield", - "/enterprise/2.20/v4/enum/reforderfield": "/en/enterprise-server@2.20/graphql/reference/enums#reforderfield", - "/en/enterprise/2.20/v4/enum/reforderfield": "/en/enterprise-server@2.20/graphql/reference/enums#reforderfield", - "/enterprise/2.20/v4/enum/registrypackagedependencytype": "/en/enterprise-server@2.20/graphql/reference/enums#registrypackagedependencytype", - "/en/enterprise/2.20/v4/enum/registrypackagedependencytype": "/en/enterprise-server@2.20/graphql/reference/enums#registrypackagedependencytype", - "/enterprise/2.20/v4/enum/registrypackagetype": "/en/enterprise-server@2.20/graphql/reference/enums#registrypackagetype", - "/en/enterprise/2.20/v4/enum/registrypackagetype": "/en/enterprise-server@2.20/graphql/reference/enums#registrypackagetype", - "/enterprise/2.20/v4/enum/releaseorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#releaseorderfield", - "/en/enterprise/2.20/v4/enum/releaseorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#releaseorderfield", - "/enterprise/2.20/v4/enum/repoaccessauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repoaccessauditentryvisibility", - "/en/enterprise/2.20/v4/enum/repoaccessauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repoaccessauditentryvisibility", - "/enterprise/2.20/v4/enum/repoaddmemberauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repoaddmemberauditentryvisibility", - "/en/enterprise/2.20/v4/enum/repoaddmemberauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repoaddmemberauditentryvisibility", - "/enterprise/2.20/v4/enum/repoarchivedauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repoarchivedauditentryvisibility", - "/en/enterprise/2.20/v4/enum/repoarchivedauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repoarchivedauditentryvisibility", - "/enterprise/2.20/v4/enum/repochangemergesettingauditentrymergetype": "/en/enterprise-server@2.20/graphql/reference/enums#repochangemergesettingauditentrymergetype", - "/en/enterprise/2.20/v4/enum/repochangemergesettingauditentrymergetype": "/en/enterprise-server@2.20/graphql/reference/enums#repochangemergesettingauditentrymergetype", - "/enterprise/2.20/v4/enum/repocreateauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repocreateauditentryvisibility", - "/en/enterprise/2.20/v4/enum/repocreateauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repocreateauditentryvisibility", - "/enterprise/2.20/v4/enum/repodestroyauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repodestroyauditentryvisibility", - "/en/enterprise/2.20/v4/enum/repodestroyauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repodestroyauditentryvisibility", - "/enterprise/2.20/v4/enum/reporemovememberauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#reporemovememberauditentryvisibility", - "/en/enterprise/2.20/v4/enum/reporemovememberauditentryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#reporemovememberauditentryvisibility", - "/enterprise/2.20/v4/enum/reportedcontentclassifiers": "/en/enterprise-server@2.20/graphql/reference/enums#reportedcontentclassifiers", - "/en/enterprise/2.20/v4/enum/reportedcontentclassifiers": "/en/enterprise-server@2.20/graphql/reference/enums#reportedcontentclassifiers", - "/enterprise/2.20/v4/enum/repositoryaffiliation": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryaffiliation", - "/en/enterprise/2.20/v4/enum/repositoryaffiliation": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryaffiliation", - "/enterprise/2.20/v4/enum/repositorycontributiontype": "/en/enterprise-server@2.20/graphql/reference/enums#repositorycontributiontype", - "/en/enterprise/2.20/v4/enum/repositorycontributiontype": "/en/enterprise-server@2.20/graphql/reference/enums#repositorycontributiontype", - "/enterprise/2.20/v4/enum/repositoryinvitationorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryinvitationorderfield", - "/en/enterprise/2.20/v4/enum/repositoryinvitationorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryinvitationorderfield", - "/enterprise/2.20/v4/enum/repositorylockreason": "/en/enterprise-server@2.20/graphql/reference/enums#repositorylockreason", - "/en/enterprise/2.20/v4/enum/repositorylockreason": "/en/enterprise-server@2.20/graphql/reference/enums#repositorylockreason", - "/enterprise/2.20/v4/enum/repositoryorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryorderfield", - "/en/enterprise/2.20/v4/enum/repositoryorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryorderfield", - "/enterprise/2.20/v4/enum/repositorypermission": "/en/enterprise-server@2.20/graphql/reference/enums#repositorypermission", - "/en/enterprise/2.20/v4/enum/repositorypermission": "/en/enterprise-server@2.20/graphql/reference/enums#repositorypermission", - "/enterprise/2.20/v4/enum/repositoryprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryprivacy", - "/en/enterprise/2.20/v4/enum/repositoryprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryprivacy", - "/enterprise/2.20/v4/enum/repositoryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryvisibility", - "/en/enterprise/2.20/v4/enum/repositoryvisibility": "/en/enterprise-server@2.20/graphql/reference/enums#repositoryvisibility", - "/enterprise/2.20/v4/enum/requestablecheckstatusstate": "/en/enterprise-server@2.20/graphql/reference/enums#requestablecheckstatusstate", - "/en/enterprise/2.20/v4/enum/requestablecheckstatusstate": "/en/enterprise-server@2.20/graphql/reference/enums#requestablecheckstatusstate", - "/enterprise/2.20/v4/enum/samldigestalgorithm": "/en/enterprise-server@2.20/graphql/reference/enums#samldigestalgorithm", - "/en/enterprise/2.20/v4/enum/samldigestalgorithm": "/en/enterprise-server@2.20/graphql/reference/enums#samldigestalgorithm", - "/enterprise/2.20/v4/enum/samlsignaturealgorithm": "/en/enterprise-server@2.20/graphql/reference/enums#samlsignaturealgorithm", - "/en/enterprise/2.20/v4/enum/samlsignaturealgorithm": "/en/enterprise-server@2.20/graphql/reference/enums#samlsignaturealgorithm", - "/enterprise/2.20/v4/enum/savedreplyorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#savedreplyorderfield", - "/en/enterprise/2.20/v4/enum/savedreplyorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#savedreplyorderfield", - "/enterprise/2.20/v4/enum/searchtype": "/en/enterprise-server@2.20/graphql/reference/enums#searchtype", - "/en/enterprise/2.20/v4/enum/searchtype": "/en/enterprise-server@2.20/graphql/reference/enums#searchtype", - "/enterprise/2.20/v4/enum/securityadvisoryecosystem": "/en/enterprise-server@2.20/graphql/reference/enums#securityadvisoryecosystem", - "/en/enterprise/2.20/v4/enum/securityadvisoryecosystem": "/en/enterprise-server@2.20/graphql/reference/enums#securityadvisoryecosystem", - "/enterprise/2.20/v4/enum/securityadvisoryseverity": "/en/enterprise-server@2.20/graphql/reference/enums#securityadvisoryseverity", - "/en/enterprise/2.20/v4/enum/securityadvisoryseverity": "/en/enterprise-server@2.20/graphql/reference/enums#securityadvisoryseverity", - "/enterprise/2.20/v4/enum/sponsorshipprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#sponsorshipprivacy", - "/en/enterprise/2.20/v4/enum/sponsorshipprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#sponsorshipprivacy", - "/enterprise/2.20/v4/enum/starorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#starorderfield", - "/en/enterprise/2.20/v4/enum/starorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#starorderfield", - "/enterprise/2.20/v4/enum/statusstate": "/en/enterprise-server@2.20/graphql/reference/enums#statusstate", - "/en/enterprise/2.20/v4/enum/statusstate": "/en/enterprise-server@2.20/graphql/reference/enums#statusstate", - "/enterprise/2.20/v4/enum/subscriptionstate": "/en/enterprise-server@2.20/graphql/reference/enums#subscriptionstate", - "/en/enterprise/2.20/v4/enum/subscriptionstate": "/en/enterprise-server@2.20/graphql/reference/enums#subscriptionstate", - "/enterprise/2.20/v4/enum/teamdiscussioncommentorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamdiscussioncommentorderfield", - "/en/enterprise/2.20/v4/enum/teamdiscussioncommentorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamdiscussioncommentorderfield", - "/enterprise/2.20/v4/enum/teamdiscussionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamdiscussionorderfield", - "/en/enterprise/2.20/v4/enum/teamdiscussionorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamdiscussionorderfield", - "/enterprise/2.20/v4/enum/teammemberorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teammemberorderfield", - "/en/enterprise/2.20/v4/enum/teammemberorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teammemberorderfield", - "/enterprise/2.20/v4/enum/teammemberrole": "/en/enterprise-server@2.20/graphql/reference/enums#teammemberrole", - "/en/enterprise/2.20/v4/enum/teammemberrole": "/en/enterprise-server@2.20/graphql/reference/enums#teammemberrole", - "/enterprise/2.20/v4/enum/teammembershiptype": "/en/enterprise-server@2.20/graphql/reference/enums#teammembershiptype", - "/en/enterprise/2.20/v4/enum/teammembershiptype": "/en/enterprise-server@2.20/graphql/reference/enums#teammembershiptype", - "/enterprise/2.20/v4/enum/teamorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamorderfield", - "/en/enterprise/2.20/v4/enum/teamorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamorderfield", - "/enterprise/2.20/v4/enum/teamprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#teamprivacy", - "/en/enterprise/2.20/v4/enum/teamprivacy": "/en/enterprise-server@2.20/graphql/reference/enums#teamprivacy", - "/enterprise/2.20/v4/enum/teamrepositoryorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamrepositoryorderfield", - "/en/enterprise/2.20/v4/enum/teamrepositoryorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#teamrepositoryorderfield", - "/enterprise/2.20/v4/enum/teamreviewassignmentalgorithm": "/en/enterprise-server@2.20/graphql/reference/enums#teamreviewassignmentalgorithm", - "/en/enterprise/2.20/v4/enum/teamreviewassignmentalgorithm": "/en/enterprise-server@2.20/graphql/reference/enums#teamreviewassignmentalgorithm", - "/enterprise/2.20/v4/enum/teamrole": "/en/enterprise-server@2.20/graphql/reference/enums#teamrole", - "/en/enterprise/2.20/v4/enum/teamrole": "/en/enterprise-server@2.20/graphql/reference/enums#teamrole", - "/enterprise/2.20/v4/enum/userblockduration": "/en/enterprise-server@2.20/graphql/reference/enums#userblockduration", - "/en/enterprise/2.20/v4/enum/userblockduration": "/en/enterprise-server@2.20/graphql/reference/enums#userblockduration", - "/enterprise/2.20/v4/enum/userstatusorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#userstatusorderfield", - "/en/enterprise/2.20/v4/enum/userstatusorderfield": "/en/enterprise-server@2.20/graphql/reference/enums#userstatusorderfield", - "/enterprise/2.20/v4/input_object/addassigneestoassignableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addassigneestoassignableinput", - "/en/enterprise/2.20/v4/input_object/addassigneestoassignableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addassigneestoassignableinput", - "/enterprise/2.20/v4/input_object/addcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addcommentinput", - "/en/enterprise/2.20/v4/input_object/addcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addcommentinput", - "/enterprise/2.20/v4/input_object/addenterpriseadmininput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addenterpriseadmininput", - "/en/enterprise/2.20/v4/input_object/addenterpriseadmininput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addenterpriseadmininput", - "/enterprise/2.20/v4/input_object/addlabelstolabelableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addlabelstolabelableinput", - "/en/enterprise/2.20/v4/input_object/addlabelstolabelableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addlabelstolabelableinput", - "/enterprise/2.20/v4/input_object/addprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addprojectcardinput", - "/en/enterprise/2.20/v4/input_object/addprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addprojectcardinput", - "/enterprise/2.20/v4/input_object/addprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addprojectcolumninput", - "/en/enterprise/2.20/v4/input_object/addprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addprojectcolumninput", - "/enterprise/2.20/v4/input_object/addpullrequestreviewcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewcommentinput", - "/en/enterprise/2.20/v4/input_object/addpullrequestreviewcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewcommentinput", - "/enterprise/2.20/v4/input_object/addpullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewinput", - "/en/enterprise/2.20/v4/input_object/addpullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewinput", - "/enterprise/2.20/v4/input_object/addpullrequestreviewthreadinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewthreadinput", - "/en/enterprise/2.20/v4/input_object/addpullrequestreviewthreadinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewthreadinput", - "/enterprise/2.20/v4/input_object/addreactioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addreactioninput", - "/en/enterprise/2.20/v4/input_object/addreactioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addreactioninput", - "/enterprise/2.20/v4/input_object/addstarinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addstarinput", - "/en/enterprise/2.20/v4/input_object/addstarinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#addstarinput", - "/enterprise/2.20/v4/input_object/archiverepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#archiverepositoryinput", - "/en/enterprise/2.20/v4/input_object/archiverepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#archiverepositoryinput", - "/enterprise/2.20/v4/input_object/auditlogorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#auditlogorder", - "/en/enterprise/2.20/v4/input_object/auditlogorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#auditlogorder", - "/enterprise/2.20/v4/input_object/changeuserstatusinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#changeuserstatusinput", - "/en/enterprise/2.20/v4/input_object/changeuserstatusinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#changeuserstatusinput", - "/enterprise/2.20/v4/input_object/checkannotationdata": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkannotationdata", - "/en/enterprise/2.20/v4/input_object/checkannotationdata": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkannotationdata", - "/enterprise/2.20/v4/input_object/checkannotationrange": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkannotationrange", - "/en/enterprise/2.20/v4/input_object/checkannotationrange": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkannotationrange", - "/enterprise/2.20/v4/input_object/checkrunaction": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunaction", - "/en/enterprise/2.20/v4/input_object/checkrunaction": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunaction", - "/enterprise/2.20/v4/input_object/checkrunfilter": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunfilter", - "/en/enterprise/2.20/v4/input_object/checkrunfilter": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunfilter", - "/enterprise/2.20/v4/input_object/checkrunoutput": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunoutput", - "/en/enterprise/2.20/v4/input_object/checkrunoutput": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunoutput", - "/enterprise/2.20/v4/input_object/checkrunoutputimage": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunoutputimage", - "/en/enterprise/2.20/v4/input_object/checkrunoutputimage": "/en/enterprise-server@2.20/graphql/reference/input-objects#checkrunoutputimage", - "/enterprise/2.20/v4/input_object/checksuiteautotriggerpreference": "/en/enterprise-server@2.20/graphql/reference/input-objects#checksuiteautotriggerpreference", - "/en/enterprise/2.20/v4/input_object/checksuiteautotriggerpreference": "/en/enterprise-server@2.20/graphql/reference/input-objects#checksuiteautotriggerpreference", - "/enterprise/2.20/v4/input_object/checksuitefilter": "/en/enterprise-server@2.20/graphql/reference/input-objects#checksuitefilter", - "/en/enterprise/2.20/v4/input_object/checksuitefilter": "/en/enterprise-server@2.20/graphql/reference/input-objects#checksuitefilter", - "/enterprise/2.20/v4/input_object/clearlabelsfromlabelableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#clearlabelsfromlabelableinput", - "/en/enterprise/2.20/v4/input_object/clearlabelsfromlabelableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#clearlabelsfromlabelableinput", - "/enterprise/2.20/v4/input_object/cloneprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#cloneprojectinput", - "/en/enterprise/2.20/v4/input_object/cloneprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#cloneprojectinput", - "/enterprise/2.20/v4/input_object/clonetemplaterepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#clonetemplaterepositoryinput", - "/en/enterprise/2.20/v4/input_object/clonetemplaterepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#clonetemplaterepositoryinput", - "/enterprise/2.20/v4/input_object/closeissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#closeissueinput", - "/en/enterprise/2.20/v4/input_object/closeissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#closeissueinput", - "/enterprise/2.20/v4/input_object/closepullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#closepullrequestinput", - "/en/enterprise/2.20/v4/input_object/closepullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#closepullrequestinput", - "/enterprise/2.20/v4/input_object/commitauthor": "/en/enterprise-server@2.20/graphql/reference/input-objects#commitauthor", - "/en/enterprise/2.20/v4/input_object/commitauthor": "/en/enterprise-server@2.20/graphql/reference/input-objects#commitauthor", - "/enterprise/2.20/v4/input_object/commitcontributionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#commitcontributionorder", - "/en/enterprise/2.20/v4/input_object/commitcontributionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#commitcontributionorder", - "/enterprise/2.20/v4/input_object/contributionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#contributionorder", - "/en/enterprise/2.20/v4/input_object/contributionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#contributionorder", - "/enterprise/2.20/v4/input_object/convertprojectcardnotetoissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#convertprojectcardnotetoissueinput", - "/en/enterprise/2.20/v4/input_object/convertprojectcardnotetoissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#convertprojectcardnotetoissueinput", - "/enterprise/2.20/v4/input_object/createbranchprotectionruleinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createbranchprotectionruleinput", - "/en/enterprise/2.20/v4/input_object/createbranchprotectionruleinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createbranchprotectionruleinput", - "/enterprise/2.20/v4/input_object/createcheckruninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createcheckruninput", - "/en/enterprise/2.20/v4/input_object/createcheckruninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createcheckruninput", - "/enterprise/2.20/v4/input_object/createchecksuiteinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createchecksuiteinput", - "/en/enterprise/2.20/v4/input_object/createchecksuiteinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createchecksuiteinput", - "/enterprise/2.20/v4/input_object/createcontentattachmentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createcontentattachmentinput", - "/en/enterprise/2.20/v4/input_object/createcontentattachmentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createcontentattachmentinput", - "/enterprise/2.20/v4/input_object/createdeploymentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createdeploymentinput", - "/en/enterprise/2.20/v4/input_object/createdeploymentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createdeploymentinput", - "/enterprise/2.20/v4/input_object/createdeploymentstatusinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createdeploymentstatusinput", - "/en/enterprise/2.20/v4/input_object/createdeploymentstatusinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createdeploymentstatusinput", - "/enterprise/2.20/v4/input_object/createissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createissueinput", - "/en/enterprise/2.20/v4/input_object/createissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createissueinput", - "/enterprise/2.20/v4/input_object/createlabelinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createlabelinput", - "/en/enterprise/2.20/v4/input_object/createlabelinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createlabelinput", - "/enterprise/2.20/v4/input_object/createprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createprojectinput", - "/en/enterprise/2.20/v4/input_object/createprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createprojectinput", - "/enterprise/2.20/v4/input_object/createpullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createpullrequestinput", - "/en/enterprise/2.20/v4/input_object/createpullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createpullrequestinput", - "/enterprise/2.20/v4/input_object/createrefinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createrefinput", - "/en/enterprise/2.20/v4/input_object/createrefinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createrefinput", - "/enterprise/2.20/v4/input_object/createrepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createrepositoryinput", - "/en/enterprise/2.20/v4/input_object/createrepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createrepositoryinput", - "/enterprise/2.20/v4/input_object/createteamdiscussioncommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createteamdiscussioncommentinput", - "/en/enterprise/2.20/v4/input_object/createteamdiscussioncommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createteamdiscussioncommentinput", - "/enterprise/2.20/v4/input_object/createteamdiscussioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createteamdiscussioninput", - "/en/enterprise/2.20/v4/input_object/createteamdiscussioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#createteamdiscussioninput", - "/enterprise/2.20/v4/input_object/deletebranchprotectionruleinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletebranchprotectionruleinput", - "/en/enterprise/2.20/v4/input_object/deletebranchprotectionruleinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletebranchprotectionruleinput", - "/enterprise/2.20/v4/input_object/deleteissuecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteissuecommentinput", - "/en/enterprise/2.20/v4/input_object/deleteissuecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteissuecommentinput", - "/enterprise/2.20/v4/input_object/deleteissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteissueinput", - "/en/enterprise/2.20/v4/input_object/deleteissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteissueinput", - "/enterprise/2.20/v4/input_object/deletelabelinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletelabelinput", - "/en/enterprise/2.20/v4/input_object/deletelabelinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletelabelinput", - "/enterprise/2.20/v4/input_object/deleteprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectcardinput", - "/en/enterprise/2.20/v4/input_object/deleteprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectcardinput", - "/enterprise/2.20/v4/input_object/deleteprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectcolumninput", - "/en/enterprise/2.20/v4/input_object/deleteprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectcolumninput", - "/enterprise/2.20/v4/input_object/deleteprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectinput", - "/en/enterprise/2.20/v4/input_object/deleteprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectinput", - "/enterprise/2.20/v4/input_object/deletepullrequestreviewcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletepullrequestreviewcommentinput", - "/en/enterprise/2.20/v4/input_object/deletepullrequestreviewcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletepullrequestreviewcommentinput", - "/enterprise/2.20/v4/input_object/deletepullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletepullrequestreviewinput", - "/en/enterprise/2.20/v4/input_object/deletepullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deletepullrequestreviewinput", - "/enterprise/2.20/v4/input_object/deleterefinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleterefinput", - "/en/enterprise/2.20/v4/input_object/deleterefinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleterefinput", - "/enterprise/2.20/v4/input_object/deleteteamdiscussioncommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteteamdiscussioncommentinput", - "/en/enterprise/2.20/v4/input_object/deleteteamdiscussioncommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteteamdiscussioncommentinput", - "/enterprise/2.20/v4/input_object/deleteteamdiscussioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteteamdiscussioninput", - "/en/enterprise/2.20/v4/input_object/deleteteamdiscussioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#deleteteamdiscussioninput", - "/enterprise/2.20/v4/input_object/deploymentorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#deploymentorder", - "/en/enterprise/2.20/v4/input_object/deploymentorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#deploymentorder", - "/enterprise/2.20/v4/input_object/dismisspullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#dismisspullrequestreviewinput", - "/en/enterprise/2.20/v4/input_object/dismisspullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#dismisspullrequestreviewinput", - "/enterprise/2.20/v4/input_object/draftpullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/input-objects#draftpullrequestreviewcomment", - "/en/enterprise/2.20/v4/input_object/draftpullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/input-objects#draftpullrequestreviewcomment", - "/enterprise/2.20/v4/input_object/draftpullrequestreviewthread": "/en/enterprise-server@2.20/graphql/reference/input-objects#draftpullrequestreviewthread", - "/en/enterprise/2.20/v4/input_object/draftpullrequestreviewthread": "/en/enterprise-server@2.20/graphql/reference/input-objects#draftpullrequestreviewthread", - "/enterprise/2.20/v4/input_object/enterpriseadministratorinvitationorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseadministratorinvitationorder", - "/en/enterprise/2.20/v4/input_object/enterpriseadministratorinvitationorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseadministratorinvitationorder", - "/enterprise/2.20/v4/input_object/enterprisememberorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterprisememberorder", - "/en/enterprise/2.20/v4/input_object/enterprisememberorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterprisememberorder", - "/enterprise/2.20/v4/input_object/enterpriseserveruseraccountemailorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", - "/en/enterprise/2.20/v4/input_object/enterpriseserveruseraccountemailorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", - "/enterprise/2.20/v4/input_object/enterpriseserveruseraccountorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountorder", - "/en/enterprise/2.20/v4/input_object/enterpriseserveruseraccountorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountorder", - "/enterprise/2.20/v4/input_object/enterpriseserveruseraccountsuploadorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", - "/en/enterprise/2.20/v4/input_object/enterpriseserveruseraccountsuploadorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", - "/enterprise/2.20/v4/input_object/followuserinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#followuserinput", - "/en/enterprise/2.20/v4/input_object/followuserinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#followuserinput", - "/enterprise/2.20/v4/input_object/gistorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#gistorder", - "/en/enterprise/2.20/v4/input_object/gistorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#gistorder", - "/enterprise/2.20/v4/input_object/importprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#importprojectinput", - "/en/enterprise/2.20/v4/input_object/importprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#importprojectinput", - "/enterprise/2.20/v4/input_object/issuefilters": "/en/enterprise-server@2.20/graphql/reference/input-objects#issuefilters", - "/en/enterprise/2.20/v4/input_object/issuefilters": "/en/enterprise-server@2.20/graphql/reference/input-objects#issuefilters", - "/enterprise/2.20/v4/input_object/issueorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#issueorder", - "/en/enterprise/2.20/v4/input_object/issueorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#issueorder", - "/enterprise/2.20/v4/input_object/labelorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#labelorder", - "/en/enterprise/2.20/v4/input_object/labelorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#labelorder", - "/enterprise/2.20/v4/input_object/languageorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#languageorder", - "/en/enterprise/2.20/v4/input_object/languageorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#languageorder", - "/enterprise/2.20/v4/input_object/linkrepositorytoprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#linkrepositorytoprojectinput", - "/en/enterprise/2.20/v4/input_object/linkrepositorytoprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#linkrepositorytoprojectinput", - "/enterprise/2.20/v4/input_object/locklockableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#locklockableinput", - "/en/enterprise/2.20/v4/input_object/locklockableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#locklockableinput", - "/enterprise/2.20/v4/input_object/markpullrequestreadyforreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#markpullrequestreadyforreviewinput", - "/en/enterprise/2.20/v4/input_object/markpullrequestreadyforreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#markpullrequestreadyforreviewinput", - "/enterprise/2.20/v4/input_object/mergebranchinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#mergebranchinput", - "/en/enterprise/2.20/v4/input_object/mergebranchinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#mergebranchinput", - "/enterprise/2.20/v4/input_object/mergepullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#mergepullrequestinput", - "/en/enterprise/2.20/v4/input_object/mergepullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#mergepullrequestinput", - "/enterprise/2.20/v4/input_object/milestoneorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#milestoneorder", - "/en/enterprise/2.20/v4/input_object/milestoneorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#milestoneorder", - "/enterprise/2.20/v4/input_object/minimizecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#minimizecommentinput", - "/en/enterprise/2.20/v4/input_object/minimizecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#minimizecommentinput", - "/enterprise/2.20/v4/input_object/moveprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#moveprojectcardinput", - "/en/enterprise/2.20/v4/input_object/moveprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#moveprojectcardinput", - "/enterprise/2.20/v4/input_object/moveprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#moveprojectcolumninput", - "/en/enterprise/2.20/v4/input_object/moveprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#moveprojectcolumninput", - "/enterprise/2.20/v4/input_object/organizationorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#organizationorder", - "/en/enterprise/2.20/v4/input_object/organizationorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#organizationorder", - "/enterprise/2.20/v4/input_object/packagefileorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#packagefileorder", - "/en/enterprise/2.20/v4/input_object/packagefileorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#packagefileorder", - "/enterprise/2.20/v4/input_object/packageorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#packageorder", - "/en/enterprise/2.20/v4/input_object/packageorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#packageorder", - "/enterprise/2.20/v4/input_object/packageversionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#packageversionorder", - "/en/enterprise/2.20/v4/input_object/packageversionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#packageversionorder", - "/enterprise/2.20/v4/input_object/pinissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#pinissueinput", - "/en/enterprise/2.20/v4/input_object/pinissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#pinissueinput", - "/enterprise/2.20/v4/input_object/projectcardimport": "/en/enterprise-server@2.20/graphql/reference/input-objects#projectcardimport", - "/en/enterprise/2.20/v4/input_object/projectcardimport": "/en/enterprise-server@2.20/graphql/reference/input-objects#projectcardimport", - "/enterprise/2.20/v4/input_object/projectcolumnimport": "/en/enterprise-server@2.20/graphql/reference/input-objects#projectcolumnimport", - "/en/enterprise/2.20/v4/input_object/projectcolumnimport": "/en/enterprise-server@2.20/graphql/reference/input-objects#projectcolumnimport", - "/enterprise/2.20/v4/input_object/projectorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#projectorder", - "/en/enterprise/2.20/v4/input_object/projectorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#projectorder", - "/enterprise/2.20/v4/input_object/pullrequestorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#pullrequestorder", - "/en/enterprise/2.20/v4/input_object/pullrequestorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#pullrequestorder", - "/enterprise/2.20/v4/input_object/reactionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#reactionorder", - "/en/enterprise/2.20/v4/input_object/reactionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#reactionorder", - "/enterprise/2.20/v4/input_object/reforder": "/en/enterprise-server@2.20/graphql/reference/input-objects#reforder", - "/en/enterprise/2.20/v4/input_object/reforder": "/en/enterprise-server@2.20/graphql/reference/input-objects#reforder", - "/enterprise/2.20/v4/input_object/refupdate": "/en/enterprise-server@2.20/graphql/reference/input-objects#refupdate", - "/en/enterprise/2.20/v4/input_object/refupdate": "/en/enterprise-server@2.20/graphql/reference/input-objects#refupdate", - "/enterprise/2.20/v4/input_object/registrypackagemetadatum": "/en/enterprise-server@2.20/graphql/reference/input-objects#registrypackagemetadatum", - "/en/enterprise/2.20/v4/input_object/registrypackagemetadatum": "/en/enterprise-server@2.20/graphql/reference/input-objects#registrypackagemetadatum", - "/enterprise/2.20/v4/input_object/releaseorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#releaseorder", - "/en/enterprise/2.20/v4/input_object/releaseorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#releaseorder", - "/enterprise/2.20/v4/input_object/removeassigneesfromassignableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removeassigneesfromassignableinput", - "/en/enterprise/2.20/v4/input_object/removeassigneesfromassignableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removeassigneesfromassignableinput", - "/enterprise/2.20/v4/input_object/removeenterpriseadmininput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removeenterpriseadmininput", - "/en/enterprise/2.20/v4/input_object/removeenterpriseadmininput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removeenterpriseadmininput", - "/enterprise/2.20/v4/input_object/removelabelsfromlabelableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removelabelsfromlabelableinput", - "/en/enterprise/2.20/v4/input_object/removelabelsfromlabelableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removelabelsfromlabelableinput", - "/enterprise/2.20/v4/input_object/removeoutsidecollaboratorinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removeoutsidecollaboratorinput", - "/en/enterprise/2.20/v4/input_object/removeoutsidecollaboratorinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removeoutsidecollaboratorinput", - "/enterprise/2.20/v4/input_object/removereactioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removereactioninput", - "/en/enterprise/2.20/v4/input_object/removereactioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removereactioninput", - "/enterprise/2.20/v4/input_object/removestarinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removestarinput", - "/en/enterprise/2.20/v4/input_object/removestarinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#removestarinput", - "/enterprise/2.20/v4/input_object/reopenissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#reopenissueinput", - "/en/enterprise/2.20/v4/input_object/reopenissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#reopenissueinput", - "/enterprise/2.20/v4/input_object/reopenpullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#reopenpullrequestinput", - "/en/enterprise/2.20/v4/input_object/reopenpullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#reopenpullrequestinput", - "/enterprise/2.20/v4/input_object/repositoryinvitationorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#repositoryinvitationorder", - "/en/enterprise/2.20/v4/input_object/repositoryinvitationorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#repositoryinvitationorder", - "/enterprise/2.20/v4/input_object/repositoryorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#repositoryorder", - "/en/enterprise/2.20/v4/input_object/repositoryorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#repositoryorder", - "/enterprise/2.20/v4/input_object/requestreviewsinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#requestreviewsinput", - "/en/enterprise/2.20/v4/input_object/requestreviewsinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#requestreviewsinput", - "/enterprise/2.20/v4/input_object/rerequestchecksuiteinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#rerequestchecksuiteinput", - "/en/enterprise/2.20/v4/input_object/rerequestchecksuiteinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#rerequestchecksuiteinput", - "/enterprise/2.20/v4/input_object/resolvereviewthreadinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#resolvereviewthreadinput", - "/en/enterprise/2.20/v4/input_object/resolvereviewthreadinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#resolvereviewthreadinput", - "/enterprise/2.20/v4/input_object/savedreplyorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#savedreplyorder", - "/en/enterprise/2.20/v4/input_object/savedreplyorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#savedreplyorder", - "/enterprise/2.20/v4/input_object/sponsorshiporder": "/en/enterprise-server@2.20/graphql/reference/input-objects#sponsorshiporder", - "/en/enterprise/2.20/v4/input_object/sponsorshiporder": "/en/enterprise-server@2.20/graphql/reference/input-objects#sponsorshiporder", - "/enterprise/2.20/v4/input_object/starorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#starorder", - "/en/enterprise/2.20/v4/input_object/starorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#starorder", - "/enterprise/2.20/v4/input_object/submitpullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#submitpullrequestreviewinput", - "/en/enterprise/2.20/v4/input_object/submitpullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#submitpullrequestreviewinput", - "/enterprise/2.20/v4/input_object/teamdiscussioncommentorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamdiscussioncommentorder", - "/en/enterprise/2.20/v4/input_object/teamdiscussioncommentorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamdiscussioncommentorder", - "/enterprise/2.20/v4/input_object/teamdiscussionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamdiscussionorder", - "/en/enterprise/2.20/v4/input_object/teamdiscussionorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamdiscussionorder", - "/enterprise/2.20/v4/input_object/teammemberorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teammemberorder", - "/en/enterprise/2.20/v4/input_object/teammemberorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teammemberorder", - "/enterprise/2.20/v4/input_object/teamorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamorder", - "/en/enterprise/2.20/v4/input_object/teamorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamorder", - "/enterprise/2.20/v4/input_object/teamrepositoryorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamrepositoryorder", - "/en/enterprise/2.20/v4/input_object/teamrepositoryorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#teamrepositoryorder", - "/enterprise/2.20/v4/input_object/transferissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#transferissueinput", - "/en/enterprise/2.20/v4/input_object/transferissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#transferissueinput", - "/enterprise/2.20/v4/input_object/unarchiverepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unarchiverepositoryinput", - "/en/enterprise/2.20/v4/input_object/unarchiverepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unarchiverepositoryinput", - "/enterprise/2.20/v4/input_object/unfollowuserinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unfollowuserinput", - "/en/enterprise/2.20/v4/input_object/unfollowuserinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unfollowuserinput", - "/enterprise/2.20/v4/input_object/unlinkrepositoryfromprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", - "/en/enterprise/2.20/v4/input_object/unlinkrepositoryfromprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", - "/enterprise/2.20/v4/input_object/unlocklockableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unlocklockableinput", - "/en/enterprise/2.20/v4/input_object/unlocklockableinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unlocklockableinput", - "/enterprise/2.20/v4/input_object/unmarkissueasduplicateinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unmarkissueasduplicateinput", - "/en/enterprise/2.20/v4/input_object/unmarkissueasduplicateinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unmarkissueasduplicateinput", - "/enterprise/2.20/v4/input_object/unminimizecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unminimizecommentinput", - "/en/enterprise/2.20/v4/input_object/unminimizecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unminimizecommentinput", - "/enterprise/2.20/v4/input_object/unpinissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unpinissueinput", - "/en/enterprise/2.20/v4/input_object/unpinissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unpinissueinput", - "/enterprise/2.20/v4/input_object/unresolvereviewthreadinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unresolvereviewthreadinput", - "/en/enterprise/2.20/v4/input_object/unresolvereviewthreadinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#unresolvereviewthreadinput", - "/enterprise/2.20/v4/input_object/updatebranchprotectionruleinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatebranchprotectionruleinput", - "/en/enterprise/2.20/v4/input_object/updatebranchprotectionruleinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatebranchprotectionruleinput", - "/enterprise/2.20/v4/input_object/updatecheckruninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatecheckruninput", - "/en/enterprise/2.20/v4/input_object/updatecheckruninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatecheckruninput", - "/enterprise/2.20/v4/input_object/updatechecksuitepreferencesinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatechecksuitepreferencesinput", - "/en/enterprise/2.20/v4/input_object/updatechecksuitepreferencesinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatechecksuitepreferencesinput", - "/enterprise/2.20/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", - "/enterprise/2.20/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", - "/enterprise/2.20/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", - "/enterprise/2.20/v4/input_object/updateenterpriseprofileinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseprofileinput", - "/en/enterprise/2.20/v4/input_object/updateenterpriseprofileinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseprofileinput", - "/enterprise/2.20/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", - "/enterprise/2.20/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", - "/enterprise/2.20/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", - "/en/enterprise/2.20/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", - "/enterprise/2.20/v4/input_object/updateissuecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateissuecommentinput", - "/en/enterprise/2.20/v4/input_object/updateissuecommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateissuecommentinput", - "/enterprise/2.20/v4/input_object/updateissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateissueinput", - "/en/enterprise/2.20/v4/input_object/updateissueinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateissueinput", - "/enterprise/2.20/v4/input_object/updatelabelinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatelabelinput", - "/en/enterprise/2.20/v4/input_object/updatelabelinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatelabelinput", - "/enterprise/2.20/v4/input_object/updateprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateprojectcardinput", - "/en/enterprise/2.20/v4/input_object/updateprojectcardinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateprojectcardinput", - "/enterprise/2.20/v4/input_object/updateprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateprojectcolumninput", - "/en/enterprise/2.20/v4/input_object/updateprojectcolumninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateprojectcolumninput", - "/enterprise/2.20/v4/input_object/updateprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateprojectinput", - "/en/enterprise/2.20/v4/input_object/updateprojectinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateprojectinput", - "/enterprise/2.20/v4/input_object/updatepullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestinput", - "/en/enterprise/2.20/v4/input_object/updatepullrequestinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestinput", - "/enterprise/2.20/v4/input_object/updatepullrequestreviewcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestreviewcommentinput", - "/en/enterprise/2.20/v4/input_object/updatepullrequestreviewcommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestreviewcommentinput", - "/enterprise/2.20/v4/input_object/updatepullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestreviewinput", - "/en/enterprise/2.20/v4/input_object/updatepullrequestreviewinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestreviewinput", - "/enterprise/2.20/v4/input_object/updaterefinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updaterefinput", - "/en/enterprise/2.20/v4/input_object/updaterefinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updaterefinput", - "/enterprise/2.20/v4/input_object/updaterefsinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updaterefsinput", - "/en/enterprise/2.20/v4/input_object/updaterefsinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updaterefsinput", - "/enterprise/2.20/v4/input_object/updaterepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updaterepositoryinput", - "/en/enterprise/2.20/v4/input_object/updaterepositoryinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updaterepositoryinput", - "/enterprise/2.20/v4/input_object/updatesubscriptioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatesubscriptioninput", - "/en/enterprise/2.20/v4/input_object/updatesubscriptioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatesubscriptioninput", - "/enterprise/2.20/v4/input_object/updateteamdiscussioncommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateteamdiscussioncommentinput", - "/en/enterprise/2.20/v4/input_object/updateteamdiscussioncommentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateteamdiscussioncommentinput", - "/enterprise/2.20/v4/input_object/updateteamdiscussioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateteamdiscussioninput", - "/en/enterprise/2.20/v4/input_object/updateteamdiscussioninput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateteamdiscussioninput", - "/enterprise/2.20/v4/input_object/updateteamreviewassignmentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateteamreviewassignmentinput", - "/en/enterprise/2.20/v4/input_object/updateteamreviewassignmentinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updateteamreviewassignmentinput", - "/enterprise/2.20/v4/input_object/updatetopicsinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatetopicsinput", - "/en/enterprise/2.20/v4/input_object/updatetopicsinput": "/en/enterprise-server@2.20/graphql/reference/input-objects#updatetopicsinput", - "/enterprise/2.20/v4/input_object/userstatusorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#userstatusorder", - "/en/enterprise/2.20/v4/input_object/userstatusorder": "/en/enterprise-server@2.20/graphql/reference/input-objects#userstatusorder", - "/enterprise/2.20/v4/interface/actor": "/en/enterprise-server@2.20/graphql/reference/interfaces#actor", - "/en/enterprise/2.20/v4/interface/actor": "/en/enterprise-server@2.20/graphql/reference/interfaces#actor", - "/enterprise/2.20/v4/interface/assignable": "/en/enterprise-server@2.20/graphql/reference/interfaces#assignable", - "/en/enterprise/2.20/v4/interface/assignable": "/en/enterprise-server@2.20/graphql/reference/interfaces#assignable", - "/enterprise/2.20/v4/interface/auditentry": "/en/enterprise-server@2.20/graphql/reference/interfaces#auditentry", - "/en/enterprise/2.20/v4/interface/auditentry": "/en/enterprise-server@2.20/graphql/reference/interfaces#auditentry", - "/enterprise/2.20/v4/interface/closable": "/en/enterprise-server@2.20/graphql/reference/interfaces#closable", - "/en/enterprise/2.20/v4/interface/closable": "/en/enterprise-server@2.20/graphql/reference/interfaces#closable", - "/enterprise/2.20/v4/interface/comment": "/en/enterprise-server@2.20/graphql/reference/interfaces#comment", - "/en/enterprise/2.20/v4/interface/comment": "/en/enterprise-server@2.20/graphql/reference/interfaces#comment", - "/enterprise/2.20/v4/interface/contribution": "/en/enterprise-server@2.20/graphql/reference/interfaces#contribution", - "/en/enterprise/2.20/v4/interface/contribution": "/en/enterprise-server@2.20/graphql/reference/interfaces#contribution", - "/enterprise/2.20/v4/interface/deletable": "/en/enterprise-server@2.20/graphql/reference/interfaces#deletable", - "/en/enterprise/2.20/v4/interface/deletable": "/en/enterprise-server@2.20/graphql/reference/interfaces#deletable", - "/enterprise/2.20/v4/interface/enterpriseauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#enterpriseauditentrydata", - "/en/enterprise/2.20/v4/interface/enterpriseauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#enterpriseauditentrydata", - "/enterprise/2.20/v4/interface/gitobject": "/en/enterprise-server@2.20/graphql/reference/interfaces#gitobject", - "/en/enterprise/2.20/v4/interface/gitobject": "/en/enterprise-server@2.20/graphql/reference/interfaces#gitobject", - "/enterprise/2.20/v4/interface/gitsignature": "/en/enterprise-server@2.20/graphql/reference/interfaces#gitsignature", - "/en/enterprise/2.20/v4/interface/gitsignature": "/en/enterprise-server@2.20/graphql/reference/interfaces#gitsignature", - "/enterprise/2.20/v4/interface/hovercardcontext": "/en/enterprise-server@2.20/graphql/reference/interfaces#hovercardcontext", - "/en/enterprise/2.20/v4/interface/hovercardcontext": "/en/enterprise-server@2.20/graphql/reference/interfaces#hovercardcontext", - "/enterprise/2.20/v4/interface/labelable": "/en/enterprise-server@2.20/graphql/reference/interfaces#labelable", - "/en/enterprise/2.20/v4/interface/labelable": "/en/enterprise-server@2.20/graphql/reference/interfaces#labelable", - "/enterprise/2.20/v4/interface/lockable": "/en/enterprise-server@2.20/graphql/reference/interfaces#lockable", - "/en/enterprise/2.20/v4/interface/lockable": "/en/enterprise-server@2.20/graphql/reference/interfaces#lockable", - "/enterprise/2.20/v4/interface/memberstatusable": "/en/enterprise-server@2.20/graphql/reference/interfaces#memberstatusable", - "/en/enterprise/2.20/v4/interface/memberstatusable": "/en/enterprise-server@2.20/graphql/reference/interfaces#memberstatusable", - "/enterprise/2.20/v4/interface/minimizable": "/en/enterprise-server@2.20/graphql/reference/interfaces#minimizable", - "/en/enterprise/2.20/v4/interface/minimizable": "/en/enterprise-server@2.20/graphql/reference/interfaces#minimizable", - "/enterprise/2.20/v4/interface/node": "/en/enterprise-server@2.20/graphql/reference/interfaces#node", - "/en/enterprise/2.20/v4/interface/node": "/en/enterprise-server@2.20/graphql/reference/interfaces#node", - "/enterprise/2.20/v4/interface/oauthapplicationauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#oauthapplicationauditentrydata", - "/en/enterprise/2.20/v4/interface/oauthapplicationauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#oauthapplicationauditentrydata", - "/enterprise/2.20/v4/interface/organizationauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#organizationauditentrydata", - "/en/enterprise/2.20/v4/interface/organizationauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#organizationauditentrydata", - "/enterprise/2.20/v4/interface/packageowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#packageowner", - "/en/enterprise/2.20/v4/interface/packageowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#packageowner", - "/enterprise/2.20/v4/interface/profileowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#profileowner", - "/en/enterprise/2.20/v4/interface/profileowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#profileowner", - "/enterprise/2.20/v4/interface/projectowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#projectowner", - "/en/enterprise/2.20/v4/interface/projectowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#projectowner", - "/enterprise/2.20/v4/interface/reactable": "/en/enterprise-server@2.20/graphql/reference/interfaces#reactable", - "/en/enterprise/2.20/v4/interface/reactable": "/en/enterprise-server@2.20/graphql/reference/interfaces#reactable", - "/enterprise/2.20/v4/interface/registrypackageowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#registrypackageowner", - "/en/enterprise/2.20/v4/interface/registrypackageowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#registrypackageowner", - "/enterprise/2.20/v4/interface/registrypackagesearch": "/en/enterprise-server@2.20/graphql/reference/interfaces#registrypackagesearch", - "/en/enterprise/2.20/v4/interface/registrypackagesearch": "/en/enterprise-server@2.20/graphql/reference/interfaces#registrypackagesearch", - "/enterprise/2.20/v4/interface/repositoryauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositoryauditentrydata", - "/en/enterprise/2.20/v4/interface/repositoryauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositoryauditentrydata", - "/enterprise/2.20/v4/interface/repositoryinfo": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositoryinfo", - "/en/enterprise/2.20/v4/interface/repositoryinfo": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositoryinfo", - "/enterprise/2.20/v4/interface/repositorynode": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositorynode", - "/en/enterprise/2.20/v4/interface/repositorynode": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositorynode", - "/enterprise/2.20/v4/interface/repositoryowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositoryowner", - "/en/enterprise/2.20/v4/interface/repositoryowner": "/en/enterprise-server@2.20/graphql/reference/interfaces#repositoryowner", - "/enterprise/2.20/v4/interface/starrable": "/en/enterprise-server@2.20/graphql/reference/interfaces#starrable", - "/en/enterprise/2.20/v4/interface/starrable": "/en/enterprise-server@2.20/graphql/reference/interfaces#starrable", - "/enterprise/2.20/v4/interface/subscribable": "/en/enterprise-server@2.20/graphql/reference/interfaces#subscribable", - "/en/enterprise/2.20/v4/interface/subscribable": "/en/enterprise-server@2.20/graphql/reference/interfaces#subscribable", - "/enterprise/2.20/v4/interface/teamauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#teamauditentrydata", - "/en/enterprise/2.20/v4/interface/teamauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#teamauditentrydata", - "/enterprise/2.20/v4/interface/topicauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#topicauditentrydata", - "/en/enterprise/2.20/v4/interface/topicauditentrydata": "/en/enterprise-server@2.20/graphql/reference/interfaces#topicauditentrydata", - "/enterprise/2.20/v4/interface/uniformresourcelocatable": "/en/enterprise-server@2.20/graphql/reference/interfaces#uniformresourcelocatable", - "/en/enterprise/2.20/v4/interface/uniformresourcelocatable": "/en/enterprise-server@2.20/graphql/reference/interfaces#uniformresourcelocatable", - "/enterprise/2.20/v4/interface/updatable": "/en/enterprise-server@2.20/graphql/reference/interfaces#updatable", - "/en/enterprise/2.20/v4/interface/updatable": "/en/enterprise-server@2.20/graphql/reference/interfaces#updatable", - "/enterprise/2.20/v4/interface/updatablecomment": "/en/enterprise-server@2.20/graphql/reference/interfaces#updatablecomment", - "/en/enterprise/2.20/v4/interface/updatablecomment": "/en/enterprise-server@2.20/graphql/reference/interfaces#updatablecomment", - "/enterprise/2.20/v4/mutation/addassigneestoassignable": "/en/enterprise-server@2.20/graphql/reference/mutations#addassigneestoassignable", - "/en/enterprise/2.20/v4/mutation/addassigneestoassignable": "/en/enterprise-server@2.20/graphql/reference/mutations#addassigneestoassignable", - "/enterprise/2.20/v4/mutation/addcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#addcomment", - "/en/enterprise/2.20/v4/mutation/addcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#addcomment", - "/enterprise/2.20/v4/mutation/addenterpriseadmin": "/en/enterprise-server@2.20/graphql/reference/mutations#addenterpriseadmin", - "/en/enterprise/2.20/v4/mutation/addenterpriseadmin": "/en/enterprise-server@2.20/graphql/reference/mutations#addenterpriseadmin", - "/enterprise/2.20/v4/mutation/addlabelstolabelable": "/en/enterprise-server@2.20/graphql/reference/mutations#addlabelstolabelable", - "/en/enterprise/2.20/v4/mutation/addlabelstolabelable": "/en/enterprise-server@2.20/graphql/reference/mutations#addlabelstolabelable", - "/enterprise/2.20/v4/mutation/addprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#addprojectcard", - "/en/enterprise/2.20/v4/mutation/addprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#addprojectcard", - "/enterprise/2.20/v4/mutation/addprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#addprojectcolumn", - "/en/enterprise/2.20/v4/mutation/addprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#addprojectcolumn", - "/enterprise/2.20/v4/mutation/addpullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreview", - "/en/enterprise/2.20/v4/mutation/addpullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreview", - "/enterprise/2.20/v4/mutation/addpullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreviewcomment", - "/en/enterprise/2.20/v4/mutation/addpullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreviewcomment", - "/enterprise/2.20/v4/mutation/addpullrequestreviewthread": "/en/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreviewthread", - "/en/enterprise/2.20/v4/mutation/addpullrequestreviewthread": "/en/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreviewthread", - "/enterprise/2.20/v4/mutation/addreaction": "/en/enterprise-server@2.20/graphql/reference/mutations#addreaction", - "/en/enterprise/2.20/v4/mutation/addreaction": "/en/enterprise-server@2.20/graphql/reference/mutations#addreaction", - "/enterprise/2.20/v4/mutation/addstar": "/en/enterprise-server@2.20/graphql/reference/mutations#addstar", - "/en/enterprise/2.20/v4/mutation/addstar": "/en/enterprise-server@2.20/graphql/reference/mutations#addstar", - "/enterprise/2.20/v4/mutation/archiverepository": "/en/enterprise-server@2.20/graphql/reference/mutations#archiverepository", - "/en/enterprise/2.20/v4/mutation/archiverepository": "/en/enterprise-server@2.20/graphql/reference/mutations#archiverepository", - "/enterprise/2.20/v4/mutation/changeuserstatus": "/en/enterprise-server@2.20/graphql/reference/mutations#changeuserstatus", - "/en/enterprise/2.20/v4/mutation/changeuserstatus": "/en/enterprise-server@2.20/graphql/reference/mutations#changeuserstatus", - "/enterprise/2.20/v4/mutation/clearlabelsfromlabelable": "/en/enterprise-server@2.20/graphql/reference/mutations#clearlabelsfromlabelable", - "/en/enterprise/2.20/v4/mutation/clearlabelsfromlabelable": "/en/enterprise-server@2.20/graphql/reference/mutations#clearlabelsfromlabelable", - "/enterprise/2.20/v4/mutation/cloneproject": "/en/enterprise-server@2.20/graphql/reference/mutations#cloneproject", - "/en/enterprise/2.20/v4/mutation/cloneproject": "/en/enterprise-server@2.20/graphql/reference/mutations#cloneproject", - "/enterprise/2.20/v4/mutation/clonetemplaterepository": "/en/enterprise-server@2.20/graphql/reference/mutations#clonetemplaterepository", - "/en/enterprise/2.20/v4/mutation/clonetemplaterepository": "/en/enterprise-server@2.20/graphql/reference/mutations#clonetemplaterepository", - "/enterprise/2.20/v4/mutation/closeissue": "/en/enterprise-server@2.20/graphql/reference/mutations#closeissue", - "/en/enterprise/2.20/v4/mutation/closeissue": "/en/enterprise-server@2.20/graphql/reference/mutations#closeissue", - "/enterprise/2.20/v4/mutation/closepullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#closepullrequest", - "/en/enterprise/2.20/v4/mutation/closepullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#closepullrequest", - "/enterprise/2.20/v4/mutation/convertprojectcardnotetoissue": "/en/enterprise-server@2.20/graphql/reference/mutations#convertprojectcardnotetoissue", - "/en/enterprise/2.20/v4/mutation/convertprojectcardnotetoissue": "/en/enterprise-server@2.20/graphql/reference/mutations#convertprojectcardnotetoissue", - "/enterprise/2.20/v4/mutation/createbranchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/mutations#createbranchprotectionrule", - "/en/enterprise/2.20/v4/mutation/createbranchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/mutations#createbranchprotectionrule", - "/enterprise/2.20/v4/mutation/createcheckrun": "/en/enterprise-server@2.20/graphql/reference/mutations#createcheckrun", - "/en/enterprise/2.20/v4/mutation/createcheckrun": "/en/enterprise-server@2.20/graphql/reference/mutations#createcheckrun", - "/enterprise/2.20/v4/mutation/createchecksuite": "/en/enterprise-server@2.20/graphql/reference/mutations#createchecksuite", - "/en/enterprise/2.20/v4/mutation/createchecksuite": "/en/enterprise-server@2.20/graphql/reference/mutations#createchecksuite", - "/enterprise/2.20/v4/mutation/createcontentattachment": "/en/enterprise-server@2.20/graphql/reference/mutations#createcontentattachment", - "/en/enterprise/2.20/v4/mutation/createcontentattachment": "/en/enterprise-server@2.20/graphql/reference/mutations#createcontentattachment", - "/enterprise/2.20/v4/mutation/createdeployment": "/en/enterprise-server@2.20/graphql/reference/mutations#createdeployment", - "/en/enterprise/2.20/v4/mutation/createdeployment": "/en/enterprise-server@2.20/graphql/reference/mutations#createdeployment", - "/enterprise/2.20/v4/mutation/createdeploymentstatus": "/en/enterprise-server@2.20/graphql/reference/mutations#createdeploymentstatus", - "/en/enterprise/2.20/v4/mutation/createdeploymentstatus": "/en/enterprise-server@2.20/graphql/reference/mutations#createdeploymentstatus", - "/enterprise/2.20/v4/mutation/createissue": "/en/enterprise-server@2.20/graphql/reference/mutations#createissue", - "/en/enterprise/2.20/v4/mutation/createissue": "/en/enterprise-server@2.20/graphql/reference/mutations#createissue", - "/enterprise/2.20/v4/mutation/createlabel": "/en/enterprise-server@2.20/graphql/reference/mutations#createlabel", - "/en/enterprise/2.20/v4/mutation/createlabel": "/en/enterprise-server@2.20/graphql/reference/mutations#createlabel", - "/enterprise/2.20/v4/mutation/createproject": "/en/enterprise-server@2.20/graphql/reference/mutations#createproject", - "/en/enterprise/2.20/v4/mutation/createproject": "/en/enterprise-server@2.20/graphql/reference/mutations#createproject", - "/enterprise/2.20/v4/mutation/createpullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#createpullrequest", - "/en/enterprise/2.20/v4/mutation/createpullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#createpullrequest", - "/enterprise/2.20/v4/mutation/createref": "/en/enterprise-server@2.20/graphql/reference/mutations#createref", - "/en/enterprise/2.20/v4/mutation/createref": "/en/enterprise-server@2.20/graphql/reference/mutations#createref", - "/enterprise/2.20/v4/mutation/createrepository": "/en/enterprise-server@2.20/graphql/reference/mutations#createrepository", - "/en/enterprise/2.20/v4/mutation/createrepository": "/en/enterprise-server@2.20/graphql/reference/mutations#createrepository", - "/enterprise/2.20/v4/mutation/createteamdiscussion": "/en/enterprise-server@2.20/graphql/reference/mutations#createteamdiscussion", - "/en/enterprise/2.20/v4/mutation/createteamdiscussion": "/en/enterprise-server@2.20/graphql/reference/mutations#createteamdiscussion", - "/enterprise/2.20/v4/mutation/createteamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/mutations#createteamdiscussioncomment", - "/en/enterprise/2.20/v4/mutation/createteamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/mutations#createteamdiscussioncomment", - "/enterprise/2.20/v4/mutation/deletebranchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/mutations#deletebranchprotectionrule", - "/en/enterprise/2.20/v4/mutation/deletebranchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/mutations#deletebranchprotectionrule", - "/enterprise/2.20/v4/mutation/deleteissue": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteissue", - "/en/enterprise/2.20/v4/mutation/deleteissue": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteissue", - "/enterprise/2.20/v4/mutation/deleteissuecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteissuecomment", - "/en/enterprise/2.20/v4/mutation/deleteissuecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteissuecomment", - "/enterprise/2.20/v4/mutation/deletelabel": "/en/enterprise-server@2.20/graphql/reference/mutations#deletelabel", - "/en/enterprise/2.20/v4/mutation/deletelabel": "/en/enterprise-server@2.20/graphql/reference/mutations#deletelabel", - "/enterprise/2.20/v4/mutation/deleteproject": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteproject", - "/en/enterprise/2.20/v4/mutation/deleteproject": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteproject", - "/enterprise/2.20/v4/mutation/deleteprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteprojectcard", - "/en/enterprise/2.20/v4/mutation/deleteprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteprojectcard", - "/enterprise/2.20/v4/mutation/deleteprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteprojectcolumn", - "/en/enterprise/2.20/v4/mutation/deleteprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteprojectcolumn", - "/enterprise/2.20/v4/mutation/deletepullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#deletepullrequestreview", - "/en/enterprise/2.20/v4/mutation/deletepullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#deletepullrequestreview", - "/enterprise/2.20/v4/mutation/deletepullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#deletepullrequestreviewcomment", - "/en/enterprise/2.20/v4/mutation/deletepullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#deletepullrequestreviewcomment", - "/enterprise/2.20/v4/mutation/deleteref": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteref", - "/en/enterprise/2.20/v4/mutation/deleteref": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteref", - "/enterprise/2.20/v4/mutation/deleteteamdiscussion": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteteamdiscussion", - "/en/enterprise/2.20/v4/mutation/deleteteamdiscussion": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteteamdiscussion", - "/enterprise/2.20/v4/mutation/deleteteamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteteamdiscussioncomment", - "/en/enterprise/2.20/v4/mutation/deleteteamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/mutations#deleteteamdiscussioncomment", - "/enterprise/2.20/v4/mutation/dismisspullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#dismisspullrequestreview", - "/en/enterprise/2.20/v4/mutation/dismisspullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#dismisspullrequestreview", - "/enterprise/2.20/v4/mutation/followuser": "/en/enterprise-server@2.20/graphql/reference/mutations#followuser", - "/en/enterprise/2.20/v4/mutation/followuser": "/en/enterprise-server@2.20/graphql/reference/mutations#followuser", - "/enterprise/2.20/v4/mutation/importproject": "/en/enterprise-server@2.20/graphql/reference/mutations#importproject", - "/en/enterprise/2.20/v4/mutation/importproject": "/en/enterprise-server@2.20/graphql/reference/mutations#importproject", - "/enterprise/2.20/v4/mutation/linkrepositorytoproject": "/en/enterprise-server@2.20/graphql/reference/mutations#linkrepositorytoproject", - "/en/enterprise/2.20/v4/mutation/linkrepositorytoproject": "/en/enterprise-server@2.20/graphql/reference/mutations#linkrepositorytoproject", - "/enterprise/2.20/v4/mutation/locklockable": "/en/enterprise-server@2.20/graphql/reference/mutations#locklockable", - "/en/enterprise/2.20/v4/mutation/locklockable": "/en/enterprise-server@2.20/graphql/reference/mutations#locklockable", - "/enterprise/2.20/v4/mutation/markpullrequestreadyforreview": "/en/enterprise-server@2.20/graphql/reference/mutations#markpullrequestreadyforreview", - "/en/enterprise/2.20/v4/mutation/markpullrequestreadyforreview": "/en/enterprise-server@2.20/graphql/reference/mutations#markpullrequestreadyforreview", - "/enterprise/2.20/v4/mutation/mergebranch": "/en/enterprise-server@2.20/graphql/reference/mutations#mergebranch", - "/en/enterprise/2.20/v4/mutation/mergebranch": "/en/enterprise-server@2.20/graphql/reference/mutations#mergebranch", - "/enterprise/2.20/v4/mutation/mergepullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#mergepullrequest", - "/en/enterprise/2.20/v4/mutation/mergepullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#mergepullrequest", - "/enterprise/2.20/v4/mutation/minimizecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#minimizecomment", - "/en/enterprise/2.20/v4/mutation/minimizecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#minimizecomment", - "/enterprise/2.20/v4/mutation/moveprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#moveprojectcard", - "/en/enterprise/2.20/v4/mutation/moveprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#moveprojectcard", - "/enterprise/2.20/v4/mutation/moveprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#moveprojectcolumn", - "/en/enterprise/2.20/v4/mutation/moveprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#moveprojectcolumn", - "/enterprise/2.20/v4/mutation/pinissue": "/en/enterprise-server@2.20/graphql/reference/mutations#pinissue", - "/en/enterprise/2.20/v4/mutation/pinissue": "/en/enterprise-server@2.20/graphql/reference/mutations#pinissue", - "/enterprise/2.20/v4/mutation/removeassigneesfromassignable": "/en/enterprise-server@2.20/graphql/reference/mutations#removeassigneesfromassignable", - "/en/enterprise/2.20/v4/mutation/removeassigneesfromassignable": "/en/enterprise-server@2.20/graphql/reference/mutations#removeassigneesfromassignable", - "/enterprise/2.20/v4/mutation/removeenterpriseadmin": "/en/enterprise-server@2.20/graphql/reference/mutations#removeenterpriseadmin", - "/en/enterprise/2.20/v4/mutation/removeenterpriseadmin": "/en/enterprise-server@2.20/graphql/reference/mutations#removeenterpriseadmin", - "/enterprise/2.20/v4/mutation/removelabelsfromlabelable": "/en/enterprise-server@2.20/graphql/reference/mutations#removelabelsfromlabelable", - "/en/enterprise/2.20/v4/mutation/removelabelsfromlabelable": "/en/enterprise-server@2.20/graphql/reference/mutations#removelabelsfromlabelable", - "/enterprise/2.20/v4/mutation/removeoutsidecollaborator": "/en/enterprise-server@2.20/graphql/reference/mutations#removeoutsidecollaborator", - "/en/enterprise/2.20/v4/mutation/removeoutsidecollaborator": "/en/enterprise-server@2.20/graphql/reference/mutations#removeoutsidecollaborator", - "/enterprise/2.20/v4/mutation/removereaction": "/en/enterprise-server@2.20/graphql/reference/mutations#removereaction", - "/en/enterprise/2.20/v4/mutation/removereaction": "/en/enterprise-server@2.20/graphql/reference/mutations#removereaction", - "/enterprise/2.20/v4/mutation/removestar": "/en/enterprise-server@2.20/graphql/reference/mutations#removestar", - "/en/enterprise/2.20/v4/mutation/removestar": "/en/enterprise-server@2.20/graphql/reference/mutations#removestar", - "/enterprise/2.20/v4/mutation/reopenissue": "/en/enterprise-server@2.20/graphql/reference/mutations#reopenissue", - "/en/enterprise/2.20/v4/mutation/reopenissue": "/en/enterprise-server@2.20/graphql/reference/mutations#reopenissue", - "/enterprise/2.20/v4/mutation/reopenpullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#reopenpullrequest", - "/en/enterprise/2.20/v4/mutation/reopenpullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#reopenpullrequest", - "/enterprise/2.20/v4/mutation/requestreviews": "/en/enterprise-server@2.20/graphql/reference/mutations#requestreviews", - "/en/enterprise/2.20/v4/mutation/requestreviews": "/en/enterprise-server@2.20/graphql/reference/mutations#requestreviews", - "/enterprise/2.20/v4/mutation/rerequestchecksuite": "/en/enterprise-server@2.20/graphql/reference/mutations#rerequestchecksuite", - "/en/enterprise/2.20/v4/mutation/rerequestchecksuite": "/en/enterprise-server@2.20/graphql/reference/mutations#rerequestchecksuite", - "/enterprise/2.20/v4/mutation/resolvereviewthread": "/en/enterprise-server@2.20/graphql/reference/mutations#resolvereviewthread", - "/en/enterprise/2.20/v4/mutation/resolvereviewthread": "/en/enterprise-server@2.20/graphql/reference/mutations#resolvereviewthread", - "/enterprise/2.20/v4/mutation/submitpullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#submitpullrequestreview", - "/en/enterprise/2.20/v4/mutation/submitpullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#submitpullrequestreview", - "/enterprise/2.20/v4/mutation/transferissue": "/en/enterprise-server@2.20/graphql/reference/mutations#transferissue", - "/en/enterprise/2.20/v4/mutation/transferissue": "/en/enterprise-server@2.20/graphql/reference/mutations#transferissue", - "/enterprise/2.20/v4/mutation/unarchiverepository": "/en/enterprise-server@2.20/graphql/reference/mutations#unarchiverepository", - "/en/enterprise/2.20/v4/mutation/unarchiverepository": "/en/enterprise-server@2.20/graphql/reference/mutations#unarchiverepository", - "/enterprise/2.20/v4/mutation/unfollowuser": "/en/enterprise-server@2.20/graphql/reference/mutations#unfollowuser", - "/en/enterprise/2.20/v4/mutation/unfollowuser": "/en/enterprise-server@2.20/graphql/reference/mutations#unfollowuser", - "/enterprise/2.20/v4/mutation/unlinkrepositoryfromproject": "/en/enterprise-server@2.20/graphql/reference/mutations#unlinkrepositoryfromproject", - "/en/enterprise/2.20/v4/mutation/unlinkrepositoryfromproject": "/en/enterprise-server@2.20/graphql/reference/mutations#unlinkrepositoryfromproject", - "/enterprise/2.20/v4/mutation/unlocklockable": "/en/enterprise-server@2.20/graphql/reference/mutations#unlocklockable", - "/en/enterprise/2.20/v4/mutation/unlocklockable": "/en/enterprise-server@2.20/graphql/reference/mutations#unlocklockable", - "/enterprise/2.20/v4/mutation/unmarkissueasduplicate": "/en/enterprise-server@2.20/graphql/reference/mutations#unmarkissueasduplicate", - "/en/enterprise/2.20/v4/mutation/unmarkissueasduplicate": "/en/enterprise-server@2.20/graphql/reference/mutations#unmarkissueasduplicate", - "/enterprise/2.20/v4/mutation/unminimizecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#unminimizecomment", - "/en/enterprise/2.20/v4/mutation/unminimizecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#unminimizecomment", - "/enterprise/2.20/v4/mutation/unpinissue": "/en/enterprise-server@2.20/graphql/reference/mutations#unpinissue", - "/en/enterprise/2.20/v4/mutation/unpinissue": "/en/enterprise-server@2.20/graphql/reference/mutations#unpinissue", - "/enterprise/2.20/v4/mutation/unresolvereviewthread": "/en/enterprise-server@2.20/graphql/reference/mutations#unresolvereviewthread", - "/en/enterprise/2.20/v4/mutation/unresolvereviewthread": "/en/enterprise-server@2.20/graphql/reference/mutations#unresolvereviewthread", - "/enterprise/2.20/v4/mutation/updatebranchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/mutations#updatebranchprotectionrule", - "/en/enterprise/2.20/v4/mutation/updatebranchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/mutations#updatebranchprotectionrule", - "/enterprise/2.20/v4/mutation/updatecheckrun": "/en/enterprise-server@2.20/graphql/reference/mutations#updatecheckrun", - "/en/enterprise/2.20/v4/mutation/updatecheckrun": "/en/enterprise-server@2.20/graphql/reference/mutations#updatecheckrun", - "/enterprise/2.20/v4/mutation/updatechecksuitepreferences": "/en/enterprise-server@2.20/graphql/reference/mutations#updatechecksuitepreferences", - "/en/enterprise/2.20/v4/mutation/updatechecksuitepreferences": "/en/enterprise-server@2.20/graphql/reference/mutations#updatechecksuitepreferences", - "/enterprise/2.20/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", - "/en/enterprise/2.20/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", - "/enterprise/2.20/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", - "/en/enterprise/2.20/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", - "/enterprise/2.20/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscandeleteissuessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscandeleteissuessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", - "/enterprise/2.20/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", - "/enterprise/2.20/v4/mutation/updateenterpriseorganizationprojectssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", - "/en/enterprise/2.20/v4/mutation/updateenterpriseorganizationprojectssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", - "/enterprise/2.20/v4/mutation/updateenterpriseprofile": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseprofile", - "/en/enterprise/2.20/v4/mutation/updateenterpriseprofile": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseprofile", - "/enterprise/2.20/v4/mutation/updateenterpriserepositoryprojectssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", - "/en/enterprise/2.20/v4/mutation/updateenterpriserepositoryprojectssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", - "/enterprise/2.20/v4/mutation/updateenterpriseteamdiscussionssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", - "/en/enterprise/2.20/v4/mutation/updateenterpriseteamdiscussionssetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", - "/enterprise/2.20/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", - "/en/enterprise/2.20/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/en/enterprise-server@2.20/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", - "/enterprise/2.20/v4/mutation/updateissue": "/en/enterprise-server@2.20/graphql/reference/mutations#updateissue", - "/en/enterprise/2.20/v4/mutation/updateissue": "/en/enterprise-server@2.20/graphql/reference/mutations#updateissue", - "/enterprise/2.20/v4/mutation/updateissuecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#updateissuecomment", - "/en/enterprise/2.20/v4/mutation/updateissuecomment": "/en/enterprise-server@2.20/graphql/reference/mutations#updateissuecomment", - "/enterprise/2.20/v4/mutation/updatelabel": "/en/enterprise-server@2.20/graphql/reference/mutations#updatelabel", - "/en/enterprise/2.20/v4/mutation/updatelabel": "/en/enterprise-server@2.20/graphql/reference/mutations#updatelabel", - "/enterprise/2.20/v4/mutation/updateproject": "/en/enterprise-server@2.20/graphql/reference/mutations#updateproject", - "/en/enterprise/2.20/v4/mutation/updateproject": "/en/enterprise-server@2.20/graphql/reference/mutations#updateproject", - "/enterprise/2.20/v4/mutation/updateprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#updateprojectcard", - "/en/enterprise/2.20/v4/mutation/updateprojectcard": "/en/enterprise-server@2.20/graphql/reference/mutations#updateprojectcard", - "/enterprise/2.20/v4/mutation/updateprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#updateprojectcolumn", - "/en/enterprise/2.20/v4/mutation/updateprojectcolumn": "/en/enterprise-server@2.20/graphql/reference/mutations#updateprojectcolumn", - "/enterprise/2.20/v4/mutation/updatepullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#updatepullrequest", - "/en/enterprise/2.20/v4/mutation/updatepullrequest": "/en/enterprise-server@2.20/graphql/reference/mutations#updatepullrequest", - "/enterprise/2.20/v4/mutation/updatepullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#updatepullrequestreview", - "/en/enterprise/2.20/v4/mutation/updatepullrequestreview": "/en/enterprise-server@2.20/graphql/reference/mutations#updatepullrequestreview", - "/enterprise/2.20/v4/mutation/updatepullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#updatepullrequestreviewcomment", - "/en/enterprise/2.20/v4/mutation/updatepullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/mutations#updatepullrequestreviewcomment", - "/enterprise/2.20/v4/mutation/updateref": "/en/enterprise-server@2.20/graphql/reference/mutations#updateref", - "/en/enterprise/2.20/v4/mutation/updateref": "/en/enterprise-server@2.20/graphql/reference/mutations#updateref", - "/enterprise/2.20/v4/mutation/updaterefs": "/en/enterprise-server@2.20/graphql/reference/mutations#updaterefs", - "/en/enterprise/2.20/v4/mutation/updaterefs": "/en/enterprise-server@2.20/graphql/reference/mutations#updaterefs", - "/enterprise/2.20/v4/mutation/updaterepository": "/en/enterprise-server@2.20/graphql/reference/mutations#updaterepository", - "/en/enterprise/2.20/v4/mutation/updaterepository": "/en/enterprise-server@2.20/graphql/reference/mutations#updaterepository", - "/enterprise/2.20/v4/mutation/updatesubscription": "/en/enterprise-server@2.20/graphql/reference/mutations#updatesubscription", - "/en/enterprise/2.20/v4/mutation/updatesubscription": "/en/enterprise-server@2.20/graphql/reference/mutations#updatesubscription", - "/enterprise/2.20/v4/mutation/updateteamdiscussion": "/en/enterprise-server@2.20/graphql/reference/mutations#updateteamdiscussion", - "/en/enterprise/2.20/v4/mutation/updateteamdiscussion": "/en/enterprise-server@2.20/graphql/reference/mutations#updateteamdiscussion", - "/enterprise/2.20/v4/mutation/updateteamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/mutations#updateteamdiscussioncomment", - "/en/enterprise/2.20/v4/mutation/updateteamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/mutations#updateteamdiscussioncomment", - "/enterprise/2.20/v4/mutation/updateteamreviewassignment": "/en/enterprise-server@2.20/graphql/reference/mutations#updateteamreviewassignment", - "/en/enterprise/2.20/v4/mutation/updateteamreviewassignment": "/en/enterprise-server@2.20/graphql/reference/mutations#updateteamreviewassignment", - "/enterprise/2.20/v4/mutation/updatetopics": "/en/enterprise-server@2.20/graphql/reference/mutations#updatetopics", - "/en/enterprise/2.20/v4/mutation/updatetopics": "/en/enterprise-server@2.20/graphql/reference/mutations#updatetopics", - "/enterprise/2.20/v4/object/__directive": "/en/enterprise-server@2.20/graphql/reference/objects#__directive", - "/en/enterprise/2.20/v4/object/__directive": "/en/enterprise-server@2.20/graphql/reference/objects#__directive", - "/enterprise/2.20/v4/object/__enumvalue": "/en/enterprise-server@2.20/graphql/reference/objects#__enumvalue", - "/en/enterprise/2.20/v4/object/__enumvalue": "/en/enterprise-server@2.20/graphql/reference/objects#__enumvalue", - "/enterprise/2.20/v4/object/__field": "/en/enterprise-server@2.20/graphql/reference/objects#__field", - "/en/enterprise/2.20/v4/object/__field": "/en/enterprise-server@2.20/graphql/reference/objects#__field", - "/enterprise/2.20/v4/object/__inputvalue": "/en/enterprise-server@2.20/graphql/reference/objects#__inputvalue", - "/en/enterprise/2.20/v4/object/__inputvalue": "/en/enterprise-server@2.20/graphql/reference/objects#__inputvalue", - "/enterprise/2.20/v4/object/__schema": "/en/enterprise-server@2.20/graphql/reference/objects#__schema", - "/en/enterprise/2.20/v4/object/__schema": "/en/enterprise-server@2.20/graphql/reference/objects#__schema", - "/enterprise/2.20/v4/object/__type": "/en/enterprise-server@2.20/graphql/reference/objects#__type", - "/en/enterprise/2.20/v4/object/__type": "/en/enterprise-server@2.20/graphql/reference/objects#__type", - "/enterprise/2.20/v4/object/actorlocation": "/en/enterprise-server@2.20/graphql/reference/objects#actorlocation", - "/en/enterprise/2.20/v4/object/actorlocation": "/en/enterprise-server@2.20/graphql/reference/objects#actorlocation", - "/enterprise/2.20/v4/object/addassigneestoassignablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#addassigneestoassignablepayload", - "/en/enterprise/2.20/v4/object/addassigneestoassignablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#addassigneestoassignablepayload", - "/enterprise/2.20/v4/object/addcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addcommentpayload", - "/en/enterprise/2.20/v4/object/addcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addcommentpayload", - "/enterprise/2.20/v4/object/addedtoprojectevent": "/en/enterprise-server@2.20/graphql/reference/objects#addedtoprojectevent", - "/en/enterprise/2.20/v4/object/addedtoprojectevent": "/en/enterprise-server@2.20/graphql/reference/objects#addedtoprojectevent", - "/enterprise/2.20/v4/object/addenterpriseadminpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addenterpriseadminpayload", - "/en/enterprise/2.20/v4/object/addenterpriseadminpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addenterpriseadminpayload", - "/enterprise/2.20/v4/object/addlabelstolabelablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#addlabelstolabelablepayload", - "/en/enterprise/2.20/v4/object/addlabelstolabelablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#addlabelstolabelablepayload", - "/enterprise/2.20/v4/object/addprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addprojectcardpayload", - "/en/enterprise/2.20/v4/object/addprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addprojectcardpayload", - "/enterprise/2.20/v4/object/addprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addprojectcolumnpayload", - "/en/enterprise/2.20/v4/object/addprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addprojectcolumnpayload", - "/enterprise/2.20/v4/object/addpullrequestreviewcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewcommentpayload", - "/en/enterprise/2.20/v4/object/addpullrequestreviewcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewcommentpayload", - "/enterprise/2.20/v4/object/addpullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewpayload", - "/en/enterprise/2.20/v4/object/addpullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewpayload", - "/enterprise/2.20/v4/object/addpullrequestreviewthreadpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewthreadpayload", - "/en/enterprise/2.20/v4/object/addpullrequestreviewthreadpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewthreadpayload", - "/enterprise/2.20/v4/object/addreactionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addreactionpayload", - "/en/enterprise/2.20/v4/object/addreactionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addreactionpayload", - "/enterprise/2.20/v4/object/addstarpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addstarpayload", - "/en/enterprise/2.20/v4/object/addstarpayload": "/en/enterprise-server@2.20/graphql/reference/objects#addstarpayload", - "/enterprise/2.20/v4/object/app": "/en/enterprise-server@2.20/graphql/reference/objects#app", - "/en/enterprise/2.20/v4/object/app": "/en/enterprise-server@2.20/graphql/reference/objects#app", - "/enterprise/2.20/v4/object/archiverepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#archiverepositorypayload", - "/en/enterprise/2.20/v4/object/archiverepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#archiverepositorypayload", - "/enterprise/2.20/v4/object/assignedevent": "/en/enterprise-server@2.20/graphql/reference/objects#assignedevent", - "/en/enterprise/2.20/v4/object/assignedevent": "/en/enterprise-server@2.20/graphql/reference/objects#assignedevent", - "/enterprise/2.20/v4/object/baserefchangedevent": "/en/enterprise-server@2.20/graphql/reference/objects#baserefchangedevent", - "/en/enterprise/2.20/v4/object/baserefchangedevent": "/en/enterprise-server@2.20/graphql/reference/objects#baserefchangedevent", - "/enterprise/2.20/v4/object/baserefforcepushedevent": "/en/enterprise-server@2.20/graphql/reference/objects#baserefforcepushedevent", - "/en/enterprise/2.20/v4/object/baserefforcepushedevent": "/en/enterprise-server@2.20/graphql/reference/objects#baserefforcepushedevent", - "/enterprise/2.20/v4/object/blame": "/en/enterprise-server@2.20/graphql/reference/objects#blame", - "/en/enterprise/2.20/v4/object/blame": "/en/enterprise-server@2.20/graphql/reference/objects#blame", - "/enterprise/2.20/v4/object/blamerange": "/en/enterprise-server@2.20/graphql/reference/objects#blamerange", - "/en/enterprise/2.20/v4/object/blamerange": "/en/enterprise-server@2.20/graphql/reference/objects#blamerange", - "/enterprise/2.20/v4/object/blob": "/en/enterprise-server@2.20/graphql/reference/objects#blob", - "/en/enterprise/2.20/v4/object/blob": "/en/enterprise-server@2.20/graphql/reference/objects#blob", - "/enterprise/2.20/v4/object/bot": "/en/enterprise-server@2.20/graphql/reference/objects#bot", - "/en/enterprise/2.20/v4/object/bot": "/en/enterprise-server@2.20/graphql/reference/objects#bot", - "/enterprise/2.20/v4/object/branchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionrule", - "/en/enterprise/2.20/v4/object/branchprotectionrule": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionrule", - "/enterprise/2.20/v4/object/branchprotectionruleconflict": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflict", - "/en/enterprise/2.20/v4/object/branchprotectionruleconflict": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflict", - "/enterprise/2.20/v4/object/branchprotectionruleconflictconnection": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflictconnection", - "/en/enterprise/2.20/v4/object/branchprotectionruleconflictconnection": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflictconnection", - "/enterprise/2.20/v4/object/branchprotectionruleconflictedge": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflictedge", - "/en/enterprise/2.20/v4/object/branchprotectionruleconflictedge": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflictedge", - "/enterprise/2.20/v4/object/branchprotectionruleconnection": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconnection", - "/en/enterprise/2.20/v4/object/branchprotectionruleconnection": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconnection", - "/enterprise/2.20/v4/object/branchprotectionruleedge": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleedge", - "/en/enterprise/2.20/v4/object/branchprotectionruleedge": "/en/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleedge", - "/enterprise/2.20/v4/object/changeuserstatuspayload": "/en/enterprise-server@2.20/graphql/reference/objects#changeuserstatuspayload", - "/en/enterprise/2.20/v4/object/changeuserstatuspayload": "/en/enterprise-server@2.20/graphql/reference/objects#changeuserstatuspayload", - "/enterprise/2.20/v4/object/checkannotation": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotation", - "/en/enterprise/2.20/v4/object/checkannotation": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotation", - "/enterprise/2.20/v4/object/checkannotationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationconnection", - "/en/enterprise/2.20/v4/object/checkannotationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationconnection", - "/enterprise/2.20/v4/object/checkannotationedge": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationedge", - "/en/enterprise/2.20/v4/object/checkannotationedge": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationedge", - "/enterprise/2.20/v4/object/checkannotationposition": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationposition", - "/en/enterprise/2.20/v4/object/checkannotationposition": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationposition", - "/enterprise/2.20/v4/object/checkannotationspan": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationspan", - "/en/enterprise/2.20/v4/object/checkannotationspan": "/en/enterprise-server@2.20/graphql/reference/objects#checkannotationspan", - "/enterprise/2.20/v4/object/checkrun": "/en/enterprise-server@2.20/graphql/reference/objects#checkrun", - "/en/enterprise/2.20/v4/object/checkrun": "/en/enterprise-server@2.20/graphql/reference/objects#checkrun", - "/enterprise/2.20/v4/object/checkrunconnection": "/en/enterprise-server@2.20/graphql/reference/objects#checkrunconnection", - "/en/enterprise/2.20/v4/object/checkrunconnection": "/en/enterprise-server@2.20/graphql/reference/objects#checkrunconnection", - "/enterprise/2.20/v4/object/checkrunedge": "/en/enterprise-server@2.20/graphql/reference/objects#checkrunedge", - "/en/enterprise/2.20/v4/object/checkrunedge": "/en/enterprise-server@2.20/graphql/reference/objects#checkrunedge", - "/enterprise/2.20/v4/object/checksuite": "/en/enterprise-server@2.20/graphql/reference/objects#checksuite", - "/en/enterprise/2.20/v4/object/checksuite": "/en/enterprise-server@2.20/graphql/reference/objects#checksuite", - "/enterprise/2.20/v4/object/checksuiteconnection": "/en/enterprise-server@2.20/graphql/reference/objects#checksuiteconnection", - "/en/enterprise/2.20/v4/object/checksuiteconnection": "/en/enterprise-server@2.20/graphql/reference/objects#checksuiteconnection", - "/enterprise/2.20/v4/object/checksuiteedge": "/en/enterprise-server@2.20/graphql/reference/objects#checksuiteedge", - "/en/enterprise/2.20/v4/object/checksuiteedge": "/en/enterprise-server@2.20/graphql/reference/objects#checksuiteedge", - "/enterprise/2.20/v4/object/clearlabelsfromlabelablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#clearlabelsfromlabelablepayload", - "/en/enterprise/2.20/v4/object/clearlabelsfromlabelablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#clearlabelsfromlabelablepayload", - "/enterprise/2.20/v4/object/cloneprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#cloneprojectpayload", - "/en/enterprise/2.20/v4/object/cloneprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#cloneprojectpayload", - "/enterprise/2.20/v4/object/clonetemplaterepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#clonetemplaterepositorypayload", - "/en/enterprise/2.20/v4/object/clonetemplaterepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#clonetemplaterepositorypayload", - "/enterprise/2.20/v4/object/closedevent": "/en/enterprise-server@2.20/graphql/reference/objects#closedevent", - "/en/enterprise/2.20/v4/object/closedevent": "/en/enterprise-server@2.20/graphql/reference/objects#closedevent", - "/enterprise/2.20/v4/object/closeissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#closeissuepayload", - "/en/enterprise/2.20/v4/object/closeissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#closeissuepayload", - "/enterprise/2.20/v4/object/closepullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#closepullrequestpayload", - "/en/enterprise/2.20/v4/object/closepullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#closepullrequestpayload", - "/enterprise/2.20/v4/object/codeofconduct": "/en/enterprise-server@2.20/graphql/reference/objects#codeofconduct", - "/en/enterprise/2.20/v4/object/codeofconduct": "/en/enterprise-server@2.20/graphql/reference/objects#codeofconduct", - "/enterprise/2.20/v4/object/commentdeletedevent": "/en/enterprise-server@2.20/graphql/reference/objects#commentdeletedevent", - "/en/enterprise/2.20/v4/object/commentdeletedevent": "/en/enterprise-server@2.20/graphql/reference/objects#commentdeletedevent", - "/enterprise/2.20/v4/object/commit": "/en/enterprise-server@2.20/graphql/reference/objects#commit", - "/en/enterprise/2.20/v4/object/commit": "/en/enterprise-server@2.20/graphql/reference/objects#commit", - "/enterprise/2.20/v4/object/commitcomment": "/en/enterprise-server@2.20/graphql/reference/objects#commitcomment", - "/en/enterprise/2.20/v4/object/commitcomment": "/en/enterprise-server@2.20/graphql/reference/objects#commitcomment", - "/enterprise/2.20/v4/object/commitcommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#commitcommentconnection", - "/en/enterprise/2.20/v4/object/commitcommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#commitcommentconnection", - "/enterprise/2.20/v4/object/commitcommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#commitcommentedge", - "/en/enterprise/2.20/v4/object/commitcommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#commitcommentedge", - "/enterprise/2.20/v4/object/commitcommentthread": "/en/enterprise-server@2.20/graphql/reference/objects#commitcommentthread", - "/en/enterprise/2.20/v4/object/commitcommentthread": "/en/enterprise-server@2.20/graphql/reference/objects#commitcommentthread", - "/enterprise/2.20/v4/object/commitconnection": "/en/enterprise-server@2.20/graphql/reference/objects#commitconnection", - "/en/enterprise/2.20/v4/object/commitconnection": "/en/enterprise-server@2.20/graphql/reference/objects#commitconnection", - "/enterprise/2.20/v4/object/commitcontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#commitcontributionsbyrepository", - "/en/enterprise/2.20/v4/object/commitcontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#commitcontributionsbyrepository", - "/enterprise/2.20/v4/object/commitedge": "/en/enterprise-server@2.20/graphql/reference/objects#commitedge", - "/en/enterprise/2.20/v4/object/commitedge": "/en/enterprise-server@2.20/graphql/reference/objects#commitedge", - "/enterprise/2.20/v4/object/commithistoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#commithistoryconnection", - "/en/enterprise/2.20/v4/object/commithistoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#commithistoryconnection", - "/enterprise/2.20/v4/object/contentattachment": "/en/enterprise-server@2.20/graphql/reference/objects#contentattachment", - "/en/enterprise/2.20/v4/object/contentattachment": "/en/enterprise-server@2.20/graphql/reference/objects#contentattachment", - "/enterprise/2.20/v4/object/contentreference": "/en/enterprise-server@2.20/graphql/reference/objects#contentreference", - "/en/enterprise/2.20/v4/object/contentreference": "/en/enterprise-server@2.20/graphql/reference/objects#contentreference", - "/enterprise/2.20/v4/object/contributioncalendar": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendar", - "/en/enterprise/2.20/v4/object/contributioncalendar": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendar", - "/enterprise/2.20/v4/object/contributioncalendarday": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendarday", - "/en/enterprise/2.20/v4/object/contributioncalendarday": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendarday", - "/enterprise/2.20/v4/object/contributioncalendarmonth": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendarmonth", - "/en/enterprise/2.20/v4/object/contributioncalendarmonth": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendarmonth", - "/enterprise/2.20/v4/object/contributioncalendarweek": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendarweek", - "/en/enterprise/2.20/v4/object/contributioncalendarweek": "/en/enterprise-server@2.20/graphql/reference/objects#contributioncalendarweek", - "/enterprise/2.20/v4/object/contributionscollection": "/en/enterprise-server@2.20/graphql/reference/objects#contributionscollection", - "/en/enterprise/2.20/v4/object/contributionscollection": "/en/enterprise-server@2.20/graphql/reference/objects#contributionscollection", - "/enterprise/2.20/v4/object/convertednotetoissueevent": "/en/enterprise-server@2.20/graphql/reference/objects#convertednotetoissueevent", - "/en/enterprise/2.20/v4/object/convertednotetoissueevent": "/en/enterprise-server@2.20/graphql/reference/objects#convertednotetoissueevent", - "/enterprise/2.20/v4/object/convertprojectcardnotetoissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#convertprojectcardnotetoissuepayload", - "/en/enterprise/2.20/v4/object/convertprojectcardnotetoissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#convertprojectcardnotetoissuepayload", - "/enterprise/2.20/v4/object/createbranchprotectionrulepayload": "/en/enterprise-server@2.20/graphql/reference/objects#createbranchprotectionrulepayload", - "/en/enterprise/2.20/v4/object/createbranchprotectionrulepayload": "/en/enterprise-server@2.20/graphql/reference/objects#createbranchprotectionrulepayload", - "/enterprise/2.20/v4/object/createcheckrunpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createcheckrunpayload", - "/en/enterprise/2.20/v4/object/createcheckrunpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createcheckrunpayload", - "/enterprise/2.20/v4/object/createchecksuitepayload": "/en/enterprise-server@2.20/graphql/reference/objects#createchecksuitepayload", - "/en/enterprise/2.20/v4/object/createchecksuitepayload": "/en/enterprise-server@2.20/graphql/reference/objects#createchecksuitepayload", - "/enterprise/2.20/v4/object/createcontentattachmentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createcontentattachmentpayload", - "/en/enterprise/2.20/v4/object/createcontentattachmentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createcontentattachmentpayload", - "/enterprise/2.20/v4/object/createdcommitcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdcommitcontribution", - "/en/enterprise/2.20/v4/object/createdcommitcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdcommitcontribution", - "/enterprise/2.20/v4/object/createdcommitcontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdcommitcontributionconnection", - "/en/enterprise/2.20/v4/object/createdcommitcontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdcommitcontributionconnection", - "/enterprise/2.20/v4/object/createdcommitcontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdcommitcontributionedge", - "/en/enterprise/2.20/v4/object/createdcommitcontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdcommitcontributionedge", - "/enterprise/2.20/v4/object/createdeploymentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createdeploymentpayload", - "/en/enterprise/2.20/v4/object/createdeploymentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createdeploymentpayload", - "/enterprise/2.20/v4/object/createdeploymentstatuspayload": "/en/enterprise-server@2.20/graphql/reference/objects#createdeploymentstatuspayload", - "/en/enterprise/2.20/v4/object/createdeploymentstatuspayload": "/en/enterprise-server@2.20/graphql/reference/objects#createdeploymentstatuspayload", - "/enterprise/2.20/v4/object/createdissuecontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdissuecontribution", - "/en/enterprise/2.20/v4/object/createdissuecontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdissuecontribution", - "/enterprise/2.20/v4/object/createdissuecontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdissuecontributionconnection", - "/en/enterprise/2.20/v4/object/createdissuecontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdissuecontributionconnection", - "/enterprise/2.20/v4/object/createdissuecontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdissuecontributionedge", - "/en/enterprise/2.20/v4/object/createdissuecontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdissuecontributionedge", - "/enterprise/2.20/v4/object/createdpullrequestcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontribution", - "/en/enterprise/2.20/v4/object/createdpullrequestcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontribution", - "/enterprise/2.20/v4/object/createdpullrequestcontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontributionconnection", - "/en/enterprise/2.20/v4/object/createdpullrequestcontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontributionconnection", - "/enterprise/2.20/v4/object/createdpullrequestcontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontributionedge", - "/en/enterprise/2.20/v4/object/createdpullrequestcontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontributionedge", - "/enterprise/2.20/v4/object/createdpullrequestreviewcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontribution", - "/en/enterprise/2.20/v4/object/createdpullrequestreviewcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontribution", - "/enterprise/2.20/v4/object/createdpullrequestreviewcontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontributionconnection", - "/en/enterprise/2.20/v4/object/createdpullrequestreviewcontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontributionconnection", - "/enterprise/2.20/v4/object/createdpullrequestreviewcontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontributionedge", - "/en/enterprise/2.20/v4/object/createdpullrequestreviewcontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontributionedge", - "/enterprise/2.20/v4/object/createdrepositorycontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontribution", - "/en/enterprise/2.20/v4/object/createdrepositorycontribution": "/en/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontribution", - "/enterprise/2.20/v4/object/createdrepositorycontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontributionconnection", - "/en/enterprise/2.20/v4/object/createdrepositorycontributionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontributionconnection", - "/enterprise/2.20/v4/object/createdrepositorycontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontributionedge", - "/en/enterprise/2.20/v4/object/createdrepositorycontributionedge": "/en/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontributionedge", - "/enterprise/2.20/v4/object/createissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#createissuepayload", - "/en/enterprise/2.20/v4/object/createissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#createissuepayload", - "/enterprise/2.20/v4/object/createlabelpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createlabelpayload", - "/en/enterprise/2.20/v4/object/createlabelpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createlabelpayload", - "/enterprise/2.20/v4/object/createprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createprojectpayload", - "/en/enterprise/2.20/v4/object/createprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createprojectpayload", - "/enterprise/2.20/v4/object/createpullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createpullrequestpayload", - "/en/enterprise/2.20/v4/object/createpullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createpullrequestpayload", - "/enterprise/2.20/v4/object/createrefpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createrefpayload", - "/en/enterprise/2.20/v4/object/createrefpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createrefpayload", - "/enterprise/2.20/v4/object/createrepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#createrepositorypayload", - "/en/enterprise/2.20/v4/object/createrepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#createrepositorypayload", - "/enterprise/2.20/v4/object/createteamdiscussioncommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createteamdiscussioncommentpayload", - "/en/enterprise/2.20/v4/object/createteamdiscussioncommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createteamdiscussioncommentpayload", - "/enterprise/2.20/v4/object/createteamdiscussionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createteamdiscussionpayload", - "/en/enterprise/2.20/v4/object/createteamdiscussionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#createteamdiscussionpayload", - "/enterprise/2.20/v4/object/crossreferencedevent": "/en/enterprise-server@2.20/graphql/reference/objects#crossreferencedevent", - "/en/enterprise/2.20/v4/object/crossreferencedevent": "/en/enterprise-server@2.20/graphql/reference/objects#crossreferencedevent", - "/enterprise/2.20/v4/object/deletebranchprotectionrulepayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletebranchprotectionrulepayload", - "/en/enterprise/2.20/v4/object/deletebranchprotectionrulepayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletebranchprotectionrulepayload", - "/enterprise/2.20/v4/object/deleteissuecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteissuecommentpayload", - "/en/enterprise/2.20/v4/object/deleteissuecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteissuecommentpayload", - "/enterprise/2.20/v4/object/deleteissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteissuepayload", - "/en/enterprise/2.20/v4/object/deleteissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteissuepayload", - "/enterprise/2.20/v4/object/deletelabelpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletelabelpayload", - "/en/enterprise/2.20/v4/object/deletelabelpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletelabelpayload", - "/enterprise/2.20/v4/object/deleteprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteprojectcardpayload", - "/en/enterprise/2.20/v4/object/deleteprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteprojectcardpayload", - "/enterprise/2.20/v4/object/deleteprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteprojectcolumnpayload", - "/en/enterprise/2.20/v4/object/deleteprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteprojectcolumnpayload", - "/enterprise/2.20/v4/object/deleteprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteprojectpayload", - "/en/enterprise/2.20/v4/object/deleteprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteprojectpayload", - "/enterprise/2.20/v4/object/deletepullrequestreviewcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletepullrequestreviewcommentpayload", - "/en/enterprise/2.20/v4/object/deletepullrequestreviewcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletepullrequestreviewcommentpayload", - "/enterprise/2.20/v4/object/deletepullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletepullrequestreviewpayload", - "/en/enterprise/2.20/v4/object/deletepullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deletepullrequestreviewpayload", - "/enterprise/2.20/v4/object/deleterefpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleterefpayload", - "/en/enterprise/2.20/v4/object/deleterefpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleterefpayload", - "/enterprise/2.20/v4/object/deleteteamdiscussioncommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteteamdiscussioncommentpayload", - "/en/enterprise/2.20/v4/object/deleteteamdiscussioncommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteteamdiscussioncommentpayload", - "/enterprise/2.20/v4/object/deleteteamdiscussionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteteamdiscussionpayload", - "/en/enterprise/2.20/v4/object/deleteteamdiscussionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#deleteteamdiscussionpayload", - "/enterprise/2.20/v4/object/demilestonedevent": "/en/enterprise-server@2.20/graphql/reference/objects#demilestonedevent", - "/en/enterprise/2.20/v4/object/demilestonedevent": "/en/enterprise-server@2.20/graphql/reference/objects#demilestonedevent", - "/enterprise/2.20/v4/object/deployedevent": "/en/enterprise-server@2.20/graphql/reference/objects#deployedevent", - "/en/enterprise/2.20/v4/object/deployedevent": "/en/enterprise-server@2.20/graphql/reference/objects#deployedevent", - "/enterprise/2.20/v4/object/deploykey": "/en/enterprise-server@2.20/graphql/reference/objects#deploykey", - "/en/enterprise/2.20/v4/object/deploykey": "/en/enterprise-server@2.20/graphql/reference/objects#deploykey", - "/enterprise/2.20/v4/object/deploykeyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#deploykeyconnection", - "/en/enterprise/2.20/v4/object/deploykeyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#deploykeyconnection", - "/enterprise/2.20/v4/object/deploykeyedge": "/en/enterprise-server@2.20/graphql/reference/objects#deploykeyedge", - "/en/enterprise/2.20/v4/object/deploykeyedge": "/en/enterprise-server@2.20/graphql/reference/objects#deploykeyedge", - "/enterprise/2.20/v4/object/deployment": "/en/enterprise-server@2.20/graphql/reference/objects#deployment", - "/en/enterprise/2.20/v4/object/deployment": "/en/enterprise-server@2.20/graphql/reference/objects#deployment", - "/enterprise/2.20/v4/object/deploymentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentconnection", - "/en/enterprise/2.20/v4/object/deploymentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentconnection", - "/enterprise/2.20/v4/object/deploymentedge": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentedge", - "/en/enterprise/2.20/v4/object/deploymentedge": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentedge", - "/enterprise/2.20/v4/object/deploymentenvironmentchangedevent": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentenvironmentchangedevent", - "/en/enterprise/2.20/v4/object/deploymentenvironmentchangedevent": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentenvironmentchangedevent", - "/enterprise/2.20/v4/object/deploymentstatus": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentstatus", - "/en/enterprise/2.20/v4/object/deploymentstatus": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentstatus", - "/enterprise/2.20/v4/object/deploymentstatusconnection": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentstatusconnection", - "/en/enterprise/2.20/v4/object/deploymentstatusconnection": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentstatusconnection", - "/enterprise/2.20/v4/object/deploymentstatusedge": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentstatusedge", - "/en/enterprise/2.20/v4/object/deploymentstatusedge": "/en/enterprise-server@2.20/graphql/reference/objects#deploymentstatusedge", - "/enterprise/2.20/v4/object/dismisspullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#dismisspullrequestreviewpayload", - "/en/enterprise/2.20/v4/object/dismisspullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#dismisspullrequestreviewpayload", - "/enterprise/2.20/v4/object/enterprise": "/en/enterprise-server@2.20/graphql/reference/objects#enterprise", - "/en/enterprise/2.20/v4/object/enterprise": "/en/enterprise-server@2.20/graphql/reference/objects#enterprise", - "/enterprise/2.20/v4/object/enterpriseadministratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorconnection", - "/en/enterprise/2.20/v4/object/enterpriseadministratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorconnection", - "/enterprise/2.20/v4/object/enterpriseadministratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratoredge", - "/en/enterprise/2.20/v4/object/enterpriseadministratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratoredge", - "/enterprise/2.20/v4/object/enterpriseadministratorinvitation": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitation", - "/en/enterprise/2.20/v4/object/enterpriseadministratorinvitation": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitation", - "/enterprise/2.20/v4/object/enterpriseadministratorinvitationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitationconnection", - "/en/enterprise/2.20/v4/object/enterpriseadministratorinvitationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitationconnection", - "/enterprise/2.20/v4/object/enterpriseadministratorinvitationedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitationedge", - "/en/enterprise/2.20/v4/object/enterpriseadministratorinvitationedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitationedge", - "/enterprise/2.20/v4/object/enterprisebillinginfo": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisebillinginfo", - "/en/enterprise/2.20/v4/object/enterprisebillinginfo": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisebillinginfo", - "/enterprise/2.20/v4/object/enterpriseidentityprovider": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseidentityprovider", - "/en/enterprise/2.20/v4/object/enterpriseidentityprovider": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseidentityprovider", - "/enterprise/2.20/v4/object/enterprisememberconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisememberconnection", - "/en/enterprise/2.20/v4/object/enterprisememberconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisememberconnection", - "/enterprise/2.20/v4/object/enterprisememberedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisememberedge", - "/en/enterprise/2.20/v4/object/enterprisememberedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisememberedge", - "/enterprise/2.20/v4/object/enterpriseorganizationmembershipconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseorganizationmembershipconnection", - "/en/enterprise/2.20/v4/object/enterpriseorganizationmembershipconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseorganizationmembershipconnection", - "/enterprise/2.20/v4/object/enterpriseorganizationmembershipedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseorganizationmembershipedge", - "/en/enterprise/2.20/v4/object/enterpriseorganizationmembershipedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseorganizationmembershipedge", - "/enterprise/2.20/v4/object/enterpriseoutsidecollaboratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", - "/en/enterprise/2.20/v4/object/enterpriseoutsidecollaboratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", - "/enterprise/2.20/v4/object/enterpriseoutsidecollaboratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseoutsidecollaboratoredge", - "/en/enterprise/2.20/v4/object/enterpriseoutsidecollaboratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseoutsidecollaboratoredge", - "/enterprise/2.20/v4/object/enterpriseownerinfo": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseownerinfo", - "/en/enterprise/2.20/v4/object/enterpriseownerinfo": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseownerinfo", - "/enterprise/2.20/v4/object/enterprisependingcollaboratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingcollaboratorconnection", - "/en/enterprise/2.20/v4/object/enterprisependingcollaboratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingcollaboratorconnection", - "/enterprise/2.20/v4/object/enterprisependingcollaboratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingcollaboratoredge", - "/en/enterprise/2.20/v4/object/enterprisependingcollaboratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingcollaboratoredge", - "/enterprise/2.20/v4/object/enterprisependingmemberinvitationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingmemberinvitationconnection", - "/en/enterprise/2.20/v4/object/enterprisependingmemberinvitationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingmemberinvitationconnection", - "/enterprise/2.20/v4/object/enterprisependingmemberinvitationedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingmemberinvitationedge", - "/en/enterprise/2.20/v4/object/enterprisependingmemberinvitationedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterprisependingmemberinvitationedge", - "/enterprise/2.20/v4/object/enterpriserepositoryinfo": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfo", - "/en/enterprise/2.20/v4/object/enterpriserepositoryinfo": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfo", - "/enterprise/2.20/v4/object/enterpriserepositoryinfoconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfoconnection", - "/en/enterprise/2.20/v4/object/enterpriserepositoryinfoconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfoconnection", - "/enterprise/2.20/v4/object/enterpriserepositoryinfoedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfoedge", - "/en/enterprise/2.20/v4/object/enterpriserepositoryinfoedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfoedge", - "/enterprise/2.20/v4/object/enterpriseserverinstallation": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserverinstallation", - "/en/enterprise/2.20/v4/object/enterpriseserverinstallation": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserverinstallation", - "/enterprise/2.20/v4/object/enterpriseserveruseraccount": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccount", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccount": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccount", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountconnection", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountconnection", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountedge", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountedge", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountemail": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemail", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountemail": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemail", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountemailconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemailconnection", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountemailconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemailconnection", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountemailedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemailedge", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountemailedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemailedge", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountsupload": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsupload", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountsupload": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsupload", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountsuploadconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountsuploadconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", - "/enterprise/2.20/v4/object/enterpriseserveruseraccountsuploadedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", - "/en/enterprise/2.20/v4/object/enterpriseserveruseraccountsuploadedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", - "/enterprise/2.20/v4/object/enterpriseuseraccount": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccount", - "/en/enterprise/2.20/v4/object/enterpriseuseraccount": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccount", - "/enterprise/2.20/v4/object/enterpriseuseraccountconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccountconnection", - "/en/enterprise/2.20/v4/object/enterpriseuseraccountconnection": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccountconnection", - "/enterprise/2.20/v4/object/enterpriseuseraccountedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccountedge", - "/en/enterprise/2.20/v4/object/enterpriseuseraccountedge": "/en/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccountedge", - "/enterprise/2.20/v4/object/externalidentity": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentity", - "/en/enterprise/2.20/v4/object/externalidentity": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentity", - "/enterprise/2.20/v4/object/externalidentityconnection": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentityconnection", - "/en/enterprise/2.20/v4/object/externalidentityconnection": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentityconnection", - "/enterprise/2.20/v4/object/externalidentityedge": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentityedge", - "/en/enterprise/2.20/v4/object/externalidentityedge": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentityedge", - "/enterprise/2.20/v4/object/externalidentitysamlattributes": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentitysamlattributes", - "/en/enterprise/2.20/v4/object/externalidentitysamlattributes": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentitysamlattributes", - "/enterprise/2.20/v4/object/externalidentityscimattributes": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentityscimattributes", - "/en/enterprise/2.20/v4/object/externalidentityscimattributes": "/en/enterprise-server@2.20/graphql/reference/objects#externalidentityscimattributes", - "/enterprise/2.20/v4/object/followerconnection": "/en/enterprise-server@2.20/graphql/reference/objects#followerconnection", - "/en/enterprise/2.20/v4/object/followerconnection": "/en/enterprise-server@2.20/graphql/reference/objects#followerconnection", - "/enterprise/2.20/v4/object/followingconnection": "/en/enterprise-server@2.20/graphql/reference/objects#followingconnection", - "/en/enterprise/2.20/v4/object/followingconnection": "/en/enterprise-server@2.20/graphql/reference/objects#followingconnection", - "/enterprise/2.20/v4/object/followuserpayload": "/en/enterprise-server@2.20/graphql/reference/objects#followuserpayload", - "/en/enterprise/2.20/v4/object/followuserpayload": "/en/enterprise-server@2.20/graphql/reference/objects#followuserpayload", - "/enterprise/2.20/v4/object/generichovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#generichovercardcontext", - "/en/enterprise/2.20/v4/object/generichovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#generichovercardcontext", - "/enterprise/2.20/v4/object/gist": "/en/enterprise-server@2.20/graphql/reference/objects#gist", - "/en/enterprise/2.20/v4/object/gist": "/en/enterprise-server@2.20/graphql/reference/objects#gist", - "/enterprise/2.20/v4/object/gistcomment": "/en/enterprise-server@2.20/graphql/reference/objects#gistcomment", - "/en/enterprise/2.20/v4/object/gistcomment": "/en/enterprise-server@2.20/graphql/reference/objects#gistcomment", - "/enterprise/2.20/v4/object/gistcommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#gistcommentconnection", - "/en/enterprise/2.20/v4/object/gistcommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#gistcommentconnection", - "/enterprise/2.20/v4/object/gistcommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#gistcommentedge", - "/en/enterprise/2.20/v4/object/gistcommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#gistcommentedge", - "/enterprise/2.20/v4/object/gistconnection": "/en/enterprise-server@2.20/graphql/reference/objects#gistconnection", - "/en/enterprise/2.20/v4/object/gistconnection": "/en/enterprise-server@2.20/graphql/reference/objects#gistconnection", - "/enterprise/2.20/v4/object/gistedge": "/en/enterprise-server@2.20/graphql/reference/objects#gistedge", - "/en/enterprise/2.20/v4/object/gistedge": "/en/enterprise-server@2.20/graphql/reference/objects#gistedge", - "/enterprise/2.20/v4/object/gistfile": "/en/enterprise-server@2.20/graphql/reference/objects#gistfile", - "/en/enterprise/2.20/v4/object/gistfile": "/en/enterprise-server@2.20/graphql/reference/objects#gistfile", - "/enterprise/2.20/v4/object/gitactor": "/en/enterprise-server@2.20/graphql/reference/objects#gitactor", - "/en/enterprise/2.20/v4/object/gitactor": "/en/enterprise-server@2.20/graphql/reference/objects#gitactor", - "/enterprise/2.20/v4/object/githubmetadata": "/en/enterprise-server@2.20/graphql/reference/objects#githubmetadata", - "/en/enterprise/2.20/v4/object/githubmetadata": "/en/enterprise-server@2.20/graphql/reference/objects#githubmetadata", - "/enterprise/2.20/v4/object/gpgsignature": "/en/enterprise-server@2.20/graphql/reference/objects#gpgsignature", - "/en/enterprise/2.20/v4/object/gpgsignature": "/en/enterprise-server@2.20/graphql/reference/objects#gpgsignature", - "/enterprise/2.20/v4/object/headrefdeletedevent": "/en/enterprise-server@2.20/graphql/reference/objects#headrefdeletedevent", - "/en/enterprise/2.20/v4/object/headrefdeletedevent": "/en/enterprise-server@2.20/graphql/reference/objects#headrefdeletedevent", - "/enterprise/2.20/v4/object/headrefforcepushedevent": "/en/enterprise-server@2.20/graphql/reference/objects#headrefforcepushedevent", - "/en/enterprise/2.20/v4/object/headrefforcepushedevent": "/en/enterprise-server@2.20/graphql/reference/objects#headrefforcepushedevent", - "/enterprise/2.20/v4/object/headrefrestoredevent": "/en/enterprise-server@2.20/graphql/reference/objects#headrefrestoredevent", - "/en/enterprise/2.20/v4/object/headrefrestoredevent": "/en/enterprise-server@2.20/graphql/reference/objects#headrefrestoredevent", - "/enterprise/2.20/v4/object/hovercard": "/en/enterprise-server@2.20/graphql/reference/objects#hovercard", - "/en/enterprise/2.20/v4/object/hovercard": "/en/enterprise-server@2.20/graphql/reference/objects#hovercard", - "/enterprise/2.20/v4/object/importprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#importprojectpayload", - "/en/enterprise/2.20/v4/object/importprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#importprojectpayload", - "/enterprise/2.20/v4/object/issue": "/en/enterprise-server@2.20/graphql/reference/objects#issue", - "/en/enterprise/2.20/v4/object/issue": "/en/enterprise-server@2.20/graphql/reference/objects#issue", - "/enterprise/2.20/v4/object/issuecomment": "/en/enterprise-server@2.20/graphql/reference/objects#issuecomment", - "/en/enterprise/2.20/v4/object/issuecomment": "/en/enterprise-server@2.20/graphql/reference/objects#issuecomment", - "/enterprise/2.20/v4/object/issuecommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issuecommentconnection", - "/en/enterprise/2.20/v4/object/issuecommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issuecommentconnection", - "/enterprise/2.20/v4/object/issuecommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#issuecommentedge", - "/en/enterprise/2.20/v4/object/issuecommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#issuecommentedge", - "/enterprise/2.20/v4/object/issueconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issueconnection", - "/en/enterprise/2.20/v4/object/issueconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issueconnection", - "/enterprise/2.20/v4/object/issuecontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#issuecontributionsbyrepository", - "/en/enterprise/2.20/v4/object/issuecontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#issuecontributionsbyrepository", - "/enterprise/2.20/v4/object/issueedge": "/en/enterprise-server@2.20/graphql/reference/objects#issueedge", - "/en/enterprise/2.20/v4/object/issueedge": "/en/enterprise-server@2.20/graphql/reference/objects#issueedge", - "/enterprise/2.20/v4/object/issuetimelineconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineconnection", - "/en/enterprise/2.20/v4/object/issuetimelineconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineconnection", - "/enterprise/2.20/v4/object/issuetimelineitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemedge", - "/en/enterprise/2.20/v4/object/issuetimelineitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemedge", - "/enterprise/2.20/v4/object/issuetimelineitemsconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemsconnection", - "/en/enterprise/2.20/v4/object/issuetimelineitemsconnection": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemsconnection", - "/enterprise/2.20/v4/object/issuetimelineitemsedge": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemsedge", - "/en/enterprise/2.20/v4/object/issuetimelineitemsedge": "/en/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemsedge", - "/enterprise/2.20/v4/object/joinedgithubcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#joinedgithubcontribution", - "/en/enterprise/2.20/v4/object/joinedgithubcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#joinedgithubcontribution", - "/enterprise/2.20/v4/object/label": "/en/enterprise-server@2.20/graphql/reference/objects#label", - "/en/enterprise/2.20/v4/object/label": "/en/enterprise-server@2.20/graphql/reference/objects#label", - "/enterprise/2.20/v4/object/labelconnection": "/en/enterprise-server@2.20/graphql/reference/objects#labelconnection", - "/en/enterprise/2.20/v4/object/labelconnection": "/en/enterprise-server@2.20/graphql/reference/objects#labelconnection", - "/enterprise/2.20/v4/object/labeledevent": "/en/enterprise-server@2.20/graphql/reference/objects#labeledevent", - "/en/enterprise/2.20/v4/object/labeledevent": "/en/enterprise-server@2.20/graphql/reference/objects#labeledevent", - "/enterprise/2.20/v4/object/labeledge": "/en/enterprise-server@2.20/graphql/reference/objects#labeledge", - "/en/enterprise/2.20/v4/object/labeledge": "/en/enterprise-server@2.20/graphql/reference/objects#labeledge", - "/enterprise/2.20/v4/object/language": "/en/enterprise-server@2.20/graphql/reference/objects#language", - "/en/enterprise/2.20/v4/object/language": "/en/enterprise-server@2.20/graphql/reference/objects#language", - "/enterprise/2.20/v4/object/languageconnection": "/en/enterprise-server@2.20/graphql/reference/objects#languageconnection", - "/en/enterprise/2.20/v4/object/languageconnection": "/en/enterprise-server@2.20/graphql/reference/objects#languageconnection", - "/enterprise/2.20/v4/object/languageedge": "/en/enterprise-server@2.20/graphql/reference/objects#languageedge", - "/en/enterprise/2.20/v4/object/languageedge": "/en/enterprise-server@2.20/graphql/reference/objects#languageedge", - "/enterprise/2.20/v4/object/license": "/en/enterprise-server@2.20/graphql/reference/objects#license", - "/en/enterprise/2.20/v4/object/license": "/en/enterprise-server@2.20/graphql/reference/objects#license", - "/enterprise/2.20/v4/object/licenserule": "/en/enterprise-server@2.20/graphql/reference/objects#licenserule", - "/en/enterprise/2.20/v4/object/licenserule": "/en/enterprise-server@2.20/graphql/reference/objects#licenserule", - "/enterprise/2.20/v4/object/linkrepositorytoprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#linkrepositorytoprojectpayload", - "/en/enterprise/2.20/v4/object/linkrepositorytoprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#linkrepositorytoprojectpayload", - "/enterprise/2.20/v4/object/lockedevent": "/en/enterprise-server@2.20/graphql/reference/objects#lockedevent", - "/en/enterprise/2.20/v4/object/lockedevent": "/en/enterprise-server@2.20/graphql/reference/objects#lockedevent", - "/enterprise/2.20/v4/object/locklockablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#locklockablepayload", - "/en/enterprise/2.20/v4/object/locklockablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#locklockablepayload", - "/enterprise/2.20/v4/object/mannequin": "/en/enterprise-server@2.20/graphql/reference/objects#mannequin", - "/en/enterprise/2.20/v4/object/mannequin": "/en/enterprise-server@2.20/graphql/reference/objects#mannequin", - "/enterprise/2.20/v4/object/markedasduplicateevent": "/en/enterprise-server@2.20/graphql/reference/objects#markedasduplicateevent", - "/en/enterprise/2.20/v4/object/markedasduplicateevent": "/en/enterprise-server@2.20/graphql/reference/objects#markedasduplicateevent", - "/enterprise/2.20/v4/object/markpullrequestreadyforreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#markpullrequestreadyforreviewpayload", - "/en/enterprise/2.20/v4/object/markpullrequestreadyforreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#markpullrequestreadyforreviewpayload", - "/enterprise/2.20/v4/object/memberscandeletereposclearauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposclearauditentry", - "/en/enterprise/2.20/v4/object/memberscandeletereposclearauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposclearauditentry", - "/enterprise/2.20/v4/object/memberscandeletereposdisableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposdisableauditentry", - "/en/enterprise/2.20/v4/object/memberscandeletereposdisableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposdisableauditentry", - "/enterprise/2.20/v4/object/memberscandeletereposenableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposenableauditentry", - "/en/enterprise/2.20/v4/object/memberscandeletereposenableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposenableauditentry", - "/enterprise/2.20/v4/object/mentionedevent": "/en/enterprise-server@2.20/graphql/reference/objects#mentionedevent", - "/en/enterprise/2.20/v4/object/mentionedevent": "/en/enterprise-server@2.20/graphql/reference/objects#mentionedevent", - "/enterprise/2.20/v4/object/mergebranchpayload": "/en/enterprise-server@2.20/graphql/reference/objects#mergebranchpayload", - "/en/enterprise/2.20/v4/object/mergebranchpayload": "/en/enterprise-server@2.20/graphql/reference/objects#mergebranchpayload", - "/enterprise/2.20/v4/object/mergedevent": "/en/enterprise-server@2.20/graphql/reference/objects#mergedevent", - "/en/enterprise/2.20/v4/object/mergedevent": "/en/enterprise-server@2.20/graphql/reference/objects#mergedevent", - "/enterprise/2.20/v4/object/mergepullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#mergepullrequestpayload", - "/en/enterprise/2.20/v4/object/mergepullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#mergepullrequestpayload", - "/enterprise/2.20/v4/object/milestone": "/en/enterprise-server@2.20/graphql/reference/objects#milestone", - "/en/enterprise/2.20/v4/object/milestone": "/en/enterprise-server@2.20/graphql/reference/objects#milestone", - "/enterprise/2.20/v4/object/milestoneconnection": "/en/enterprise-server@2.20/graphql/reference/objects#milestoneconnection", - "/en/enterprise/2.20/v4/object/milestoneconnection": "/en/enterprise-server@2.20/graphql/reference/objects#milestoneconnection", - "/enterprise/2.20/v4/object/milestonedevent": "/en/enterprise-server@2.20/graphql/reference/objects#milestonedevent", - "/en/enterprise/2.20/v4/object/milestonedevent": "/en/enterprise-server@2.20/graphql/reference/objects#milestonedevent", - "/enterprise/2.20/v4/object/milestoneedge": "/en/enterprise-server@2.20/graphql/reference/objects#milestoneedge", - "/en/enterprise/2.20/v4/object/milestoneedge": "/en/enterprise-server@2.20/graphql/reference/objects#milestoneedge", - "/enterprise/2.20/v4/object/minimizecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#minimizecommentpayload", - "/en/enterprise/2.20/v4/object/minimizecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#minimizecommentpayload", - "/enterprise/2.20/v4/object/movedcolumnsinprojectevent": "/en/enterprise-server@2.20/graphql/reference/objects#movedcolumnsinprojectevent", - "/en/enterprise/2.20/v4/object/movedcolumnsinprojectevent": "/en/enterprise-server@2.20/graphql/reference/objects#movedcolumnsinprojectevent", - "/enterprise/2.20/v4/object/moveprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#moveprojectcardpayload", - "/en/enterprise/2.20/v4/object/moveprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#moveprojectcardpayload", - "/enterprise/2.20/v4/object/moveprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#moveprojectcolumnpayload", - "/en/enterprise/2.20/v4/object/moveprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#moveprojectcolumnpayload", - "/enterprise/2.20/v4/object/oauthapplicationcreateauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#oauthapplicationcreateauditentry", - "/en/enterprise/2.20/v4/object/oauthapplicationcreateauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#oauthapplicationcreateauditentry", - "/enterprise/2.20/v4/object/orgaddbillingmanagerauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgaddbillingmanagerauditentry", - "/en/enterprise/2.20/v4/object/orgaddbillingmanagerauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgaddbillingmanagerauditentry", - "/enterprise/2.20/v4/object/orgaddmemberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgaddmemberauditentry", - "/en/enterprise/2.20/v4/object/orgaddmemberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgaddmemberauditentry", - "/enterprise/2.20/v4/object/organization": "/en/enterprise-server@2.20/graphql/reference/objects#organization", - "/en/enterprise/2.20/v4/object/organization": "/en/enterprise-server@2.20/graphql/reference/objects#organization", - "/enterprise/2.20/v4/object/organizationauditentryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationauditentryconnection", - "/en/enterprise/2.20/v4/object/organizationauditentryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationauditentryconnection", - "/enterprise/2.20/v4/object/organizationauditentryedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationauditentryedge", - "/en/enterprise/2.20/v4/object/organizationauditentryedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationauditentryedge", - "/enterprise/2.20/v4/object/organizationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationconnection", - "/en/enterprise/2.20/v4/object/organizationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationconnection", - "/enterprise/2.20/v4/object/organizationedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationedge", - "/en/enterprise/2.20/v4/object/organizationedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationedge", - "/enterprise/2.20/v4/object/organizationidentityprovider": "/en/enterprise-server@2.20/graphql/reference/objects#organizationidentityprovider", - "/en/enterprise/2.20/v4/object/organizationidentityprovider": "/en/enterprise-server@2.20/graphql/reference/objects#organizationidentityprovider", - "/enterprise/2.20/v4/object/organizationinvitation": "/en/enterprise-server@2.20/graphql/reference/objects#organizationinvitation", - "/en/enterprise/2.20/v4/object/organizationinvitation": "/en/enterprise-server@2.20/graphql/reference/objects#organizationinvitation", - "/enterprise/2.20/v4/object/organizationinvitationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationinvitationconnection", - "/en/enterprise/2.20/v4/object/organizationinvitationconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationinvitationconnection", - "/enterprise/2.20/v4/object/organizationinvitationedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationinvitationedge", - "/en/enterprise/2.20/v4/object/organizationinvitationedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationinvitationedge", - "/enterprise/2.20/v4/object/organizationmemberconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationmemberconnection", - "/en/enterprise/2.20/v4/object/organizationmemberconnection": "/en/enterprise-server@2.20/graphql/reference/objects#organizationmemberconnection", - "/enterprise/2.20/v4/object/organizationmemberedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationmemberedge", - "/en/enterprise/2.20/v4/object/organizationmemberedge": "/en/enterprise-server@2.20/graphql/reference/objects#organizationmemberedge", - "/enterprise/2.20/v4/object/organizationshovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#organizationshovercardcontext", - "/en/enterprise/2.20/v4/object/organizationshovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#organizationshovercardcontext", - "/enterprise/2.20/v4/object/organizationteamshovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#organizationteamshovercardcontext", - "/en/enterprise/2.20/v4/object/organizationteamshovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#organizationteamshovercardcontext", - "/enterprise/2.20/v4/object/orgblockuserauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgblockuserauditentry", - "/en/enterprise/2.20/v4/object/orgblockuserauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgblockuserauditentry", - "/enterprise/2.20/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", - "/en/enterprise/2.20/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", - "/enterprise/2.20/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", - "/en/enterprise/2.20/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", - "/enterprise/2.20/v4/object/orgcreateauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgcreateauditentry", - "/en/enterprise/2.20/v4/object/orgcreateauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgcreateauditentry", - "/enterprise/2.20/v4/object/orgdisableoauthapprestrictionsauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", - "/en/enterprise/2.20/v4/object/orgdisableoauthapprestrictionsauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", - "/enterprise/2.20/v4/object/orgdisablesamlauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgdisablesamlauditentry", - "/en/enterprise/2.20/v4/object/orgdisablesamlauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgdisablesamlauditentry", - "/enterprise/2.20/v4/object/orgdisabletwofactorrequirementauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", - "/en/enterprise/2.20/v4/object/orgdisabletwofactorrequirementauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", - "/enterprise/2.20/v4/object/orgenableoauthapprestrictionsauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", - "/en/enterprise/2.20/v4/object/orgenableoauthapprestrictionsauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", - "/enterprise/2.20/v4/object/orgenablesamlauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgenablesamlauditentry", - "/en/enterprise/2.20/v4/object/orgenablesamlauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgenablesamlauditentry", - "/enterprise/2.20/v4/object/orgenabletwofactorrequirementauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgenabletwofactorrequirementauditentry", - "/en/enterprise/2.20/v4/object/orgenabletwofactorrequirementauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgenabletwofactorrequirementauditentry", - "/enterprise/2.20/v4/object/orginvitememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orginvitememberauditentry", - "/en/enterprise/2.20/v4/object/orginvitememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orginvitememberauditentry", - "/enterprise/2.20/v4/object/orginvitetobusinessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orginvitetobusinessauditentry", - "/en/enterprise/2.20/v4/object/orginvitetobusinessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orginvitetobusinessauditentry", - "/enterprise/2.20/v4/object/orgoauthappaccessapprovedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessapprovedauditentry", - "/en/enterprise/2.20/v4/object/orgoauthappaccessapprovedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessapprovedauditentry", - "/enterprise/2.20/v4/object/orgoauthappaccessdeniedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessdeniedauditentry", - "/en/enterprise/2.20/v4/object/orgoauthappaccessdeniedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessdeniedauditentry", - "/enterprise/2.20/v4/object/orgoauthappaccessrequestedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessrequestedauditentry", - "/en/enterprise/2.20/v4/object/orgoauthappaccessrequestedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessrequestedauditentry", - "/enterprise/2.20/v4/object/orgremovebillingmanagerauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgremovebillingmanagerauditentry", - "/en/enterprise/2.20/v4/object/orgremovebillingmanagerauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgremovebillingmanagerauditentry", - "/enterprise/2.20/v4/object/orgremovememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgremovememberauditentry", - "/en/enterprise/2.20/v4/object/orgremovememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgremovememberauditentry", - "/enterprise/2.20/v4/object/orgremoveoutsidecollaboratorauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", - "/en/enterprise/2.20/v4/object/orgremoveoutsidecollaboratorauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", - "/enterprise/2.20/v4/object/orgrestorememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestorememberauditentry", - "/en/enterprise/2.20/v4/object/orgrestorememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestorememberauditentry", - "/enterprise/2.20/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", - "/en/enterprise/2.20/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", - "/enterprise/2.20/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", - "/en/enterprise/2.20/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", - "/enterprise/2.20/v4/object/orgrestoremembermembershipteamauditentrydata": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", - "/en/enterprise/2.20/v4/object/orgrestoremembermembershipteamauditentrydata": "/en/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", - "/enterprise/2.20/v4/object/orgunblockuserauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgunblockuserauditentry", - "/en/enterprise/2.20/v4/object/orgunblockuserauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgunblockuserauditentry", - "/enterprise/2.20/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", - "/en/enterprise/2.20/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", - "/enterprise/2.20/v4/object/orgupdatememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatememberauditentry", - "/en/enterprise/2.20/v4/object/orgupdatememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatememberauditentry", - "/enterprise/2.20/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", - "/en/enterprise/2.20/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", - "/enterprise/2.20/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", - "/en/enterprise/2.20/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", - "/enterprise/2.20/v4/object/package": "/en/enterprise-server@2.20/graphql/reference/objects#package", - "/en/enterprise/2.20/v4/object/package": "/en/enterprise-server@2.20/graphql/reference/objects#package", - "/enterprise/2.20/v4/object/packageconnection": "/en/enterprise-server@2.20/graphql/reference/objects#packageconnection", - "/en/enterprise/2.20/v4/object/packageconnection": "/en/enterprise-server@2.20/graphql/reference/objects#packageconnection", - "/enterprise/2.20/v4/object/packageedge": "/en/enterprise-server@2.20/graphql/reference/objects#packageedge", - "/en/enterprise/2.20/v4/object/packageedge": "/en/enterprise-server@2.20/graphql/reference/objects#packageedge", - "/enterprise/2.20/v4/object/packagefile": "/en/enterprise-server@2.20/graphql/reference/objects#packagefile", - "/en/enterprise/2.20/v4/object/packagefile": "/en/enterprise-server@2.20/graphql/reference/objects#packagefile", - "/enterprise/2.20/v4/object/packagefileconnection": "/en/enterprise-server@2.20/graphql/reference/objects#packagefileconnection", - "/en/enterprise/2.20/v4/object/packagefileconnection": "/en/enterprise-server@2.20/graphql/reference/objects#packagefileconnection", - "/enterprise/2.20/v4/object/packagefileedge": "/en/enterprise-server@2.20/graphql/reference/objects#packagefileedge", - "/en/enterprise/2.20/v4/object/packagefileedge": "/en/enterprise-server@2.20/graphql/reference/objects#packagefileedge", - "/enterprise/2.20/v4/object/packagestatistics": "/en/enterprise-server@2.20/graphql/reference/objects#packagestatistics", - "/en/enterprise/2.20/v4/object/packagestatistics": "/en/enterprise-server@2.20/graphql/reference/objects#packagestatistics", - "/enterprise/2.20/v4/object/packagetag": "/en/enterprise-server@2.20/graphql/reference/objects#packagetag", - "/en/enterprise/2.20/v4/object/packagetag": "/en/enterprise-server@2.20/graphql/reference/objects#packagetag", - "/enterprise/2.20/v4/object/packageversion": "/en/enterprise-server@2.20/graphql/reference/objects#packageversion", - "/en/enterprise/2.20/v4/object/packageversion": "/en/enterprise-server@2.20/graphql/reference/objects#packageversion", - "/enterprise/2.20/v4/object/packageversionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#packageversionconnection", - "/en/enterprise/2.20/v4/object/packageversionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#packageversionconnection", - "/enterprise/2.20/v4/object/packageversionedge": "/en/enterprise-server@2.20/graphql/reference/objects#packageversionedge", - "/en/enterprise/2.20/v4/object/packageversionedge": "/en/enterprise-server@2.20/graphql/reference/objects#packageversionedge", - "/enterprise/2.20/v4/object/packageversionstatistics": "/en/enterprise-server@2.20/graphql/reference/objects#packageversionstatistics", - "/en/enterprise/2.20/v4/object/packageversionstatistics": "/en/enterprise-server@2.20/graphql/reference/objects#packageversionstatistics", - "/enterprise/2.20/v4/object/pageinfo": "/en/enterprise-server@2.20/graphql/reference/objects#pageinfo", - "/en/enterprise/2.20/v4/object/pageinfo": "/en/enterprise-server@2.20/graphql/reference/objects#pageinfo", - "/enterprise/2.20/v4/object/permissionsource": "/en/enterprise-server@2.20/graphql/reference/objects#permissionsource", - "/en/enterprise/2.20/v4/object/permissionsource": "/en/enterprise-server@2.20/graphql/reference/objects#permissionsource", - "/enterprise/2.20/v4/object/pinissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#pinissuepayload", - "/en/enterprise/2.20/v4/object/pinissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#pinissuepayload", - "/enterprise/2.20/v4/object/pinnableitemconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pinnableitemconnection", - "/en/enterprise/2.20/v4/object/pinnableitemconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pinnableitemconnection", - "/enterprise/2.20/v4/object/pinnableitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#pinnableitemedge", - "/en/enterprise/2.20/v4/object/pinnableitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#pinnableitemedge", - "/enterprise/2.20/v4/object/pinnedevent": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedevent", - "/en/enterprise/2.20/v4/object/pinnedevent": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedevent", - "/enterprise/2.20/v4/object/pinnedissue": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedissue", - "/en/enterprise/2.20/v4/object/pinnedissue": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedissue", - "/enterprise/2.20/v4/object/pinnedissueconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedissueconnection", - "/en/enterprise/2.20/v4/object/pinnedissueconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedissueconnection", - "/enterprise/2.20/v4/object/pinnedissueedge": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedissueedge", - "/en/enterprise/2.20/v4/object/pinnedissueedge": "/en/enterprise-server@2.20/graphql/reference/objects#pinnedissueedge", - "/enterprise/2.20/v4/object/privaterepositoryforkingdisableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#privaterepositoryforkingdisableauditentry", - "/en/enterprise/2.20/v4/object/privaterepositoryforkingdisableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#privaterepositoryforkingdisableauditentry", - "/enterprise/2.20/v4/object/privaterepositoryforkingenableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#privaterepositoryforkingenableauditentry", - "/en/enterprise/2.20/v4/object/privaterepositoryforkingenableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#privaterepositoryforkingenableauditentry", - "/enterprise/2.20/v4/object/profileitemshowcase": "/en/enterprise-server@2.20/graphql/reference/objects#profileitemshowcase", - "/en/enterprise/2.20/v4/object/profileitemshowcase": "/en/enterprise-server@2.20/graphql/reference/objects#profileitemshowcase", - "/enterprise/2.20/v4/object/project": "/en/enterprise-server@2.20/graphql/reference/objects#project", - "/en/enterprise/2.20/v4/object/project": "/en/enterprise-server@2.20/graphql/reference/objects#project", - "/enterprise/2.20/v4/object/projectcard": "/en/enterprise-server@2.20/graphql/reference/objects#projectcard", - "/en/enterprise/2.20/v4/object/projectcard": "/en/enterprise-server@2.20/graphql/reference/objects#projectcard", - "/enterprise/2.20/v4/object/projectcardconnection": "/en/enterprise-server@2.20/graphql/reference/objects#projectcardconnection", - "/en/enterprise/2.20/v4/object/projectcardconnection": "/en/enterprise-server@2.20/graphql/reference/objects#projectcardconnection", - "/enterprise/2.20/v4/object/projectcardedge": "/en/enterprise-server@2.20/graphql/reference/objects#projectcardedge", - "/en/enterprise/2.20/v4/object/projectcardedge": "/en/enterprise-server@2.20/graphql/reference/objects#projectcardedge", - "/enterprise/2.20/v4/object/projectcolumn": "/en/enterprise-server@2.20/graphql/reference/objects#projectcolumn", - "/en/enterprise/2.20/v4/object/projectcolumn": "/en/enterprise-server@2.20/graphql/reference/objects#projectcolumn", - "/enterprise/2.20/v4/object/projectcolumnconnection": "/en/enterprise-server@2.20/graphql/reference/objects#projectcolumnconnection", - "/en/enterprise/2.20/v4/object/projectcolumnconnection": "/en/enterprise-server@2.20/graphql/reference/objects#projectcolumnconnection", - "/enterprise/2.20/v4/object/projectcolumnedge": "/en/enterprise-server@2.20/graphql/reference/objects#projectcolumnedge", - "/en/enterprise/2.20/v4/object/projectcolumnedge": "/en/enterprise-server@2.20/graphql/reference/objects#projectcolumnedge", - "/enterprise/2.20/v4/object/projectconnection": "/en/enterprise-server@2.20/graphql/reference/objects#projectconnection", - "/en/enterprise/2.20/v4/object/projectconnection": "/en/enterprise-server@2.20/graphql/reference/objects#projectconnection", - "/enterprise/2.20/v4/object/projectedge": "/en/enterprise-server@2.20/graphql/reference/objects#projectedge", - "/en/enterprise/2.20/v4/object/projectedge": "/en/enterprise-server@2.20/graphql/reference/objects#projectedge", - "/enterprise/2.20/v4/object/publickey": "/en/enterprise-server@2.20/graphql/reference/objects#publickey", - "/en/enterprise/2.20/v4/object/publickey": "/en/enterprise-server@2.20/graphql/reference/objects#publickey", - "/enterprise/2.20/v4/object/publickeyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#publickeyconnection", - "/en/enterprise/2.20/v4/object/publickeyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#publickeyconnection", - "/enterprise/2.20/v4/object/publickeyedge": "/en/enterprise-server@2.20/graphql/reference/objects#publickeyedge", - "/en/enterprise/2.20/v4/object/publickeyedge": "/en/enterprise-server@2.20/graphql/reference/objects#publickeyedge", - "/enterprise/2.20/v4/object/pullrequest": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequest", - "/en/enterprise/2.20/v4/object/pullrequest": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequest", - "/enterprise/2.20/v4/object/pullrequestchangedfile": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfile", - "/en/enterprise/2.20/v4/object/pullrequestchangedfile": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfile", - "/enterprise/2.20/v4/object/pullrequestchangedfileconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfileconnection", - "/en/enterprise/2.20/v4/object/pullrequestchangedfileconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfileconnection", - "/enterprise/2.20/v4/object/pullrequestchangedfileedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfileedge", - "/en/enterprise/2.20/v4/object/pullrequestchangedfileedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfileedge", - "/enterprise/2.20/v4/object/pullrequestcommit": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommit", - "/en/enterprise/2.20/v4/object/pullrequestcommit": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommit", - "/enterprise/2.20/v4/object/pullrequestcommitcommentthread": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitcommentthread", - "/en/enterprise/2.20/v4/object/pullrequestcommitcommentthread": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitcommentthread", - "/enterprise/2.20/v4/object/pullrequestcommitconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitconnection", - "/en/enterprise/2.20/v4/object/pullrequestcommitconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitconnection", - "/enterprise/2.20/v4/object/pullrequestcommitedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitedge", - "/en/enterprise/2.20/v4/object/pullrequestcommitedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitedge", - "/enterprise/2.20/v4/object/pullrequestconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestconnection", - "/en/enterprise/2.20/v4/object/pullrequestconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestconnection", - "/enterprise/2.20/v4/object/pullrequestcontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcontributionsbyrepository", - "/en/enterprise/2.20/v4/object/pullrequestcontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestcontributionsbyrepository", - "/enterprise/2.20/v4/object/pullrequestedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestedge", - "/en/enterprise/2.20/v4/object/pullrequestedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestedge", - "/enterprise/2.20/v4/object/pullrequestreview": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreview", - "/en/enterprise/2.20/v4/object/pullrequestreview": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreview", - "/enterprise/2.20/v4/object/pullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcomment", - "/en/enterprise/2.20/v4/object/pullrequestreviewcomment": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcomment", - "/enterprise/2.20/v4/object/pullrequestreviewcommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcommentconnection", - "/en/enterprise/2.20/v4/object/pullrequestreviewcommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcommentconnection", - "/enterprise/2.20/v4/object/pullrequestreviewcommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcommentedge", - "/en/enterprise/2.20/v4/object/pullrequestreviewcommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcommentedge", - "/enterprise/2.20/v4/object/pullrequestreviewconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewconnection", - "/en/enterprise/2.20/v4/object/pullrequestreviewconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewconnection", - "/enterprise/2.20/v4/object/pullrequestreviewcontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", - "/en/enterprise/2.20/v4/object/pullrequestreviewcontributionsbyrepository": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", - "/enterprise/2.20/v4/object/pullrequestreviewedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewedge", - "/en/enterprise/2.20/v4/object/pullrequestreviewedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewedge", - "/enterprise/2.20/v4/object/pullrequestreviewthread": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthread", - "/en/enterprise/2.20/v4/object/pullrequestreviewthread": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthread", - "/enterprise/2.20/v4/object/pullrequestreviewthreadconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthreadconnection", - "/en/enterprise/2.20/v4/object/pullrequestreviewthreadconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthreadconnection", - "/enterprise/2.20/v4/object/pullrequestreviewthreadedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthreadedge", - "/en/enterprise/2.20/v4/object/pullrequestreviewthreadedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthreadedge", - "/enterprise/2.20/v4/object/pullrequestrevisionmarker": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestrevisionmarker", - "/en/enterprise/2.20/v4/object/pullrequestrevisionmarker": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequestrevisionmarker", - "/enterprise/2.20/v4/object/pullrequesttimelineconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineconnection", - "/en/enterprise/2.20/v4/object/pullrequesttimelineconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineconnection", - "/enterprise/2.20/v4/object/pullrequesttimelineitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemedge", - "/en/enterprise/2.20/v4/object/pullrequesttimelineitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemedge", - "/enterprise/2.20/v4/object/pullrequesttimelineitemsconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemsconnection", - "/en/enterprise/2.20/v4/object/pullrequesttimelineitemsconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemsconnection", - "/enterprise/2.20/v4/object/pullrequesttimelineitemsedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemsedge", - "/en/enterprise/2.20/v4/object/pullrequesttimelineitemsedge": "/en/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemsedge", - "/enterprise/2.20/v4/object/push": "/en/enterprise-server@2.20/graphql/reference/objects#push", - "/en/enterprise/2.20/v4/object/push": "/en/enterprise-server@2.20/graphql/reference/objects#push", - "/enterprise/2.20/v4/object/pushallowance": "/en/enterprise-server@2.20/graphql/reference/objects#pushallowance", - "/en/enterprise/2.20/v4/object/pushallowance": "/en/enterprise-server@2.20/graphql/reference/objects#pushallowance", - "/enterprise/2.20/v4/object/pushallowanceconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pushallowanceconnection", - "/en/enterprise/2.20/v4/object/pushallowanceconnection": "/en/enterprise-server@2.20/graphql/reference/objects#pushallowanceconnection", - "/enterprise/2.20/v4/object/pushallowanceedge": "/en/enterprise-server@2.20/graphql/reference/objects#pushallowanceedge", - "/en/enterprise/2.20/v4/object/pushallowanceedge": "/en/enterprise-server@2.20/graphql/reference/objects#pushallowanceedge", - "/enterprise/2.20/v4/object/ratelimit": "/en/enterprise-server@2.20/graphql/reference/objects#ratelimit", - "/en/enterprise/2.20/v4/object/ratelimit": "/en/enterprise-server@2.20/graphql/reference/objects#ratelimit", - "/enterprise/2.20/v4/object/reactinguserconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reactinguserconnection", - "/en/enterprise/2.20/v4/object/reactinguserconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reactinguserconnection", - "/enterprise/2.20/v4/object/reactinguseredge": "/en/enterprise-server@2.20/graphql/reference/objects#reactinguseredge", - "/en/enterprise/2.20/v4/object/reactinguseredge": "/en/enterprise-server@2.20/graphql/reference/objects#reactinguseredge", - "/enterprise/2.20/v4/object/reaction": "/en/enterprise-server@2.20/graphql/reference/objects#reaction", - "/en/enterprise/2.20/v4/object/reaction": "/en/enterprise-server@2.20/graphql/reference/objects#reaction", - "/enterprise/2.20/v4/object/reactionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reactionconnection", - "/en/enterprise/2.20/v4/object/reactionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reactionconnection", - "/enterprise/2.20/v4/object/reactionedge": "/en/enterprise-server@2.20/graphql/reference/objects#reactionedge", - "/en/enterprise/2.20/v4/object/reactionedge": "/en/enterprise-server@2.20/graphql/reference/objects#reactionedge", - "/enterprise/2.20/v4/object/reactiongroup": "/en/enterprise-server@2.20/graphql/reference/objects#reactiongroup", - "/en/enterprise/2.20/v4/object/reactiongroup": "/en/enterprise-server@2.20/graphql/reference/objects#reactiongroup", - "/enterprise/2.20/v4/object/readyforreviewevent": "/en/enterprise-server@2.20/graphql/reference/objects#readyforreviewevent", - "/en/enterprise/2.20/v4/object/readyforreviewevent": "/en/enterprise-server@2.20/graphql/reference/objects#readyforreviewevent", - "/enterprise/2.20/v4/object/ref": "/en/enterprise-server@2.20/graphql/reference/objects#ref", - "/en/enterprise/2.20/v4/object/ref": "/en/enterprise-server@2.20/graphql/reference/objects#ref", - "/enterprise/2.20/v4/object/refconnection": "/en/enterprise-server@2.20/graphql/reference/objects#refconnection", - "/en/enterprise/2.20/v4/object/refconnection": "/en/enterprise-server@2.20/graphql/reference/objects#refconnection", - "/enterprise/2.20/v4/object/refedge": "/en/enterprise-server@2.20/graphql/reference/objects#refedge", - "/en/enterprise/2.20/v4/object/refedge": "/en/enterprise-server@2.20/graphql/reference/objects#refedge", - "/enterprise/2.20/v4/object/referencedevent": "/en/enterprise-server@2.20/graphql/reference/objects#referencedevent", - "/en/enterprise/2.20/v4/object/referencedevent": "/en/enterprise-server@2.20/graphql/reference/objects#referencedevent", - "/enterprise/2.20/v4/object/registrypackage": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackage", - "/en/enterprise/2.20/v4/object/registrypackage": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackage", - "/enterprise/2.20/v4/object/registrypackageconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageconnection", - "/en/enterprise/2.20/v4/object/registrypackageconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageconnection", - "/enterprise/2.20/v4/object/registrypackagedependency": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagedependency", - "/en/enterprise/2.20/v4/object/registrypackagedependency": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagedependency", - "/enterprise/2.20/v4/object/registrypackagedependencyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagedependencyconnection", - "/en/enterprise/2.20/v4/object/registrypackagedependencyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagedependencyconnection", - "/enterprise/2.20/v4/object/registrypackagedependencyedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagedependencyedge", - "/en/enterprise/2.20/v4/object/registrypackagedependencyedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagedependencyedge", - "/enterprise/2.20/v4/object/registrypackageedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageedge", - "/en/enterprise/2.20/v4/object/registrypackageedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageedge", - "/enterprise/2.20/v4/object/registrypackagefile": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagefile", - "/en/enterprise/2.20/v4/object/registrypackagefile": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagefile", - "/enterprise/2.20/v4/object/registrypackagefileconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagefileconnection", - "/en/enterprise/2.20/v4/object/registrypackagefileconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagefileconnection", - "/enterprise/2.20/v4/object/registrypackagefileedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagefileedge", - "/en/enterprise/2.20/v4/object/registrypackagefileedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagefileedge", - "/enterprise/2.20/v4/object/registrypackagestatistics": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagestatistics", - "/en/enterprise/2.20/v4/object/registrypackagestatistics": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagestatistics", - "/enterprise/2.20/v4/object/registrypackagetag": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagetag", - "/en/enterprise/2.20/v4/object/registrypackagetag": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagetag", - "/enterprise/2.20/v4/object/registrypackagetagconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagetagconnection", - "/en/enterprise/2.20/v4/object/registrypackagetagconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagetagconnection", - "/enterprise/2.20/v4/object/registrypackagetagedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagetagedge", - "/en/enterprise/2.20/v4/object/registrypackagetagedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackagetagedge", - "/enterprise/2.20/v4/object/registrypackageversion": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversion", - "/en/enterprise/2.20/v4/object/registrypackageversion": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversion", - "/enterprise/2.20/v4/object/registrypackageversionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversionconnection", - "/en/enterprise/2.20/v4/object/registrypackageversionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversionconnection", - "/enterprise/2.20/v4/object/registrypackageversionedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversionedge", - "/en/enterprise/2.20/v4/object/registrypackageversionedge": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversionedge", - "/enterprise/2.20/v4/object/registrypackageversionstatistics": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversionstatistics", - "/en/enterprise/2.20/v4/object/registrypackageversionstatistics": "/en/enterprise-server@2.20/graphql/reference/objects#registrypackageversionstatistics", - "/enterprise/2.20/v4/object/release": "/en/enterprise-server@2.20/graphql/reference/objects#release", - "/en/enterprise/2.20/v4/object/release": "/en/enterprise-server@2.20/graphql/reference/objects#release", - "/enterprise/2.20/v4/object/releaseasset": "/en/enterprise-server@2.20/graphql/reference/objects#releaseasset", - "/en/enterprise/2.20/v4/object/releaseasset": "/en/enterprise-server@2.20/graphql/reference/objects#releaseasset", - "/enterprise/2.20/v4/object/releaseassetconnection": "/en/enterprise-server@2.20/graphql/reference/objects#releaseassetconnection", - "/en/enterprise/2.20/v4/object/releaseassetconnection": "/en/enterprise-server@2.20/graphql/reference/objects#releaseassetconnection", - "/enterprise/2.20/v4/object/releaseassetedge": "/en/enterprise-server@2.20/graphql/reference/objects#releaseassetedge", - "/en/enterprise/2.20/v4/object/releaseassetedge": "/en/enterprise-server@2.20/graphql/reference/objects#releaseassetedge", - "/enterprise/2.20/v4/object/releaseconnection": "/en/enterprise-server@2.20/graphql/reference/objects#releaseconnection", - "/en/enterprise/2.20/v4/object/releaseconnection": "/en/enterprise-server@2.20/graphql/reference/objects#releaseconnection", - "/enterprise/2.20/v4/object/releaseedge": "/en/enterprise-server@2.20/graphql/reference/objects#releaseedge", - "/en/enterprise/2.20/v4/object/releaseedge": "/en/enterprise-server@2.20/graphql/reference/objects#releaseedge", - "/enterprise/2.20/v4/object/removeassigneesfromassignablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#removeassigneesfromassignablepayload", - "/en/enterprise/2.20/v4/object/removeassigneesfromassignablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#removeassigneesfromassignablepayload", - "/enterprise/2.20/v4/object/removedfromprojectevent": "/en/enterprise-server@2.20/graphql/reference/objects#removedfromprojectevent", - "/en/enterprise/2.20/v4/object/removedfromprojectevent": "/en/enterprise-server@2.20/graphql/reference/objects#removedfromprojectevent", - "/enterprise/2.20/v4/object/removeenterpriseadminpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removeenterpriseadminpayload", - "/en/enterprise/2.20/v4/object/removeenterpriseadminpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removeenterpriseadminpayload", - "/enterprise/2.20/v4/object/removelabelsfromlabelablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#removelabelsfromlabelablepayload", - "/en/enterprise/2.20/v4/object/removelabelsfromlabelablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#removelabelsfromlabelablepayload", - "/enterprise/2.20/v4/object/removeoutsidecollaboratorpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removeoutsidecollaboratorpayload", - "/en/enterprise/2.20/v4/object/removeoutsidecollaboratorpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removeoutsidecollaboratorpayload", - "/enterprise/2.20/v4/object/removereactionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removereactionpayload", - "/en/enterprise/2.20/v4/object/removereactionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removereactionpayload", - "/enterprise/2.20/v4/object/removestarpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removestarpayload", - "/en/enterprise/2.20/v4/object/removestarpayload": "/en/enterprise-server@2.20/graphql/reference/objects#removestarpayload", - "/enterprise/2.20/v4/object/renamedtitleevent": "/en/enterprise-server@2.20/graphql/reference/objects#renamedtitleevent", - "/en/enterprise/2.20/v4/object/renamedtitleevent": "/en/enterprise-server@2.20/graphql/reference/objects#renamedtitleevent", - "/enterprise/2.20/v4/object/reopenedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reopenedevent", - "/en/enterprise/2.20/v4/object/reopenedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reopenedevent", - "/enterprise/2.20/v4/object/reopenissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#reopenissuepayload", - "/en/enterprise/2.20/v4/object/reopenissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#reopenissuepayload", - "/enterprise/2.20/v4/object/reopenpullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#reopenpullrequestpayload", - "/en/enterprise/2.20/v4/object/reopenpullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#reopenpullrequestpayload", - "/enterprise/2.20/v4/object/repoaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoaccessauditentry", - "/en/enterprise/2.20/v4/object/repoaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoaccessauditentry", - "/enterprise/2.20/v4/object/repoaddmemberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoaddmemberauditentry", - "/en/enterprise/2.20/v4/object/repoaddmemberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoaddmemberauditentry", - "/enterprise/2.20/v4/object/repoaddtopicauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoaddtopicauditentry", - "/en/enterprise/2.20/v4/object/repoaddtopicauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoaddtopicauditentry", - "/enterprise/2.20/v4/object/repoarchivedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoarchivedauditentry", - "/en/enterprise/2.20/v4/object/repoarchivedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoarchivedauditentry", - "/enterprise/2.20/v4/object/repochangemergesettingauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repochangemergesettingauditentry", - "/en/enterprise/2.20/v4/object/repochangemergesettingauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repochangemergesettingauditentry", - "/enterprise/2.20/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", - "/en/enterprise/2.20/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", - "/enterprise/2.20/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", - "/en/enterprise/2.20/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", - "/enterprise/2.20/v4/object/repoconfigdisablecontributorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", - "/en/enterprise/2.20/v4/object/repoconfigdisablecontributorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", - "/enterprise/2.20/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", - "/en/enterprise/2.20/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", - "/enterprise/2.20/v4/object/repoconfigenableanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", - "/en/enterprise/2.20/v4/object/repoconfigenableanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", - "/enterprise/2.20/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", - "/en/enterprise/2.20/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", - "/enterprise/2.20/v4/object/repoconfigenablecontributorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", - "/en/enterprise/2.20/v4/object/repoconfigenablecontributorsonlyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", - "/enterprise/2.20/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", - "/en/enterprise/2.20/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", - "/enterprise/2.20/v4/object/repoconfiglockanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", - "/en/enterprise/2.20/v4/object/repoconfiglockanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", - "/enterprise/2.20/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", - "/en/enterprise/2.20/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", - "/enterprise/2.20/v4/object/repocreateauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repocreateauditentry", - "/en/enterprise/2.20/v4/object/repocreateauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repocreateauditentry", - "/enterprise/2.20/v4/object/repodestroyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repodestroyauditentry", - "/en/enterprise/2.20/v4/object/repodestroyauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repodestroyauditentry", - "/enterprise/2.20/v4/object/reporemovememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#reporemovememberauditentry", - "/en/enterprise/2.20/v4/object/reporemovememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#reporemovememberauditentry", - "/enterprise/2.20/v4/object/reporemovetopicauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#reporemovetopicauditentry", - "/en/enterprise/2.20/v4/object/reporemovetopicauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#reporemovetopicauditentry", - "/enterprise/2.20/v4/object/repository": "/en/enterprise-server@2.20/graphql/reference/objects#repository", - "/en/enterprise/2.20/v4/object/repository": "/en/enterprise-server@2.20/graphql/reference/objects#repository", - "/enterprise/2.20/v4/object/repositorycollaboratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositorycollaboratorconnection", - "/en/enterprise/2.20/v4/object/repositorycollaboratorconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositorycollaboratorconnection", - "/enterprise/2.20/v4/object/repositorycollaboratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#repositorycollaboratoredge", - "/en/enterprise/2.20/v4/object/repositorycollaboratoredge": "/en/enterprise-server@2.20/graphql/reference/objects#repositorycollaboratoredge", - "/enterprise/2.20/v4/object/repositoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryconnection", - "/en/enterprise/2.20/v4/object/repositoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryconnection", - "/enterprise/2.20/v4/object/repositoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryedge", - "/en/enterprise/2.20/v4/object/repositoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryedge", - "/enterprise/2.20/v4/object/repositoryinvitation": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryinvitation", - "/en/enterprise/2.20/v4/object/repositoryinvitation": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryinvitation", - "/enterprise/2.20/v4/object/repositorytopic": "/en/enterprise-server@2.20/graphql/reference/objects#repositorytopic", - "/en/enterprise/2.20/v4/object/repositorytopic": "/en/enterprise-server@2.20/graphql/reference/objects#repositorytopic", - "/enterprise/2.20/v4/object/repositorytopicconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositorytopicconnection", - "/en/enterprise/2.20/v4/object/repositorytopicconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositorytopicconnection", - "/enterprise/2.20/v4/object/repositorytopicedge": "/en/enterprise-server@2.20/graphql/reference/objects#repositorytopicedge", - "/en/enterprise/2.20/v4/object/repositorytopicedge": "/en/enterprise-server@2.20/graphql/reference/objects#repositorytopicedge", - "/enterprise/2.20/v4/object/repositoryvisibilitychangedisableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", - "/en/enterprise/2.20/v4/object/repositoryvisibilitychangedisableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", - "/enterprise/2.20/v4/object/repositoryvisibilitychangeenableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", - "/en/enterprise/2.20/v4/object/repositoryvisibilitychangeenableauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", - "/enterprise/2.20/v4/object/repositoryvulnerabilityalert": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalert", - "/en/enterprise/2.20/v4/object/repositoryvulnerabilityalert": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalert", - "/enterprise/2.20/v4/object/repositoryvulnerabilityalertconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalertconnection", - "/en/enterprise/2.20/v4/object/repositoryvulnerabilityalertconnection": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalertconnection", - "/enterprise/2.20/v4/object/repositoryvulnerabilityalertedge": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalertedge", - "/en/enterprise/2.20/v4/object/repositoryvulnerabilityalertedge": "/en/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalertedge", - "/enterprise/2.20/v4/object/requestreviewspayload": "/en/enterprise-server@2.20/graphql/reference/objects#requestreviewspayload", - "/en/enterprise/2.20/v4/object/requestreviewspayload": "/en/enterprise-server@2.20/graphql/reference/objects#requestreviewspayload", - "/enterprise/2.20/v4/object/rerequestchecksuitepayload": "/en/enterprise-server@2.20/graphql/reference/objects#rerequestchecksuitepayload", - "/en/enterprise/2.20/v4/object/rerequestchecksuitepayload": "/en/enterprise-server@2.20/graphql/reference/objects#rerequestchecksuitepayload", - "/enterprise/2.20/v4/object/resolvereviewthreadpayload": "/en/enterprise-server@2.20/graphql/reference/objects#resolvereviewthreadpayload", - "/en/enterprise/2.20/v4/object/resolvereviewthreadpayload": "/en/enterprise-server@2.20/graphql/reference/objects#resolvereviewthreadpayload", - "/enterprise/2.20/v4/object/restrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#restrictedcontribution", - "/en/enterprise/2.20/v4/object/restrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/objects#restrictedcontribution", - "/enterprise/2.20/v4/object/reviewdismissalallowance": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowance", - "/en/enterprise/2.20/v4/object/reviewdismissalallowance": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowance", - "/enterprise/2.20/v4/object/reviewdismissalallowanceconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowanceconnection", - "/en/enterprise/2.20/v4/object/reviewdismissalallowanceconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowanceconnection", - "/enterprise/2.20/v4/object/reviewdismissalallowanceedge": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowanceedge", - "/en/enterprise/2.20/v4/object/reviewdismissalallowanceedge": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowanceedge", - "/enterprise/2.20/v4/object/reviewdismissedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissedevent", - "/en/enterprise/2.20/v4/object/reviewdismissedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reviewdismissedevent", - "/enterprise/2.20/v4/object/reviewrequest": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequest", - "/en/enterprise/2.20/v4/object/reviewrequest": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequest", - "/enterprise/2.20/v4/object/reviewrequestconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestconnection", - "/en/enterprise/2.20/v4/object/reviewrequestconnection": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestconnection", - "/enterprise/2.20/v4/object/reviewrequestedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestedevent", - "/en/enterprise/2.20/v4/object/reviewrequestedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestedevent", - "/enterprise/2.20/v4/object/reviewrequestedge": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestedge", - "/en/enterprise/2.20/v4/object/reviewrequestedge": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestedge", - "/enterprise/2.20/v4/object/reviewrequestremovedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestremovedevent", - "/en/enterprise/2.20/v4/object/reviewrequestremovedevent": "/en/enterprise-server@2.20/graphql/reference/objects#reviewrequestremovedevent", - "/enterprise/2.20/v4/object/reviewstatushovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#reviewstatushovercardcontext", - "/en/enterprise/2.20/v4/object/reviewstatushovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#reviewstatushovercardcontext", - "/enterprise/2.20/v4/object/savedreply": "/en/enterprise-server@2.20/graphql/reference/objects#savedreply", - "/en/enterprise/2.20/v4/object/savedreply": "/en/enterprise-server@2.20/graphql/reference/objects#savedreply", - "/enterprise/2.20/v4/object/savedreplyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#savedreplyconnection", - "/en/enterprise/2.20/v4/object/savedreplyconnection": "/en/enterprise-server@2.20/graphql/reference/objects#savedreplyconnection", - "/enterprise/2.20/v4/object/savedreplyedge": "/en/enterprise-server@2.20/graphql/reference/objects#savedreplyedge", - "/en/enterprise/2.20/v4/object/savedreplyedge": "/en/enterprise-server@2.20/graphql/reference/objects#savedreplyedge", - "/enterprise/2.20/v4/object/searchresultitemconnection": "/en/enterprise-server@2.20/graphql/reference/objects#searchresultitemconnection", - "/en/enterprise/2.20/v4/object/searchresultitemconnection": "/en/enterprise-server@2.20/graphql/reference/objects#searchresultitemconnection", - "/enterprise/2.20/v4/object/searchresultitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#searchresultitemedge", - "/en/enterprise/2.20/v4/object/searchresultitemedge": "/en/enterprise-server@2.20/graphql/reference/objects#searchresultitemedge", - "/enterprise/2.20/v4/object/securityadvisory": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisory", - "/en/enterprise/2.20/v4/object/securityadvisory": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisory", - "/enterprise/2.20/v4/object/securityadvisoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryconnection", - "/en/enterprise/2.20/v4/object/securityadvisoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryconnection", - "/enterprise/2.20/v4/object/securityadvisoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryedge", - "/en/enterprise/2.20/v4/object/securityadvisoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryedge", - "/enterprise/2.20/v4/object/securityadvisoryidentifier": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryidentifier", - "/en/enterprise/2.20/v4/object/securityadvisoryidentifier": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryidentifier", - "/enterprise/2.20/v4/object/securityadvisorypackage": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisorypackage", - "/en/enterprise/2.20/v4/object/securityadvisorypackage": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisorypackage", - "/enterprise/2.20/v4/object/securityadvisorypackageversion": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisorypackageversion", - "/en/enterprise/2.20/v4/object/securityadvisorypackageversion": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisorypackageversion", - "/enterprise/2.20/v4/object/securityadvisoryreference": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryreference", - "/en/enterprise/2.20/v4/object/securityadvisoryreference": "/en/enterprise-server@2.20/graphql/reference/objects#securityadvisoryreference", - "/enterprise/2.20/v4/object/securityvulnerability": "/en/enterprise-server@2.20/graphql/reference/objects#securityvulnerability", - "/en/enterprise/2.20/v4/object/securityvulnerability": "/en/enterprise-server@2.20/graphql/reference/objects#securityvulnerability", - "/enterprise/2.20/v4/object/securityvulnerabilityconnection": "/en/enterprise-server@2.20/graphql/reference/objects#securityvulnerabilityconnection", - "/en/enterprise/2.20/v4/object/securityvulnerabilityconnection": "/en/enterprise-server@2.20/graphql/reference/objects#securityvulnerabilityconnection", - "/enterprise/2.20/v4/object/securityvulnerabilityedge": "/en/enterprise-server@2.20/graphql/reference/objects#securityvulnerabilityedge", - "/en/enterprise/2.20/v4/object/securityvulnerabilityedge": "/en/enterprise-server@2.20/graphql/reference/objects#securityvulnerabilityedge", - "/enterprise/2.20/v4/object/smimesignature": "/en/enterprise-server@2.20/graphql/reference/objects#smimesignature", - "/en/enterprise/2.20/v4/object/smimesignature": "/en/enterprise-server@2.20/graphql/reference/objects#smimesignature", - "/enterprise/2.20/v4/object/sponsorship": "/en/enterprise-server@2.20/graphql/reference/objects#sponsorship", - "/en/enterprise/2.20/v4/object/sponsorship": "/en/enterprise-server@2.20/graphql/reference/objects#sponsorship", - "/enterprise/2.20/v4/object/sponsorshipconnection": "/en/enterprise-server@2.20/graphql/reference/objects#sponsorshipconnection", - "/en/enterprise/2.20/v4/object/sponsorshipconnection": "/en/enterprise-server@2.20/graphql/reference/objects#sponsorshipconnection", - "/enterprise/2.20/v4/object/sponsorshipedge": "/en/enterprise-server@2.20/graphql/reference/objects#sponsorshipedge", - "/en/enterprise/2.20/v4/object/sponsorshipedge": "/en/enterprise-server@2.20/graphql/reference/objects#sponsorshipedge", - "/enterprise/2.20/v4/object/stargazerconnection": "/en/enterprise-server@2.20/graphql/reference/objects#stargazerconnection", - "/en/enterprise/2.20/v4/object/stargazerconnection": "/en/enterprise-server@2.20/graphql/reference/objects#stargazerconnection", - "/enterprise/2.20/v4/object/stargazeredge": "/en/enterprise-server@2.20/graphql/reference/objects#stargazeredge", - "/en/enterprise/2.20/v4/object/stargazeredge": "/en/enterprise-server@2.20/graphql/reference/objects#stargazeredge", - "/enterprise/2.20/v4/object/starredrepositoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#starredrepositoryconnection", - "/en/enterprise/2.20/v4/object/starredrepositoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#starredrepositoryconnection", - "/enterprise/2.20/v4/object/starredrepositoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#starredrepositoryedge", - "/en/enterprise/2.20/v4/object/starredrepositoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#starredrepositoryedge", - "/enterprise/2.20/v4/object/status": "/en/enterprise-server@2.20/graphql/reference/objects#status", - "/en/enterprise/2.20/v4/object/status": "/en/enterprise-server@2.20/graphql/reference/objects#status", - "/enterprise/2.20/v4/object/statuscontext": "/en/enterprise-server@2.20/graphql/reference/objects#statuscontext", - "/en/enterprise/2.20/v4/object/statuscontext": "/en/enterprise-server@2.20/graphql/reference/objects#statuscontext", - "/enterprise/2.20/v4/object/submitpullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#submitpullrequestreviewpayload", - "/en/enterprise/2.20/v4/object/submitpullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#submitpullrequestreviewpayload", - "/enterprise/2.20/v4/object/subscribedevent": "/en/enterprise-server@2.20/graphql/reference/objects#subscribedevent", - "/en/enterprise/2.20/v4/object/subscribedevent": "/en/enterprise-server@2.20/graphql/reference/objects#subscribedevent", - "/enterprise/2.20/v4/object/suggestedreviewer": "/en/enterprise-server@2.20/graphql/reference/objects#suggestedreviewer", - "/en/enterprise/2.20/v4/object/suggestedreviewer": "/en/enterprise-server@2.20/graphql/reference/objects#suggestedreviewer", - "/enterprise/2.20/v4/object/tag": "/en/enterprise-server@2.20/graphql/reference/objects#tag", - "/en/enterprise/2.20/v4/object/tag": "/en/enterprise-server@2.20/graphql/reference/objects#tag", - "/enterprise/2.20/v4/object/team": "/en/enterprise-server@2.20/graphql/reference/objects#team", - "/en/enterprise/2.20/v4/object/team": "/en/enterprise-server@2.20/graphql/reference/objects#team", - "/enterprise/2.20/v4/object/teamaddmemberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamaddmemberauditentry", - "/en/enterprise/2.20/v4/object/teamaddmemberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamaddmemberauditentry", - "/enterprise/2.20/v4/object/teamaddrepositoryauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamaddrepositoryauditentry", - "/en/enterprise/2.20/v4/object/teamaddrepositoryauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamaddrepositoryauditentry", - "/enterprise/2.20/v4/object/teamchangeparentteamauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamchangeparentteamauditentry", - "/en/enterprise/2.20/v4/object/teamchangeparentteamauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamchangeparentteamauditentry", - "/enterprise/2.20/v4/object/teamconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamconnection", - "/en/enterprise/2.20/v4/object/teamconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamconnection", - "/enterprise/2.20/v4/object/teamdiscussion": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussion", - "/en/enterprise/2.20/v4/object/teamdiscussion": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussion", - "/enterprise/2.20/v4/object/teamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncomment", - "/en/enterprise/2.20/v4/object/teamdiscussioncomment": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncomment", - "/enterprise/2.20/v4/object/teamdiscussioncommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncommentconnection", - "/en/enterprise/2.20/v4/object/teamdiscussioncommentconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncommentconnection", - "/enterprise/2.20/v4/object/teamdiscussioncommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncommentedge", - "/en/enterprise/2.20/v4/object/teamdiscussioncommentedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncommentedge", - "/enterprise/2.20/v4/object/teamdiscussionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussionconnection", - "/en/enterprise/2.20/v4/object/teamdiscussionconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussionconnection", - "/enterprise/2.20/v4/object/teamdiscussionedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussionedge", - "/en/enterprise/2.20/v4/object/teamdiscussionedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamdiscussionedge", - "/enterprise/2.20/v4/object/teamedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamedge", - "/en/enterprise/2.20/v4/object/teamedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamedge", - "/enterprise/2.20/v4/object/teammemberconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teammemberconnection", - "/en/enterprise/2.20/v4/object/teammemberconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teammemberconnection", - "/enterprise/2.20/v4/object/teammemberedge": "/en/enterprise-server@2.20/graphql/reference/objects#teammemberedge", - "/en/enterprise/2.20/v4/object/teammemberedge": "/en/enterprise-server@2.20/graphql/reference/objects#teammemberedge", - "/enterprise/2.20/v4/object/teamremovememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamremovememberauditentry", - "/en/enterprise/2.20/v4/object/teamremovememberauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamremovememberauditentry", - "/enterprise/2.20/v4/object/teamremoverepositoryauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamremoverepositoryauditentry", - "/en/enterprise/2.20/v4/object/teamremoverepositoryauditentry": "/en/enterprise-server@2.20/graphql/reference/objects#teamremoverepositoryauditentry", - "/enterprise/2.20/v4/object/teamrepositoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamrepositoryconnection", - "/en/enterprise/2.20/v4/object/teamrepositoryconnection": "/en/enterprise-server@2.20/graphql/reference/objects#teamrepositoryconnection", - "/enterprise/2.20/v4/object/teamrepositoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamrepositoryedge", - "/en/enterprise/2.20/v4/object/teamrepositoryedge": "/en/enterprise-server@2.20/graphql/reference/objects#teamrepositoryedge", - "/enterprise/2.20/v4/object/textmatch": "/en/enterprise-server@2.20/graphql/reference/objects#textmatch", - "/en/enterprise/2.20/v4/object/textmatch": "/en/enterprise-server@2.20/graphql/reference/objects#textmatch", - "/enterprise/2.20/v4/object/textmatchhighlight": "/en/enterprise-server@2.20/graphql/reference/objects#textmatchhighlight", - "/en/enterprise/2.20/v4/object/textmatchhighlight": "/en/enterprise-server@2.20/graphql/reference/objects#textmatchhighlight", - "/enterprise/2.20/v4/object/topic": "/en/enterprise-server@2.20/graphql/reference/objects#topic", - "/en/enterprise/2.20/v4/object/topic": "/en/enterprise-server@2.20/graphql/reference/objects#topic", - "/enterprise/2.20/v4/object/topicconnection": "/en/enterprise-server@2.20/graphql/reference/objects#topicconnection", - "/en/enterprise/2.20/v4/object/topicconnection": "/en/enterprise-server@2.20/graphql/reference/objects#topicconnection", - "/enterprise/2.20/v4/object/topicedge": "/en/enterprise-server@2.20/graphql/reference/objects#topicedge", - "/en/enterprise/2.20/v4/object/topicedge": "/en/enterprise-server@2.20/graphql/reference/objects#topicedge", - "/enterprise/2.20/v4/object/transferissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#transferissuepayload", - "/en/enterprise/2.20/v4/object/transferissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#transferissuepayload", - "/enterprise/2.20/v4/object/transferredevent": "/en/enterprise-server@2.20/graphql/reference/objects#transferredevent", - "/en/enterprise/2.20/v4/object/transferredevent": "/en/enterprise-server@2.20/graphql/reference/objects#transferredevent", - "/enterprise/2.20/v4/object/tree": "/en/enterprise-server@2.20/graphql/reference/objects#tree", - "/en/enterprise/2.20/v4/object/tree": "/en/enterprise-server@2.20/graphql/reference/objects#tree", - "/enterprise/2.20/v4/object/treeentry": "/en/enterprise-server@2.20/graphql/reference/objects#treeentry", - "/en/enterprise/2.20/v4/object/treeentry": "/en/enterprise-server@2.20/graphql/reference/objects#treeentry", - "/enterprise/2.20/v4/object/unarchiverepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#unarchiverepositorypayload", - "/en/enterprise/2.20/v4/object/unarchiverepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#unarchiverepositorypayload", - "/enterprise/2.20/v4/object/unassignedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unassignedevent", - "/en/enterprise/2.20/v4/object/unassignedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unassignedevent", - "/enterprise/2.20/v4/object/unfollowuserpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unfollowuserpayload", - "/en/enterprise/2.20/v4/object/unfollowuserpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unfollowuserpayload", - "/enterprise/2.20/v4/object/unknownsignature": "/en/enterprise-server@2.20/graphql/reference/objects#unknownsignature", - "/en/enterprise/2.20/v4/object/unknownsignature": "/en/enterprise-server@2.20/graphql/reference/objects#unknownsignature", - "/enterprise/2.20/v4/object/unlabeledevent": "/en/enterprise-server@2.20/graphql/reference/objects#unlabeledevent", - "/en/enterprise/2.20/v4/object/unlabeledevent": "/en/enterprise-server@2.20/graphql/reference/objects#unlabeledevent", - "/enterprise/2.20/v4/object/unlinkrepositoryfromprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unlinkrepositoryfromprojectpayload", - "/en/enterprise/2.20/v4/object/unlinkrepositoryfromprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unlinkrepositoryfromprojectpayload", - "/enterprise/2.20/v4/object/unlockedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unlockedevent", - "/en/enterprise/2.20/v4/object/unlockedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unlockedevent", - "/enterprise/2.20/v4/object/unlocklockablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#unlocklockablepayload", - "/en/enterprise/2.20/v4/object/unlocklockablepayload": "/en/enterprise-server@2.20/graphql/reference/objects#unlocklockablepayload", - "/enterprise/2.20/v4/object/unmarkissueasduplicatepayload": "/en/enterprise-server@2.20/graphql/reference/objects#unmarkissueasduplicatepayload", - "/en/enterprise/2.20/v4/object/unmarkissueasduplicatepayload": "/en/enterprise-server@2.20/graphql/reference/objects#unmarkissueasduplicatepayload", - "/enterprise/2.20/v4/object/unminimizecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unminimizecommentpayload", - "/en/enterprise/2.20/v4/object/unminimizecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unminimizecommentpayload", - "/enterprise/2.20/v4/object/unpinissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#unpinissuepayload", - "/en/enterprise/2.20/v4/object/unpinissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#unpinissuepayload", - "/enterprise/2.20/v4/object/unpinnedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unpinnedevent", - "/en/enterprise/2.20/v4/object/unpinnedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unpinnedevent", - "/enterprise/2.20/v4/object/unresolvereviewthreadpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unresolvereviewthreadpayload", - "/en/enterprise/2.20/v4/object/unresolvereviewthreadpayload": "/en/enterprise-server@2.20/graphql/reference/objects#unresolvereviewthreadpayload", - "/enterprise/2.20/v4/object/unsubscribedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unsubscribedevent", - "/en/enterprise/2.20/v4/object/unsubscribedevent": "/en/enterprise-server@2.20/graphql/reference/objects#unsubscribedevent", - "/enterprise/2.20/v4/object/updatebranchprotectionrulepayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatebranchprotectionrulepayload", - "/en/enterprise/2.20/v4/object/updatebranchprotectionrulepayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatebranchprotectionrulepayload", - "/enterprise/2.20/v4/object/updatecheckrunpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatecheckrunpayload", - "/en/enterprise/2.20/v4/object/updatecheckrunpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatecheckrunpayload", - "/enterprise/2.20/v4/object/updatechecksuitepreferencespayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatechecksuitepreferencespayload", - "/en/enterprise/2.20/v4/object/updatechecksuitepreferencespayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatechecksuitepreferencespayload", - "/enterprise/2.20/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", - "/en/enterprise/2.20/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", - "/enterprise/2.20/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", - "/en/enterprise/2.20/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", - "/enterprise/2.20/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", - "/enterprise/2.20/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", - "/enterprise/2.20/v4/object/updateenterpriseorganizationprojectssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", - "/en/enterprise/2.20/v4/object/updateenterpriseorganizationprojectssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", - "/enterprise/2.20/v4/object/updateenterpriseprofilepayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseprofilepayload", - "/en/enterprise/2.20/v4/object/updateenterpriseprofilepayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseprofilepayload", - "/enterprise/2.20/v4/object/updateenterpriserepositoryprojectssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", - "/en/enterprise/2.20/v4/object/updateenterpriserepositoryprojectssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", - "/enterprise/2.20/v4/object/updateenterpriseteamdiscussionssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", - "/en/enterprise/2.20/v4/object/updateenterpriseteamdiscussionssettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", - "/enterprise/2.20/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", - "/en/enterprise/2.20/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", - "/enterprise/2.20/v4/object/updateissuecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateissuecommentpayload", - "/en/enterprise/2.20/v4/object/updateissuecommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateissuecommentpayload", - "/enterprise/2.20/v4/object/updateissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateissuepayload", - "/en/enterprise/2.20/v4/object/updateissuepayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateissuepayload", - "/enterprise/2.20/v4/object/updatelabelpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatelabelpayload", - "/en/enterprise/2.20/v4/object/updatelabelpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatelabelpayload", - "/enterprise/2.20/v4/object/updateprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateprojectcardpayload", - "/en/enterprise/2.20/v4/object/updateprojectcardpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateprojectcardpayload", - "/enterprise/2.20/v4/object/updateprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateprojectcolumnpayload", - "/en/enterprise/2.20/v4/object/updateprojectcolumnpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateprojectcolumnpayload", - "/enterprise/2.20/v4/object/updateprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateprojectpayload", - "/en/enterprise/2.20/v4/object/updateprojectpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateprojectpayload", - "/enterprise/2.20/v4/object/updatepullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatepullrequestpayload", - "/en/enterprise/2.20/v4/object/updatepullrequestpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatepullrequestpayload", - "/enterprise/2.20/v4/object/updatepullrequestreviewcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatepullrequestreviewcommentpayload", - "/en/enterprise/2.20/v4/object/updatepullrequestreviewcommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatepullrequestreviewcommentpayload", - "/enterprise/2.20/v4/object/updatepullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatepullrequestreviewpayload", - "/en/enterprise/2.20/v4/object/updatepullrequestreviewpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatepullrequestreviewpayload", - "/enterprise/2.20/v4/object/updaterefpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updaterefpayload", - "/en/enterprise/2.20/v4/object/updaterefpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updaterefpayload", - "/enterprise/2.20/v4/object/updaterefspayload": "/en/enterprise-server@2.20/graphql/reference/objects#updaterefspayload", - "/en/enterprise/2.20/v4/object/updaterefspayload": "/en/enterprise-server@2.20/graphql/reference/objects#updaterefspayload", - "/enterprise/2.20/v4/object/updaterepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#updaterepositorypayload", - "/en/enterprise/2.20/v4/object/updaterepositorypayload": "/en/enterprise-server@2.20/graphql/reference/objects#updaterepositorypayload", - "/enterprise/2.20/v4/object/updatesubscriptionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatesubscriptionpayload", - "/en/enterprise/2.20/v4/object/updatesubscriptionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatesubscriptionpayload", - "/enterprise/2.20/v4/object/updateteamdiscussioncommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateteamdiscussioncommentpayload", - "/en/enterprise/2.20/v4/object/updateteamdiscussioncommentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateteamdiscussioncommentpayload", - "/enterprise/2.20/v4/object/updateteamdiscussionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateteamdiscussionpayload", - "/en/enterprise/2.20/v4/object/updateteamdiscussionpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateteamdiscussionpayload", - "/enterprise/2.20/v4/object/updateteamreviewassignmentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateteamreviewassignmentpayload", - "/en/enterprise/2.20/v4/object/updateteamreviewassignmentpayload": "/en/enterprise-server@2.20/graphql/reference/objects#updateteamreviewassignmentpayload", - "/enterprise/2.20/v4/object/updatetopicspayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatetopicspayload", - "/en/enterprise/2.20/v4/object/updatetopicspayload": "/en/enterprise-server@2.20/graphql/reference/objects#updatetopicspayload", - "/enterprise/2.20/v4/object/user": "/en/enterprise-server@2.20/graphql/reference/objects#user", - "/en/enterprise/2.20/v4/object/user": "/en/enterprise-server@2.20/graphql/reference/objects#user", - "/enterprise/2.20/v4/object/userblockedevent": "/en/enterprise-server@2.20/graphql/reference/objects#userblockedevent", - "/en/enterprise/2.20/v4/object/userblockedevent": "/en/enterprise-server@2.20/graphql/reference/objects#userblockedevent", - "/enterprise/2.20/v4/object/userconnection": "/en/enterprise-server@2.20/graphql/reference/objects#userconnection", - "/en/enterprise/2.20/v4/object/userconnection": "/en/enterprise-server@2.20/graphql/reference/objects#userconnection", - "/enterprise/2.20/v4/object/usercontentedit": "/en/enterprise-server@2.20/graphql/reference/objects#usercontentedit", - "/en/enterprise/2.20/v4/object/usercontentedit": "/en/enterprise-server@2.20/graphql/reference/objects#usercontentedit", - "/enterprise/2.20/v4/object/usercontenteditconnection": "/en/enterprise-server@2.20/graphql/reference/objects#usercontenteditconnection", - "/en/enterprise/2.20/v4/object/usercontenteditconnection": "/en/enterprise-server@2.20/graphql/reference/objects#usercontenteditconnection", - "/enterprise/2.20/v4/object/usercontenteditedge": "/en/enterprise-server@2.20/graphql/reference/objects#usercontenteditedge", - "/en/enterprise/2.20/v4/object/usercontenteditedge": "/en/enterprise-server@2.20/graphql/reference/objects#usercontenteditedge", - "/enterprise/2.20/v4/object/useredge": "/en/enterprise-server@2.20/graphql/reference/objects#useredge", - "/en/enterprise/2.20/v4/object/useredge": "/en/enterprise-server@2.20/graphql/reference/objects#useredge", - "/enterprise/2.20/v4/object/userstatus": "/en/enterprise-server@2.20/graphql/reference/objects#userstatus", - "/en/enterprise/2.20/v4/object/userstatus": "/en/enterprise-server@2.20/graphql/reference/objects#userstatus", - "/enterprise/2.20/v4/object/userstatusconnection": "/en/enterprise-server@2.20/graphql/reference/objects#userstatusconnection", - "/en/enterprise/2.20/v4/object/userstatusconnection": "/en/enterprise-server@2.20/graphql/reference/objects#userstatusconnection", - "/enterprise/2.20/v4/object/userstatusedge": "/en/enterprise-server@2.20/graphql/reference/objects#userstatusedge", - "/en/enterprise/2.20/v4/object/userstatusedge": "/en/enterprise-server@2.20/graphql/reference/objects#userstatusedge", - "/enterprise/2.20/v4/object/viewerhovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#viewerhovercardcontext", - "/en/enterprise/2.20/v4/object/viewerhovercardcontext": "/en/enterprise-server@2.20/graphql/reference/objects#viewerhovercardcontext", - "/enterprise/2.20/v4/scalar/boolean": "/en/enterprise-server@2.20/graphql/reference/scalars#boolean", - "/en/enterprise/2.20/v4/scalar/boolean": "/en/enterprise-server@2.20/graphql/reference/scalars#boolean", - "/enterprise/2.20/v4/scalar/date": "/en/enterprise-server@2.20/graphql/reference/scalars#date", - "/en/enterprise/2.20/v4/scalar/date": "/en/enterprise-server@2.20/graphql/reference/scalars#date", - "/enterprise/2.20/v4/scalar/datetime": "/en/enterprise-server@2.20/graphql/reference/scalars#datetime", - "/en/enterprise/2.20/v4/scalar/datetime": "/en/enterprise-server@2.20/graphql/reference/scalars#datetime", - "/enterprise/2.20/v4/scalar/float": "/en/enterprise-server@2.20/graphql/reference/scalars#float", - "/en/enterprise/2.20/v4/scalar/float": "/en/enterprise-server@2.20/graphql/reference/scalars#float", - "/enterprise/2.20/v4/scalar/gitobjectid": "/en/enterprise-server@2.20/graphql/reference/scalars#gitobjectid", - "/en/enterprise/2.20/v4/scalar/gitobjectid": "/en/enterprise-server@2.20/graphql/reference/scalars#gitobjectid", - "/enterprise/2.20/v4/scalar/gitrefname": "/en/enterprise-server@2.20/graphql/reference/scalars#gitrefname", - "/en/enterprise/2.20/v4/scalar/gitrefname": "/en/enterprise-server@2.20/graphql/reference/scalars#gitrefname", - "/enterprise/2.20/v4/scalar/gitsshremote": "/en/enterprise-server@2.20/graphql/reference/scalars#gitsshremote", - "/en/enterprise/2.20/v4/scalar/gitsshremote": "/en/enterprise-server@2.20/graphql/reference/scalars#gitsshremote", - "/enterprise/2.20/v4/scalar/gittimestamp": "/en/enterprise-server@2.20/graphql/reference/scalars#gittimestamp", - "/en/enterprise/2.20/v4/scalar/gittimestamp": "/en/enterprise-server@2.20/graphql/reference/scalars#gittimestamp", - "/enterprise/2.20/v4/scalar/html": "/en/enterprise-server@2.20/graphql/reference/scalars#html", - "/en/enterprise/2.20/v4/scalar/html": "/en/enterprise-server@2.20/graphql/reference/scalars#html", - "/enterprise/2.20/v4/scalar/id": "/en/enterprise-server@2.20/graphql/reference/scalars#id", - "/en/enterprise/2.20/v4/scalar/id": "/en/enterprise-server@2.20/graphql/reference/scalars#id", - "/enterprise/2.20/v4/scalar/int": "/en/enterprise-server@2.20/graphql/reference/scalars#int", - "/en/enterprise/2.20/v4/scalar/int": "/en/enterprise-server@2.20/graphql/reference/scalars#int", - "/enterprise/2.20/v4/scalar/precisedatetime": "/en/enterprise-server@2.20/graphql/reference/scalars#precisedatetime", - "/en/enterprise/2.20/v4/scalar/precisedatetime": "/en/enterprise-server@2.20/graphql/reference/scalars#precisedatetime", - "/enterprise/2.20/v4/scalar/string": "/en/enterprise-server@2.20/graphql/reference/scalars#string", - "/en/enterprise/2.20/v4/scalar/string": "/en/enterprise-server@2.20/graphql/reference/scalars#string", - "/enterprise/2.20/v4/scalar/uri": "/en/enterprise-server@2.20/graphql/reference/scalars#uri", - "/en/enterprise/2.20/v4/scalar/uri": "/en/enterprise-server@2.20/graphql/reference/scalars#uri", - "/enterprise/2.20/v4/scalar/x509certificate": "/en/enterprise-server@2.20/graphql/reference/scalars#x509certificate", - "/en/enterprise/2.20/v4/scalar/x509certificate": "/en/enterprise-server@2.20/graphql/reference/scalars#x509certificate", - "/enterprise/2.20/v4/union/assignee": "/en/enterprise-server@2.20/graphql/reference/unions#assignee", - "/en/enterprise/2.20/v4/union/assignee": "/en/enterprise-server@2.20/graphql/reference/unions#assignee", - "/enterprise/2.20/v4/union/auditentryactor": "/en/enterprise-server@2.20/graphql/reference/unions#auditentryactor", - "/en/enterprise/2.20/v4/union/auditentryactor": "/en/enterprise-server@2.20/graphql/reference/unions#auditentryactor", - "/enterprise/2.20/v4/union/closer": "/en/enterprise-server@2.20/graphql/reference/unions#closer", - "/en/enterprise/2.20/v4/union/closer": "/en/enterprise-server@2.20/graphql/reference/unions#closer", - "/enterprise/2.20/v4/union/createdissueorrestrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/unions#createdissueorrestrictedcontribution", - "/en/enterprise/2.20/v4/union/createdissueorrestrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/unions#createdissueorrestrictedcontribution", - "/enterprise/2.20/v4/union/createdpullrequestorrestrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/unions#createdpullrequestorrestrictedcontribution", - "/en/enterprise/2.20/v4/union/createdpullrequestorrestrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/unions#createdpullrequestorrestrictedcontribution", - "/enterprise/2.20/v4/union/createdrepositoryorrestrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/unions#createdrepositoryorrestrictedcontribution", - "/en/enterprise/2.20/v4/union/createdrepositoryorrestrictedcontribution": "/en/enterprise-server@2.20/graphql/reference/unions#createdrepositoryorrestrictedcontribution", - "/enterprise/2.20/v4/union/enterprisemember": "/en/enterprise-server@2.20/graphql/reference/unions#enterprisemember", - "/en/enterprise/2.20/v4/union/enterprisemember": "/en/enterprise-server@2.20/graphql/reference/unions#enterprisemember", - "/enterprise/2.20/v4/union/issueorpullrequest": "/en/enterprise-server@2.20/graphql/reference/unions#issueorpullrequest", - "/en/enterprise/2.20/v4/union/issueorpullrequest": "/en/enterprise-server@2.20/graphql/reference/unions#issueorpullrequest", - "/enterprise/2.20/v4/union/issuetimelineitem": "/en/enterprise-server@2.20/graphql/reference/unions#issuetimelineitem", - "/en/enterprise/2.20/v4/union/issuetimelineitem": "/en/enterprise-server@2.20/graphql/reference/unions#issuetimelineitem", - "/enterprise/2.20/v4/union/issuetimelineitems": "/en/enterprise-server@2.20/graphql/reference/unions#issuetimelineitems", - "/en/enterprise/2.20/v4/union/issuetimelineitems": "/en/enterprise-server@2.20/graphql/reference/unions#issuetimelineitems", - "/enterprise/2.20/v4/union/milestoneitem": "/en/enterprise-server@2.20/graphql/reference/unions#milestoneitem", - "/en/enterprise/2.20/v4/union/milestoneitem": "/en/enterprise-server@2.20/graphql/reference/unions#milestoneitem", - "/enterprise/2.20/v4/union/organizationauditentry": "/en/enterprise-server@2.20/graphql/reference/unions#organizationauditentry", - "/en/enterprise/2.20/v4/union/organizationauditentry": "/en/enterprise-server@2.20/graphql/reference/unions#organizationauditentry", - "/enterprise/2.20/v4/union/orgrestorememberauditentrymembership": "/en/enterprise-server@2.20/graphql/reference/unions#orgrestorememberauditentrymembership", - "/en/enterprise/2.20/v4/union/orgrestorememberauditentrymembership": "/en/enterprise-server@2.20/graphql/reference/unions#orgrestorememberauditentrymembership", - "/enterprise/2.20/v4/union/permissiongranter": "/en/enterprise-server@2.20/graphql/reference/unions#permissiongranter", - "/en/enterprise/2.20/v4/union/permissiongranter": "/en/enterprise-server@2.20/graphql/reference/unions#permissiongranter", - "/enterprise/2.20/v4/union/pinnableitem": "/en/enterprise-server@2.20/graphql/reference/unions#pinnableitem", - "/en/enterprise/2.20/v4/union/pinnableitem": "/en/enterprise-server@2.20/graphql/reference/unions#pinnableitem", - "/enterprise/2.20/v4/union/projectcarditem": "/en/enterprise-server@2.20/graphql/reference/unions#projectcarditem", - "/en/enterprise/2.20/v4/union/projectcarditem": "/en/enterprise-server@2.20/graphql/reference/unions#projectcarditem", - "/enterprise/2.20/v4/union/pullrequesttimelineitem": "/en/enterprise-server@2.20/graphql/reference/unions#pullrequesttimelineitem", - "/en/enterprise/2.20/v4/union/pullrequesttimelineitem": "/en/enterprise-server@2.20/graphql/reference/unions#pullrequesttimelineitem", - "/enterprise/2.20/v4/union/pullrequesttimelineitems": "/en/enterprise-server@2.20/graphql/reference/unions#pullrequesttimelineitems", - "/en/enterprise/2.20/v4/union/pullrequesttimelineitems": "/en/enterprise-server@2.20/graphql/reference/unions#pullrequesttimelineitems", - "/enterprise/2.20/v4/union/pushallowanceactor": "/en/enterprise-server@2.20/graphql/reference/unions#pushallowanceactor", - "/en/enterprise/2.20/v4/union/pushallowanceactor": "/en/enterprise-server@2.20/graphql/reference/unions#pushallowanceactor", - "/enterprise/2.20/v4/union/referencedsubject": "/en/enterprise-server@2.20/graphql/reference/unions#referencedsubject", - "/en/enterprise/2.20/v4/union/referencedsubject": "/en/enterprise-server@2.20/graphql/reference/unions#referencedsubject", - "/enterprise/2.20/v4/union/renamedtitlesubject": "/en/enterprise-server@2.20/graphql/reference/unions#renamedtitlesubject", - "/en/enterprise/2.20/v4/union/renamedtitlesubject": "/en/enterprise-server@2.20/graphql/reference/unions#renamedtitlesubject", - "/enterprise/2.20/v4/union/requestedreviewer": "/en/enterprise-server@2.20/graphql/reference/unions#requestedreviewer", - "/en/enterprise/2.20/v4/union/requestedreviewer": "/en/enterprise-server@2.20/graphql/reference/unions#requestedreviewer", - "/enterprise/2.20/v4/union/reviewdismissalallowanceactor": "/en/enterprise-server@2.20/graphql/reference/unions#reviewdismissalallowanceactor", - "/en/enterprise/2.20/v4/union/reviewdismissalallowanceactor": "/en/enterprise-server@2.20/graphql/reference/unions#reviewdismissalallowanceactor", - "/enterprise/2.20/v4/union/searchresultitem": "/en/enterprise-server@2.20/graphql/reference/unions#searchresultitem", - "/en/enterprise/2.20/v4/union/searchresultitem": "/en/enterprise-server@2.20/graphql/reference/unions#searchresultitem", - "/enterprise/v3/activity/events": "/en/enterprise-server@latest/rest/reference/activity#events", - "/en/enterprise/v3/activity/events": "/en/enterprise-server@latest/rest/reference/activity#events", - "/enterprise/v3/activity/feeds": "/en/enterprise-server@latest/rest/reference/activity#feeds", - "/en/enterprise/v3/activity/feeds": "/en/enterprise-server@latest/rest/reference/activity#feeds", - "/enterprise/v3/activity/notifications": "/en/enterprise-server@latest/rest/reference/activity#notifications", - "/en/enterprise/v3/activity/notifications": "/en/enterprise-server@latest/rest/reference/activity#notifications", - "/enterprise/v3/activity/starring": "/en/enterprise-server@latest/rest/reference/activity#starring", - "/en/enterprise/v3/activity/starring": "/en/enterprise-server@latest/rest/reference/activity#starring", - "/enterprise/v3/activity/watching": "/en/enterprise-server@latest/rest/reference/activity#watching", - "/en/enterprise/v3/activity/watching": "/en/enterprise-server@latest/rest/reference/activity#watching", - "/enterprise/v3/apps/installations": "/en/enterprise-server@latest/rest/reference/apps#installations", - "/en/enterprise/v3/apps/installations": "/en/enterprise-server@latest/rest/reference/apps#installations", - "/enterprise/v3/apps/oauth_applications": "/en/enterprise-server@latest/rest/reference/apps#oauth-applications", - "/en/enterprise/v3/apps/oauth_applications": "/en/enterprise-server@latest/rest/reference/apps#oauth-applications", - "/enterprise/v3/checks/runs": "/en/enterprise-server@latest/rest/reference/checks#runs", - "/en/enterprise/v3/checks/runs": "/en/enterprise-server@latest/rest/reference/checks#runs", - "/enterprise/v3/checks/suites": "/en/enterprise-server@latest/rest/reference/checks#suites", - "/en/enterprise/v3/checks/suites": "/en/enterprise-server@latest/rest/reference/checks#suites", - "/enterprise/v3/enterprise-admin/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/en/enterprise/v3/enterprise-admin/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/enterprise/v3/enterprise-admin/global_webhooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", - "/en/enterprise/v3/enterprise-admin/global_webhooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", - "/enterprise/v3/enterprise-admin/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/en/enterprise/v3/enterprise-admin/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/enterprise/v3/enterprise-admin/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/en/enterprise/v3/enterprise-admin/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/enterprise/v3/enterprise-admin/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/en/enterprise/v3/enterprise-admin/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/enterprise/v3/enterprise-admin/org_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/en/enterprise/v3/enterprise-admin/org_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/enterprise/v3/enterprise-admin/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/en/enterprise/v3/enterprise-admin/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/enterprise/v3/enterprise-admin/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/en/enterprise/v3/enterprise-admin/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/enterprise/v3/enterprise-admin/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/en/enterprise/v3/enterprise-admin/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/enterprise/v3/enterprise-admin/repo_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/en/enterprise/v3/enterprise-admin/repo_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/enterprise/v3/enterprise-admin/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/en/enterprise/v3/enterprise-admin/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/enterprise/v3/enterprise-admin/users": "/en/enterprise-server@latest/rest/reference/enterprise-admin#users", - "/en/enterprise/v3/enterprise-admin/users": "/en/enterprise-server@latest/rest/reference/enterprise-admin#users", - "/enterprise/v3/enterprise/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/en/enterprise/v3/enterprise/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/enterprise/v3/enterprise/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/en/enterprise/v3/enterprise/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/enterprise/v3/enterprise/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/en/enterprise/v3/enterprise/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/enterprise/v3/enterprise/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/en/enterprise/v3/enterprise/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/enterprise/v3/enterprise/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/en/enterprise/v3/enterprise/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/enterprise/v3/enterprise/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/en/enterprise/v3/enterprise/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/enterprise/v3/enterprise/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/en/enterprise/v3/enterprise/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/enterprise/v3/enterprise/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/en/enterprise/v3/enterprise/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/enterprise/v3/gists/comments": "/en/enterprise-server@latest/rest/reference/gists#comments", - "/en/enterprise/v3/gists/comments": "/en/enterprise-server@latest/rest/reference/gists#comments", - "/enterprise/v3/git/blobs": "/en/enterprise-server@latest/rest/reference/git#blobs", - "/en/enterprise/v3/git/blobs": "/en/enterprise-server@latest/rest/reference/git#blobs", - "/enterprise/v3/git/commits": "/en/enterprise-server@latest/rest/reference/git#commits", - "/en/enterprise/v3/git/commits": "/en/enterprise-server@latest/rest/reference/git#commits", - "/enterprise/v3/git/refs": "/en/enterprise-server@latest/rest/reference/git#refs", - "/en/enterprise/v3/git/refs": "/en/enterprise-server@latest/rest/reference/git#refs", - "/enterprise/v3/git/tags": "/en/enterprise-server@latest/rest/reference/git#tags", - "/en/enterprise/v3/git/tags": "/en/enterprise-server@latest/rest/reference/git#tags", - "/enterprise/v3/git/trees": "/en/enterprise-server@latest/rest/reference/git#trees", - "/en/enterprise/v3/git/trees": "/en/enterprise-server@latest/rest/reference/git#trees", - "/enterprise/v3/integrations/installations": "/en/enterprise-server@latest/developers/apps#installations", - "/en/enterprise/v3/integrations/installations": "/en/enterprise-server@latest/developers/apps#installations", - "/enterprise/v3/issues/assignees": "/en/enterprise-server@latest/rest/reference/issues#assignees", - "/en/enterprise/v3/issues/assignees": "/en/enterprise-server@latest/rest/reference/issues#assignees", - "/enterprise/v3/issues/comments": "/en/enterprise-server@latest/rest/reference/issues#comments", - "/en/enterprise/v3/issues/comments": "/en/enterprise-server@latest/rest/reference/issues#comments", - "/enterprise/v3/issues/events": "/en/enterprise-server@latest/rest/reference/issues#events", - "/en/enterprise/v3/issues/events": "/en/enterprise-server@latest/rest/reference/issues#events", - "/enterprise/v3/issues/labels": "/en/enterprise-server@latest/rest/reference/issues#labels", - "/en/enterprise/v3/issues/labels": "/en/enterprise-server@latest/rest/reference/issues#labels", - "/enterprise/v3/issues/milestones": "/en/enterprise-server@latest/rest/reference/issues#milestones", - "/en/enterprise/v3/issues/milestones": "/en/enterprise-server@latest/rest/reference/issues#milestones", - "/enterprise/v3/issues/timeline": "/en/enterprise-server@latest/rest/reference/issues#timeline", - "/en/enterprise/v3/issues/timeline": "/en/enterprise-server@latest/rest/reference/issues#timeline", - "/enterprise/v3/orgs/hooks": "/en/enterprise-server@latest/rest/reference/orgs#webhooks", - "/en/enterprise/v3/orgs/hooks": "/en/enterprise-server@latest/rest/reference/orgs#webhooks", - "/enterprise/v3/orgs/members": "/en/enterprise-server@latest/rest/reference/orgs#members", - "/en/enterprise/v3/orgs/members": "/en/enterprise-server@latest/rest/reference/orgs#members", - "/enterprise/v3/orgs/outside_collaborators": "/en/enterprise-server@latest/rest/reference/orgs#outside-collaborators", - "/en/enterprise/v3/orgs/outside_collaborators": "/en/enterprise-server@latest/rest/reference/orgs#outside-collaborators", - "/enterprise/v3/orgs/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/en/enterprise/v3/orgs/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/enterprise/v3/orgs/teams": "/en/enterprise-server@latest/rest/reference/orgs#teams", - "/en/enterprise/v3/orgs/teams": "/en/enterprise-server@latest/rest/reference/orgs#teams", - "/enterprise/v3/projects/cards": "/en/enterprise-server@latest/rest/reference/projects#cards", - "/en/enterprise/v3/projects/cards": "/en/enterprise-server@latest/rest/reference/projects#cards", - "/enterprise/v3/projects/collaborators": "/en/enterprise-server@latest/rest/reference/projects#collaborators", - "/en/enterprise/v3/projects/collaborators": "/en/enterprise-server@latest/rest/reference/projects#collaborators", - "/enterprise/v3/projects/columns": "/en/enterprise-server@latest/rest/reference/projects#columns", - "/en/enterprise/v3/projects/columns": "/en/enterprise-server@latest/rest/reference/projects#columns", - "/enterprise/v3/pulls/comments": "/en/enterprise-server@latest/rest/reference/pulls#comments", - "/en/enterprise/v3/pulls/comments": "/en/enterprise-server@latest/rest/reference/pulls#comments", - "/enterprise/v3/pulls/review_requests": "/en/enterprise-server@latest/rest/reference/pulls#review-requests", - "/en/enterprise/v3/pulls/review_requests": "/en/enterprise-server@latest/rest/reference/pulls#review-requests", - "/enterprise/v3/pulls/reviews": "/en/enterprise-server@latest/rest/reference/pulls#reviews", - "/en/enterprise/v3/pulls/reviews": "/en/enterprise-server@latest/rest/reference/pulls#reviews", - "/enterprise/v3/repos/branches": "/en/enterprise-server@latest/rest/reference/repos#branches", - "/en/enterprise/v3/repos/branches": "/en/enterprise-server@latest/rest/reference/repos#branches", - "/enterprise/v3/repos/collaborators": "/en/enterprise-server@latest/rest/reference/repos#collaborators", - "/en/enterprise/v3/repos/collaborators": "/en/enterprise-server@latest/rest/reference/repos#collaborators", - "/enterprise/v3/repos/comments": "/en/enterprise-server@latest/rest/reference/repos#comments", - "/en/enterprise/v3/repos/comments": "/en/enterprise-server@latest/rest/reference/repos#comments", - "/enterprise/v3/repos/commits": "/en/enterprise-server@latest/rest/reference/repos#commits", - "/en/enterprise/v3/repos/commits": "/en/enterprise-server@latest/rest/reference/repos#commits", - "/enterprise/v3/repos/contents": "/en/enterprise-server@latest/rest/reference/repos#contents", - "/en/enterprise/v3/repos/contents": "/en/enterprise-server@latest/rest/reference/repos#contents", - "/enterprise/v3/repos/deployments": "/en/enterprise-server@latest/rest/reference/repos#deployments", - "/en/enterprise/v3/repos/deployments": "/en/enterprise-server@latest/rest/reference/repos#deployments", - "/enterprise/v3/repos/downloads": "/en/enterprise-server@latest/rest/reference/repos#downloads", - "/en/enterprise/v3/repos/downloads": "/en/enterprise-server@latest/rest/reference/repos#downloads", - "/enterprise/v3/repos/forks": "/en/enterprise-server@latest/rest/reference/repos#forks", - "/en/enterprise/v3/repos/forks": "/en/enterprise-server@latest/rest/reference/repos#forks", - "/enterprise/v3/repos/hooks": "/en/enterprise-server@latest/rest/reference/repos#webhooks", - "/en/enterprise/v3/repos/hooks": "/en/enterprise-server@latest/rest/reference/repos#webhooks", - "/enterprise/v3/repos/invitations": "/en/enterprise-server@latest/rest/reference/repos#invitations", - "/en/enterprise/v3/repos/invitations": "/en/enterprise-server@latest/rest/reference/repos#invitations", - "/enterprise/v3/repos/keys": "/en/enterprise-server@latest/rest/reference/repos#keys", - "/en/enterprise/v3/repos/keys": "/en/enterprise-server@latest/rest/reference/repos#keys", - "/enterprise/v3/repos/merging": "/en/enterprise-server@latest/rest/reference/repos#merging", - "/en/enterprise/v3/repos/merging": "/en/enterprise-server@latest/rest/reference/repos#merging", - "/enterprise/v3/repos/pages": "/en/enterprise-server@latest/rest/reference/repos#pages", - "/en/enterprise/v3/repos/pages": "/en/enterprise-server@latest/rest/reference/repos#pages", - "/enterprise/v3/repos/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/en/enterprise/v3/repos/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/enterprise/v3/repos/releases": "/en/enterprise-server@latest/rest/reference/repos#releases", - "/en/enterprise/v3/repos/releases": "/en/enterprise-server@latest/rest/reference/repos#releases", - "/enterprise/v3/repos/statistics": "/en/enterprise-server@latest/rest/reference/repos#statistics", - "/en/enterprise/v3/repos/statistics": "/en/enterprise-server@latest/rest/reference/repos#statistics", - "/enterprise/v3/repos/statuses": "/en/enterprise-server@latest/rest/reference/repos#statuses", - "/en/enterprise/v3/repos/statuses": "/en/enterprise-server@latest/rest/reference/repos#statuses", - "/enterprise/v3/teams/discussion_comments": "/en/enterprise-server@latest/rest/reference/teams#discussion-comments", - "/en/enterprise/v3/teams/discussion_comments": "/en/enterprise-server@latest/rest/reference/teams#discussion-comments", - "/enterprise/v3/teams/discussions": "/en/enterprise-server@latest/rest/reference/teams#discussions", - "/en/enterprise/v3/teams/discussions": "/en/enterprise-server@latest/rest/reference/teams#discussions", - "/enterprise/v3/teams/members": "/en/enterprise-server@latest/rest/reference/teams#members", - "/en/enterprise/v3/teams/members": "/en/enterprise-server@latest/rest/reference/teams#members", - "/enterprise/v3/users/administration": "/en/enterprise-server@latest/rest/reference/users#administration", - "/en/enterprise/v3/users/administration": "/en/enterprise-server@latest/rest/reference/users#administration", - "/enterprise/v3/users/emails": "/en/enterprise-server@latest/rest/reference/users#emails", - "/en/enterprise/v3/users/emails": "/en/enterprise-server@latest/rest/reference/users#emails", - "/enterprise/v3/users/followers": "/en/enterprise-server@latest/rest/reference/users#followers", - "/en/enterprise/v3/users/followers": "/en/enterprise-server@latest/rest/reference/users#followers", - "/enterprise/v3/users/gpg_keys": "/en/enterprise-server@latest/rest/reference/users#gpg-keys", - "/en/enterprise/v3/users/gpg_keys": "/en/enterprise-server@latest/rest/reference/users#gpg-keys", - "/enterprise/v3/users/keys": "/en/enterprise-server@latest/rest/reference/users#keys", - "/en/enterprise/v3/users/keys": "/en/enterprise-server@latest/rest/reference/users#keys", - "/enterprise/v4/enum/__directivelocation": "/en/enterprise-server@latest/graphql/reference/enums#__directivelocation", - "/en/enterprise/v4/enum/__directivelocation": "/en/enterprise-server@latest/graphql/reference/enums#__directivelocation", - "/enterprise/v4/enum/__typekind": "/en/enterprise-server@latest/graphql/reference/enums#__typekind", - "/en/enterprise/v4/enum/__typekind": "/en/enterprise-server@latest/graphql/reference/enums#__typekind", - "/enterprise/v4/enum/actionexecutioncapabilitysetting": "/en/enterprise-server@latest/graphql/reference/enums#actionexecutioncapabilitysetting", - "/en/enterprise/v4/enum/actionexecutioncapabilitysetting": "/en/enterprise-server@latest/graphql/reference/enums#actionexecutioncapabilitysetting", - "/enterprise/v4/enum/auditlogorderfield": "/en/enterprise-server@latest/graphql/reference/enums#auditlogorderfield", - "/en/enterprise/v4/enum/auditlogorderfield": "/en/enterprise-server@latest/graphql/reference/enums#auditlogorderfield", - "/enterprise/v4/enum/checkannotationlevel": "/en/enterprise-server@latest/graphql/reference/enums#checkannotationlevel", - "/en/enterprise/v4/enum/checkannotationlevel": "/en/enterprise-server@latest/graphql/reference/enums#checkannotationlevel", - "/enterprise/v4/enum/checkconclusionstate": "/en/enterprise-server@latest/graphql/reference/enums#checkconclusionstate", - "/en/enterprise/v4/enum/checkconclusionstate": "/en/enterprise-server@latest/graphql/reference/enums#checkconclusionstate", - "/enterprise/v4/enum/checkruntype": "/en/enterprise-server@latest/graphql/reference/enums#checkruntype", - "/en/enterprise/v4/enum/checkruntype": "/en/enterprise-server@latest/graphql/reference/enums#checkruntype", - "/enterprise/v4/enum/checkstatusstate": "/en/enterprise-server@latest/graphql/reference/enums#checkstatusstate", - "/en/enterprise/v4/enum/checkstatusstate": "/en/enterprise-server@latest/graphql/reference/enums#checkstatusstate", - "/enterprise/v4/enum/collaboratoraffiliation": "/en/enterprise-server@latest/graphql/reference/enums#collaboratoraffiliation", - "/en/enterprise/v4/enum/collaboratoraffiliation": "/en/enterprise-server@latest/graphql/reference/enums#collaboratoraffiliation", - "/enterprise/v4/enum/commentauthorassociation": "/en/enterprise-server@latest/graphql/reference/enums#commentauthorassociation", - "/en/enterprise/v4/enum/commentauthorassociation": "/en/enterprise-server@latest/graphql/reference/enums#commentauthorassociation", - "/enterprise/v4/enum/commentcannotupdatereason": "/en/enterprise-server@latest/graphql/reference/enums#commentcannotupdatereason", - "/en/enterprise/v4/enum/commentcannotupdatereason": "/en/enterprise-server@latest/graphql/reference/enums#commentcannotupdatereason", - "/enterprise/v4/enum/commitcontributionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#commitcontributionorderfield", - "/en/enterprise/v4/enum/commitcontributionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#commitcontributionorderfield", - "/enterprise/v4/enum/contributionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#contributionorderfield", - "/en/enterprise/v4/enum/contributionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#contributionorderfield", - "/enterprise/v4/enum/defaultrepositorypermissionfield": "/en/enterprise-server@latest/graphql/reference/enums#defaultrepositorypermissionfield", - "/en/enterprise/v4/enum/defaultrepositorypermissionfield": "/en/enterprise-server@latest/graphql/reference/enums#defaultrepositorypermissionfield", - "/enterprise/v4/enum/deploymentorderfield": "/en/enterprise-server@latest/graphql/reference/enums#deploymentorderfield", - "/en/enterprise/v4/enum/deploymentorderfield": "/en/enterprise-server@latest/graphql/reference/enums#deploymentorderfield", - "/enterprise/v4/enum/deploymentstate": "/en/enterprise-server@latest/graphql/reference/enums#deploymentstate", - "/en/enterprise/v4/enum/deploymentstate": "/en/enterprise-server@latest/graphql/reference/enums#deploymentstate", - "/enterprise/v4/enum/deploymentstatusstate": "/en/enterprise-server@latest/graphql/reference/enums#deploymentstatusstate", - "/en/enterprise/v4/enum/deploymentstatusstate": "/en/enterprise-server@latest/graphql/reference/enums#deploymentstatusstate", - "/enterprise/v4/enum/diffside": "/en/enterprise-server@latest/graphql/reference/enums#diffside", - "/en/enterprise/v4/enum/diffside": "/en/enterprise-server@latest/graphql/reference/enums#diffside", - "/enterprise/v4/enum/enterpriseadministratorinvitationorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseadministratorinvitationorderfield", - "/en/enterprise/v4/enum/enterpriseadministratorinvitationorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseadministratorinvitationorderfield", - "/enterprise/v4/enum/enterpriseadministratorrole": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseadministratorrole", - "/en/enterprise/v4/enum/enterpriseadministratorrole": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseadministratorrole", - "/enterprise/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", - "/en/enterprise/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", - "/enterprise/v4/enum/enterpriseenableddisabledsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseenableddisabledsettingvalue", - "/en/enterprise/v4/enum/enterpriseenableddisabledsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseenableddisabledsettingvalue", - "/enterprise/v4/enum/enterpriseenabledsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseenabledsettingvalue", - "/en/enterprise/v4/enum/enterpriseenabledsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseenabledsettingvalue", - "/enterprise/v4/enum/enterprisememberorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterprisememberorderfield", - "/en/enterprise/v4/enum/enterprisememberorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterprisememberorderfield", - "/enterprise/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", - "/en/enterprise/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", - "/enterprise/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", - "/en/enterprise/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", - "/enterprise/v4/enum/enterpriseserveruseraccountemailorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", - "/en/enterprise/v4/enum/enterpriseserveruseraccountemailorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", - "/enterprise/v4/enum/enterpriseserveruseraccountorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountorderfield", - "/en/enterprise/v4/enum/enterpriseserveruseraccountorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountorderfield", - "/enterprise/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", - "/en/enterprise/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", - "/enterprise/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", - "/en/enterprise/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", - "/enterprise/v4/enum/enterpriseuseraccountmembershiprole": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseuseraccountmembershiprole", - "/en/enterprise/v4/enum/enterpriseuseraccountmembershiprole": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseuseraccountmembershiprole", - "/enterprise/v4/enum/enterpriseuserdeployment": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseuserdeployment", - "/en/enterprise/v4/enum/enterpriseuserdeployment": "/en/enterprise-server@latest/graphql/reference/enums#enterpriseuserdeployment", - "/enterprise/v4/enum/gistorderfield": "/en/enterprise-server@latest/graphql/reference/enums#gistorderfield", - "/en/enterprise/v4/enum/gistorderfield": "/en/enterprise-server@latest/graphql/reference/enums#gistorderfield", - "/enterprise/v4/enum/gistprivacy": "/en/enterprise-server@latest/graphql/reference/enums#gistprivacy", - "/en/enterprise/v4/enum/gistprivacy": "/en/enterprise-server@latest/graphql/reference/enums#gistprivacy", - "/enterprise/v4/enum/gitsignaturestate": "/en/enterprise-server@latest/graphql/reference/enums#gitsignaturestate", - "/en/enterprise/v4/enum/gitsignaturestate": "/en/enterprise-server@latest/graphql/reference/enums#gitsignaturestate", - "/enterprise/v4/enum/identityproviderconfigurationstate": "/en/enterprise-server@latest/graphql/reference/enums#identityproviderconfigurationstate", - "/en/enterprise/v4/enum/identityproviderconfigurationstate": "/en/enterprise-server@latest/graphql/reference/enums#identityproviderconfigurationstate", - "/enterprise/v4/enum/ipallowlistenabledsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#ipallowlistenabledsettingvalue", - "/en/enterprise/v4/enum/ipallowlistenabledsettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#ipallowlistenabledsettingvalue", - "/enterprise/v4/enum/ipallowlistentryorderfield": "/en/enterprise-server@latest/graphql/reference/enums#ipallowlistentryorderfield", - "/en/enterprise/v4/enum/ipallowlistentryorderfield": "/en/enterprise-server@latest/graphql/reference/enums#ipallowlistentryorderfield", - "/enterprise/v4/enum/issueorderfield": "/en/enterprise-server@latest/graphql/reference/enums#issueorderfield", - "/en/enterprise/v4/enum/issueorderfield": "/en/enterprise-server@latest/graphql/reference/enums#issueorderfield", - "/enterprise/v4/enum/issuestate": "/en/enterprise-server@latest/graphql/reference/enums#issuestate", - "/en/enterprise/v4/enum/issuestate": "/en/enterprise-server@latest/graphql/reference/enums#issuestate", - "/enterprise/v4/enum/issuetimelineitemsitemtype": "/en/enterprise-server@latest/graphql/reference/enums#issuetimelineitemsitemtype", - "/en/enterprise/v4/enum/issuetimelineitemsitemtype": "/en/enterprise-server@latest/graphql/reference/enums#issuetimelineitemsitemtype", - "/enterprise/v4/enum/labelorderfield": "/en/enterprise-server@latest/graphql/reference/enums#labelorderfield", - "/en/enterprise/v4/enum/labelorderfield": "/en/enterprise-server@latest/graphql/reference/enums#labelorderfield", - "/enterprise/v4/enum/languageorderfield": "/en/enterprise-server@latest/graphql/reference/enums#languageorderfield", - "/en/enterprise/v4/enum/languageorderfield": "/en/enterprise-server@latest/graphql/reference/enums#languageorderfield", - "/enterprise/v4/enum/lockreason": "/en/enterprise-server@latest/graphql/reference/enums#lockreason", - "/en/enterprise/v4/enum/lockreason": "/en/enterprise-server@latest/graphql/reference/enums#lockreason", - "/enterprise/v4/enum/mergeablestate": "/en/enterprise-server@latest/graphql/reference/enums#mergeablestate", - "/en/enterprise/v4/enum/mergeablestate": "/en/enterprise-server@latest/graphql/reference/enums#mergeablestate", - "/enterprise/v4/enum/mergestatestatus": "/en/enterprise-server@latest/graphql/reference/enums#mergestatestatus", - "/en/enterprise/v4/enum/mergestatestatus": "/en/enterprise-server@latest/graphql/reference/enums#mergestatestatus", - "/enterprise/v4/enum/milestoneorderfield": "/en/enterprise-server@latest/graphql/reference/enums#milestoneorderfield", - "/en/enterprise/v4/enum/milestoneorderfield": "/en/enterprise-server@latest/graphql/reference/enums#milestoneorderfield", - "/enterprise/v4/enum/milestonestate": "/en/enterprise-server@latest/graphql/reference/enums#milestonestate", - "/en/enterprise/v4/enum/milestonestate": "/en/enterprise-server@latest/graphql/reference/enums#milestonestate", - "/enterprise/v4/enum/oauthapplicationcreateauditentrystate": "/en/enterprise-server@latest/graphql/reference/enums#oauthapplicationcreateauditentrystate", - "/en/enterprise/v4/enum/oauthapplicationcreateauditentrystate": "/en/enterprise-server@latest/graphql/reference/enums#oauthapplicationcreateauditentrystate", - "/enterprise/v4/enum/operationtype": "/en/enterprise-server@latest/graphql/reference/enums#operationtype", - "/en/enterprise/v4/enum/operationtype": "/en/enterprise-server@latest/graphql/reference/enums#operationtype", - "/enterprise/v4/enum/orderdirection": "/en/enterprise-server@latest/graphql/reference/enums#orderdirection", - "/en/enterprise/v4/enum/orderdirection": "/en/enterprise-server@latest/graphql/reference/enums#orderdirection", - "/enterprise/v4/enum/orgaddmemberauditentrypermission": "/en/enterprise-server@latest/graphql/reference/enums#orgaddmemberauditentrypermission", - "/en/enterprise/v4/enum/orgaddmemberauditentrypermission": "/en/enterprise-server@latest/graphql/reference/enums#orgaddmemberauditentrypermission", - "/enterprise/v4/enum/organizationinvitationrole": "/en/enterprise-server@latest/graphql/reference/enums#organizationinvitationrole", - "/en/enterprise/v4/enum/organizationinvitationrole": "/en/enterprise-server@latest/graphql/reference/enums#organizationinvitationrole", - "/enterprise/v4/enum/organizationinvitationtype": "/en/enterprise-server@latest/graphql/reference/enums#organizationinvitationtype", - "/en/enterprise/v4/enum/organizationinvitationtype": "/en/enterprise-server@latest/graphql/reference/enums#organizationinvitationtype", - "/enterprise/v4/enum/organizationmemberrole": "/en/enterprise-server@latest/graphql/reference/enums#organizationmemberrole", - "/en/enterprise/v4/enum/organizationmemberrole": "/en/enterprise-server@latest/graphql/reference/enums#organizationmemberrole", - "/enterprise/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", - "/en/enterprise/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/en/enterprise-server@latest/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", - "/enterprise/v4/enum/organizationorderfield": "/en/enterprise-server@latest/graphql/reference/enums#organizationorderfield", - "/en/enterprise/v4/enum/organizationorderfield": "/en/enterprise-server@latest/graphql/reference/enums#organizationorderfield", - "/enterprise/v4/enum/orgcreateauditentrybillingplan": "/en/enterprise-server@latest/graphql/reference/enums#orgcreateauditentrybillingplan", - "/en/enterprise/v4/enum/orgcreateauditentrybillingplan": "/en/enterprise-server@latest/graphql/reference/enums#orgcreateauditentrybillingplan", - "/enterprise/v4/enum/orgremovebillingmanagerauditentryreason": "/en/enterprise-server@latest/graphql/reference/enums#orgremovebillingmanagerauditentryreason", - "/en/enterprise/v4/enum/orgremovebillingmanagerauditentryreason": "/en/enterprise-server@latest/graphql/reference/enums#orgremovebillingmanagerauditentryreason", - "/enterprise/v4/enum/orgremovememberauditentrymembershiptype": "/en/enterprise-server@latest/graphql/reference/enums#orgremovememberauditentrymembershiptype", - "/en/enterprise/v4/enum/orgremovememberauditentrymembershiptype": "/en/enterprise-server@latest/graphql/reference/enums#orgremovememberauditentrymembershiptype", - "/enterprise/v4/enum/orgremovememberauditentryreason": "/en/enterprise-server@latest/graphql/reference/enums#orgremovememberauditentryreason", - "/en/enterprise/v4/enum/orgremovememberauditentryreason": "/en/enterprise-server@latest/graphql/reference/enums#orgremovememberauditentryreason", - "/enterprise/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/en/enterprise-server@latest/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", - "/en/enterprise/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/en/enterprise-server@latest/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", - "/enterprise/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/en/enterprise-server@latest/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", - "/en/enterprise/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/en/enterprise-server@latest/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", - "/enterprise/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/en/enterprise-server@latest/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", - "/en/enterprise/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/en/enterprise-server@latest/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", - "/enterprise/v4/enum/orgupdatememberauditentrypermission": "/en/enterprise-server@latest/graphql/reference/enums#orgupdatememberauditentrypermission", - "/en/enterprise/v4/enum/orgupdatememberauditentrypermission": "/en/enterprise-server@latest/graphql/reference/enums#orgupdatememberauditentrypermission", - "/enterprise/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", - "/en/enterprise/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", - "/enterprise/v4/enum/packagefileorderfield": "/en/enterprise-server@latest/graphql/reference/enums#packagefileorderfield", - "/en/enterprise/v4/enum/packagefileorderfield": "/en/enterprise-server@latest/graphql/reference/enums#packagefileorderfield", - "/enterprise/v4/enum/packageorderfield": "/en/enterprise-server@latest/graphql/reference/enums#packageorderfield", - "/en/enterprise/v4/enum/packageorderfield": "/en/enterprise-server@latest/graphql/reference/enums#packageorderfield", - "/enterprise/v4/enum/packagetype": "/en/enterprise-server@latest/graphql/reference/enums#packagetype", - "/en/enterprise/v4/enum/packagetype": "/en/enterprise-server@latest/graphql/reference/enums#packagetype", - "/enterprise/v4/enum/packageversionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#packageversionorderfield", - "/en/enterprise/v4/enum/packageversionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#packageversionorderfield", - "/enterprise/v4/enum/pinnableitemtype": "/en/enterprise-server@latest/graphql/reference/enums#pinnableitemtype", - "/en/enterprise/v4/enum/pinnableitemtype": "/en/enterprise-server@latest/graphql/reference/enums#pinnableitemtype", - "/enterprise/v4/enum/projectcardarchivedstate": "/en/enterprise-server@latest/graphql/reference/enums#projectcardarchivedstate", - "/en/enterprise/v4/enum/projectcardarchivedstate": "/en/enterprise-server@latest/graphql/reference/enums#projectcardarchivedstate", - "/enterprise/v4/enum/projectcardstate": "/en/enterprise-server@latest/graphql/reference/enums#projectcardstate", - "/en/enterprise/v4/enum/projectcardstate": "/en/enterprise-server@latest/graphql/reference/enums#projectcardstate", - "/enterprise/v4/enum/projectcolumnpurpose": "/en/enterprise-server@latest/graphql/reference/enums#projectcolumnpurpose", - "/en/enterprise/v4/enum/projectcolumnpurpose": "/en/enterprise-server@latest/graphql/reference/enums#projectcolumnpurpose", - "/enterprise/v4/enum/projectorderfield": "/en/enterprise-server@latest/graphql/reference/enums#projectorderfield", - "/en/enterprise/v4/enum/projectorderfield": "/en/enterprise-server@latest/graphql/reference/enums#projectorderfield", - "/enterprise/v4/enum/projectstate": "/en/enterprise-server@latest/graphql/reference/enums#projectstate", - "/en/enterprise/v4/enum/projectstate": "/en/enterprise-server@latest/graphql/reference/enums#projectstate", - "/enterprise/v4/enum/projecttemplate": "/en/enterprise-server@latest/graphql/reference/enums#projecttemplate", - "/en/enterprise/v4/enum/projecttemplate": "/en/enterprise-server@latest/graphql/reference/enums#projecttemplate", - "/enterprise/v4/enum/pullrequestmergemethod": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestmergemethod", - "/en/enterprise/v4/enum/pullrequestmergemethod": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestmergemethod", - "/enterprise/v4/enum/pullrequestorderfield": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestorderfield", - "/en/enterprise/v4/enum/pullrequestorderfield": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestorderfield", - "/enterprise/v4/enum/pullrequestreviewcommentstate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewcommentstate", - "/en/enterprise/v4/enum/pullrequestreviewcommentstate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewcommentstate", - "/enterprise/v4/enum/pullrequestreviewdecision": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewdecision", - "/en/enterprise/v4/enum/pullrequestreviewdecision": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewdecision", - "/enterprise/v4/enum/pullrequestreviewevent": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewevent", - "/en/enterprise/v4/enum/pullrequestreviewevent": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewevent", - "/enterprise/v4/enum/pullrequestreviewstate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewstate", - "/en/enterprise/v4/enum/pullrequestreviewstate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestreviewstate", - "/enterprise/v4/enum/pullrequeststate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequeststate", - "/en/enterprise/v4/enum/pullrequeststate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequeststate", - "/enterprise/v4/enum/pullrequesttimelineitemsitemtype": "/en/enterprise-server@latest/graphql/reference/enums#pullrequesttimelineitemsitemtype", - "/en/enterprise/v4/enum/pullrequesttimelineitemsitemtype": "/en/enterprise-server@latest/graphql/reference/enums#pullrequesttimelineitemsitemtype", - "/enterprise/v4/enum/pullrequestupdatestate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestupdatestate", - "/en/enterprise/v4/enum/pullrequestupdatestate": "/en/enterprise-server@latest/graphql/reference/enums#pullrequestupdatestate", - "/enterprise/v4/enum/reactioncontent": "/en/enterprise-server@latest/graphql/reference/enums#reactioncontent", - "/en/enterprise/v4/enum/reactioncontent": "/en/enterprise-server@latest/graphql/reference/enums#reactioncontent", - "/enterprise/v4/enum/reactionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#reactionorderfield", - "/en/enterprise/v4/enum/reactionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#reactionorderfield", - "/enterprise/v4/enum/reforderfield": "/en/enterprise-server@latest/graphql/reference/enums#reforderfield", - "/en/enterprise/v4/enum/reforderfield": "/en/enterprise-server@latest/graphql/reference/enums#reforderfield", - "/enterprise/v4/enum/registrypackagedependencytype": "/en/enterprise-server@latest/graphql/reference/enums#registrypackagedependencytype", - "/en/enterprise/v4/enum/registrypackagedependencytype": "/en/enterprise-server@latest/graphql/reference/enums#registrypackagedependencytype", - "/enterprise/v4/enum/registrypackagetype": "/en/enterprise-server@latest/graphql/reference/enums#registrypackagetype", - "/en/enterprise/v4/enum/registrypackagetype": "/en/enterprise-server@latest/graphql/reference/enums#registrypackagetype", - "/enterprise/v4/enum/releaseorderfield": "/en/enterprise-server@latest/graphql/reference/enums#releaseorderfield", - "/en/enterprise/v4/enum/releaseorderfield": "/en/enterprise-server@latest/graphql/reference/enums#releaseorderfield", - "/enterprise/v4/enum/repoaccessauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repoaccessauditentryvisibility", - "/en/enterprise/v4/enum/repoaccessauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repoaccessauditentryvisibility", - "/enterprise/v4/enum/repoaddmemberauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repoaddmemberauditentryvisibility", - "/en/enterprise/v4/enum/repoaddmemberauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repoaddmemberauditentryvisibility", - "/enterprise/v4/enum/repoarchivedauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repoarchivedauditentryvisibility", - "/en/enterprise/v4/enum/repoarchivedauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repoarchivedauditentryvisibility", - "/enterprise/v4/enum/repochangemergesettingauditentrymergetype": "/en/enterprise-server@latest/graphql/reference/enums#repochangemergesettingauditentrymergetype", - "/en/enterprise/v4/enum/repochangemergesettingauditentrymergetype": "/en/enterprise-server@latest/graphql/reference/enums#repochangemergesettingauditentrymergetype", - "/enterprise/v4/enum/repocreateauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repocreateauditentryvisibility", - "/en/enterprise/v4/enum/repocreateauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repocreateauditentryvisibility", - "/enterprise/v4/enum/repodestroyauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repodestroyauditentryvisibility", - "/en/enterprise/v4/enum/repodestroyauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repodestroyauditentryvisibility", - "/enterprise/v4/enum/reporemovememberauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#reporemovememberauditentryvisibility", - "/en/enterprise/v4/enum/reporemovememberauditentryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#reporemovememberauditentryvisibility", - "/enterprise/v4/enum/reportedcontentclassifiers": "/en/enterprise-server@latest/graphql/reference/enums#reportedcontentclassifiers", - "/en/enterprise/v4/enum/reportedcontentclassifiers": "/en/enterprise-server@latest/graphql/reference/enums#reportedcontentclassifiers", - "/enterprise/v4/enum/repositoryaffiliation": "/en/enterprise-server@latest/graphql/reference/enums#repositoryaffiliation", - "/en/enterprise/v4/enum/repositoryaffiliation": "/en/enterprise-server@latest/graphql/reference/enums#repositoryaffiliation", - "/enterprise/v4/enum/repositorycontributiontype": "/en/enterprise-server@latest/graphql/reference/enums#repositorycontributiontype", - "/en/enterprise/v4/enum/repositorycontributiontype": "/en/enterprise-server@latest/graphql/reference/enums#repositorycontributiontype", - "/enterprise/v4/enum/repositoryinvitationorderfield": "/en/enterprise-server@latest/graphql/reference/enums#repositoryinvitationorderfield", - "/en/enterprise/v4/enum/repositoryinvitationorderfield": "/en/enterprise-server@latest/graphql/reference/enums#repositoryinvitationorderfield", - "/enterprise/v4/enum/repositorylockreason": "/en/enterprise-server@latest/graphql/reference/enums#repositorylockreason", - "/en/enterprise/v4/enum/repositorylockreason": "/en/enterprise-server@latest/graphql/reference/enums#repositorylockreason", - "/enterprise/v4/enum/repositoryorderfield": "/en/enterprise-server@latest/graphql/reference/enums#repositoryorderfield", - "/en/enterprise/v4/enum/repositoryorderfield": "/en/enterprise-server@latest/graphql/reference/enums#repositoryorderfield", - "/enterprise/v4/enum/repositorypermission": "/en/enterprise-server@latest/graphql/reference/enums#repositorypermission", - "/en/enterprise/v4/enum/repositorypermission": "/en/enterprise-server@latest/graphql/reference/enums#repositorypermission", - "/enterprise/v4/enum/repositoryprivacy": "/en/enterprise-server@latest/graphql/reference/enums#repositoryprivacy", - "/en/enterprise/v4/enum/repositoryprivacy": "/en/enterprise-server@latest/graphql/reference/enums#repositoryprivacy", - "/enterprise/v4/enum/repositoryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repositoryvisibility", - "/en/enterprise/v4/enum/repositoryvisibility": "/en/enterprise-server@latest/graphql/reference/enums#repositoryvisibility", - "/enterprise/v4/enum/requestablecheckstatusstate": "/en/enterprise-server@latest/graphql/reference/enums#requestablecheckstatusstate", - "/en/enterprise/v4/enum/requestablecheckstatusstate": "/en/enterprise-server@latest/graphql/reference/enums#requestablecheckstatusstate", - "/enterprise/v4/enum/samldigestalgorithm": "/en/enterprise-server@latest/graphql/reference/enums#samldigestalgorithm", - "/en/enterprise/v4/enum/samldigestalgorithm": "/en/enterprise-server@latest/graphql/reference/enums#samldigestalgorithm", - "/enterprise/v4/enum/samlsignaturealgorithm": "/en/enterprise-server@latest/graphql/reference/enums#samlsignaturealgorithm", - "/en/enterprise/v4/enum/samlsignaturealgorithm": "/en/enterprise-server@latest/graphql/reference/enums#samlsignaturealgorithm", - "/enterprise/v4/enum/savedreplyorderfield": "/en/enterprise-server@latest/graphql/reference/enums#savedreplyorderfield", - "/en/enterprise/v4/enum/savedreplyorderfield": "/en/enterprise-server@latest/graphql/reference/enums#savedreplyorderfield", - "/enterprise/v4/enum/searchtype": "/en/enterprise-server@latest/graphql/reference/enums#searchtype", - "/en/enterprise/v4/enum/searchtype": "/en/enterprise-server@latest/graphql/reference/enums#searchtype", - "/enterprise/v4/enum/securityadvisoryecosystem": "/en/enterprise-server@latest/graphql/reference/enums#securityadvisoryecosystem", - "/en/enterprise/v4/enum/securityadvisoryecosystem": "/en/enterprise-server@latest/graphql/reference/enums#securityadvisoryecosystem", - "/enterprise/v4/enum/securityadvisoryseverity": "/en/enterprise-server@latest/graphql/reference/enums#securityadvisoryseverity", - "/en/enterprise/v4/enum/securityadvisoryseverity": "/en/enterprise-server@latest/graphql/reference/enums#securityadvisoryseverity", - "/enterprise/v4/enum/sponsorshipprivacy": "/en/enterprise-server@latest/graphql/reference/enums#sponsorshipprivacy", - "/en/enterprise/v4/enum/sponsorshipprivacy": "/en/enterprise-server@latest/graphql/reference/enums#sponsorshipprivacy", - "/enterprise/v4/enum/starorderfield": "/en/enterprise-server@latest/graphql/reference/enums#starorderfield", - "/en/enterprise/v4/enum/starorderfield": "/en/enterprise-server@latest/graphql/reference/enums#starorderfield", - "/enterprise/v4/enum/statusstate": "/en/enterprise-server@latest/graphql/reference/enums#statusstate", - "/en/enterprise/v4/enum/statusstate": "/en/enterprise-server@latest/graphql/reference/enums#statusstate", - "/enterprise/v4/enum/subscriptionstate": "/en/enterprise-server@latest/graphql/reference/enums#subscriptionstate", - "/en/enterprise/v4/enum/subscriptionstate": "/en/enterprise-server@latest/graphql/reference/enums#subscriptionstate", - "/enterprise/v4/enum/teamdiscussioncommentorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamdiscussioncommentorderfield", - "/en/enterprise/v4/enum/teamdiscussioncommentorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamdiscussioncommentorderfield", - "/enterprise/v4/enum/teamdiscussionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamdiscussionorderfield", - "/en/enterprise/v4/enum/teamdiscussionorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamdiscussionorderfield", - "/enterprise/v4/enum/teammemberorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teammemberorderfield", - "/en/enterprise/v4/enum/teammemberorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teammemberorderfield", - "/enterprise/v4/enum/teammemberrole": "/en/enterprise-server@latest/graphql/reference/enums#teammemberrole", - "/en/enterprise/v4/enum/teammemberrole": "/en/enterprise-server@latest/graphql/reference/enums#teammemberrole", - "/enterprise/v4/enum/teammembershiptype": "/en/enterprise-server@latest/graphql/reference/enums#teammembershiptype", - "/en/enterprise/v4/enum/teammembershiptype": "/en/enterprise-server@latest/graphql/reference/enums#teammembershiptype", - "/enterprise/v4/enum/teamorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamorderfield", - "/en/enterprise/v4/enum/teamorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamorderfield", - "/enterprise/v4/enum/teamprivacy": "/en/enterprise-server@latest/graphql/reference/enums#teamprivacy", - "/en/enterprise/v4/enum/teamprivacy": "/en/enterprise-server@latest/graphql/reference/enums#teamprivacy", - "/enterprise/v4/enum/teamrepositoryorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamrepositoryorderfield", - "/en/enterprise/v4/enum/teamrepositoryorderfield": "/en/enterprise-server@latest/graphql/reference/enums#teamrepositoryorderfield", - "/enterprise/v4/enum/teamreviewassignmentalgorithm": "/en/enterprise-server@latest/graphql/reference/enums#teamreviewassignmentalgorithm", - "/en/enterprise/v4/enum/teamreviewassignmentalgorithm": "/en/enterprise-server@latest/graphql/reference/enums#teamreviewassignmentalgorithm", - "/enterprise/v4/enum/teamrole": "/en/enterprise-server@latest/graphql/reference/enums#teamrole", - "/en/enterprise/v4/enum/teamrole": "/en/enterprise-server@latest/graphql/reference/enums#teamrole", - "/enterprise/v4/enum/userblockduration": "/en/enterprise-server@latest/graphql/reference/enums#userblockduration", - "/en/enterprise/v4/enum/userblockduration": "/en/enterprise-server@latest/graphql/reference/enums#userblockduration", - "/enterprise/v4/enum/userstatusorderfield": "/en/enterprise-server@latest/graphql/reference/enums#userstatusorderfield", - "/en/enterprise/v4/enum/userstatusorderfield": "/en/enterprise-server@latest/graphql/reference/enums#userstatusorderfield", - "/enterprise/v4/input_object/addassigneestoassignableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addassigneestoassignableinput", - "/en/enterprise/v4/input_object/addassigneestoassignableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addassigneestoassignableinput", - "/enterprise/v4/input_object/addcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addcommentinput", - "/en/enterprise/v4/input_object/addcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addcommentinput", - "/enterprise/v4/input_object/addenterpriseadmininput": "/en/enterprise-server@latest/graphql/reference/input-objects#addenterpriseadmininput", - "/en/enterprise/v4/input_object/addenterpriseadmininput": "/en/enterprise-server@latest/graphql/reference/input-objects#addenterpriseadmininput", - "/enterprise/v4/input_object/addlabelstolabelableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addlabelstolabelableinput", - "/en/enterprise/v4/input_object/addlabelstolabelableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addlabelstolabelableinput", - "/enterprise/v4/input_object/addprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addprojectcardinput", - "/en/enterprise/v4/input_object/addprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addprojectcardinput", - "/enterprise/v4/input_object/addprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#addprojectcolumninput", - "/en/enterprise/v4/input_object/addprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#addprojectcolumninput", - "/enterprise/v4/input_object/addpullrequestreviewcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewcommentinput", - "/en/enterprise/v4/input_object/addpullrequestreviewcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewcommentinput", - "/enterprise/v4/input_object/addpullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewinput", - "/en/enterprise/v4/input_object/addpullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewinput", - "/enterprise/v4/input_object/addpullrequestreviewthreadinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewthreadinput", - "/en/enterprise/v4/input_object/addpullrequestreviewthreadinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewthreadinput", - "/enterprise/v4/input_object/addreactioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#addreactioninput", - "/en/enterprise/v4/input_object/addreactioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#addreactioninput", - "/enterprise/v4/input_object/addstarinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addstarinput", - "/en/enterprise/v4/input_object/addstarinput": "/en/enterprise-server@latest/graphql/reference/input-objects#addstarinput", - "/enterprise/v4/input_object/archiverepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#archiverepositoryinput", - "/en/enterprise/v4/input_object/archiverepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#archiverepositoryinput", - "/enterprise/v4/input_object/auditlogorder": "/en/enterprise-server@latest/graphql/reference/input-objects#auditlogorder", - "/en/enterprise/v4/input_object/auditlogorder": "/en/enterprise-server@latest/graphql/reference/input-objects#auditlogorder", - "/enterprise/v4/input_object/changeuserstatusinput": "/en/enterprise-server@latest/graphql/reference/input-objects#changeuserstatusinput", - "/en/enterprise/v4/input_object/changeuserstatusinput": "/en/enterprise-server@latest/graphql/reference/input-objects#changeuserstatusinput", - "/enterprise/v4/input_object/checkannotationdata": "/en/enterprise-server@latest/graphql/reference/input-objects#checkannotationdata", - "/en/enterprise/v4/input_object/checkannotationdata": "/en/enterprise-server@latest/graphql/reference/input-objects#checkannotationdata", - "/enterprise/v4/input_object/checkannotationrange": "/en/enterprise-server@latest/graphql/reference/input-objects#checkannotationrange", - "/en/enterprise/v4/input_object/checkannotationrange": "/en/enterprise-server@latest/graphql/reference/input-objects#checkannotationrange", - "/enterprise/v4/input_object/checkrunaction": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunaction", - "/en/enterprise/v4/input_object/checkrunaction": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunaction", - "/enterprise/v4/input_object/checkrunfilter": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunfilter", - "/en/enterprise/v4/input_object/checkrunfilter": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunfilter", - "/enterprise/v4/input_object/checkrunoutput": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunoutput", - "/en/enterprise/v4/input_object/checkrunoutput": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunoutput", - "/enterprise/v4/input_object/checkrunoutputimage": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunoutputimage", - "/en/enterprise/v4/input_object/checkrunoutputimage": "/en/enterprise-server@latest/graphql/reference/input-objects#checkrunoutputimage", - "/enterprise/v4/input_object/checksuiteautotriggerpreference": "/en/enterprise-server@latest/graphql/reference/input-objects#checksuiteautotriggerpreference", - "/en/enterprise/v4/input_object/checksuiteautotriggerpreference": "/en/enterprise-server@latest/graphql/reference/input-objects#checksuiteautotriggerpreference", - "/enterprise/v4/input_object/checksuitefilter": "/en/enterprise-server@latest/graphql/reference/input-objects#checksuitefilter", - "/en/enterprise/v4/input_object/checksuitefilter": "/en/enterprise-server@latest/graphql/reference/input-objects#checksuitefilter", - "/enterprise/v4/input_object/clearlabelsfromlabelableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#clearlabelsfromlabelableinput", - "/en/enterprise/v4/input_object/clearlabelsfromlabelableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#clearlabelsfromlabelableinput", - "/enterprise/v4/input_object/cloneprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#cloneprojectinput", - "/en/enterprise/v4/input_object/cloneprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#cloneprojectinput", - "/enterprise/v4/input_object/clonetemplaterepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#clonetemplaterepositoryinput", - "/en/enterprise/v4/input_object/clonetemplaterepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#clonetemplaterepositoryinput", - "/enterprise/v4/input_object/closeissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#closeissueinput", - "/en/enterprise/v4/input_object/closeissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#closeissueinput", - "/enterprise/v4/input_object/closepullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#closepullrequestinput", - "/en/enterprise/v4/input_object/closepullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#closepullrequestinput", - "/enterprise/v4/input_object/commitauthor": "/en/enterprise-server@latest/graphql/reference/input-objects#commitauthor", - "/en/enterprise/v4/input_object/commitauthor": "/en/enterprise-server@latest/graphql/reference/input-objects#commitauthor", - "/enterprise/v4/input_object/commitcontributionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#commitcontributionorder", - "/en/enterprise/v4/input_object/commitcontributionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#commitcontributionorder", - "/enterprise/v4/input_object/contributionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#contributionorder", - "/en/enterprise/v4/input_object/contributionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#contributionorder", - "/enterprise/v4/input_object/convertprojectcardnotetoissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#convertprojectcardnotetoissueinput", - "/en/enterprise/v4/input_object/convertprojectcardnotetoissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#convertprojectcardnotetoissueinput", - "/enterprise/v4/input_object/createbranchprotectionruleinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createbranchprotectionruleinput", - "/en/enterprise/v4/input_object/createbranchprotectionruleinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createbranchprotectionruleinput", - "/enterprise/v4/input_object/createcheckruninput": "/en/enterprise-server@latest/graphql/reference/input-objects#createcheckruninput", - "/en/enterprise/v4/input_object/createcheckruninput": "/en/enterprise-server@latest/graphql/reference/input-objects#createcheckruninput", - "/enterprise/v4/input_object/createchecksuiteinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createchecksuiteinput", - "/en/enterprise/v4/input_object/createchecksuiteinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createchecksuiteinput", - "/enterprise/v4/input_object/createcontentattachmentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createcontentattachmentinput", - "/en/enterprise/v4/input_object/createcontentattachmentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createcontentattachmentinput", - "/enterprise/v4/input_object/createdeploymentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createdeploymentinput", - "/en/enterprise/v4/input_object/createdeploymentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createdeploymentinput", - "/enterprise/v4/input_object/createdeploymentstatusinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createdeploymentstatusinput", - "/en/enterprise/v4/input_object/createdeploymentstatusinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createdeploymentstatusinput", - "/enterprise/v4/input_object/createipallowlistentryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createipallowlistentryinput", - "/en/enterprise/v4/input_object/createipallowlistentryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createipallowlistentryinput", - "/enterprise/v4/input_object/createissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createissueinput", - "/en/enterprise/v4/input_object/createissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createissueinput", - "/enterprise/v4/input_object/createlabelinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createlabelinput", - "/en/enterprise/v4/input_object/createlabelinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createlabelinput", - "/enterprise/v4/input_object/createprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createprojectinput", - "/en/enterprise/v4/input_object/createprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createprojectinput", - "/enterprise/v4/input_object/createpullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createpullrequestinput", - "/en/enterprise/v4/input_object/createpullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createpullrequestinput", - "/enterprise/v4/input_object/createrefinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createrefinput", - "/en/enterprise/v4/input_object/createrefinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createrefinput", - "/enterprise/v4/input_object/createrepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createrepositoryinput", - "/en/enterprise/v4/input_object/createrepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createrepositoryinput", - "/enterprise/v4/input_object/createteamdiscussioncommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createteamdiscussioncommentinput", - "/en/enterprise/v4/input_object/createteamdiscussioncommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#createteamdiscussioncommentinput", - "/enterprise/v4/input_object/createteamdiscussioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#createteamdiscussioninput", - "/en/enterprise/v4/input_object/createteamdiscussioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#createteamdiscussioninput", - "/enterprise/v4/input_object/deletebranchprotectionruleinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletebranchprotectionruleinput", - "/en/enterprise/v4/input_object/deletebranchprotectionruleinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletebranchprotectionruleinput", - "/enterprise/v4/input_object/deletedeploymentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletedeploymentinput", - "/en/enterprise/v4/input_object/deletedeploymentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletedeploymentinput", - "/enterprise/v4/input_object/deleteipallowlistentryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteipallowlistentryinput", - "/en/enterprise/v4/input_object/deleteipallowlistentryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteipallowlistentryinput", - "/enterprise/v4/input_object/deleteissuecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteissuecommentinput", - "/en/enterprise/v4/input_object/deleteissuecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteissuecommentinput", - "/enterprise/v4/input_object/deleteissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteissueinput", - "/en/enterprise/v4/input_object/deleteissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteissueinput", - "/enterprise/v4/input_object/deletelabelinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletelabelinput", - "/en/enterprise/v4/input_object/deletelabelinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletelabelinput", - "/enterprise/v4/input_object/deletepackageversioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletepackageversioninput", - "/en/enterprise/v4/input_object/deletepackageversioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletepackageversioninput", - "/enterprise/v4/input_object/deleteprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteprojectcardinput", - "/en/enterprise/v4/input_object/deleteprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteprojectcardinput", - "/enterprise/v4/input_object/deleteprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteprojectcolumninput", - "/en/enterprise/v4/input_object/deleteprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteprojectcolumninput", - "/enterprise/v4/input_object/deleteprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteprojectinput", - "/en/enterprise/v4/input_object/deleteprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteprojectinput", - "/enterprise/v4/input_object/deletepullrequestreviewcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletepullrequestreviewcommentinput", - "/en/enterprise/v4/input_object/deletepullrequestreviewcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletepullrequestreviewcommentinput", - "/enterprise/v4/input_object/deletepullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletepullrequestreviewinput", - "/en/enterprise/v4/input_object/deletepullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deletepullrequestreviewinput", - "/enterprise/v4/input_object/deleterefinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleterefinput", - "/en/enterprise/v4/input_object/deleterefinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleterefinput", - "/enterprise/v4/input_object/deleteteamdiscussioncommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteteamdiscussioncommentinput", - "/en/enterprise/v4/input_object/deleteteamdiscussioncommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteteamdiscussioncommentinput", - "/enterprise/v4/input_object/deleteteamdiscussioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteteamdiscussioninput", - "/en/enterprise/v4/input_object/deleteteamdiscussioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#deleteteamdiscussioninput", - "/enterprise/v4/input_object/deploymentorder": "/en/enterprise-server@latest/graphql/reference/input-objects#deploymentorder", - "/en/enterprise/v4/input_object/deploymentorder": "/en/enterprise-server@latest/graphql/reference/input-objects#deploymentorder", - "/enterprise/v4/input_object/dismisspullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#dismisspullrequestreviewinput", - "/en/enterprise/v4/input_object/dismisspullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#dismisspullrequestreviewinput", - "/enterprise/v4/input_object/draftpullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/input-objects#draftpullrequestreviewcomment", - "/en/enterprise/v4/input_object/draftpullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/input-objects#draftpullrequestreviewcomment", - "/enterprise/v4/input_object/draftpullrequestreviewthread": "/en/enterprise-server@latest/graphql/reference/input-objects#draftpullrequestreviewthread", - "/en/enterprise/v4/input_object/draftpullrequestreviewthread": "/en/enterprise-server@latest/graphql/reference/input-objects#draftpullrequestreviewthread", - "/enterprise/v4/input_object/enterpriseadministratorinvitationorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseadministratorinvitationorder", - "/en/enterprise/v4/input_object/enterpriseadministratorinvitationorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseadministratorinvitationorder", - "/enterprise/v4/input_object/enterprisememberorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterprisememberorder", - "/en/enterprise/v4/input_object/enterprisememberorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterprisememberorder", - "/enterprise/v4/input_object/enterpriseserveruseraccountemailorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", - "/en/enterprise/v4/input_object/enterpriseserveruseraccountemailorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", - "/enterprise/v4/input_object/enterpriseserveruseraccountorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountorder", - "/en/enterprise/v4/input_object/enterpriseserveruseraccountorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountorder", - "/enterprise/v4/input_object/enterpriseserveruseraccountsuploadorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", - "/en/enterprise/v4/input_object/enterpriseserveruseraccountsuploadorder": "/en/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", - "/enterprise/v4/input_object/followuserinput": "/en/enterprise-server@latest/graphql/reference/input-objects#followuserinput", - "/en/enterprise/v4/input_object/followuserinput": "/en/enterprise-server@latest/graphql/reference/input-objects#followuserinput", - "/enterprise/v4/input_object/gistorder": "/en/enterprise-server@latest/graphql/reference/input-objects#gistorder", - "/en/enterprise/v4/input_object/gistorder": "/en/enterprise-server@latest/graphql/reference/input-objects#gistorder", - "/enterprise/v4/input_object/importprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#importprojectinput", - "/en/enterprise/v4/input_object/importprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#importprojectinput", - "/enterprise/v4/input_object/ipallowlistentryorder": "/en/enterprise-server@latest/graphql/reference/input-objects#ipallowlistentryorder", - "/en/enterprise/v4/input_object/ipallowlistentryorder": "/en/enterprise-server@latest/graphql/reference/input-objects#ipallowlistentryorder", - "/enterprise/v4/input_object/issuefilters": "/en/enterprise-server@latest/graphql/reference/input-objects#issuefilters", - "/en/enterprise/v4/input_object/issuefilters": "/en/enterprise-server@latest/graphql/reference/input-objects#issuefilters", - "/enterprise/v4/input_object/issueorder": "/en/enterprise-server@latest/graphql/reference/input-objects#issueorder", - "/en/enterprise/v4/input_object/issueorder": "/en/enterprise-server@latest/graphql/reference/input-objects#issueorder", - "/enterprise/v4/input_object/labelorder": "/en/enterprise-server@latest/graphql/reference/input-objects#labelorder", - "/en/enterprise/v4/input_object/labelorder": "/en/enterprise-server@latest/graphql/reference/input-objects#labelorder", - "/enterprise/v4/input_object/languageorder": "/en/enterprise-server@latest/graphql/reference/input-objects#languageorder", - "/en/enterprise/v4/input_object/languageorder": "/en/enterprise-server@latest/graphql/reference/input-objects#languageorder", - "/enterprise/v4/input_object/linkrepositorytoprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#linkrepositorytoprojectinput", - "/en/enterprise/v4/input_object/linkrepositorytoprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#linkrepositorytoprojectinput", - "/enterprise/v4/input_object/locklockableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#locklockableinput", - "/en/enterprise/v4/input_object/locklockableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#locklockableinput", - "/enterprise/v4/input_object/markpullrequestreadyforreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#markpullrequestreadyforreviewinput", - "/en/enterprise/v4/input_object/markpullrequestreadyforreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#markpullrequestreadyforreviewinput", - "/enterprise/v4/input_object/mergebranchinput": "/en/enterprise-server@latest/graphql/reference/input-objects#mergebranchinput", - "/en/enterprise/v4/input_object/mergebranchinput": "/en/enterprise-server@latest/graphql/reference/input-objects#mergebranchinput", - "/enterprise/v4/input_object/mergepullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#mergepullrequestinput", - "/en/enterprise/v4/input_object/mergepullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#mergepullrequestinput", - "/enterprise/v4/input_object/milestoneorder": "/en/enterprise-server@latest/graphql/reference/input-objects#milestoneorder", - "/en/enterprise/v4/input_object/milestoneorder": "/en/enterprise-server@latest/graphql/reference/input-objects#milestoneorder", - "/enterprise/v4/input_object/minimizecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#minimizecommentinput", - "/en/enterprise/v4/input_object/minimizecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#minimizecommentinput", - "/enterprise/v4/input_object/moveprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#moveprojectcardinput", - "/en/enterprise/v4/input_object/moveprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#moveprojectcardinput", - "/enterprise/v4/input_object/moveprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#moveprojectcolumninput", - "/en/enterprise/v4/input_object/moveprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#moveprojectcolumninput", - "/enterprise/v4/input_object/organizationorder": "/en/enterprise-server@latest/graphql/reference/input-objects#organizationorder", - "/en/enterprise/v4/input_object/organizationorder": "/en/enterprise-server@latest/graphql/reference/input-objects#organizationorder", - "/enterprise/v4/input_object/packagefileorder": "/en/enterprise-server@latest/graphql/reference/input-objects#packagefileorder", - "/en/enterprise/v4/input_object/packagefileorder": "/en/enterprise-server@latest/graphql/reference/input-objects#packagefileorder", - "/enterprise/v4/input_object/packageorder": "/en/enterprise-server@latest/graphql/reference/input-objects#packageorder", - "/en/enterprise/v4/input_object/packageorder": "/en/enterprise-server@latest/graphql/reference/input-objects#packageorder", - "/enterprise/v4/input_object/packageversionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#packageversionorder", - "/en/enterprise/v4/input_object/packageversionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#packageversionorder", - "/enterprise/v4/input_object/pinissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#pinissueinput", - "/en/enterprise/v4/input_object/pinissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#pinissueinput", - "/enterprise/v4/input_object/projectcardimport": "/en/enterprise-server@latest/graphql/reference/input-objects#projectcardimport", - "/en/enterprise/v4/input_object/projectcardimport": "/en/enterprise-server@latest/graphql/reference/input-objects#projectcardimport", - "/enterprise/v4/input_object/projectcolumnimport": "/en/enterprise-server@latest/graphql/reference/input-objects#projectcolumnimport", - "/en/enterprise/v4/input_object/projectcolumnimport": "/en/enterprise-server@latest/graphql/reference/input-objects#projectcolumnimport", - "/enterprise/v4/input_object/projectorder": "/en/enterprise-server@latest/graphql/reference/input-objects#projectorder", - "/en/enterprise/v4/input_object/projectorder": "/en/enterprise-server@latest/graphql/reference/input-objects#projectorder", - "/enterprise/v4/input_object/pullrequestorder": "/en/enterprise-server@latest/graphql/reference/input-objects#pullrequestorder", - "/en/enterprise/v4/input_object/pullrequestorder": "/en/enterprise-server@latest/graphql/reference/input-objects#pullrequestorder", - "/enterprise/v4/input_object/reactionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#reactionorder", - "/en/enterprise/v4/input_object/reactionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#reactionorder", - "/enterprise/v4/input_object/reforder": "/en/enterprise-server@latest/graphql/reference/input-objects#reforder", - "/en/enterprise/v4/input_object/reforder": "/en/enterprise-server@latest/graphql/reference/input-objects#reforder", - "/enterprise/v4/input_object/refupdate": "/en/enterprise-server@latest/graphql/reference/input-objects#refupdate", - "/en/enterprise/v4/input_object/refupdate": "/en/enterprise-server@latest/graphql/reference/input-objects#refupdate", - "/enterprise/v4/input_object/registrypackagemetadatum": "/en/enterprise-server@latest/graphql/reference/input-objects#registrypackagemetadatum", - "/en/enterprise/v4/input_object/registrypackagemetadatum": "/en/enterprise-server@latest/graphql/reference/input-objects#registrypackagemetadatum", - "/enterprise/v4/input_object/releaseorder": "/en/enterprise-server@latest/graphql/reference/input-objects#releaseorder", - "/en/enterprise/v4/input_object/releaseorder": "/en/enterprise-server@latest/graphql/reference/input-objects#releaseorder", - "/enterprise/v4/input_object/removeassigneesfromassignableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removeassigneesfromassignableinput", - "/en/enterprise/v4/input_object/removeassigneesfromassignableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removeassigneesfromassignableinput", - "/enterprise/v4/input_object/removeenterpriseadmininput": "/en/enterprise-server@latest/graphql/reference/input-objects#removeenterpriseadmininput", - "/en/enterprise/v4/input_object/removeenterpriseadmininput": "/en/enterprise-server@latest/graphql/reference/input-objects#removeenterpriseadmininput", - "/enterprise/v4/input_object/removelabelsfromlabelableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removelabelsfromlabelableinput", - "/en/enterprise/v4/input_object/removelabelsfromlabelableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removelabelsfromlabelableinput", - "/enterprise/v4/input_object/removeoutsidecollaboratorinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removeoutsidecollaboratorinput", - "/en/enterprise/v4/input_object/removeoutsidecollaboratorinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removeoutsidecollaboratorinput", - "/enterprise/v4/input_object/removereactioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#removereactioninput", - "/en/enterprise/v4/input_object/removereactioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#removereactioninput", - "/enterprise/v4/input_object/removestarinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removestarinput", - "/en/enterprise/v4/input_object/removestarinput": "/en/enterprise-server@latest/graphql/reference/input-objects#removestarinput", - "/enterprise/v4/input_object/reopenissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#reopenissueinput", - "/en/enterprise/v4/input_object/reopenissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#reopenissueinput", - "/enterprise/v4/input_object/reopenpullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#reopenpullrequestinput", - "/en/enterprise/v4/input_object/reopenpullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#reopenpullrequestinput", - "/enterprise/v4/input_object/repositoryinvitationorder": "/en/enterprise-server@latest/graphql/reference/input-objects#repositoryinvitationorder", - "/en/enterprise/v4/input_object/repositoryinvitationorder": "/en/enterprise-server@latest/graphql/reference/input-objects#repositoryinvitationorder", - "/enterprise/v4/input_object/repositoryorder": "/en/enterprise-server@latest/graphql/reference/input-objects#repositoryorder", - "/en/enterprise/v4/input_object/repositoryorder": "/en/enterprise-server@latest/graphql/reference/input-objects#repositoryorder", - "/enterprise/v4/input_object/requestreviewsinput": "/en/enterprise-server@latest/graphql/reference/input-objects#requestreviewsinput", - "/en/enterprise/v4/input_object/requestreviewsinput": "/en/enterprise-server@latest/graphql/reference/input-objects#requestreviewsinput", - "/enterprise/v4/input_object/rerequestchecksuiteinput": "/en/enterprise-server@latest/graphql/reference/input-objects#rerequestchecksuiteinput", - "/en/enterprise/v4/input_object/rerequestchecksuiteinput": "/en/enterprise-server@latest/graphql/reference/input-objects#rerequestchecksuiteinput", - "/enterprise/v4/input_object/resolvereviewthreadinput": "/en/enterprise-server@latest/graphql/reference/input-objects#resolvereviewthreadinput", - "/en/enterprise/v4/input_object/resolvereviewthreadinput": "/en/enterprise-server@latest/graphql/reference/input-objects#resolvereviewthreadinput", - "/enterprise/v4/input_object/savedreplyorder": "/en/enterprise-server@latest/graphql/reference/input-objects#savedreplyorder", - "/en/enterprise/v4/input_object/savedreplyorder": "/en/enterprise-server@latest/graphql/reference/input-objects#savedreplyorder", - "/enterprise/v4/input_object/sponsorshiporder": "/en/enterprise-server@latest/graphql/reference/input-objects#sponsorshiporder", - "/en/enterprise/v4/input_object/sponsorshiporder": "/en/enterprise-server@latest/graphql/reference/input-objects#sponsorshiporder", - "/enterprise/v4/input_object/starorder": "/en/enterprise-server@latest/graphql/reference/input-objects#starorder", - "/en/enterprise/v4/input_object/starorder": "/en/enterprise-server@latest/graphql/reference/input-objects#starorder", - "/enterprise/v4/input_object/submitpullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#submitpullrequestreviewinput", - "/en/enterprise/v4/input_object/submitpullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#submitpullrequestreviewinput", - "/enterprise/v4/input_object/teamdiscussioncommentorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamdiscussioncommentorder", - "/en/enterprise/v4/input_object/teamdiscussioncommentorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamdiscussioncommentorder", - "/enterprise/v4/input_object/teamdiscussionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamdiscussionorder", - "/en/enterprise/v4/input_object/teamdiscussionorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamdiscussionorder", - "/enterprise/v4/input_object/teammemberorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teammemberorder", - "/en/enterprise/v4/input_object/teammemberorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teammemberorder", - "/enterprise/v4/input_object/teamorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamorder", - "/en/enterprise/v4/input_object/teamorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamorder", - "/enterprise/v4/input_object/teamrepositoryorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamrepositoryorder", - "/en/enterprise/v4/input_object/teamrepositoryorder": "/en/enterprise-server@latest/graphql/reference/input-objects#teamrepositoryorder", - "/enterprise/v4/input_object/transferissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#transferissueinput", - "/en/enterprise/v4/input_object/transferissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#transferissueinput", - "/enterprise/v4/input_object/unarchiverepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unarchiverepositoryinput", - "/en/enterprise/v4/input_object/unarchiverepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unarchiverepositoryinput", - "/enterprise/v4/input_object/unfollowuserinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unfollowuserinput", - "/en/enterprise/v4/input_object/unfollowuserinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unfollowuserinput", - "/enterprise/v4/input_object/unlinkrepositoryfromprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", - "/en/enterprise/v4/input_object/unlinkrepositoryfromprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", - "/enterprise/v4/input_object/unlocklockableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unlocklockableinput", - "/en/enterprise/v4/input_object/unlocklockableinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unlocklockableinput", - "/enterprise/v4/input_object/unmarkissueasduplicateinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unmarkissueasduplicateinput", - "/en/enterprise/v4/input_object/unmarkissueasduplicateinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unmarkissueasduplicateinput", - "/enterprise/v4/input_object/unminimizecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unminimizecommentinput", - "/en/enterprise/v4/input_object/unminimizecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unminimizecommentinput", - "/enterprise/v4/input_object/unpinissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unpinissueinput", - "/en/enterprise/v4/input_object/unpinissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unpinissueinput", - "/enterprise/v4/input_object/unresolvereviewthreadinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unresolvereviewthreadinput", - "/en/enterprise/v4/input_object/unresolvereviewthreadinput": "/en/enterprise-server@latest/graphql/reference/input-objects#unresolvereviewthreadinput", - "/enterprise/v4/input_object/updatebranchprotectionruleinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatebranchprotectionruleinput", - "/en/enterprise/v4/input_object/updatebranchprotectionruleinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatebranchprotectionruleinput", - "/enterprise/v4/input_object/updatecheckruninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatecheckruninput", - "/en/enterprise/v4/input_object/updatecheckruninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatecheckruninput", - "/enterprise/v4/input_object/updatechecksuitepreferencesinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatechecksuitepreferencesinput", - "/en/enterprise/v4/input_object/updatechecksuitepreferencesinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatechecksuitepreferencesinput", - "/enterprise/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", - "/en/enterprise/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", - "/enterprise/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", - "/en/enterprise/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", - "/enterprise/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", - "/en/enterprise/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", - "/enterprise/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", - "/enterprise/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", - "/enterprise/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", - "/enterprise/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", - "/enterprise/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", - "/enterprise/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", - "/enterprise/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", - "/enterprise/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", - "/en/enterprise/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", - "/enterprise/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", - "/en/enterprise/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", - "/enterprise/v4/input_object/updateenterpriseprofileinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseprofileinput", - "/en/enterprise/v4/input_object/updateenterpriseprofileinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseprofileinput", - "/enterprise/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", - "/en/enterprise/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", - "/enterprise/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", - "/en/enterprise/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", - "/enterprise/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", - "/en/enterprise/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", - "/enterprise/v4/input_object/updateipallowlistenabledsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateipallowlistenabledsettinginput", - "/en/enterprise/v4/input_object/updateipallowlistenabledsettinginput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateipallowlistenabledsettinginput", - "/enterprise/v4/input_object/updateipallowlistentryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateipallowlistentryinput", - "/en/enterprise/v4/input_object/updateipallowlistentryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateipallowlistentryinput", - "/enterprise/v4/input_object/updateissuecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateissuecommentinput", - "/en/enterprise/v4/input_object/updateissuecommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateissuecommentinput", - "/enterprise/v4/input_object/updateissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateissueinput", - "/en/enterprise/v4/input_object/updateissueinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateissueinput", - "/enterprise/v4/input_object/updatelabelinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatelabelinput", - "/en/enterprise/v4/input_object/updatelabelinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatelabelinput", - "/enterprise/v4/input_object/updateprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateprojectcardinput", - "/en/enterprise/v4/input_object/updateprojectcardinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateprojectcardinput", - "/enterprise/v4/input_object/updateprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateprojectcolumninput", - "/en/enterprise/v4/input_object/updateprojectcolumninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateprojectcolumninput", - "/enterprise/v4/input_object/updateprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateprojectinput", - "/en/enterprise/v4/input_object/updateprojectinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateprojectinput", - "/enterprise/v4/input_object/updatepullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestinput", - "/en/enterprise/v4/input_object/updatepullrequestinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestinput", - "/enterprise/v4/input_object/updatepullrequestreviewcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestreviewcommentinput", - "/en/enterprise/v4/input_object/updatepullrequestreviewcommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestreviewcommentinput", - "/enterprise/v4/input_object/updatepullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestreviewinput", - "/en/enterprise/v4/input_object/updatepullrequestreviewinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestreviewinput", - "/enterprise/v4/input_object/updaterefinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updaterefinput", - "/en/enterprise/v4/input_object/updaterefinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updaterefinput", - "/enterprise/v4/input_object/updaterefsinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updaterefsinput", - "/en/enterprise/v4/input_object/updaterefsinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updaterefsinput", - "/enterprise/v4/input_object/updaterepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updaterepositoryinput", - "/en/enterprise/v4/input_object/updaterepositoryinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updaterepositoryinput", - "/enterprise/v4/input_object/updatesubscriptioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatesubscriptioninput", - "/en/enterprise/v4/input_object/updatesubscriptioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatesubscriptioninput", - "/enterprise/v4/input_object/updateteamdiscussioncommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateteamdiscussioncommentinput", - "/en/enterprise/v4/input_object/updateteamdiscussioncommentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateteamdiscussioncommentinput", - "/enterprise/v4/input_object/updateteamdiscussioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateteamdiscussioninput", - "/en/enterprise/v4/input_object/updateteamdiscussioninput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateteamdiscussioninput", - "/enterprise/v4/input_object/updateteamreviewassignmentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateteamreviewassignmentinput", - "/en/enterprise/v4/input_object/updateteamreviewassignmentinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updateteamreviewassignmentinput", - "/enterprise/v4/input_object/updatetopicsinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatetopicsinput", - "/en/enterprise/v4/input_object/updatetopicsinput": "/en/enterprise-server@latest/graphql/reference/input-objects#updatetopicsinput", - "/enterprise/v4/input_object/userstatusorder": "/en/enterprise-server@latest/graphql/reference/input-objects#userstatusorder", - "/en/enterprise/v4/input_object/userstatusorder": "/en/enterprise-server@latest/graphql/reference/input-objects#userstatusorder", - "/enterprise/v4/interface/actor": "/en/enterprise-server@latest/graphql/reference/interfaces#actor", - "/en/enterprise/v4/interface/actor": "/en/enterprise-server@latest/graphql/reference/interfaces#actor", - "/enterprise/v4/interface/assignable": "/en/enterprise-server@latest/graphql/reference/interfaces#assignable", - "/en/enterprise/v4/interface/assignable": "/en/enterprise-server@latest/graphql/reference/interfaces#assignable", - "/enterprise/v4/interface/auditentry": "/en/enterprise-server@latest/graphql/reference/interfaces#auditentry", - "/en/enterprise/v4/interface/auditentry": "/en/enterprise-server@latest/graphql/reference/interfaces#auditentry", - "/enterprise/v4/interface/closable": "/en/enterprise-server@latest/graphql/reference/interfaces#closable", - "/en/enterprise/v4/interface/closable": "/en/enterprise-server@latest/graphql/reference/interfaces#closable", - "/enterprise/v4/interface/comment": "/en/enterprise-server@latest/graphql/reference/interfaces#comment", - "/en/enterprise/v4/interface/comment": "/en/enterprise-server@latest/graphql/reference/interfaces#comment", - "/enterprise/v4/interface/contribution": "/en/enterprise-server@latest/graphql/reference/interfaces#contribution", - "/en/enterprise/v4/interface/contribution": "/en/enterprise-server@latest/graphql/reference/interfaces#contribution", - "/enterprise/v4/interface/deletable": "/en/enterprise-server@latest/graphql/reference/interfaces#deletable", - "/en/enterprise/v4/interface/deletable": "/en/enterprise-server@latest/graphql/reference/interfaces#deletable", - "/enterprise/v4/interface/enterpriseauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#enterpriseauditentrydata", - "/en/enterprise/v4/interface/enterpriseauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#enterpriseauditentrydata", - "/enterprise/v4/interface/gitobject": "/en/enterprise-server@latest/graphql/reference/interfaces#gitobject", - "/en/enterprise/v4/interface/gitobject": "/en/enterprise-server@latest/graphql/reference/interfaces#gitobject", - "/enterprise/v4/interface/gitsignature": "/en/enterprise-server@latest/graphql/reference/interfaces#gitsignature", - "/en/enterprise/v4/interface/gitsignature": "/en/enterprise-server@latest/graphql/reference/interfaces#gitsignature", - "/enterprise/v4/interface/hovercardcontext": "/en/enterprise-server@latest/graphql/reference/interfaces#hovercardcontext", - "/en/enterprise/v4/interface/hovercardcontext": "/en/enterprise-server@latest/graphql/reference/interfaces#hovercardcontext", - "/enterprise/v4/interface/labelable": "/en/enterprise-server@latest/graphql/reference/interfaces#labelable", - "/en/enterprise/v4/interface/labelable": "/en/enterprise-server@latest/graphql/reference/interfaces#labelable", - "/enterprise/v4/interface/lockable": "/en/enterprise-server@latest/graphql/reference/interfaces#lockable", - "/en/enterprise/v4/interface/lockable": "/en/enterprise-server@latest/graphql/reference/interfaces#lockable", - "/enterprise/v4/interface/memberstatusable": "/en/enterprise-server@latest/graphql/reference/interfaces#memberstatusable", - "/en/enterprise/v4/interface/memberstatusable": "/en/enterprise-server@latest/graphql/reference/interfaces#memberstatusable", - "/enterprise/v4/interface/minimizable": "/en/enterprise-server@latest/graphql/reference/interfaces#minimizable", - "/en/enterprise/v4/interface/minimizable": "/en/enterprise-server@latest/graphql/reference/interfaces#minimizable", - "/enterprise/v4/interface/node": "/en/enterprise-server@latest/graphql/reference/interfaces#node", - "/en/enterprise/v4/interface/node": "/en/enterprise-server@latest/graphql/reference/interfaces#node", - "/enterprise/v4/interface/oauthapplicationauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#oauthapplicationauditentrydata", - "/en/enterprise/v4/interface/oauthapplicationauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#oauthapplicationauditentrydata", - "/enterprise/v4/interface/organizationauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#organizationauditentrydata", - "/en/enterprise/v4/interface/organizationauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#organizationauditentrydata", - "/enterprise/v4/interface/packageowner": "/en/enterprise-server@latest/graphql/reference/interfaces#packageowner", - "/en/enterprise/v4/interface/packageowner": "/en/enterprise-server@latest/graphql/reference/interfaces#packageowner", - "/enterprise/v4/interface/profileowner": "/en/enterprise-server@latest/graphql/reference/interfaces#profileowner", - "/en/enterprise/v4/interface/profileowner": "/en/enterprise-server@latest/graphql/reference/interfaces#profileowner", - "/enterprise/v4/interface/projectowner": "/en/enterprise-server@latest/graphql/reference/interfaces#projectowner", - "/en/enterprise/v4/interface/projectowner": "/en/enterprise-server@latest/graphql/reference/interfaces#projectowner", - "/enterprise/v4/interface/reactable": "/en/enterprise-server@latest/graphql/reference/interfaces#reactable", - "/en/enterprise/v4/interface/reactable": "/en/enterprise-server@latest/graphql/reference/interfaces#reactable", - "/enterprise/v4/interface/registrypackageowner": "/en/enterprise-server@latest/graphql/reference/interfaces#registrypackageowner", - "/en/enterprise/v4/interface/registrypackageowner": "/en/enterprise-server@latest/graphql/reference/interfaces#registrypackageowner", - "/enterprise/v4/interface/registrypackagesearch": "/en/enterprise-server@latest/graphql/reference/interfaces#registrypackagesearch", - "/en/enterprise/v4/interface/registrypackagesearch": "/en/enterprise-server@latest/graphql/reference/interfaces#registrypackagesearch", - "/enterprise/v4/interface/repositoryauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#repositoryauditentrydata", - "/en/enterprise/v4/interface/repositoryauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#repositoryauditentrydata", - "/enterprise/v4/interface/repositoryinfo": "/en/enterprise-server@latest/graphql/reference/interfaces#repositoryinfo", - "/en/enterprise/v4/interface/repositoryinfo": "/en/enterprise-server@latest/graphql/reference/interfaces#repositoryinfo", - "/enterprise/v4/interface/repositorynode": "/en/enterprise-server@latest/graphql/reference/interfaces#repositorynode", - "/en/enterprise/v4/interface/repositorynode": "/en/enterprise-server@latest/graphql/reference/interfaces#repositorynode", - "/enterprise/v4/interface/repositoryowner": "/en/enterprise-server@latest/graphql/reference/interfaces#repositoryowner", - "/en/enterprise/v4/interface/repositoryowner": "/en/enterprise-server@latest/graphql/reference/interfaces#repositoryowner", - "/enterprise/v4/interface/starrable": "/en/enterprise-server@latest/graphql/reference/interfaces#starrable", - "/en/enterprise/v4/interface/starrable": "/en/enterprise-server@latest/graphql/reference/interfaces#starrable", - "/enterprise/v4/interface/subscribable": "/en/enterprise-server@latest/graphql/reference/interfaces#subscribable", - "/en/enterprise/v4/interface/subscribable": "/en/enterprise-server@latest/graphql/reference/interfaces#subscribable", - "/enterprise/v4/interface/teamauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#teamauditentrydata", - "/en/enterprise/v4/interface/teamauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#teamauditentrydata", - "/enterprise/v4/interface/topicauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#topicauditentrydata", - "/en/enterprise/v4/interface/topicauditentrydata": "/en/enterprise-server@latest/graphql/reference/interfaces#topicauditentrydata", - "/enterprise/v4/interface/uniformresourcelocatable": "/en/enterprise-server@latest/graphql/reference/interfaces#uniformresourcelocatable", - "/en/enterprise/v4/interface/uniformresourcelocatable": "/en/enterprise-server@latest/graphql/reference/interfaces#uniformresourcelocatable", - "/enterprise/v4/interface/updatable": "/en/enterprise-server@latest/graphql/reference/interfaces#updatable", - "/en/enterprise/v4/interface/updatable": "/en/enterprise-server@latest/graphql/reference/interfaces#updatable", - "/enterprise/v4/interface/updatablecomment": "/en/enterprise-server@latest/graphql/reference/interfaces#updatablecomment", - "/en/enterprise/v4/interface/updatablecomment": "/en/enterprise-server@latest/graphql/reference/interfaces#updatablecomment", - "/enterprise/v4/mutation/addassigneestoassignable": "/en/enterprise-server@latest/graphql/reference/mutations#addassigneestoassignable", - "/en/enterprise/v4/mutation/addassigneestoassignable": "/en/enterprise-server@latest/graphql/reference/mutations#addassigneestoassignable", - "/enterprise/v4/mutation/addcomment": "/en/enterprise-server@latest/graphql/reference/mutations#addcomment", - "/en/enterprise/v4/mutation/addcomment": "/en/enterprise-server@latest/graphql/reference/mutations#addcomment", - "/enterprise/v4/mutation/addenterpriseadmin": "/en/enterprise-server@latest/graphql/reference/mutations#addenterpriseadmin", - "/en/enterprise/v4/mutation/addenterpriseadmin": "/en/enterprise-server@latest/graphql/reference/mutations#addenterpriseadmin", - "/enterprise/v4/mutation/addlabelstolabelable": "/en/enterprise-server@latest/graphql/reference/mutations#addlabelstolabelable", - "/en/enterprise/v4/mutation/addlabelstolabelable": "/en/enterprise-server@latest/graphql/reference/mutations#addlabelstolabelable", - "/enterprise/v4/mutation/addprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#addprojectcard", - "/en/enterprise/v4/mutation/addprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#addprojectcard", - "/enterprise/v4/mutation/addprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#addprojectcolumn", - "/en/enterprise/v4/mutation/addprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#addprojectcolumn", - "/enterprise/v4/mutation/addpullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#addpullrequestreview", - "/en/enterprise/v4/mutation/addpullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#addpullrequestreview", - "/enterprise/v4/mutation/addpullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/mutations#addpullrequestreviewcomment", - "/en/enterprise/v4/mutation/addpullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/mutations#addpullrequestreviewcomment", - "/enterprise/v4/mutation/addpullrequestreviewthread": "/en/enterprise-server@latest/graphql/reference/mutations#addpullrequestreviewthread", - "/en/enterprise/v4/mutation/addpullrequestreviewthread": "/en/enterprise-server@latest/graphql/reference/mutations#addpullrequestreviewthread", - "/enterprise/v4/mutation/addreaction": "/en/enterprise-server@latest/graphql/reference/mutations#addreaction", - "/en/enterprise/v4/mutation/addreaction": "/en/enterprise-server@latest/graphql/reference/mutations#addreaction", - "/enterprise/v4/mutation/addstar": "/en/enterprise-server@latest/graphql/reference/mutations#addstar", - "/en/enterprise/v4/mutation/addstar": "/en/enterprise-server@latest/graphql/reference/mutations#addstar", - "/enterprise/v4/mutation/archiverepository": "/en/enterprise-server@latest/graphql/reference/mutations#archiverepository", - "/en/enterprise/v4/mutation/archiverepository": "/en/enterprise-server@latest/graphql/reference/mutations#archiverepository", - "/enterprise/v4/mutation/changeuserstatus": "/en/enterprise-server@latest/graphql/reference/mutations#changeuserstatus", - "/en/enterprise/v4/mutation/changeuserstatus": "/en/enterprise-server@latest/graphql/reference/mutations#changeuserstatus", - "/enterprise/v4/mutation/clearlabelsfromlabelable": "/en/enterprise-server@latest/graphql/reference/mutations#clearlabelsfromlabelable", - "/en/enterprise/v4/mutation/clearlabelsfromlabelable": "/en/enterprise-server@latest/graphql/reference/mutations#clearlabelsfromlabelable", - "/enterprise/v4/mutation/cloneproject": "/en/enterprise-server@latest/graphql/reference/mutations#cloneproject", - "/en/enterprise/v4/mutation/cloneproject": "/en/enterprise-server@latest/graphql/reference/mutations#cloneproject", - "/enterprise/v4/mutation/clonetemplaterepository": "/en/enterprise-server@latest/graphql/reference/mutations#clonetemplaterepository", - "/en/enterprise/v4/mutation/clonetemplaterepository": "/en/enterprise-server@latest/graphql/reference/mutations#clonetemplaterepository", - "/enterprise/v4/mutation/closeissue": "/en/enterprise-server@latest/graphql/reference/mutations#closeissue", - "/en/enterprise/v4/mutation/closeissue": "/en/enterprise-server@latest/graphql/reference/mutations#closeissue", - "/enterprise/v4/mutation/closepullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#closepullrequest", - "/en/enterprise/v4/mutation/closepullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#closepullrequest", - "/enterprise/v4/mutation/convertprojectcardnotetoissue": "/en/enterprise-server@latest/graphql/reference/mutations#convertprojectcardnotetoissue", - "/en/enterprise/v4/mutation/convertprojectcardnotetoissue": "/en/enterprise-server@latest/graphql/reference/mutations#convertprojectcardnotetoissue", - "/enterprise/v4/mutation/createbranchprotectionrule": "/en/enterprise-server@latest/graphql/reference/mutations#createbranchprotectionrule", - "/en/enterprise/v4/mutation/createbranchprotectionrule": "/en/enterprise-server@latest/graphql/reference/mutations#createbranchprotectionrule", - "/enterprise/v4/mutation/createcheckrun": "/en/enterprise-server@latest/graphql/reference/mutations#createcheckrun", - "/en/enterprise/v4/mutation/createcheckrun": "/en/enterprise-server@latest/graphql/reference/mutations#createcheckrun", - "/enterprise/v4/mutation/createchecksuite": "/en/enterprise-server@latest/graphql/reference/mutations#createchecksuite", - "/en/enterprise/v4/mutation/createchecksuite": "/en/enterprise-server@latest/graphql/reference/mutations#createchecksuite", - "/enterprise/v4/mutation/createcontentattachment": "/en/enterprise-server@latest/graphql/reference/mutations#createcontentattachment", - "/en/enterprise/v4/mutation/createcontentattachment": "/en/enterprise-server@latest/graphql/reference/mutations#createcontentattachment", - "/enterprise/v4/mutation/createdeployment": "/en/enterprise-server@latest/graphql/reference/mutations#createdeployment", - "/en/enterprise/v4/mutation/createdeployment": "/en/enterprise-server@latest/graphql/reference/mutations#createdeployment", - "/enterprise/v4/mutation/createdeploymentstatus": "/en/enterprise-server@latest/graphql/reference/mutations#createdeploymentstatus", - "/en/enterprise/v4/mutation/createdeploymentstatus": "/en/enterprise-server@latest/graphql/reference/mutations#createdeploymentstatus", - "/enterprise/v4/mutation/createipallowlistentry": "/en/enterprise-server@latest/graphql/reference/mutations#createipallowlistentry", - "/en/enterprise/v4/mutation/createipallowlistentry": "/en/enterprise-server@latest/graphql/reference/mutations#createipallowlistentry", - "/enterprise/v4/mutation/createissue": "/en/enterprise-server@latest/graphql/reference/mutations#createissue", - "/en/enterprise/v4/mutation/createissue": "/en/enterprise-server@latest/graphql/reference/mutations#createissue", - "/enterprise/v4/mutation/createlabel": "/en/enterprise-server@latest/graphql/reference/mutations#createlabel", - "/en/enterprise/v4/mutation/createlabel": "/en/enterprise-server@latest/graphql/reference/mutations#createlabel", - "/enterprise/v4/mutation/createproject": "/en/enterprise-server@latest/graphql/reference/mutations#createproject", - "/en/enterprise/v4/mutation/createproject": "/en/enterprise-server@latest/graphql/reference/mutations#createproject", - "/enterprise/v4/mutation/createpullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#createpullrequest", - "/en/enterprise/v4/mutation/createpullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#createpullrequest", - "/enterprise/v4/mutation/createref": "/en/enterprise-server@latest/graphql/reference/mutations#createref", - "/en/enterprise/v4/mutation/createref": "/en/enterprise-server@latest/graphql/reference/mutations#createref", - "/enterprise/v4/mutation/createrepository": "/en/enterprise-server@latest/graphql/reference/mutations#createrepository", - "/en/enterprise/v4/mutation/createrepository": "/en/enterprise-server@latest/graphql/reference/mutations#createrepository", - "/enterprise/v4/mutation/createteamdiscussion": "/en/enterprise-server@latest/graphql/reference/mutations#createteamdiscussion", - "/en/enterprise/v4/mutation/createteamdiscussion": "/en/enterprise-server@latest/graphql/reference/mutations#createteamdiscussion", - "/enterprise/v4/mutation/createteamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/mutations#createteamdiscussioncomment", - "/en/enterprise/v4/mutation/createteamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/mutations#createteamdiscussioncomment", - "/enterprise/v4/mutation/deletebranchprotectionrule": "/en/enterprise-server@latest/graphql/reference/mutations#deletebranchprotectionrule", - "/en/enterprise/v4/mutation/deletebranchprotectionrule": "/en/enterprise-server@latest/graphql/reference/mutations#deletebranchprotectionrule", - "/enterprise/v4/mutation/deletedeployment": "/en/enterprise-server@latest/graphql/reference/mutations#deletedeployment", - "/en/enterprise/v4/mutation/deletedeployment": "/en/enterprise-server@latest/graphql/reference/mutations#deletedeployment", - "/enterprise/v4/mutation/deleteipallowlistentry": "/en/enterprise-server@latest/graphql/reference/mutations#deleteipallowlistentry", - "/en/enterprise/v4/mutation/deleteipallowlistentry": "/en/enterprise-server@latest/graphql/reference/mutations#deleteipallowlistentry", - "/enterprise/v4/mutation/deleteissue": "/en/enterprise-server@latest/graphql/reference/mutations#deleteissue", - "/en/enterprise/v4/mutation/deleteissue": "/en/enterprise-server@latest/graphql/reference/mutations#deleteissue", - "/enterprise/v4/mutation/deleteissuecomment": "/en/enterprise-server@latest/graphql/reference/mutations#deleteissuecomment", - "/en/enterprise/v4/mutation/deleteissuecomment": "/en/enterprise-server@latest/graphql/reference/mutations#deleteissuecomment", - "/enterprise/v4/mutation/deletelabel": "/en/enterprise-server@latest/graphql/reference/mutations#deletelabel", - "/en/enterprise/v4/mutation/deletelabel": "/en/enterprise-server@latest/graphql/reference/mutations#deletelabel", - "/enterprise/v4/mutation/deletepackageversion": "/en/enterprise-server@latest/graphql/reference/mutations#deletepackageversion", - "/en/enterprise/v4/mutation/deletepackageversion": "/en/enterprise-server@latest/graphql/reference/mutations#deletepackageversion", - "/enterprise/v4/mutation/deleteproject": "/en/enterprise-server@latest/graphql/reference/mutations#deleteproject", - "/en/enterprise/v4/mutation/deleteproject": "/en/enterprise-server@latest/graphql/reference/mutations#deleteproject", - "/enterprise/v4/mutation/deleteprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#deleteprojectcard", - "/en/enterprise/v4/mutation/deleteprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#deleteprojectcard", - "/enterprise/v4/mutation/deleteprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#deleteprojectcolumn", - "/en/enterprise/v4/mutation/deleteprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#deleteprojectcolumn", - "/enterprise/v4/mutation/deletepullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#deletepullrequestreview", - "/en/enterprise/v4/mutation/deletepullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#deletepullrequestreview", - "/enterprise/v4/mutation/deletepullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/mutations#deletepullrequestreviewcomment", - "/en/enterprise/v4/mutation/deletepullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/mutations#deletepullrequestreviewcomment", - "/enterprise/v4/mutation/deleteref": "/en/enterprise-server@latest/graphql/reference/mutations#deleteref", - "/en/enterprise/v4/mutation/deleteref": "/en/enterprise-server@latest/graphql/reference/mutations#deleteref", - "/enterprise/v4/mutation/deleteteamdiscussion": "/en/enterprise-server@latest/graphql/reference/mutations#deleteteamdiscussion", - "/en/enterprise/v4/mutation/deleteteamdiscussion": "/en/enterprise-server@latest/graphql/reference/mutations#deleteteamdiscussion", - "/enterprise/v4/mutation/deleteteamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/mutations#deleteteamdiscussioncomment", - "/en/enterprise/v4/mutation/deleteteamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/mutations#deleteteamdiscussioncomment", - "/enterprise/v4/mutation/dismisspullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#dismisspullrequestreview", - "/en/enterprise/v4/mutation/dismisspullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#dismisspullrequestreview", - "/enterprise/v4/mutation/followuser": "/en/enterprise-server@latest/graphql/reference/mutations#followuser", - "/en/enterprise/v4/mutation/followuser": "/en/enterprise-server@latest/graphql/reference/mutations#followuser", - "/enterprise/v4/mutation/importproject": "/en/enterprise-server@latest/graphql/reference/mutations#importproject", - "/en/enterprise/v4/mutation/importproject": "/en/enterprise-server@latest/graphql/reference/mutations#importproject", - "/enterprise/v4/mutation/linkrepositorytoproject": "/en/enterprise-server@latest/graphql/reference/mutations#linkrepositorytoproject", - "/en/enterprise/v4/mutation/linkrepositorytoproject": "/en/enterprise-server@latest/graphql/reference/mutations#linkrepositorytoproject", - "/enterprise/v4/mutation/locklockable": "/en/enterprise-server@latest/graphql/reference/mutations#locklockable", - "/en/enterprise/v4/mutation/locklockable": "/en/enterprise-server@latest/graphql/reference/mutations#locklockable", - "/enterprise/v4/mutation/markpullrequestreadyforreview": "/en/enterprise-server@latest/graphql/reference/mutations#markpullrequestreadyforreview", - "/en/enterprise/v4/mutation/markpullrequestreadyforreview": "/en/enterprise-server@latest/graphql/reference/mutations#markpullrequestreadyforreview", - "/enterprise/v4/mutation/mergebranch": "/en/enterprise-server@latest/graphql/reference/mutations#mergebranch", - "/en/enterprise/v4/mutation/mergebranch": "/en/enterprise-server@latest/graphql/reference/mutations#mergebranch", - "/enterprise/v4/mutation/mergepullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#mergepullrequest", - "/en/enterprise/v4/mutation/mergepullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#mergepullrequest", - "/enterprise/v4/mutation/minimizecomment": "/en/enterprise-server@latest/graphql/reference/mutations#minimizecomment", - "/en/enterprise/v4/mutation/minimizecomment": "/en/enterprise-server@latest/graphql/reference/mutations#minimizecomment", - "/enterprise/v4/mutation/moveprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#moveprojectcard", - "/en/enterprise/v4/mutation/moveprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#moveprojectcard", - "/enterprise/v4/mutation/moveprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#moveprojectcolumn", - "/en/enterprise/v4/mutation/moveprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#moveprojectcolumn", - "/enterprise/v4/mutation/pinissue": "/en/enterprise-server@latest/graphql/reference/mutations#pinissue", - "/en/enterprise/v4/mutation/pinissue": "/en/enterprise-server@latest/graphql/reference/mutations#pinissue", - "/enterprise/v4/mutation/removeassigneesfromassignable": "/en/enterprise-server@latest/graphql/reference/mutations#removeassigneesfromassignable", - "/en/enterprise/v4/mutation/removeassigneesfromassignable": "/en/enterprise-server@latest/graphql/reference/mutations#removeassigneesfromassignable", - "/enterprise/v4/mutation/removeenterpriseadmin": "/en/enterprise-server@latest/graphql/reference/mutations#removeenterpriseadmin", - "/en/enterprise/v4/mutation/removeenterpriseadmin": "/en/enterprise-server@latest/graphql/reference/mutations#removeenterpriseadmin", - "/enterprise/v4/mutation/removelabelsfromlabelable": "/en/enterprise-server@latest/graphql/reference/mutations#removelabelsfromlabelable", - "/en/enterprise/v4/mutation/removelabelsfromlabelable": "/en/enterprise-server@latest/graphql/reference/mutations#removelabelsfromlabelable", - "/enterprise/v4/mutation/removeoutsidecollaborator": "/en/enterprise-server@latest/graphql/reference/mutations#removeoutsidecollaborator", - "/en/enterprise/v4/mutation/removeoutsidecollaborator": "/en/enterprise-server@latest/graphql/reference/mutations#removeoutsidecollaborator", - "/enterprise/v4/mutation/removereaction": "/en/enterprise-server@latest/graphql/reference/mutations#removereaction", - "/en/enterprise/v4/mutation/removereaction": "/en/enterprise-server@latest/graphql/reference/mutations#removereaction", - "/enterprise/v4/mutation/removestar": "/en/enterprise-server@latest/graphql/reference/mutations#removestar", - "/en/enterprise/v4/mutation/removestar": "/en/enterprise-server@latest/graphql/reference/mutations#removestar", - "/enterprise/v4/mutation/reopenissue": "/en/enterprise-server@latest/graphql/reference/mutations#reopenissue", - "/en/enterprise/v4/mutation/reopenissue": "/en/enterprise-server@latest/graphql/reference/mutations#reopenissue", - "/enterprise/v4/mutation/reopenpullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#reopenpullrequest", - "/en/enterprise/v4/mutation/reopenpullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#reopenpullrequest", - "/enterprise/v4/mutation/requestreviews": "/en/enterprise-server@latest/graphql/reference/mutations#requestreviews", - "/en/enterprise/v4/mutation/requestreviews": "/en/enterprise-server@latest/graphql/reference/mutations#requestreviews", - "/enterprise/v4/mutation/rerequestchecksuite": "/en/enterprise-server@latest/graphql/reference/mutations#rerequestchecksuite", - "/en/enterprise/v4/mutation/rerequestchecksuite": "/en/enterprise-server@latest/graphql/reference/mutations#rerequestchecksuite", - "/enterprise/v4/mutation/resolvereviewthread": "/en/enterprise-server@latest/graphql/reference/mutations#resolvereviewthread", - "/en/enterprise/v4/mutation/resolvereviewthread": "/en/enterprise-server@latest/graphql/reference/mutations#resolvereviewthread", - "/enterprise/v4/mutation/submitpullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#submitpullrequestreview", - "/en/enterprise/v4/mutation/submitpullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#submitpullrequestreview", - "/enterprise/v4/mutation/transferissue": "/en/enterprise-server@latest/graphql/reference/mutations#transferissue", - "/en/enterprise/v4/mutation/transferissue": "/en/enterprise-server@latest/graphql/reference/mutations#transferissue", - "/enterprise/v4/mutation/unarchiverepository": "/en/enterprise-server@latest/graphql/reference/mutations#unarchiverepository", - "/en/enterprise/v4/mutation/unarchiverepository": "/en/enterprise-server@latest/graphql/reference/mutations#unarchiverepository", - "/enterprise/v4/mutation/unfollowuser": "/en/enterprise-server@latest/graphql/reference/mutations#unfollowuser", - "/en/enterprise/v4/mutation/unfollowuser": "/en/enterprise-server@latest/graphql/reference/mutations#unfollowuser", - "/enterprise/v4/mutation/unlinkrepositoryfromproject": "/en/enterprise-server@latest/graphql/reference/mutations#unlinkrepositoryfromproject", - "/en/enterprise/v4/mutation/unlinkrepositoryfromproject": "/en/enterprise-server@latest/graphql/reference/mutations#unlinkrepositoryfromproject", - "/enterprise/v4/mutation/unlocklockable": "/en/enterprise-server@latest/graphql/reference/mutations#unlocklockable", - "/en/enterprise/v4/mutation/unlocklockable": "/en/enterprise-server@latest/graphql/reference/mutations#unlocklockable", - "/enterprise/v4/mutation/unmarkissueasduplicate": "/en/enterprise-server@latest/graphql/reference/mutations#unmarkissueasduplicate", - "/en/enterprise/v4/mutation/unmarkissueasduplicate": "/en/enterprise-server@latest/graphql/reference/mutations#unmarkissueasduplicate", - "/enterprise/v4/mutation/unminimizecomment": "/en/enterprise-server@latest/graphql/reference/mutations#unminimizecomment", - "/en/enterprise/v4/mutation/unminimizecomment": "/en/enterprise-server@latest/graphql/reference/mutations#unminimizecomment", - "/enterprise/v4/mutation/unpinissue": "/en/enterprise-server@latest/graphql/reference/mutations#unpinissue", - "/en/enterprise/v4/mutation/unpinissue": "/en/enterprise-server@latest/graphql/reference/mutations#unpinissue", - "/enterprise/v4/mutation/unresolvereviewthread": "/en/enterprise-server@latest/graphql/reference/mutations#unresolvereviewthread", - "/en/enterprise/v4/mutation/unresolvereviewthread": "/en/enterprise-server@latest/graphql/reference/mutations#unresolvereviewthread", - "/enterprise/v4/mutation/updatebranchprotectionrule": "/en/enterprise-server@latest/graphql/reference/mutations#updatebranchprotectionrule", - "/en/enterprise/v4/mutation/updatebranchprotectionrule": "/en/enterprise-server@latest/graphql/reference/mutations#updatebranchprotectionrule", - "/enterprise/v4/mutation/updatecheckrun": "/en/enterprise-server@latest/graphql/reference/mutations#updatecheckrun", - "/en/enterprise/v4/mutation/updatecheckrun": "/en/enterprise-server@latest/graphql/reference/mutations#updatecheckrun", - "/enterprise/v4/mutation/updatechecksuitepreferences": "/en/enterprise-server@latest/graphql/reference/mutations#updatechecksuitepreferences", - "/en/enterprise/v4/mutation/updatechecksuitepreferences": "/en/enterprise-server@latest/graphql/reference/mutations#updatechecksuitepreferences", - "/enterprise/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", - "/en/enterprise/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", - "/enterprise/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", - "/en/enterprise/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", - "/enterprise/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", - "/en/enterprise/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", - "/enterprise/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", - "/en/enterprise/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", - "/enterprise/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", - "/en/enterprise/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", - "/enterprise/v4/mutation/updateenterprisememberscandeleteissuessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", - "/en/enterprise/v4/mutation/updateenterprisememberscandeleteissuessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", - "/enterprise/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", - "/en/enterprise/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", - "/enterprise/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", - "/en/enterprise/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", - "/enterprise/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", - "/en/enterprise/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", - "/enterprise/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", - "/en/enterprise/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", - "/enterprise/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", - "/en/enterprise/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", - "/enterprise/v4/mutation/updateenterpriseorganizationprojectssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", - "/en/enterprise/v4/mutation/updateenterpriseorganizationprojectssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", - "/enterprise/v4/mutation/updateenterpriseprofile": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseprofile", - "/en/enterprise/v4/mutation/updateenterpriseprofile": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseprofile", - "/enterprise/v4/mutation/updateenterpriserepositoryprojectssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", - "/en/enterprise/v4/mutation/updateenterpriserepositoryprojectssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", - "/enterprise/v4/mutation/updateenterpriseteamdiscussionssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", - "/en/enterprise/v4/mutation/updateenterpriseteamdiscussionssetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", - "/enterprise/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", - "/en/enterprise/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", - "/enterprise/v4/mutation/updateipallowlistenabledsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateipallowlistenabledsetting", - "/en/enterprise/v4/mutation/updateipallowlistenabledsetting": "/en/enterprise-server@latest/graphql/reference/mutations#updateipallowlistenabledsetting", - "/enterprise/v4/mutation/updateipallowlistentry": "/en/enterprise-server@latest/graphql/reference/mutations#updateipallowlistentry", - "/en/enterprise/v4/mutation/updateipallowlistentry": "/en/enterprise-server@latest/graphql/reference/mutations#updateipallowlistentry", - "/enterprise/v4/mutation/updateissue": "/en/enterprise-server@latest/graphql/reference/mutations#updateissue", - "/en/enterprise/v4/mutation/updateissue": "/en/enterprise-server@latest/graphql/reference/mutations#updateissue", - "/enterprise/v4/mutation/updateissuecomment": "/en/enterprise-server@latest/graphql/reference/mutations#updateissuecomment", - "/en/enterprise/v4/mutation/updateissuecomment": "/en/enterprise-server@latest/graphql/reference/mutations#updateissuecomment", - "/enterprise/v4/mutation/updatelabel": "/en/enterprise-server@latest/graphql/reference/mutations#updatelabel", - "/en/enterprise/v4/mutation/updatelabel": "/en/enterprise-server@latest/graphql/reference/mutations#updatelabel", - "/enterprise/v4/mutation/updateproject": "/en/enterprise-server@latest/graphql/reference/mutations#updateproject", - "/en/enterprise/v4/mutation/updateproject": "/en/enterprise-server@latest/graphql/reference/mutations#updateproject", - "/enterprise/v4/mutation/updateprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#updateprojectcard", - "/en/enterprise/v4/mutation/updateprojectcard": "/en/enterprise-server@latest/graphql/reference/mutations#updateprojectcard", - "/enterprise/v4/mutation/updateprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#updateprojectcolumn", - "/en/enterprise/v4/mutation/updateprojectcolumn": "/en/enterprise-server@latest/graphql/reference/mutations#updateprojectcolumn", - "/enterprise/v4/mutation/updatepullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#updatepullrequest", - "/en/enterprise/v4/mutation/updatepullrequest": "/en/enterprise-server@latest/graphql/reference/mutations#updatepullrequest", - "/enterprise/v4/mutation/updatepullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#updatepullrequestreview", - "/en/enterprise/v4/mutation/updatepullrequestreview": "/en/enterprise-server@latest/graphql/reference/mutations#updatepullrequestreview", - "/enterprise/v4/mutation/updatepullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/mutations#updatepullrequestreviewcomment", - "/en/enterprise/v4/mutation/updatepullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/mutations#updatepullrequestreviewcomment", - "/enterprise/v4/mutation/updateref": "/en/enterprise-server@latest/graphql/reference/mutations#updateref", - "/en/enterprise/v4/mutation/updateref": "/en/enterprise-server@latest/graphql/reference/mutations#updateref", - "/enterprise/v4/mutation/updaterefs": "/en/enterprise-server@latest/graphql/reference/mutations#updaterefs", - "/en/enterprise/v4/mutation/updaterefs": "/en/enterprise-server@latest/graphql/reference/mutations#updaterefs", - "/enterprise/v4/mutation/updaterepository": "/en/enterprise-server@latest/graphql/reference/mutations#updaterepository", - "/en/enterprise/v4/mutation/updaterepository": "/en/enterprise-server@latest/graphql/reference/mutations#updaterepository", - "/enterprise/v4/mutation/updatesubscription": "/en/enterprise-server@latest/graphql/reference/mutations#updatesubscription", - "/en/enterprise/v4/mutation/updatesubscription": "/en/enterprise-server@latest/graphql/reference/mutations#updatesubscription", - "/enterprise/v4/mutation/updateteamdiscussion": "/en/enterprise-server@latest/graphql/reference/mutations#updateteamdiscussion", - "/en/enterprise/v4/mutation/updateteamdiscussion": "/en/enterprise-server@latest/graphql/reference/mutations#updateteamdiscussion", - "/enterprise/v4/mutation/updateteamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/mutations#updateteamdiscussioncomment", - "/en/enterprise/v4/mutation/updateteamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/mutations#updateteamdiscussioncomment", - "/enterprise/v4/mutation/updateteamreviewassignment": "/en/enterprise-server@latest/graphql/reference/mutations#updateteamreviewassignment", - "/en/enterprise/v4/mutation/updateteamreviewassignment": "/en/enterprise-server@latest/graphql/reference/mutations#updateteamreviewassignment", - "/enterprise/v4/mutation/updatetopics": "/en/enterprise-server@latest/graphql/reference/mutations#updatetopics", - "/en/enterprise/v4/mutation/updatetopics": "/en/enterprise-server@latest/graphql/reference/mutations#updatetopics", - "/enterprise/v4/object/__directive": "/en/enterprise-server@latest/graphql/reference/objects#__directive", - "/en/enterprise/v4/object/__directive": "/en/enterprise-server@latest/graphql/reference/objects#__directive", - "/enterprise/v4/object/__enumvalue": "/en/enterprise-server@latest/graphql/reference/objects#__enumvalue", - "/en/enterprise/v4/object/__enumvalue": "/en/enterprise-server@latest/graphql/reference/objects#__enumvalue", - "/enterprise/v4/object/__field": "/en/enterprise-server@latest/graphql/reference/objects#__field", - "/en/enterprise/v4/object/__field": "/en/enterprise-server@latest/graphql/reference/objects#__field", - "/enterprise/v4/object/__inputvalue": "/en/enterprise-server@latest/graphql/reference/objects#__inputvalue", - "/en/enterprise/v4/object/__inputvalue": "/en/enterprise-server@latest/graphql/reference/objects#__inputvalue", - "/enterprise/v4/object/__schema": "/en/enterprise-server@latest/graphql/reference/objects#__schema", - "/en/enterprise/v4/object/__schema": "/en/enterprise-server@latest/graphql/reference/objects#__schema", - "/enterprise/v4/object/__type": "/en/enterprise-server@latest/graphql/reference/objects#__type", - "/en/enterprise/v4/object/__type": "/en/enterprise-server@latest/graphql/reference/objects#__type", - "/enterprise/v4/object/actorlocation": "/en/enterprise-server@latest/graphql/reference/objects#actorlocation", - "/en/enterprise/v4/object/actorlocation": "/en/enterprise-server@latest/graphql/reference/objects#actorlocation", - "/enterprise/v4/object/addassigneestoassignablepayload": "/en/enterprise-server@latest/graphql/reference/objects#addassigneestoassignablepayload", - "/en/enterprise/v4/object/addassigneestoassignablepayload": "/en/enterprise-server@latest/graphql/reference/objects#addassigneestoassignablepayload", - "/enterprise/v4/object/addcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#addcommentpayload", - "/en/enterprise/v4/object/addcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#addcommentpayload", - "/enterprise/v4/object/addedtoprojectevent": "/en/enterprise-server@latest/graphql/reference/objects#addedtoprojectevent", - "/en/enterprise/v4/object/addedtoprojectevent": "/en/enterprise-server@latest/graphql/reference/objects#addedtoprojectevent", - "/enterprise/v4/object/addenterpriseadminpayload": "/en/enterprise-server@latest/graphql/reference/objects#addenterpriseadminpayload", - "/en/enterprise/v4/object/addenterpriseadminpayload": "/en/enterprise-server@latest/graphql/reference/objects#addenterpriseadminpayload", - "/enterprise/v4/object/addlabelstolabelablepayload": "/en/enterprise-server@latest/graphql/reference/objects#addlabelstolabelablepayload", - "/en/enterprise/v4/object/addlabelstolabelablepayload": "/en/enterprise-server@latest/graphql/reference/objects#addlabelstolabelablepayload", - "/enterprise/v4/object/addprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#addprojectcardpayload", - "/en/enterprise/v4/object/addprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#addprojectcardpayload", - "/enterprise/v4/object/addprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#addprojectcolumnpayload", - "/en/enterprise/v4/object/addprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#addprojectcolumnpayload", - "/enterprise/v4/object/addpullrequestreviewcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewcommentpayload", - "/en/enterprise/v4/object/addpullrequestreviewcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewcommentpayload", - "/enterprise/v4/object/addpullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewpayload", - "/en/enterprise/v4/object/addpullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewpayload", - "/enterprise/v4/object/addpullrequestreviewthreadpayload": "/en/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewthreadpayload", - "/en/enterprise/v4/object/addpullrequestreviewthreadpayload": "/en/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewthreadpayload", - "/enterprise/v4/object/addreactionpayload": "/en/enterprise-server@latest/graphql/reference/objects#addreactionpayload", - "/en/enterprise/v4/object/addreactionpayload": "/en/enterprise-server@latest/graphql/reference/objects#addreactionpayload", - "/enterprise/v4/object/addstarpayload": "/en/enterprise-server@latest/graphql/reference/objects#addstarpayload", - "/en/enterprise/v4/object/addstarpayload": "/en/enterprise-server@latest/graphql/reference/objects#addstarpayload", - "/enterprise/v4/object/app": "/en/enterprise-server@latest/graphql/reference/objects#app", - "/en/enterprise/v4/object/app": "/en/enterprise-server@latest/graphql/reference/objects#app", - "/enterprise/v4/object/archiverepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#archiverepositorypayload", - "/en/enterprise/v4/object/archiverepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#archiverepositorypayload", - "/enterprise/v4/object/assignedevent": "/en/enterprise-server@latest/graphql/reference/objects#assignedevent", - "/en/enterprise/v4/object/assignedevent": "/en/enterprise-server@latest/graphql/reference/objects#assignedevent", - "/enterprise/v4/object/baserefchangedevent": "/en/enterprise-server@latest/graphql/reference/objects#baserefchangedevent", - "/en/enterprise/v4/object/baserefchangedevent": "/en/enterprise-server@latest/graphql/reference/objects#baserefchangedevent", - "/enterprise/v4/object/baserefforcepushedevent": "/en/enterprise-server@latest/graphql/reference/objects#baserefforcepushedevent", - "/en/enterprise/v4/object/baserefforcepushedevent": "/en/enterprise-server@latest/graphql/reference/objects#baserefforcepushedevent", - "/enterprise/v4/object/blame": "/en/enterprise-server@latest/graphql/reference/objects#blame", - "/en/enterprise/v4/object/blame": "/en/enterprise-server@latest/graphql/reference/objects#blame", - "/enterprise/v4/object/blamerange": "/en/enterprise-server@latest/graphql/reference/objects#blamerange", - "/en/enterprise/v4/object/blamerange": "/en/enterprise-server@latest/graphql/reference/objects#blamerange", - "/enterprise/v4/object/blob": "/en/enterprise-server@latest/graphql/reference/objects#blob", - "/en/enterprise/v4/object/blob": "/en/enterprise-server@latest/graphql/reference/objects#blob", - "/enterprise/v4/object/bot": "/en/enterprise-server@latest/graphql/reference/objects#bot", - "/en/enterprise/v4/object/bot": "/en/enterprise-server@latest/graphql/reference/objects#bot", - "/enterprise/v4/object/branchprotectionrule": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionrule", - "/en/enterprise/v4/object/branchprotectionrule": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionrule", - "/enterprise/v4/object/branchprotectionruleconflict": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflict", - "/en/enterprise/v4/object/branchprotectionruleconflict": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflict", - "/enterprise/v4/object/branchprotectionruleconflictconnection": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflictconnection", - "/en/enterprise/v4/object/branchprotectionruleconflictconnection": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflictconnection", - "/enterprise/v4/object/branchprotectionruleconflictedge": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflictedge", - "/en/enterprise/v4/object/branchprotectionruleconflictedge": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflictedge", - "/enterprise/v4/object/branchprotectionruleconnection": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconnection", - "/en/enterprise/v4/object/branchprotectionruleconnection": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconnection", - "/enterprise/v4/object/branchprotectionruleedge": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleedge", - "/en/enterprise/v4/object/branchprotectionruleedge": "/en/enterprise-server@latest/graphql/reference/objects#branchprotectionruleedge", - "/enterprise/v4/object/changeuserstatuspayload": "/en/enterprise-server@latest/graphql/reference/objects#changeuserstatuspayload", - "/en/enterprise/v4/object/changeuserstatuspayload": "/en/enterprise-server@latest/graphql/reference/objects#changeuserstatuspayload", - "/enterprise/v4/object/checkannotation": "/en/enterprise-server@latest/graphql/reference/objects#checkannotation", - "/en/enterprise/v4/object/checkannotation": "/en/enterprise-server@latest/graphql/reference/objects#checkannotation", - "/enterprise/v4/object/checkannotationconnection": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationconnection", - "/en/enterprise/v4/object/checkannotationconnection": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationconnection", - "/enterprise/v4/object/checkannotationedge": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationedge", - "/en/enterprise/v4/object/checkannotationedge": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationedge", - "/enterprise/v4/object/checkannotationposition": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationposition", - "/en/enterprise/v4/object/checkannotationposition": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationposition", - "/enterprise/v4/object/checkannotationspan": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationspan", - "/en/enterprise/v4/object/checkannotationspan": "/en/enterprise-server@latest/graphql/reference/objects#checkannotationspan", - "/enterprise/v4/object/checkrun": "/en/enterprise-server@latest/graphql/reference/objects#checkrun", - "/en/enterprise/v4/object/checkrun": "/en/enterprise-server@latest/graphql/reference/objects#checkrun", - "/enterprise/v4/object/checkrunconnection": "/en/enterprise-server@latest/graphql/reference/objects#checkrunconnection", - "/en/enterprise/v4/object/checkrunconnection": "/en/enterprise-server@latest/graphql/reference/objects#checkrunconnection", - "/enterprise/v4/object/checkrunedge": "/en/enterprise-server@latest/graphql/reference/objects#checkrunedge", - "/en/enterprise/v4/object/checkrunedge": "/en/enterprise-server@latest/graphql/reference/objects#checkrunedge", - "/enterprise/v4/object/checksuite": "/en/enterprise-server@latest/graphql/reference/objects#checksuite", - "/en/enterprise/v4/object/checksuite": "/en/enterprise-server@latest/graphql/reference/objects#checksuite", - "/enterprise/v4/object/checksuiteconnection": "/en/enterprise-server@latest/graphql/reference/objects#checksuiteconnection", - "/en/enterprise/v4/object/checksuiteconnection": "/en/enterprise-server@latest/graphql/reference/objects#checksuiteconnection", - "/enterprise/v4/object/checksuiteedge": "/en/enterprise-server@latest/graphql/reference/objects#checksuiteedge", - "/en/enterprise/v4/object/checksuiteedge": "/en/enterprise-server@latest/graphql/reference/objects#checksuiteedge", - "/enterprise/v4/object/clearlabelsfromlabelablepayload": "/en/enterprise-server@latest/graphql/reference/objects#clearlabelsfromlabelablepayload", - "/en/enterprise/v4/object/clearlabelsfromlabelablepayload": "/en/enterprise-server@latest/graphql/reference/objects#clearlabelsfromlabelablepayload", - "/enterprise/v4/object/cloneprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#cloneprojectpayload", - "/en/enterprise/v4/object/cloneprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#cloneprojectpayload", - "/enterprise/v4/object/clonetemplaterepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#clonetemplaterepositorypayload", - "/en/enterprise/v4/object/clonetemplaterepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#clonetemplaterepositorypayload", - "/enterprise/v4/object/closedevent": "/en/enterprise-server@latest/graphql/reference/objects#closedevent", - "/en/enterprise/v4/object/closedevent": "/en/enterprise-server@latest/graphql/reference/objects#closedevent", - "/enterprise/v4/object/closeissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#closeissuepayload", - "/en/enterprise/v4/object/closeissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#closeissuepayload", - "/enterprise/v4/object/closepullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#closepullrequestpayload", - "/en/enterprise/v4/object/closepullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#closepullrequestpayload", - "/enterprise/v4/object/codeofconduct": "/en/enterprise-server@latest/graphql/reference/objects#codeofconduct", - "/en/enterprise/v4/object/codeofconduct": "/en/enterprise-server@latest/graphql/reference/objects#codeofconduct", - "/enterprise/v4/object/commentdeletedevent": "/en/enterprise-server@latest/graphql/reference/objects#commentdeletedevent", - "/en/enterprise/v4/object/commentdeletedevent": "/en/enterprise-server@latest/graphql/reference/objects#commentdeletedevent", - "/enterprise/v4/object/commit": "/en/enterprise-server@latest/graphql/reference/objects#commit", - "/en/enterprise/v4/object/commit": "/en/enterprise-server@latest/graphql/reference/objects#commit", - "/enterprise/v4/object/commitcomment": "/en/enterprise-server@latest/graphql/reference/objects#commitcomment", - "/en/enterprise/v4/object/commitcomment": "/en/enterprise-server@latest/graphql/reference/objects#commitcomment", - "/enterprise/v4/object/commitcommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#commitcommentconnection", - "/en/enterprise/v4/object/commitcommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#commitcommentconnection", - "/enterprise/v4/object/commitcommentedge": "/en/enterprise-server@latest/graphql/reference/objects#commitcommentedge", - "/en/enterprise/v4/object/commitcommentedge": "/en/enterprise-server@latest/graphql/reference/objects#commitcommentedge", - "/enterprise/v4/object/commitcommentthread": "/en/enterprise-server@latest/graphql/reference/objects#commitcommentthread", - "/en/enterprise/v4/object/commitcommentthread": "/en/enterprise-server@latest/graphql/reference/objects#commitcommentthread", - "/enterprise/v4/object/commitconnection": "/en/enterprise-server@latest/graphql/reference/objects#commitconnection", - "/en/enterprise/v4/object/commitconnection": "/en/enterprise-server@latest/graphql/reference/objects#commitconnection", - "/enterprise/v4/object/commitcontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#commitcontributionsbyrepository", - "/en/enterprise/v4/object/commitcontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#commitcontributionsbyrepository", - "/enterprise/v4/object/commitedge": "/en/enterprise-server@latest/graphql/reference/objects#commitedge", - "/en/enterprise/v4/object/commitedge": "/en/enterprise-server@latest/graphql/reference/objects#commitedge", - "/enterprise/v4/object/commithistoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#commithistoryconnection", - "/en/enterprise/v4/object/commithistoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#commithistoryconnection", - "/enterprise/v4/object/connectedevent": "/en/enterprise-server@latest/graphql/reference/objects#connectedevent", - "/en/enterprise/v4/object/connectedevent": "/en/enterprise-server@latest/graphql/reference/objects#connectedevent", - "/enterprise/v4/object/contentattachment": "/en/enterprise-server@latest/graphql/reference/objects#contentattachment", - "/en/enterprise/v4/object/contentattachment": "/en/enterprise-server@latest/graphql/reference/objects#contentattachment", - "/enterprise/v4/object/contentreference": "/en/enterprise-server@latest/graphql/reference/objects#contentreference", - "/en/enterprise/v4/object/contentreference": "/en/enterprise-server@latest/graphql/reference/objects#contentreference", - "/enterprise/v4/object/contributioncalendar": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendar", - "/en/enterprise/v4/object/contributioncalendar": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendar", - "/enterprise/v4/object/contributioncalendarday": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendarday", - "/en/enterprise/v4/object/contributioncalendarday": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendarday", - "/enterprise/v4/object/contributioncalendarmonth": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendarmonth", - "/en/enterprise/v4/object/contributioncalendarmonth": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendarmonth", - "/enterprise/v4/object/contributioncalendarweek": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendarweek", - "/en/enterprise/v4/object/contributioncalendarweek": "/en/enterprise-server@latest/graphql/reference/objects#contributioncalendarweek", - "/enterprise/v4/object/contributionscollection": "/en/enterprise-server@latest/graphql/reference/objects#contributionscollection", - "/en/enterprise/v4/object/contributionscollection": "/en/enterprise-server@latest/graphql/reference/objects#contributionscollection", - "/enterprise/v4/object/convertednotetoissueevent": "/en/enterprise-server@latest/graphql/reference/objects#convertednotetoissueevent", - "/en/enterprise/v4/object/convertednotetoissueevent": "/en/enterprise-server@latest/graphql/reference/objects#convertednotetoissueevent", - "/enterprise/v4/object/convertprojectcardnotetoissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#convertprojectcardnotetoissuepayload", - "/en/enterprise/v4/object/convertprojectcardnotetoissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#convertprojectcardnotetoissuepayload", - "/enterprise/v4/object/converttodraftevent": "/en/enterprise-server@latest/graphql/reference/objects#converttodraftevent", - "/en/enterprise/v4/object/converttodraftevent": "/en/enterprise-server@latest/graphql/reference/objects#converttodraftevent", - "/enterprise/v4/object/createbranchprotectionrulepayload": "/en/enterprise-server@latest/graphql/reference/objects#createbranchprotectionrulepayload", - "/en/enterprise/v4/object/createbranchprotectionrulepayload": "/en/enterprise-server@latest/graphql/reference/objects#createbranchprotectionrulepayload", - "/enterprise/v4/object/createcheckrunpayload": "/en/enterprise-server@latest/graphql/reference/objects#createcheckrunpayload", - "/en/enterprise/v4/object/createcheckrunpayload": "/en/enterprise-server@latest/graphql/reference/objects#createcheckrunpayload", - "/enterprise/v4/object/createchecksuitepayload": "/en/enterprise-server@latest/graphql/reference/objects#createchecksuitepayload", - "/en/enterprise/v4/object/createchecksuitepayload": "/en/enterprise-server@latest/graphql/reference/objects#createchecksuitepayload", - "/enterprise/v4/object/createcontentattachmentpayload": "/en/enterprise-server@latest/graphql/reference/objects#createcontentattachmentpayload", - "/en/enterprise/v4/object/createcontentattachmentpayload": "/en/enterprise-server@latest/graphql/reference/objects#createcontentattachmentpayload", - "/enterprise/v4/object/createdcommitcontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdcommitcontribution", - "/en/enterprise/v4/object/createdcommitcontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdcommitcontribution", - "/enterprise/v4/object/createdcommitcontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdcommitcontributionconnection", - "/en/enterprise/v4/object/createdcommitcontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdcommitcontributionconnection", - "/enterprise/v4/object/createdcommitcontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdcommitcontributionedge", - "/en/enterprise/v4/object/createdcommitcontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdcommitcontributionedge", - "/enterprise/v4/object/createdeploymentpayload": "/en/enterprise-server@latest/graphql/reference/objects#createdeploymentpayload", - "/en/enterprise/v4/object/createdeploymentpayload": "/en/enterprise-server@latest/graphql/reference/objects#createdeploymentpayload", - "/enterprise/v4/object/createdeploymentstatuspayload": "/en/enterprise-server@latest/graphql/reference/objects#createdeploymentstatuspayload", - "/en/enterprise/v4/object/createdeploymentstatuspayload": "/en/enterprise-server@latest/graphql/reference/objects#createdeploymentstatuspayload", - "/enterprise/v4/object/createdissuecontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdissuecontribution", - "/en/enterprise/v4/object/createdissuecontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdissuecontribution", - "/enterprise/v4/object/createdissuecontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdissuecontributionconnection", - "/en/enterprise/v4/object/createdissuecontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdissuecontributionconnection", - "/enterprise/v4/object/createdissuecontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdissuecontributionedge", - "/en/enterprise/v4/object/createdissuecontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdissuecontributionedge", - "/enterprise/v4/object/createdpullrequestcontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontribution", - "/en/enterprise/v4/object/createdpullrequestcontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontribution", - "/enterprise/v4/object/createdpullrequestcontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontributionconnection", - "/en/enterprise/v4/object/createdpullrequestcontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontributionconnection", - "/enterprise/v4/object/createdpullrequestcontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontributionedge", - "/en/enterprise/v4/object/createdpullrequestcontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontributionedge", - "/enterprise/v4/object/createdpullrequestreviewcontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontribution", - "/en/enterprise/v4/object/createdpullrequestreviewcontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontribution", - "/enterprise/v4/object/createdpullrequestreviewcontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontributionconnection", - "/en/enterprise/v4/object/createdpullrequestreviewcontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontributionconnection", - "/enterprise/v4/object/createdpullrequestreviewcontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontributionedge", - "/en/enterprise/v4/object/createdpullrequestreviewcontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontributionedge", - "/enterprise/v4/object/createdrepositorycontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdrepositorycontribution", - "/en/enterprise/v4/object/createdrepositorycontribution": "/en/enterprise-server@latest/graphql/reference/objects#createdrepositorycontribution", - "/enterprise/v4/object/createdrepositorycontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdrepositorycontributionconnection", - "/en/enterprise/v4/object/createdrepositorycontributionconnection": "/en/enterprise-server@latest/graphql/reference/objects#createdrepositorycontributionconnection", - "/enterprise/v4/object/createdrepositorycontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdrepositorycontributionedge", - "/en/enterprise/v4/object/createdrepositorycontributionedge": "/en/enterprise-server@latest/graphql/reference/objects#createdrepositorycontributionedge", - "/enterprise/v4/object/createipallowlistentrypayload": "/en/enterprise-server@latest/graphql/reference/objects#createipallowlistentrypayload", - "/en/enterprise/v4/object/createipallowlistentrypayload": "/en/enterprise-server@latest/graphql/reference/objects#createipallowlistentrypayload", - "/enterprise/v4/object/createissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#createissuepayload", - "/en/enterprise/v4/object/createissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#createissuepayload", - "/enterprise/v4/object/createlabelpayload": "/en/enterprise-server@latest/graphql/reference/objects#createlabelpayload", - "/en/enterprise/v4/object/createlabelpayload": "/en/enterprise-server@latest/graphql/reference/objects#createlabelpayload", - "/enterprise/v4/object/createprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#createprojectpayload", - "/en/enterprise/v4/object/createprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#createprojectpayload", - "/enterprise/v4/object/createpullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#createpullrequestpayload", - "/en/enterprise/v4/object/createpullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#createpullrequestpayload", - "/enterprise/v4/object/createrefpayload": "/en/enterprise-server@latest/graphql/reference/objects#createrefpayload", - "/en/enterprise/v4/object/createrefpayload": "/en/enterprise-server@latest/graphql/reference/objects#createrefpayload", - "/enterprise/v4/object/createrepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#createrepositorypayload", - "/en/enterprise/v4/object/createrepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#createrepositorypayload", - "/enterprise/v4/object/createteamdiscussioncommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#createteamdiscussioncommentpayload", - "/en/enterprise/v4/object/createteamdiscussioncommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#createteamdiscussioncommentpayload", - "/enterprise/v4/object/createteamdiscussionpayload": "/en/enterprise-server@latest/graphql/reference/objects#createteamdiscussionpayload", - "/en/enterprise/v4/object/createteamdiscussionpayload": "/en/enterprise-server@latest/graphql/reference/objects#createteamdiscussionpayload", - "/enterprise/v4/object/crossreferencedevent": "/en/enterprise-server@latest/graphql/reference/objects#crossreferencedevent", - "/en/enterprise/v4/object/crossreferencedevent": "/en/enterprise-server@latest/graphql/reference/objects#crossreferencedevent", - "/enterprise/v4/object/deletebranchprotectionrulepayload": "/en/enterprise-server@latest/graphql/reference/objects#deletebranchprotectionrulepayload", - "/en/enterprise/v4/object/deletebranchprotectionrulepayload": "/en/enterprise-server@latest/graphql/reference/objects#deletebranchprotectionrulepayload", - "/enterprise/v4/object/deletedeploymentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletedeploymentpayload", - "/en/enterprise/v4/object/deletedeploymentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletedeploymentpayload", - "/enterprise/v4/object/deleteipallowlistentrypayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteipallowlistentrypayload", - "/en/enterprise/v4/object/deleteipallowlistentrypayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteipallowlistentrypayload", - "/enterprise/v4/object/deleteissuecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteissuecommentpayload", - "/en/enterprise/v4/object/deleteissuecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteissuecommentpayload", - "/enterprise/v4/object/deleteissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteissuepayload", - "/en/enterprise/v4/object/deleteissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteissuepayload", - "/enterprise/v4/object/deletelabelpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletelabelpayload", - "/en/enterprise/v4/object/deletelabelpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletelabelpayload", - "/enterprise/v4/object/deletepackageversionpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletepackageversionpayload", - "/en/enterprise/v4/object/deletepackageversionpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletepackageversionpayload", - "/enterprise/v4/object/deleteprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteprojectcardpayload", - "/en/enterprise/v4/object/deleteprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteprojectcardpayload", - "/enterprise/v4/object/deleteprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteprojectcolumnpayload", - "/en/enterprise/v4/object/deleteprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteprojectcolumnpayload", - "/enterprise/v4/object/deleteprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteprojectpayload", - "/en/enterprise/v4/object/deleteprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteprojectpayload", - "/enterprise/v4/object/deletepullrequestreviewcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletepullrequestreviewcommentpayload", - "/en/enterprise/v4/object/deletepullrequestreviewcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletepullrequestreviewcommentpayload", - "/enterprise/v4/object/deletepullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletepullrequestreviewpayload", - "/en/enterprise/v4/object/deletepullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#deletepullrequestreviewpayload", - "/enterprise/v4/object/deleterefpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleterefpayload", - "/en/enterprise/v4/object/deleterefpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleterefpayload", - "/enterprise/v4/object/deleteteamdiscussioncommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteteamdiscussioncommentpayload", - "/en/enterprise/v4/object/deleteteamdiscussioncommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteteamdiscussioncommentpayload", - "/enterprise/v4/object/deleteteamdiscussionpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteteamdiscussionpayload", - "/en/enterprise/v4/object/deleteteamdiscussionpayload": "/en/enterprise-server@latest/graphql/reference/objects#deleteteamdiscussionpayload", - "/enterprise/v4/object/demilestonedevent": "/en/enterprise-server@latest/graphql/reference/objects#demilestonedevent", - "/en/enterprise/v4/object/demilestonedevent": "/en/enterprise-server@latest/graphql/reference/objects#demilestonedevent", - "/enterprise/v4/object/deployedevent": "/en/enterprise-server@latest/graphql/reference/objects#deployedevent", - "/en/enterprise/v4/object/deployedevent": "/en/enterprise-server@latest/graphql/reference/objects#deployedevent", - "/enterprise/v4/object/deploykey": "/en/enterprise-server@latest/graphql/reference/objects#deploykey", - "/en/enterprise/v4/object/deploykey": "/en/enterprise-server@latest/graphql/reference/objects#deploykey", - "/enterprise/v4/object/deploykeyconnection": "/en/enterprise-server@latest/graphql/reference/objects#deploykeyconnection", - "/en/enterprise/v4/object/deploykeyconnection": "/en/enterprise-server@latest/graphql/reference/objects#deploykeyconnection", - "/enterprise/v4/object/deploykeyedge": "/en/enterprise-server@latest/graphql/reference/objects#deploykeyedge", - "/en/enterprise/v4/object/deploykeyedge": "/en/enterprise-server@latest/graphql/reference/objects#deploykeyedge", - "/enterprise/v4/object/deployment": "/en/enterprise-server@latest/graphql/reference/objects#deployment", - "/en/enterprise/v4/object/deployment": "/en/enterprise-server@latest/graphql/reference/objects#deployment", - "/enterprise/v4/object/deploymentconnection": "/en/enterprise-server@latest/graphql/reference/objects#deploymentconnection", - "/en/enterprise/v4/object/deploymentconnection": "/en/enterprise-server@latest/graphql/reference/objects#deploymentconnection", - "/enterprise/v4/object/deploymentedge": "/en/enterprise-server@latest/graphql/reference/objects#deploymentedge", - "/en/enterprise/v4/object/deploymentedge": "/en/enterprise-server@latest/graphql/reference/objects#deploymentedge", - "/enterprise/v4/object/deploymentenvironmentchangedevent": "/en/enterprise-server@latest/graphql/reference/objects#deploymentenvironmentchangedevent", - "/en/enterprise/v4/object/deploymentenvironmentchangedevent": "/en/enterprise-server@latest/graphql/reference/objects#deploymentenvironmentchangedevent", - "/enterprise/v4/object/deploymentstatus": "/en/enterprise-server@latest/graphql/reference/objects#deploymentstatus", - "/en/enterprise/v4/object/deploymentstatus": "/en/enterprise-server@latest/graphql/reference/objects#deploymentstatus", - "/enterprise/v4/object/deploymentstatusconnection": "/en/enterprise-server@latest/graphql/reference/objects#deploymentstatusconnection", - "/en/enterprise/v4/object/deploymentstatusconnection": "/en/enterprise-server@latest/graphql/reference/objects#deploymentstatusconnection", - "/enterprise/v4/object/deploymentstatusedge": "/en/enterprise-server@latest/graphql/reference/objects#deploymentstatusedge", - "/en/enterprise/v4/object/deploymentstatusedge": "/en/enterprise-server@latest/graphql/reference/objects#deploymentstatusedge", - "/enterprise/v4/object/disconnectedevent": "/en/enterprise-server@latest/graphql/reference/objects#disconnectedevent", - "/en/enterprise/v4/object/disconnectedevent": "/en/enterprise-server@latest/graphql/reference/objects#disconnectedevent", - "/enterprise/v4/object/dismisspullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#dismisspullrequestreviewpayload", - "/en/enterprise/v4/object/dismisspullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#dismisspullrequestreviewpayload", - "/enterprise/v4/object/enterprise": "/en/enterprise-server@latest/graphql/reference/objects#enterprise", - "/en/enterprise/v4/object/enterprise": "/en/enterprise-server@latest/graphql/reference/objects#enterprise", - "/enterprise/v4/object/enterpriseadministratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorconnection", - "/en/enterprise/v4/object/enterpriseadministratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorconnection", - "/enterprise/v4/object/enterpriseadministratoredge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratoredge", - "/en/enterprise/v4/object/enterpriseadministratoredge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratoredge", - "/enterprise/v4/object/enterpriseadministratorinvitation": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitation", - "/en/enterprise/v4/object/enterpriseadministratorinvitation": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitation", - "/enterprise/v4/object/enterpriseadministratorinvitationconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitationconnection", - "/en/enterprise/v4/object/enterpriseadministratorinvitationconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitationconnection", - "/enterprise/v4/object/enterpriseadministratorinvitationedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitationedge", - "/en/enterprise/v4/object/enterpriseadministratorinvitationedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitationedge", - "/enterprise/v4/object/enterprisebillinginfo": "/en/enterprise-server@latest/graphql/reference/objects#enterprisebillinginfo", - "/en/enterprise/v4/object/enterprisebillinginfo": "/en/enterprise-server@latest/graphql/reference/objects#enterprisebillinginfo", - "/enterprise/v4/object/enterpriseidentityprovider": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseidentityprovider", - "/en/enterprise/v4/object/enterpriseidentityprovider": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseidentityprovider", - "/enterprise/v4/object/enterprisememberconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterprisememberconnection", - "/en/enterprise/v4/object/enterprisememberconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterprisememberconnection", - "/enterprise/v4/object/enterprisememberedge": "/en/enterprise-server@latest/graphql/reference/objects#enterprisememberedge", - "/en/enterprise/v4/object/enterprisememberedge": "/en/enterprise-server@latest/graphql/reference/objects#enterprisememberedge", - "/enterprise/v4/object/enterpriseorganizationmembershipconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseorganizationmembershipconnection", - "/en/enterprise/v4/object/enterpriseorganizationmembershipconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseorganizationmembershipconnection", - "/enterprise/v4/object/enterpriseorganizationmembershipedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseorganizationmembershipedge", - "/en/enterprise/v4/object/enterpriseorganizationmembershipedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseorganizationmembershipedge", - "/enterprise/v4/object/enterpriseoutsidecollaboratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", - "/en/enterprise/v4/object/enterpriseoutsidecollaboratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", - "/enterprise/v4/object/enterpriseoutsidecollaboratoredge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseoutsidecollaboratoredge", - "/en/enterprise/v4/object/enterpriseoutsidecollaboratoredge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseoutsidecollaboratoredge", - "/enterprise/v4/object/enterpriseownerinfo": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseownerinfo", - "/en/enterprise/v4/object/enterpriseownerinfo": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseownerinfo", - "/enterprise/v4/object/enterprisependingcollaboratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingcollaboratorconnection", - "/en/enterprise/v4/object/enterprisependingcollaboratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingcollaboratorconnection", - "/enterprise/v4/object/enterprisependingcollaboratoredge": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingcollaboratoredge", - "/en/enterprise/v4/object/enterprisependingcollaboratoredge": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingcollaboratoredge", - "/enterprise/v4/object/enterprisependingmemberinvitationconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingmemberinvitationconnection", - "/en/enterprise/v4/object/enterprisependingmemberinvitationconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingmemberinvitationconnection", - "/enterprise/v4/object/enterprisependingmemberinvitationedge": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingmemberinvitationedge", - "/en/enterprise/v4/object/enterprisependingmemberinvitationedge": "/en/enterprise-server@latest/graphql/reference/objects#enterprisependingmemberinvitationedge", - "/enterprise/v4/object/enterpriserepositoryinfo": "/en/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfo", - "/en/enterprise/v4/object/enterpriserepositoryinfo": "/en/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfo", - "/enterprise/v4/object/enterpriserepositoryinfoconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfoconnection", - "/en/enterprise/v4/object/enterpriserepositoryinfoconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfoconnection", - "/enterprise/v4/object/enterpriserepositoryinfoedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfoedge", - "/en/enterprise/v4/object/enterpriserepositoryinfoedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfoedge", - "/enterprise/v4/object/enterpriseserverinstallation": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserverinstallation", - "/en/enterprise/v4/object/enterpriseserverinstallation": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserverinstallation", - "/enterprise/v4/object/enterpriseserveruseraccount": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccount", - "/en/enterprise/v4/object/enterpriseserveruseraccount": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccount", - "/enterprise/v4/object/enterpriseserveruseraccountconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountconnection", - "/en/enterprise/v4/object/enterpriseserveruseraccountconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountconnection", - "/enterprise/v4/object/enterpriseserveruseraccountedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountedge", - "/en/enterprise/v4/object/enterpriseserveruseraccountedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountedge", - "/enterprise/v4/object/enterpriseserveruseraccountemail": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemail", - "/en/enterprise/v4/object/enterpriseserveruseraccountemail": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemail", - "/enterprise/v4/object/enterpriseserveruseraccountemailconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemailconnection", - "/en/enterprise/v4/object/enterpriseserveruseraccountemailconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemailconnection", - "/enterprise/v4/object/enterpriseserveruseraccountemailedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemailedge", - "/en/enterprise/v4/object/enterpriseserveruseraccountemailedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemailedge", - "/enterprise/v4/object/enterpriseserveruseraccountsupload": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsupload", - "/en/enterprise/v4/object/enterpriseserveruseraccountsupload": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsupload", - "/enterprise/v4/object/enterpriseserveruseraccountsuploadconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", - "/en/enterprise/v4/object/enterpriseserveruseraccountsuploadconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", - "/enterprise/v4/object/enterpriseserveruseraccountsuploadedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", - "/en/enterprise/v4/object/enterpriseserveruseraccountsuploadedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", - "/enterprise/v4/object/enterpriseuseraccount": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccount", - "/en/enterprise/v4/object/enterpriseuseraccount": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccount", - "/enterprise/v4/object/enterpriseuseraccountconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccountconnection", - "/en/enterprise/v4/object/enterpriseuseraccountconnection": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccountconnection", - "/enterprise/v4/object/enterpriseuseraccountedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccountedge", - "/en/enterprise/v4/object/enterpriseuseraccountedge": "/en/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccountedge", - "/enterprise/v4/object/externalidentity": "/en/enterprise-server@latest/graphql/reference/objects#externalidentity", - "/en/enterprise/v4/object/externalidentity": "/en/enterprise-server@latest/graphql/reference/objects#externalidentity", - "/enterprise/v4/object/externalidentityconnection": "/en/enterprise-server@latest/graphql/reference/objects#externalidentityconnection", - "/en/enterprise/v4/object/externalidentityconnection": "/en/enterprise-server@latest/graphql/reference/objects#externalidentityconnection", - "/enterprise/v4/object/externalidentityedge": "/en/enterprise-server@latest/graphql/reference/objects#externalidentityedge", - "/en/enterprise/v4/object/externalidentityedge": "/en/enterprise-server@latest/graphql/reference/objects#externalidentityedge", - "/enterprise/v4/object/externalidentitysamlattributes": "/en/enterprise-server@latest/graphql/reference/objects#externalidentitysamlattributes", - "/en/enterprise/v4/object/externalidentitysamlattributes": "/en/enterprise-server@latest/graphql/reference/objects#externalidentitysamlattributes", - "/enterprise/v4/object/externalidentityscimattributes": "/en/enterprise-server@latest/graphql/reference/objects#externalidentityscimattributes", - "/en/enterprise/v4/object/externalidentityscimattributes": "/en/enterprise-server@latest/graphql/reference/objects#externalidentityscimattributes", - "/enterprise/v4/object/followerconnection": "/en/enterprise-server@latest/graphql/reference/objects#followerconnection", - "/en/enterprise/v4/object/followerconnection": "/en/enterprise-server@latest/graphql/reference/objects#followerconnection", - "/enterprise/v4/object/followingconnection": "/en/enterprise-server@latest/graphql/reference/objects#followingconnection", - "/en/enterprise/v4/object/followingconnection": "/en/enterprise-server@latest/graphql/reference/objects#followingconnection", - "/enterprise/v4/object/followuserpayload": "/en/enterprise-server@latest/graphql/reference/objects#followuserpayload", - "/en/enterprise/v4/object/followuserpayload": "/en/enterprise-server@latest/graphql/reference/objects#followuserpayload", - "/enterprise/v4/object/generichovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#generichovercardcontext", - "/en/enterprise/v4/object/generichovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#generichovercardcontext", - "/enterprise/v4/object/gist": "/en/enterprise-server@latest/graphql/reference/objects#gist", - "/en/enterprise/v4/object/gist": "/en/enterprise-server@latest/graphql/reference/objects#gist", - "/enterprise/v4/object/gistcomment": "/en/enterprise-server@latest/graphql/reference/objects#gistcomment", - "/en/enterprise/v4/object/gistcomment": "/en/enterprise-server@latest/graphql/reference/objects#gistcomment", - "/enterprise/v4/object/gistcommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#gistcommentconnection", - "/en/enterprise/v4/object/gistcommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#gistcommentconnection", - "/enterprise/v4/object/gistcommentedge": "/en/enterprise-server@latest/graphql/reference/objects#gistcommentedge", - "/en/enterprise/v4/object/gistcommentedge": "/en/enterprise-server@latest/graphql/reference/objects#gistcommentedge", - "/enterprise/v4/object/gistconnection": "/en/enterprise-server@latest/graphql/reference/objects#gistconnection", - "/en/enterprise/v4/object/gistconnection": "/en/enterprise-server@latest/graphql/reference/objects#gistconnection", - "/enterprise/v4/object/gistedge": "/en/enterprise-server@latest/graphql/reference/objects#gistedge", - "/en/enterprise/v4/object/gistedge": "/en/enterprise-server@latest/graphql/reference/objects#gistedge", - "/enterprise/v4/object/gistfile": "/en/enterprise-server@latest/graphql/reference/objects#gistfile", - "/en/enterprise/v4/object/gistfile": "/en/enterprise-server@latest/graphql/reference/objects#gistfile", - "/enterprise/v4/object/gitactor": "/en/enterprise-server@latest/graphql/reference/objects#gitactor", - "/en/enterprise/v4/object/gitactor": "/en/enterprise-server@latest/graphql/reference/objects#gitactor", - "/enterprise/v4/object/githubmetadata": "/en/enterprise-server@latest/graphql/reference/objects#githubmetadata", - "/en/enterprise/v4/object/githubmetadata": "/en/enterprise-server@latest/graphql/reference/objects#githubmetadata", - "/enterprise/v4/object/gpgsignature": "/en/enterprise-server@latest/graphql/reference/objects#gpgsignature", - "/en/enterprise/v4/object/gpgsignature": "/en/enterprise-server@latest/graphql/reference/objects#gpgsignature", - "/enterprise/v4/object/headrefdeletedevent": "/en/enterprise-server@latest/graphql/reference/objects#headrefdeletedevent", - "/en/enterprise/v4/object/headrefdeletedevent": "/en/enterprise-server@latest/graphql/reference/objects#headrefdeletedevent", - "/enterprise/v4/object/headrefforcepushedevent": "/en/enterprise-server@latest/graphql/reference/objects#headrefforcepushedevent", - "/en/enterprise/v4/object/headrefforcepushedevent": "/en/enterprise-server@latest/graphql/reference/objects#headrefforcepushedevent", - "/enterprise/v4/object/headrefrestoredevent": "/en/enterprise-server@latest/graphql/reference/objects#headrefrestoredevent", - "/en/enterprise/v4/object/headrefrestoredevent": "/en/enterprise-server@latest/graphql/reference/objects#headrefrestoredevent", - "/enterprise/v4/object/hovercard": "/en/enterprise-server@latest/graphql/reference/objects#hovercard", - "/en/enterprise/v4/object/hovercard": "/en/enterprise-server@latest/graphql/reference/objects#hovercard", - "/enterprise/v4/object/importprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#importprojectpayload", - "/en/enterprise/v4/object/importprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#importprojectpayload", - "/enterprise/v4/object/ipallowlistentry": "/en/enterprise-server@latest/graphql/reference/objects#ipallowlistentry", - "/en/enterprise/v4/object/ipallowlistentry": "/en/enterprise-server@latest/graphql/reference/objects#ipallowlistentry", - "/enterprise/v4/object/ipallowlistentryconnection": "/en/enterprise-server@latest/graphql/reference/objects#ipallowlistentryconnection", - "/en/enterprise/v4/object/ipallowlistentryconnection": "/en/enterprise-server@latest/graphql/reference/objects#ipallowlistentryconnection", - "/enterprise/v4/object/ipallowlistentryedge": "/en/enterprise-server@latest/graphql/reference/objects#ipallowlistentryedge", - "/en/enterprise/v4/object/ipallowlistentryedge": "/en/enterprise-server@latest/graphql/reference/objects#ipallowlistentryedge", - "/enterprise/v4/object/issue": "/en/enterprise-server@latest/graphql/reference/objects#issue", - "/en/enterprise/v4/object/issue": "/en/enterprise-server@latest/graphql/reference/objects#issue", - "/enterprise/v4/object/issuecomment": "/en/enterprise-server@latest/graphql/reference/objects#issuecomment", - "/en/enterprise/v4/object/issuecomment": "/en/enterprise-server@latest/graphql/reference/objects#issuecomment", - "/enterprise/v4/object/issuecommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#issuecommentconnection", - "/en/enterprise/v4/object/issuecommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#issuecommentconnection", - "/enterprise/v4/object/issuecommentedge": "/en/enterprise-server@latest/graphql/reference/objects#issuecommentedge", - "/en/enterprise/v4/object/issuecommentedge": "/en/enterprise-server@latest/graphql/reference/objects#issuecommentedge", - "/enterprise/v4/object/issueconnection": "/en/enterprise-server@latest/graphql/reference/objects#issueconnection", - "/en/enterprise/v4/object/issueconnection": "/en/enterprise-server@latest/graphql/reference/objects#issueconnection", - "/enterprise/v4/object/issuecontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#issuecontributionsbyrepository", - "/en/enterprise/v4/object/issuecontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#issuecontributionsbyrepository", - "/enterprise/v4/object/issueedge": "/en/enterprise-server@latest/graphql/reference/objects#issueedge", - "/en/enterprise/v4/object/issueedge": "/en/enterprise-server@latest/graphql/reference/objects#issueedge", - "/enterprise/v4/object/issuetimelineconnection": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineconnection", - "/en/enterprise/v4/object/issuetimelineconnection": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineconnection", - "/enterprise/v4/object/issuetimelineitemedge": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineitemedge", - "/en/enterprise/v4/object/issuetimelineitemedge": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineitemedge", - "/enterprise/v4/object/issuetimelineitemsconnection": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineitemsconnection", - "/en/enterprise/v4/object/issuetimelineitemsconnection": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineitemsconnection", - "/enterprise/v4/object/issuetimelineitemsedge": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineitemsedge", - "/en/enterprise/v4/object/issuetimelineitemsedge": "/en/enterprise-server@latest/graphql/reference/objects#issuetimelineitemsedge", - "/enterprise/v4/object/joinedgithubcontribution": "/en/enterprise-server@latest/graphql/reference/objects#joinedgithubcontribution", - "/en/enterprise/v4/object/joinedgithubcontribution": "/en/enterprise-server@latest/graphql/reference/objects#joinedgithubcontribution", - "/enterprise/v4/object/label": "/en/enterprise-server@latest/graphql/reference/objects#label", - "/en/enterprise/v4/object/label": "/en/enterprise-server@latest/graphql/reference/objects#label", - "/enterprise/v4/object/labelconnection": "/en/enterprise-server@latest/graphql/reference/objects#labelconnection", - "/en/enterprise/v4/object/labelconnection": "/en/enterprise-server@latest/graphql/reference/objects#labelconnection", - "/enterprise/v4/object/labeledevent": "/en/enterprise-server@latest/graphql/reference/objects#labeledevent", - "/en/enterprise/v4/object/labeledevent": "/en/enterprise-server@latest/graphql/reference/objects#labeledevent", - "/enterprise/v4/object/labeledge": "/en/enterprise-server@latest/graphql/reference/objects#labeledge", - "/en/enterprise/v4/object/labeledge": "/en/enterprise-server@latest/graphql/reference/objects#labeledge", - "/enterprise/v4/object/language": "/en/enterprise-server@latest/graphql/reference/objects#language", - "/en/enterprise/v4/object/language": "/en/enterprise-server@latest/graphql/reference/objects#language", - "/enterprise/v4/object/languageconnection": "/en/enterprise-server@latest/graphql/reference/objects#languageconnection", - "/en/enterprise/v4/object/languageconnection": "/en/enterprise-server@latest/graphql/reference/objects#languageconnection", - "/enterprise/v4/object/languageedge": "/en/enterprise-server@latest/graphql/reference/objects#languageedge", - "/en/enterprise/v4/object/languageedge": "/en/enterprise-server@latest/graphql/reference/objects#languageedge", - "/enterprise/v4/object/license": "/en/enterprise-server@latest/graphql/reference/objects#license", - "/en/enterprise/v4/object/license": "/en/enterprise-server@latest/graphql/reference/objects#license", - "/enterprise/v4/object/licenserule": "/en/enterprise-server@latest/graphql/reference/objects#licenserule", - "/en/enterprise/v4/object/licenserule": "/en/enterprise-server@latest/graphql/reference/objects#licenserule", - "/enterprise/v4/object/linkrepositorytoprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#linkrepositorytoprojectpayload", - "/en/enterprise/v4/object/linkrepositorytoprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#linkrepositorytoprojectpayload", - "/enterprise/v4/object/lockedevent": "/en/enterprise-server@latest/graphql/reference/objects#lockedevent", - "/en/enterprise/v4/object/lockedevent": "/en/enterprise-server@latest/graphql/reference/objects#lockedevent", - "/enterprise/v4/object/locklockablepayload": "/en/enterprise-server@latest/graphql/reference/objects#locklockablepayload", - "/en/enterprise/v4/object/locklockablepayload": "/en/enterprise-server@latest/graphql/reference/objects#locklockablepayload", - "/enterprise/v4/object/mannequin": "/en/enterprise-server@latest/graphql/reference/objects#mannequin", - "/en/enterprise/v4/object/mannequin": "/en/enterprise-server@latest/graphql/reference/objects#mannequin", - "/enterprise/v4/object/markedasduplicateevent": "/en/enterprise-server@latest/graphql/reference/objects#markedasduplicateevent", - "/en/enterprise/v4/object/markedasduplicateevent": "/en/enterprise-server@latest/graphql/reference/objects#markedasduplicateevent", - "/enterprise/v4/object/markpullrequestreadyforreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#markpullrequestreadyforreviewpayload", - "/en/enterprise/v4/object/markpullrequestreadyforreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#markpullrequestreadyforreviewpayload", - "/enterprise/v4/object/memberscandeletereposclearauditentry": "/en/enterprise-server@latest/graphql/reference/objects#memberscandeletereposclearauditentry", - "/en/enterprise/v4/object/memberscandeletereposclearauditentry": "/en/enterprise-server@latest/graphql/reference/objects#memberscandeletereposclearauditentry", - "/enterprise/v4/object/memberscandeletereposdisableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#memberscandeletereposdisableauditentry", - "/en/enterprise/v4/object/memberscandeletereposdisableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#memberscandeletereposdisableauditentry", - "/enterprise/v4/object/memberscandeletereposenableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#memberscandeletereposenableauditentry", - "/en/enterprise/v4/object/memberscandeletereposenableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#memberscandeletereposenableauditentry", - "/enterprise/v4/object/mentionedevent": "/en/enterprise-server@latest/graphql/reference/objects#mentionedevent", - "/en/enterprise/v4/object/mentionedevent": "/en/enterprise-server@latest/graphql/reference/objects#mentionedevent", - "/enterprise/v4/object/mergebranchpayload": "/en/enterprise-server@latest/graphql/reference/objects#mergebranchpayload", - "/en/enterprise/v4/object/mergebranchpayload": "/en/enterprise-server@latest/graphql/reference/objects#mergebranchpayload", - "/enterprise/v4/object/mergedevent": "/en/enterprise-server@latest/graphql/reference/objects#mergedevent", - "/en/enterprise/v4/object/mergedevent": "/en/enterprise-server@latest/graphql/reference/objects#mergedevent", - "/enterprise/v4/object/mergepullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#mergepullrequestpayload", - "/en/enterprise/v4/object/mergepullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#mergepullrequestpayload", - "/enterprise/v4/object/milestone": "/en/enterprise-server@latest/graphql/reference/objects#milestone", - "/en/enterprise/v4/object/milestone": "/en/enterprise-server@latest/graphql/reference/objects#milestone", - "/enterprise/v4/object/milestoneconnection": "/en/enterprise-server@latest/graphql/reference/objects#milestoneconnection", - "/en/enterprise/v4/object/milestoneconnection": "/en/enterprise-server@latest/graphql/reference/objects#milestoneconnection", - "/enterprise/v4/object/milestonedevent": "/en/enterprise-server@latest/graphql/reference/objects#milestonedevent", - "/en/enterprise/v4/object/milestonedevent": "/en/enterprise-server@latest/graphql/reference/objects#milestonedevent", - "/enterprise/v4/object/milestoneedge": "/en/enterprise-server@latest/graphql/reference/objects#milestoneedge", - "/en/enterprise/v4/object/milestoneedge": "/en/enterprise-server@latest/graphql/reference/objects#milestoneedge", - "/enterprise/v4/object/minimizecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#minimizecommentpayload", - "/en/enterprise/v4/object/minimizecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#minimizecommentpayload", - "/enterprise/v4/object/movedcolumnsinprojectevent": "/en/enterprise-server@latest/graphql/reference/objects#movedcolumnsinprojectevent", - "/en/enterprise/v4/object/movedcolumnsinprojectevent": "/en/enterprise-server@latest/graphql/reference/objects#movedcolumnsinprojectevent", - "/enterprise/v4/object/moveprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#moveprojectcardpayload", - "/en/enterprise/v4/object/moveprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#moveprojectcardpayload", - "/enterprise/v4/object/moveprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#moveprojectcolumnpayload", - "/en/enterprise/v4/object/moveprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#moveprojectcolumnpayload", - "/enterprise/v4/object/oauthapplicationcreateauditentry": "/en/enterprise-server@latest/graphql/reference/objects#oauthapplicationcreateauditentry", - "/en/enterprise/v4/object/oauthapplicationcreateauditentry": "/en/enterprise-server@latest/graphql/reference/objects#oauthapplicationcreateauditentry", - "/enterprise/v4/object/orgaddbillingmanagerauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgaddbillingmanagerauditentry", - "/en/enterprise/v4/object/orgaddbillingmanagerauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgaddbillingmanagerauditentry", - "/enterprise/v4/object/orgaddmemberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgaddmemberauditentry", - "/en/enterprise/v4/object/orgaddmemberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgaddmemberauditentry", - "/enterprise/v4/object/organization": "/en/enterprise-server@latest/graphql/reference/objects#organization", - "/en/enterprise/v4/object/organization": "/en/enterprise-server@latest/graphql/reference/objects#organization", - "/enterprise/v4/object/organizationauditentryconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationauditentryconnection", - "/en/enterprise/v4/object/organizationauditentryconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationauditentryconnection", - "/enterprise/v4/object/organizationauditentryedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationauditentryedge", - "/en/enterprise/v4/object/organizationauditentryedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationauditentryedge", - "/enterprise/v4/object/organizationconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationconnection", - "/en/enterprise/v4/object/organizationconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationconnection", - "/enterprise/v4/object/organizationedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationedge", - "/en/enterprise/v4/object/organizationedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationedge", - "/enterprise/v4/object/organizationidentityprovider": "/en/enterprise-server@latest/graphql/reference/objects#organizationidentityprovider", - "/en/enterprise/v4/object/organizationidentityprovider": "/en/enterprise-server@latest/graphql/reference/objects#organizationidentityprovider", - "/enterprise/v4/object/organizationinvitation": "/en/enterprise-server@latest/graphql/reference/objects#organizationinvitation", - "/en/enterprise/v4/object/organizationinvitation": "/en/enterprise-server@latest/graphql/reference/objects#organizationinvitation", - "/enterprise/v4/object/organizationinvitationconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationinvitationconnection", - "/en/enterprise/v4/object/organizationinvitationconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationinvitationconnection", - "/enterprise/v4/object/organizationinvitationedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationinvitationedge", - "/en/enterprise/v4/object/organizationinvitationedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationinvitationedge", - "/enterprise/v4/object/organizationmemberconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationmemberconnection", - "/en/enterprise/v4/object/organizationmemberconnection": "/en/enterprise-server@latest/graphql/reference/objects#organizationmemberconnection", - "/enterprise/v4/object/organizationmemberedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationmemberedge", - "/en/enterprise/v4/object/organizationmemberedge": "/en/enterprise-server@latest/graphql/reference/objects#organizationmemberedge", - "/enterprise/v4/object/organizationshovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#organizationshovercardcontext", - "/en/enterprise/v4/object/organizationshovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#organizationshovercardcontext", - "/enterprise/v4/object/organizationteamshovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#organizationteamshovercardcontext", - "/en/enterprise/v4/object/organizationteamshovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#organizationteamshovercardcontext", - "/enterprise/v4/object/orgblockuserauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgblockuserauditentry", - "/en/enterprise/v4/object/orgblockuserauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgblockuserauditentry", - "/enterprise/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", - "/en/enterprise/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", - "/enterprise/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", - "/en/enterprise/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", - "/enterprise/v4/object/orgcreateauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgcreateauditentry", - "/en/enterprise/v4/object/orgcreateauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgcreateauditentry", - "/enterprise/v4/object/orgdisableoauthapprestrictionsauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", - "/en/enterprise/v4/object/orgdisableoauthapprestrictionsauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", - "/enterprise/v4/object/orgdisablesamlauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgdisablesamlauditentry", - "/en/enterprise/v4/object/orgdisablesamlauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgdisablesamlauditentry", - "/enterprise/v4/object/orgdisabletwofactorrequirementauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", - "/en/enterprise/v4/object/orgdisabletwofactorrequirementauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", - "/enterprise/v4/object/orgenableoauthapprestrictionsauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", - "/en/enterprise/v4/object/orgenableoauthapprestrictionsauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", - "/enterprise/v4/object/orgenablesamlauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgenablesamlauditentry", - "/en/enterprise/v4/object/orgenablesamlauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgenablesamlauditentry", - "/enterprise/v4/object/orgenabletwofactorrequirementauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgenabletwofactorrequirementauditentry", - "/en/enterprise/v4/object/orgenabletwofactorrequirementauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgenabletwofactorrequirementauditentry", - "/enterprise/v4/object/orginvitememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orginvitememberauditentry", - "/en/enterprise/v4/object/orginvitememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orginvitememberauditentry", - "/enterprise/v4/object/orginvitetobusinessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orginvitetobusinessauditentry", - "/en/enterprise/v4/object/orginvitetobusinessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orginvitetobusinessauditentry", - "/enterprise/v4/object/orgoauthappaccessapprovedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessapprovedauditentry", - "/en/enterprise/v4/object/orgoauthappaccessapprovedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessapprovedauditentry", - "/enterprise/v4/object/orgoauthappaccessdeniedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessdeniedauditentry", - "/en/enterprise/v4/object/orgoauthappaccessdeniedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessdeniedauditentry", - "/enterprise/v4/object/orgoauthappaccessrequestedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessrequestedauditentry", - "/en/enterprise/v4/object/orgoauthappaccessrequestedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessrequestedauditentry", - "/enterprise/v4/object/orgremovebillingmanagerauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgremovebillingmanagerauditentry", - "/en/enterprise/v4/object/orgremovebillingmanagerauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgremovebillingmanagerauditentry", - "/enterprise/v4/object/orgremovememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgremovememberauditentry", - "/en/enterprise/v4/object/orgremovememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgremovememberauditentry", - "/enterprise/v4/object/orgremoveoutsidecollaboratorauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", - "/en/enterprise/v4/object/orgremoveoutsidecollaboratorauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", - "/enterprise/v4/object/orgrestorememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgrestorememberauditentry", - "/en/enterprise/v4/object/orgrestorememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgrestorememberauditentry", - "/enterprise/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/en/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", - "/en/enterprise/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/en/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", - "/enterprise/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/en/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", - "/en/enterprise/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/en/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", - "/enterprise/v4/object/orgrestoremembermembershipteamauditentrydata": "/en/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", - "/en/enterprise/v4/object/orgrestoremembermembershipteamauditentrydata": "/en/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", - "/enterprise/v4/object/orgunblockuserauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgunblockuserauditentry", - "/en/enterprise/v4/object/orgunblockuserauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgunblockuserauditentry", - "/enterprise/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", - "/en/enterprise/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", - "/enterprise/v4/object/orgupdatememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatememberauditentry", - "/en/enterprise/v4/object/orgupdatememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatememberauditentry", - "/enterprise/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", - "/en/enterprise/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", - "/enterprise/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", - "/en/enterprise/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/en/enterprise-server@latest/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", - "/enterprise/v4/object/package": "/en/enterprise-server@latest/graphql/reference/objects#package", - "/en/enterprise/v4/object/package": "/en/enterprise-server@latest/graphql/reference/objects#package", - "/enterprise/v4/object/packageconnection": "/en/enterprise-server@latest/graphql/reference/objects#packageconnection", - "/en/enterprise/v4/object/packageconnection": "/en/enterprise-server@latest/graphql/reference/objects#packageconnection", - "/enterprise/v4/object/packageedge": "/en/enterprise-server@latest/graphql/reference/objects#packageedge", - "/en/enterprise/v4/object/packageedge": "/en/enterprise-server@latest/graphql/reference/objects#packageedge", - "/enterprise/v4/object/packagefile": "/en/enterprise-server@latest/graphql/reference/objects#packagefile", - "/en/enterprise/v4/object/packagefile": "/en/enterprise-server@latest/graphql/reference/objects#packagefile", - "/enterprise/v4/object/packagefileconnection": "/en/enterprise-server@latest/graphql/reference/objects#packagefileconnection", - "/en/enterprise/v4/object/packagefileconnection": "/en/enterprise-server@latest/graphql/reference/objects#packagefileconnection", - "/enterprise/v4/object/packagefileedge": "/en/enterprise-server@latest/graphql/reference/objects#packagefileedge", - "/en/enterprise/v4/object/packagefileedge": "/en/enterprise-server@latest/graphql/reference/objects#packagefileedge", - "/enterprise/v4/object/packagestatistics": "/en/enterprise-server@latest/graphql/reference/objects#packagestatistics", - "/en/enterprise/v4/object/packagestatistics": "/en/enterprise-server@latest/graphql/reference/objects#packagestatistics", - "/enterprise/v4/object/packagetag": "/en/enterprise-server@latest/graphql/reference/objects#packagetag", - "/en/enterprise/v4/object/packagetag": "/en/enterprise-server@latest/graphql/reference/objects#packagetag", - "/enterprise/v4/object/packageversion": "/en/enterprise-server@latest/graphql/reference/objects#packageversion", - "/en/enterprise/v4/object/packageversion": "/en/enterprise-server@latest/graphql/reference/objects#packageversion", - "/enterprise/v4/object/packageversionconnection": "/en/enterprise-server@latest/graphql/reference/objects#packageversionconnection", - "/en/enterprise/v4/object/packageversionconnection": "/en/enterprise-server@latest/graphql/reference/objects#packageversionconnection", - "/enterprise/v4/object/packageversionedge": "/en/enterprise-server@latest/graphql/reference/objects#packageversionedge", - "/en/enterprise/v4/object/packageversionedge": "/en/enterprise-server@latest/graphql/reference/objects#packageversionedge", - "/enterprise/v4/object/packageversionstatistics": "/en/enterprise-server@latest/graphql/reference/objects#packageversionstatistics", - "/en/enterprise/v4/object/packageversionstatistics": "/en/enterprise-server@latest/graphql/reference/objects#packageversionstatistics", - "/enterprise/v4/object/pageinfo": "/en/enterprise-server@latest/graphql/reference/objects#pageinfo", - "/en/enterprise/v4/object/pageinfo": "/en/enterprise-server@latest/graphql/reference/objects#pageinfo", - "/enterprise/v4/object/permissionsource": "/en/enterprise-server@latest/graphql/reference/objects#permissionsource", - "/en/enterprise/v4/object/permissionsource": "/en/enterprise-server@latest/graphql/reference/objects#permissionsource", - "/enterprise/v4/object/pinissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#pinissuepayload", - "/en/enterprise/v4/object/pinissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#pinissuepayload", - "/enterprise/v4/object/pinnableitemconnection": "/en/enterprise-server@latest/graphql/reference/objects#pinnableitemconnection", - "/en/enterprise/v4/object/pinnableitemconnection": "/en/enterprise-server@latest/graphql/reference/objects#pinnableitemconnection", - "/enterprise/v4/object/pinnableitemedge": "/en/enterprise-server@latest/graphql/reference/objects#pinnableitemedge", - "/en/enterprise/v4/object/pinnableitemedge": "/en/enterprise-server@latest/graphql/reference/objects#pinnableitemedge", - "/enterprise/v4/object/pinnedevent": "/en/enterprise-server@latest/graphql/reference/objects#pinnedevent", - "/en/enterprise/v4/object/pinnedevent": "/en/enterprise-server@latest/graphql/reference/objects#pinnedevent", - "/enterprise/v4/object/pinnedissue": "/en/enterprise-server@latest/graphql/reference/objects#pinnedissue", - "/en/enterprise/v4/object/pinnedissue": "/en/enterprise-server@latest/graphql/reference/objects#pinnedissue", - "/enterprise/v4/object/pinnedissueconnection": "/en/enterprise-server@latest/graphql/reference/objects#pinnedissueconnection", - "/en/enterprise/v4/object/pinnedissueconnection": "/en/enterprise-server@latest/graphql/reference/objects#pinnedissueconnection", - "/enterprise/v4/object/pinnedissueedge": "/en/enterprise-server@latest/graphql/reference/objects#pinnedissueedge", - "/en/enterprise/v4/object/pinnedissueedge": "/en/enterprise-server@latest/graphql/reference/objects#pinnedissueedge", - "/enterprise/v4/object/privaterepositoryforkingdisableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#privaterepositoryforkingdisableauditentry", - "/en/enterprise/v4/object/privaterepositoryforkingdisableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#privaterepositoryforkingdisableauditentry", - "/enterprise/v4/object/privaterepositoryforkingenableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#privaterepositoryforkingenableauditentry", - "/en/enterprise/v4/object/privaterepositoryforkingenableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#privaterepositoryforkingenableauditentry", - "/enterprise/v4/object/profileitemshowcase": "/en/enterprise-server@latest/graphql/reference/objects#profileitemshowcase", - "/en/enterprise/v4/object/profileitemshowcase": "/en/enterprise-server@latest/graphql/reference/objects#profileitemshowcase", - "/enterprise/v4/object/project": "/en/enterprise-server@latest/graphql/reference/objects#project", - "/en/enterprise/v4/object/project": "/en/enterprise-server@latest/graphql/reference/objects#project", - "/enterprise/v4/object/projectcard": "/en/enterprise-server@latest/graphql/reference/objects#projectcard", - "/en/enterprise/v4/object/projectcard": "/en/enterprise-server@latest/graphql/reference/objects#projectcard", - "/enterprise/v4/object/projectcardconnection": "/en/enterprise-server@latest/graphql/reference/objects#projectcardconnection", - "/en/enterprise/v4/object/projectcardconnection": "/en/enterprise-server@latest/graphql/reference/objects#projectcardconnection", - "/enterprise/v4/object/projectcardedge": "/en/enterprise-server@latest/graphql/reference/objects#projectcardedge", - "/en/enterprise/v4/object/projectcardedge": "/en/enterprise-server@latest/graphql/reference/objects#projectcardedge", - "/enterprise/v4/object/projectcolumn": "/en/enterprise-server@latest/graphql/reference/objects#projectcolumn", - "/en/enterprise/v4/object/projectcolumn": "/en/enterprise-server@latest/graphql/reference/objects#projectcolumn", - "/enterprise/v4/object/projectcolumnconnection": "/en/enterprise-server@latest/graphql/reference/objects#projectcolumnconnection", - "/en/enterprise/v4/object/projectcolumnconnection": "/en/enterprise-server@latest/graphql/reference/objects#projectcolumnconnection", - "/enterprise/v4/object/projectcolumnedge": "/en/enterprise-server@latest/graphql/reference/objects#projectcolumnedge", - "/en/enterprise/v4/object/projectcolumnedge": "/en/enterprise-server@latest/graphql/reference/objects#projectcolumnedge", - "/enterprise/v4/object/projectconnection": "/en/enterprise-server@latest/graphql/reference/objects#projectconnection", - "/en/enterprise/v4/object/projectconnection": "/en/enterprise-server@latest/graphql/reference/objects#projectconnection", - "/enterprise/v4/object/projectedge": "/en/enterprise-server@latest/graphql/reference/objects#projectedge", - "/en/enterprise/v4/object/projectedge": "/en/enterprise-server@latest/graphql/reference/objects#projectedge", - "/enterprise/v4/object/publickey": "/en/enterprise-server@latest/graphql/reference/objects#publickey", - "/en/enterprise/v4/object/publickey": "/en/enterprise-server@latest/graphql/reference/objects#publickey", - "/enterprise/v4/object/publickeyconnection": "/en/enterprise-server@latest/graphql/reference/objects#publickeyconnection", - "/en/enterprise/v4/object/publickeyconnection": "/en/enterprise-server@latest/graphql/reference/objects#publickeyconnection", - "/enterprise/v4/object/publickeyedge": "/en/enterprise-server@latest/graphql/reference/objects#publickeyedge", - "/en/enterprise/v4/object/publickeyedge": "/en/enterprise-server@latest/graphql/reference/objects#publickeyedge", - "/enterprise/v4/object/pullrequest": "/en/enterprise-server@latest/graphql/reference/objects#pullrequest", - "/en/enterprise/v4/object/pullrequest": "/en/enterprise-server@latest/graphql/reference/objects#pullrequest", - "/enterprise/v4/object/pullrequestchangedfile": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfile", - "/en/enterprise/v4/object/pullrequestchangedfile": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfile", - "/enterprise/v4/object/pullrequestchangedfileconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfileconnection", - "/en/enterprise/v4/object/pullrequestchangedfileconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfileconnection", - "/enterprise/v4/object/pullrequestchangedfileedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfileedge", - "/en/enterprise/v4/object/pullrequestchangedfileedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfileedge", - "/enterprise/v4/object/pullrequestcommit": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommit", - "/en/enterprise/v4/object/pullrequestcommit": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommit", - "/enterprise/v4/object/pullrequestcommitcommentthread": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommitcommentthread", - "/en/enterprise/v4/object/pullrequestcommitcommentthread": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommitcommentthread", - "/enterprise/v4/object/pullrequestcommitconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommitconnection", - "/en/enterprise/v4/object/pullrequestcommitconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommitconnection", - "/enterprise/v4/object/pullrequestcommitedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommitedge", - "/en/enterprise/v4/object/pullrequestcommitedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcommitedge", - "/enterprise/v4/object/pullrequestconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestconnection", - "/en/enterprise/v4/object/pullrequestconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestconnection", - "/enterprise/v4/object/pullrequestcontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcontributionsbyrepository", - "/en/enterprise/v4/object/pullrequestcontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestcontributionsbyrepository", - "/enterprise/v4/object/pullrequestedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestedge", - "/en/enterprise/v4/object/pullrequestedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestedge", - "/enterprise/v4/object/pullrequestreview": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreview", - "/en/enterprise/v4/object/pullrequestreview": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreview", - "/enterprise/v4/object/pullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcomment", - "/en/enterprise/v4/object/pullrequestreviewcomment": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcomment", - "/enterprise/v4/object/pullrequestreviewcommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcommentconnection", - "/en/enterprise/v4/object/pullrequestreviewcommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcommentconnection", - "/enterprise/v4/object/pullrequestreviewcommentedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcommentedge", - "/en/enterprise/v4/object/pullrequestreviewcommentedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcommentedge", - "/enterprise/v4/object/pullrequestreviewconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewconnection", - "/en/enterprise/v4/object/pullrequestreviewconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewconnection", - "/enterprise/v4/object/pullrequestreviewcontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", - "/en/enterprise/v4/object/pullrequestreviewcontributionsbyrepository": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", - "/enterprise/v4/object/pullrequestreviewedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewedge", - "/en/enterprise/v4/object/pullrequestreviewedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewedge", - "/enterprise/v4/object/pullrequestreviewthread": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthread", - "/en/enterprise/v4/object/pullrequestreviewthread": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthread", - "/enterprise/v4/object/pullrequestreviewthreadconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthreadconnection", - "/en/enterprise/v4/object/pullrequestreviewthreadconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthreadconnection", - "/enterprise/v4/object/pullrequestreviewthreadedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthreadedge", - "/en/enterprise/v4/object/pullrequestreviewthreadedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthreadedge", - "/enterprise/v4/object/pullrequestrevisionmarker": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestrevisionmarker", - "/en/enterprise/v4/object/pullrequestrevisionmarker": "/en/enterprise-server@latest/graphql/reference/objects#pullrequestrevisionmarker", - "/enterprise/v4/object/pullrequesttimelineconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineconnection", - "/en/enterprise/v4/object/pullrequesttimelineconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineconnection", - "/enterprise/v4/object/pullrequesttimelineitemedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemedge", - "/en/enterprise/v4/object/pullrequesttimelineitemedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemedge", - "/enterprise/v4/object/pullrequesttimelineitemsconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemsconnection", - "/en/enterprise/v4/object/pullrequesttimelineitemsconnection": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemsconnection", - "/enterprise/v4/object/pullrequesttimelineitemsedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemsedge", - "/en/enterprise/v4/object/pullrequesttimelineitemsedge": "/en/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemsedge", - "/enterprise/v4/object/push": "/en/enterprise-server@latest/graphql/reference/objects#push", - "/en/enterprise/v4/object/push": "/en/enterprise-server@latest/graphql/reference/objects#push", - "/enterprise/v4/object/pushallowance": "/en/enterprise-server@latest/graphql/reference/objects#pushallowance", - "/en/enterprise/v4/object/pushallowance": "/en/enterprise-server@latest/graphql/reference/objects#pushallowance", - "/enterprise/v4/object/pushallowanceconnection": "/en/enterprise-server@latest/graphql/reference/objects#pushallowanceconnection", - "/en/enterprise/v4/object/pushallowanceconnection": "/en/enterprise-server@latest/graphql/reference/objects#pushallowanceconnection", - "/enterprise/v4/object/pushallowanceedge": "/en/enterprise-server@latest/graphql/reference/objects#pushallowanceedge", - "/en/enterprise/v4/object/pushallowanceedge": "/en/enterprise-server@latest/graphql/reference/objects#pushallowanceedge", - "/enterprise/v4/object/ratelimit": "/en/enterprise-server@latest/graphql/reference/objects#ratelimit", - "/en/enterprise/v4/object/ratelimit": "/en/enterprise-server@latest/graphql/reference/objects#ratelimit", - "/enterprise/v4/object/reactinguserconnection": "/en/enterprise-server@latest/graphql/reference/objects#reactinguserconnection", - "/en/enterprise/v4/object/reactinguserconnection": "/en/enterprise-server@latest/graphql/reference/objects#reactinguserconnection", - "/enterprise/v4/object/reactinguseredge": "/en/enterprise-server@latest/graphql/reference/objects#reactinguseredge", - "/en/enterprise/v4/object/reactinguseredge": "/en/enterprise-server@latest/graphql/reference/objects#reactinguseredge", - "/enterprise/v4/object/reaction": "/en/enterprise-server@latest/graphql/reference/objects#reaction", - "/en/enterprise/v4/object/reaction": "/en/enterprise-server@latest/graphql/reference/objects#reaction", - "/enterprise/v4/object/reactionconnection": "/en/enterprise-server@latest/graphql/reference/objects#reactionconnection", - "/en/enterprise/v4/object/reactionconnection": "/en/enterprise-server@latest/graphql/reference/objects#reactionconnection", - "/enterprise/v4/object/reactionedge": "/en/enterprise-server@latest/graphql/reference/objects#reactionedge", - "/en/enterprise/v4/object/reactionedge": "/en/enterprise-server@latest/graphql/reference/objects#reactionedge", - "/enterprise/v4/object/reactiongroup": "/en/enterprise-server@latest/graphql/reference/objects#reactiongroup", - "/en/enterprise/v4/object/reactiongroup": "/en/enterprise-server@latest/graphql/reference/objects#reactiongroup", - "/enterprise/v4/object/readyforreviewevent": "/en/enterprise-server@latest/graphql/reference/objects#readyforreviewevent", - "/en/enterprise/v4/object/readyforreviewevent": "/en/enterprise-server@latest/graphql/reference/objects#readyforreviewevent", - "/enterprise/v4/object/ref": "/en/enterprise-server@latest/graphql/reference/objects#ref", - "/en/enterprise/v4/object/ref": "/en/enterprise-server@latest/graphql/reference/objects#ref", - "/enterprise/v4/object/refconnection": "/en/enterprise-server@latest/graphql/reference/objects#refconnection", - "/en/enterprise/v4/object/refconnection": "/en/enterprise-server@latest/graphql/reference/objects#refconnection", - "/enterprise/v4/object/refedge": "/en/enterprise-server@latest/graphql/reference/objects#refedge", - "/en/enterprise/v4/object/refedge": "/en/enterprise-server@latest/graphql/reference/objects#refedge", - "/enterprise/v4/object/referencedevent": "/en/enterprise-server@latest/graphql/reference/objects#referencedevent", - "/en/enterprise/v4/object/referencedevent": "/en/enterprise-server@latest/graphql/reference/objects#referencedevent", - "/enterprise/v4/object/registrypackage": "/en/enterprise-server@latest/graphql/reference/objects#registrypackage", - "/en/enterprise/v4/object/registrypackage": "/en/enterprise-server@latest/graphql/reference/objects#registrypackage", - "/enterprise/v4/object/registrypackageconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageconnection", - "/en/enterprise/v4/object/registrypackageconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageconnection", - "/enterprise/v4/object/registrypackagedependency": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagedependency", - "/en/enterprise/v4/object/registrypackagedependency": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagedependency", - "/enterprise/v4/object/registrypackagedependencyconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagedependencyconnection", - "/en/enterprise/v4/object/registrypackagedependencyconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagedependencyconnection", - "/enterprise/v4/object/registrypackagedependencyedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagedependencyedge", - "/en/enterprise/v4/object/registrypackagedependencyedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagedependencyedge", - "/enterprise/v4/object/registrypackageedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageedge", - "/en/enterprise/v4/object/registrypackageedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageedge", - "/enterprise/v4/object/registrypackagefile": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagefile", - "/en/enterprise/v4/object/registrypackagefile": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagefile", - "/enterprise/v4/object/registrypackagefileconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagefileconnection", - "/en/enterprise/v4/object/registrypackagefileconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagefileconnection", - "/enterprise/v4/object/registrypackagefileedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagefileedge", - "/en/enterprise/v4/object/registrypackagefileedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagefileedge", - "/enterprise/v4/object/registrypackagestatistics": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagestatistics", - "/en/enterprise/v4/object/registrypackagestatistics": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagestatistics", - "/enterprise/v4/object/registrypackagetag": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagetag", - "/en/enterprise/v4/object/registrypackagetag": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagetag", - "/enterprise/v4/object/registrypackagetagconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagetagconnection", - "/en/enterprise/v4/object/registrypackagetagconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagetagconnection", - "/enterprise/v4/object/registrypackagetagedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagetagedge", - "/en/enterprise/v4/object/registrypackagetagedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackagetagedge", - "/enterprise/v4/object/registrypackageversion": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversion", - "/en/enterprise/v4/object/registrypackageversion": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversion", - "/enterprise/v4/object/registrypackageversionconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversionconnection", - "/en/enterprise/v4/object/registrypackageversionconnection": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversionconnection", - "/enterprise/v4/object/registrypackageversionedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversionedge", - "/en/enterprise/v4/object/registrypackageversionedge": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversionedge", - "/enterprise/v4/object/registrypackageversionstatistics": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversionstatistics", - "/en/enterprise/v4/object/registrypackageversionstatistics": "/en/enterprise-server@latest/graphql/reference/objects#registrypackageversionstatistics", - "/enterprise/v4/object/release": "/en/enterprise-server@latest/graphql/reference/objects#release", - "/en/enterprise/v4/object/release": "/en/enterprise-server@latest/graphql/reference/objects#release", - "/enterprise/v4/object/releaseasset": "/en/enterprise-server@latest/graphql/reference/objects#releaseasset", - "/en/enterprise/v4/object/releaseasset": "/en/enterprise-server@latest/graphql/reference/objects#releaseasset", - "/enterprise/v4/object/releaseassetconnection": "/en/enterprise-server@latest/graphql/reference/objects#releaseassetconnection", - "/en/enterprise/v4/object/releaseassetconnection": "/en/enterprise-server@latest/graphql/reference/objects#releaseassetconnection", - "/enterprise/v4/object/releaseassetedge": "/en/enterprise-server@latest/graphql/reference/objects#releaseassetedge", - "/en/enterprise/v4/object/releaseassetedge": "/en/enterprise-server@latest/graphql/reference/objects#releaseassetedge", - "/enterprise/v4/object/releaseconnection": "/en/enterprise-server@latest/graphql/reference/objects#releaseconnection", - "/en/enterprise/v4/object/releaseconnection": "/en/enterprise-server@latest/graphql/reference/objects#releaseconnection", - "/enterprise/v4/object/releaseedge": "/en/enterprise-server@latest/graphql/reference/objects#releaseedge", - "/en/enterprise/v4/object/releaseedge": "/en/enterprise-server@latest/graphql/reference/objects#releaseedge", - "/enterprise/v4/object/removeassigneesfromassignablepayload": "/en/enterprise-server@latest/graphql/reference/objects#removeassigneesfromassignablepayload", - "/en/enterprise/v4/object/removeassigneesfromassignablepayload": "/en/enterprise-server@latest/graphql/reference/objects#removeassigneesfromassignablepayload", - "/enterprise/v4/object/removedfromprojectevent": "/en/enterprise-server@latest/graphql/reference/objects#removedfromprojectevent", - "/en/enterprise/v4/object/removedfromprojectevent": "/en/enterprise-server@latest/graphql/reference/objects#removedfromprojectevent", - "/enterprise/v4/object/removeenterpriseadminpayload": "/en/enterprise-server@latest/graphql/reference/objects#removeenterpriseadminpayload", - "/en/enterprise/v4/object/removeenterpriseadminpayload": "/en/enterprise-server@latest/graphql/reference/objects#removeenterpriseadminpayload", - "/enterprise/v4/object/removelabelsfromlabelablepayload": "/en/enterprise-server@latest/graphql/reference/objects#removelabelsfromlabelablepayload", - "/en/enterprise/v4/object/removelabelsfromlabelablepayload": "/en/enterprise-server@latest/graphql/reference/objects#removelabelsfromlabelablepayload", - "/enterprise/v4/object/removeoutsidecollaboratorpayload": "/en/enterprise-server@latest/graphql/reference/objects#removeoutsidecollaboratorpayload", - "/en/enterprise/v4/object/removeoutsidecollaboratorpayload": "/en/enterprise-server@latest/graphql/reference/objects#removeoutsidecollaboratorpayload", - "/enterprise/v4/object/removereactionpayload": "/en/enterprise-server@latest/graphql/reference/objects#removereactionpayload", - "/en/enterprise/v4/object/removereactionpayload": "/en/enterprise-server@latest/graphql/reference/objects#removereactionpayload", - "/enterprise/v4/object/removestarpayload": "/en/enterprise-server@latest/graphql/reference/objects#removestarpayload", - "/en/enterprise/v4/object/removestarpayload": "/en/enterprise-server@latest/graphql/reference/objects#removestarpayload", - "/enterprise/v4/object/renamedtitleevent": "/en/enterprise-server@latest/graphql/reference/objects#renamedtitleevent", - "/en/enterprise/v4/object/renamedtitleevent": "/en/enterprise-server@latest/graphql/reference/objects#renamedtitleevent", - "/enterprise/v4/object/reopenedevent": "/en/enterprise-server@latest/graphql/reference/objects#reopenedevent", - "/en/enterprise/v4/object/reopenedevent": "/en/enterprise-server@latest/graphql/reference/objects#reopenedevent", - "/enterprise/v4/object/reopenissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#reopenissuepayload", - "/en/enterprise/v4/object/reopenissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#reopenissuepayload", - "/enterprise/v4/object/reopenpullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#reopenpullrequestpayload", - "/en/enterprise/v4/object/reopenpullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#reopenpullrequestpayload", - "/enterprise/v4/object/repoaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoaccessauditentry", - "/en/enterprise/v4/object/repoaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoaccessauditentry", - "/enterprise/v4/object/repoaddmemberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoaddmemberauditentry", - "/en/enterprise/v4/object/repoaddmemberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoaddmemberauditentry", - "/enterprise/v4/object/repoaddtopicauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoaddtopicauditentry", - "/en/enterprise/v4/object/repoaddtopicauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoaddtopicauditentry", - "/enterprise/v4/object/repoarchivedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoarchivedauditentry", - "/en/enterprise/v4/object/repoarchivedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoarchivedauditentry", - "/enterprise/v4/object/repochangemergesettingauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repochangemergesettingauditentry", - "/en/enterprise/v4/object/repochangemergesettingauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repochangemergesettingauditentry", - "/enterprise/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", - "/en/enterprise/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", - "/enterprise/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", - "/en/enterprise/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", - "/enterprise/v4/object/repoconfigdisablecontributorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", - "/en/enterprise/v4/object/repoconfigdisablecontributorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", - "/enterprise/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", - "/en/enterprise/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", - "/enterprise/v4/object/repoconfigenableanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", - "/en/enterprise/v4/object/repoconfigenableanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", - "/enterprise/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", - "/en/enterprise/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", - "/enterprise/v4/object/repoconfigenablecontributorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", - "/en/enterprise/v4/object/repoconfigenablecontributorsonlyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", - "/enterprise/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", - "/en/enterprise/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", - "/enterprise/v4/object/repoconfiglockanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", - "/en/enterprise/v4/object/repoconfiglockanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", - "/enterprise/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", - "/en/enterprise/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", - "/enterprise/v4/object/repocreateauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repocreateauditentry", - "/en/enterprise/v4/object/repocreateauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repocreateauditentry", - "/enterprise/v4/object/repodestroyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repodestroyauditentry", - "/en/enterprise/v4/object/repodestroyauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repodestroyauditentry", - "/enterprise/v4/object/reporemovememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#reporemovememberauditentry", - "/en/enterprise/v4/object/reporemovememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#reporemovememberauditentry", - "/enterprise/v4/object/reporemovetopicauditentry": "/en/enterprise-server@latest/graphql/reference/objects#reporemovetopicauditentry", - "/en/enterprise/v4/object/reporemovetopicauditentry": "/en/enterprise-server@latest/graphql/reference/objects#reporemovetopicauditentry", - "/enterprise/v4/object/repository": "/en/enterprise-server@latest/graphql/reference/objects#repository", - "/en/enterprise/v4/object/repository": "/en/enterprise-server@latest/graphql/reference/objects#repository", - "/enterprise/v4/object/repositorycollaboratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositorycollaboratorconnection", - "/en/enterprise/v4/object/repositorycollaboratorconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositorycollaboratorconnection", - "/enterprise/v4/object/repositorycollaboratoredge": "/en/enterprise-server@latest/graphql/reference/objects#repositorycollaboratoredge", - "/en/enterprise/v4/object/repositorycollaboratoredge": "/en/enterprise-server@latest/graphql/reference/objects#repositorycollaboratoredge", - "/enterprise/v4/object/repositoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositoryconnection", - "/en/enterprise/v4/object/repositoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositoryconnection", - "/enterprise/v4/object/repositoryedge": "/en/enterprise-server@latest/graphql/reference/objects#repositoryedge", - "/en/enterprise/v4/object/repositoryedge": "/en/enterprise-server@latest/graphql/reference/objects#repositoryedge", - "/enterprise/v4/object/repositoryinvitation": "/en/enterprise-server@latest/graphql/reference/objects#repositoryinvitation", - "/en/enterprise/v4/object/repositoryinvitation": "/en/enterprise-server@latest/graphql/reference/objects#repositoryinvitation", - "/enterprise/v4/object/repositorytopic": "/en/enterprise-server@latest/graphql/reference/objects#repositorytopic", - "/en/enterprise/v4/object/repositorytopic": "/en/enterprise-server@latest/graphql/reference/objects#repositorytopic", - "/enterprise/v4/object/repositorytopicconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositorytopicconnection", - "/en/enterprise/v4/object/repositorytopicconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositorytopicconnection", - "/enterprise/v4/object/repositorytopicedge": "/en/enterprise-server@latest/graphql/reference/objects#repositorytopicedge", - "/en/enterprise/v4/object/repositorytopicedge": "/en/enterprise-server@latest/graphql/reference/objects#repositorytopicedge", - "/enterprise/v4/object/repositoryvisibilitychangedisableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", - "/en/enterprise/v4/object/repositoryvisibilitychangedisableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", - "/enterprise/v4/object/repositoryvisibilitychangeenableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", - "/en/enterprise/v4/object/repositoryvisibilitychangeenableauditentry": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", - "/enterprise/v4/object/repositoryvulnerabilityalert": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalert", - "/en/enterprise/v4/object/repositoryvulnerabilityalert": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalert", - "/enterprise/v4/object/repositoryvulnerabilityalertconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalertconnection", - "/en/enterprise/v4/object/repositoryvulnerabilityalertconnection": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalertconnection", - "/enterprise/v4/object/repositoryvulnerabilityalertedge": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalertedge", - "/en/enterprise/v4/object/repositoryvulnerabilityalertedge": "/en/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalertedge", - "/enterprise/v4/object/requestreviewspayload": "/en/enterprise-server@latest/graphql/reference/objects#requestreviewspayload", - "/en/enterprise/v4/object/requestreviewspayload": "/en/enterprise-server@latest/graphql/reference/objects#requestreviewspayload", - "/enterprise/v4/object/rerequestchecksuitepayload": "/en/enterprise-server@latest/graphql/reference/objects#rerequestchecksuitepayload", - "/en/enterprise/v4/object/rerequestchecksuitepayload": "/en/enterprise-server@latest/graphql/reference/objects#rerequestchecksuitepayload", - "/enterprise/v4/object/resolvereviewthreadpayload": "/en/enterprise-server@latest/graphql/reference/objects#resolvereviewthreadpayload", - "/en/enterprise/v4/object/resolvereviewthreadpayload": "/en/enterprise-server@latest/graphql/reference/objects#resolvereviewthreadpayload", - "/enterprise/v4/object/restrictedcontribution": "/en/enterprise-server@latest/graphql/reference/objects#restrictedcontribution", - "/en/enterprise/v4/object/restrictedcontribution": "/en/enterprise-server@latest/graphql/reference/objects#restrictedcontribution", - "/enterprise/v4/object/reviewdismissalallowance": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowance", - "/en/enterprise/v4/object/reviewdismissalallowance": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowance", - "/enterprise/v4/object/reviewdismissalallowanceconnection": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowanceconnection", - "/en/enterprise/v4/object/reviewdismissalallowanceconnection": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowanceconnection", - "/enterprise/v4/object/reviewdismissalallowanceedge": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowanceedge", - "/en/enterprise/v4/object/reviewdismissalallowanceedge": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowanceedge", - "/enterprise/v4/object/reviewdismissedevent": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissedevent", - "/en/enterprise/v4/object/reviewdismissedevent": "/en/enterprise-server@latest/graphql/reference/objects#reviewdismissedevent", - "/enterprise/v4/object/reviewrequest": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequest", - "/en/enterprise/v4/object/reviewrequest": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequest", - "/enterprise/v4/object/reviewrequestconnection": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestconnection", - "/en/enterprise/v4/object/reviewrequestconnection": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestconnection", - "/enterprise/v4/object/reviewrequestedevent": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestedevent", - "/en/enterprise/v4/object/reviewrequestedevent": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestedevent", - "/enterprise/v4/object/reviewrequestedge": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestedge", - "/en/enterprise/v4/object/reviewrequestedge": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestedge", - "/enterprise/v4/object/reviewrequestremovedevent": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestremovedevent", - "/en/enterprise/v4/object/reviewrequestremovedevent": "/en/enterprise-server@latest/graphql/reference/objects#reviewrequestremovedevent", - "/enterprise/v4/object/reviewstatushovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#reviewstatushovercardcontext", - "/en/enterprise/v4/object/reviewstatushovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#reviewstatushovercardcontext", - "/enterprise/v4/object/savedreply": "/en/enterprise-server@latest/graphql/reference/objects#savedreply", - "/en/enterprise/v4/object/savedreply": "/en/enterprise-server@latest/graphql/reference/objects#savedreply", - "/enterprise/v4/object/savedreplyconnection": "/en/enterprise-server@latest/graphql/reference/objects#savedreplyconnection", - "/en/enterprise/v4/object/savedreplyconnection": "/en/enterprise-server@latest/graphql/reference/objects#savedreplyconnection", - "/enterprise/v4/object/savedreplyedge": "/en/enterprise-server@latest/graphql/reference/objects#savedreplyedge", - "/en/enterprise/v4/object/savedreplyedge": "/en/enterprise-server@latest/graphql/reference/objects#savedreplyedge", - "/enterprise/v4/object/searchresultitemconnection": "/en/enterprise-server@latest/graphql/reference/objects#searchresultitemconnection", - "/en/enterprise/v4/object/searchresultitemconnection": "/en/enterprise-server@latest/graphql/reference/objects#searchresultitemconnection", - "/enterprise/v4/object/searchresultitemedge": "/en/enterprise-server@latest/graphql/reference/objects#searchresultitemedge", - "/en/enterprise/v4/object/searchresultitemedge": "/en/enterprise-server@latest/graphql/reference/objects#searchresultitemedge", - "/enterprise/v4/object/securityadvisory": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisory", - "/en/enterprise/v4/object/securityadvisory": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisory", - "/enterprise/v4/object/securityadvisoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryconnection", - "/en/enterprise/v4/object/securityadvisoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryconnection", - "/enterprise/v4/object/securityadvisoryedge": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryedge", - "/en/enterprise/v4/object/securityadvisoryedge": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryedge", - "/enterprise/v4/object/securityadvisoryidentifier": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryidentifier", - "/en/enterprise/v4/object/securityadvisoryidentifier": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryidentifier", - "/enterprise/v4/object/securityadvisorypackage": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisorypackage", - "/en/enterprise/v4/object/securityadvisorypackage": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisorypackage", - "/enterprise/v4/object/securityadvisorypackageversion": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisorypackageversion", - "/en/enterprise/v4/object/securityadvisorypackageversion": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisorypackageversion", - "/enterprise/v4/object/securityadvisoryreference": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryreference", - "/en/enterprise/v4/object/securityadvisoryreference": "/en/enterprise-server@latest/graphql/reference/objects#securityadvisoryreference", - "/enterprise/v4/object/securityvulnerability": "/en/enterprise-server@latest/graphql/reference/objects#securityvulnerability", - "/en/enterprise/v4/object/securityvulnerability": "/en/enterprise-server@latest/graphql/reference/objects#securityvulnerability", - "/enterprise/v4/object/securityvulnerabilityconnection": "/en/enterprise-server@latest/graphql/reference/objects#securityvulnerabilityconnection", - "/en/enterprise/v4/object/securityvulnerabilityconnection": "/en/enterprise-server@latest/graphql/reference/objects#securityvulnerabilityconnection", - "/enterprise/v4/object/securityvulnerabilityedge": "/en/enterprise-server@latest/graphql/reference/objects#securityvulnerabilityedge", - "/en/enterprise/v4/object/securityvulnerabilityedge": "/en/enterprise-server@latest/graphql/reference/objects#securityvulnerabilityedge", - "/enterprise/v4/object/smimesignature": "/en/enterprise-server@latest/graphql/reference/objects#smimesignature", - "/en/enterprise/v4/object/smimesignature": "/en/enterprise-server@latest/graphql/reference/objects#smimesignature", - "/enterprise/v4/object/sponsorship": "/en/enterprise-server@latest/graphql/reference/objects#sponsorship", - "/en/enterprise/v4/object/sponsorship": "/en/enterprise-server@latest/graphql/reference/objects#sponsorship", - "/enterprise/v4/object/sponsorshipconnection": "/en/enterprise-server@latest/graphql/reference/objects#sponsorshipconnection", - "/en/enterprise/v4/object/sponsorshipconnection": "/en/enterprise-server@latest/graphql/reference/objects#sponsorshipconnection", - "/enterprise/v4/object/sponsorshipedge": "/en/enterprise-server@latest/graphql/reference/objects#sponsorshipedge", - "/en/enterprise/v4/object/sponsorshipedge": "/en/enterprise-server@latest/graphql/reference/objects#sponsorshipedge", - "/enterprise/v4/object/stargazerconnection": "/en/enterprise-server@latest/graphql/reference/objects#stargazerconnection", - "/en/enterprise/v4/object/stargazerconnection": "/en/enterprise-server@latest/graphql/reference/objects#stargazerconnection", - "/enterprise/v4/object/stargazeredge": "/en/enterprise-server@latest/graphql/reference/objects#stargazeredge", - "/en/enterprise/v4/object/stargazeredge": "/en/enterprise-server@latest/graphql/reference/objects#stargazeredge", - "/enterprise/v4/object/starredrepositoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#starredrepositoryconnection", - "/en/enterprise/v4/object/starredrepositoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#starredrepositoryconnection", - "/enterprise/v4/object/starredrepositoryedge": "/en/enterprise-server@latest/graphql/reference/objects#starredrepositoryedge", - "/en/enterprise/v4/object/starredrepositoryedge": "/en/enterprise-server@latest/graphql/reference/objects#starredrepositoryedge", - "/enterprise/v4/object/status": "/en/enterprise-server@latest/graphql/reference/objects#status", - "/en/enterprise/v4/object/status": "/en/enterprise-server@latest/graphql/reference/objects#status", - "/enterprise/v4/object/statuscheckrollup": "/en/enterprise-server@latest/graphql/reference/objects#statuscheckrollup", - "/en/enterprise/v4/object/statuscheckrollup": "/en/enterprise-server@latest/graphql/reference/objects#statuscheckrollup", - "/enterprise/v4/object/statuscheckrollupcontextconnection": "/en/enterprise-server@latest/graphql/reference/objects#statuscheckrollupcontextconnection", - "/en/enterprise/v4/object/statuscheckrollupcontextconnection": "/en/enterprise-server@latest/graphql/reference/objects#statuscheckrollupcontextconnection", - "/enterprise/v4/object/statuscheckrollupcontextedge": "/en/enterprise-server@latest/graphql/reference/objects#statuscheckrollupcontextedge", - "/en/enterprise/v4/object/statuscheckrollupcontextedge": "/en/enterprise-server@latest/graphql/reference/objects#statuscheckrollupcontextedge", - "/enterprise/v4/object/statuscontext": "/en/enterprise-server@latest/graphql/reference/objects#statuscontext", - "/en/enterprise/v4/object/statuscontext": "/en/enterprise-server@latest/graphql/reference/objects#statuscontext", - "/enterprise/v4/object/submitpullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#submitpullrequestreviewpayload", - "/en/enterprise/v4/object/submitpullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#submitpullrequestreviewpayload", - "/enterprise/v4/object/submodule": "/en/enterprise-server@latest/graphql/reference/objects#submodule", - "/en/enterprise/v4/object/submodule": "/en/enterprise-server@latest/graphql/reference/objects#submodule", - "/enterprise/v4/object/submoduleconnection": "/en/enterprise-server@latest/graphql/reference/objects#submoduleconnection", - "/en/enterprise/v4/object/submoduleconnection": "/en/enterprise-server@latest/graphql/reference/objects#submoduleconnection", - "/enterprise/v4/object/submoduleedge": "/en/enterprise-server@latest/graphql/reference/objects#submoduleedge", - "/en/enterprise/v4/object/submoduleedge": "/en/enterprise-server@latest/graphql/reference/objects#submoduleedge", - "/enterprise/v4/object/subscribedevent": "/en/enterprise-server@latest/graphql/reference/objects#subscribedevent", - "/en/enterprise/v4/object/subscribedevent": "/en/enterprise-server@latest/graphql/reference/objects#subscribedevent", - "/enterprise/v4/object/suggestedreviewer": "/en/enterprise-server@latest/graphql/reference/objects#suggestedreviewer", - "/en/enterprise/v4/object/suggestedreviewer": "/en/enterprise-server@latest/graphql/reference/objects#suggestedreviewer", - "/enterprise/v4/object/tag": "/en/enterprise-server@latest/graphql/reference/objects#tag", - "/en/enterprise/v4/object/tag": "/en/enterprise-server@latest/graphql/reference/objects#tag", - "/enterprise/v4/object/team": "/en/enterprise-server@latest/graphql/reference/objects#team", - "/en/enterprise/v4/object/team": "/en/enterprise-server@latest/graphql/reference/objects#team", - "/enterprise/v4/object/teamaddmemberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamaddmemberauditentry", - "/en/enterprise/v4/object/teamaddmemberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamaddmemberauditentry", - "/enterprise/v4/object/teamaddrepositoryauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamaddrepositoryauditentry", - "/en/enterprise/v4/object/teamaddrepositoryauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamaddrepositoryauditentry", - "/enterprise/v4/object/teamchangeparentteamauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamchangeparentteamauditentry", - "/en/enterprise/v4/object/teamchangeparentteamauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamchangeparentteamauditentry", - "/enterprise/v4/object/teamconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamconnection", - "/en/enterprise/v4/object/teamconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamconnection", - "/enterprise/v4/object/teamdiscussion": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussion", - "/en/enterprise/v4/object/teamdiscussion": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussion", - "/enterprise/v4/object/teamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussioncomment", - "/en/enterprise/v4/object/teamdiscussioncomment": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussioncomment", - "/enterprise/v4/object/teamdiscussioncommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussioncommentconnection", - "/en/enterprise/v4/object/teamdiscussioncommentconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussioncommentconnection", - "/enterprise/v4/object/teamdiscussioncommentedge": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussioncommentedge", - "/en/enterprise/v4/object/teamdiscussioncommentedge": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussioncommentedge", - "/enterprise/v4/object/teamdiscussionconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussionconnection", - "/en/enterprise/v4/object/teamdiscussionconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussionconnection", - "/enterprise/v4/object/teamdiscussionedge": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussionedge", - "/en/enterprise/v4/object/teamdiscussionedge": "/en/enterprise-server@latest/graphql/reference/objects#teamdiscussionedge", - "/enterprise/v4/object/teamedge": "/en/enterprise-server@latest/graphql/reference/objects#teamedge", - "/en/enterprise/v4/object/teamedge": "/en/enterprise-server@latest/graphql/reference/objects#teamedge", - "/enterprise/v4/object/teammemberconnection": "/en/enterprise-server@latest/graphql/reference/objects#teammemberconnection", - "/en/enterprise/v4/object/teammemberconnection": "/en/enterprise-server@latest/graphql/reference/objects#teammemberconnection", - "/enterprise/v4/object/teammemberedge": "/en/enterprise-server@latest/graphql/reference/objects#teammemberedge", - "/en/enterprise/v4/object/teammemberedge": "/en/enterprise-server@latest/graphql/reference/objects#teammemberedge", - "/enterprise/v4/object/teamremovememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamremovememberauditentry", - "/en/enterprise/v4/object/teamremovememberauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamremovememberauditentry", - "/enterprise/v4/object/teamremoverepositoryauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamremoverepositoryauditentry", - "/en/enterprise/v4/object/teamremoverepositoryauditentry": "/en/enterprise-server@latest/graphql/reference/objects#teamremoverepositoryauditentry", - "/enterprise/v4/object/teamrepositoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamrepositoryconnection", - "/en/enterprise/v4/object/teamrepositoryconnection": "/en/enterprise-server@latest/graphql/reference/objects#teamrepositoryconnection", - "/enterprise/v4/object/teamrepositoryedge": "/en/enterprise-server@latest/graphql/reference/objects#teamrepositoryedge", - "/en/enterprise/v4/object/teamrepositoryedge": "/en/enterprise-server@latest/graphql/reference/objects#teamrepositoryedge", - "/enterprise/v4/object/textmatch": "/en/enterprise-server@latest/graphql/reference/objects#textmatch", - "/en/enterprise/v4/object/textmatch": "/en/enterprise-server@latest/graphql/reference/objects#textmatch", - "/enterprise/v4/object/textmatchhighlight": "/en/enterprise-server@latest/graphql/reference/objects#textmatchhighlight", - "/en/enterprise/v4/object/textmatchhighlight": "/en/enterprise-server@latest/graphql/reference/objects#textmatchhighlight", - "/enterprise/v4/object/topic": "/en/enterprise-server@latest/graphql/reference/objects#topic", - "/en/enterprise/v4/object/topic": "/en/enterprise-server@latest/graphql/reference/objects#topic", - "/enterprise/v4/object/topicconnection": "/en/enterprise-server@latest/graphql/reference/objects#topicconnection", - "/en/enterprise/v4/object/topicconnection": "/en/enterprise-server@latest/graphql/reference/objects#topicconnection", - "/enterprise/v4/object/topicedge": "/en/enterprise-server@latest/graphql/reference/objects#topicedge", - "/en/enterprise/v4/object/topicedge": "/en/enterprise-server@latest/graphql/reference/objects#topicedge", - "/enterprise/v4/object/transferissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#transferissuepayload", - "/en/enterprise/v4/object/transferissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#transferissuepayload", - "/enterprise/v4/object/transferredevent": "/en/enterprise-server@latest/graphql/reference/objects#transferredevent", - "/en/enterprise/v4/object/transferredevent": "/en/enterprise-server@latest/graphql/reference/objects#transferredevent", - "/enterprise/v4/object/tree": "/en/enterprise-server@latest/graphql/reference/objects#tree", - "/en/enterprise/v4/object/tree": "/en/enterprise-server@latest/graphql/reference/objects#tree", - "/enterprise/v4/object/treeentry": "/en/enterprise-server@latest/graphql/reference/objects#treeentry", - "/en/enterprise/v4/object/treeentry": "/en/enterprise-server@latest/graphql/reference/objects#treeentry", - "/enterprise/v4/object/unarchiverepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#unarchiverepositorypayload", - "/en/enterprise/v4/object/unarchiverepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#unarchiverepositorypayload", - "/enterprise/v4/object/unassignedevent": "/en/enterprise-server@latest/graphql/reference/objects#unassignedevent", - "/en/enterprise/v4/object/unassignedevent": "/en/enterprise-server@latest/graphql/reference/objects#unassignedevent", - "/enterprise/v4/object/unfollowuserpayload": "/en/enterprise-server@latest/graphql/reference/objects#unfollowuserpayload", - "/en/enterprise/v4/object/unfollowuserpayload": "/en/enterprise-server@latest/graphql/reference/objects#unfollowuserpayload", - "/enterprise/v4/object/unknownsignature": "/en/enterprise-server@latest/graphql/reference/objects#unknownsignature", - "/en/enterprise/v4/object/unknownsignature": "/en/enterprise-server@latest/graphql/reference/objects#unknownsignature", - "/enterprise/v4/object/unlabeledevent": "/en/enterprise-server@latest/graphql/reference/objects#unlabeledevent", - "/en/enterprise/v4/object/unlabeledevent": "/en/enterprise-server@latest/graphql/reference/objects#unlabeledevent", - "/enterprise/v4/object/unlinkrepositoryfromprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#unlinkrepositoryfromprojectpayload", - "/en/enterprise/v4/object/unlinkrepositoryfromprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#unlinkrepositoryfromprojectpayload", - "/enterprise/v4/object/unlockedevent": "/en/enterprise-server@latest/graphql/reference/objects#unlockedevent", - "/en/enterprise/v4/object/unlockedevent": "/en/enterprise-server@latest/graphql/reference/objects#unlockedevent", - "/enterprise/v4/object/unlocklockablepayload": "/en/enterprise-server@latest/graphql/reference/objects#unlocklockablepayload", - "/en/enterprise/v4/object/unlocklockablepayload": "/en/enterprise-server@latest/graphql/reference/objects#unlocklockablepayload", - "/enterprise/v4/object/unmarkedasduplicateevent": "/en/enterprise-server@latest/graphql/reference/objects#unmarkedasduplicateevent", - "/en/enterprise/v4/object/unmarkedasduplicateevent": "/en/enterprise-server@latest/graphql/reference/objects#unmarkedasduplicateevent", - "/enterprise/v4/object/unmarkissueasduplicatepayload": "/en/enterprise-server@latest/graphql/reference/objects#unmarkissueasduplicatepayload", - "/en/enterprise/v4/object/unmarkissueasduplicatepayload": "/en/enterprise-server@latest/graphql/reference/objects#unmarkissueasduplicatepayload", - "/enterprise/v4/object/unminimizecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#unminimizecommentpayload", - "/en/enterprise/v4/object/unminimizecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#unminimizecommentpayload", - "/enterprise/v4/object/unpinissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#unpinissuepayload", - "/en/enterprise/v4/object/unpinissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#unpinissuepayload", - "/enterprise/v4/object/unpinnedevent": "/en/enterprise-server@latest/graphql/reference/objects#unpinnedevent", - "/en/enterprise/v4/object/unpinnedevent": "/en/enterprise-server@latest/graphql/reference/objects#unpinnedevent", - "/enterprise/v4/object/unresolvereviewthreadpayload": "/en/enterprise-server@latest/graphql/reference/objects#unresolvereviewthreadpayload", - "/en/enterprise/v4/object/unresolvereviewthreadpayload": "/en/enterprise-server@latest/graphql/reference/objects#unresolvereviewthreadpayload", - "/enterprise/v4/object/unsubscribedevent": "/en/enterprise-server@latest/graphql/reference/objects#unsubscribedevent", - "/en/enterprise/v4/object/unsubscribedevent": "/en/enterprise-server@latest/graphql/reference/objects#unsubscribedevent", - "/enterprise/v4/object/updatebranchprotectionrulepayload": "/en/enterprise-server@latest/graphql/reference/objects#updatebranchprotectionrulepayload", - "/en/enterprise/v4/object/updatebranchprotectionrulepayload": "/en/enterprise-server@latest/graphql/reference/objects#updatebranchprotectionrulepayload", - "/enterprise/v4/object/updatecheckrunpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatecheckrunpayload", - "/en/enterprise/v4/object/updatecheckrunpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatecheckrunpayload", - "/enterprise/v4/object/updatechecksuitepreferencespayload": "/en/enterprise-server@latest/graphql/reference/objects#updatechecksuitepreferencespayload", - "/en/enterprise/v4/object/updatechecksuitepreferencespayload": "/en/enterprise-server@latest/graphql/reference/objects#updatechecksuitepreferencespayload", - "/enterprise/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", - "/en/enterprise/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", - "/enterprise/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", - "/en/enterprise/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", - "/enterprise/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", - "/en/enterprise/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", - "/enterprise/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", - "/enterprise/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", - "/enterprise/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", - "/enterprise/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", - "/enterprise/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", - "/enterprise/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", - "/enterprise/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", - "/enterprise/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", - "/en/enterprise/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", - "/enterprise/v4/object/updateenterpriseorganizationprojectssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", - "/en/enterprise/v4/object/updateenterpriseorganizationprojectssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", - "/enterprise/v4/object/updateenterpriseprofilepayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseprofilepayload", - "/en/enterprise/v4/object/updateenterpriseprofilepayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseprofilepayload", - "/enterprise/v4/object/updateenterpriserepositoryprojectssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", - "/en/enterprise/v4/object/updateenterpriserepositoryprojectssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", - "/enterprise/v4/object/updateenterpriseteamdiscussionssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", - "/en/enterprise/v4/object/updateenterpriseteamdiscussionssettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", - "/enterprise/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", - "/en/enterprise/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", - "/enterprise/v4/object/updateipallowlistenabledsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateipallowlistenabledsettingpayload", - "/en/enterprise/v4/object/updateipallowlistenabledsettingpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateipallowlistenabledsettingpayload", - "/enterprise/v4/object/updateipallowlistentrypayload": "/en/enterprise-server@latest/graphql/reference/objects#updateipallowlistentrypayload", - "/en/enterprise/v4/object/updateipallowlistentrypayload": "/en/enterprise-server@latest/graphql/reference/objects#updateipallowlistentrypayload", - "/enterprise/v4/object/updateissuecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateissuecommentpayload", - "/en/enterprise/v4/object/updateissuecommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateissuecommentpayload", - "/enterprise/v4/object/updateissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#updateissuepayload", - "/en/enterprise/v4/object/updateissuepayload": "/en/enterprise-server@latest/graphql/reference/objects#updateissuepayload", - "/enterprise/v4/object/updatelabelpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatelabelpayload", - "/en/enterprise/v4/object/updatelabelpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatelabelpayload", - "/enterprise/v4/object/updateprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateprojectcardpayload", - "/en/enterprise/v4/object/updateprojectcardpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateprojectcardpayload", - "/enterprise/v4/object/updateprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateprojectcolumnpayload", - "/en/enterprise/v4/object/updateprojectcolumnpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateprojectcolumnpayload", - "/enterprise/v4/object/updateprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateprojectpayload", - "/en/enterprise/v4/object/updateprojectpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateprojectpayload", - "/enterprise/v4/object/updatepullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatepullrequestpayload", - "/en/enterprise/v4/object/updatepullrequestpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatepullrequestpayload", - "/enterprise/v4/object/updatepullrequestreviewcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatepullrequestreviewcommentpayload", - "/en/enterprise/v4/object/updatepullrequestreviewcommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatepullrequestreviewcommentpayload", - "/enterprise/v4/object/updatepullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatepullrequestreviewpayload", - "/en/enterprise/v4/object/updatepullrequestreviewpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatepullrequestreviewpayload", - "/enterprise/v4/object/updaterefpayload": "/en/enterprise-server@latest/graphql/reference/objects#updaterefpayload", - "/en/enterprise/v4/object/updaterefpayload": "/en/enterprise-server@latest/graphql/reference/objects#updaterefpayload", - "/enterprise/v4/object/updaterefspayload": "/en/enterprise-server@latest/graphql/reference/objects#updaterefspayload", - "/en/enterprise/v4/object/updaterefspayload": "/en/enterprise-server@latest/graphql/reference/objects#updaterefspayload", - "/enterprise/v4/object/updaterepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#updaterepositorypayload", - "/en/enterprise/v4/object/updaterepositorypayload": "/en/enterprise-server@latest/graphql/reference/objects#updaterepositorypayload", - "/enterprise/v4/object/updatesubscriptionpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatesubscriptionpayload", - "/en/enterprise/v4/object/updatesubscriptionpayload": "/en/enterprise-server@latest/graphql/reference/objects#updatesubscriptionpayload", - "/enterprise/v4/object/updateteamdiscussioncommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateteamdiscussioncommentpayload", - "/en/enterprise/v4/object/updateteamdiscussioncommentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateteamdiscussioncommentpayload", - "/enterprise/v4/object/updateteamdiscussionpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateteamdiscussionpayload", - "/en/enterprise/v4/object/updateteamdiscussionpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateteamdiscussionpayload", - "/enterprise/v4/object/updateteamreviewassignmentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateteamreviewassignmentpayload", - "/en/enterprise/v4/object/updateteamreviewassignmentpayload": "/en/enterprise-server@latest/graphql/reference/objects#updateteamreviewassignmentpayload", - "/enterprise/v4/object/updatetopicspayload": "/en/enterprise-server@latest/graphql/reference/objects#updatetopicspayload", - "/en/enterprise/v4/object/updatetopicspayload": "/en/enterprise-server@latest/graphql/reference/objects#updatetopicspayload", - "/enterprise/v4/object/user": "/en/enterprise-server@latest/graphql/reference/objects#user", - "/en/enterprise/v4/object/user": "/en/enterprise-server@latest/graphql/reference/objects#user", - "/enterprise/v4/object/userblockedevent": "/en/enterprise-server@latest/graphql/reference/objects#userblockedevent", - "/en/enterprise/v4/object/userblockedevent": "/en/enterprise-server@latest/graphql/reference/objects#userblockedevent", - "/enterprise/v4/object/userconnection": "/en/enterprise-server@latest/graphql/reference/objects#userconnection", - "/en/enterprise/v4/object/userconnection": "/en/enterprise-server@latest/graphql/reference/objects#userconnection", - "/enterprise/v4/object/usercontentedit": "/en/enterprise-server@latest/graphql/reference/objects#usercontentedit", - "/en/enterprise/v4/object/usercontentedit": "/en/enterprise-server@latest/graphql/reference/objects#usercontentedit", - "/enterprise/v4/object/usercontenteditconnection": "/en/enterprise-server@latest/graphql/reference/objects#usercontenteditconnection", - "/en/enterprise/v4/object/usercontenteditconnection": "/en/enterprise-server@latest/graphql/reference/objects#usercontenteditconnection", - "/enterprise/v4/object/usercontenteditedge": "/en/enterprise-server@latest/graphql/reference/objects#usercontenteditedge", - "/en/enterprise/v4/object/usercontenteditedge": "/en/enterprise-server@latest/graphql/reference/objects#usercontenteditedge", - "/enterprise/v4/object/useredge": "/en/enterprise-server@latest/graphql/reference/objects#useredge", - "/en/enterprise/v4/object/useredge": "/en/enterprise-server@latest/graphql/reference/objects#useredge", - "/enterprise/v4/object/userstatus": "/en/enterprise-server@latest/graphql/reference/objects#userstatus", - "/en/enterprise/v4/object/userstatus": "/en/enterprise-server@latest/graphql/reference/objects#userstatus", - "/enterprise/v4/object/userstatusconnection": "/en/enterprise-server@latest/graphql/reference/objects#userstatusconnection", - "/en/enterprise/v4/object/userstatusconnection": "/en/enterprise-server@latest/graphql/reference/objects#userstatusconnection", - "/enterprise/v4/object/userstatusedge": "/en/enterprise-server@latest/graphql/reference/objects#userstatusedge", - "/en/enterprise/v4/object/userstatusedge": "/en/enterprise-server@latest/graphql/reference/objects#userstatusedge", - "/enterprise/v4/object/viewerhovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#viewerhovercardcontext", - "/en/enterprise/v4/object/viewerhovercardcontext": "/en/enterprise-server@latest/graphql/reference/objects#viewerhovercardcontext", - "/enterprise/v4/scalar/boolean": "/en/enterprise-server@latest/graphql/reference/scalars#boolean", - "/en/enterprise/v4/scalar/boolean": "/en/enterprise-server@latest/graphql/reference/scalars#boolean", - "/enterprise/v4/scalar/date": "/en/enterprise-server@latest/graphql/reference/scalars#date", - "/en/enterprise/v4/scalar/date": "/en/enterprise-server@latest/graphql/reference/scalars#date", - "/enterprise/v4/scalar/datetime": "/en/enterprise-server@latest/graphql/reference/scalars#datetime", - "/en/enterprise/v4/scalar/datetime": "/en/enterprise-server@latest/graphql/reference/scalars#datetime", - "/enterprise/v4/scalar/float": "/en/enterprise-server@latest/graphql/reference/scalars#float", - "/en/enterprise/v4/scalar/float": "/en/enterprise-server@latest/graphql/reference/scalars#float", - "/enterprise/v4/scalar/gitobjectid": "/en/enterprise-server@latest/graphql/reference/scalars#gitobjectid", - "/en/enterprise/v4/scalar/gitobjectid": "/en/enterprise-server@latest/graphql/reference/scalars#gitobjectid", - "/enterprise/v4/scalar/gitrefname": "/en/enterprise-server@latest/graphql/reference/scalars#gitrefname", - "/en/enterprise/v4/scalar/gitrefname": "/en/enterprise-server@latest/graphql/reference/scalars#gitrefname", - "/enterprise/v4/scalar/gitsshremote": "/en/enterprise-server@latest/graphql/reference/scalars#gitsshremote", - "/en/enterprise/v4/scalar/gitsshremote": "/en/enterprise-server@latest/graphql/reference/scalars#gitsshremote", - "/enterprise/v4/scalar/gittimestamp": "/en/enterprise-server@latest/graphql/reference/scalars#gittimestamp", - "/en/enterprise/v4/scalar/gittimestamp": "/en/enterprise-server@latest/graphql/reference/scalars#gittimestamp", - "/enterprise/v4/scalar/html": "/en/enterprise-server@latest/graphql/reference/scalars#html", - "/en/enterprise/v4/scalar/html": "/en/enterprise-server@latest/graphql/reference/scalars#html", - "/enterprise/v4/scalar/id": "/en/enterprise-server@latest/graphql/reference/scalars#id", - "/en/enterprise/v4/scalar/id": "/en/enterprise-server@latest/graphql/reference/scalars#id", - "/enterprise/v4/scalar/int": "/en/enterprise-server@latest/graphql/reference/scalars#int", - "/en/enterprise/v4/scalar/int": "/en/enterprise-server@latest/graphql/reference/scalars#int", - "/enterprise/v4/scalar/precisedatetime": "/en/enterprise-server@latest/graphql/reference/scalars#precisedatetime", - "/en/enterprise/v4/scalar/precisedatetime": "/en/enterprise-server@latest/graphql/reference/scalars#precisedatetime", - "/enterprise/v4/scalar/string": "/en/enterprise-server@latest/graphql/reference/scalars#string", - "/en/enterprise/v4/scalar/string": "/en/enterprise-server@latest/graphql/reference/scalars#string", - "/enterprise/v4/scalar/uri": "/en/enterprise-server@latest/graphql/reference/scalars#uri", - "/en/enterprise/v4/scalar/uri": "/en/enterprise-server@latest/graphql/reference/scalars#uri", - "/enterprise/v4/scalar/x509certificate": "/en/enterprise-server@latest/graphql/reference/scalars#x509certificate", - "/en/enterprise/v4/scalar/x509certificate": "/en/enterprise-server@latest/graphql/reference/scalars#x509certificate", - "/enterprise/v4/union/assignee": "/en/enterprise-server@latest/graphql/reference/unions#assignee", - "/en/enterprise/v4/union/assignee": "/en/enterprise-server@latest/graphql/reference/unions#assignee", - "/enterprise/v4/union/auditentryactor": "/en/enterprise-server@latest/graphql/reference/unions#auditentryactor", - "/en/enterprise/v4/union/auditentryactor": "/en/enterprise-server@latest/graphql/reference/unions#auditentryactor", - "/enterprise/v4/union/closer": "/en/enterprise-server@latest/graphql/reference/unions#closer", - "/en/enterprise/v4/union/closer": "/en/enterprise-server@latest/graphql/reference/unions#closer", - "/enterprise/v4/union/createdissueorrestrictedcontribution": "/en/enterprise-server@latest/graphql/reference/unions#createdissueorrestrictedcontribution", - "/en/enterprise/v4/union/createdissueorrestrictedcontribution": "/en/enterprise-server@latest/graphql/reference/unions#createdissueorrestrictedcontribution", - "/enterprise/v4/union/createdpullrequestorrestrictedcontribution": "/en/enterprise-server@latest/graphql/reference/unions#createdpullrequestorrestrictedcontribution", - "/en/enterprise/v4/union/createdpullrequestorrestrictedcontribution": "/en/enterprise-server@latest/graphql/reference/unions#createdpullrequestorrestrictedcontribution", - "/enterprise/v4/union/createdrepositoryorrestrictedcontribution": "/en/enterprise-server@latest/graphql/reference/unions#createdrepositoryorrestrictedcontribution", - "/en/enterprise/v4/union/createdrepositoryorrestrictedcontribution": "/en/enterprise-server@latest/graphql/reference/unions#createdrepositoryorrestrictedcontribution", - "/enterprise/v4/union/enterprisemember": "/en/enterprise-server@latest/graphql/reference/unions#enterprisemember", - "/en/enterprise/v4/union/enterprisemember": "/en/enterprise-server@latest/graphql/reference/unions#enterprisemember", - "/enterprise/v4/union/ipallowlistowner": "/en/enterprise-server@latest/graphql/reference/unions#ipallowlistowner", - "/en/enterprise/v4/union/ipallowlistowner": "/en/enterprise-server@latest/graphql/reference/unions#ipallowlistowner", - "/enterprise/v4/union/issueorpullrequest": "/en/enterprise-server@latest/graphql/reference/unions#issueorpullrequest", - "/en/enterprise/v4/union/issueorpullrequest": "/en/enterprise-server@latest/graphql/reference/unions#issueorpullrequest", - "/enterprise/v4/union/issuetimelineitem": "/en/enterprise-server@latest/graphql/reference/unions#issuetimelineitem", - "/en/enterprise/v4/union/issuetimelineitem": "/en/enterprise-server@latest/graphql/reference/unions#issuetimelineitem", - "/enterprise/v4/union/issuetimelineitems": "/en/enterprise-server@latest/graphql/reference/unions#issuetimelineitems", - "/en/enterprise/v4/union/issuetimelineitems": "/en/enterprise-server@latest/graphql/reference/unions#issuetimelineitems", - "/enterprise/v4/union/milestoneitem": "/en/enterprise-server@latest/graphql/reference/unions#milestoneitem", - "/en/enterprise/v4/union/milestoneitem": "/en/enterprise-server@latest/graphql/reference/unions#milestoneitem", - "/enterprise/v4/union/organizationauditentry": "/en/enterprise-server@latest/graphql/reference/unions#organizationauditentry", - "/en/enterprise/v4/union/organizationauditentry": "/en/enterprise-server@latest/graphql/reference/unions#organizationauditentry", - "/enterprise/v4/union/orgrestorememberauditentrymembership": "/en/enterprise-server@latest/graphql/reference/unions#orgrestorememberauditentrymembership", - "/en/enterprise/v4/union/orgrestorememberauditentrymembership": "/en/enterprise-server@latest/graphql/reference/unions#orgrestorememberauditentrymembership", - "/enterprise/v4/union/permissiongranter": "/en/enterprise-server@latest/graphql/reference/unions#permissiongranter", - "/en/enterprise/v4/union/permissiongranter": "/en/enterprise-server@latest/graphql/reference/unions#permissiongranter", - "/enterprise/v4/union/pinnableitem": "/en/enterprise-server@latest/graphql/reference/unions#pinnableitem", - "/en/enterprise/v4/union/pinnableitem": "/en/enterprise-server@latest/graphql/reference/unions#pinnableitem", - "/enterprise/v4/union/projectcarditem": "/en/enterprise-server@latest/graphql/reference/unions#projectcarditem", - "/en/enterprise/v4/union/projectcarditem": "/en/enterprise-server@latest/graphql/reference/unions#projectcarditem", - "/enterprise/v4/union/pullrequesttimelineitem": "/en/enterprise-server@latest/graphql/reference/unions#pullrequesttimelineitem", - "/en/enterprise/v4/union/pullrequesttimelineitem": "/en/enterprise-server@latest/graphql/reference/unions#pullrequesttimelineitem", - "/enterprise/v4/union/pullrequesttimelineitems": "/en/enterprise-server@latest/graphql/reference/unions#pullrequesttimelineitems", - "/en/enterprise/v4/union/pullrequesttimelineitems": "/en/enterprise-server@latest/graphql/reference/unions#pullrequesttimelineitems", - "/enterprise/v4/union/pushallowanceactor": "/en/enterprise-server@latest/graphql/reference/unions#pushallowanceactor", - "/en/enterprise/v4/union/pushallowanceactor": "/en/enterprise-server@latest/graphql/reference/unions#pushallowanceactor", - "/enterprise/v4/union/referencedsubject": "/en/enterprise-server@latest/graphql/reference/unions#referencedsubject", - "/en/enterprise/v4/union/referencedsubject": "/en/enterprise-server@latest/graphql/reference/unions#referencedsubject", - "/enterprise/v4/union/renamedtitlesubject": "/en/enterprise-server@latest/graphql/reference/unions#renamedtitlesubject", - "/en/enterprise/v4/union/renamedtitlesubject": "/en/enterprise-server@latest/graphql/reference/unions#renamedtitlesubject", - "/enterprise/v4/union/requestedreviewer": "/en/enterprise-server@latest/graphql/reference/unions#requestedreviewer", - "/en/enterprise/v4/union/requestedreviewer": "/en/enterprise-server@latest/graphql/reference/unions#requestedreviewer", - "/enterprise/v4/union/reviewdismissalallowanceactor": "/en/enterprise-server@latest/graphql/reference/unions#reviewdismissalallowanceactor", - "/en/enterprise/v4/union/reviewdismissalallowanceactor": "/en/enterprise-server@latest/graphql/reference/unions#reviewdismissalallowanceactor", - "/enterprise/v4/union/searchresultitem": "/en/enterprise-server@latest/graphql/reference/unions#searchresultitem", - "/en/enterprise/v4/union/searchresultitem": "/en/enterprise-server@latest/graphql/reference/unions#searchresultitem", - "/enterprise/v4/union/statuscheckrollupcontext": "/en/enterprise-server@latest/graphql/reference/unions#statuscheckrollupcontext", - "/en/enterprise/v4/union/statuscheckrollupcontext": "/en/enterprise-server@latest/graphql/reference/unions#statuscheckrollupcontext", - "/v3/actions/artifacts": "/en/rest/reference/actions#artifacts", - "/en/v3/actions/artifacts": "/en/rest/reference/actions#artifacts", - "/v3/actions/secrets": "/en/rest/reference/actions#secrets", - "/en/v3/actions/secrets": "/en/rest/reference/actions#secrets", - "/v3/actions/self-hosted-runners": "/en/rest/reference/actions#self-hosted-runners", - "/en/v3/actions/self-hosted-runners": "/en/rest/reference/actions#self-hosted-runners", - "/v3/actions/self_hosted_runners": "/en/rest/reference/actions#self-hosted-runners", - "/en/v3/actions/self_hosted_runners": "/en/rest/reference/actions#self-hosted-runners", - "/v3/actions/workflow-jobs": "/en/rest/reference/actions#workflow-jobs", - "/en/v3/actions/workflow-jobs": "/en/rest/reference/actions#workflow-jobs", - "/v3/actions/workflow-runs": "/en/rest/reference/actions#workflow-runs", - "/en/v3/actions/workflow-runs": "/en/rest/reference/actions#workflow-runs", - "/v3/actions/workflow_jobs": "/en/rest/reference/actions#workflow-jobs", - "/en/v3/actions/workflow_jobs": "/en/rest/reference/actions#workflow-jobs", - "/v3/actions/workflow_runs": "/en/rest/reference/actions#workflow-runs", - "/en/v3/actions/workflow_runs": "/en/rest/reference/actions#workflow-runs", - "/v3/actions/workflows": "/en/rest/reference/actions#workflows", - "/en/v3/actions/workflows": "/en/rest/reference/actions#workflows", - "/v3/activity/events": "/en/rest/reference/activity#events", - "/en/v3/activity/events": "/en/rest/reference/activity#events", - "/v3/activity/feeds": "/en/rest/reference/activity#feeds", - "/en/v3/activity/feeds": "/en/rest/reference/activity#feeds", - "/v3/activity/notifications": "/en/rest/reference/activity#notifications", - "/en/v3/activity/notifications": "/en/rest/reference/activity#notifications", - "/v3/activity/starring": "/en/rest/reference/activity#starring", - "/en/v3/activity/starring": "/en/rest/reference/activity#starring", - "/v3/activity/watching": "/en/rest/reference/activity#watching", - "/en/v3/activity/watching": "/en/rest/reference/activity#watching", - "/v3/apps/installations": "/en/rest/reference/apps#installations", - "/en/v3/apps/installations": "/en/rest/reference/apps#installations", - "/v3/apps/marketplace": "/en/rest/reference/apps#marketplace", - "/en/v3/apps/marketplace": "/en/rest/reference/apps#marketplace", - "/v3/apps/oauth_applications": "/en/rest/reference/apps#oauth-applications", - "/en/v3/apps/oauth_applications": "/en/rest/reference/apps#oauth-applications", - "/v3/checks/runs": "/en/rest/reference/checks#runs", - "/en/v3/checks/runs": "/en/rest/reference/checks#runs", - "/v3/checks/suites": "/en/rest/reference/checks#suites", - "/en/v3/checks/suites": "/en/rest/reference/checks#suites", - "/v3/enterprise-admin/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/en/v3/enterprise-admin/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/v3/enterprise-admin/global_webhooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", - "/en/v3/enterprise-admin/global_webhooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", - "/v3/enterprise-admin/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/en/v3/enterprise-admin/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/v3/enterprise-admin/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/en/v3/enterprise-admin/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/v3/enterprise-admin/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/en/v3/enterprise-admin/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/v3/enterprise-admin/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/en/v3/enterprise-admin/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/v3/enterprise-admin/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/en/v3/enterprise-admin/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/v3/enterprise-admin/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/en/v3/enterprise-admin/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/v3/enterprise-admin/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/en/v3/enterprise-admin/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/v3/enterprise-admin/users": "/en/enterprise-server@latest/rest/reference/enterprise-admin#users", - "/en/v3/enterprise-admin/users": "/en/enterprise-server@latest/rest/reference/enterprise-admin#users", - "/v3/enterprise/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/en/v3/enterprise/admin_stats": "/en/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", - "/v3/enterprise/global_webhooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", - "/en/v3/enterprise/global_webhooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", - "/v3/enterprise/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/en/v3/enterprise/ldap": "/en/enterprise-server@latest/rest/reference/enterprise-admin#ldap", - "/v3/enterprise/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/en/v3/enterprise/license": "/en/enterprise-server@latest/rest/reference/enterprise-admin#license", - "/v3/enterprise/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/en/v3/enterprise/management_console": "/en/enterprise-server@latest/rest/reference/enterprise-admin#management-console", - "/v3/enterprise/org_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/en/v3/enterprise/org_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/v3/enterprise/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/en/v3/enterprise/orgs": "/en/enterprise-server@latest/rest/reference/enterprise-admin#orgs", - "/v3/enterprise/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/en/v3/enterprise/pre_receive_environments": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", - "/v3/enterprise/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/en/v3/enterprise/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", - "/v3/enterprise/repo_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/en/v3/enterprise/repo_pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/v3/enterprise/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/en/v3/enterprise/search_indexing": "/en/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", - "/v3/enterprise/users": "/en/enterprise-server@latest/rest/reference/enterprise-admin#users", - "/en/v3/enterprise/users": "/en/enterprise-server@latest/rest/reference/enterprise-admin#users", - "/v3/gists/comments": "/en/rest/reference/gists#comments", - "/en/v3/gists/comments": "/en/rest/reference/gists#comments", - "/v3/git/blobs": "/en/rest/reference/git#blobs", - "/en/v3/git/blobs": "/en/rest/reference/git#blobs", - "/v3/git/commits": "/en/rest/reference/git#commits", - "/en/v3/git/commits": "/en/rest/reference/git#commits", - "/v3/git/refs": "/en/rest/reference/git#refs", - "/en/v3/git/refs": "/en/rest/reference/git#refs", - "/v3/git/tags": "/en/rest/reference/git#tags", - "/en/v3/git/tags": "/en/rest/reference/git#tags", - "/v3/git/trees": "/en/rest/reference/git#trees", - "/en/v3/git/trees": "/en/rest/reference/git#trees", - "/v3/integrations/installations": "/en/developers/apps#installations", - "/en/v3/integrations/installations": "/en/developers/apps#installations", - "/v3/interactions/orgs": "/en/rest/reference/interactions#orgs", - "/en/v3/interactions/orgs": "/en/rest/reference/interactions#orgs", - "/v3/interactions/repos": "/en/rest/reference/interactions#repos", - "/en/v3/interactions/repos": "/en/rest/reference/interactions#repos", - "/v3/issues/assignees": "/en/rest/reference/issues#assignees", - "/en/v3/issues/assignees": "/en/rest/reference/issues#assignees", - "/v3/issues/comments": "/en/rest/reference/issues#comments", - "/en/v3/issues/comments": "/en/rest/reference/issues#comments", - "/v3/issues/events": "/en/rest/reference/issues#events", - "/en/v3/issues/events": "/en/rest/reference/issues#events", - "/v3/issues/labels": "/en/rest/reference/issues#labels", - "/en/v3/issues/labels": "/en/rest/reference/issues#labels", - "/v3/issues/milestones": "/en/rest/reference/issues#milestones", - "/en/v3/issues/milestones": "/en/rest/reference/issues#milestones", - "/v3/issues/timeline": "/en/rest/reference/issues#timeline", - "/en/v3/issues/timeline": "/en/rest/reference/issues#timeline", - "/v3/migration/source_imports": "/en/rest/reference/migrations#source-imports", - "/en/v3/migration/source_imports": "/en/rest/reference/migrations#source-imports", - "/v3/migrations/orgs": "/en/rest/reference/migrations#orgs", - "/en/v3/migrations/orgs": "/en/rest/reference/migrations#orgs", - "/v3/migrations/source_imports": "/en/rest/reference/migrations#source-imports", - "/en/v3/migrations/source_imports": "/en/rest/reference/migrations#source-imports", - "/v3/migrations/users": "/en/rest/reference/migrations#users", - "/en/v3/migrations/users": "/en/rest/reference/migrations#users", - "/v3/oauth_authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/en/v3/oauth_authorizations": "/en/enterprise-server@latest/rest/reference/oauth-authorizations", - "/v3/orgs/blocking": "/en/rest/reference/orgs#blocking", - "/en/v3/orgs/blocking": "/en/rest/reference/orgs#blocking", - "/v3/orgs/hooks": "/en/rest/reference/orgs#webhooks", - "/en/v3/orgs/hooks": "/en/rest/reference/orgs#webhooks", - "/v3/orgs/members": "/en/rest/reference/orgs#members", - "/en/v3/orgs/members": "/en/rest/reference/orgs#members", - "/v3/orgs/migrations": "/en/rest/reference/orgs#migrations", - "/en/v3/orgs/migrations": "/en/rest/reference/orgs#migrations", - "/v3/orgs/outside_collaborators": "/en/rest/reference/orgs#outside-collaborators", - "/en/v3/orgs/outside_collaborators": "/en/rest/reference/orgs#outside-collaborators", - "/v3/orgs/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/en/v3/orgs/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", - "/v3/orgs/teams": "/en/rest/reference/orgs#teams", - "/en/v3/orgs/teams": "/en/rest/reference/orgs#teams", - "/v3/projects/cards": "/en/rest/reference/projects#cards", - "/en/v3/projects/cards": "/en/rest/reference/projects#cards", - "/v3/projects/collaborators": "/en/rest/reference/projects#collaborators", - "/en/v3/projects/collaborators": "/en/rest/reference/projects#collaborators", - "/v3/projects/columns": "/en/rest/reference/projects#columns", - "/en/v3/projects/columns": "/en/rest/reference/projects#columns", - "/v3/pulls/comments": "/en/rest/reference/pulls#comments", - "/en/v3/pulls/comments": "/en/rest/reference/pulls#comments", - "/v3/pulls/review_requests": "/en/rest/reference/pulls#review-requests", - "/en/v3/pulls/review_requests": "/en/rest/reference/pulls#review-requests", - "/v3/pulls/reviews": "/en/rest/reference/pulls#reviews", - "/en/v3/pulls/reviews": "/en/rest/reference/pulls#reviews", - "/v3/repos/branches": "/en/rest/reference/repos#branches", - "/en/v3/repos/branches": "/en/rest/reference/repos#branches", - "/v3/repos/collaborators": "/en/rest/reference/repos#collaborators", - "/en/v3/repos/collaborators": "/en/rest/reference/repos#collaborators", - "/v3/repos/comments": "/en/rest/reference/repos#comments", - "/en/v3/repos/comments": "/en/rest/reference/repos#comments", - "/v3/repos/commits": "/en/rest/reference/repos#commits", - "/en/v3/repos/commits": "/en/rest/reference/repos#commits", - "/v3/repos/community": "/en/rest/reference/repos#community", - "/en/v3/repos/community": "/en/rest/reference/repos#community", - "/v3/repos/contents": "/en/rest/reference/repos#contents", - "/en/v3/repos/contents": "/en/rest/reference/repos#contents", - "/v3/repos/deployments": "/en/rest/reference/repos#deployments", - "/en/v3/repos/deployments": "/en/rest/reference/repos#deployments", - "/v3/repos/downloads": "/en/rest/reference/repos#downloads", - "/en/v3/repos/downloads": "/en/rest/reference/repos#downloads", - "/v3/repos/forks": "/en/rest/reference/repos#forks", - "/en/v3/repos/forks": "/en/rest/reference/repos#forks", - "/v3/repos/hooks": "/en/rest/reference/repos#webhooks", - "/en/v3/repos/hooks": "/en/rest/reference/repos#webhooks", - "/v3/repos/invitations": "/en/rest/reference/repos#invitations", - "/en/v3/repos/invitations": "/en/rest/reference/repos#invitations", - "/v3/repos/keys": "/en/rest/reference/repos#keys", - "/en/v3/repos/keys": "/en/rest/reference/repos#keys", - "/v3/repos/merging": "/en/rest/reference/repos#merging", - "/en/v3/repos/merging": "/en/rest/reference/repos#merging", - "/v3/repos/pages": "/en/rest/reference/repos#pages", - "/en/v3/repos/pages": "/en/rest/reference/repos#pages", - "/v3/repos/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/en/v3/repos/pre_receive_hooks": "/en/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", - "/v3/repos/releases": "/en/rest/reference/repos#releases", - "/en/v3/repos/releases": "/en/rest/reference/repos#releases", - "/v3/repos/statistics": "/en/rest/reference/repos#statistics", - "/en/v3/repos/statistics": "/en/rest/reference/repos#statistics", - "/v3/repos/statuses": "/en/rest/reference/repos#statuses", - "/en/v3/repos/statuses": "/en/rest/reference/repos#statuses", - "/v3/repos/traffic": "/en/rest/reference/repos#traffic", - "/en/v3/repos/traffic": "/en/rest/reference/repos#traffic", - "/v3/teams/discussion_comments": "/en/rest/reference/teams#discussion-comments", - "/en/v3/teams/discussion_comments": "/en/rest/reference/teams#discussion-comments", - "/v3/teams/discussions": "/en/rest/reference/teams#discussions", - "/en/v3/teams/discussions": "/en/rest/reference/teams#discussions", - "/v3/teams/members": "/en/rest/reference/teams#members", - "/en/v3/teams/members": "/en/rest/reference/teams#members", - "/v3/teams/team_sync": "/en/rest/reference/teams#team-sync", - "/en/v3/teams/team_sync": "/en/rest/reference/teams#team-sync", - "/v3/users/blocking": "/en/rest/reference/users#blocking", - "/en/v3/users/blocking": "/en/rest/reference/users#blocking", - "/v3/users/emails": "/en/rest/reference/users#emails", - "/en/v3/users/emails": "/en/rest/reference/users#emails", - "/v3/users/followers": "/en/rest/reference/users#followers", - "/en/v3/users/followers": "/en/rest/reference/users#followers", - "/v3/users/gpg_keys": "/en/rest/reference/users#gpg-keys", - "/en/v3/users/gpg_keys": "/en/rest/reference/users#gpg-keys", - "/v3/users/keys": "/en/rest/reference/users#keys", - "/en/v3/users/keys": "/en/rest/reference/users#keys", - "/v4/enum/__directivelocation": "/en/graphql/reference/enums#__directivelocation", - "/en/v4/enum/__directivelocation": "/en/graphql/reference/enums#__directivelocation", - "/v4/enum/__typekind": "/en/graphql/reference/enums#__typekind", - "/en/v4/enum/__typekind": "/en/graphql/reference/enums#__typekind", - "/v4/enum/actionexecutioncapabilitysetting": "/en/graphql/reference/enums#actionexecutioncapabilitysetting", - "/en/v4/enum/actionexecutioncapabilitysetting": "/en/graphql/reference/enums#actionexecutioncapabilitysetting", - "/v4/enum/auditlogorderfield": "/en/graphql/reference/enums#auditlogorderfield", - "/en/v4/enum/auditlogorderfield": "/en/graphql/reference/enums#auditlogorderfield", - "/v4/enum/checkannotationlevel": "/en/graphql/reference/enums#checkannotationlevel", - "/en/v4/enum/checkannotationlevel": "/en/graphql/reference/enums#checkannotationlevel", - "/v4/enum/checkconclusionstate": "/en/graphql/reference/enums#checkconclusionstate", - "/en/v4/enum/checkconclusionstate": "/en/graphql/reference/enums#checkconclusionstate", - "/v4/enum/checkruntype": "/en/graphql/reference/enums#checkruntype", - "/en/v4/enum/checkruntype": "/en/graphql/reference/enums#checkruntype", - "/v4/enum/checkstatusstate": "/en/graphql/reference/enums#checkstatusstate", - "/en/v4/enum/checkstatusstate": "/en/graphql/reference/enums#checkstatusstate", - "/v4/enum/collaboratoraffiliation": "/en/graphql/reference/enums#collaboratoraffiliation", - "/en/v4/enum/collaboratoraffiliation": "/en/graphql/reference/enums#collaboratoraffiliation", - "/v4/enum/commentauthorassociation": "/en/graphql/reference/enums#commentauthorassociation", - "/en/v4/enum/commentauthorassociation": "/en/graphql/reference/enums#commentauthorassociation", - "/v4/enum/commentcannotupdatereason": "/en/graphql/reference/enums#commentcannotupdatereason", - "/en/v4/enum/commentcannotupdatereason": "/en/graphql/reference/enums#commentcannotupdatereason", - "/v4/enum/commitcontributionorderfield": "/en/graphql/reference/enums#commitcontributionorderfield", - "/en/v4/enum/commitcontributionorderfield": "/en/graphql/reference/enums#commitcontributionorderfield", - "/v4/enum/defaultrepositorypermissionfield": "/en/graphql/reference/enums#defaultrepositorypermissionfield", - "/en/v4/enum/defaultrepositorypermissionfield": "/en/graphql/reference/enums#defaultrepositorypermissionfield", - "/v4/enum/deploymentorderfield": "/en/graphql/reference/enums#deploymentorderfield", - "/en/v4/enum/deploymentorderfield": "/en/graphql/reference/enums#deploymentorderfield", - "/v4/enum/deploymentstate": "/en/graphql/reference/enums#deploymentstate", - "/en/v4/enum/deploymentstate": "/en/graphql/reference/enums#deploymentstate", - "/v4/enum/deploymentstatusstate": "/en/graphql/reference/enums#deploymentstatusstate", - "/en/v4/enum/deploymentstatusstate": "/en/graphql/reference/enums#deploymentstatusstate", - "/v4/enum/diffside": "/en/graphql/reference/enums#diffside", - "/en/v4/enum/diffside": "/en/graphql/reference/enums#diffside", - "/v4/enum/enterpriseadministratorinvitationorderfield": "/en/graphql/reference/enums#enterpriseadministratorinvitationorderfield", - "/en/v4/enum/enterpriseadministratorinvitationorderfield": "/en/graphql/reference/enums#enterpriseadministratorinvitationorderfield", - "/v4/enum/enterpriseadministratorrole": "/en/graphql/reference/enums#enterpriseadministratorrole", - "/en/v4/enum/enterpriseadministratorrole": "/en/graphql/reference/enums#enterpriseadministratorrole", - "/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/en/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", - "/en/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/en/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", - "/v4/enum/enterpriseenableddisabledsettingvalue": "/en/graphql/reference/enums#enterpriseenableddisabledsettingvalue", - "/en/v4/enum/enterpriseenableddisabledsettingvalue": "/en/graphql/reference/enums#enterpriseenableddisabledsettingvalue", - "/v4/enum/enterpriseenabledsettingvalue": "/en/graphql/reference/enums#enterpriseenabledsettingvalue", - "/en/v4/enum/enterpriseenabledsettingvalue": "/en/graphql/reference/enums#enterpriseenabledsettingvalue", - "/v4/enum/enterprisememberorderfield": "/en/graphql/reference/enums#enterprisememberorderfield", - "/en/v4/enum/enterprisememberorderfield": "/en/graphql/reference/enums#enterprisememberorderfield", - "/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/en/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", - "/en/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/en/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", - "/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/en/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", - "/en/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/en/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", - "/v4/enum/enterpriseserverinstallationorderfield": "/en/graphql/reference/enums#enterpriseserverinstallationorderfield", - "/en/v4/enum/enterpriseserverinstallationorderfield": "/en/graphql/reference/enums#enterpriseserverinstallationorderfield", - "/v4/enum/enterpriseserveruseraccountemailorderfield": "/en/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", - "/en/v4/enum/enterpriseserveruseraccountemailorderfield": "/en/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", - "/v4/enum/enterpriseserveruseraccountorderfield": "/en/graphql/reference/enums#enterpriseserveruseraccountorderfield", - "/en/v4/enum/enterpriseserveruseraccountorderfield": "/en/graphql/reference/enums#enterpriseserveruseraccountorderfield", - "/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/en/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", - "/en/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/en/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", - "/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/en/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", - "/en/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/en/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", - "/v4/enum/enterpriseuseraccountmembershiprole": "/en/graphql/reference/enums#enterpriseuseraccountmembershiprole", - "/en/v4/enum/enterpriseuseraccountmembershiprole": "/en/graphql/reference/enums#enterpriseuseraccountmembershiprole", - "/v4/enum/enterpriseuserdeployment": "/en/graphql/reference/enums#enterpriseuserdeployment", - "/en/v4/enum/enterpriseuserdeployment": "/en/graphql/reference/enums#enterpriseuserdeployment", - "/v4/enum/fundingplatform": "/en/graphql/reference/enums#fundingplatform", - "/en/v4/enum/fundingplatform": "/en/graphql/reference/enums#fundingplatform", - "/v4/enum/gistorderfield": "/en/graphql/reference/enums#gistorderfield", - "/en/v4/enum/gistorderfield": "/en/graphql/reference/enums#gistorderfield", - "/v4/enum/gistprivacy": "/en/graphql/reference/enums#gistprivacy", - "/en/v4/enum/gistprivacy": "/en/graphql/reference/enums#gistprivacy", - "/v4/enum/gitsignaturestate": "/en/graphql/reference/enums#gitsignaturestate", - "/en/v4/enum/gitsignaturestate": "/en/graphql/reference/enums#gitsignaturestate", - "/v4/enum/identityproviderconfigurationstate": "/en/graphql/reference/enums#identityproviderconfigurationstate", - "/en/v4/enum/identityproviderconfigurationstate": "/en/graphql/reference/enums#identityproviderconfigurationstate", - "/v4/enum/ipallowlistenabledsettingvalue": "/en/graphql/reference/enums#ipallowlistenabledsettingvalue", - "/en/v4/enum/ipallowlistenabledsettingvalue": "/en/graphql/reference/enums#ipallowlistenabledsettingvalue", - "/v4/enum/ipallowlistentryorderfield": "/en/graphql/reference/enums#ipallowlistentryorderfield", - "/en/v4/enum/ipallowlistentryorderfield": "/en/graphql/reference/enums#ipallowlistentryorderfield", - "/v4/enum/issueorderfield": "/en/graphql/reference/enums#issueorderfield", - "/en/v4/enum/issueorderfield": "/en/graphql/reference/enums#issueorderfield", - "/v4/enum/issuestate": "/en/graphql/reference/enums#issuestate", - "/en/v4/enum/issuestate": "/en/graphql/reference/enums#issuestate", - "/v4/enum/issuetimelineitemsitemtype": "/en/graphql/reference/enums#issuetimelineitemsitemtype", - "/en/v4/enum/issuetimelineitemsitemtype": "/en/graphql/reference/enums#issuetimelineitemsitemtype", - "/v4/enum/labelorderfield": "/en/graphql/reference/enums#labelorderfield", - "/en/v4/enum/labelorderfield": "/en/graphql/reference/enums#labelorderfield", - "/v4/enum/languageorderfield": "/en/graphql/reference/enums#languageorderfield", - "/en/v4/enum/languageorderfield": "/en/graphql/reference/enums#languageorderfield", - "/v4/enum/lockreason": "/en/graphql/reference/enums#lockreason", - "/en/v4/enum/lockreason": "/en/graphql/reference/enums#lockreason", - "/v4/enum/mergeablestate": "/en/graphql/reference/enums#mergeablestate", - "/en/v4/enum/mergeablestate": "/en/graphql/reference/enums#mergeablestate", - "/v4/enum/mergestatestatus": "/en/graphql/reference/enums#mergestatestatus", - "/en/v4/enum/mergestatestatus": "/en/graphql/reference/enums#mergestatestatus", - "/v4/enum/milestoneorderfield": "/en/graphql/reference/enums#milestoneorderfield", - "/en/v4/enum/milestoneorderfield": "/en/graphql/reference/enums#milestoneorderfield", - "/v4/enum/milestonestate": "/en/graphql/reference/enums#milestonestate", - "/en/v4/enum/milestonestate": "/en/graphql/reference/enums#milestonestate", - "/v4/enum/oauthapplicationcreateauditentrystate": "/en/graphql/reference/enums#oauthapplicationcreateauditentrystate", - "/en/v4/enum/oauthapplicationcreateauditentrystate": "/en/graphql/reference/enums#oauthapplicationcreateauditentrystate", - "/v4/enum/operationtype": "/en/graphql/reference/enums#operationtype", - "/en/v4/enum/operationtype": "/en/graphql/reference/enums#operationtype", - "/v4/enum/orderdirection": "/en/graphql/reference/enums#orderdirection", - "/en/v4/enum/orderdirection": "/en/graphql/reference/enums#orderdirection", - "/v4/enum/orgaddmemberauditentrypermission": "/en/graphql/reference/enums#orgaddmemberauditentrypermission", - "/en/v4/enum/orgaddmemberauditentrypermission": "/en/graphql/reference/enums#orgaddmemberauditentrypermission", - "/v4/enum/organizationinvitationrole": "/en/graphql/reference/enums#organizationinvitationrole", - "/en/v4/enum/organizationinvitationrole": "/en/graphql/reference/enums#organizationinvitationrole", - "/v4/enum/organizationinvitationtype": "/en/graphql/reference/enums#organizationinvitationtype", - "/en/v4/enum/organizationinvitationtype": "/en/graphql/reference/enums#organizationinvitationtype", - "/v4/enum/organizationmemberrole": "/en/graphql/reference/enums#organizationmemberrole", - "/en/v4/enum/organizationmemberrole": "/en/graphql/reference/enums#organizationmemberrole", - "/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/en/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", - "/en/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/en/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", - "/v4/enum/organizationorderfield": "/en/graphql/reference/enums#organizationorderfield", - "/en/v4/enum/organizationorderfield": "/en/graphql/reference/enums#organizationorderfield", - "/v4/enum/orgcreateauditentrybillingplan": "/en/graphql/reference/enums#orgcreateauditentrybillingplan", - "/en/v4/enum/orgcreateauditentrybillingplan": "/en/graphql/reference/enums#orgcreateauditentrybillingplan", - "/v4/enum/orgremovebillingmanagerauditentryreason": "/en/graphql/reference/enums#orgremovebillingmanagerauditentryreason", - "/en/v4/enum/orgremovebillingmanagerauditentryreason": "/en/graphql/reference/enums#orgremovebillingmanagerauditentryreason", - "/v4/enum/orgremovememberauditentrymembershiptype": "/en/graphql/reference/enums#orgremovememberauditentrymembershiptype", - "/en/v4/enum/orgremovememberauditentrymembershiptype": "/en/graphql/reference/enums#orgremovememberauditentrymembershiptype", - "/v4/enum/orgremovememberauditentryreason": "/en/graphql/reference/enums#orgremovememberauditentryreason", - "/en/v4/enum/orgremovememberauditentryreason": "/en/graphql/reference/enums#orgremovememberauditentryreason", - "/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/en/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", - "/en/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/en/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", - "/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/en/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", - "/en/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/en/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", - "/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/en/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", - "/en/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/en/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", - "/v4/enum/orgupdatememberauditentrypermission": "/en/graphql/reference/enums#orgupdatememberauditentrypermission", - "/en/v4/enum/orgupdatememberauditentrypermission": "/en/graphql/reference/enums#orgupdatememberauditentrypermission", - "/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/en/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", - "/en/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/en/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", - "/v4/enum/packagefileorderfield": "/en/graphql/reference/enums#packagefileorderfield", - "/en/v4/enum/packagefileorderfield": "/en/graphql/reference/enums#packagefileorderfield", - "/v4/enum/packageorderfield": "/en/graphql/reference/enums#packageorderfield", - "/en/v4/enum/packageorderfield": "/en/graphql/reference/enums#packageorderfield", - "/v4/enum/packagetype": "/en/graphql/reference/enums#packagetype", - "/en/v4/enum/packagetype": "/en/graphql/reference/enums#packagetype", - "/v4/enum/packageversionorderfield": "/en/graphql/reference/enums#packageversionorderfield", - "/en/v4/enum/packageversionorderfield": "/en/graphql/reference/enums#packageversionorderfield", - "/v4/enum/pinnableitemtype": "/en/graphql/reference/enums#pinnableitemtype", - "/en/v4/enum/pinnableitemtype": "/en/graphql/reference/enums#pinnableitemtype", - "/v4/enum/projectcardarchivedstate": "/en/graphql/reference/enums#projectcardarchivedstate", - "/en/v4/enum/projectcardarchivedstate": "/en/graphql/reference/enums#projectcardarchivedstate", - "/v4/enum/projectcardstate": "/en/graphql/reference/enums#projectcardstate", - "/en/v4/enum/projectcardstate": "/en/graphql/reference/enums#projectcardstate", - "/v4/enum/projectcolumnpurpose": "/en/graphql/reference/enums#projectcolumnpurpose", - "/en/v4/enum/projectcolumnpurpose": "/en/graphql/reference/enums#projectcolumnpurpose", - "/v4/enum/projectorderfield": "/en/graphql/reference/enums#projectorderfield", - "/en/v4/enum/projectorderfield": "/en/graphql/reference/enums#projectorderfield", - "/v4/enum/projectstate": "/en/graphql/reference/enums#projectstate", - "/en/v4/enum/projectstate": "/en/graphql/reference/enums#projectstate", - "/v4/enum/projecttemplate": "/en/graphql/reference/enums#projecttemplate", - "/en/v4/enum/projecttemplate": "/en/graphql/reference/enums#projecttemplate", - "/v4/enum/pullrequestmergemethod": "/en/graphql/reference/enums#pullrequestmergemethod", - "/en/v4/enum/pullrequestmergemethod": "/en/graphql/reference/enums#pullrequestmergemethod", - "/v4/enum/pullrequestorderfield": "/en/graphql/reference/enums#pullrequestorderfield", - "/en/v4/enum/pullrequestorderfield": "/en/graphql/reference/enums#pullrequestorderfield", - "/v4/enum/pullrequestreviewcommentstate": "/en/graphql/reference/enums#pullrequestreviewcommentstate", - "/en/v4/enum/pullrequestreviewcommentstate": "/en/graphql/reference/enums#pullrequestreviewcommentstate", - "/v4/enum/pullrequestreviewdecision": "/en/graphql/reference/enums#pullrequestreviewdecision", - "/en/v4/enum/pullrequestreviewdecision": "/en/graphql/reference/enums#pullrequestreviewdecision", - "/v4/enum/pullrequestreviewevent": "/en/graphql/reference/enums#pullrequestreviewevent", - "/en/v4/enum/pullrequestreviewevent": "/en/graphql/reference/enums#pullrequestreviewevent", - "/v4/enum/pullrequestreviewstate": "/en/graphql/reference/enums#pullrequestreviewstate", - "/en/v4/enum/pullrequestreviewstate": "/en/graphql/reference/enums#pullrequestreviewstate", - "/v4/enum/pullrequeststate": "/en/graphql/reference/enums#pullrequeststate", - "/en/v4/enum/pullrequeststate": "/en/graphql/reference/enums#pullrequeststate", - "/v4/enum/pullrequesttimelineitemsitemtype": "/en/graphql/reference/enums#pullrequesttimelineitemsitemtype", - "/en/v4/enum/pullrequesttimelineitemsitemtype": "/en/graphql/reference/enums#pullrequesttimelineitemsitemtype", - "/v4/enum/pullrequestupdatestate": "/en/graphql/reference/enums#pullrequestupdatestate", - "/en/v4/enum/pullrequestupdatestate": "/en/graphql/reference/enums#pullrequestupdatestate", - "/v4/enum/reactioncontent": "/en/graphql/reference/enums#reactioncontent", - "/en/v4/enum/reactioncontent": "/en/graphql/reference/enums#reactioncontent", - "/v4/enum/reactionorderfield": "/en/graphql/reference/enums#reactionorderfield", - "/en/v4/enum/reactionorderfield": "/en/graphql/reference/enums#reactionorderfield", - "/v4/enum/reforderfield": "/en/graphql/reference/enums#reforderfield", - "/en/v4/enum/reforderfield": "/en/graphql/reference/enums#reforderfield", - "/v4/enum/releaseorderfield": "/en/graphql/reference/enums#releaseorderfield", - "/en/v4/enum/releaseorderfield": "/en/graphql/reference/enums#releaseorderfield", - "/v4/enum/repoaccessauditentryvisibility": "/en/graphql/reference/enums#repoaccessauditentryvisibility", - "/en/v4/enum/repoaccessauditentryvisibility": "/en/graphql/reference/enums#repoaccessauditentryvisibility", - "/v4/enum/repoaddmemberauditentryvisibility": "/en/graphql/reference/enums#repoaddmemberauditentryvisibility", - "/en/v4/enum/repoaddmemberauditentryvisibility": "/en/graphql/reference/enums#repoaddmemberauditentryvisibility", - "/v4/enum/repoarchivedauditentryvisibility": "/en/graphql/reference/enums#repoarchivedauditentryvisibility", - "/en/v4/enum/repoarchivedauditentryvisibility": "/en/graphql/reference/enums#repoarchivedauditentryvisibility", - "/v4/enum/repochangemergesettingauditentrymergetype": "/en/graphql/reference/enums#repochangemergesettingauditentrymergetype", - "/en/v4/enum/repochangemergesettingauditentrymergetype": "/en/graphql/reference/enums#repochangemergesettingauditentrymergetype", - "/v4/enum/repocreateauditentryvisibility": "/en/graphql/reference/enums#repocreateauditentryvisibility", - "/en/v4/enum/repocreateauditentryvisibility": "/en/graphql/reference/enums#repocreateauditentryvisibility", - "/v4/enum/repodestroyauditentryvisibility": "/en/graphql/reference/enums#repodestroyauditentryvisibility", - "/en/v4/enum/repodestroyauditentryvisibility": "/en/graphql/reference/enums#repodestroyauditentryvisibility", - "/v4/enum/reporemovememberauditentryvisibility": "/en/graphql/reference/enums#reporemovememberauditentryvisibility", - "/en/v4/enum/reporemovememberauditentryvisibility": "/en/graphql/reference/enums#reporemovememberauditentryvisibility", - "/v4/enum/reportedcontentclassifiers": "/en/graphql/reference/enums#reportedcontentclassifiers", - "/en/v4/enum/reportedcontentclassifiers": "/en/graphql/reference/enums#reportedcontentclassifiers", - "/v4/enum/repositoryaffiliation": "/en/graphql/reference/enums#repositoryaffiliation", - "/en/v4/enum/repositoryaffiliation": "/en/graphql/reference/enums#repositoryaffiliation", - "/v4/enum/repositorycontributiontype": "/en/graphql/reference/enums#repositorycontributiontype", - "/en/v4/enum/repositorycontributiontype": "/en/graphql/reference/enums#repositorycontributiontype", - "/v4/enum/repositoryinvitationorderfield": "/en/graphql/reference/enums#repositoryinvitationorderfield", - "/en/v4/enum/repositoryinvitationorderfield": "/en/graphql/reference/enums#repositoryinvitationorderfield", - "/v4/enum/repositorylockreason": "/en/graphql/reference/enums#repositorylockreason", - "/en/v4/enum/repositorylockreason": "/en/graphql/reference/enums#repositorylockreason", - "/v4/enum/repositoryorderfield": "/en/graphql/reference/enums#repositoryorderfield", - "/en/v4/enum/repositoryorderfield": "/en/graphql/reference/enums#repositoryorderfield", - "/v4/enum/repositorypermission": "/en/graphql/reference/enums#repositorypermission", - "/en/v4/enum/repositorypermission": "/en/graphql/reference/enums#repositorypermission", - "/v4/enum/repositoryprivacy": "/en/graphql/reference/enums#repositoryprivacy", - "/en/v4/enum/repositoryprivacy": "/en/graphql/reference/enums#repositoryprivacy", - "/v4/enum/repositoryvisibility": "/en/graphql/reference/enums#repositoryvisibility", - "/en/v4/enum/repositoryvisibility": "/en/graphql/reference/enums#repositoryvisibility", - "/v4/enum/requestablecheckstatusstate": "/en/graphql/reference/enums#requestablecheckstatusstate", - "/en/v4/enum/requestablecheckstatusstate": "/en/graphql/reference/enums#requestablecheckstatusstate", - "/v4/enum/samldigestalgorithm": "/en/graphql/reference/enums#samldigestalgorithm", - "/en/v4/enum/samldigestalgorithm": "/en/graphql/reference/enums#samldigestalgorithm", - "/v4/enum/samlsignaturealgorithm": "/en/graphql/reference/enums#samlsignaturealgorithm", - "/en/v4/enum/samlsignaturealgorithm": "/en/graphql/reference/enums#samlsignaturealgorithm", - "/v4/enum/savedreplyorderfield": "/en/graphql/reference/enums#savedreplyorderfield", - "/en/v4/enum/savedreplyorderfield": "/en/graphql/reference/enums#savedreplyorderfield", - "/v4/enum/searchtype": "/en/graphql/reference/enums#searchtype", - "/en/v4/enum/searchtype": "/en/graphql/reference/enums#searchtype", - "/v4/enum/securityadvisoryecosystem": "/en/graphql/reference/enums#securityadvisoryecosystem", - "/en/v4/enum/securityadvisoryecosystem": "/en/graphql/reference/enums#securityadvisoryecosystem", - "/v4/enum/securityadvisoryidentifiertype": "/en/graphql/reference/enums#securityadvisoryidentifiertype", - "/en/v4/enum/securityadvisoryidentifiertype": "/en/graphql/reference/enums#securityadvisoryidentifiertype", - "/v4/enum/securityadvisoryorderfield": "/en/graphql/reference/enums#securityadvisoryorderfield", - "/en/v4/enum/securityadvisoryorderfield": "/en/graphql/reference/enums#securityadvisoryorderfield", - "/v4/enum/securityadvisoryseverity": "/en/graphql/reference/enums#securityadvisoryseverity", - "/en/v4/enum/securityadvisoryseverity": "/en/graphql/reference/enums#securityadvisoryseverity", - "/v4/enum/securityvulnerabilityorderfield": "/en/graphql/reference/enums#securityvulnerabilityorderfield", - "/en/v4/enum/securityvulnerabilityorderfield": "/en/graphql/reference/enums#securityvulnerabilityorderfield", - "/v4/enum/sponsorshiporderfield": "/en/graphql/reference/enums#sponsorshiporderfield", - "/en/v4/enum/sponsorshiporderfield": "/en/graphql/reference/enums#sponsorshiporderfield", - "/v4/enum/sponsorshipprivacy": "/en/graphql/reference/enums#sponsorshipprivacy", - "/en/v4/enum/sponsorshipprivacy": "/en/graphql/reference/enums#sponsorshipprivacy", - "/v4/enum/sponsorstierorderfield": "/en/graphql/reference/enums#sponsorstierorderfield", - "/en/v4/enum/sponsorstierorderfield": "/en/graphql/reference/enums#sponsorstierorderfield", - "/v4/enum/starorderfield": "/en/graphql/reference/enums#starorderfield", - "/en/v4/enum/starorderfield": "/en/graphql/reference/enums#starorderfield", - "/v4/enum/statusstate": "/en/graphql/reference/enums#statusstate", - "/en/v4/enum/statusstate": "/en/graphql/reference/enums#statusstate", - "/v4/enum/subscriptionstate": "/en/graphql/reference/enums#subscriptionstate", - "/en/v4/enum/subscriptionstate": "/en/graphql/reference/enums#subscriptionstate", - "/v4/enum/teamdiscussioncommentorderfield": "/en/graphql/reference/enums#teamdiscussioncommentorderfield", - "/en/v4/enum/teamdiscussioncommentorderfield": "/en/graphql/reference/enums#teamdiscussioncommentorderfield", - "/v4/enum/teamdiscussionorderfield": "/en/graphql/reference/enums#teamdiscussionorderfield", - "/en/v4/enum/teamdiscussionorderfield": "/en/graphql/reference/enums#teamdiscussionorderfield", - "/v4/enum/teammemberorderfield": "/en/graphql/reference/enums#teammemberorderfield", - "/en/v4/enum/teammemberorderfield": "/en/graphql/reference/enums#teammemberorderfield", - "/v4/enum/teammemberrole": "/en/graphql/reference/enums#teammemberrole", - "/en/v4/enum/teammemberrole": "/en/graphql/reference/enums#teammemberrole", - "/v4/enum/teammembershiptype": "/en/graphql/reference/enums#teammembershiptype", - "/en/v4/enum/teammembershiptype": "/en/graphql/reference/enums#teammembershiptype", - "/v4/enum/teamorderfield": "/en/graphql/reference/enums#teamorderfield", - "/en/v4/enum/teamorderfield": "/en/graphql/reference/enums#teamorderfield", - "/v4/enum/teamprivacy": "/en/graphql/reference/enums#teamprivacy", - "/en/v4/enum/teamprivacy": "/en/graphql/reference/enums#teamprivacy", - "/v4/enum/teamrepositoryorderfield": "/en/graphql/reference/enums#teamrepositoryorderfield", - "/en/v4/enum/teamrepositoryorderfield": "/en/graphql/reference/enums#teamrepositoryorderfield", - "/v4/enum/teamreviewassignmentalgorithm": "/en/graphql/reference/enums#teamreviewassignmentalgorithm", - "/en/v4/enum/teamreviewassignmentalgorithm": "/en/graphql/reference/enums#teamreviewassignmentalgorithm", - "/v4/enum/teamrole": "/en/graphql/reference/enums#teamrole", - "/en/v4/enum/teamrole": "/en/graphql/reference/enums#teamrole", - "/v4/enum/topicsuggestiondeclinereason": "/en/graphql/reference/enums#topicsuggestiondeclinereason", - "/en/v4/enum/topicsuggestiondeclinereason": "/en/graphql/reference/enums#topicsuggestiondeclinereason", - "/v4/enum/userblockduration": "/en/graphql/reference/enums#userblockduration", - "/en/v4/enum/userblockduration": "/en/graphql/reference/enums#userblockduration", - "/v4/enum/userstatusorderfield": "/en/graphql/reference/enums#userstatusorderfield", - "/en/v4/enum/userstatusorderfield": "/en/graphql/reference/enums#userstatusorderfield", - "/v4/input_object/acceptenterpriseadministratorinvitationinput": "/en/graphql/reference/input-objects#acceptenterpriseadministratorinvitationinput", - "/en/v4/input_object/acceptenterpriseadministratorinvitationinput": "/en/graphql/reference/input-objects#acceptenterpriseadministratorinvitationinput", - "/v4/input_object/accepttopicsuggestioninput": "/en/graphql/reference/input-objects#accepttopicsuggestioninput", - "/en/v4/input_object/accepttopicsuggestioninput": "/en/graphql/reference/input-objects#accepttopicsuggestioninput", - "/v4/input_object/addassigneestoassignableinput": "/en/graphql/reference/input-objects#addassigneestoassignableinput", - "/en/v4/input_object/addassigneestoassignableinput": "/en/graphql/reference/input-objects#addassigneestoassignableinput", - "/v4/input_object/addcommentinput": "/en/graphql/reference/input-objects#addcommentinput", - "/en/v4/input_object/addcommentinput": "/en/graphql/reference/input-objects#addcommentinput", - "/v4/input_object/addlabelstolabelableinput": "/en/graphql/reference/input-objects#addlabelstolabelableinput", - "/en/v4/input_object/addlabelstolabelableinput": "/en/graphql/reference/input-objects#addlabelstolabelableinput", - "/v4/input_object/addprojectcardinput": "/en/graphql/reference/input-objects#addprojectcardinput", - "/en/v4/input_object/addprojectcardinput": "/en/graphql/reference/input-objects#addprojectcardinput", - "/v4/input_object/addprojectcolumninput": "/en/graphql/reference/input-objects#addprojectcolumninput", - "/en/v4/input_object/addprojectcolumninput": "/en/graphql/reference/input-objects#addprojectcolumninput", - "/v4/input_object/addpullrequestreviewcommentinput": "/en/graphql/reference/input-objects#addpullrequestreviewcommentinput", - "/en/v4/input_object/addpullrequestreviewcommentinput": "/en/graphql/reference/input-objects#addpullrequestreviewcommentinput", - "/v4/input_object/addpullrequestreviewinput": "/en/graphql/reference/input-objects#addpullrequestreviewinput", - "/en/v4/input_object/addpullrequestreviewinput": "/en/graphql/reference/input-objects#addpullrequestreviewinput", - "/v4/input_object/addpullrequestreviewthreadinput": "/en/graphql/reference/input-objects#addpullrequestreviewthreadinput", - "/en/v4/input_object/addpullrequestreviewthreadinput": "/en/graphql/reference/input-objects#addpullrequestreviewthreadinput", - "/v4/input_object/addreactioninput": "/en/graphql/reference/input-objects#addreactioninput", - "/en/v4/input_object/addreactioninput": "/en/graphql/reference/input-objects#addreactioninput", - "/v4/input_object/addstarinput": "/en/graphql/reference/input-objects#addstarinput", - "/en/v4/input_object/addstarinput": "/en/graphql/reference/input-objects#addstarinput", - "/v4/input_object/archiverepositoryinput": "/en/graphql/reference/input-objects#archiverepositoryinput", - "/en/v4/input_object/archiverepositoryinput": "/en/graphql/reference/input-objects#archiverepositoryinput", - "/v4/input_object/auditlogorder": "/en/graphql/reference/input-objects#auditlogorder", - "/en/v4/input_object/auditlogorder": "/en/graphql/reference/input-objects#auditlogorder", - "/v4/input_object/cancelenterpriseadmininvitationinput": "/en/graphql/reference/input-objects#cancelenterpriseadmininvitationinput", - "/en/v4/input_object/cancelenterpriseadmininvitationinput": "/en/graphql/reference/input-objects#cancelenterpriseadmininvitationinput", - "/v4/input_object/changeuserstatusinput": "/en/graphql/reference/input-objects#changeuserstatusinput", - "/en/v4/input_object/changeuserstatusinput": "/en/graphql/reference/input-objects#changeuserstatusinput", - "/v4/input_object/checkannotationdata": "/en/graphql/reference/input-objects#checkannotationdata", - "/en/v4/input_object/checkannotationdata": "/en/graphql/reference/input-objects#checkannotationdata", - "/v4/input_object/checkannotationrange": "/en/graphql/reference/input-objects#checkannotationrange", - "/en/v4/input_object/checkannotationrange": "/en/graphql/reference/input-objects#checkannotationrange", - "/v4/input_object/checkrunaction": "/en/graphql/reference/input-objects#checkrunaction", - "/en/v4/input_object/checkrunaction": "/en/graphql/reference/input-objects#checkrunaction", - "/v4/input_object/checkrunfilter": "/en/graphql/reference/input-objects#checkrunfilter", - "/en/v4/input_object/checkrunfilter": "/en/graphql/reference/input-objects#checkrunfilter", - "/v4/input_object/checkrunoutput": "/en/graphql/reference/input-objects#checkrunoutput", - "/en/v4/input_object/checkrunoutput": "/en/graphql/reference/input-objects#checkrunoutput", - "/v4/input_object/checkrunoutputimage": "/en/graphql/reference/input-objects#checkrunoutputimage", - "/en/v4/input_object/checkrunoutputimage": "/en/graphql/reference/input-objects#checkrunoutputimage", - "/v4/input_object/checksuiteautotriggerpreference": "/en/graphql/reference/input-objects#checksuiteautotriggerpreference", - "/en/v4/input_object/checksuiteautotriggerpreference": "/en/graphql/reference/input-objects#checksuiteautotriggerpreference", - "/v4/input_object/checksuitefilter": "/en/graphql/reference/input-objects#checksuitefilter", - "/en/v4/input_object/checksuitefilter": "/en/graphql/reference/input-objects#checksuitefilter", - "/v4/input_object/clearlabelsfromlabelableinput": "/en/graphql/reference/input-objects#clearlabelsfromlabelableinput", - "/en/v4/input_object/clearlabelsfromlabelableinput": "/en/graphql/reference/input-objects#clearlabelsfromlabelableinput", - "/v4/input_object/cloneprojectinput": "/en/graphql/reference/input-objects#cloneprojectinput", - "/en/v4/input_object/cloneprojectinput": "/en/graphql/reference/input-objects#cloneprojectinput", - "/v4/input_object/clonetemplaterepositoryinput": "/en/graphql/reference/input-objects#clonetemplaterepositoryinput", - "/en/v4/input_object/clonetemplaterepositoryinput": "/en/graphql/reference/input-objects#clonetemplaterepositoryinput", - "/v4/input_object/closeissueinput": "/en/graphql/reference/input-objects#closeissueinput", - "/en/v4/input_object/closeissueinput": "/en/graphql/reference/input-objects#closeissueinput", - "/v4/input_object/closepullrequestinput": "/en/graphql/reference/input-objects#closepullrequestinput", - "/en/v4/input_object/closepullrequestinput": "/en/graphql/reference/input-objects#closepullrequestinput", - "/v4/input_object/commitauthor": "/en/graphql/reference/input-objects#commitauthor", - "/en/v4/input_object/commitauthor": "/en/graphql/reference/input-objects#commitauthor", - "/v4/input_object/commitcontributionorder": "/en/graphql/reference/input-objects#commitcontributionorder", - "/en/v4/input_object/commitcontributionorder": "/en/graphql/reference/input-objects#commitcontributionorder", - "/v4/input_object/contributionorder": "/en/graphql/reference/input-objects#contributionorder", - "/en/v4/input_object/contributionorder": "/en/graphql/reference/input-objects#contributionorder", - "/v4/input_object/convertprojectcardnotetoissueinput": "/en/graphql/reference/input-objects#convertprojectcardnotetoissueinput", - "/en/v4/input_object/convertprojectcardnotetoissueinput": "/en/graphql/reference/input-objects#convertprojectcardnotetoissueinput", - "/v4/input_object/createbranchprotectionruleinput": "/en/graphql/reference/input-objects#createbranchprotectionruleinput", - "/en/v4/input_object/createbranchprotectionruleinput": "/en/graphql/reference/input-objects#createbranchprotectionruleinput", - "/v4/input_object/createcheckruninput": "/en/graphql/reference/input-objects#createcheckruninput", - "/en/v4/input_object/createcheckruninput": "/en/graphql/reference/input-objects#createcheckruninput", - "/v4/input_object/createchecksuiteinput": "/en/graphql/reference/input-objects#createchecksuiteinput", - "/en/v4/input_object/createchecksuiteinput": "/en/graphql/reference/input-objects#createchecksuiteinput", - "/v4/input_object/createcontentattachmentinput": "/en/graphql/reference/input-objects#createcontentattachmentinput", - "/en/v4/input_object/createcontentattachmentinput": "/en/graphql/reference/input-objects#createcontentattachmentinput", - "/v4/input_object/createdeploymentinput": "/en/graphql/reference/input-objects#createdeploymentinput", - "/en/v4/input_object/createdeploymentinput": "/en/graphql/reference/input-objects#createdeploymentinput", - "/v4/input_object/createdeploymentstatusinput": "/en/graphql/reference/input-objects#createdeploymentstatusinput", - "/en/v4/input_object/createdeploymentstatusinput": "/en/graphql/reference/input-objects#createdeploymentstatusinput", - "/v4/input_object/createenterpriseorganizationinput": "/en/graphql/reference/input-objects#createenterpriseorganizationinput", - "/en/v4/input_object/createenterpriseorganizationinput": "/en/graphql/reference/input-objects#createenterpriseorganizationinput", - "/v4/input_object/createipallowlistentryinput": "/en/graphql/reference/input-objects#createipallowlistentryinput", - "/en/v4/input_object/createipallowlistentryinput": "/en/graphql/reference/input-objects#createipallowlistentryinput", - "/v4/input_object/createissueinput": "/en/graphql/reference/input-objects#createissueinput", - "/en/v4/input_object/createissueinput": "/en/graphql/reference/input-objects#createissueinput", - "/v4/input_object/createlabelinput": "/en/graphql/reference/input-objects#createlabelinput", - "/en/v4/input_object/createlabelinput": "/en/graphql/reference/input-objects#createlabelinput", - "/v4/input_object/createprojectinput": "/en/graphql/reference/input-objects#createprojectinput", - "/en/v4/input_object/createprojectinput": "/en/graphql/reference/input-objects#createprojectinput", - "/v4/input_object/createpullrequestinput": "/en/graphql/reference/input-objects#createpullrequestinput", - "/en/v4/input_object/createpullrequestinput": "/en/graphql/reference/input-objects#createpullrequestinput", - "/v4/input_object/createrefinput": "/en/graphql/reference/input-objects#createrefinput", - "/en/v4/input_object/createrefinput": "/en/graphql/reference/input-objects#createrefinput", - "/v4/input_object/createrepositoryinput": "/en/graphql/reference/input-objects#createrepositoryinput", - "/en/v4/input_object/createrepositoryinput": "/en/graphql/reference/input-objects#createrepositoryinput", - "/v4/input_object/createteamdiscussioncommentinput": "/en/graphql/reference/input-objects#createteamdiscussioncommentinput", - "/en/v4/input_object/createteamdiscussioncommentinput": "/en/graphql/reference/input-objects#createteamdiscussioncommentinput", - "/v4/input_object/createteamdiscussioninput": "/en/graphql/reference/input-objects#createteamdiscussioninput", - "/en/v4/input_object/createteamdiscussioninput": "/en/graphql/reference/input-objects#createteamdiscussioninput", - "/v4/input_object/declinetopicsuggestioninput": "/en/graphql/reference/input-objects#declinetopicsuggestioninput", - "/en/v4/input_object/declinetopicsuggestioninput": "/en/graphql/reference/input-objects#declinetopicsuggestioninput", - "/v4/input_object/deletebranchprotectionruleinput": "/en/graphql/reference/input-objects#deletebranchprotectionruleinput", - "/en/v4/input_object/deletebranchprotectionruleinput": "/en/graphql/reference/input-objects#deletebranchprotectionruleinput", - "/v4/input_object/deletedeploymentinput": "/en/graphql/reference/input-objects#deletedeploymentinput", - "/en/v4/input_object/deletedeploymentinput": "/en/graphql/reference/input-objects#deletedeploymentinput", - "/v4/input_object/deleteipallowlistentryinput": "/en/graphql/reference/input-objects#deleteipallowlistentryinput", - "/en/v4/input_object/deleteipallowlistentryinput": "/en/graphql/reference/input-objects#deleteipallowlistentryinput", - "/v4/input_object/deleteissuecommentinput": "/en/graphql/reference/input-objects#deleteissuecommentinput", - "/en/v4/input_object/deleteissuecommentinput": "/en/graphql/reference/input-objects#deleteissuecommentinput", - "/v4/input_object/deleteissueinput": "/en/graphql/reference/input-objects#deleteissueinput", - "/en/v4/input_object/deleteissueinput": "/en/graphql/reference/input-objects#deleteissueinput", - "/v4/input_object/deletelabelinput": "/en/graphql/reference/input-objects#deletelabelinput", - "/en/v4/input_object/deletelabelinput": "/en/graphql/reference/input-objects#deletelabelinput", - "/v4/input_object/deletepackageversioninput": "/en/graphql/reference/input-objects#deletepackageversioninput", - "/en/v4/input_object/deletepackageversioninput": "/en/graphql/reference/input-objects#deletepackageversioninput", - "/v4/input_object/deleteprojectcardinput": "/en/graphql/reference/input-objects#deleteprojectcardinput", - "/en/v4/input_object/deleteprojectcardinput": "/en/graphql/reference/input-objects#deleteprojectcardinput", - "/v4/input_object/deleteprojectcolumninput": "/en/graphql/reference/input-objects#deleteprojectcolumninput", - "/en/v4/input_object/deleteprojectcolumninput": "/en/graphql/reference/input-objects#deleteprojectcolumninput", - "/v4/input_object/deleteprojectinput": "/en/graphql/reference/input-objects#deleteprojectinput", - "/en/v4/input_object/deleteprojectinput": "/en/graphql/reference/input-objects#deleteprojectinput", - "/v4/input_object/deletepullrequestreviewcommentinput": "/en/graphql/reference/input-objects#deletepullrequestreviewcommentinput", - "/en/v4/input_object/deletepullrequestreviewcommentinput": "/en/graphql/reference/input-objects#deletepullrequestreviewcommentinput", - "/v4/input_object/deletepullrequestreviewinput": "/en/graphql/reference/input-objects#deletepullrequestreviewinput", - "/en/v4/input_object/deletepullrequestreviewinput": "/en/graphql/reference/input-objects#deletepullrequestreviewinput", - "/v4/input_object/deleterefinput": "/en/graphql/reference/input-objects#deleterefinput", - "/en/v4/input_object/deleterefinput": "/en/graphql/reference/input-objects#deleterefinput", - "/v4/input_object/deleteteamdiscussioncommentinput": "/en/graphql/reference/input-objects#deleteteamdiscussioncommentinput", - "/en/v4/input_object/deleteteamdiscussioncommentinput": "/en/graphql/reference/input-objects#deleteteamdiscussioncommentinput", - "/v4/input_object/deleteteamdiscussioninput": "/en/graphql/reference/input-objects#deleteteamdiscussioninput", - "/en/v4/input_object/deleteteamdiscussioninput": "/en/graphql/reference/input-objects#deleteteamdiscussioninput", - "/v4/input_object/deploymentorder": "/en/graphql/reference/input-objects#deploymentorder", - "/en/v4/input_object/deploymentorder": "/en/graphql/reference/input-objects#deploymentorder", - "/v4/input_object/dismisspullrequestreviewinput": "/en/graphql/reference/input-objects#dismisspullrequestreviewinput", - "/en/v4/input_object/dismisspullrequestreviewinput": "/en/graphql/reference/input-objects#dismisspullrequestreviewinput", - "/v4/input_object/draftpullrequestreviewcomment": "/en/graphql/reference/input-objects#draftpullrequestreviewcomment", - "/en/v4/input_object/draftpullrequestreviewcomment": "/en/graphql/reference/input-objects#draftpullrequestreviewcomment", - "/v4/input_object/draftpullrequestreviewthread": "/en/graphql/reference/input-objects#draftpullrequestreviewthread", - "/en/v4/input_object/draftpullrequestreviewthread": "/en/graphql/reference/input-objects#draftpullrequestreviewthread", - "/v4/input_object/enterpriseadministratorinvitationorder": "/en/graphql/reference/input-objects#enterpriseadministratorinvitationorder", - "/en/v4/input_object/enterpriseadministratorinvitationorder": "/en/graphql/reference/input-objects#enterpriseadministratorinvitationorder", - "/v4/input_object/enterprisememberorder": "/en/graphql/reference/input-objects#enterprisememberorder", - "/en/v4/input_object/enterprisememberorder": "/en/graphql/reference/input-objects#enterprisememberorder", - "/v4/input_object/enterpriseserverinstallationorder": "/en/graphql/reference/input-objects#enterpriseserverinstallationorder", - "/en/v4/input_object/enterpriseserverinstallationorder": "/en/graphql/reference/input-objects#enterpriseserverinstallationorder", - "/v4/input_object/enterpriseserveruseraccountemailorder": "/en/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", - "/en/v4/input_object/enterpriseserveruseraccountemailorder": "/en/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", - "/v4/input_object/enterpriseserveruseraccountorder": "/en/graphql/reference/input-objects#enterpriseserveruseraccountorder", - "/en/v4/input_object/enterpriseserveruseraccountorder": "/en/graphql/reference/input-objects#enterpriseserveruseraccountorder", - "/v4/input_object/enterpriseserveruseraccountsuploadorder": "/en/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", - "/en/v4/input_object/enterpriseserveruseraccountsuploadorder": "/en/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", - "/v4/input_object/followuserinput": "/en/graphql/reference/input-objects#followuserinput", - "/en/v4/input_object/followuserinput": "/en/graphql/reference/input-objects#followuserinput", - "/v4/input_object/gistorder": "/en/graphql/reference/input-objects#gistorder", - "/en/v4/input_object/gistorder": "/en/graphql/reference/input-objects#gistorder", - "/v4/input_object/importprojectinput": "/en/graphql/reference/input-objects#importprojectinput", - "/en/v4/input_object/importprojectinput": "/en/graphql/reference/input-objects#importprojectinput", - "/v4/input_object/inviteenterpriseadmininput": "/en/graphql/reference/input-objects#inviteenterpriseadmininput", - "/en/v4/input_object/inviteenterpriseadmininput": "/en/graphql/reference/input-objects#inviteenterpriseadmininput", - "/v4/input_object/ipallowlistentryorder": "/en/graphql/reference/input-objects#ipallowlistentryorder", - "/en/v4/input_object/ipallowlistentryorder": "/en/graphql/reference/input-objects#ipallowlistentryorder", - "/v4/input_object/issuefilters": "/en/graphql/reference/input-objects#issuefilters", - "/en/v4/input_object/issuefilters": "/en/graphql/reference/input-objects#issuefilters", - "/v4/input_object/issueorder": "/en/graphql/reference/input-objects#issueorder", - "/en/v4/input_object/issueorder": "/en/graphql/reference/input-objects#issueorder", - "/v4/input_object/labelorder": "/en/graphql/reference/input-objects#labelorder", - "/en/v4/input_object/labelorder": "/en/graphql/reference/input-objects#labelorder", - "/v4/input_object/languageorder": "/en/graphql/reference/input-objects#languageorder", - "/en/v4/input_object/languageorder": "/en/graphql/reference/input-objects#languageorder", - "/v4/input_object/linkrepositorytoprojectinput": "/en/graphql/reference/input-objects#linkrepositorytoprojectinput", - "/en/v4/input_object/linkrepositorytoprojectinput": "/en/graphql/reference/input-objects#linkrepositorytoprojectinput", - "/v4/input_object/locklockableinput": "/en/graphql/reference/input-objects#locklockableinput", - "/en/v4/input_object/locklockableinput": "/en/graphql/reference/input-objects#locklockableinput", - "/v4/input_object/markpullrequestreadyforreviewinput": "/en/graphql/reference/input-objects#markpullrequestreadyforreviewinput", - "/en/v4/input_object/markpullrequestreadyforreviewinput": "/en/graphql/reference/input-objects#markpullrequestreadyforreviewinput", - "/v4/input_object/mergebranchinput": "/en/graphql/reference/input-objects#mergebranchinput", - "/en/v4/input_object/mergebranchinput": "/en/graphql/reference/input-objects#mergebranchinput", - "/v4/input_object/mergepullrequestinput": "/en/graphql/reference/input-objects#mergepullrequestinput", - "/en/v4/input_object/mergepullrequestinput": "/en/graphql/reference/input-objects#mergepullrequestinput", - "/v4/input_object/milestoneorder": "/en/graphql/reference/input-objects#milestoneorder", - "/en/v4/input_object/milestoneorder": "/en/graphql/reference/input-objects#milestoneorder", - "/v4/input_object/minimizecommentinput": "/en/graphql/reference/input-objects#minimizecommentinput", - "/en/v4/input_object/minimizecommentinput": "/en/graphql/reference/input-objects#minimizecommentinput", - "/v4/input_object/moveprojectcardinput": "/en/graphql/reference/input-objects#moveprojectcardinput", - "/en/v4/input_object/moveprojectcardinput": "/en/graphql/reference/input-objects#moveprojectcardinput", - "/v4/input_object/moveprojectcolumninput": "/en/graphql/reference/input-objects#moveprojectcolumninput", - "/en/v4/input_object/moveprojectcolumninput": "/en/graphql/reference/input-objects#moveprojectcolumninput", - "/v4/input_object/organizationorder": "/en/graphql/reference/input-objects#organizationorder", - "/en/v4/input_object/organizationorder": "/en/graphql/reference/input-objects#organizationorder", - "/v4/input_object/packagefileorder": "/en/graphql/reference/input-objects#packagefileorder", - "/en/v4/input_object/packagefileorder": "/en/graphql/reference/input-objects#packagefileorder", - "/v4/input_object/packageorder": "/en/graphql/reference/input-objects#packageorder", - "/en/v4/input_object/packageorder": "/en/graphql/reference/input-objects#packageorder", - "/v4/input_object/packageversionorder": "/en/graphql/reference/input-objects#packageversionorder", - "/en/v4/input_object/packageversionorder": "/en/graphql/reference/input-objects#packageversionorder", - "/v4/input_object/pinissueinput": "/en/graphql/reference/input-objects#pinissueinput", - "/en/v4/input_object/pinissueinput": "/en/graphql/reference/input-objects#pinissueinput", - "/v4/input_object/projectcardimport": "/en/graphql/reference/input-objects#projectcardimport", - "/en/v4/input_object/projectcardimport": "/en/graphql/reference/input-objects#projectcardimport", - "/v4/input_object/projectcolumnimport": "/en/graphql/reference/input-objects#projectcolumnimport", - "/en/v4/input_object/projectcolumnimport": "/en/graphql/reference/input-objects#projectcolumnimport", - "/v4/input_object/projectorder": "/en/graphql/reference/input-objects#projectorder", - "/en/v4/input_object/projectorder": "/en/graphql/reference/input-objects#projectorder", - "/v4/input_object/pullrequestorder": "/en/graphql/reference/input-objects#pullrequestorder", - "/en/v4/input_object/pullrequestorder": "/en/graphql/reference/input-objects#pullrequestorder", - "/v4/input_object/reactionorder": "/en/graphql/reference/input-objects#reactionorder", - "/en/v4/input_object/reactionorder": "/en/graphql/reference/input-objects#reactionorder", - "/v4/input_object/reforder": "/en/graphql/reference/input-objects#reforder", - "/en/v4/input_object/reforder": "/en/graphql/reference/input-objects#reforder", - "/v4/input_object/refupdate": "/en/graphql/reference/input-objects#refupdate", - "/en/v4/input_object/refupdate": "/en/graphql/reference/input-objects#refupdate", - "/v4/input_object/regenerateenterpriseidentityproviderrecoverycodesinput": "/en/graphql/reference/input-objects#regenerateenterpriseidentityproviderrecoverycodesinput", - "/en/v4/input_object/regenerateenterpriseidentityproviderrecoverycodesinput": "/en/graphql/reference/input-objects#regenerateenterpriseidentityproviderrecoverycodesinput", - "/v4/input_object/releaseorder": "/en/graphql/reference/input-objects#releaseorder", - "/en/v4/input_object/releaseorder": "/en/graphql/reference/input-objects#releaseorder", - "/v4/input_object/removeassigneesfromassignableinput": "/en/graphql/reference/input-objects#removeassigneesfromassignableinput", - "/en/v4/input_object/removeassigneesfromassignableinput": "/en/graphql/reference/input-objects#removeassigneesfromassignableinput", - "/v4/input_object/removeenterpriseadmininput": "/en/graphql/reference/input-objects#removeenterpriseadmininput", - "/en/v4/input_object/removeenterpriseadmininput": "/en/graphql/reference/input-objects#removeenterpriseadmininput", - "/v4/input_object/removeenterpriseidentityproviderinput": "/en/graphql/reference/input-objects#removeenterpriseidentityproviderinput", - "/en/v4/input_object/removeenterpriseidentityproviderinput": "/en/graphql/reference/input-objects#removeenterpriseidentityproviderinput", - "/v4/input_object/removeenterpriseorganizationinput": "/en/graphql/reference/input-objects#removeenterpriseorganizationinput", - "/en/v4/input_object/removeenterpriseorganizationinput": "/en/graphql/reference/input-objects#removeenterpriseorganizationinput", - "/v4/input_object/removelabelsfromlabelableinput": "/en/graphql/reference/input-objects#removelabelsfromlabelableinput", - "/en/v4/input_object/removelabelsfromlabelableinput": "/en/graphql/reference/input-objects#removelabelsfromlabelableinput", - "/v4/input_object/removeoutsidecollaboratorinput": "/en/graphql/reference/input-objects#removeoutsidecollaboratorinput", - "/en/v4/input_object/removeoutsidecollaboratorinput": "/en/graphql/reference/input-objects#removeoutsidecollaboratorinput", - "/v4/input_object/removereactioninput": "/en/graphql/reference/input-objects#removereactioninput", - "/en/v4/input_object/removereactioninput": "/en/graphql/reference/input-objects#removereactioninput", - "/v4/input_object/removestarinput": "/en/graphql/reference/input-objects#removestarinput", - "/en/v4/input_object/removestarinput": "/en/graphql/reference/input-objects#removestarinput", - "/v4/input_object/reopenissueinput": "/en/graphql/reference/input-objects#reopenissueinput", - "/en/v4/input_object/reopenissueinput": "/en/graphql/reference/input-objects#reopenissueinput", - "/v4/input_object/reopenpullrequestinput": "/en/graphql/reference/input-objects#reopenpullrequestinput", - "/en/v4/input_object/reopenpullrequestinput": "/en/graphql/reference/input-objects#reopenpullrequestinput", - "/v4/input_object/repositoryinvitationorder": "/en/graphql/reference/input-objects#repositoryinvitationorder", - "/en/v4/input_object/repositoryinvitationorder": "/en/graphql/reference/input-objects#repositoryinvitationorder", - "/v4/input_object/repositoryorder": "/en/graphql/reference/input-objects#repositoryorder", - "/en/v4/input_object/repositoryorder": "/en/graphql/reference/input-objects#repositoryorder", - "/v4/input_object/requestreviewsinput": "/en/graphql/reference/input-objects#requestreviewsinput", - "/en/v4/input_object/requestreviewsinput": "/en/graphql/reference/input-objects#requestreviewsinput", - "/v4/input_object/rerequestchecksuiteinput": "/en/graphql/reference/input-objects#rerequestchecksuiteinput", - "/en/v4/input_object/rerequestchecksuiteinput": "/en/graphql/reference/input-objects#rerequestchecksuiteinput", - "/v4/input_object/resolvereviewthreadinput": "/en/graphql/reference/input-objects#resolvereviewthreadinput", - "/en/v4/input_object/resolvereviewthreadinput": "/en/graphql/reference/input-objects#resolvereviewthreadinput", - "/v4/input_object/savedreplyorder": "/en/graphql/reference/input-objects#savedreplyorder", - "/en/v4/input_object/savedreplyorder": "/en/graphql/reference/input-objects#savedreplyorder", - "/v4/input_object/securityadvisoryidentifierfilter": "/en/graphql/reference/input-objects#securityadvisoryidentifierfilter", - "/en/v4/input_object/securityadvisoryidentifierfilter": "/en/graphql/reference/input-objects#securityadvisoryidentifierfilter", - "/v4/input_object/securityadvisoryorder": "/en/graphql/reference/input-objects#securityadvisoryorder", - "/en/v4/input_object/securityadvisoryorder": "/en/graphql/reference/input-objects#securityadvisoryorder", - "/v4/input_object/securityvulnerabilityorder": "/en/graphql/reference/input-objects#securityvulnerabilityorder", - "/en/v4/input_object/securityvulnerabilityorder": "/en/graphql/reference/input-objects#securityvulnerabilityorder", - "/v4/input_object/setenterpriseidentityproviderinput": "/en/graphql/reference/input-objects#setenterpriseidentityproviderinput", - "/en/v4/input_object/setenterpriseidentityproviderinput": "/en/graphql/reference/input-objects#setenterpriseidentityproviderinput", - "/v4/input_object/sponsorshiporder": "/en/graphql/reference/input-objects#sponsorshiporder", - "/en/v4/input_object/sponsorshiporder": "/en/graphql/reference/input-objects#sponsorshiporder", - "/v4/input_object/sponsorstierorder": "/en/graphql/reference/input-objects#sponsorstierorder", - "/en/v4/input_object/sponsorstierorder": "/en/graphql/reference/input-objects#sponsorstierorder", - "/v4/input_object/starorder": "/en/graphql/reference/input-objects#starorder", - "/en/v4/input_object/starorder": "/en/graphql/reference/input-objects#starorder", - "/v4/input_object/submitpullrequestreviewinput": "/en/graphql/reference/input-objects#submitpullrequestreviewinput", - "/en/v4/input_object/submitpullrequestreviewinput": "/en/graphql/reference/input-objects#submitpullrequestreviewinput", - "/v4/input_object/teamdiscussioncommentorder": "/en/graphql/reference/input-objects#teamdiscussioncommentorder", - "/en/v4/input_object/teamdiscussioncommentorder": "/en/graphql/reference/input-objects#teamdiscussioncommentorder", - "/v4/input_object/teamdiscussionorder": "/en/graphql/reference/input-objects#teamdiscussionorder", - "/en/v4/input_object/teamdiscussionorder": "/en/graphql/reference/input-objects#teamdiscussionorder", - "/v4/input_object/teammemberorder": "/en/graphql/reference/input-objects#teammemberorder", - "/en/v4/input_object/teammemberorder": "/en/graphql/reference/input-objects#teammemberorder", - "/v4/input_object/teamorder": "/en/graphql/reference/input-objects#teamorder", - "/en/v4/input_object/teamorder": "/en/graphql/reference/input-objects#teamorder", - "/v4/input_object/teamrepositoryorder": "/en/graphql/reference/input-objects#teamrepositoryorder", - "/en/v4/input_object/teamrepositoryorder": "/en/graphql/reference/input-objects#teamrepositoryorder", - "/v4/input_object/transferissueinput": "/en/graphql/reference/input-objects#transferissueinput", - "/en/v4/input_object/transferissueinput": "/en/graphql/reference/input-objects#transferissueinput", - "/v4/input_object/unarchiverepositoryinput": "/en/graphql/reference/input-objects#unarchiverepositoryinput", - "/en/v4/input_object/unarchiverepositoryinput": "/en/graphql/reference/input-objects#unarchiverepositoryinput", - "/v4/input_object/unfollowuserinput": "/en/graphql/reference/input-objects#unfollowuserinput", - "/en/v4/input_object/unfollowuserinput": "/en/graphql/reference/input-objects#unfollowuserinput", - "/v4/input_object/unlinkrepositoryfromprojectinput": "/en/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", - "/en/v4/input_object/unlinkrepositoryfromprojectinput": "/en/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", - "/v4/input_object/unlocklockableinput": "/en/graphql/reference/input-objects#unlocklockableinput", - "/en/v4/input_object/unlocklockableinput": "/en/graphql/reference/input-objects#unlocklockableinput", - "/v4/input_object/unmarkissueasduplicateinput": "/en/graphql/reference/input-objects#unmarkissueasduplicateinput", - "/en/v4/input_object/unmarkissueasduplicateinput": "/en/graphql/reference/input-objects#unmarkissueasduplicateinput", - "/v4/input_object/unminimizecommentinput": "/en/graphql/reference/input-objects#unminimizecommentinput", - "/en/v4/input_object/unminimizecommentinput": "/en/graphql/reference/input-objects#unminimizecommentinput", - "/v4/input_object/unpinissueinput": "/en/graphql/reference/input-objects#unpinissueinput", - "/en/v4/input_object/unpinissueinput": "/en/graphql/reference/input-objects#unpinissueinput", - "/v4/input_object/unresolvereviewthreadinput": "/en/graphql/reference/input-objects#unresolvereviewthreadinput", - "/en/v4/input_object/unresolvereviewthreadinput": "/en/graphql/reference/input-objects#unresolvereviewthreadinput", - "/v4/input_object/updatebranchprotectionruleinput": "/en/graphql/reference/input-objects#updatebranchprotectionruleinput", - "/en/v4/input_object/updatebranchprotectionruleinput": "/en/graphql/reference/input-objects#updatebranchprotectionruleinput", - "/v4/input_object/updatecheckruninput": "/en/graphql/reference/input-objects#updatecheckruninput", - "/en/v4/input_object/updatecheckruninput": "/en/graphql/reference/input-objects#updatecheckruninput", - "/v4/input_object/updatechecksuitepreferencesinput": "/en/graphql/reference/input-objects#updatechecksuitepreferencesinput", - "/en/v4/input_object/updatechecksuitepreferencesinput": "/en/graphql/reference/input-objects#updatechecksuitepreferencesinput", - "/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/en/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", - "/en/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/en/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", - "/v4/input_object/updateenterpriseadministratorroleinput": "/en/graphql/reference/input-objects#updateenterpriseadministratorroleinput", - "/en/v4/input_object/updateenterpriseadministratorroleinput": "/en/graphql/reference/input-objects#updateenterpriseadministratorroleinput", - "/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/en/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", - "/en/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/en/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", - "/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/en/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", - "/en/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/en/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", - "/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", - "/en/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", - "/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", - "/en/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", - "/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", - "/en/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", - "/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", - "/en/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", - "/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", - "/en/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", - "/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", - "/en/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", - "/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", - "/en/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", - "/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", - "/en/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/en/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", - "/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/en/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", - "/en/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/en/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", - "/v4/input_object/updateenterpriseprofileinput": "/en/graphql/reference/input-objects#updateenterpriseprofileinput", - "/en/v4/input_object/updateenterpriseprofileinput": "/en/graphql/reference/input-objects#updateenterpriseprofileinput", - "/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/en/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", - "/en/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/en/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", - "/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/en/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", - "/en/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/en/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", - "/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/en/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", - "/en/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/en/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", - "/v4/input_object/updateipallowlistenabledsettinginput": "/en/graphql/reference/input-objects#updateipallowlistenabledsettinginput", - "/en/v4/input_object/updateipallowlistenabledsettinginput": "/en/graphql/reference/input-objects#updateipallowlistenabledsettinginput", - "/v4/input_object/updateipallowlistentryinput": "/en/graphql/reference/input-objects#updateipallowlistentryinput", - "/en/v4/input_object/updateipallowlistentryinput": "/en/graphql/reference/input-objects#updateipallowlistentryinput", - "/v4/input_object/updateissuecommentinput": "/en/graphql/reference/input-objects#updateissuecommentinput", - "/en/v4/input_object/updateissuecommentinput": "/en/graphql/reference/input-objects#updateissuecommentinput", - "/v4/input_object/updateissueinput": "/en/graphql/reference/input-objects#updateissueinput", - "/en/v4/input_object/updateissueinput": "/en/graphql/reference/input-objects#updateissueinput", - "/v4/input_object/updatelabelinput": "/en/graphql/reference/input-objects#updatelabelinput", - "/en/v4/input_object/updatelabelinput": "/en/graphql/reference/input-objects#updatelabelinput", - "/v4/input_object/updateprojectcardinput": "/en/graphql/reference/input-objects#updateprojectcardinput", - "/en/v4/input_object/updateprojectcardinput": "/en/graphql/reference/input-objects#updateprojectcardinput", - "/v4/input_object/updateprojectcolumninput": "/en/graphql/reference/input-objects#updateprojectcolumninput", - "/en/v4/input_object/updateprojectcolumninput": "/en/graphql/reference/input-objects#updateprojectcolumninput", - "/v4/input_object/updateprojectinput": "/en/graphql/reference/input-objects#updateprojectinput", - "/en/v4/input_object/updateprojectinput": "/en/graphql/reference/input-objects#updateprojectinput", - "/v4/input_object/updatepullrequestinput": "/en/graphql/reference/input-objects#updatepullrequestinput", - "/en/v4/input_object/updatepullrequestinput": "/en/graphql/reference/input-objects#updatepullrequestinput", - "/v4/input_object/updatepullrequestreviewcommentinput": "/en/graphql/reference/input-objects#updatepullrequestreviewcommentinput", - "/en/v4/input_object/updatepullrequestreviewcommentinput": "/en/graphql/reference/input-objects#updatepullrequestreviewcommentinput", - "/v4/input_object/updatepullrequestreviewinput": "/en/graphql/reference/input-objects#updatepullrequestreviewinput", - "/en/v4/input_object/updatepullrequestreviewinput": "/en/graphql/reference/input-objects#updatepullrequestreviewinput", - "/v4/input_object/updaterefinput": "/en/graphql/reference/input-objects#updaterefinput", - "/en/v4/input_object/updaterefinput": "/en/graphql/reference/input-objects#updaterefinput", - "/v4/input_object/updaterefsinput": "/en/graphql/reference/input-objects#updaterefsinput", - "/en/v4/input_object/updaterefsinput": "/en/graphql/reference/input-objects#updaterefsinput", - "/v4/input_object/updaterepositoryinput": "/en/graphql/reference/input-objects#updaterepositoryinput", - "/en/v4/input_object/updaterepositoryinput": "/en/graphql/reference/input-objects#updaterepositoryinput", - "/v4/input_object/updatesubscriptioninput": "/en/graphql/reference/input-objects#updatesubscriptioninput", - "/en/v4/input_object/updatesubscriptioninput": "/en/graphql/reference/input-objects#updatesubscriptioninput", - "/v4/input_object/updateteamdiscussioncommentinput": "/en/graphql/reference/input-objects#updateteamdiscussioncommentinput", - "/en/v4/input_object/updateteamdiscussioncommentinput": "/en/graphql/reference/input-objects#updateteamdiscussioncommentinput", - "/v4/input_object/updateteamdiscussioninput": "/en/graphql/reference/input-objects#updateteamdiscussioninput", - "/en/v4/input_object/updateteamdiscussioninput": "/en/graphql/reference/input-objects#updateteamdiscussioninput", - "/v4/input_object/updateteamreviewassignmentinput": "/en/graphql/reference/input-objects#updateteamreviewassignmentinput", - "/en/v4/input_object/updateteamreviewassignmentinput": "/en/graphql/reference/input-objects#updateteamreviewassignmentinput", - "/v4/input_object/updatetopicsinput": "/en/graphql/reference/input-objects#updatetopicsinput", - "/en/v4/input_object/updatetopicsinput": "/en/graphql/reference/input-objects#updatetopicsinput", - "/v4/input_object/userstatusorder": "/en/graphql/reference/input-objects#userstatusorder", - "/en/v4/input_object/userstatusorder": "/en/graphql/reference/input-objects#userstatusorder", - "/v4/interface/actor": "/en/graphql/reference/interfaces#actor", - "/en/v4/interface/actor": "/en/graphql/reference/interfaces#actor", - "/v4/interface/assignable": "/en/graphql/reference/interfaces#assignable", - "/en/v4/interface/assignable": "/en/graphql/reference/interfaces#assignable", - "/v4/interface/auditentry": "/en/graphql/reference/interfaces#auditentry", - "/en/v4/interface/auditentry": "/en/graphql/reference/interfaces#auditentry", - "/v4/interface/closable": "/en/graphql/reference/interfaces#closable", - "/en/v4/interface/closable": "/en/graphql/reference/interfaces#closable", - "/v4/interface/comment": "/en/graphql/reference/interfaces#comment", - "/en/v4/interface/comment": "/en/graphql/reference/interfaces#comment", - "/v4/interface/contribution": "/en/graphql/reference/interfaces#contribution", - "/en/v4/interface/contribution": "/en/graphql/reference/interfaces#contribution", - "/v4/interface/deletable": "/en/graphql/reference/interfaces#deletable", - "/en/v4/interface/deletable": "/en/graphql/reference/interfaces#deletable", - "/v4/interface/enterpriseauditentrydata": "/en/graphql/reference/interfaces#enterpriseauditentrydata", - "/en/v4/interface/enterpriseauditentrydata": "/en/graphql/reference/interfaces#enterpriseauditentrydata", - "/v4/interface/gitobject": "/en/graphql/reference/interfaces#gitobject", - "/en/v4/interface/gitobject": "/en/graphql/reference/interfaces#gitobject", - "/v4/interface/gitsignature": "/en/graphql/reference/interfaces#gitsignature", - "/en/v4/interface/gitsignature": "/en/graphql/reference/interfaces#gitsignature", - "/v4/interface/hovercardcontext": "/en/graphql/reference/interfaces#hovercardcontext", - "/en/v4/interface/hovercardcontext": "/en/graphql/reference/interfaces#hovercardcontext", - "/v4/interface/labelable": "/en/graphql/reference/interfaces#labelable", - "/en/v4/interface/labelable": "/en/graphql/reference/interfaces#labelable", - "/v4/interface/lockable": "/en/graphql/reference/interfaces#lockable", - "/en/v4/interface/lockable": "/en/graphql/reference/interfaces#lockable", - "/v4/interface/memberstatusable": "/en/graphql/reference/interfaces#memberstatusable", - "/en/v4/interface/memberstatusable": "/en/graphql/reference/interfaces#memberstatusable", - "/v4/interface/minimizable": "/en/graphql/reference/interfaces#minimizable", - "/en/v4/interface/minimizable": "/en/graphql/reference/interfaces#minimizable", - "/v4/interface/node": "/en/graphql/reference/interfaces#node", - "/en/v4/interface/node": "/en/graphql/reference/interfaces#node", - "/v4/interface/oauthapplicationauditentrydata": "/en/graphql/reference/interfaces#oauthapplicationauditentrydata", - "/en/v4/interface/oauthapplicationauditentrydata": "/en/graphql/reference/interfaces#oauthapplicationauditentrydata", - "/v4/interface/organizationauditentrydata": "/en/graphql/reference/interfaces#organizationauditentrydata", - "/en/v4/interface/organizationauditentrydata": "/en/graphql/reference/interfaces#organizationauditentrydata", - "/v4/interface/packageowner": "/en/graphql/reference/interfaces#packageowner", - "/en/v4/interface/packageowner": "/en/graphql/reference/interfaces#packageowner", - "/v4/interface/profileowner": "/en/graphql/reference/interfaces#profileowner", - "/en/v4/interface/profileowner": "/en/graphql/reference/interfaces#profileowner", - "/v4/interface/projectowner": "/en/graphql/reference/interfaces#projectowner", - "/en/v4/interface/projectowner": "/en/graphql/reference/interfaces#projectowner", - "/v4/interface/reactable": "/en/graphql/reference/interfaces#reactable", - "/en/v4/interface/reactable": "/en/graphql/reference/interfaces#reactable", - "/v4/interface/repositoryauditentrydata": "/en/graphql/reference/interfaces#repositoryauditentrydata", - "/en/v4/interface/repositoryauditentrydata": "/en/graphql/reference/interfaces#repositoryauditentrydata", - "/v4/interface/repositoryinfo": "/en/graphql/reference/interfaces#repositoryinfo", - "/en/v4/interface/repositoryinfo": "/en/graphql/reference/interfaces#repositoryinfo", - "/v4/interface/repositorynode": "/en/graphql/reference/interfaces#repositorynode", - "/en/v4/interface/repositorynode": "/en/graphql/reference/interfaces#repositorynode", - "/v4/interface/repositoryowner": "/en/graphql/reference/interfaces#repositoryowner", - "/en/v4/interface/repositoryowner": "/en/graphql/reference/interfaces#repositoryowner", - "/v4/interface/sponsorable": "/en/graphql/reference/interfaces#sponsorable", - "/en/v4/interface/sponsorable": "/en/graphql/reference/interfaces#sponsorable", - "/v4/interface/starrable": "/en/graphql/reference/interfaces#starrable", - "/en/v4/interface/starrable": "/en/graphql/reference/interfaces#starrable", - "/v4/interface/subscribable": "/en/graphql/reference/interfaces#subscribable", - "/en/v4/interface/subscribable": "/en/graphql/reference/interfaces#subscribable", - "/v4/interface/teamauditentrydata": "/en/graphql/reference/interfaces#teamauditentrydata", - "/en/v4/interface/teamauditentrydata": "/en/graphql/reference/interfaces#teamauditentrydata", - "/v4/interface/topicauditentrydata": "/en/graphql/reference/interfaces#topicauditentrydata", - "/en/v4/interface/topicauditentrydata": "/en/graphql/reference/interfaces#topicauditentrydata", - "/v4/interface/uniformresourcelocatable": "/en/graphql/reference/interfaces#uniformresourcelocatable", - "/en/v4/interface/uniformresourcelocatable": "/en/graphql/reference/interfaces#uniformresourcelocatable", - "/v4/interface/updatable": "/en/graphql/reference/interfaces#updatable", - "/en/v4/interface/updatable": "/en/graphql/reference/interfaces#updatable", - "/v4/interface/updatablecomment": "/en/graphql/reference/interfaces#updatablecomment", - "/en/v4/interface/updatablecomment": "/en/graphql/reference/interfaces#updatablecomment", - "/v4/mutation/acceptenterpriseadministratorinvitation": "/en/graphql/reference/mutations#acceptenterpriseadministratorinvitation", - "/en/v4/mutation/acceptenterpriseadministratorinvitation": "/en/graphql/reference/mutations#acceptenterpriseadministratorinvitation", - "/v4/mutation/accepttopicsuggestion": "/en/graphql/reference/mutations#accepttopicsuggestion", - "/en/v4/mutation/accepttopicsuggestion": "/en/graphql/reference/mutations#accepttopicsuggestion", - "/v4/mutation/addassigneestoassignable": "/en/graphql/reference/mutations#addassigneestoassignable", - "/en/v4/mutation/addassigneestoassignable": "/en/graphql/reference/mutations#addassigneestoassignable", - "/v4/mutation/addcomment": "/en/graphql/reference/mutations#addcomment", - "/en/v4/mutation/addcomment": "/en/graphql/reference/mutations#addcomment", - "/v4/mutation/addlabelstolabelable": "/en/graphql/reference/mutations#addlabelstolabelable", - "/en/v4/mutation/addlabelstolabelable": "/en/graphql/reference/mutations#addlabelstolabelable", - "/v4/mutation/addprojectcard": "/en/graphql/reference/mutations#addprojectcard", - "/en/v4/mutation/addprojectcard": "/en/graphql/reference/mutations#addprojectcard", - "/v4/mutation/addprojectcolumn": "/en/graphql/reference/mutations#addprojectcolumn", - "/en/v4/mutation/addprojectcolumn": "/en/graphql/reference/mutations#addprojectcolumn", - "/v4/mutation/addpullrequestreview": "/en/graphql/reference/mutations#addpullrequestreview", - "/en/v4/mutation/addpullrequestreview": "/en/graphql/reference/mutations#addpullrequestreview", - "/v4/mutation/addpullrequestreviewcomment": "/en/graphql/reference/mutations#addpullrequestreviewcomment", - "/en/v4/mutation/addpullrequestreviewcomment": "/en/graphql/reference/mutations#addpullrequestreviewcomment", - "/v4/mutation/addpullrequestreviewthread": "/en/graphql/reference/mutations#addpullrequestreviewthread", - "/en/v4/mutation/addpullrequestreviewthread": "/en/graphql/reference/mutations#addpullrequestreviewthread", - "/v4/mutation/addreaction": "/en/graphql/reference/mutations#addreaction", - "/en/v4/mutation/addreaction": "/en/graphql/reference/mutations#addreaction", - "/v4/mutation/addstar": "/en/graphql/reference/mutations#addstar", - "/en/v4/mutation/addstar": "/en/graphql/reference/mutations#addstar", - "/v4/mutation/archiverepository": "/en/graphql/reference/mutations#archiverepository", - "/en/v4/mutation/archiverepository": "/en/graphql/reference/mutations#archiverepository", - "/v4/mutation/cancelenterpriseadmininvitation": "/en/graphql/reference/mutations#cancelenterpriseadmininvitation", - "/en/v4/mutation/cancelenterpriseadmininvitation": "/en/graphql/reference/mutations#cancelenterpriseadmininvitation", - "/v4/mutation/changeuserstatus": "/en/graphql/reference/mutations#changeuserstatus", - "/en/v4/mutation/changeuserstatus": "/en/graphql/reference/mutations#changeuserstatus", - "/v4/mutation/clearlabelsfromlabelable": "/en/graphql/reference/mutations#clearlabelsfromlabelable", - "/en/v4/mutation/clearlabelsfromlabelable": "/en/graphql/reference/mutations#clearlabelsfromlabelable", - "/v4/mutation/cloneproject": "/en/graphql/reference/mutations#cloneproject", - "/en/v4/mutation/cloneproject": "/en/graphql/reference/mutations#cloneproject", - "/v4/mutation/clonetemplaterepository": "/en/graphql/reference/mutations#clonetemplaterepository", - "/en/v4/mutation/clonetemplaterepository": "/en/graphql/reference/mutations#clonetemplaterepository", - "/v4/mutation/closeissue": "/en/graphql/reference/mutations#closeissue", - "/en/v4/mutation/closeissue": "/en/graphql/reference/mutations#closeissue", - "/v4/mutation/closepullrequest": "/en/graphql/reference/mutations#closepullrequest", - "/en/v4/mutation/closepullrequest": "/en/graphql/reference/mutations#closepullrequest", - "/v4/mutation/convertprojectcardnotetoissue": "/en/graphql/reference/mutations#convertprojectcardnotetoissue", - "/en/v4/mutation/convertprojectcardnotetoissue": "/en/graphql/reference/mutations#convertprojectcardnotetoissue", - "/v4/mutation/createbranchprotectionrule": "/en/graphql/reference/mutations#createbranchprotectionrule", - "/en/v4/mutation/createbranchprotectionrule": "/en/graphql/reference/mutations#createbranchprotectionrule", - "/v4/mutation/createcheckrun": "/en/graphql/reference/mutations#createcheckrun", - "/en/v4/mutation/createcheckrun": "/en/graphql/reference/mutations#createcheckrun", - "/v4/mutation/createchecksuite": "/en/graphql/reference/mutations#createchecksuite", - "/en/v4/mutation/createchecksuite": "/en/graphql/reference/mutations#createchecksuite", - "/v4/mutation/createcontentattachment": "/en/graphql/reference/mutations#createcontentattachment", - "/en/v4/mutation/createcontentattachment": "/en/graphql/reference/mutations#createcontentattachment", - "/v4/mutation/createdeployment": "/en/graphql/reference/mutations#createdeployment", - "/en/v4/mutation/createdeployment": "/en/graphql/reference/mutations#createdeployment", - "/v4/mutation/createdeploymentstatus": "/en/graphql/reference/mutations#createdeploymentstatus", - "/en/v4/mutation/createdeploymentstatus": "/en/graphql/reference/mutations#createdeploymentstatus", - "/v4/mutation/createenterpriseorganization": "/en/graphql/reference/mutations#createenterpriseorganization", - "/en/v4/mutation/createenterpriseorganization": "/en/graphql/reference/mutations#createenterpriseorganization", - "/v4/mutation/createipallowlistentry": "/en/graphql/reference/mutations#createipallowlistentry", - "/en/v4/mutation/createipallowlistentry": "/en/graphql/reference/mutations#createipallowlistentry", - "/v4/mutation/createissue": "/en/graphql/reference/mutations#createissue", - "/en/v4/mutation/createissue": "/en/graphql/reference/mutations#createissue", - "/v4/mutation/createlabel": "/en/graphql/reference/mutations#createlabel", - "/en/v4/mutation/createlabel": "/en/graphql/reference/mutations#createlabel", - "/v4/mutation/createproject": "/en/graphql/reference/mutations#createproject", - "/en/v4/mutation/createproject": "/en/graphql/reference/mutations#createproject", - "/v4/mutation/createpullrequest": "/en/graphql/reference/mutations#createpullrequest", - "/en/v4/mutation/createpullrequest": "/en/graphql/reference/mutations#createpullrequest", - "/v4/mutation/createref": "/en/graphql/reference/mutations#createref", - "/en/v4/mutation/createref": "/en/graphql/reference/mutations#createref", - "/v4/mutation/createrepository": "/en/graphql/reference/mutations#createrepository", - "/en/v4/mutation/createrepository": "/en/graphql/reference/mutations#createrepository", - "/v4/mutation/createteamdiscussion": "/en/graphql/reference/mutations#createteamdiscussion", - "/en/v4/mutation/createteamdiscussion": "/en/graphql/reference/mutations#createteamdiscussion", - "/v4/mutation/createteamdiscussioncomment": "/en/graphql/reference/mutations#createteamdiscussioncomment", - "/en/v4/mutation/createteamdiscussioncomment": "/en/graphql/reference/mutations#createteamdiscussioncomment", - "/v4/mutation/declinetopicsuggestion": "/en/graphql/reference/mutations#declinetopicsuggestion", - "/en/v4/mutation/declinetopicsuggestion": "/en/graphql/reference/mutations#declinetopicsuggestion", - "/v4/mutation/deletebranchprotectionrule": "/en/graphql/reference/mutations#deletebranchprotectionrule", - "/en/v4/mutation/deletebranchprotectionrule": "/en/graphql/reference/mutations#deletebranchprotectionrule", - "/v4/mutation/deletedeployment": "/en/graphql/reference/mutations#deletedeployment", - "/en/v4/mutation/deletedeployment": "/en/graphql/reference/mutations#deletedeployment", - "/v4/mutation/deleteipallowlistentry": "/en/graphql/reference/mutations#deleteipallowlistentry", - "/en/v4/mutation/deleteipallowlistentry": "/en/graphql/reference/mutations#deleteipallowlistentry", - "/v4/mutation/deleteissue": "/en/graphql/reference/mutations#deleteissue", - "/en/v4/mutation/deleteissue": "/en/graphql/reference/mutations#deleteissue", - "/v4/mutation/deleteissuecomment": "/en/graphql/reference/mutations#deleteissuecomment", - "/en/v4/mutation/deleteissuecomment": "/en/graphql/reference/mutations#deleteissuecomment", - "/v4/mutation/deletelabel": "/en/graphql/reference/mutations#deletelabel", - "/en/v4/mutation/deletelabel": "/en/graphql/reference/mutations#deletelabel", - "/v4/mutation/deletepackageversion": "/en/graphql/reference/mutations#deletepackageversion", - "/en/v4/mutation/deletepackageversion": "/en/graphql/reference/mutations#deletepackageversion", - "/v4/mutation/deleteproject": "/en/graphql/reference/mutations#deleteproject", - "/en/v4/mutation/deleteproject": "/en/graphql/reference/mutations#deleteproject", - "/v4/mutation/deleteprojectcard": "/en/graphql/reference/mutations#deleteprojectcard", - "/en/v4/mutation/deleteprojectcard": "/en/graphql/reference/mutations#deleteprojectcard", - "/v4/mutation/deleteprojectcolumn": "/en/graphql/reference/mutations#deleteprojectcolumn", - "/en/v4/mutation/deleteprojectcolumn": "/en/graphql/reference/mutations#deleteprojectcolumn", - "/v4/mutation/deletepullrequestreview": "/en/graphql/reference/mutations#deletepullrequestreview", - "/en/v4/mutation/deletepullrequestreview": "/en/graphql/reference/mutations#deletepullrequestreview", - "/v4/mutation/deletepullrequestreviewcomment": "/en/graphql/reference/mutations#deletepullrequestreviewcomment", - "/en/v4/mutation/deletepullrequestreviewcomment": "/en/graphql/reference/mutations#deletepullrequestreviewcomment", - "/v4/mutation/deleteref": "/en/graphql/reference/mutations#deleteref", - "/en/v4/mutation/deleteref": "/en/graphql/reference/mutations#deleteref", - "/v4/mutation/deleteteamdiscussion": "/en/graphql/reference/mutations#deleteteamdiscussion", - "/en/v4/mutation/deleteteamdiscussion": "/en/graphql/reference/mutations#deleteteamdiscussion", - "/v4/mutation/deleteteamdiscussioncomment": "/en/graphql/reference/mutations#deleteteamdiscussioncomment", - "/en/v4/mutation/deleteteamdiscussioncomment": "/en/graphql/reference/mutations#deleteteamdiscussioncomment", - "/v4/mutation/dismisspullrequestreview": "/en/graphql/reference/mutations#dismisspullrequestreview", - "/en/v4/mutation/dismisspullrequestreview": "/en/graphql/reference/mutations#dismisspullrequestreview", - "/v4/mutation/followuser": "/en/graphql/reference/mutations#followuser", - "/en/v4/mutation/followuser": "/en/graphql/reference/mutations#followuser", - "/v4/mutation/importproject": "/en/graphql/reference/mutations#importproject", - "/en/v4/mutation/importproject": "/en/graphql/reference/mutations#importproject", - "/v4/mutation/inviteenterpriseadmin": "/en/graphql/reference/mutations#inviteenterpriseadmin", - "/en/v4/mutation/inviteenterpriseadmin": "/en/graphql/reference/mutations#inviteenterpriseadmin", - "/v4/mutation/linkrepositorytoproject": "/en/graphql/reference/mutations#linkrepositorytoproject", - "/en/v4/mutation/linkrepositorytoproject": "/en/graphql/reference/mutations#linkrepositorytoproject", - "/v4/mutation/locklockable": "/en/graphql/reference/mutations#locklockable", - "/en/v4/mutation/locklockable": "/en/graphql/reference/mutations#locklockable", - "/v4/mutation/markpullrequestreadyforreview": "/en/graphql/reference/mutations#markpullrequestreadyforreview", - "/en/v4/mutation/markpullrequestreadyforreview": "/en/graphql/reference/mutations#markpullrequestreadyforreview", - "/v4/mutation/mergebranch": "/en/graphql/reference/mutations#mergebranch", - "/en/v4/mutation/mergebranch": "/en/graphql/reference/mutations#mergebranch", - "/v4/mutation/mergepullrequest": "/en/graphql/reference/mutations#mergepullrequest", - "/en/v4/mutation/mergepullrequest": "/en/graphql/reference/mutations#mergepullrequest", - "/v4/mutation/minimizecomment": "/en/graphql/reference/mutations#minimizecomment", - "/en/v4/mutation/minimizecomment": "/en/graphql/reference/mutations#minimizecomment", - "/v4/mutation/moveprojectcard": "/en/graphql/reference/mutations#moveprojectcard", - "/en/v4/mutation/moveprojectcard": "/en/graphql/reference/mutations#moveprojectcard", - "/v4/mutation/moveprojectcolumn": "/en/graphql/reference/mutations#moveprojectcolumn", - "/en/v4/mutation/moveprojectcolumn": "/en/graphql/reference/mutations#moveprojectcolumn", - "/v4/mutation/pinissue": "/en/graphql/reference/mutations#pinissue", - "/en/v4/mutation/pinissue": "/en/graphql/reference/mutations#pinissue", - "/v4/mutation/regenerateenterpriseidentityproviderrecoverycodes": "/en/graphql/reference/mutations#regenerateenterpriseidentityproviderrecoverycodes", - "/en/v4/mutation/regenerateenterpriseidentityproviderrecoverycodes": "/en/graphql/reference/mutations#regenerateenterpriseidentityproviderrecoverycodes", - "/v4/mutation/removeassigneesfromassignable": "/en/graphql/reference/mutations#removeassigneesfromassignable", - "/en/v4/mutation/removeassigneesfromassignable": "/en/graphql/reference/mutations#removeassigneesfromassignable", - "/v4/mutation/removeenterpriseadmin": "/en/graphql/reference/mutations#removeenterpriseadmin", - "/en/v4/mutation/removeenterpriseadmin": "/en/graphql/reference/mutations#removeenterpriseadmin", - "/v4/mutation/removeenterpriseidentityprovider": "/en/graphql/reference/mutations#removeenterpriseidentityprovider", - "/en/v4/mutation/removeenterpriseidentityprovider": "/en/graphql/reference/mutations#removeenterpriseidentityprovider", - "/v4/mutation/removeenterpriseorganization": "/en/graphql/reference/mutations#removeenterpriseorganization", - "/en/v4/mutation/removeenterpriseorganization": "/en/graphql/reference/mutations#removeenterpriseorganization", - "/v4/mutation/removelabelsfromlabelable": "/en/graphql/reference/mutations#removelabelsfromlabelable", - "/en/v4/mutation/removelabelsfromlabelable": "/en/graphql/reference/mutations#removelabelsfromlabelable", - "/v4/mutation/removeoutsidecollaborator": "/en/graphql/reference/mutations#removeoutsidecollaborator", - "/en/v4/mutation/removeoutsidecollaborator": "/en/graphql/reference/mutations#removeoutsidecollaborator", - "/v4/mutation/removereaction": "/en/graphql/reference/mutations#removereaction", - "/en/v4/mutation/removereaction": "/en/graphql/reference/mutations#removereaction", - "/v4/mutation/removestar": "/en/graphql/reference/mutations#removestar", - "/en/v4/mutation/removestar": "/en/graphql/reference/mutations#removestar", - "/v4/mutation/reopenissue": "/en/graphql/reference/mutations#reopenissue", - "/en/v4/mutation/reopenissue": "/en/graphql/reference/mutations#reopenissue", - "/v4/mutation/reopenpullrequest": "/en/graphql/reference/mutations#reopenpullrequest", - "/en/v4/mutation/reopenpullrequest": "/en/graphql/reference/mutations#reopenpullrequest", - "/v4/mutation/requestreviews": "/en/graphql/reference/mutations#requestreviews", - "/en/v4/mutation/requestreviews": "/en/graphql/reference/mutations#requestreviews", - "/v4/mutation/rerequestchecksuite": "/en/graphql/reference/mutations#rerequestchecksuite", - "/en/v4/mutation/rerequestchecksuite": "/en/graphql/reference/mutations#rerequestchecksuite", - "/v4/mutation/resolvereviewthread": "/en/graphql/reference/mutations#resolvereviewthread", - "/en/v4/mutation/resolvereviewthread": "/en/graphql/reference/mutations#resolvereviewthread", - "/v4/mutation/setenterpriseidentityprovider": "/en/graphql/reference/mutations#setenterpriseidentityprovider", - "/en/v4/mutation/setenterpriseidentityprovider": "/en/graphql/reference/mutations#setenterpriseidentityprovider", - "/v4/mutation/submitpullrequestreview": "/en/graphql/reference/mutations#submitpullrequestreview", - "/en/v4/mutation/submitpullrequestreview": "/en/graphql/reference/mutations#submitpullrequestreview", - "/v4/mutation/transferissue": "/en/graphql/reference/mutations#transferissue", - "/en/v4/mutation/transferissue": "/en/graphql/reference/mutations#transferissue", - "/v4/mutation/unarchiverepository": "/en/graphql/reference/mutations#unarchiverepository", - "/en/v4/mutation/unarchiverepository": "/en/graphql/reference/mutations#unarchiverepository", - "/v4/mutation/unfollowuser": "/en/graphql/reference/mutations#unfollowuser", - "/en/v4/mutation/unfollowuser": "/en/graphql/reference/mutations#unfollowuser", - "/v4/mutation/unlinkrepositoryfromproject": "/en/graphql/reference/mutations#unlinkrepositoryfromproject", - "/en/v4/mutation/unlinkrepositoryfromproject": "/en/graphql/reference/mutations#unlinkrepositoryfromproject", - "/v4/mutation/unlocklockable": "/en/graphql/reference/mutations#unlocklockable", - "/en/v4/mutation/unlocklockable": "/en/graphql/reference/mutations#unlocklockable", - "/v4/mutation/unmarkissueasduplicate": "/en/graphql/reference/mutations#unmarkissueasduplicate", - "/en/v4/mutation/unmarkissueasduplicate": "/en/graphql/reference/mutations#unmarkissueasduplicate", - "/v4/mutation/unminimizecomment": "/en/graphql/reference/mutations#unminimizecomment", - "/en/v4/mutation/unminimizecomment": "/en/graphql/reference/mutations#unminimizecomment", - "/v4/mutation/unpinissue": "/en/graphql/reference/mutations#unpinissue", - "/en/v4/mutation/unpinissue": "/en/graphql/reference/mutations#unpinissue", - "/v4/mutation/unresolvereviewthread": "/en/graphql/reference/mutations#unresolvereviewthread", - "/en/v4/mutation/unresolvereviewthread": "/en/graphql/reference/mutations#unresolvereviewthread", - "/v4/mutation/updatebranchprotectionrule": "/en/graphql/reference/mutations#updatebranchprotectionrule", - "/en/v4/mutation/updatebranchprotectionrule": "/en/graphql/reference/mutations#updatebranchprotectionrule", - "/v4/mutation/updatecheckrun": "/en/graphql/reference/mutations#updatecheckrun", - "/en/v4/mutation/updatecheckrun": "/en/graphql/reference/mutations#updatecheckrun", - "/v4/mutation/updatechecksuitepreferences": "/en/graphql/reference/mutations#updatechecksuitepreferences", - "/en/v4/mutation/updatechecksuitepreferences": "/en/graphql/reference/mutations#updatechecksuitepreferences", - "/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/en/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", - "/en/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/en/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", - "/v4/mutation/updateenterpriseadministratorrole": "/en/graphql/reference/mutations#updateenterpriseadministratorrole", - "/en/v4/mutation/updateenterpriseadministratorrole": "/en/graphql/reference/mutations#updateenterpriseadministratorrole", - "/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/en/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", - "/en/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/en/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", - "/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/en/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", - "/en/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/en/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", - "/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/en/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", - "/en/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/en/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", - "/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/en/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", - "/en/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/en/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", - "/v4/mutation/updateenterprisememberscandeleteissuessetting": "/en/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", - "/en/v4/mutation/updateenterprisememberscandeleteissuessetting": "/en/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", - "/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/en/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", - "/en/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/en/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", - "/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/en/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", - "/en/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/en/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", - "/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/en/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", - "/en/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/en/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", - "/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/en/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", - "/en/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/en/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", - "/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/en/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", - "/en/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/en/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", - "/v4/mutation/updateenterpriseorganizationprojectssetting": "/en/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", - "/en/v4/mutation/updateenterpriseorganizationprojectssetting": "/en/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", - "/v4/mutation/updateenterpriseprofile": "/en/graphql/reference/mutations#updateenterpriseprofile", - "/en/v4/mutation/updateenterpriseprofile": "/en/graphql/reference/mutations#updateenterpriseprofile", - "/v4/mutation/updateenterpriserepositoryprojectssetting": "/en/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", - "/en/v4/mutation/updateenterpriserepositoryprojectssetting": "/en/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", - "/v4/mutation/updateenterpriseteamdiscussionssetting": "/en/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", - "/en/v4/mutation/updateenterpriseteamdiscussionssetting": "/en/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", - "/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/en/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", - "/en/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/en/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", - "/v4/mutation/updateipallowlistenabledsetting": "/en/graphql/reference/mutations#updateipallowlistenabledsetting", - "/en/v4/mutation/updateipallowlistenabledsetting": "/en/graphql/reference/mutations#updateipallowlistenabledsetting", - "/v4/mutation/updateipallowlistentry": "/en/graphql/reference/mutations#updateipallowlistentry", - "/en/v4/mutation/updateipallowlistentry": "/en/graphql/reference/mutations#updateipallowlistentry", - "/v4/mutation/updateissue": "/en/graphql/reference/mutations#updateissue", - "/en/v4/mutation/updateissue": "/en/graphql/reference/mutations#updateissue", - "/v4/mutation/updateissuecomment": "/en/graphql/reference/mutations#updateissuecomment", - "/en/v4/mutation/updateissuecomment": "/en/graphql/reference/mutations#updateissuecomment", - "/v4/mutation/updatelabel": "/en/graphql/reference/mutations#updatelabel", - "/en/v4/mutation/updatelabel": "/en/graphql/reference/mutations#updatelabel", - "/v4/mutation/updateproject": "/en/graphql/reference/mutations#updateproject", - "/en/v4/mutation/updateproject": "/en/graphql/reference/mutations#updateproject", - "/v4/mutation/updateprojectcard": "/en/graphql/reference/mutations#updateprojectcard", - "/en/v4/mutation/updateprojectcard": "/en/graphql/reference/mutations#updateprojectcard", - "/v4/mutation/updateprojectcolumn": "/en/graphql/reference/mutations#updateprojectcolumn", - "/en/v4/mutation/updateprojectcolumn": "/en/graphql/reference/mutations#updateprojectcolumn", - "/v4/mutation/updatepullrequest": "/en/graphql/reference/mutations#updatepullrequest", - "/en/v4/mutation/updatepullrequest": "/en/graphql/reference/mutations#updatepullrequest", - "/v4/mutation/updatepullrequestreview": "/en/graphql/reference/mutations#updatepullrequestreview", - "/en/v4/mutation/updatepullrequestreview": "/en/graphql/reference/mutations#updatepullrequestreview", - "/v4/mutation/updatepullrequestreviewcomment": "/en/graphql/reference/mutations#updatepullrequestreviewcomment", - "/en/v4/mutation/updatepullrequestreviewcomment": "/en/graphql/reference/mutations#updatepullrequestreviewcomment", - "/v4/mutation/updateref": "/en/graphql/reference/mutations#updateref", - "/en/v4/mutation/updateref": "/en/graphql/reference/mutations#updateref", - "/v4/mutation/updaterefs": "/en/graphql/reference/mutations#updaterefs", - "/en/v4/mutation/updaterefs": "/en/graphql/reference/mutations#updaterefs", - "/v4/mutation/updaterepository": "/en/graphql/reference/mutations#updaterepository", - "/en/v4/mutation/updaterepository": "/en/graphql/reference/mutations#updaterepository", - "/v4/mutation/updatesubscription": "/en/graphql/reference/mutations#updatesubscription", - "/en/v4/mutation/updatesubscription": "/en/graphql/reference/mutations#updatesubscription", - "/v4/mutation/updateteamdiscussion": "/en/graphql/reference/mutations#updateteamdiscussion", - "/en/v4/mutation/updateteamdiscussion": "/en/graphql/reference/mutations#updateteamdiscussion", - "/v4/mutation/updateteamdiscussioncomment": "/en/graphql/reference/mutations#updateteamdiscussioncomment", - "/en/v4/mutation/updateteamdiscussioncomment": "/en/graphql/reference/mutations#updateteamdiscussioncomment", - "/v4/mutation/updateteamreviewassignment": "/en/graphql/reference/mutations#updateteamreviewassignment", - "/en/v4/mutation/updateteamreviewassignment": "/en/graphql/reference/mutations#updateteamreviewassignment", - "/v4/mutation/updatetopics": "/en/graphql/reference/mutations#updatetopics", - "/en/v4/mutation/updatetopics": "/en/graphql/reference/mutations#updatetopics", - "/v4/object/__directive": "/en/graphql/reference/objects#__directive", - "/en/v4/object/__directive": "/en/graphql/reference/objects#__directive", - "/v4/object/__enumvalue": "/en/graphql/reference/objects#__enumvalue", - "/en/v4/object/__enumvalue": "/en/graphql/reference/objects#__enumvalue", - "/v4/object/__field": "/en/graphql/reference/objects#__field", - "/en/v4/object/__field": "/en/graphql/reference/objects#__field", - "/v4/object/__inputvalue": "/en/graphql/reference/objects#__inputvalue", - "/en/v4/object/__inputvalue": "/en/graphql/reference/objects#__inputvalue", - "/v4/object/__schema": "/en/graphql/reference/objects#__schema", - "/en/v4/object/__schema": "/en/graphql/reference/objects#__schema", - "/v4/object/__type": "/en/graphql/reference/objects#__type", - "/en/v4/object/__type": "/en/graphql/reference/objects#__type", - "/v4/object/acceptenterpriseadministratorinvitationpayload": "/en/graphql/reference/objects#acceptenterpriseadministratorinvitationpayload", - "/en/v4/object/acceptenterpriseadministratorinvitationpayload": "/en/graphql/reference/objects#acceptenterpriseadministratorinvitationpayload", - "/v4/object/accepttopicsuggestionpayload": "/en/graphql/reference/objects#accepttopicsuggestionpayload", - "/en/v4/object/accepttopicsuggestionpayload": "/en/graphql/reference/objects#accepttopicsuggestionpayload", - "/v4/object/actorlocation": "/en/graphql/reference/objects#actorlocation", - "/en/v4/object/actorlocation": "/en/graphql/reference/objects#actorlocation", - "/v4/object/addassigneestoassignablepayload": "/en/graphql/reference/objects#addassigneestoassignablepayload", - "/en/v4/object/addassigneestoassignablepayload": "/en/graphql/reference/objects#addassigneestoassignablepayload", - "/v4/object/addcommentpayload": "/en/graphql/reference/objects#addcommentpayload", - "/en/v4/object/addcommentpayload": "/en/graphql/reference/objects#addcommentpayload", - "/v4/object/addedtoprojectevent": "/en/graphql/reference/objects#addedtoprojectevent", - "/en/v4/object/addedtoprojectevent": "/en/graphql/reference/objects#addedtoprojectevent", - "/v4/object/addlabelstolabelablepayload": "/en/graphql/reference/objects#addlabelstolabelablepayload", - "/en/v4/object/addlabelstolabelablepayload": "/en/graphql/reference/objects#addlabelstolabelablepayload", - "/v4/object/addprojectcardpayload": "/en/graphql/reference/objects#addprojectcardpayload", - "/en/v4/object/addprojectcardpayload": "/en/graphql/reference/objects#addprojectcardpayload", - "/v4/object/addprojectcolumnpayload": "/en/graphql/reference/objects#addprojectcolumnpayload", - "/en/v4/object/addprojectcolumnpayload": "/en/graphql/reference/objects#addprojectcolumnpayload", - "/v4/object/addpullrequestreviewcommentpayload": "/en/graphql/reference/objects#addpullrequestreviewcommentpayload", - "/en/v4/object/addpullrequestreviewcommentpayload": "/en/graphql/reference/objects#addpullrequestreviewcommentpayload", - "/v4/object/addpullrequestreviewpayload": "/en/graphql/reference/objects#addpullrequestreviewpayload", - "/en/v4/object/addpullrequestreviewpayload": "/en/graphql/reference/objects#addpullrequestreviewpayload", - "/v4/object/addpullrequestreviewthreadpayload": "/en/graphql/reference/objects#addpullrequestreviewthreadpayload", - "/en/v4/object/addpullrequestreviewthreadpayload": "/en/graphql/reference/objects#addpullrequestreviewthreadpayload", - "/v4/object/addreactionpayload": "/en/graphql/reference/objects#addreactionpayload", - "/en/v4/object/addreactionpayload": "/en/graphql/reference/objects#addreactionpayload", - "/v4/object/addstarpayload": "/en/graphql/reference/objects#addstarpayload", - "/en/v4/object/addstarpayload": "/en/graphql/reference/objects#addstarpayload", - "/v4/object/app": "/en/graphql/reference/objects#app", - "/en/v4/object/app": "/en/graphql/reference/objects#app", - "/v4/object/archiverepositorypayload": "/en/graphql/reference/objects#archiverepositorypayload", - "/en/v4/object/archiverepositorypayload": "/en/graphql/reference/objects#archiverepositorypayload", - "/v4/object/assignedevent": "/en/graphql/reference/objects#assignedevent", - "/en/v4/object/assignedevent": "/en/graphql/reference/objects#assignedevent", - "/v4/object/automaticbasechangefailedevent": "/en/graphql/reference/objects#automaticbasechangefailedevent", - "/en/v4/object/automaticbasechangefailedevent": "/en/graphql/reference/objects#automaticbasechangefailedevent", - "/v4/object/automaticbasechangesucceededevent": "/en/graphql/reference/objects#automaticbasechangesucceededevent", - "/en/v4/object/automaticbasechangesucceededevent": "/en/graphql/reference/objects#automaticbasechangesucceededevent", - "/v4/object/baserefchangedevent": "/en/graphql/reference/objects#baserefchangedevent", - "/en/v4/object/baserefchangedevent": "/en/graphql/reference/objects#baserefchangedevent", - "/v4/object/baserefforcepushedevent": "/en/graphql/reference/objects#baserefforcepushedevent", - "/en/v4/object/baserefforcepushedevent": "/en/graphql/reference/objects#baserefforcepushedevent", - "/v4/object/blame": "/en/graphql/reference/objects#blame", - "/en/v4/object/blame": "/en/graphql/reference/objects#blame", - "/v4/object/blamerange": "/en/graphql/reference/objects#blamerange", - "/en/v4/object/blamerange": "/en/graphql/reference/objects#blamerange", - "/v4/object/blob": "/en/graphql/reference/objects#blob", - "/en/v4/object/blob": "/en/graphql/reference/objects#blob", - "/v4/object/bot": "/en/graphql/reference/objects#bot", - "/en/v4/object/bot": "/en/graphql/reference/objects#bot", - "/v4/object/branchprotectionrule": "/en/graphql/reference/objects#branchprotectionrule", - "/en/v4/object/branchprotectionrule": "/en/graphql/reference/objects#branchprotectionrule", - "/v4/object/branchprotectionruleconflict": "/en/graphql/reference/objects#branchprotectionruleconflict", - "/en/v4/object/branchprotectionruleconflict": "/en/graphql/reference/objects#branchprotectionruleconflict", - "/v4/object/branchprotectionruleconflictconnection": "/en/graphql/reference/objects#branchprotectionruleconflictconnection", - "/en/v4/object/branchprotectionruleconflictconnection": "/en/graphql/reference/objects#branchprotectionruleconflictconnection", - "/v4/object/branchprotectionruleconflictedge": "/en/graphql/reference/objects#branchprotectionruleconflictedge", - "/en/v4/object/branchprotectionruleconflictedge": "/en/graphql/reference/objects#branchprotectionruleconflictedge", - "/v4/object/branchprotectionruleconnection": "/en/graphql/reference/objects#branchprotectionruleconnection", - "/en/v4/object/branchprotectionruleconnection": "/en/graphql/reference/objects#branchprotectionruleconnection", - "/v4/object/branchprotectionruleedge": "/en/graphql/reference/objects#branchprotectionruleedge", - "/en/v4/object/branchprotectionruleedge": "/en/graphql/reference/objects#branchprotectionruleedge", - "/v4/object/cancelenterpriseadmininvitationpayload": "/en/graphql/reference/objects#cancelenterpriseadmininvitationpayload", - "/en/v4/object/cancelenterpriseadmininvitationpayload": "/en/graphql/reference/objects#cancelenterpriseadmininvitationpayload", - "/v4/object/changeuserstatuspayload": "/en/graphql/reference/objects#changeuserstatuspayload", - "/en/v4/object/changeuserstatuspayload": "/en/graphql/reference/objects#changeuserstatuspayload", - "/v4/object/checkannotation": "/en/graphql/reference/objects#checkannotation", - "/en/v4/object/checkannotation": "/en/graphql/reference/objects#checkannotation", - "/v4/object/checkannotationconnection": "/en/graphql/reference/objects#checkannotationconnection", - "/en/v4/object/checkannotationconnection": "/en/graphql/reference/objects#checkannotationconnection", - "/v4/object/checkannotationedge": "/en/graphql/reference/objects#checkannotationedge", - "/en/v4/object/checkannotationedge": "/en/graphql/reference/objects#checkannotationedge", - "/v4/object/checkannotationposition": "/en/graphql/reference/objects#checkannotationposition", - "/en/v4/object/checkannotationposition": "/en/graphql/reference/objects#checkannotationposition", - "/v4/object/checkannotationspan": "/en/graphql/reference/objects#checkannotationspan", - "/en/v4/object/checkannotationspan": "/en/graphql/reference/objects#checkannotationspan", - "/v4/object/checkrun": "/en/graphql/reference/objects#checkrun", - "/en/v4/object/checkrun": "/en/graphql/reference/objects#checkrun", - "/v4/object/checkrunconnection": "/en/graphql/reference/objects#checkrunconnection", - "/en/v4/object/checkrunconnection": "/en/graphql/reference/objects#checkrunconnection", - "/v4/object/checkrunedge": "/en/graphql/reference/objects#checkrunedge", - "/en/v4/object/checkrunedge": "/en/graphql/reference/objects#checkrunedge", - "/v4/object/checksuite": "/en/graphql/reference/objects#checksuite", - "/en/v4/object/checksuite": "/en/graphql/reference/objects#checksuite", - "/v4/object/checksuiteconnection": "/en/graphql/reference/objects#checksuiteconnection", - "/en/v4/object/checksuiteconnection": "/en/graphql/reference/objects#checksuiteconnection", - "/v4/object/checksuiteedge": "/en/graphql/reference/objects#checksuiteedge", - "/en/v4/object/checksuiteedge": "/en/graphql/reference/objects#checksuiteedge", - "/v4/object/clearlabelsfromlabelablepayload": "/en/graphql/reference/objects#clearlabelsfromlabelablepayload", - "/en/v4/object/clearlabelsfromlabelablepayload": "/en/graphql/reference/objects#clearlabelsfromlabelablepayload", - "/v4/object/cloneprojectpayload": "/en/graphql/reference/objects#cloneprojectpayload", - "/en/v4/object/cloneprojectpayload": "/en/graphql/reference/objects#cloneprojectpayload", - "/v4/object/clonetemplaterepositorypayload": "/en/graphql/reference/objects#clonetemplaterepositorypayload", - "/en/v4/object/clonetemplaterepositorypayload": "/en/graphql/reference/objects#clonetemplaterepositorypayload", - "/v4/object/closedevent": "/en/graphql/reference/objects#closedevent", - "/en/v4/object/closedevent": "/en/graphql/reference/objects#closedevent", - "/v4/object/closeissuepayload": "/en/graphql/reference/objects#closeissuepayload", - "/en/v4/object/closeissuepayload": "/en/graphql/reference/objects#closeissuepayload", - "/v4/object/closepullrequestpayload": "/en/graphql/reference/objects#closepullrequestpayload", - "/en/v4/object/closepullrequestpayload": "/en/graphql/reference/objects#closepullrequestpayload", - "/v4/object/codeofconduct": "/en/graphql/reference/objects#codeofconduct", - "/en/v4/object/codeofconduct": "/en/graphql/reference/objects#codeofconduct", - "/v4/object/commentdeletedevent": "/en/graphql/reference/objects#commentdeletedevent", - "/en/v4/object/commentdeletedevent": "/en/graphql/reference/objects#commentdeletedevent", - "/v4/object/commit": "/en/graphql/reference/objects#commit", - "/en/v4/object/commit": "/en/graphql/reference/objects#commit", - "/v4/object/commitcomment": "/en/graphql/reference/objects#commitcomment", - "/en/v4/object/commitcomment": "/en/graphql/reference/objects#commitcomment", - "/v4/object/commitcommentconnection": "/en/graphql/reference/objects#commitcommentconnection", - "/en/v4/object/commitcommentconnection": "/en/graphql/reference/objects#commitcommentconnection", - "/v4/object/commitcommentedge": "/en/graphql/reference/objects#commitcommentedge", - "/en/v4/object/commitcommentedge": "/en/graphql/reference/objects#commitcommentedge", - "/v4/object/commitcommentthread": "/en/graphql/reference/objects#commitcommentthread", - "/en/v4/object/commitcommentthread": "/en/graphql/reference/objects#commitcommentthread", - "/v4/object/commitconnection": "/en/graphql/reference/objects#commitconnection", - "/en/v4/object/commitconnection": "/en/graphql/reference/objects#commitconnection", - "/v4/object/commitcontributionsbyrepository": "/en/graphql/reference/objects#commitcontributionsbyrepository", - "/en/v4/object/commitcontributionsbyrepository": "/en/graphql/reference/objects#commitcontributionsbyrepository", - "/v4/object/commitedge": "/en/graphql/reference/objects#commitedge", - "/en/v4/object/commitedge": "/en/graphql/reference/objects#commitedge", - "/v4/object/commithistoryconnection": "/en/graphql/reference/objects#commithistoryconnection", - "/en/v4/object/commithistoryconnection": "/en/graphql/reference/objects#commithistoryconnection", - "/v4/object/connectedevent": "/en/graphql/reference/objects#connectedevent", - "/en/v4/object/connectedevent": "/en/graphql/reference/objects#connectedevent", - "/v4/object/contentattachment": "/en/graphql/reference/objects#contentattachment", - "/en/v4/object/contentattachment": "/en/graphql/reference/objects#contentattachment", - "/v4/object/contentreference": "/en/graphql/reference/objects#contentreference", - "/en/v4/object/contentreference": "/en/graphql/reference/objects#contentreference", - "/v4/object/contributioncalendar": "/en/graphql/reference/objects#contributioncalendar", - "/en/v4/object/contributioncalendar": "/en/graphql/reference/objects#contributioncalendar", - "/v4/object/contributioncalendarday": "/en/graphql/reference/objects#contributioncalendarday", - "/en/v4/object/contributioncalendarday": "/en/graphql/reference/objects#contributioncalendarday", - "/v4/object/contributioncalendarmonth": "/en/graphql/reference/objects#contributioncalendarmonth", - "/en/v4/object/contributioncalendarmonth": "/en/graphql/reference/objects#contributioncalendarmonth", - "/v4/object/contributioncalendarweek": "/en/graphql/reference/objects#contributioncalendarweek", - "/en/v4/object/contributioncalendarweek": "/en/graphql/reference/objects#contributioncalendarweek", - "/v4/object/contributionscollection": "/en/graphql/reference/objects#contributionscollection", - "/en/v4/object/contributionscollection": "/en/graphql/reference/objects#contributionscollection", - "/v4/object/convertednotetoissueevent": "/en/graphql/reference/objects#convertednotetoissueevent", - "/en/v4/object/convertednotetoissueevent": "/en/graphql/reference/objects#convertednotetoissueevent", - "/v4/object/convertprojectcardnotetoissuepayload": "/en/graphql/reference/objects#convertprojectcardnotetoissuepayload", - "/en/v4/object/convertprojectcardnotetoissuepayload": "/en/graphql/reference/objects#convertprojectcardnotetoissuepayload", - "/v4/object/converttodraftevent": "/en/graphql/reference/objects#converttodraftevent", - "/en/v4/object/converttodraftevent": "/en/graphql/reference/objects#converttodraftevent", - "/v4/object/createbranchprotectionrulepayload": "/en/graphql/reference/objects#createbranchprotectionrulepayload", - "/en/v4/object/createbranchprotectionrulepayload": "/en/graphql/reference/objects#createbranchprotectionrulepayload", - "/v4/object/createcheckrunpayload": "/en/graphql/reference/objects#createcheckrunpayload", - "/en/v4/object/createcheckrunpayload": "/en/graphql/reference/objects#createcheckrunpayload", - "/v4/object/createchecksuitepayload": "/en/graphql/reference/objects#createchecksuitepayload", - "/en/v4/object/createchecksuitepayload": "/en/graphql/reference/objects#createchecksuitepayload", - "/v4/object/createcontentattachmentpayload": "/en/graphql/reference/objects#createcontentattachmentpayload", - "/en/v4/object/createcontentattachmentpayload": "/en/graphql/reference/objects#createcontentattachmentpayload", - "/v4/object/createdcommitcontribution": "/en/graphql/reference/objects#createdcommitcontribution", - "/en/v4/object/createdcommitcontribution": "/en/graphql/reference/objects#createdcommitcontribution", - "/v4/object/createdcommitcontributionconnection": "/en/graphql/reference/objects#createdcommitcontributionconnection", - "/en/v4/object/createdcommitcontributionconnection": "/en/graphql/reference/objects#createdcommitcontributionconnection", - "/v4/object/createdcommitcontributionedge": "/en/graphql/reference/objects#createdcommitcontributionedge", - "/en/v4/object/createdcommitcontributionedge": "/en/graphql/reference/objects#createdcommitcontributionedge", - "/v4/object/createdeploymentpayload": "/en/graphql/reference/objects#createdeploymentpayload", - "/en/v4/object/createdeploymentpayload": "/en/graphql/reference/objects#createdeploymentpayload", - "/v4/object/createdeploymentstatuspayload": "/en/graphql/reference/objects#createdeploymentstatuspayload", - "/en/v4/object/createdeploymentstatuspayload": "/en/graphql/reference/objects#createdeploymentstatuspayload", - "/v4/object/createdissuecontribution": "/en/graphql/reference/objects#createdissuecontribution", - "/en/v4/object/createdissuecontribution": "/en/graphql/reference/objects#createdissuecontribution", - "/v4/object/createdissuecontributionconnection": "/en/graphql/reference/objects#createdissuecontributionconnection", - "/en/v4/object/createdissuecontributionconnection": "/en/graphql/reference/objects#createdissuecontributionconnection", - "/v4/object/createdissuecontributionedge": "/en/graphql/reference/objects#createdissuecontributionedge", - "/en/v4/object/createdissuecontributionedge": "/en/graphql/reference/objects#createdissuecontributionedge", - "/v4/object/createdpullrequestcontribution": "/en/graphql/reference/objects#createdpullrequestcontribution", - "/en/v4/object/createdpullrequestcontribution": "/en/graphql/reference/objects#createdpullrequestcontribution", - "/v4/object/createdpullrequestcontributionconnection": "/en/graphql/reference/objects#createdpullrequestcontributionconnection", - "/en/v4/object/createdpullrequestcontributionconnection": "/en/graphql/reference/objects#createdpullrequestcontributionconnection", - "/v4/object/createdpullrequestcontributionedge": "/en/graphql/reference/objects#createdpullrequestcontributionedge", - "/en/v4/object/createdpullrequestcontributionedge": "/en/graphql/reference/objects#createdpullrequestcontributionedge", - "/v4/object/createdpullrequestreviewcontribution": "/en/graphql/reference/objects#createdpullrequestreviewcontribution", - "/en/v4/object/createdpullrequestreviewcontribution": "/en/graphql/reference/objects#createdpullrequestreviewcontribution", - "/v4/object/createdpullrequestreviewcontributionconnection": "/en/graphql/reference/objects#createdpullrequestreviewcontributionconnection", - "/en/v4/object/createdpullrequestreviewcontributionconnection": "/en/graphql/reference/objects#createdpullrequestreviewcontributionconnection", - "/v4/object/createdpullrequestreviewcontributionedge": "/en/graphql/reference/objects#createdpullrequestreviewcontributionedge", - "/en/v4/object/createdpullrequestreviewcontributionedge": "/en/graphql/reference/objects#createdpullrequestreviewcontributionedge", - "/v4/object/createdrepositorycontribution": "/en/graphql/reference/objects#createdrepositorycontribution", - "/en/v4/object/createdrepositorycontribution": "/en/graphql/reference/objects#createdrepositorycontribution", - "/v4/object/createdrepositorycontributionconnection": "/en/graphql/reference/objects#createdrepositorycontributionconnection", - "/en/v4/object/createdrepositorycontributionconnection": "/en/graphql/reference/objects#createdrepositorycontributionconnection", - "/v4/object/createdrepositorycontributionedge": "/en/graphql/reference/objects#createdrepositorycontributionedge", - "/en/v4/object/createdrepositorycontributionedge": "/en/graphql/reference/objects#createdrepositorycontributionedge", - "/v4/object/createenterpriseorganizationpayload": "/en/graphql/reference/objects#createenterpriseorganizationpayload", - "/en/v4/object/createenterpriseorganizationpayload": "/en/graphql/reference/objects#createenterpriseorganizationpayload", - "/v4/object/createipallowlistentrypayload": "/en/graphql/reference/objects#createipallowlistentrypayload", - "/en/v4/object/createipallowlistentrypayload": "/en/graphql/reference/objects#createipallowlistentrypayload", - "/v4/object/createissuepayload": "/en/graphql/reference/objects#createissuepayload", - "/en/v4/object/createissuepayload": "/en/graphql/reference/objects#createissuepayload", - "/v4/object/createlabelpayload": "/en/graphql/reference/objects#createlabelpayload", - "/en/v4/object/createlabelpayload": "/en/graphql/reference/objects#createlabelpayload", - "/v4/object/createprojectpayload": "/en/graphql/reference/objects#createprojectpayload", - "/en/v4/object/createprojectpayload": "/en/graphql/reference/objects#createprojectpayload", - "/v4/object/createpullrequestpayload": "/en/graphql/reference/objects#createpullrequestpayload", - "/en/v4/object/createpullrequestpayload": "/en/graphql/reference/objects#createpullrequestpayload", - "/v4/object/createrefpayload": "/en/graphql/reference/objects#createrefpayload", - "/en/v4/object/createrefpayload": "/en/graphql/reference/objects#createrefpayload", - "/v4/object/createrepositorypayload": "/en/graphql/reference/objects#createrepositorypayload", - "/en/v4/object/createrepositorypayload": "/en/graphql/reference/objects#createrepositorypayload", - "/v4/object/createteamdiscussioncommentpayload": "/en/graphql/reference/objects#createteamdiscussioncommentpayload", - "/en/v4/object/createteamdiscussioncommentpayload": "/en/graphql/reference/objects#createteamdiscussioncommentpayload", - "/v4/object/createteamdiscussionpayload": "/en/graphql/reference/objects#createteamdiscussionpayload", - "/en/v4/object/createteamdiscussionpayload": "/en/graphql/reference/objects#createteamdiscussionpayload", - "/v4/object/crossreferencedevent": "/en/graphql/reference/objects#crossreferencedevent", - "/en/v4/object/crossreferencedevent": "/en/graphql/reference/objects#crossreferencedevent", - "/v4/object/declinetopicsuggestionpayload": "/en/graphql/reference/objects#declinetopicsuggestionpayload", - "/en/v4/object/declinetopicsuggestionpayload": "/en/graphql/reference/objects#declinetopicsuggestionpayload", - "/v4/object/deletebranchprotectionrulepayload": "/en/graphql/reference/objects#deletebranchprotectionrulepayload", - "/en/v4/object/deletebranchprotectionrulepayload": "/en/graphql/reference/objects#deletebranchprotectionrulepayload", - "/v4/object/deletedeploymentpayload": "/en/graphql/reference/objects#deletedeploymentpayload", - "/en/v4/object/deletedeploymentpayload": "/en/graphql/reference/objects#deletedeploymentpayload", - "/v4/object/deleteipallowlistentrypayload": "/en/graphql/reference/objects#deleteipallowlistentrypayload", - "/en/v4/object/deleteipallowlistentrypayload": "/en/graphql/reference/objects#deleteipallowlistentrypayload", - "/v4/object/deleteissuecommentpayload": "/en/graphql/reference/objects#deleteissuecommentpayload", - "/en/v4/object/deleteissuecommentpayload": "/en/graphql/reference/objects#deleteissuecommentpayload", - "/v4/object/deleteissuepayload": "/en/graphql/reference/objects#deleteissuepayload", - "/en/v4/object/deleteissuepayload": "/en/graphql/reference/objects#deleteissuepayload", - "/v4/object/deletelabelpayload": "/en/graphql/reference/objects#deletelabelpayload", - "/en/v4/object/deletelabelpayload": "/en/graphql/reference/objects#deletelabelpayload", - "/v4/object/deletepackageversionpayload": "/en/graphql/reference/objects#deletepackageversionpayload", - "/en/v4/object/deletepackageversionpayload": "/en/graphql/reference/objects#deletepackageversionpayload", - "/v4/object/deleteprojectcardpayload": "/en/graphql/reference/objects#deleteprojectcardpayload", - "/en/v4/object/deleteprojectcardpayload": "/en/graphql/reference/objects#deleteprojectcardpayload", - "/v4/object/deleteprojectcolumnpayload": "/en/graphql/reference/objects#deleteprojectcolumnpayload", - "/en/v4/object/deleteprojectcolumnpayload": "/en/graphql/reference/objects#deleteprojectcolumnpayload", - "/v4/object/deleteprojectpayload": "/en/graphql/reference/objects#deleteprojectpayload", - "/en/v4/object/deleteprojectpayload": "/en/graphql/reference/objects#deleteprojectpayload", - "/v4/object/deletepullrequestreviewcommentpayload": "/en/graphql/reference/objects#deletepullrequestreviewcommentpayload", - "/en/v4/object/deletepullrequestreviewcommentpayload": "/en/graphql/reference/objects#deletepullrequestreviewcommentpayload", - "/v4/object/deletepullrequestreviewpayload": "/en/graphql/reference/objects#deletepullrequestreviewpayload", - "/en/v4/object/deletepullrequestreviewpayload": "/en/graphql/reference/objects#deletepullrequestreviewpayload", - "/v4/object/deleterefpayload": "/en/graphql/reference/objects#deleterefpayload", - "/en/v4/object/deleterefpayload": "/en/graphql/reference/objects#deleterefpayload", - "/v4/object/deleteteamdiscussioncommentpayload": "/en/graphql/reference/objects#deleteteamdiscussioncommentpayload", - "/en/v4/object/deleteteamdiscussioncommentpayload": "/en/graphql/reference/objects#deleteteamdiscussioncommentpayload", - "/v4/object/deleteteamdiscussionpayload": "/en/graphql/reference/objects#deleteteamdiscussionpayload", - "/en/v4/object/deleteteamdiscussionpayload": "/en/graphql/reference/objects#deleteteamdiscussionpayload", - "/v4/object/demilestonedevent": "/en/graphql/reference/objects#demilestonedevent", - "/en/v4/object/demilestonedevent": "/en/graphql/reference/objects#demilestonedevent", - "/v4/object/dependencygraphdependency": "/en/graphql/reference/objects#dependencygraphdependency", - "/en/v4/object/dependencygraphdependency": "/en/graphql/reference/objects#dependencygraphdependency", - "/v4/object/dependencygraphdependencyconnection": "/en/graphql/reference/objects#dependencygraphdependencyconnection", - "/en/v4/object/dependencygraphdependencyconnection": "/en/graphql/reference/objects#dependencygraphdependencyconnection", - "/v4/object/dependencygraphdependencyedge": "/en/graphql/reference/objects#dependencygraphdependencyedge", - "/en/v4/object/dependencygraphdependencyedge": "/en/graphql/reference/objects#dependencygraphdependencyedge", - "/v4/object/dependencygraphmanifest": "/en/graphql/reference/objects#dependencygraphmanifest", - "/en/v4/object/dependencygraphmanifest": "/en/graphql/reference/objects#dependencygraphmanifest", - "/v4/object/dependencygraphmanifestconnection": "/en/graphql/reference/objects#dependencygraphmanifestconnection", - "/en/v4/object/dependencygraphmanifestconnection": "/en/graphql/reference/objects#dependencygraphmanifestconnection", - "/v4/object/dependencygraphmanifestedge": "/en/graphql/reference/objects#dependencygraphmanifestedge", - "/en/v4/object/dependencygraphmanifestedge": "/en/graphql/reference/objects#dependencygraphmanifestedge", - "/v4/object/deployedevent": "/en/graphql/reference/objects#deployedevent", - "/en/v4/object/deployedevent": "/en/graphql/reference/objects#deployedevent", - "/v4/object/deploykey": "/en/graphql/reference/objects#deploykey", - "/en/v4/object/deploykey": "/en/graphql/reference/objects#deploykey", - "/v4/object/deploykeyconnection": "/en/graphql/reference/objects#deploykeyconnection", - "/en/v4/object/deploykeyconnection": "/en/graphql/reference/objects#deploykeyconnection", - "/v4/object/deploykeyedge": "/en/graphql/reference/objects#deploykeyedge", - "/en/v4/object/deploykeyedge": "/en/graphql/reference/objects#deploykeyedge", - "/v4/object/deployment": "/en/graphql/reference/objects#deployment", - "/en/v4/object/deployment": "/en/graphql/reference/objects#deployment", - "/v4/object/deploymentconnection": "/en/graphql/reference/objects#deploymentconnection", - "/en/v4/object/deploymentconnection": "/en/graphql/reference/objects#deploymentconnection", - "/v4/object/deploymentedge": "/en/graphql/reference/objects#deploymentedge", - "/en/v4/object/deploymentedge": "/en/graphql/reference/objects#deploymentedge", - "/v4/object/deploymentenvironmentchangedevent": "/en/graphql/reference/objects#deploymentenvironmentchangedevent", - "/en/v4/object/deploymentenvironmentchangedevent": "/en/graphql/reference/objects#deploymentenvironmentchangedevent", - "/v4/object/deploymentstatus": "/en/graphql/reference/objects#deploymentstatus", - "/en/v4/object/deploymentstatus": "/en/graphql/reference/objects#deploymentstatus", - "/v4/object/deploymentstatusconnection": "/en/graphql/reference/objects#deploymentstatusconnection", - "/en/v4/object/deploymentstatusconnection": "/en/graphql/reference/objects#deploymentstatusconnection", - "/v4/object/deploymentstatusedge": "/en/graphql/reference/objects#deploymentstatusedge", - "/en/v4/object/deploymentstatusedge": "/en/graphql/reference/objects#deploymentstatusedge", - "/v4/object/disconnectedevent": "/en/graphql/reference/objects#disconnectedevent", - "/en/v4/object/disconnectedevent": "/en/graphql/reference/objects#disconnectedevent", - "/v4/object/dismisspullrequestreviewpayload": "/en/graphql/reference/objects#dismisspullrequestreviewpayload", - "/en/v4/object/dismisspullrequestreviewpayload": "/en/graphql/reference/objects#dismisspullrequestreviewpayload", - "/v4/object/enterprise": "/en/graphql/reference/objects#enterprise", - "/en/v4/object/enterprise": "/en/graphql/reference/objects#enterprise", - "/v4/object/enterpriseadministratorconnection": "/en/graphql/reference/objects#enterpriseadministratorconnection", - "/en/v4/object/enterpriseadministratorconnection": "/en/graphql/reference/objects#enterpriseadministratorconnection", - "/v4/object/enterpriseadministratoredge": "/en/graphql/reference/objects#enterpriseadministratoredge", - "/en/v4/object/enterpriseadministratoredge": "/en/graphql/reference/objects#enterpriseadministratoredge", - "/v4/object/enterpriseadministratorinvitation": "/en/graphql/reference/objects#enterpriseadministratorinvitation", - "/en/v4/object/enterpriseadministratorinvitation": "/en/graphql/reference/objects#enterpriseadministratorinvitation", - "/v4/object/enterpriseadministratorinvitationconnection": "/en/graphql/reference/objects#enterpriseadministratorinvitationconnection", - "/en/v4/object/enterpriseadministratorinvitationconnection": "/en/graphql/reference/objects#enterpriseadministratorinvitationconnection", - "/v4/object/enterpriseadministratorinvitationedge": "/en/graphql/reference/objects#enterpriseadministratorinvitationedge", - "/en/v4/object/enterpriseadministratorinvitationedge": "/en/graphql/reference/objects#enterpriseadministratorinvitationedge", - "/v4/object/enterprisebillinginfo": "/en/graphql/reference/objects#enterprisebillinginfo", - "/en/v4/object/enterprisebillinginfo": "/en/graphql/reference/objects#enterprisebillinginfo", - "/v4/object/enterpriseidentityprovider": "/en/graphql/reference/objects#enterpriseidentityprovider", - "/en/v4/object/enterpriseidentityprovider": "/en/graphql/reference/objects#enterpriseidentityprovider", - "/v4/object/enterprisememberconnection": "/en/graphql/reference/objects#enterprisememberconnection", - "/en/v4/object/enterprisememberconnection": "/en/graphql/reference/objects#enterprisememberconnection", - "/v4/object/enterprisememberedge": "/en/graphql/reference/objects#enterprisememberedge", - "/en/v4/object/enterprisememberedge": "/en/graphql/reference/objects#enterprisememberedge", - "/v4/object/enterpriseorganizationmembershipconnection": "/en/graphql/reference/objects#enterpriseorganizationmembershipconnection", - "/en/v4/object/enterpriseorganizationmembershipconnection": "/en/graphql/reference/objects#enterpriseorganizationmembershipconnection", - "/v4/object/enterpriseorganizationmembershipedge": "/en/graphql/reference/objects#enterpriseorganizationmembershipedge", - "/en/v4/object/enterpriseorganizationmembershipedge": "/en/graphql/reference/objects#enterpriseorganizationmembershipedge", - "/v4/object/enterpriseoutsidecollaboratorconnection": "/en/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", - "/en/v4/object/enterpriseoutsidecollaboratorconnection": "/en/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", - "/v4/object/enterpriseoutsidecollaboratoredge": "/en/graphql/reference/objects#enterpriseoutsidecollaboratoredge", - "/en/v4/object/enterpriseoutsidecollaboratoredge": "/en/graphql/reference/objects#enterpriseoutsidecollaboratoredge", - "/v4/object/enterpriseownerinfo": "/en/graphql/reference/objects#enterpriseownerinfo", - "/en/v4/object/enterpriseownerinfo": "/en/graphql/reference/objects#enterpriseownerinfo", - "/v4/object/enterprisependingcollaboratorconnection": "/en/graphql/reference/objects#enterprisependingcollaboratorconnection", - "/en/v4/object/enterprisependingcollaboratorconnection": "/en/graphql/reference/objects#enterprisependingcollaboratorconnection", - "/v4/object/enterprisependingcollaboratoredge": "/en/graphql/reference/objects#enterprisependingcollaboratoredge", - "/en/v4/object/enterprisependingcollaboratoredge": "/en/graphql/reference/objects#enterprisependingcollaboratoredge", - "/v4/object/enterprisependingmemberinvitationconnection": "/en/graphql/reference/objects#enterprisependingmemberinvitationconnection", - "/en/v4/object/enterprisependingmemberinvitationconnection": "/en/graphql/reference/objects#enterprisependingmemberinvitationconnection", - "/v4/object/enterprisependingmemberinvitationedge": "/en/graphql/reference/objects#enterprisependingmemberinvitationedge", - "/en/v4/object/enterprisependingmemberinvitationedge": "/en/graphql/reference/objects#enterprisependingmemberinvitationedge", - "/v4/object/enterpriserepositoryinfo": "/en/graphql/reference/objects#enterpriserepositoryinfo", - "/en/v4/object/enterpriserepositoryinfo": "/en/graphql/reference/objects#enterpriserepositoryinfo", - "/v4/object/enterpriserepositoryinfoconnection": "/en/graphql/reference/objects#enterpriserepositoryinfoconnection", - "/en/v4/object/enterpriserepositoryinfoconnection": "/en/graphql/reference/objects#enterpriserepositoryinfoconnection", - "/v4/object/enterpriserepositoryinfoedge": "/en/graphql/reference/objects#enterpriserepositoryinfoedge", - "/en/v4/object/enterpriserepositoryinfoedge": "/en/graphql/reference/objects#enterpriserepositoryinfoedge", - "/v4/object/enterpriseserverinstallation": "/en/graphql/reference/objects#enterpriseserverinstallation", - "/en/v4/object/enterpriseserverinstallation": "/en/graphql/reference/objects#enterpriseserverinstallation", - "/v4/object/enterpriseserverinstallationconnection": "/en/graphql/reference/objects#enterpriseserverinstallationconnection", - "/en/v4/object/enterpriseserverinstallationconnection": "/en/graphql/reference/objects#enterpriseserverinstallationconnection", - "/v4/object/enterpriseserverinstallationedge": "/en/graphql/reference/objects#enterpriseserverinstallationedge", - "/en/v4/object/enterpriseserverinstallationedge": "/en/graphql/reference/objects#enterpriseserverinstallationedge", - "/v4/object/enterpriseserveruseraccount": "/en/graphql/reference/objects#enterpriseserveruseraccount", - "/en/v4/object/enterpriseserveruseraccount": "/en/graphql/reference/objects#enterpriseserveruseraccount", - "/v4/object/enterpriseserveruseraccountconnection": "/en/graphql/reference/objects#enterpriseserveruseraccountconnection", - "/en/v4/object/enterpriseserveruseraccountconnection": "/en/graphql/reference/objects#enterpriseserveruseraccountconnection", - "/v4/object/enterpriseserveruseraccountedge": "/en/graphql/reference/objects#enterpriseserveruseraccountedge", - "/en/v4/object/enterpriseserveruseraccountedge": "/en/graphql/reference/objects#enterpriseserveruseraccountedge", - "/v4/object/enterpriseserveruseraccountemail": "/en/graphql/reference/objects#enterpriseserveruseraccountemail", - "/en/v4/object/enterpriseserveruseraccountemail": "/en/graphql/reference/objects#enterpriseserveruseraccountemail", - "/v4/object/enterpriseserveruseraccountemailconnection": "/en/graphql/reference/objects#enterpriseserveruseraccountemailconnection", - "/en/v4/object/enterpriseserveruseraccountemailconnection": "/en/graphql/reference/objects#enterpriseserveruseraccountemailconnection", - "/v4/object/enterpriseserveruseraccountemailedge": "/en/graphql/reference/objects#enterpriseserveruseraccountemailedge", - "/en/v4/object/enterpriseserveruseraccountemailedge": "/en/graphql/reference/objects#enterpriseserveruseraccountemailedge", - "/v4/object/enterpriseserveruseraccountsupload": "/en/graphql/reference/objects#enterpriseserveruseraccountsupload", - "/en/v4/object/enterpriseserveruseraccountsupload": "/en/graphql/reference/objects#enterpriseserveruseraccountsupload", - "/v4/object/enterpriseserveruseraccountsuploadconnection": "/en/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", - "/en/v4/object/enterpriseserveruseraccountsuploadconnection": "/en/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", - "/v4/object/enterpriseserveruseraccountsuploadedge": "/en/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", - "/en/v4/object/enterpriseserveruseraccountsuploadedge": "/en/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", - "/v4/object/enterpriseuseraccount": "/en/graphql/reference/objects#enterpriseuseraccount", - "/en/v4/object/enterpriseuseraccount": "/en/graphql/reference/objects#enterpriseuseraccount", - "/v4/object/enterpriseuseraccountconnection": "/en/graphql/reference/objects#enterpriseuseraccountconnection", - "/en/v4/object/enterpriseuseraccountconnection": "/en/graphql/reference/objects#enterpriseuseraccountconnection", - "/v4/object/enterpriseuseraccountedge": "/en/graphql/reference/objects#enterpriseuseraccountedge", - "/en/v4/object/enterpriseuseraccountedge": "/en/graphql/reference/objects#enterpriseuseraccountedge", - "/v4/object/externalidentity": "/en/graphql/reference/objects#externalidentity", - "/en/v4/object/externalidentity": "/en/graphql/reference/objects#externalidentity", - "/v4/object/externalidentityconnection": "/en/graphql/reference/objects#externalidentityconnection", - "/en/v4/object/externalidentityconnection": "/en/graphql/reference/objects#externalidentityconnection", - "/v4/object/externalidentityedge": "/en/graphql/reference/objects#externalidentityedge", - "/en/v4/object/externalidentityedge": "/en/graphql/reference/objects#externalidentityedge", - "/v4/object/externalidentitysamlattributes": "/en/graphql/reference/objects#externalidentitysamlattributes", - "/en/v4/object/externalidentitysamlattributes": "/en/graphql/reference/objects#externalidentitysamlattributes", - "/v4/object/externalidentityscimattributes": "/en/graphql/reference/objects#externalidentityscimattributes", - "/en/v4/object/externalidentityscimattributes": "/en/graphql/reference/objects#externalidentityscimattributes", - "/v4/object/followerconnection": "/en/graphql/reference/objects#followerconnection", - "/en/v4/object/followerconnection": "/en/graphql/reference/objects#followerconnection", - "/v4/object/followingconnection": "/en/graphql/reference/objects#followingconnection", - "/en/v4/object/followingconnection": "/en/graphql/reference/objects#followingconnection", - "/v4/object/followuserpayload": "/en/graphql/reference/objects#followuserpayload", - "/en/v4/object/followuserpayload": "/en/graphql/reference/objects#followuserpayload", - "/v4/object/fundinglink": "/en/graphql/reference/objects#fundinglink", - "/en/v4/object/fundinglink": "/en/graphql/reference/objects#fundinglink", - "/v4/object/generichovercardcontext": "/en/graphql/reference/objects#generichovercardcontext", - "/en/v4/object/generichovercardcontext": "/en/graphql/reference/objects#generichovercardcontext", - "/v4/object/gist": "/en/graphql/reference/objects#gist", - "/en/v4/object/gist": "/en/graphql/reference/objects#gist", - "/v4/object/gistcomment": "/en/graphql/reference/objects#gistcomment", - "/en/v4/object/gistcomment": "/en/graphql/reference/objects#gistcomment", - "/v4/object/gistcommentconnection": "/en/graphql/reference/objects#gistcommentconnection", - "/en/v4/object/gistcommentconnection": "/en/graphql/reference/objects#gistcommentconnection", - "/v4/object/gistcommentedge": "/en/graphql/reference/objects#gistcommentedge", - "/en/v4/object/gistcommentedge": "/en/graphql/reference/objects#gistcommentedge", - "/v4/object/gistconnection": "/en/graphql/reference/objects#gistconnection", - "/en/v4/object/gistconnection": "/en/graphql/reference/objects#gistconnection", - "/v4/object/gistedge": "/en/graphql/reference/objects#gistedge", - "/en/v4/object/gistedge": "/en/graphql/reference/objects#gistedge", - "/v4/object/gistfile": "/en/graphql/reference/objects#gistfile", - "/en/v4/object/gistfile": "/en/graphql/reference/objects#gistfile", - "/v4/object/gitactor": "/en/graphql/reference/objects#gitactor", - "/en/v4/object/gitactor": "/en/graphql/reference/objects#gitactor", - "/v4/object/githubmetadata": "/en/graphql/reference/objects#githubmetadata", - "/en/v4/object/githubmetadata": "/en/graphql/reference/objects#githubmetadata", - "/v4/object/gpgsignature": "/en/graphql/reference/objects#gpgsignature", - "/en/v4/object/gpgsignature": "/en/graphql/reference/objects#gpgsignature", - "/v4/object/headrefdeletedevent": "/en/graphql/reference/objects#headrefdeletedevent", - "/en/v4/object/headrefdeletedevent": "/en/graphql/reference/objects#headrefdeletedevent", - "/v4/object/headrefforcepushedevent": "/en/graphql/reference/objects#headrefforcepushedevent", - "/en/v4/object/headrefforcepushedevent": "/en/graphql/reference/objects#headrefforcepushedevent", - "/v4/object/headrefrestoredevent": "/en/graphql/reference/objects#headrefrestoredevent", - "/en/v4/object/headrefrestoredevent": "/en/graphql/reference/objects#headrefrestoredevent", - "/v4/object/hovercard": "/en/graphql/reference/objects#hovercard", - "/en/v4/object/hovercard": "/en/graphql/reference/objects#hovercard", - "/v4/object/importprojectpayload": "/en/graphql/reference/objects#importprojectpayload", - "/en/v4/object/importprojectpayload": "/en/graphql/reference/objects#importprojectpayload", - "/v4/object/inviteenterpriseadminpayload": "/en/graphql/reference/objects#inviteenterpriseadminpayload", - "/en/v4/object/inviteenterpriseadminpayload": "/en/graphql/reference/objects#inviteenterpriseadminpayload", - "/v4/object/ipallowlistentry": "/en/graphql/reference/objects#ipallowlistentry", - "/en/v4/object/ipallowlistentry": "/en/graphql/reference/objects#ipallowlistentry", - "/v4/object/ipallowlistentryconnection": "/en/graphql/reference/objects#ipallowlistentryconnection", - "/en/v4/object/ipallowlistentryconnection": "/en/graphql/reference/objects#ipallowlistentryconnection", - "/v4/object/ipallowlistentryedge": "/en/graphql/reference/objects#ipallowlistentryedge", - "/en/v4/object/ipallowlistentryedge": "/en/graphql/reference/objects#ipallowlistentryedge", - "/v4/object/issue": "/en/graphql/reference/objects#issue", - "/en/v4/object/issue": "/en/graphql/reference/objects#issue", - "/v4/object/issuecomment": "/en/graphql/reference/objects#issuecomment", - "/en/v4/object/issuecomment": "/en/graphql/reference/objects#issuecomment", - "/v4/object/issuecommentconnection": "/en/graphql/reference/objects#issuecommentconnection", - "/en/v4/object/issuecommentconnection": "/en/graphql/reference/objects#issuecommentconnection", - "/v4/object/issuecommentedge": "/en/graphql/reference/objects#issuecommentedge", - "/en/v4/object/issuecommentedge": "/en/graphql/reference/objects#issuecommentedge", - "/v4/object/issueconnection": "/en/graphql/reference/objects#issueconnection", - "/en/v4/object/issueconnection": "/en/graphql/reference/objects#issueconnection", - "/v4/object/issuecontributionsbyrepository": "/en/graphql/reference/objects#issuecontributionsbyrepository", - "/en/v4/object/issuecontributionsbyrepository": "/en/graphql/reference/objects#issuecontributionsbyrepository", - "/v4/object/issueedge": "/en/graphql/reference/objects#issueedge", - "/en/v4/object/issueedge": "/en/graphql/reference/objects#issueedge", - "/v4/object/issuetimelineconnection": "/en/graphql/reference/objects#issuetimelineconnection", - "/en/v4/object/issuetimelineconnection": "/en/graphql/reference/objects#issuetimelineconnection", - "/v4/object/issuetimelineitemedge": "/en/graphql/reference/objects#issuetimelineitemedge", - "/en/v4/object/issuetimelineitemedge": "/en/graphql/reference/objects#issuetimelineitemedge", - "/v4/object/issuetimelineitemsconnection": "/en/graphql/reference/objects#issuetimelineitemsconnection", - "/en/v4/object/issuetimelineitemsconnection": "/en/graphql/reference/objects#issuetimelineitemsconnection", - "/v4/object/issuetimelineitemsedge": "/en/graphql/reference/objects#issuetimelineitemsedge", - "/en/v4/object/issuetimelineitemsedge": "/en/graphql/reference/objects#issuetimelineitemsedge", - "/v4/object/joinedgithubcontribution": "/en/graphql/reference/objects#joinedgithubcontribution", - "/en/v4/object/joinedgithubcontribution": "/en/graphql/reference/objects#joinedgithubcontribution", - "/v4/object/label": "/en/graphql/reference/objects#label", - "/en/v4/object/label": "/en/graphql/reference/objects#label", - "/v4/object/labelconnection": "/en/graphql/reference/objects#labelconnection", - "/en/v4/object/labelconnection": "/en/graphql/reference/objects#labelconnection", - "/v4/object/labeledevent": "/en/graphql/reference/objects#labeledevent", - "/en/v4/object/labeledevent": "/en/graphql/reference/objects#labeledevent", - "/v4/object/labeledge": "/en/graphql/reference/objects#labeledge", - "/en/v4/object/labeledge": "/en/graphql/reference/objects#labeledge", - "/v4/object/language": "/en/graphql/reference/objects#language", - "/en/v4/object/language": "/en/graphql/reference/objects#language", - "/v4/object/languageconnection": "/en/graphql/reference/objects#languageconnection", - "/en/v4/object/languageconnection": "/en/graphql/reference/objects#languageconnection", - "/v4/object/languageedge": "/en/graphql/reference/objects#languageedge", - "/en/v4/object/languageedge": "/en/graphql/reference/objects#languageedge", - "/v4/object/license": "/en/graphql/reference/objects#license", - "/en/v4/object/license": "/en/graphql/reference/objects#license", - "/v4/object/licenserule": "/en/graphql/reference/objects#licenserule", - "/en/v4/object/licenserule": "/en/graphql/reference/objects#licenserule", - "/v4/object/linkrepositorytoprojectpayload": "/en/graphql/reference/objects#linkrepositorytoprojectpayload", - "/en/v4/object/linkrepositorytoprojectpayload": "/en/graphql/reference/objects#linkrepositorytoprojectpayload", - "/v4/object/lockedevent": "/en/graphql/reference/objects#lockedevent", - "/en/v4/object/lockedevent": "/en/graphql/reference/objects#lockedevent", - "/v4/object/locklockablepayload": "/en/graphql/reference/objects#locklockablepayload", - "/en/v4/object/locklockablepayload": "/en/graphql/reference/objects#locklockablepayload", - "/v4/object/mannequin": "/en/graphql/reference/objects#mannequin", - "/en/v4/object/mannequin": "/en/graphql/reference/objects#mannequin", - "/v4/object/markedasduplicateevent": "/en/graphql/reference/objects#markedasduplicateevent", - "/en/v4/object/markedasduplicateevent": "/en/graphql/reference/objects#markedasduplicateevent", - "/v4/object/marketplacecategory": "/en/graphql/reference/objects#marketplacecategory", - "/en/v4/object/marketplacecategory": "/en/graphql/reference/objects#marketplacecategory", - "/v4/object/marketplacelisting": "/en/graphql/reference/objects#marketplacelisting", - "/en/v4/object/marketplacelisting": "/en/graphql/reference/objects#marketplacelisting", - "/v4/object/marketplacelistingconnection": "/en/graphql/reference/objects#marketplacelistingconnection", - "/en/v4/object/marketplacelistingconnection": "/en/graphql/reference/objects#marketplacelistingconnection", - "/v4/object/marketplacelistingedge": "/en/graphql/reference/objects#marketplacelistingedge", - "/en/v4/object/marketplacelistingedge": "/en/graphql/reference/objects#marketplacelistingedge", - "/v4/object/markpullrequestreadyforreviewpayload": "/en/graphql/reference/objects#markpullrequestreadyforreviewpayload", - "/en/v4/object/markpullrequestreadyforreviewpayload": "/en/graphql/reference/objects#markpullrequestreadyforreviewpayload", - "/v4/object/memberscandeletereposclearauditentry": "/en/graphql/reference/objects#memberscandeletereposclearauditentry", - "/en/v4/object/memberscandeletereposclearauditentry": "/en/graphql/reference/objects#memberscandeletereposclearauditentry", - "/v4/object/memberscandeletereposdisableauditentry": "/en/graphql/reference/objects#memberscandeletereposdisableauditentry", - "/en/v4/object/memberscandeletereposdisableauditentry": "/en/graphql/reference/objects#memberscandeletereposdisableauditentry", - "/v4/object/memberscandeletereposenableauditentry": "/en/graphql/reference/objects#memberscandeletereposenableauditentry", - "/en/v4/object/memberscandeletereposenableauditentry": "/en/graphql/reference/objects#memberscandeletereposenableauditentry", - "/v4/object/mentionedevent": "/en/graphql/reference/objects#mentionedevent", - "/en/v4/object/mentionedevent": "/en/graphql/reference/objects#mentionedevent", - "/v4/object/mergebranchpayload": "/en/graphql/reference/objects#mergebranchpayload", - "/en/v4/object/mergebranchpayload": "/en/graphql/reference/objects#mergebranchpayload", - "/v4/object/mergedevent": "/en/graphql/reference/objects#mergedevent", - "/en/v4/object/mergedevent": "/en/graphql/reference/objects#mergedevent", - "/v4/object/mergepullrequestpayload": "/en/graphql/reference/objects#mergepullrequestpayload", - "/en/v4/object/mergepullrequestpayload": "/en/graphql/reference/objects#mergepullrequestpayload", - "/v4/object/milestone": "/en/graphql/reference/objects#milestone", - "/en/v4/object/milestone": "/en/graphql/reference/objects#milestone", - "/v4/object/milestoneconnection": "/en/graphql/reference/objects#milestoneconnection", - "/en/v4/object/milestoneconnection": "/en/graphql/reference/objects#milestoneconnection", - "/v4/object/milestonedevent": "/en/graphql/reference/objects#milestonedevent", - "/en/v4/object/milestonedevent": "/en/graphql/reference/objects#milestonedevent", - "/v4/object/milestoneedge": "/en/graphql/reference/objects#milestoneedge", - "/en/v4/object/milestoneedge": "/en/graphql/reference/objects#milestoneedge", - "/v4/object/minimizecommentpayload": "/en/graphql/reference/objects#minimizecommentpayload", - "/en/v4/object/minimizecommentpayload": "/en/graphql/reference/objects#minimizecommentpayload", - "/v4/object/movedcolumnsinprojectevent": "/en/graphql/reference/objects#movedcolumnsinprojectevent", - "/en/v4/object/movedcolumnsinprojectevent": "/en/graphql/reference/objects#movedcolumnsinprojectevent", - "/v4/object/moveprojectcardpayload": "/en/graphql/reference/objects#moveprojectcardpayload", - "/en/v4/object/moveprojectcardpayload": "/en/graphql/reference/objects#moveprojectcardpayload", - "/v4/object/moveprojectcolumnpayload": "/en/graphql/reference/objects#moveprojectcolumnpayload", - "/en/v4/object/moveprojectcolumnpayload": "/en/graphql/reference/objects#moveprojectcolumnpayload", - "/v4/object/oauthapplicationcreateauditentry": "/en/graphql/reference/objects#oauthapplicationcreateauditentry", - "/en/v4/object/oauthapplicationcreateauditentry": "/en/graphql/reference/objects#oauthapplicationcreateauditentry", - "/v4/object/orgaddbillingmanagerauditentry": "/en/graphql/reference/objects#orgaddbillingmanagerauditentry", - "/en/v4/object/orgaddbillingmanagerauditentry": "/en/graphql/reference/objects#orgaddbillingmanagerauditentry", - "/v4/object/orgaddmemberauditentry": "/en/graphql/reference/objects#orgaddmemberauditentry", - "/en/v4/object/orgaddmemberauditentry": "/en/graphql/reference/objects#orgaddmemberauditentry", - "/v4/object/organization": "/en/graphql/reference/objects#organization", - "/en/v4/object/organization": "/en/graphql/reference/objects#organization", - "/v4/object/organizationauditentryconnection": "/en/graphql/reference/objects#organizationauditentryconnection", - "/en/v4/object/organizationauditentryconnection": "/en/graphql/reference/objects#organizationauditentryconnection", - "/v4/object/organizationauditentryedge": "/en/graphql/reference/objects#organizationauditentryedge", - "/en/v4/object/organizationauditentryedge": "/en/graphql/reference/objects#organizationauditentryedge", - "/v4/object/organizationconnection": "/en/graphql/reference/objects#organizationconnection", - "/en/v4/object/organizationconnection": "/en/graphql/reference/objects#organizationconnection", - "/v4/object/organizationedge": "/en/graphql/reference/objects#organizationedge", - "/en/v4/object/organizationedge": "/en/graphql/reference/objects#organizationedge", - "/v4/object/organizationidentityprovider": "/en/graphql/reference/objects#organizationidentityprovider", - "/en/v4/object/organizationidentityprovider": "/en/graphql/reference/objects#organizationidentityprovider", - "/v4/object/organizationinvitation": "/en/graphql/reference/objects#organizationinvitation", - "/en/v4/object/organizationinvitation": "/en/graphql/reference/objects#organizationinvitation", - "/v4/object/organizationinvitationconnection": "/en/graphql/reference/objects#organizationinvitationconnection", - "/en/v4/object/organizationinvitationconnection": "/en/graphql/reference/objects#organizationinvitationconnection", - "/v4/object/organizationinvitationedge": "/en/graphql/reference/objects#organizationinvitationedge", - "/en/v4/object/organizationinvitationedge": "/en/graphql/reference/objects#organizationinvitationedge", - "/v4/object/organizationmemberconnection": "/en/graphql/reference/objects#organizationmemberconnection", - "/en/v4/object/organizationmemberconnection": "/en/graphql/reference/objects#organizationmemberconnection", - "/v4/object/organizationmemberedge": "/en/graphql/reference/objects#organizationmemberedge", - "/en/v4/object/organizationmemberedge": "/en/graphql/reference/objects#organizationmemberedge", - "/v4/object/organizationshovercardcontext": "/en/graphql/reference/objects#organizationshovercardcontext", - "/en/v4/object/organizationshovercardcontext": "/en/graphql/reference/objects#organizationshovercardcontext", - "/v4/object/organizationteamshovercardcontext": "/en/graphql/reference/objects#organizationteamshovercardcontext", - "/en/v4/object/organizationteamshovercardcontext": "/en/graphql/reference/objects#organizationteamshovercardcontext", - "/v4/object/orgblockuserauditentry": "/en/graphql/reference/objects#orgblockuserauditentry", - "/en/v4/object/orgblockuserauditentry": "/en/graphql/reference/objects#orgblockuserauditentry", - "/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", - "/en/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", - "/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", - "/en/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", - "/v4/object/orgcreateauditentry": "/en/graphql/reference/objects#orgcreateauditentry", - "/en/v4/object/orgcreateauditentry": "/en/graphql/reference/objects#orgcreateauditentry", - "/v4/object/orgdisableoauthapprestrictionsauditentry": "/en/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", - "/en/v4/object/orgdisableoauthapprestrictionsauditentry": "/en/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", - "/v4/object/orgdisablesamlauditentry": "/en/graphql/reference/objects#orgdisablesamlauditentry", - "/en/v4/object/orgdisablesamlauditentry": "/en/graphql/reference/objects#orgdisablesamlauditentry", - "/v4/object/orgdisabletwofactorrequirementauditentry": "/en/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", - "/en/v4/object/orgdisabletwofactorrequirementauditentry": "/en/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", - "/v4/object/orgenableoauthapprestrictionsauditentry": "/en/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", - "/en/v4/object/orgenableoauthapprestrictionsauditentry": "/en/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", - "/v4/object/orgenablesamlauditentry": "/en/graphql/reference/objects#orgenablesamlauditentry", - "/en/v4/object/orgenablesamlauditentry": "/en/graphql/reference/objects#orgenablesamlauditentry", - "/v4/object/orgenabletwofactorrequirementauditentry": "/en/graphql/reference/objects#orgenabletwofactorrequirementauditentry", - "/en/v4/object/orgenabletwofactorrequirementauditentry": "/en/graphql/reference/objects#orgenabletwofactorrequirementauditentry", - "/v4/object/orginvitememberauditentry": "/en/graphql/reference/objects#orginvitememberauditentry", - "/en/v4/object/orginvitememberauditentry": "/en/graphql/reference/objects#orginvitememberauditentry", - "/v4/object/orginvitetobusinessauditentry": "/en/graphql/reference/objects#orginvitetobusinessauditentry", - "/en/v4/object/orginvitetobusinessauditentry": "/en/graphql/reference/objects#orginvitetobusinessauditentry", - "/v4/object/orgoauthappaccessapprovedauditentry": "/en/graphql/reference/objects#orgoauthappaccessapprovedauditentry", - "/en/v4/object/orgoauthappaccessapprovedauditentry": "/en/graphql/reference/objects#orgoauthappaccessapprovedauditentry", - "/v4/object/orgoauthappaccessdeniedauditentry": "/en/graphql/reference/objects#orgoauthappaccessdeniedauditentry", - "/en/v4/object/orgoauthappaccessdeniedauditentry": "/en/graphql/reference/objects#orgoauthappaccessdeniedauditentry", - "/v4/object/orgoauthappaccessrequestedauditentry": "/en/graphql/reference/objects#orgoauthappaccessrequestedauditentry", - "/en/v4/object/orgoauthappaccessrequestedauditentry": "/en/graphql/reference/objects#orgoauthappaccessrequestedauditentry", - "/v4/object/orgremovebillingmanagerauditentry": "/en/graphql/reference/objects#orgremovebillingmanagerauditentry", - "/en/v4/object/orgremovebillingmanagerauditentry": "/en/graphql/reference/objects#orgremovebillingmanagerauditentry", - "/v4/object/orgremovememberauditentry": "/en/graphql/reference/objects#orgremovememberauditentry", - "/en/v4/object/orgremovememberauditentry": "/en/graphql/reference/objects#orgremovememberauditentry", - "/v4/object/orgremoveoutsidecollaboratorauditentry": "/en/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", - "/en/v4/object/orgremoveoutsidecollaboratorauditentry": "/en/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", - "/v4/object/orgrestorememberauditentry": "/en/graphql/reference/objects#orgrestorememberauditentry", - "/en/v4/object/orgrestorememberauditentry": "/en/graphql/reference/objects#orgrestorememberauditentry", - "/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/en/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", - "/en/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/en/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", - "/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/en/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", - "/en/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/en/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", - "/v4/object/orgrestoremembermembershipteamauditentrydata": "/en/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", - "/en/v4/object/orgrestoremembermembershipteamauditentrydata": "/en/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", - "/v4/object/orgunblockuserauditentry": "/en/graphql/reference/objects#orgunblockuserauditentry", - "/en/v4/object/orgunblockuserauditentry": "/en/graphql/reference/objects#orgunblockuserauditentry", - "/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/en/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", - "/en/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/en/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", - "/v4/object/orgupdatememberauditentry": "/en/graphql/reference/objects#orgupdatememberauditentry", - "/en/v4/object/orgupdatememberauditentry": "/en/graphql/reference/objects#orgupdatememberauditentry", - "/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/en/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", - "/en/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/en/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", - "/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/en/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", - "/en/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/en/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", - "/v4/object/package": "/en/graphql/reference/objects#package", - "/en/v4/object/package": "/en/graphql/reference/objects#package", - "/v4/object/packageconnection": "/en/graphql/reference/objects#packageconnection", - "/en/v4/object/packageconnection": "/en/graphql/reference/objects#packageconnection", - "/v4/object/packageedge": "/en/graphql/reference/objects#packageedge", - "/en/v4/object/packageedge": "/en/graphql/reference/objects#packageedge", - "/v4/object/packagefile": "/en/graphql/reference/objects#packagefile", - "/en/v4/object/packagefile": "/en/graphql/reference/objects#packagefile", - "/v4/object/packagefileconnection": "/en/graphql/reference/objects#packagefileconnection", - "/en/v4/object/packagefileconnection": "/en/graphql/reference/objects#packagefileconnection", - "/v4/object/packagefileedge": "/en/graphql/reference/objects#packagefileedge", - "/en/v4/object/packagefileedge": "/en/graphql/reference/objects#packagefileedge", - "/v4/object/packagestatistics": "/en/graphql/reference/objects#packagestatistics", - "/en/v4/object/packagestatistics": "/en/graphql/reference/objects#packagestatistics", - "/v4/object/packagetag": "/en/graphql/reference/objects#packagetag", - "/en/v4/object/packagetag": "/en/graphql/reference/objects#packagetag", - "/v4/object/packageversion": "/en/graphql/reference/objects#packageversion", - "/en/v4/object/packageversion": "/en/graphql/reference/objects#packageversion", - "/v4/object/packageversionconnection": "/en/graphql/reference/objects#packageversionconnection", - "/en/v4/object/packageversionconnection": "/en/graphql/reference/objects#packageversionconnection", - "/v4/object/packageversionedge": "/en/graphql/reference/objects#packageversionedge", - "/en/v4/object/packageversionedge": "/en/graphql/reference/objects#packageversionedge", - "/v4/object/packageversionstatistics": "/en/graphql/reference/objects#packageversionstatistics", - "/en/v4/object/packageversionstatistics": "/en/graphql/reference/objects#packageversionstatistics", - "/v4/object/pageinfo": "/en/graphql/reference/objects#pageinfo", - "/en/v4/object/pageinfo": "/en/graphql/reference/objects#pageinfo", - "/v4/object/permissionsource": "/en/graphql/reference/objects#permissionsource", - "/en/v4/object/permissionsource": "/en/graphql/reference/objects#permissionsource", - "/v4/object/pinissuepayload": "/en/graphql/reference/objects#pinissuepayload", - "/en/v4/object/pinissuepayload": "/en/graphql/reference/objects#pinissuepayload", - "/v4/object/pinnableitemconnection": "/en/graphql/reference/objects#pinnableitemconnection", - "/en/v4/object/pinnableitemconnection": "/en/graphql/reference/objects#pinnableitemconnection", - "/v4/object/pinnableitemedge": "/en/graphql/reference/objects#pinnableitemedge", - "/en/v4/object/pinnableitemedge": "/en/graphql/reference/objects#pinnableitemedge", - "/v4/object/pinnedevent": "/en/graphql/reference/objects#pinnedevent", - "/en/v4/object/pinnedevent": "/en/graphql/reference/objects#pinnedevent", - "/v4/object/pinnedissue": "/en/graphql/reference/objects#pinnedissue", - "/en/v4/object/pinnedissue": "/en/graphql/reference/objects#pinnedissue", - "/v4/object/pinnedissueconnection": "/en/graphql/reference/objects#pinnedissueconnection", - "/en/v4/object/pinnedissueconnection": "/en/graphql/reference/objects#pinnedissueconnection", - "/v4/object/pinnedissueedge": "/en/graphql/reference/objects#pinnedissueedge", - "/en/v4/object/pinnedissueedge": "/en/graphql/reference/objects#pinnedissueedge", - "/v4/object/privaterepositoryforkingdisableauditentry": "/en/graphql/reference/objects#privaterepositoryforkingdisableauditentry", - "/en/v4/object/privaterepositoryforkingdisableauditentry": "/en/graphql/reference/objects#privaterepositoryforkingdisableauditentry", - "/v4/object/privaterepositoryforkingenableauditentry": "/en/graphql/reference/objects#privaterepositoryforkingenableauditentry", - "/en/v4/object/privaterepositoryforkingenableauditentry": "/en/graphql/reference/objects#privaterepositoryforkingenableauditentry", - "/v4/object/profileitemshowcase": "/en/graphql/reference/objects#profileitemshowcase", - "/en/v4/object/profileitemshowcase": "/en/graphql/reference/objects#profileitemshowcase", - "/v4/object/project": "/en/graphql/reference/objects#project", - "/en/v4/object/project": "/en/graphql/reference/objects#project", - "/v4/object/projectcard": "/en/graphql/reference/objects#projectcard", - "/en/v4/object/projectcard": "/en/graphql/reference/objects#projectcard", - "/v4/object/projectcardconnection": "/en/graphql/reference/objects#projectcardconnection", - "/en/v4/object/projectcardconnection": "/en/graphql/reference/objects#projectcardconnection", - "/v4/object/projectcardedge": "/en/graphql/reference/objects#projectcardedge", - "/en/v4/object/projectcardedge": "/en/graphql/reference/objects#projectcardedge", - "/v4/object/projectcolumn": "/en/graphql/reference/objects#projectcolumn", - "/en/v4/object/projectcolumn": "/en/graphql/reference/objects#projectcolumn", - "/v4/object/projectcolumnconnection": "/en/graphql/reference/objects#projectcolumnconnection", - "/en/v4/object/projectcolumnconnection": "/en/graphql/reference/objects#projectcolumnconnection", - "/v4/object/projectcolumnedge": "/en/graphql/reference/objects#projectcolumnedge", - "/en/v4/object/projectcolumnedge": "/en/graphql/reference/objects#projectcolumnedge", - "/v4/object/projectconnection": "/en/graphql/reference/objects#projectconnection", - "/en/v4/object/projectconnection": "/en/graphql/reference/objects#projectconnection", - "/v4/object/projectedge": "/en/graphql/reference/objects#projectedge", - "/en/v4/object/projectedge": "/en/graphql/reference/objects#projectedge", - "/v4/object/publickey": "/en/graphql/reference/objects#publickey", - "/en/v4/object/publickey": "/en/graphql/reference/objects#publickey", - "/v4/object/publickeyconnection": "/en/graphql/reference/objects#publickeyconnection", - "/en/v4/object/publickeyconnection": "/en/graphql/reference/objects#publickeyconnection", - "/v4/object/publickeyedge": "/en/graphql/reference/objects#publickeyedge", - "/en/v4/object/publickeyedge": "/en/graphql/reference/objects#publickeyedge", - "/v4/object/pullrequest": "/en/graphql/reference/objects#pullrequest", - "/en/v4/object/pullrequest": "/en/graphql/reference/objects#pullrequest", - "/v4/object/pullrequestchangedfile": "/en/graphql/reference/objects#pullrequestchangedfile", - "/en/v4/object/pullrequestchangedfile": "/en/graphql/reference/objects#pullrequestchangedfile", - "/v4/object/pullrequestchangedfileconnection": "/en/graphql/reference/objects#pullrequestchangedfileconnection", - "/en/v4/object/pullrequestchangedfileconnection": "/en/graphql/reference/objects#pullrequestchangedfileconnection", - "/v4/object/pullrequestchangedfileedge": "/en/graphql/reference/objects#pullrequestchangedfileedge", - "/en/v4/object/pullrequestchangedfileedge": "/en/graphql/reference/objects#pullrequestchangedfileedge", - "/v4/object/pullrequestcommit": "/en/graphql/reference/objects#pullrequestcommit", - "/en/v4/object/pullrequestcommit": "/en/graphql/reference/objects#pullrequestcommit", - "/v4/object/pullrequestcommitcommentthread": "/en/graphql/reference/objects#pullrequestcommitcommentthread", - "/en/v4/object/pullrequestcommitcommentthread": "/en/graphql/reference/objects#pullrequestcommitcommentthread", - "/v4/object/pullrequestcommitconnection": "/en/graphql/reference/objects#pullrequestcommitconnection", - "/en/v4/object/pullrequestcommitconnection": "/en/graphql/reference/objects#pullrequestcommitconnection", - "/v4/object/pullrequestcommitedge": "/en/graphql/reference/objects#pullrequestcommitedge", - "/en/v4/object/pullrequestcommitedge": "/en/graphql/reference/objects#pullrequestcommitedge", - "/v4/object/pullrequestconnection": "/en/graphql/reference/objects#pullrequestconnection", - "/en/v4/object/pullrequestconnection": "/en/graphql/reference/objects#pullrequestconnection", - "/v4/object/pullrequestcontributionsbyrepository": "/en/graphql/reference/objects#pullrequestcontributionsbyrepository", - "/en/v4/object/pullrequestcontributionsbyrepository": "/en/graphql/reference/objects#pullrequestcontributionsbyrepository", - "/v4/object/pullrequestedge": "/en/graphql/reference/objects#pullrequestedge", - "/en/v4/object/pullrequestedge": "/en/graphql/reference/objects#pullrequestedge", - "/v4/object/pullrequestreview": "/en/graphql/reference/objects#pullrequestreview", - "/en/v4/object/pullrequestreview": "/en/graphql/reference/objects#pullrequestreview", - "/v4/object/pullrequestreviewcomment": "/en/graphql/reference/objects#pullrequestreviewcomment", - "/en/v4/object/pullrequestreviewcomment": "/en/graphql/reference/objects#pullrequestreviewcomment", - "/v4/object/pullrequestreviewcommentconnection": "/en/graphql/reference/objects#pullrequestreviewcommentconnection", - "/en/v4/object/pullrequestreviewcommentconnection": "/en/graphql/reference/objects#pullrequestreviewcommentconnection", - "/v4/object/pullrequestreviewcommentedge": "/en/graphql/reference/objects#pullrequestreviewcommentedge", - "/en/v4/object/pullrequestreviewcommentedge": "/en/graphql/reference/objects#pullrequestreviewcommentedge", - "/v4/object/pullrequestreviewconnection": "/en/graphql/reference/objects#pullrequestreviewconnection", - "/en/v4/object/pullrequestreviewconnection": "/en/graphql/reference/objects#pullrequestreviewconnection", - "/v4/object/pullrequestreviewcontributionsbyrepository": "/en/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", - "/en/v4/object/pullrequestreviewcontributionsbyrepository": "/en/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", - "/v4/object/pullrequestreviewedge": "/en/graphql/reference/objects#pullrequestreviewedge", - "/en/v4/object/pullrequestreviewedge": "/en/graphql/reference/objects#pullrequestreviewedge", - "/v4/object/pullrequestreviewthread": "/en/graphql/reference/objects#pullrequestreviewthread", - "/en/v4/object/pullrequestreviewthread": "/en/graphql/reference/objects#pullrequestreviewthread", - "/v4/object/pullrequestreviewthreadconnection": "/en/graphql/reference/objects#pullrequestreviewthreadconnection", - "/en/v4/object/pullrequestreviewthreadconnection": "/en/graphql/reference/objects#pullrequestreviewthreadconnection", - "/v4/object/pullrequestreviewthreadedge": "/en/graphql/reference/objects#pullrequestreviewthreadedge", - "/en/v4/object/pullrequestreviewthreadedge": "/en/graphql/reference/objects#pullrequestreviewthreadedge", - "/v4/object/pullrequestrevisionmarker": "/en/graphql/reference/objects#pullrequestrevisionmarker", - "/en/v4/object/pullrequestrevisionmarker": "/en/graphql/reference/objects#pullrequestrevisionmarker", - "/v4/object/pullrequesttimelineconnection": "/en/graphql/reference/objects#pullrequesttimelineconnection", - "/en/v4/object/pullrequesttimelineconnection": "/en/graphql/reference/objects#pullrequesttimelineconnection", - "/v4/object/pullrequesttimelineitemedge": "/en/graphql/reference/objects#pullrequesttimelineitemedge", - "/en/v4/object/pullrequesttimelineitemedge": "/en/graphql/reference/objects#pullrequesttimelineitemedge", - "/v4/object/pullrequesttimelineitemsconnection": "/en/graphql/reference/objects#pullrequesttimelineitemsconnection", - "/en/v4/object/pullrequesttimelineitemsconnection": "/en/graphql/reference/objects#pullrequesttimelineitemsconnection", - "/v4/object/pullrequesttimelineitemsedge": "/en/graphql/reference/objects#pullrequesttimelineitemsedge", - "/en/v4/object/pullrequesttimelineitemsedge": "/en/graphql/reference/objects#pullrequesttimelineitemsedge", - "/v4/object/push": "/en/graphql/reference/objects#push", - "/en/v4/object/push": "/en/graphql/reference/objects#push", - "/v4/object/pushallowance": "/en/graphql/reference/objects#pushallowance", - "/en/v4/object/pushallowance": "/en/graphql/reference/objects#pushallowance", - "/v4/object/pushallowanceconnection": "/en/graphql/reference/objects#pushallowanceconnection", - "/en/v4/object/pushallowanceconnection": "/en/graphql/reference/objects#pushallowanceconnection", - "/v4/object/pushallowanceedge": "/en/graphql/reference/objects#pushallowanceedge", - "/en/v4/object/pushallowanceedge": "/en/graphql/reference/objects#pushallowanceedge", - "/v4/object/ratelimit": "/en/graphql/reference/objects#ratelimit", - "/en/v4/object/ratelimit": "/en/graphql/reference/objects#ratelimit", - "/v4/object/reactinguserconnection": "/en/graphql/reference/objects#reactinguserconnection", - "/en/v4/object/reactinguserconnection": "/en/graphql/reference/objects#reactinguserconnection", - "/v4/object/reactinguseredge": "/en/graphql/reference/objects#reactinguseredge", - "/en/v4/object/reactinguseredge": "/en/graphql/reference/objects#reactinguseredge", - "/v4/object/reaction": "/en/graphql/reference/objects#reaction", - "/en/v4/object/reaction": "/en/graphql/reference/objects#reaction", - "/v4/object/reactionconnection": "/en/graphql/reference/objects#reactionconnection", - "/en/v4/object/reactionconnection": "/en/graphql/reference/objects#reactionconnection", - "/v4/object/reactionedge": "/en/graphql/reference/objects#reactionedge", - "/en/v4/object/reactionedge": "/en/graphql/reference/objects#reactionedge", - "/v4/object/reactiongroup": "/en/graphql/reference/objects#reactiongroup", - "/en/v4/object/reactiongroup": "/en/graphql/reference/objects#reactiongroup", - "/v4/object/readyforreviewevent": "/en/graphql/reference/objects#readyforreviewevent", - "/en/v4/object/readyforreviewevent": "/en/graphql/reference/objects#readyforreviewevent", - "/v4/object/ref": "/en/graphql/reference/objects#ref", - "/en/v4/object/ref": "/en/graphql/reference/objects#ref", - "/v4/object/refconnection": "/en/graphql/reference/objects#refconnection", - "/en/v4/object/refconnection": "/en/graphql/reference/objects#refconnection", - "/v4/object/refedge": "/en/graphql/reference/objects#refedge", - "/en/v4/object/refedge": "/en/graphql/reference/objects#refedge", - "/v4/object/referencedevent": "/en/graphql/reference/objects#referencedevent", - "/en/v4/object/referencedevent": "/en/graphql/reference/objects#referencedevent", - "/v4/object/regenerateenterpriseidentityproviderrecoverycodespayload": "/en/graphql/reference/objects#regenerateenterpriseidentityproviderrecoverycodespayload", - "/en/v4/object/regenerateenterpriseidentityproviderrecoverycodespayload": "/en/graphql/reference/objects#regenerateenterpriseidentityproviderrecoverycodespayload", - "/v4/object/release": "/en/graphql/reference/objects#release", - "/en/v4/object/release": "/en/graphql/reference/objects#release", - "/v4/object/releaseasset": "/en/graphql/reference/objects#releaseasset", - "/en/v4/object/releaseasset": "/en/graphql/reference/objects#releaseasset", - "/v4/object/releaseassetconnection": "/en/graphql/reference/objects#releaseassetconnection", - "/en/v4/object/releaseassetconnection": "/en/graphql/reference/objects#releaseassetconnection", - "/v4/object/releaseassetedge": "/en/graphql/reference/objects#releaseassetedge", - "/en/v4/object/releaseassetedge": "/en/graphql/reference/objects#releaseassetedge", - "/v4/object/releaseconnection": "/en/graphql/reference/objects#releaseconnection", - "/en/v4/object/releaseconnection": "/en/graphql/reference/objects#releaseconnection", - "/v4/object/releaseedge": "/en/graphql/reference/objects#releaseedge", - "/en/v4/object/releaseedge": "/en/graphql/reference/objects#releaseedge", - "/v4/object/removeassigneesfromassignablepayload": "/en/graphql/reference/objects#removeassigneesfromassignablepayload", - "/en/v4/object/removeassigneesfromassignablepayload": "/en/graphql/reference/objects#removeassigneesfromassignablepayload", - "/v4/object/removedfromprojectevent": "/en/graphql/reference/objects#removedfromprojectevent", - "/en/v4/object/removedfromprojectevent": "/en/graphql/reference/objects#removedfromprojectevent", - "/v4/object/removeenterpriseadminpayload": "/en/graphql/reference/objects#removeenterpriseadminpayload", - "/en/v4/object/removeenterpriseadminpayload": "/en/graphql/reference/objects#removeenterpriseadminpayload", - "/v4/object/removeenterpriseidentityproviderpayload": "/en/graphql/reference/objects#removeenterpriseidentityproviderpayload", - "/en/v4/object/removeenterpriseidentityproviderpayload": "/en/graphql/reference/objects#removeenterpriseidentityproviderpayload", - "/v4/object/removeenterpriseorganizationpayload": "/en/graphql/reference/objects#removeenterpriseorganizationpayload", - "/en/v4/object/removeenterpriseorganizationpayload": "/en/graphql/reference/objects#removeenterpriseorganizationpayload", - "/v4/object/removelabelsfromlabelablepayload": "/en/graphql/reference/objects#removelabelsfromlabelablepayload", - "/en/v4/object/removelabelsfromlabelablepayload": "/en/graphql/reference/objects#removelabelsfromlabelablepayload", - "/v4/object/removeoutsidecollaboratorpayload": "/en/graphql/reference/objects#removeoutsidecollaboratorpayload", - "/en/v4/object/removeoutsidecollaboratorpayload": "/en/graphql/reference/objects#removeoutsidecollaboratorpayload", - "/v4/object/removereactionpayload": "/en/graphql/reference/objects#removereactionpayload", - "/en/v4/object/removereactionpayload": "/en/graphql/reference/objects#removereactionpayload", - "/v4/object/removestarpayload": "/en/graphql/reference/objects#removestarpayload", - "/en/v4/object/removestarpayload": "/en/graphql/reference/objects#removestarpayload", - "/v4/object/renamedtitleevent": "/en/graphql/reference/objects#renamedtitleevent", - "/en/v4/object/renamedtitleevent": "/en/graphql/reference/objects#renamedtitleevent", - "/v4/object/reopenedevent": "/en/graphql/reference/objects#reopenedevent", - "/en/v4/object/reopenedevent": "/en/graphql/reference/objects#reopenedevent", - "/v4/object/reopenissuepayload": "/en/graphql/reference/objects#reopenissuepayload", - "/en/v4/object/reopenissuepayload": "/en/graphql/reference/objects#reopenissuepayload", - "/v4/object/reopenpullrequestpayload": "/en/graphql/reference/objects#reopenpullrequestpayload", - "/en/v4/object/reopenpullrequestpayload": "/en/graphql/reference/objects#reopenpullrequestpayload", - "/v4/object/repoaccessauditentry": "/en/graphql/reference/objects#repoaccessauditentry", - "/en/v4/object/repoaccessauditentry": "/en/graphql/reference/objects#repoaccessauditentry", - "/v4/object/repoaddmemberauditentry": "/en/graphql/reference/objects#repoaddmemberauditentry", - "/en/v4/object/repoaddmemberauditentry": "/en/graphql/reference/objects#repoaddmemberauditentry", - "/v4/object/repoaddtopicauditentry": "/en/graphql/reference/objects#repoaddtopicauditentry", - "/en/v4/object/repoaddtopicauditentry": "/en/graphql/reference/objects#repoaddtopicauditentry", - "/v4/object/repoarchivedauditentry": "/en/graphql/reference/objects#repoarchivedauditentry", - "/en/v4/object/repoarchivedauditentry": "/en/graphql/reference/objects#repoarchivedauditentry", - "/v4/object/repochangemergesettingauditentry": "/en/graphql/reference/objects#repochangemergesettingauditentry", - "/en/v4/object/repochangemergesettingauditentry": "/en/graphql/reference/objects#repochangemergesettingauditentry", - "/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", - "/en/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", - "/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", - "/en/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", - "/v4/object/repoconfigdisablecontributorsonlyauditentry": "/en/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", - "/en/v4/object/repoconfigdisablecontributorsonlyauditentry": "/en/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", - "/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/en/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", - "/en/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/en/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", - "/v4/object/repoconfigenableanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", - "/en/v4/object/repoconfigenableanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", - "/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", - "/en/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/en/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", - "/v4/object/repoconfigenablecontributorsonlyauditentry": "/en/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", - "/en/v4/object/repoconfigenablecontributorsonlyauditentry": "/en/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", - "/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/en/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", - "/en/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/en/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", - "/v4/object/repoconfiglockanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", - "/en/v4/object/repoconfiglockanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", - "/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", - "/en/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/en/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", - "/v4/object/repocreateauditentry": "/en/graphql/reference/objects#repocreateauditentry", - "/en/v4/object/repocreateauditentry": "/en/graphql/reference/objects#repocreateauditentry", - "/v4/object/repodestroyauditentry": "/en/graphql/reference/objects#repodestroyauditentry", - "/en/v4/object/repodestroyauditentry": "/en/graphql/reference/objects#repodestroyauditentry", - "/v4/object/reporemovememberauditentry": "/en/graphql/reference/objects#reporemovememberauditentry", - "/en/v4/object/reporemovememberauditentry": "/en/graphql/reference/objects#reporemovememberauditentry", - "/v4/object/reporemovetopicauditentry": "/en/graphql/reference/objects#reporemovetopicauditentry", - "/en/v4/object/reporemovetopicauditentry": "/en/graphql/reference/objects#reporemovetopicauditentry", - "/v4/object/repository": "/en/graphql/reference/objects#repository", - "/en/v4/object/repository": "/en/graphql/reference/objects#repository", - "/v4/object/repositorycollaboratorconnection": "/en/graphql/reference/objects#repositorycollaboratorconnection", - "/en/v4/object/repositorycollaboratorconnection": "/en/graphql/reference/objects#repositorycollaboratorconnection", - "/v4/object/repositorycollaboratoredge": "/en/graphql/reference/objects#repositorycollaboratoredge", - "/en/v4/object/repositorycollaboratoredge": "/en/graphql/reference/objects#repositorycollaboratoredge", - "/v4/object/repositoryconnection": "/en/graphql/reference/objects#repositoryconnection", - "/en/v4/object/repositoryconnection": "/en/graphql/reference/objects#repositoryconnection", - "/v4/object/repositoryedge": "/en/graphql/reference/objects#repositoryedge", - "/en/v4/object/repositoryedge": "/en/graphql/reference/objects#repositoryedge", - "/v4/object/repositoryinvitation": "/en/graphql/reference/objects#repositoryinvitation", - "/en/v4/object/repositoryinvitation": "/en/graphql/reference/objects#repositoryinvitation", - "/v4/object/repositoryinvitationconnection": "/en/graphql/reference/objects#repositoryinvitationconnection", - "/en/v4/object/repositoryinvitationconnection": "/en/graphql/reference/objects#repositoryinvitationconnection", - "/v4/object/repositoryinvitationedge": "/en/graphql/reference/objects#repositoryinvitationedge", - "/en/v4/object/repositoryinvitationedge": "/en/graphql/reference/objects#repositoryinvitationedge", - "/v4/object/repositorytopic": "/en/graphql/reference/objects#repositorytopic", - "/en/v4/object/repositorytopic": "/en/graphql/reference/objects#repositorytopic", - "/v4/object/repositorytopicconnection": "/en/graphql/reference/objects#repositorytopicconnection", - "/en/v4/object/repositorytopicconnection": "/en/graphql/reference/objects#repositorytopicconnection", - "/v4/object/repositorytopicedge": "/en/graphql/reference/objects#repositorytopicedge", - "/en/v4/object/repositorytopicedge": "/en/graphql/reference/objects#repositorytopicedge", - "/v4/object/repositoryvisibilitychangedisableauditentry": "/en/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", - "/en/v4/object/repositoryvisibilitychangedisableauditentry": "/en/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", - "/v4/object/repositoryvisibilitychangeenableauditentry": "/en/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", - "/en/v4/object/repositoryvisibilitychangeenableauditentry": "/en/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", - "/v4/object/repositoryvulnerabilityalert": "/en/graphql/reference/objects#repositoryvulnerabilityalert", - "/en/v4/object/repositoryvulnerabilityalert": "/en/graphql/reference/objects#repositoryvulnerabilityalert", - "/v4/object/repositoryvulnerabilityalertconnection": "/en/graphql/reference/objects#repositoryvulnerabilityalertconnection", - "/en/v4/object/repositoryvulnerabilityalertconnection": "/en/graphql/reference/objects#repositoryvulnerabilityalertconnection", - "/v4/object/repositoryvulnerabilityalertedge": "/en/graphql/reference/objects#repositoryvulnerabilityalertedge", - "/en/v4/object/repositoryvulnerabilityalertedge": "/en/graphql/reference/objects#repositoryvulnerabilityalertedge", - "/v4/object/requestreviewspayload": "/en/graphql/reference/objects#requestreviewspayload", - "/en/v4/object/requestreviewspayload": "/en/graphql/reference/objects#requestreviewspayload", - "/v4/object/rerequestchecksuitepayload": "/en/graphql/reference/objects#rerequestchecksuitepayload", - "/en/v4/object/rerequestchecksuitepayload": "/en/graphql/reference/objects#rerequestchecksuitepayload", - "/v4/object/resolvereviewthreadpayload": "/en/graphql/reference/objects#resolvereviewthreadpayload", - "/en/v4/object/resolvereviewthreadpayload": "/en/graphql/reference/objects#resolvereviewthreadpayload", - "/v4/object/restrictedcontribution": "/en/graphql/reference/objects#restrictedcontribution", - "/en/v4/object/restrictedcontribution": "/en/graphql/reference/objects#restrictedcontribution", - "/v4/object/reviewdismissalallowance": "/en/graphql/reference/objects#reviewdismissalallowance", - "/en/v4/object/reviewdismissalallowance": "/en/graphql/reference/objects#reviewdismissalallowance", - "/v4/object/reviewdismissalallowanceconnection": "/en/graphql/reference/objects#reviewdismissalallowanceconnection", - "/en/v4/object/reviewdismissalallowanceconnection": "/en/graphql/reference/objects#reviewdismissalallowanceconnection", - "/v4/object/reviewdismissalallowanceedge": "/en/graphql/reference/objects#reviewdismissalallowanceedge", - "/en/v4/object/reviewdismissalallowanceedge": "/en/graphql/reference/objects#reviewdismissalallowanceedge", - "/v4/object/reviewdismissedevent": "/en/graphql/reference/objects#reviewdismissedevent", - "/en/v4/object/reviewdismissedevent": "/en/graphql/reference/objects#reviewdismissedevent", - "/v4/object/reviewrequest": "/en/graphql/reference/objects#reviewrequest", - "/en/v4/object/reviewrequest": "/en/graphql/reference/objects#reviewrequest", - "/v4/object/reviewrequestconnection": "/en/graphql/reference/objects#reviewrequestconnection", - "/en/v4/object/reviewrequestconnection": "/en/graphql/reference/objects#reviewrequestconnection", - "/v4/object/reviewrequestedevent": "/en/graphql/reference/objects#reviewrequestedevent", - "/en/v4/object/reviewrequestedevent": "/en/graphql/reference/objects#reviewrequestedevent", - "/v4/object/reviewrequestedge": "/en/graphql/reference/objects#reviewrequestedge", - "/en/v4/object/reviewrequestedge": "/en/graphql/reference/objects#reviewrequestedge", - "/v4/object/reviewrequestremovedevent": "/en/graphql/reference/objects#reviewrequestremovedevent", - "/en/v4/object/reviewrequestremovedevent": "/en/graphql/reference/objects#reviewrequestremovedevent", - "/v4/object/reviewstatushovercardcontext": "/en/graphql/reference/objects#reviewstatushovercardcontext", - "/en/v4/object/reviewstatushovercardcontext": "/en/graphql/reference/objects#reviewstatushovercardcontext", - "/v4/object/savedreply": "/en/graphql/reference/objects#savedreply", - "/en/v4/object/savedreply": "/en/graphql/reference/objects#savedreply", - "/v4/object/savedreplyconnection": "/en/graphql/reference/objects#savedreplyconnection", - "/en/v4/object/savedreplyconnection": "/en/graphql/reference/objects#savedreplyconnection", - "/v4/object/savedreplyedge": "/en/graphql/reference/objects#savedreplyedge", - "/en/v4/object/savedreplyedge": "/en/graphql/reference/objects#savedreplyedge", - "/v4/object/searchresultitemconnection": "/en/graphql/reference/objects#searchresultitemconnection", - "/en/v4/object/searchresultitemconnection": "/en/graphql/reference/objects#searchresultitemconnection", - "/v4/object/searchresultitemedge": "/en/graphql/reference/objects#searchresultitemedge", - "/en/v4/object/searchresultitemedge": "/en/graphql/reference/objects#searchresultitemedge", - "/v4/object/securityadvisory": "/en/graphql/reference/objects#securityadvisory", - "/en/v4/object/securityadvisory": "/en/graphql/reference/objects#securityadvisory", - "/v4/object/securityadvisoryconnection": "/en/graphql/reference/objects#securityadvisoryconnection", - "/en/v4/object/securityadvisoryconnection": "/en/graphql/reference/objects#securityadvisoryconnection", - "/v4/object/securityadvisoryedge": "/en/graphql/reference/objects#securityadvisoryedge", - "/en/v4/object/securityadvisoryedge": "/en/graphql/reference/objects#securityadvisoryedge", - "/v4/object/securityadvisoryidentifier": "/en/graphql/reference/objects#securityadvisoryidentifier", - "/en/v4/object/securityadvisoryidentifier": "/en/graphql/reference/objects#securityadvisoryidentifier", - "/v4/object/securityadvisorypackage": "/en/graphql/reference/objects#securityadvisorypackage", - "/en/v4/object/securityadvisorypackage": "/en/graphql/reference/objects#securityadvisorypackage", - "/v4/object/securityadvisorypackageversion": "/en/graphql/reference/objects#securityadvisorypackageversion", - "/en/v4/object/securityadvisorypackageversion": "/en/graphql/reference/objects#securityadvisorypackageversion", - "/v4/object/securityadvisoryreference": "/en/graphql/reference/objects#securityadvisoryreference", - "/en/v4/object/securityadvisoryreference": "/en/graphql/reference/objects#securityadvisoryreference", - "/v4/object/securityvulnerability": "/en/graphql/reference/objects#securityvulnerability", - "/en/v4/object/securityvulnerability": "/en/graphql/reference/objects#securityvulnerability", - "/v4/object/securityvulnerabilityconnection": "/en/graphql/reference/objects#securityvulnerabilityconnection", - "/en/v4/object/securityvulnerabilityconnection": "/en/graphql/reference/objects#securityvulnerabilityconnection", - "/v4/object/securityvulnerabilityedge": "/en/graphql/reference/objects#securityvulnerabilityedge", - "/en/v4/object/securityvulnerabilityedge": "/en/graphql/reference/objects#securityvulnerabilityedge", - "/v4/object/setenterpriseidentityproviderpayload": "/en/graphql/reference/objects#setenterpriseidentityproviderpayload", - "/en/v4/object/setenterpriseidentityproviderpayload": "/en/graphql/reference/objects#setenterpriseidentityproviderpayload", - "/v4/object/smimesignature": "/en/graphql/reference/objects#smimesignature", - "/en/v4/object/smimesignature": "/en/graphql/reference/objects#smimesignature", - "/v4/object/sponsorship": "/en/graphql/reference/objects#sponsorship", - "/en/v4/object/sponsorship": "/en/graphql/reference/objects#sponsorship", - "/v4/object/sponsorshipconnection": "/en/graphql/reference/objects#sponsorshipconnection", - "/en/v4/object/sponsorshipconnection": "/en/graphql/reference/objects#sponsorshipconnection", - "/v4/object/sponsorshipedge": "/en/graphql/reference/objects#sponsorshipedge", - "/en/v4/object/sponsorshipedge": "/en/graphql/reference/objects#sponsorshipedge", - "/v4/object/sponsorslisting": "/en/graphql/reference/objects#sponsorslisting", - "/en/v4/object/sponsorslisting": "/en/graphql/reference/objects#sponsorslisting", - "/v4/object/sponsorstier": "/en/graphql/reference/objects#sponsorstier", - "/en/v4/object/sponsorstier": "/en/graphql/reference/objects#sponsorstier", - "/v4/object/sponsorstieradmininfo": "/en/graphql/reference/objects#sponsorstieradmininfo", - "/en/v4/object/sponsorstieradmininfo": "/en/graphql/reference/objects#sponsorstieradmininfo", - "/v4/object/sponsorstierconnection": "/en/graphql/reference/objects#sponsorstierconnection", - "/en/v4/object/sponsorstierconnection": "/en/graphql/reference/objects#sponsorstierconnection", - "/v4/object/sponsorstieredge": "/en/graphql/reference/objects#sponsorstieredge", - "/en/v4/object/sponsorstieredge": "/en/graphql/reference/objects#sponsorstieredge", - "/v4/object/stargazerconnection": "/en/graphql/reference/objects#stargazerconnection", - "/en/v4/object/stargazerconnection": "/en/graphql/reference/objects#stargazerconnection", - "/v4/object/stargazeredge": "/en/graphql/reference/objects#stargazeredge", - "/en/v4/object/stargazeredge": "/en/graphql/reference/objects#stargazeredge", - "/v4/object/starredrepositoryconnection": "/en/graphql/reference/objects#starredrepositoryconnection", - "/en/v4/object/starredrepositoryconnection": "/en/graphql/reference/objects#starredrepositoryconnection", - "/v4/object/starredrepositoryedge": "/en/graphql/reference/objects#starredrepositoryedge", - "/en/v4/object/starredrepositoryedge": "/en/graphql/reference/objects#starredrepositoryedge", - "/v4/object/status": "/en/graphql/reference/objects#status", - "/en/v4/object/status": "/en/graphql/reference/objects#status", - "/v4/object/statuscheckrollup": "/en/graphql/reference/objects#statuscheckrollup", - "/en/v4/object/statuscheckrollup": "/en/graphql/reference/objects#statuscheckrollup", - "/v4/object/statuscheckrollupcontextconnection": "/en/graphql/reference/objects#statuscheckrollupcontextconnection", - "/en/v4/object/statuscheckrollupcontextconnection": "/en/graphql/reference/objects#statuscheckrollupcontextconnection", - "/v4/object/statuscheckrollupcontextedge": "/en/graphql/reference/objects#statuscheckrollupcontextedge", - "/en/v4/object/statuscheckrollupcontextedge": "/en/graphql/reference/objects#statuscheckrollupcontextedge", - "/v4/object/statuscontext": "/en/graphql/reference/objects#statuscontext", - "/en/v4/object/statuscontext": "/en/graphql/reference/objects#statuscontext", - "/v4/object/submitpullrequestreviewpayload": "/en/graphql/reference/objects#submitpullrequestreviewpayload", - "/en/v4/object/submitpullrequestreviewpayload": "/en/graphql/reference/objects#submitpullrequestreviewpayload", - "/v4/object/submodule": "/en/graphql/reference/objects#submodule", - "/en/v4/object/submodule": "/en/graphql/reference/objects#submodule", - "/v4/object/submoduleconnection": "/en/graphql/reference/objects#submoduleconnection", - "/en/v4/object/submoduleconnection": "/en/graphql/reference/objects#submoduleconnection", - "/v4/object/submoduleedge": "/en/graphql/reference/objects#submoduleedge", - "/en/v4/object/submoduleedge": "/en/graphql/reference/objects#submoduleedge", - "/v4/object/subscribedevent": "/en/graphql/reference/objects#subscribedevent", - "/en/v4/object/subscribedevent": "/en/graphql/reference/objects#subscribedevent", - "/v4/object/suggestedreviewer": "/en/graphql/reference/objects#suggestedreviewer", - "/en/v4/object/suggestedreviewer": "/en/graphql/reference/objects#suggestedreviewer", - "/v4/object/tag": "/en/graphql/reference/objects#tag", - "/en/v4/object/tag": "/en/graphql/reference/objects#tag", - "/v4/object/team": "/en/graphql/reference/objects#team", - "/en/v4/object/team": "/en/graphql/reference/objects#team", - "/v4/object/teamaddmemberauditentry": "/en/graphql/reference/objects#teamaddmemberauditentry", - "/en/v4/object/teamaddmemberauditentry": "/en/graphql/reference/objects#teamaddmemberauditentry", - "/v4/object/teamaddrepositoryauditentry": "/en/graphql/reference/objects#teamaddrepositoryauditentry", - "/en/v4/object/teamaddrepositoryauditentry": "/en/graphql/reference/objects#teamaddrepositoryauditentry", - "/v4/object/teamchangeparentteamauditentry": "/en/graphql/reference/objects#teamchangeparentteamauditentry", - "/en/v4/object/teamchangeparentteamauditentry": "/en/graphql/reference/objects#teamchangeparentteamauditentry", - "/v4/object/teamconnection": "/en/graphql/reference/objects#teamconnection", - "/en/v4/object/teamconnection": "/en/graphql/reference/objects#teamconnection", - "/v4/object/teamdiscussion": "/en/graphql/reference/objects#teamdiscussion", - "/en/v4/object/teamdiscussion": "/en/graphql/reference/objects#teamdiscussion", - "/v4/object/teamdiscussioncomment": "/en/graphql/reference/objects#teamdiscussioncomment", - "/en/v4/object/teamdiscussioncomment": "/en/graphql/reference/objects#teamdiscussioncomment", - "/v4/object/teamdiscussioncommentconnection": "/en/graphql/reference/objects#teamdiscussioncommentconnection", - "/en/v4/object/teamdiscussioncommentconnection": "/en/graphql/reference/objects#teamdiscussioncommentconnection", - "/v4/object/teamdiscussioncommentedge": "/en/graphql/reference/objects#teamdiscussioncommentedge", - "/en/v4/object/teamdiscussioncommentedge": "/en/graphql/reference/objects#teamdiscussioncommentedge", - "/v4/object/teamdiscussionconnection": "/en/graphql/reference/objects#teamdiscussionconnection", - "/en/v4/object/teamdiscussionconnection": "/en/graphql/reference/objects#teamdiscussionconnection", - "/v4/object/teamdiscussionedge": "/en/graphql/reference/objects#teamdiscussionedge", - "/en/v4/object/teamdiscussionedge": "/en/graphql/reference/objects#teamdiscussionedge", - "/v4/object/teamedge": "/en/graphql/reference/objects#teamedge", - "/en/v4/object/teamedge": "/en/graphql/reference/objects#teamedge", - "/v4/object/teammemberconnection": "/en/graphql/reference/objects#teammemberconnection", - "/en/v4/object/teammemberconnection": "/en/graphql/reference/objects#teammemberconnection", - "/v4/object/teammemberedge": "/en/graphql/reference/objects#teammemberedge", - "/en/v4/object/teammemberedge": "/en/graphql/reference/objects#teammemberedge", - "/v4/object/teamremovememberauditentry": "/en/graphql/reference/objects#teamremovememberauditentry", - "/en/v4/object/teamremovememberauditentry": "/en/graphql/reference/objects#teamremovememberauditentry", - "/v4/object/teamremoverepositoryauditentry": "/en/graphql/reference/objects#teamremoverepositoryauditentry", - "/en/v4/object/teamremoverepositoryauditentry": "/en/graphql/reference/objects#teamremoverepositoryauditentry", - "/v4/object/teamrepositoryconnection": "/en/graphql/reference/objects#teamrepositoryconnection", - "/en/v4/object/teamrepositoryconnection": "/en/graphql/reference/objects#teamrepositoryconnection", - "/v4/object/teamrepositoryedge": "/en/graphql/reference/objects#teamrepositoryedge", - "/en/v4/object/teamrepositoryedge": "/en/graphql/reference/objects#teamrepositoryedge", - "/v4/object/textmatch": "/en/graphql/reference/objects#textmatch", - "/en/v4/object/textmatch": "/en/graphql/reference/objects#textmatch", - "/v4/object/textmatchhighlight": "/en/graphql/reference/objects#textmatchhighlight", - "/en/v4/object/textmatchhighlight": "/en/graphql/reference/objects#textmatchhighlight", - "/v4/object/topic": "/en/graphql/reference/objects#topic", - "/en/v4/object/topic": "/en/graphql/reference/objects#topic", - "/v4/object/transferissuepayload": "/en/graphql/reference/objects#transferissuepayload", - "/en/v4/object/transferissuepayload": "/en/graphql/reference/objects#transferissuepayload", - "/v4/object/transferredevent": "/en/graphql/reference/objects#transferredevent", - "/en/v4/object/transferredevent": "/en/graphql/reference/objects#transferredevent", - "/v4/object/tree": "/en/graphql/reference/objects#tree", - "/en/v4/object/tree": "/en/graphql/reference/objects#tree", - "/v4/object/treeentry": "/en/graphql/reference/objects#treeentry", - "/en/v4/object/treeentry": "/en/graphql/reference/objects#treeentry", - "/v4/object/unarchiverepositorypayload": "/en/graphql/reference/objects#unarchiverepositorypayload", - "/en/v4/object/unarchiverepositorypayload": "/en/graphql/reference/objects#unarchiverepositorypayload", - "/v4/object/unassignedevent": "/en/graphql/reference/objects#unassignedevent", - "/en/v4/object/unassignedevent": "/en/graphql/reference/objects#unassignedevent", - "/v4/object/unfollowuserpayload": "/en/graphql/reference/objects#unfollowuserpayload", - "/en/v4/object/unfollowuserpayload": "/en/graphql/reference/objects#unfollowuserpayload", - "/v4/object/unknownsignature": "/en/graphql/reference/objects#unknownsignature", - "/en/v4/object/unknownsignature": "/en/graphql/reference/objects#unknownsignature", - "/v4/object/unlabeledevent": "/en/graphql/reference/objects#unlabeledevent", - "/en/v4/object/unlabeledevent": "/en/graphql/reference/objects#unlabeledevent", - "/v4/object/unlinkrepositoryfromprojectpayload": "/en/graphql/reference/objects#unlinkrepositoryfromprojectpayload", - "/en/v4/object/unlinkrepositoryfromprojectpayload": "/en/graphql/reference/objects#unlinkrepositoryfromprojectpayload", - "/v4/object/unlockedevent": "/en/graphql/reference/objects#unlockedevent", - "/en/v4/object/unlockedevent": "/en/graphql/reference/objects#unlockedevent", - "/v4/object/unlocklockablepayload": "/en/graphql/reference/objects#unlocklockablepayload", - "/en/v4/object/unlocklockablepayload": "/en/graphql/reference/objects#unlocklockablepayload", - "/v4/object/unmarkedasduplicateevent": "/en/graphql/reference/objects#unmarkedasduplicateevent", - "/en/v4/object/unmarkedasduplicateevent": "/en/graphql/reference/objects#unmarkedasduplicateevent", - "/v4/object/unmarkissueasduplicatepayload": "/en/graphql/reference/objects#unmarkissueasduplicatepayload", - "/en/v4/object/unmarkissueasduplicatepayload": "/en/graphql/reference/objects#unmarkissueasduplicatepayload", - "/v4/object/unminimizecommentpayload": "/en/graphql/reference/objects#unminimizecommentpayload", - "/en/v4/object/unminimizecommentpayload": "/en/graphql/reference/objects#unminimizecommentpayload", - "/v4/object/unpinissuepayload": "/en/graphql/reference/objects#unpinissuepayload", - "/en/v4/object/unpinissuepayload": "/en/graphql/reference/objects#unpinissuepayload", - "/v4/object/unpinnedevent": "/en/graphql/reference/objects#unpinnedevent", - "/en/v4/object/unpinnedevent": "/en/graphql/reference/objects#unpinnedevent", - "/v4/object/unresolvereviewthreadpayload": "/en/graphql/reference/objects#unresolvereviewthreadpayload", - "/en/v4/object/unresolvereviewthreadpayload": "/en/graphql/reference/objects#unresolvereviewthreadpayload", - "/v4/object/unsubscribedevent": "/en/graphql/reference/objects#unsubscribedevent", - "/en/v4/object/unsubscribedevent": "/en/graphql/reference/objects#unsubscribedevent", - "/v4/object/updatebranchprotectionrulepayload": "/en/graphql/reference/objects#updatebranchprotectionrulepayload", - "/en/v4/object/updatebranchprotectionrulepayload": "/en/graphql/reference/objects#updatebranchprotectionrulepayload", - "/v4/object/updatecheckrunpayload": "/en/graphql/reference/objects#updatecheckrunpayload", - "/en/v4/object/updatecheckrunpayload": "/en/graphql/reference/objects#updatecheckrunpayload", - "/v4/object/updatechecksuitepreferencespayload": "/en/graphql/reference/objects#updatechecksuitepreferencespayload", - "/en/v4/object/updatechecksuitepreferencespayload": "/en/graphql/reference/objects#updatechecksuitepreferencespayload", - "/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/en/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", - "/en/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/en/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", - "/v4/object/updateenterpriseadministratorrolepayload": "/en/graphql/reference/objects#updateenterpriseadministratorrolepayload", - "/en/v4/object/updateenterpriseadministratorrolepayload": "/en/graphql/reference/objects#updateenterpriseadministratorrolepayload", - "/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/en/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", - "/en/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/en/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", - "/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/en/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", - "/en/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/en/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", - "/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", - "/en/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", - "/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", - "/en/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", - "/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", - "/en/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", - "/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", - "/en/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", - "/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/en/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", - "/en/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/en/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", - "/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", - "/en/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", - "/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", - "/en/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", - "/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", - "/en/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/en/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", - "/v4/object/updateenterpriseorganizationprojectssettingpayload": "/en/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", - "/en/v4/object/updateenterpriseorganizationprojectssettingpayload": "/en/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", - "/v4/object/updateenterpriseprofilepayload": "/en/graphql/reference/objects#updateenterpriseprofilepayload", - "/en/v4/object/updateenterpriseprofilepayload": "/en/graphql/reference/objects#updateenterpriseprofilepayload", - "/v4/object/updateenterpriserepositoryprojectssettingpayload": "/en/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", - "/en/v4/object/updateenterpriserepositoryprojectssettingpayload": "/en/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", - "/v4/object/updateenterpriseteamdiscussionssettingpayload": "/en/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", - "/en/v4/object/updateenterpriseteamdiscussionssettingpayload": "/en/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", - "/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/en/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", - "/en/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/en/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", - "/v4/object/updateipallowlistenabledsettingpayload": "/en/graphql/reference/objects#updateipallowlistenabledsettingpayload", - "/en/v4/object/updateipallowlistenabledsettingpayload": "/en/graphql/reference/objects#updateipallowlistenabledsettingpayload", - "/v4/object/updateipallowlistentrypayload": "/en/graphql/reference/objects#updateipallowlistentrypayload", - "/en/v4/object/updateipallowlistentrypayload": "/en/graphql/reference/objects#updateipallowlistentrypayload", - "/v4/object/updateissuecommentpayload": "/en/graphql/reference/objects#updateissuecommentpayload", - "/en/v4/object/updateissuecommentpayload": "/en/graphql/reference/objects#updateissuecommentpayload", - "/v4/object/updateissuepayload": "/en/graphql/reference/objects#updateissuepayload", - "/en/v4/object/updateissuepayload": "/en/graphql/reference/objects#updateissuepayload", - "/v4/object/updatelabelpayload": "/en/graphql/reference/objects#updatelabelpayload", - "/en/v4/object/updatelabelpayload": "/en/graphql/reference/objects#updatelabelpayload", - "/v4/object/updateprojectcardpayload": "/en/graphql/reference/objects#updateprojectcardpayload", - "/en/v4/object/updateprojectcardpayload": "/en/graphql/reference/objects#updateprojectcardpayload", - "/v4/object/updateprojectcolumnpayload": "/en/graphql/reference/objects#updateprojectcolumnpayload", - "/en/v4/object/updateprojectcolumnpayload": "/en/graphql/reference/objects#updateprojectcolumnpayload", - "/v4/object/updateprojectpayload": "/en/graphql/reference/objects#updateprojectpayload", - "/en/v4/object/updateprojectpayload": "/en/graphql/reference/objects#updateprojectpayload", - "/v4/object/updatepullrequestpayload": "/en/graphql/reference/objects#updatepullrequestpayload", - "/en/v4/object/updatepullrequestpayload": "/en/graphql/reference/objects#updatepullrequestpayload", - "/v4/object/updatepullrequestreviewcommentpayload": "/en/graphql/reference/objects#updatepullrequestreviewcommentpayload", - "/en/v4/object/updatepullrequestreviewcommentpayload": "/en/graphql/reference/objects#updatepullrequestreviewcommentpayload", - "/v4/object/updatepullrequestreviewpayload": "/en/graphql/reference/objects#updatepullrequestreviewpayload", - "/en/v4/object/updatepullrequestreviewpayload": "/en/graphql/reference/objects#updatepullrequestreviewpayload", - "/v4/object/updaterefpayload": "/en/graphql/reference/objects#updaterefpayload", - "/en/v4/object/updaterefpayload": "/en/graphql/reference/objects#updaterefpayload", - "/v4/object/updaterefspayload": "/en/graphql/reference/objects#updaterefspayload", - "/en/v4/object/updaterefspayload": "/en/graphql/reference/objects#updaterefspayload", - "/v4/object/updaterepositorypayload": "/en/graphql/reference/objects#updaterepositorypayload", - "/en/v4/object/updaterepositorypayload": "/en/graphql/reference/objects#updaterepositorypayload", - "/v4/object/updatesubscriptionpayload": "/en/graphql/reference/objects#updatesubscriptionpayload", - "/en/v4/object/updatesubscriptionpayload": "/en/graphql/reference/objects#updatesubscriptionpayload", - "/v4/object/updateteamdiscussioncommentpayload": "/en/graphql/reference/objects#updateteamdiscussioncommentpayload", - "/en/v4/object/updateteamdiscussioncommentpayload": "/en/graphql/reference/objects#updateteamdiscussioncommentpayload", - "/v4/object/updateteamdiscussionpayload": "/en/graphql/reference/objects#updateteamdiscussionpayload", - "/en/v4/object/updateteamdiscussionpayload": "/en/graphql/reference/objects#updateteamdiscussionpayload", - "/v4/object/updateteamreviewassignmentpayload": "/en/graphql/reference/objects#updateteamreviewassignmentpayload", - "/en/v4/object/updateteamreviewassignmentpayload": "/en/graphql/reference/objects#updateteamreviewassignmentpayload", - "/v4/object/updatetopicspayload": "/en/graphql/reference/objects#updatetopicspayload", - "/en/v4/object/updatetopicspayload": "/en/graphql/reference/objects#updatetopicspayload", - "/v4/object/user": "/en/graphql/reference/objects#user", - "/en/v4/object/user": "/en/graphql/reference/objects#user", - "/v4/object/userblockedevent": "/en/graphql/reference/objects#userblockedevent", - "/en/v4/object/userblockedevent": "/en/graphql/reference/objects#userblockedevent", - "/v4/object/userconnection": "/en/graphql/reference/objects#userconnection", - "/en/v4/object/userconnection": "/en/graphql/reference/objects#userconnection", - "/v4/object/usercontentedit": "/en/graphql/reference/objects#usercontentedit", - "/en/v4/object/usercontentedit": "/en/graphql/reference/objects#usercontentedit", - "/v4/object/usercontenteditconnection": "/en/graphql/reference/objects#usercontenteditconnection", - "/en/v4/object/usercontenteditconnection": "/en/graphql/reference/objects#usercontenteditconnection", - "/v4/object/usercontenteditedge": "/en/graphql/reference/objects#usercontenteditedge", - "/en/v4/object/usercontenteditedge": "/en/graphql/reference/objects#usercontenteditedge", - "/v4/object/useredge": "/en/graphql/reference/objects#useredge", - "/en/v4/object/useredge": "/en/graphql/reference/objects#useredge", - "/v4/object/userstatus": "/en/graphql/reference/objects#userstatus", - "/en/v4/object/userstatus": "/en/graphql/reference/objects#userstatus", - "/v4/object/userstatusconnection": "/en/graphql/reference/objects#userstatusconnection", - "/en/v4/object/userstatusconnection": "/en/graphql/reference/objects#userstatusconnection", - "/v4/object/userstatusedge": "/en/graphql/reference/objects#userstatusedge", - "/en/v4/object/userstatusedge": "/en/graphql/reference/objects#userstatusedge", - "/v4/object/viewerhovercardcontext": "/en/graphql/reference/objects#viewerhovercardcontext", - "/en/v4/object/viewerhovercardcontext": "/en/graphql/reference/objects#viewerhovercardcontext", - "/v4/scalar/boolean": "/en/graphql/reference/scalars#boolean", - "/en/v4/scalar/boolean": "/en/graphql/reference/scalars#boolean", - "/v4/scalar/date": "/en/graphql/reference/scalars#date", - "/en/v4/scalar/date": "/en/graphql/reference/scalars#date", - "/v4/scalar/datetime": "/en/graphql/reference/scalars#datetime", - "/en/v4/scalar/datetime": "/en/graphql/reference/scalars#datetime", - "/v4/scalar/float": "/en/graphql/reference/scalars#float", - "/en/v4/scalar/float": "/en/graphql/reference/scalars#float", - "/v4/scalar/gitobjectid": "/en/graphql/reference/scalars#gitobjectid", - "/en/v4/scalar/gitobjectid": "/en/graphql/reference/scalars#gitobjectid", - "/v4/scalar/gitrefname": "/en/graphql/reference/scalars#gitrefname", - "/en/v4/scalar/gitrefname": "/en/graphql/reference/scalars#gitrefname", - "/v4/scalar/gitsshremote": "/en/graphql/reference/scalars#gitsshremote", - "/en/v4/scalar/gitsshremote": "/en/graphql/reference/scalars#gitsshremote", - "/v4/scalar/gittimestamp": "/en/graphql/reference/scalars#gittimestamp", - "/en/v4/scalar/gittimestamp": "/en/graphql/reference/scalars#gittimestamp", - "/v4/scalar/html": "/en/graphql/reference/scalars#html", - "/en/v4/scalar/html": "/en/graphql/reference/scalars#html", - "/v4/scalar/id": "/en/graphql/reference/scalars#id", - "/en/v4/scalar/id": "/en/graphql/reference/scalars#id", - "/v4/scalar/int": "/en/graphql/reference/scalars#int", - "/en/v4/scalar/int": "/en/graphql/reference/scalars#int", - "/v4/scalar/precisedatetime": "/en/graphql/reference/scalars#precisedatetime", - "/en/v4/scalar/precisedatetime": "/en/graphql/reference/scalars#precisedatetime", - "/v4/scalar/string": "/en/graphql/reference/scalars#string", - "/en/v4/scalar/string": "/en/graphql/reference/scalars#string", - "/v4/scalar/uri": "/en/graphql/reference/scalars#uri", - "/en/v4/scalar/uri": "/en/graphql/reference/scalars#uri", - "/v4/scalar/x509certificate": "/en/graphql/reference/scalars#x509certificate", - "/en/v4/scalar/x509certificate": "/en/graphql/reference/scalars#x509certificate", - "/v4/union/assignee": "/en/graphql/reference/unions#assignee", - "/en/v4/union/assignee": "/en/graphql/reference/unions#assignee", - "/v4/union/auditentryactor": "/en/graphql/reference/unions#auditentryactor", - "/en/v4/union/auditentryactor": "/en/graphql/reference/unions#auditentryactor", - "/v4/union/closer": "/en/graphql/reference/unions#closer", - "/en/v4/union/closer": "/en/graphql/reference/unions#closer", - "/v4/union/createdissueorrestrictedcontribution": "/en/graphql/reference/unions#createdissueorrestrictedcontribution", - "/en/v4/union/createdissueorrestrictedcontribution": "/en/graphql/reference/unions#createdissueorrestrictedcontribution", - "/v4/union/createdpullrequestorrestrictedcontribution": "/en/graphql/reference/unions#createdpullrequestorrestrictedcontribution", - "/en/v4/union/createdpullrequestorrestrictedcontribution": "/en/graphql/reference/unions#createdpullrequestorrestrictedcontribution", - "/v4/union/createdrepositoryorrestrictedcontribution": "/en/graphql/reference/unions#createdrepositoryorrestrictedcontribution", - "/en/v4/union/createdrepositoryorrestrictedcontribution": "/en/graphql/reference/unions#createdrepositoryorrestrictedcontribution", - "/v4/union/enterprisemember": "/en/graphql/reference/unions#enterprisemember", - "/en/v4/union/enterprisemember": "/en/graphql/reference/unions#enterprisemember", - "/v4/union/ipallowlistowner": "/en/graphql/reference/unions#ipallowlistowner", - "/en/v4/union/ipallowlistowner": "/en/graphql/reference/unions#ipallowlistowner", - "/v4/union/issueorpullrequest": "/en/graphql/reference/unions#issueorpullrequest", - "/en/v4/union/issueorpullrequest": "/en/graphql/reference/unions#issueorpullrequest", - "/v4/union/issuetimelineitem": "/en/graphql/reference/unions#issuetimelineitem", - "/en/v4/union/issuetimelineitem": "/en/graphql/reference/unions#issuetimelineitem", - "/v4/union/issuetimelineitems": "/en/graphql/reference/unions#issuetimelineitems", - "/en/v4/union/issuetimelineitems": "/en/graphql/reference/unions#issuetimelineitems", - "/v4/union/milestoneitem": "/en/graphql/reference/unions#milestoneitem", - "/en/v4/union/milestoneitem": "/en/graphql/reference/unions#milestoneitem", - "/v4/union/organizationauditentry": "/en/graphql/reference/unions#organizationauditentry", - "/en/v4/union/organizationauditentry": "/en/graphql/reference/unions#organizationauditentry", - "/v4/union/orgrestorememberauditentrymembership": "/en/graphql/reference/unions#orgrestorememberauditentrymembership", - "/en/v4/union/orgrestorememberauditentrymembership": "/en/graphql/reference/unions#orgrestorememberauditentrymembership", - "/v4/union/permissiongranter": "/en/graphql/reference/unions#permissiongranter", - "/en/v4/union/permissiongranter": "/en/graphql/reference/unions#permissiongranter", - "/v4/union/pinnableitem": "/en/graphql/reference/unions#pinnableitem", - "/en/v4/union/pinnableitem": "/en/graphql/reference/unions#pinnableitem", - "/v4/union/projectcarditem": "/en/graphql/reference/unions#projectcarditem", - "/en/v4/union/projectcarditem": "/en/graphql/reference/unions#projectcarditem", - "/v4/union/pullrequesttimelineitem": "/en/graphql/reference/unions#pullrequesttimelineitem", - "/en/v4/union/pullrequesttimelineitem": "/en/graphql/reference/unions#pullrequesttimelineitem", - "/v4/union/pullrequesttimelineitems": "/en/graphql/reference/unions#pullrequesttimelineitems", - "/en/v4/union/pullrequesttimelineitems": "/en/graphql/reference/unions#pullrequesttimelineitems", - "/v4/union/pushallowanceactor": "/en/graphql/reference/unions#pushallowanceactor", - "/en/v4/union/pushallowanceactor": "/en/graphql/reference/unions#pushallowanceactor", - "/v4/union/referencedsubject": "/en/graphql/reference/unions#referencedsubject", - "/en/v4/union/referencedsubject": "/en/graphql/reference/unions#referencedsubject", - "/v4/union/renamedtitlesubject": "/en/graphql/reference/unions#renamedtitlesubject", - "/en/v4/union/renamedtitlesubject": "/en/graphql/reference/unions#renamedtitlesubject", - "/v4/union/requestedreviewer": "/en/graphql/reference/unions#requestedreviewer", - "/en/v4/union/requestedreviewer": "/en/graphql/reference/unions#requestedreviewer", - "/v4/union/reviewdismissalallowanceactor": "/en/graphql/reference/unions#reviewdismissalallowanceactor", - "/en/v4/union/reviewdismissalallowanceactor": "/en/graphql/reference/unions#reviewdismissalallowanceactor", - "/v4/union/searchresultitem": "/en/graphql/reference/unions#searchresultitem", - "/en/v4/union/searchresultitem": "/en/graphql/reference/unions#searchresultitem", - "/v4/union/sponsor": "/en/graphql/reference/unions#sponsor", - "/en/v4/union/sponsor": "/en/graphql/reference/unions#sponsor", - "/v4/union/statuscheckrollupcontext": "/en/graphql/reference/unions#statuscheckrollupcontext", - "/en/v4/union/statuscheckrollupcontext": "/en/graphql/reference/unions#statuscheckrollupcontext" + "/enterprise-server@3.0/admin/articles/restoring-github-enterprise": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/3.0/admin/articles/restoring-github-enterprise": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/admin/articles/restoring-github-enterprise": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/admin/articles/restoring-github-enterprise": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise-server@3.0/admin/articles/restoring-enterprise-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/3.0/admin/articles/restoring-enterprise-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/admin/articles/restoring-enterprise-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/admin/articles/restoring-enterprise-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise-server@3.0/admin/articles/restoring-repository-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/3.0/admin/articles/restoring-repository-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/admin/articles/restoring-repository-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/admin/articles/restoring-repository-data": "/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise-server@2.20/admin/articles/restoring-github-enterprise": "/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/2.20/admin/articles/restoring-github-enterprise": "/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise-server@2.20/admin/articles/restoring-enterprise-data": "/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/2.20/admin/articles/restoring-enterprise-data": "/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise-server@2.20/admin/articles/restoring-repository-data": "/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise/2.20/admin/articles/restoring-repository-data": "/enterprise-server@2.20/admin/configuration/configuring-backups-on-your-appliance", + "/enterprise-server@3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", + "/enterprise/3.0/admin/articles/restricting-ssh-access-to-specific-hosts": "/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", + "/admin/articles/restricting-ssh-access-to-specific-hosts": "/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", + "/enterprise/admin/articles/restricting-ssh-access-to-specific-hosts": "/enterprise-server@3.0/admin/configuration/configuring-your-enterprise", + "/enterprise-server@2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", + "/enterprise/2.20/admin/articles/restricting-ssh-access-to-specific-hosts": "/enterprise-server@2.20/admin/configuration/configuring-your-enterprise", + "/github-ae@latest/admin/articles/restricting-ssh-access-to-specific-hosts": "/github-ae@latest/admin/configuration/configuring-your-enterprise", + "/enterprise-server@3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/enterprise/3.0/admin/user-management/restricting-repository-creation-in-your-instance": "/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/admin/user-management/restricting-repository-creation-in-your-instance": "/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/enterprise/admin/user-management/restricting-repository-creation-in-your-instance": "/enterprise-server@3.0/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/enterprise-server@2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/enterprise/2.20/admin/user-management/restricting-repository-creation-in-your-instance": "/enterprise-server@2.20/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/github-ae@latest/admin/user-management/restricting-repository-creation-in-your-instance": "/github-ae@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise", + "/v3/oauth": "/developers/apps/authorizing-oauth-apps", + "/free-pro-team@latest/v3/oauth": "/developers/apps/authorizing-oauth-apps", + "/enterprise-server@3.0/v3/oauth": "/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", + "/enterprise/3.0/v3/oauth": "/enterprise-server@3.0/developers/apps/authorizing-oauth-apps", + "/enterprise/v3/oauth": "/enterprise-server@latest/developers/apps/authorizing-oauth-apps", + "/enterprise-server@2.20/v3/oauth": "/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", + "/enterprise/2.20/v3/oauth": "/enterprise-server@2.20/developers/apps/authorizing-oauth-apps", + "/github-ae@latest/v3/oauth": "/github-ae@latest/developers/apps/authorizing-oauth-apps", + "/v3/integrations": "/developers/apps", + "/free-pro-team@latest/v3/integrations": "/developers/apps", + "/enterprise-server@3.0/v3/integrations": "/enterprise-server@3.0/developers/apps", + "/enterprise/3.0/v3/integrations": "/enterprise-server@3.0/developers/apps", + "/enterprise/v3/integrations": "/enterprise-server@latest/developers/apps", + "/enterprise-server@2.20/v3/integrations": "/enterprise-server@2.20/developers/apps", + "/enterprise/2.20/v3/integrations": "/enterprise-server@2.20/developers/apps", + "/github-ae@latest/v3/integrations": "/github-ae@latest/developers/apps", + "/free-pro-team@latest/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api": "/developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api", + "/v3/versions": "/developers/overview/about-githubs-apis", + "/free-pro-team@latest/v3/versions": "/developers/overview/about-githubs-apis", + "/enterprise-server@3.0/v3/versions": "/enterprise-server@3.0/developers/overview/about-githubs-apis", + "/enterprise/3.0/v3/versions": "/enterprise-server@3.0/developers/overview/about-githubs-apis", + "/enterprise/v3/versions": "/enterprise-server@latest/developers/overview/about-githubs-apis", + "/enterprise-server@2.20/v3/versions": "/enterprise-server@2.20/developers/overview/about-githubs-apis", + "/enterprise/2.20/v3/versions": "/enterprise-server@2.20/developers/overview/about-githubs-apis", + "/github-ae@latest/v3/versions": "/github-ae@latest/developers/overview/about-githubs-apis", + "/v3/guides/managing-deploy-keys": "/developers/overview/managing-deploy-keys", + "/free-pro-team@latest/v3/guides/managing-deploy-keys": "/developers/overview/managing-deploy-keys", + "/enterprise-server@3.0/v3/guides/managing-deploy-keys": "/enterprise-server@3.0/developers/overview/managing-deploy-keys", + "/enterprise/3.0/v3/guides/managing-deploy-keys": "/enterprise-server@3.0/developers/overview/managing-deploy-keys", + "/enterprise/v3/guides/managing-deploy-keys": "/enterprise-server@latest/developers/overview/managing-deploy-keys", + "/enterprise-server@2.20/v3/guides/managing-deploy-keys": "/enterprise-server@2.20/developers/overview/managing-deploy-keys", + "/enterprise/2.20/v3/guides/managing-deploy-keys": "/enterprise-server@2.20/developers/overview/managing-deploy-keys", + "/github-ae@latest/v3/guides/managing-deploy-keys": "/github-ae@latest/developers/overview/managing-deploy-keys", + "/v3/guides/automating-deployments-to-integrators": "/developers/overview/replacing-github-services", + "/free-pro-team@latest/v3/guides/automating-deployments-to-integrators": "/developers/overview/replacing-github-services", + "/v3/guides/replacing-github-services": "/developers/overview/replacing-github-services", + "/free-pro-team@latest/v3/guides/replacing-github-services": "/developers/overview/replacing-github-services", + "/enterprise-server@3.0/v3/guides/automating-deployments-to-integrators": "/enterprise-server@3.0/developers/overview/replacing-github-services", + "/enterprise/3.0/v3/guides/automating-deployments-to-integrators": "/enterprise-server@3.0/developers/overview/replacing-github-services", + "/enterprise/v3/guides/automating-deployments-to-integrators": "/enterprise-server@latest/developers/overview/replacing-github-services", + "/enterprise-server@3.0/v3/guides/replacing-github-services": "/enterprise-server@3.0/developers/overview/replacing-github-services", + "/enterprise/3.0/v3/guides/replacing-github-services": "/enterprise-server@3.0/developers/overview/replacing-github-services", + "/enterprise/v3/guides/replacing-github-services": "/enterprise-server@latest/developers/overview/replacing-github-services", + "/enterprise-server@2.20/v3/guides/automating-deployments-to-integrators": "/enterprise-server@2.20/developers/overview/replacing-github-services", + "/enterprise/2.20/v3/guides/automating-deployments-to-integrators": "/enterprise-server@2.20/developers/overview/replacing-github-services", + "/enterprise-server@2.20/v3/guides/replacing-github-services": "/enterprise-server@2.20/developers/overview/replacing-github-services", + "/enterprise/2.20/v3/guides/replacing-github-services": "/enterprise-server@2.20/developers/overview/replacing-github-services", + "/v3/guides/using-ssh-agent-forwarding": "/developers/overview/using-ssh-agent-forwarding", + "/free-pro-team@latest/v3/guides/using-ssh-agent-forwarding": "/developers/overview/using-ssh-agent-forwarding", + "/enterprise-server@3.0/v3/guides/using-ssh-agent-forwarding": "/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", + "/enterprise/3.0/v3/guides/using-ssh-agent-forwarding": "/enterprise-server@3.0/developers/overview/using-ssh-agent-forwarding", + "/enterprise/v3/guides/using-ssh-agent-forwarding": "/enterprise-server@latest/developers/overview/using-ssh-agent-forwarding", + "/enterprise-server@2.20/v3/guides/using-ssh-agent-forwarding": "/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", + "/enterprise/2.20/v3/guides/using-ssh-agent-forwarding": "/enterprise-server@2.20/developers/overview/using-ssh-agent-forwarding", + "/github-ae@latest/v3/guides/using-ssh-agent-forwarding": "/github-ae@latest/developers/overview/using-ssh-agent-forwarding", + "/v3/activity/event_types": "/developers/webhooks-and-events/github-event-types", + "/free-pro-team@latest/v3/activity/event_types": "/developers/webhooks-and-events/github-event-types", + "/enterprise-server@3.0/v3/activity/event_types": "/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", + "/enterprise/3.0/v3/activity/event_types": "/enterprise-server@3.0/developers/webhooks-and-events/github-event-types", + "/enterprise/v3/activity/event_types": "/enterprise-server@latest/developers/webhooks-and-events/github-event-types", + "/enterprise-server@2.20/v3/activity/event_types": "/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", + "/enterprise/2.20/v3/activity/event_types": "/enterprise-server@2.20/developers/webhooks-and-events/github-event-types", + "/github-ae@latest/v3/activity/event_types": "/github-ae@latest/developers/webhooks-and-events/github-event-types", + "/v3/issues/issue-event-types": "/developers/webhooks-and-events/issue-event-types", + "/free-pro-team@latest/v3/issues/issue-event-types": "/developers/webhooks-and-events/issue-event-types", + "/enterprise-server@3.0/v3/issues/issue-event-types": "/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", + "/enterprise/3.0/v3/issues/issue-event-types": "/enterprise-server@3.0/developers/webhooks-and-events/issue-event-types", + "/enterprise/v3/issues/issue-event-types": "/enterprise-server@latest/developers/webhooks-and-events/issue-event-types", + "/enterprise-server@2.20/v3/issues/issue-event-types": "/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", + "/enterprise/2.20/v3/issues/issue-event-types": "/enterprise-server@2.20/developers/webhooks-and-events/issue-event-types", + "/github-ae@latest/v3/issues/issue-event-types": "/github-ae@latest/developers/webhooks-and-events/issue-event-types", + "/v3/activity/events/types": "/developers/webhooks-and-events/webhook-events-and-payloads", + "/free-pro-team@latest/v3/activity/events/types": "/developers/webhooks-and-events/webhook-events-and-payloads", + "/enterprise-server@3.0/v3/activity/events/types": "/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", + "/enterprise/3.0/v3/activity/events/types": "/enterprise-server@3.0/developers/webhooks-and-events/webhook-events-and-payloads", + "/enterprise/v3/activity/events/types": "/enterprise-server@latest/developers/webhooks-and-events/webhook-events-and-payloads", + "/enterprise-server@2.20/v3/activity/events/types": "/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", + "/enterprise/2.20/v3/activity/events/types": "/enterprise-server@2.20/developers/webhooks-and-events/webhook-events-and-payloads", + "/github-ae@latest/v3/activity/events/types": "/github-ae@latest/developers/webhooks-and-events/webhook-events-and-payloads", + "/articles/restoring-branches-in-a-pull-request": "/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/free-pro-team@latest/articles/restoring-branches-in-a-pull-request": "/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise-server@3.0/articles/restoring-branches-in-a-pull-request": "/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/3.0/articles/restoring-branches-in-a-pull-request": "/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/articles/restoring-branches-in-a-pull-request": "/enterprise-server@3.0/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise-server@2.20/articles/restoring-branches-in-a-pull-request": "/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/enterprise/2.20/articles/restoring-branches-in-a-pull-request": "/enterprise-server@2.20/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/github-ae@latest/articles/restoring-branches-in-a-pull-request": "/github-ae@latest/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request", + "/free-pro-team@latest/github/administering-a-repository/restoring-a-deleted-repository": "/github/administering-a-repository/restoring-a-deleted-repository", + "/articles/restoring-a-deleted-repository": "/github/administering-a-repository/restoring-a-deleted-repository", + "/free-pro-team@latest/articles/restoring-a-deleted-repository": "/github/administering-a-repository/restoring-a-deleted-repository", + "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data": "/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", + "/articles/restricting-access-to-your-organization-s-data": "/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", + "/free-pro-team@latest/articles/restricting-access-to-your-organization-s-data": "/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", + "/articles/restricting-access-to-your-organizations-data": "/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", + "/free-pro-team@latest/articles/restricting-access-to-your-organizations-data": "/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data", + "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain": "/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", + "/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", + "/free-pro-team@latest/articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain": "/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", + "/articles/restricting-email-notifications-to-an-approved-domain": "/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", + "/free-pro-team@latest/articles/restricting-email-notifications-to-an-approved-domain": "/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain", + "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/articles/restricting-repository-creation-in-your-organization": "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/free-pro-team@latest/articles/restricting-repository-creation-in-your-organization": "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise-server@3.0/articles/restricting-repository-creation-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/3.0/articles/restricting-repository-creation-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/articles/restricting-repository-creation-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise-server@2.20/articles/restricting-repository-creation-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/enterprise/2.20/articles/restricting-repository-creation-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/github-ae@latest/articles/restricting-repository-creation-in-your-organization": "/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization", + "/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/articles/restricting-repository-visibility-changes-in-your-organization": "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/free-pro-team@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/3.0/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise-server@3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/3.0/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.20/user/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise-server@2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/enterprise/2.20/articles/restricting-repository-visibility-changes-in-your-organization": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/github-ae@latest/articles/restricting-repository-visibility-changes-in-your-organization": "/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization", + "/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/free-pro-team@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise-server@3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/3.0/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise-server@2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/enterprise/2.20/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/enterprise-server@2.20/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/github-ae@latest/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories": "/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators", + "/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains": "/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains", + "/free-pro-team@latest/graphql/guides/forming-calls-with-graphql": "/graphql/guides/forming-calls-with-graphql", + "/v4/guides/forming-calls": "/graphql/guides/forming-calls-with-graphql", + "/free-pro-team@latest/v4/guides/forming-calls": "/graphql/guides/forming-calls-with-graphql", + "/graphql/guides/forming-calls": "/graphql/guides/forming-calls-with-graphql", + "/free-pro-team@latest/graphql/guides/forming-calls": "/graphql/guides/forming-calls-with-graphql", + "/enterprise/3.0/graphql/guides/forming-calls-with-graphql": "/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", + "/enterprise/graphql/guides/forming-calls-with-graphql": "/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", + "/enterprise-server@3.0/v4/guides/forming-calls": "/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", + "/enterprise/3.0/v4/guides/forming-calls": "/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", + "/enterprise/v4/guides/forming-calls": "/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", + "/enterprise-server@3.0/graphql/guides/forming-calls": "/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", + "/enterprise/3.0/graphql/guides/forming-calls": "/enterprise-server@3.0/graphql/guides/forming-calls-with-graphql", + "/enterprise/graphql/guides/forming-calls": "/enterprise-server@latest/graphql/guides/forming-calls-with-graphql", + "/enterprise/2.20/graphql/guides/forming-calls-with-graphql": "/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", + "/enterprise-server@2.20/v4/guides/forming-calls": "/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", + "/enterprise/2.20/v4/guides/forming-calls": "/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", + "/enterprise-server@2.20/graphql/guides/forming-calls": "/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", + "/enterprise/2.20/graphql/guides/forming-calls": "/enterprise-server@2.20/graphql/guides/forming-calls-with-graphql", + "/github-ae@latest/v4/guides/forming-calls": "/github-ae@latest/graphql/guides/forming-calls-with-graphql", + "/github-ae@latest/graphql/guides/forming-calls": "/github-ae@latest/graphql/guides/forming-calls-with-graphql", + "/free-pro-team@latest/graphql/guides": "/graphql/guides", + "/v4/guides": "/graphql/guides", + "/free-pro-team@latest/v4/guides": "/graphql/guides", + "/enterprise/3.0/graphql/guides": "/enterprise-server@3.0/graphql/guides", + "/enterprise/graphql/guides": "/enterprise-server@latest/graphql/guides", + "/enterprise-server@3.0/v4/guides": "/enterprise-server@3.0/graphql/guides", + "/enterprise/3.0/v4/guides": "/enterprise-server@3.0/graphql/guides", + "/enterprise/v4/guides": "/enterprise-server@latest/graphql/guides", + "/enterprise/2.20/graphql/guides": "/enterprise-server@2.20/graphql/guides", + "/enterprise-server@2.20/v4/guides": "/enterprise-server@2.20/graphql/guides", + "/enterprise/2.20/v4/guides": "/enterprise-server@2.20/graphql/guides", + "/github-ae@latest/v4/guides": "/github-ae@latest/graphql/guides", + "/free-pro-team@latest/graphql/guides/introduction-to-graphql": "/graphql/guides/introduction-to-graphql", + "/v4/guides/intro-to-graphql": "/graphql/guides/introduction-to-graphql", + "/free-pro-team@latest/v4/guides/intro-to-graphql": "/graphql/guides/introduction-to-graphql", + "/graphql/guides/intro-to-graphql": "/graphql/guides/introduction-to-graphql", + "/free-pro-team@latest/graphql/guides/intro-to-graphql": "/graphql/guides/introduction-to-graphql", + "/enterprise/3.0/graphql/guides/introduction-to-graphql": "/enterprise-server@3.0/graphql/guides/introduction-to-graphql", + "/enterprise/graphql/guides/introduction-to-graphql": "/enterprise-server@latest/graphql/guides/introduction-to-graphql", + "/enterprise-server@3.0/v4/guides/intro-to-graphql": "/enterprise-server@3.0/graphql/guides/introduction-to-graphql", + "/enterprise/3.0/v4/guides/intro-to-graphql": "/enterprise-server@3.0/graphql/guides/introduction-to-graphql", + "/enterprise/v4/guides/intro-to-graphql": "/enterprise-server@latest/graphql/guides/introduction-to-graphql", + "/enterprise-server@3.0/graphql/guides/intro-to-graphql": "/enterprise-server@3.0/graphql/guides/introduction-to-graphql", + "/enterprise/3.0/graphql/guides/intro-to-graphql": "/enterprise-server@3.0/graphql/guides/introduction-to-graphql", + "/enterprise/graphql/guides/intro-to-graphql": "/enterprise-server@latest/graphql/guides/introduction-to-graphql", + "/enterprise/2.20/graphql/guides/introduction-to-graphql": "/enterprise-server@2.20/graphql/guides/introduction-to-graphql", + "/enterprise-server@2.20/v4/guides/intro-to-graphql": "/enterprise-server@2.20/graphql/guides/introduction-to-graphql", + "/enterprise/2.20/v4/guides/intro-to-graphql": "/enterprise-server@2.20/graphql/guides/introduction-to-graphql", + "/enterprise-server@2.20/graphql/guides/intro-to-graphql": "/enterprise-server@2.20/graphql/guides/introduction-to-graphql", + "/enterprise/2.20/graphql/guides/intro-to-graphql": "/enterprise-server@2.20/graphql/guides/introduction-to-graphql", + "/github-ae@latest/v4/guides/intro-to-graphql": "/github-ae@latest/graphql/guides/introduction-to-graphql", + "/github-ae@latest/graphql/guides/intro-to-graphql": "/github-ae@latest/graphql/guides/introduction-to-graphql", + "/free-pro-team@latest/graphql/guides/managing-enterprise-accounts": "/graphql/guides/managing-enterprise-accounts", + "/v4/guides/managing-enterprise-accounts": "/graphql/guides/managing-enterprise-accounts", + "/free-pro-team@latest/v4/guides/managing-enterprise-accounts": "/graphql/guides/managing-enterprise-accounts", + "/enterprise/3.0/graphql/guides/managing-enterprise-accounts": "/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", + "/enterprise/graphql/guides/managing-enterprise-accounts": "/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", + "/enterprise-server@3.0/v4/guides/managing-enterprise-accounts": "/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", + "/enterprise/3.0/v4/guides/managing-enterprise-accounts": "/enterprise-server@3.0/graphql/guides/managing-enterprise-accounts", + "/enterprise/v4/guides/managing-enterprise-accounts": "/enterprise-server@latest/graphql/guides/managing-enterprise-accounts", + "/enterprise/2.20/graphql/guides/managing-enterprise-accounts": "/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", + "/enterprise-server@2.20/v4/guides/managing-enterprise-accounts": "/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", + "/enterprise/2.20/v4/guides/managing-enterprise-accounts": "/enterprise-server@2.20/graphql/guides/managing-enterprise-accounts", + "/github-ae@latest/v4/guides/managing-enterprise-accounts": "/github-ae@latest/graphql/guides/managing-enterprise-accounts", + "/free-pro-team@latest/graphql/guides/migrating-from-rest-to-graphql": "/graphql/guides/migrating-from-rest-to-graphql", + "/v4/guides/migrating-from-rest": "/graphql/guides/migrating-from-rest-to-graphql", + "/free-pro-team@latest/v4/guides/migrating-from-rest": "/graphql/guides/migrating-from-rest-to-graphql", + "/graphql/guides/migrating-from-rest": "/graphql/guides/migrating-from-rest-to-graphql", + "/free-pro-team@latest/graphql/guides/migrating-from-rest": "/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/3.0/graphql/guides/migrating-from-rest-to-graphql": "/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/graphql/guides/migrating-from-rest-to-graphql": "/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise-server@3.0/v4/guides/migrating-from-rest": "/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/3.0/v4/guides/migrating-from-rest": "/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/v4/guides/migrating-from-rest": "/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise-server@3.0/graphql/guides/migrating-from-rest": "/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/3.0/graphql/guides/migrating-from-rest": "/enterprise-server@3.0/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/graphql/guides/migrating-from-rest": "/enterprise-server@latest/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/2.20/graphql/guides/migrating-from-rest-to-graphql": "/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise-server@2.20/v4/guides/migrating-from-rest": "/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/2.20/v4/guides/migrating-from-rest": "/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise-server@2.20/graphql/guides/migrating-from-rest": "/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", + "/enterprise/2.20/graphql/guides/migrating-from-rest": "/enterprise-server@2.20/graphql/guides/migrating-from-rest-to-graphql", + "/github-ae@latest/v4/guides/migrating-from-rest": "/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", + "/github-ae@latest/graphql/guides/migrating-from-rest": "/github-ae@latest/graphql/guides/migrating-from-rest-to-graphql", + "/free-pro-team@latest/graphql/guides/using-global-node-ids": "/graphql/guides/using-global-node-ids", + "/v4/guides/using-global-node-ids": "/graphql/guides/using-global-node-ids", + "/free-pro-team@latest/v4/guides/using-global-node-ids": "/graphql/guides/using-global-node-ids", + "/enterprise/3.0/graphql/guides/using-global-node-ids": "/enterprise-server@3.0/graphql/guides/using-global-node-ids", + "/enterprise/graphql/guides/using-global-node-ids": "/enterprise-server@latest/graphql/guides/using-global-node-ids", + "/enterprise-server@3.0/v4/guides/using-global-node-ids": "/enterprise-server@3.0/graphql/guides/using-global-node-ids", + "/enterprise/3.0/v4/guides/using-global-node-ids": "/enterprise-server@3.0/graphql/guides/using-global-node-ids", + "/enterprise/v4/guides/using-global-node-ids": "/enterprise-server@latest/graphql/guides/using-global-node-ids", + "/enterprise/2.20/graphql/guides/using-global-node-ids": "/enterprise-server@2.20/graphql/guides/using-global-node-ids", + "/enterprise-server@2.20/v4/guides/using-global-node-ids": "/enterprise-server@2.20/graphql/guides/using-global-node-ids", + "/enterprise/2.20/v4/guides/using-global-node-ids": "/enterprise-server@2.20/graphql/guides/using-global-node-ids", + "/github-ae@latest/v4/guides/using-global-node-ids": "/github-ae@latest/graphql/guides/using-global-node-ids", + "/free-pro-team@latest/graphql/guides/using-the-explorer": "/graphql/guides/using-the-explorer", + "/v4/guides/using-the-explorer": "/graphql/guides/using-the-explorer", + "/free-pro-team@latest/v4/guides/using-the-explorer": "/graphql/guides/using-the-explorer", + "/enterprise/3.0/graphql/guides/using-the-explorer": "/enterprise-server@3.0/graphql/guides/using-the-explorer", + "/enterprise/graphql/guides/using-the-explorer": "/enterprise-server@latest/graphql/guides/using-the-explorer", + "/enterprise-server@3.0/v4/guides/using-the-explorer": "/enterprise-server@3.0/graphql/guides/using-the-explorer", + "/enterprise/3.0/v4/guides/using-the-explorer": "/enterprise-server@3.0/graphql/guides/using-the-explorer", + "/enterprise/v4/guides/using-the-explorer": "/enterprise-server@latest/graphql/guides/using-the-explorer", + "/enterprise/2.20/graphql/guides/using-the-explorer": "/enterprise-server@2.20/graphql/guides/using-the-explorer", + "/enterprise-server@2.20/v4/guides/using-the-explorer": "/enterprise-server@2.20/graphql/guides/using-the-explorer", + "/enterprise/2.20/v4/guides/using-the-explorer": "/enterprise-server@2.20/graphql/guides/using-the-explorer", + "/github-ae@latest/v4/guides/using-the-explorer": "/github-ae@latest/graphql/guides/using-the-explorer", + "/free-pro-team@latest/graphql": "/graphql", + "/v4": "/graphql", + "/free-pro-team@latest/v4": "/graphql", + "/enterprise/3.0/graphql": "/enterprise-server@3.0/graphql", + "/enterprise/graphql": "/enterprise-server@latest/graphql", + "/enterprise-server@3.0/v4": "/enterprise-server@3.0/graphql", + "/enterprise/3.0/v4": "/enterprise-server@3.0/graphql", + "/enterprise/v4": "/enterprise-server@latest/graphql", + "/enterprise/2.20/graphql": "/enterprise-server@2.20/graphql", + "/enterprise-server@2.20/v4": "/enterprise-server@2.20/graphql", + "/enterprise/2.20/v4": "/enterprise-server@2.20/graphql", + "/github-ae@latest/v4": "/github-ae@latest/graphql", + "/free-pro-team@latest/graphql/overview/about-the-graphql-api": "/graphql/overview/about-the-graphql-api", + "/enterprise/3.0/graphql/overview/about-the-graphql-api": "/enterprise-server@3.0/graphql/overview/about-the-graphql-api", + "/enterprise/graphql/overview/about-the-graphql-api": "/enterprise-server@latest/graphql/overview/about-the-graphql-api", + "/enterprise/2.20/graphql/overview/about-the-graphql-api": "/enterprise-server@2.20/graphql/overview/about-the-graphql-api", + "/free-pro-team@latest/graphql/overview/breaking-changes": "/graphql/overview/breaking-changes", + "/v4/breaking_changes": "/graphql/overview/breaking-changes", + "/free-pro-team@latest/v4/breaking_changes": "/graphql/overview/breaking-changes", + "/enterprise/3.0/graphql/overview/breaking-changes": "/enterprise-server@3.0/graphql/overview/breaking-changes", + "/enterprise/graphql/overview/breaking-changes": "/enterprise-server@latest/graphql/overview/breaking-changes", + "/enterprise-server@3.0/v4/breaking_changes": "/enterprise-server@3.0/graphql/overview/breaking-changes", + "/enterprise/3.0/v4/breaking_changes": "/enterprise-server@3.0/graphql/overview/breaking-changes", + "/enterprise/v4/breaking_changes": "/enterprise-server@latest/graphql/overview/breaking-changes", + "/enterprise/2.20/graphql/overview/breaking-changes": "/enterprise-server@2.20/graphql/overview/breaking-changes", + "/enterprise-server@2.20/v4/breaking_changes": "/enterprise-server@2.20/graphql/overview/breaking-changes", + "/enterprise/2.20/v4/breaking_changes": "/enterprise-server@2.20/graphql/overview/breaking-changes", + "/github-ae@latest/v4/breaking_changes": "/github-ae@latest/graphql/overview/breaking-changes", + "/free-pro-team@latest/graphql/overview/changelog": "/graphql/overview/changelog", + "/v4/changelog": "/graphql/overview/changelog", + "/free-pro-team@latest/v4/changelog": "/graphql/overview/changelog", + "/enterprise/3.0/graphql/overview/changelog": "/enterprise-server@3.0/graphql/overview/changelog", + "/enterprise/graphql/overview/changelog": "/enterprise-server@latest/graphql/overview/changelog", + "/enterprise-server@3.0/v4/changelog": "/enterprise-server@3.0/graphql/overview/changelog", + "/enterprise/3.0/v4/changelog": "/enterprise-server@3.0/graphql/overview/changelog", + "/enterprise/v4/changelog": "/enterprise-server@latest/graphql/overview/changelog", + "/enterprise/2.20/graphql/overview/changelog": "/enterprise-server@2.20/graphql/overview/changelog", + "/enterprise-server@2.20/v4/changelog": "/enterprise-server@2.20/graphql/overview/changelog", + "/enterprise/2.20/v4/changelog": "/enterprise-server@2.20/graphql/overview/changelog", + "/github-ae@latest/v4/changelog": "/github-ae@latest/graphql/overview/changelog", + "/free-pro-team@latest/graphql/overview/explorer": "/graphql/overview/explorer", + "/v4/explorer": "/graphql/overview/explorer", + "/free-pro-team@latest/v4/explorer": "/graphql/overview/explorer", + "/v4/explorer-new": "/graphql/overview/explorer", + "/free-pro-team@latest/v4/explorer-new": "/graphql/overview/explorer", + "/enterprise/3.0/graphql/overview/explorer": "/enterprise-server@3.0/graphql/overview/explorer", + "/enterprise/graphql/overview/explorer": "/enterprise-server@latest/graphql/overview/explorer", + "/enterprise-server@3.0/v4/explorer": "/enterprise-server@3.0/graphql/overview/explorer", + "/enterprise/3.0/v4/explorer": "/enterprise-server@3.0/graphql/overview/explorer", + "/enterprise/v4/explorer": "/enterprise-server@latest/graphql/overview/explorer", + "/enterprise-server@3.0/v4/explorer-new": "/enterprise-server@3.0/graphql/overview/explorer", + "/enterprise/3.0/v4/explorer-new": "/enterprise-server@3.0/graphql/overview/explorer", + "/enterprise/v4/explorer-new": "/enterprise-server@latest/graphql/overview/explorer", + "/enterprise/2.20/graphql/overview/explorer": "/enterprise-server@2.20/graphql/overview/explorer", + "/enterprise-server@2.20/v4/explorer": "/enterprise-server@2.20/graphql/overview/explorer", + "/enterprise/2.20/v4/explorer": "/enterprise-server@2.20/graphql/overview/explorer", + "/enterprise-server@2.20/v4/explorer-new": "/enterprise-server@2.20/graphql/overview/explorer", + "/enterprise/2.20/v4/explorer-new": "/enterprise-server@2.20/graphql/overview/explorer", + "/github-ae@latest/v4/explorer": "/github-ae@latest/graphql/overview/explorer", + "/github-ae@latest/v4/explorer-new": "/github-ae@latest/graphql/overview/explorer", + "/free-pro-team@latest/graphql/overview": "/graphql/overview", + "/enterprise/3.0/graphql/overview": "/enterprise-server@3.0/graphql/overview", + "/enterprise/graphql/overview": "/enterprise-server@latest/graphql/overview", + "/enterprise/2.20/graphql/overview": "/enterprise-server@2.20/graphql/overview", + "/free-pro-team@latest/graphql/overview/public-schema": "/graphql/overview/public-schema", + "/v4/public_schema": "/graphql/overview/public-schema", + "/free-pro-team@latest/v4/public_schema": "/graphql/overview/public-schema", + "/enterprise/3.0/graphql/overview/public-schema": "/enterprise-server@3.0/graphql/overview/public-schema", + "/enterprise/graphql/overview/public-schema": "/enterprise-server@latest/graphql/overview/public-schema", + "/enterprise-server@3.0/v4/public_schema": "/enterprise-server@3.0/graphql/overview/public-schema", + "/enterprise/3.0/v4/public_schema": "/enterprise-server@3.0/graphql/overview/public-schema", + "/enterprise/v4/public_schema": "/enterprise-server@latest/graphql/overview/public-schema", + "/enterprise/2.20/graphql/overview/public-schema": "/enterprise-server@2.20/graphql/overview/public-schema", + "/enterprise-server@2.20/v4/public_schema": "/enterprise-server@2.20/graphql/overview/public-schema", + "/enterprise/2.20/v4/public_schema": "/enterprise-server@2.20/graphql/overview/public-schema", + "/github-ae@latest/v4/public_schema": "/github-ae@latest/graphql/overview/public-schema", + "/free-pro-team@latest/graphql/overview/resource-limitations": "/graphql/overview/resource-limitations", + "/v4/guides/resource-limitations": "/graphql/overview/resource-limitations", + "/free-pro-team@latest/v4/guides/resource-limitations": "/graphql/overview/resource-limitations", + "/enterprise/3.0/graphql/overview/resource-limitations": "/enterprise-server@3.0/graphql/overview/resource-limitations", + "/enterprise/graphql/overview/resource-limitations": "/enterprise-server@latest/graphql/overview/resource-limitations", + "/enterprise-server@3.0/v4/guides/resource-limitations": "/enterprise-server@3.0/graphql/overview/resource-limitations", + "/enterprise/3.0/v4/guides/resource-limitations": "/enterprise-server@3.0/graphql/overview/resource-limitations", + "/enterprise/v4/guides/resource-limitations": "/enterprise-server@latest/graphql/overview/resource-limitations", + "/enterprise/2.20/graphql/overview/resource-limitations": "/enterprise-server@2.20/graphql/overview/resource-limitations", + "/enterprise-server@2.20/v4/guides/resource-limitations": "/enterprise-server@2.20/graphql/overview/resource-limitations", + "/enterprise/2.20/v4/guides/resource-limitations": "/enterprise-server@2.20/graphql/overview/resource-limitations", + "/github-ae@latest/v4/guides/resource-limitations": "/github-ae@latest/graphql/overview/resource-limitations", + "/free-pro-team@latest/graphql/overview/schema-previews": "/graphql/overview/schema-previews", + "/v4/previews": "/graphql/overview/schema-previews", + "/free-pro-team@latest/v4/previews": "/graphql/overview/schema-previews", + "/enterprise/3.0/graphql/overview/schema-previews": "/enterprise-server@3.0/graphql/overview/schema-previews", + "/enterprise/graphql/overview/schema-previews": "/enterprise-server@latest/graphql/overview/schema-previews", + "/enterprise-server@3.0/v4/previews": "/enterprise-server@3.0/graphql/overview/schema-previews", + "/enterprise/3.0/v4/previews": "/enterprise-server@3.0/graphql/overview/schema-previews", + "/enterprise/v4/previews": "/enterprise-server@latest/graphql/overview/schema-previews", + "/enterprise/2.20/graphql/overview/schema-previews": "/enterprise-server@2.20/graphql/overview/schema-previews", + "/enterprise-server@2.20/v4/previews": "/enterprise-server@2.20/graphql/overview/schema-previews", + "/enterprise/2.20/v4/previews": "/enterprise-server@2.20/graphql/overview/schema-previews", + "/github-ae@latest/v4/previews": "/github-ae@latest/graphql/overview/schema-previews", + "/free-pro-team@latest/graphql/reference/enums": "/graphql/reference/enums", + "/v4/enum": "/graphql/reference/enums", + "/free-pro-team@latest/v4/enum": "/graphql/reference/enums", + "/v4/reference/enum": "/graphql/reference/enums", + "/free-pro-team@latest/v4/reference/enum": "/graphql/reference/enums", + "/enterprise/3.0/graphql/reference/enums": "/enterprise-server@3.0/graphql/reference/enums", + "/enterprise/graphql/reference/enums": "/enterprise-server@latest/graphql/reference/enums", + "/enterprise-server@3.0/v4/enum": "/enterprise-server@3.0/graphql/reference/enums", + "/enterprise/3.0/v4/enum": "/enterprise-server@3.0/graphql/reference/enums", + "/enterprise/v4/enum": "/enterprise-server@latest/graphql/reference/enums", + "/enterprise-server@3.0/v4/reference/enum": "/enterprise-server@3.0/graphql/reference/enums", + "/enterprise/3.0/v4/reference/enum": "/enterprise-server@3.0/graphql/reference/enums", + "/enterprise/v4/reference/enum": "/enterprise-server@latest/graphql/reference/enums", + "/enterprise/2.20/graphql/reference/enums": "/enterprise-server@2.20/graphql/reference/enums", + "/enterprise-server@2.20/v4/enum": "/enterprise-server@2.20/graphql/reference/enums", + "/enterprise/2.20/v4/enum": "/enterprise-server@2.20/graphql/reference/enums", + "/enterprise-server@2.20/v4/reference/enum": "/enterprise-server@2.20/graphql/reference/enums", + "/enterprise/2.20/v4/reference/enum": "/enterprise-server@2.20/graphql/reference/enums", + "/github-ae@latest/v4/enum": "/github-ae@latest/graphql/reference/enums", + "/github-ae@latest/v4/reference/enum": "/github-ae@latest/graphql/reference/enums", + "/free-pro-team@latest/graphql/reference": "/graphql/reference", + "/v4/reference": "/graphql/reference", + "/free-pro-team@latest/v4/reference": "/graphql/reference", + "/enterprise/3.0/graphql/reference": "/enterprise-server@3.0/graphql/reference", + "/enterprise/graphql/reference": "/enterprise-server@latest/graphql/reference", + "/enterprise-server@3.0/v4/reference": "/enterprise-server@3.0/graphql/reference", + "/enterprise/3.0/v4/reference": "/enterprise-server@3.0/graphql/reference", + "/enterprise/v4/reference": "/enterprise-server@latest/graphql/reference", + "/enterprise/2.20/graphql/reference": "/enterprise-server@2.20/graphql/reference", + "/enterprise-server@2.20/v4/reference": "/enterprise-server@2.20/graphql/reference", + "/enterprise/2.20/v4/reference": "/enterprise-server@2.20/graphql/reference", + "/github-ae@latest/v4/reference": "/github-ae@latest/graphql/reference", + "/free-pro-team@latest/graphql/reference/input-objects": "/graphql/reference/input-objects", + "/v4/input_object": "/graphql/reference/input-objects", + "/free-pro-team@latest/v4/input_object": "/graphql/reference/input-objects", + "/v4/reference/input_object": "/graphql/reference/input-objects", + "/free-pro-team@latest/v4/reference/input_object": "/graphql/reference/input-objects", + "/enterprise/3.0/graphql/reference/input-objects": "/enterprise-server@3.0/graphql/reference/input-objects", + "/enterprise/graphql/reference/input-objects": "/enterprise-server@latest/graphql/reference/input-objects", + "/enterprise-server@3.0/v4/input_object": "/enterprise-server@3.0/graphql/reference/input-objects", + "/enterprise/3.0/v4/input_object": "/enterprise-server@3.0/graphql/reference/input-objects", + "/enterprise/v4/input_object": "/enterprise-server@latest/graphql/reference/input-objects", + "/enterprise-server@3.0/v4/reference/input_object": "/enterprise-server@3.0/graphql/reference/input-objects", + "/enterprise/3.0/v4/reference/input_object": "/enterprise-server@3.0/graphql/reference/input-objects", + "/enterprise/v4/reference/input_object": "/enterprise-server@latest/graphql/reference/input-objects", + "/enterprise/2.20/graphql/reference/input-objects": "/enterprise-server@2.20/graphql/reference/input-objects", + "/enterprise-server@2.20/v4/input_object": "/enterprise-server@2.20/graphql/reference/input-objects", + "/enterprise/2.20/v4/input_object": "/enterprise-server@2.20/graphql/reference/input-objects", + "/enterprise-server@2.20/v4/reference/input_object": "/enterprise-server@2.20/graphql/reference/input-objects", + "/enterprise/2.20/v4/reference/input_object": "/enterprise-server@2.20/graphql/reference/input-objects", + "/github-ae@latest/v4/input_object": "/github-ae@latest/graphql/reference/input-objects", + "/github-ae@latest/v4/reference/input_object": "/github-ae@latest/graphql/reference/input-objects", + "/free-pro-team@latest/graphql/reference/interfaces": "/graphql/reference/interfaces", + "/v4/interface": "/graphql/reference/interfaces", + "/free-pro-team@latest/v4/interface": "/graphql/reference/interfaces", + "/v4/reference/interface": "/graphql/reference/interfaces", + "/free-pro-team@latest/v4/reference/interface": "/graphql/reference/interfaces", + "/enterprise/3.0/graphql/reference/interfaces": "/enterprise-server@3.0/graphql/reference/interfaces", + "/enterprise/graphql/reference/interfaces": "/enterprise-server@latest/graphql/reference/interfaces", + "/enterprise-server@3.0/v4/interface": "/enterprise-server@3.0/graphql/reference/interfaces", + "/enterprise/3.0/v4/interface": "/enterprise-server@3.0/graphql/reference/interfaces", + "/enterprise/v4/interface": "/enterprise-server@latest/graphql/reference/interfaces", + "/enterprise-server@3.0/v4/reference/interface": "/enterprise-server@3.0/graphql/reference/interfaces", + "/enterprise/3.0/v4/reference/interface": "/enterprise-server@3.0/graphql/reference/interfaces", + "/enterprise/v4/reference/interface": "/enterprise-server@latest/graphql/reference/interfaces", + "/enterprise/2.20/graphql/reference/interfaces": "/enterprise-server@2.20/graphql/reference/interfaces", + "/enterprise-server@2.20/v4/interface": "/enterprise-server@2.20/graphql/reference/interfaces", + "/enterprise/2.20/v4/interface": "/enterprise-server@2.20/graphql/reference/interfaces", + "/enterprise-server@2.20/v4/reference/interface": "/enterprise-server@2.20/graphql/reference/interfaces", + "/enterprise/2.20/v4/reference/interface": "/enterprise-server@2.20/graphql/reference/interfaces", + "/github-ae@latest/v4/interface": "/github-ae@latest/graphql/reference/interfaces", + "/github-ae@latest/v4/reference/interface": "/github-ae@latest/graphql/reference/interfaces", + "/free-pro-team@latest/graphql/reference/mutations": "/graphql/reference/mutations", + "/v4/mutation": "/graphql/reference/mutations", + "/free-pro-team@latest/v4/mutation": "/graphql/reference/mutations", + "/v4/reference/mutation": "/graphql/reference/mutations", + "/free-pro-team@latest/v4/reference/mutation": "/graphql/reference/mutations", + "/enterprise/3.0/graphql/reference/mutations": "/enterprise-server@3.0/graphql/reference/mutations", + "/enterprise/graphql/reference/mutations": "/enterprise-server@latest/graphql/reference/mutations", + "/enterprise-server@3.0/v4/mutation": "/enterprise-server@3.0/graphql/reference/mutations", + "/enterprise/3.0/v4/mutation": "/enterprise-server@3.0/graphql/reference/mutations", + "/enterprise/v4/mutation": "/enterprise-server@latest/graphql/reference/mutations", + "/enterprise-server@3.0/v4/reference/mutation": "/enterprise-server@3.0/graphql/reference/mutations", + "/enterprise/3.0/v4/reference/mutation": "/enterprise-server@3.0/graphql/reference/mutations", + "/enterprise/v4/reference/mutation": "/enterprise-server@latest/graphql/reference/mutations", + "/enterprise/2.20/graphql/reference/mutations": "/enterprise-server@2.20/graphql/reference/mutations", + "/enterprise-server@2.20/v4/mutation": "/enterprise-server@2.20/graphql/reference/mutations", + "/enterprise/2.20/v4/mutation": "/enterprise-server@2.20/graphql/reference/mutations", + "/enterprise-server@2.20/v4/reference/mutation": "/enterprise-server@2.20/graphql/reference/mutations", + "/enterprise/2.20/v4/reference/mutation": "/enterprise-server@2.20/graphql/reference/mutations", + "/github-ae@latest/v4/mutation": "/github-ae@latest/graphql/reference/mutations", + "/github-ae@latest/v4/reference/mutation": "/github-ae@latest/graphql/reference/mutations", + "/free-pro-team@latest/graphql/reference/objects": "/graphql/reference/objects", + "/v4/object": "/graphql/reference/objects", + "/free-pro-team@latest/v4/object": "/graphql/reference/objects", + "/v4/reference/object": "/graphql/reference/objects", + "/free-pro-team@latest/v4/reference/object": "/graphql/reference/objects", + "/enterprise/3.0/graphql/reference/objects": "/enterprise-server@3.0/graphql/reference/objects", + "/enterprise/graphql/reference/objects": "/enterprise-server@latest/graphql/reference/objects", + "/enterprise-server@3.0/v4/object": "/enterprise-server@3.0/graphql/reference/objects", + "/enterprise/3.0/v4/object": "/enterprise-server@3.0/graphql/reference/objects", + "/enterprise/v4/object": "/enterprise-server@latest/graphql/reference/objects", + "/enterprise-server@3.0/v4/reference/object": "/enterprise-server@3.0/graphql/reference/objects", + "/enterprise/3.0/v4/reference/object": "/enterprise-server@3.0/graphql/reference/objects", + "/enterprise/v4/reference/object": "/enterprise-server@latest/graphql/reference/objects", + "/enterprise/2.20/graphql/reference/objects": "/enterprise-server@2.20/graphql/reference/objects", + "/enterprise-server@2.20/v4/object": "/enterprise-server@2.20/graphql/reference/objects", + "/enterprise/2.20/v4/object": "/enterprise-server@2.20/graphql/reference/objects", + "/enterprise-server@2.20/v4/reference/object": "/enterprise-server@2.20/graphql/reference/objects", + "/enterprise/2.20/v4/reference/object": "/enterprise-server@2.20/graphql/reference/objects", + "/github-ae@latest/v4/object": "/github-ae@latest/graphql/reference/objects", + "/github-ae@latest/v4/reference/object": "/github-ae@latest/graphql/reference/objects", + "/free-pro-team@latest/graphql/reference/queries": "/graphql/reference/queries", + "/v4/query": "/graphql/reference/queries", + "/free-pro-team@latest/v4/query": "/graphql/reference/queries", + "/v4/reference/query": "/graphql/reference/queries", + "/free-pro-team@latest/v4/reference/query": "/graphql/reference/queries", + "/enterprise/3.0/graphql/reference/queries": "/enterprise-server@3.0/graphql/reference/queries", + "/enterprise/graphql/reference/queries": "/enterprise-server@latest/graphql/reference/queries", + "/enterprise-server@3.0/v4/query": "/enterprise-server@3.0/graphql/reference/queries", + "/enterprise/3.0/v4/query": "/enterprise-server@3.0/graphql/reference/queries", + "/enterprise/v4/query": "/enterprise-server@latest/graphql/reference/queries", + "/enterprise-server@3.0/v4/reference/query": "/enterprise-server@3.0/graphql/reference/queries", + "/enterprise/3.0/v4/reference/query": "/enterprise-server@3.0/graphql/reference/queries", + "/enterprise/v4/reference/query": "/enterprise-server@latest/graphql/reference/queries", + "/enterprise/2.20/graphql/reference/queries": "/enterprise-server@2.20/graphql/reference/queries", + "/enterprise-server@2.20/v4/query": "/enterprise-server@2.20/graphql/reference/queries", + "/enterprise/2.20/v4/query": "/enterprise-server@2.20/graphql/reference/queries", + "/enterprise-server@2.20/v4/reference/query": "/enterprise-server@2.20/graphql/reference/queries", + "/enterprise/2.20/v4/reference/query": "/enterprise-server@2.20/graphql/reference/queries", + "/github-ae@latest/v4/query": "/github-ae@latest/graphql/reference/queries", + "/github-ae@latest/v4/reference/query": "/github-ae@latest/graphql/reference/queries", + "/free-pro-team@latest/graphql/reference/scalars": "/graphql/reference/scalars", + "/v4/scalar": "/graphql/reference/scalars", + "/free-pro-team@latest/v4/scalar": "/graphql/reference/scalars", + "/v4/reference/scalar": "/graphql/reference/scalars", + "/free-pro-team@latest/v4/reference/scalar": "/graphql/reference/scalars", + "/enterprise/3.0/graphql/reference/scalars": "/enterprise-server@3.0/graphql/reference/scalars", + "/enterprise/graphql/reference/scalars": "/enterprise-server@latest/graphql/reference/scalars", + "/enterprise-server@3.0/v4/scalar": "/enterprise-server@3.0/graphql/reference/scalars", + "/enterprise/3.0/v4/scalar": "/enterprise-server@3.0/graphql/reference/scalars", + "/enterprise/v4/scalar": "/enterprise-server@latest/graphql/reference/scalars", + "/enterprise-server@3.0/v4/reference/scalar": "/enterprise-server@3.0/graphql/reference/scalars", + "/enterprise/3.0/v4/reference/scalar": "/enterprise-server@3.0/graphql/reference/scalars", + "/enterprise/v4/reference/scalar": "/enterprise-server@latest/graphql/reference/scalars", + "/enterprise/2.20/graphql/reference/scalars": "/enterprise-server@2.20/graphql/reference/scalars", + "/enterprise-server@2.20/v4/scalar": "/enterprise-server@2.20/graphql/reference/scalars", + "/enterprise/2.20/v4/scalar": "/enterprise-server@2.20/graphql/reference/scalars", + "/enterprise-server@2.20/v4/reference/scalar": "/enterprise-server@2.20/graphql/reference/scalars", + "/enterprise/2.20/v4/reference/scalar": "/enterprise-server@2.20/graphql/reference/scalars", + "/github-ae@latest/v4/scalar": "/github-ae@latest/graphql/reference/scalars", + "/github-ae@latest/v4/reference/scalar": "/github-ae@latest/graphql/reference/scalars", + "/free-pro-team@latest/graphql/reference/unions": "/graphql/reference/unions", + "/v4/union": "/graphql/reference/unions", + "/free-pro-team@latest/v4/union": "/graphql/reference/unions", + "/v4/reference/union": "/graphql/reference/unions", + "/free-pro-team@latest/v4/reference/union": "/graphql/reference/unions", + "/enterprise/3.0/graphql/reference/unions": "/enterprise-server@3.0/graphql/reference/unions", + "/enterprise/graphql/reference/unions": "/enterprise-server@latest/graphql/reference/unions", + "/enterprise-server@3.0/v4/union": "/enterprise-server@3.0/graphql/reference/unions", + "/enterprise/3.0/v4/union": "/enterprise-server@3.0/graphql/reference/unions", + "/enterprise/v4/union": "/enterprise-server@latest/graphql/reference/unions", + "/enterprise-server@3.0/v4/reference/union": "/enterprise-server@3.0/graphql/reference/unions", + "/enterprise/3.0/v4/reference/union": "/enterprise-server@3.0/graphql/reference/unions", + "/enterprise/v4/reference/union": "/enterprise-server@latest/graphql/reference/unions", + "/enterprise/2.20/graphql/reference/unions": "/enterprise-server@2.20/graphql/reference/unions", + "/enterprise-server@2.20/v4/union": "/enterprise-server@2.20/graphql/reference/unions", + "/enterprise/2.20/v4/union": "/enterprise-server@2.20/graphql/reference/unions", + "/enterprise-server@2.20/v4/reference/union": "/enterprise-server@2.20/graphql/reference/unions", + "/enterprise/2.20/v4/reference/union": "/enterprise-server@2.20/graphql/reference/unions", + "/github-ae@latest/v4/union": "/github-ae@latest/graphql/reference/unions", + "/github-ae@latest/v4/reference/union": "/github-ae@latest/graphql/reference/unions", + "/free-pro-team@latest/rest/guides/basics-of-authentication": "/rest/guides/basics-of-authentication", + "/v3/guides/basics-of-authentication": "/rest/guides/basics-of-authentication", + "/free-pro-team@latest/v3/guides/basics-of-authentication": "/rest/guides/basics-of-authentication", + "/rest/basics-of-authentication": "/rest/guides/basics-of-authentication", + "/free-pro-team@latest/rest/basics-of-authentication": "/rest/guides/basics-of-authentication", + "/enterprise/3.0/rest/guides/basics-of-authentication": "/enterprise-server@3.0/rest/guides/basics-of-authentication", + "/enterprise/rest/guides/basics-of-authentication": "/enterprise-server@latest/rest/guides/basics-of-authentication", + "/enterprise-server@3.0/v3/guides/basics-of-authentication": "/enterprise-server@3.0/rest/guides/basics-of-authentication", + "/enterprise/3.0/v3/guides/basics-of-authentication": "/enterprise-server@3.0/rest/guides/basics-of-authentication", + "/enterprise/v3/guides/basics-of-authentication": "/enterprise-server@latest/rest/guides/basics-of-authentication", + "/enterprise-server@3.0/rest/basics-of-authentication": "/enterprise-server@3.0/rest/guides/basics-of-authentication", + "/enterprise/3.0/rest/basics-of-authentication": "/enterprise-server@3.0/rest/guides/basics-of-authentication", + "/enterprise/rest/basics-of-authentication": "/enterprise-server@latest/rest/guides/basics-of-authentication", + "/enterprise/2.20/rest/guides/basics-of-authentication": "/enterprise-server@2.20/rest/guides/basics-of-authentication", + "/enterprise-server@2.20/v3/guides/basics-of-authentication": "/enterprise-server@2.20/rest/guides/basics-of-authentication", + "/enterprise/2.20/v3/guides/basics-of-authentication": "/enterprise-server@2.20/rest/guides/basics-of-authentication", + "/enterprise-server@2.20/rest/basics-of-authentication": "/enterprise-server@2.20/rest/guides/basics-of-authentication", + "/enterprise/2.20/rest/basics-of-authentication": "/enterprise-server@2.20/rest/guides/basics-of-authentication", + "/github-ae@latest/v3/guides/basics-of-authentication": "/github-ae@latest/rest/guides/basics-of-authentication", + "/github-ae@latest/rest/basics-of-authentication": "/github-ae@latest/rest/guides/basics-of-authentication", + "/free-pro-team@latest/rest/guides/best-practices-for-integrators": "/rest/guides/best-practices-for-integrators", + "/v3/guides/best-practices-for-integrators": "/rest/guides/best-practices-for-integrators", + "/free-pro-team@latest/v3/guides/best-practices-for-integrators": "/rest/guides/best-practices-for-integrators", + "/enterprise/3.0/rest/guides/best-practices-for-integrators": "/enterprise-server@3.0/rest/guides/best-practices-for-integrators", + "/enterprise/rest/guides/best-practices-for-integrators": "/enterprise-server@latest/rest/guides/best-practices-for-integrators", + "/enterprise-server@3.0/v3/guides/best-practices-for-integrators": "/enterprise-server@3.0/rest/guides/best-practices-for-integrators", + "/enterprise/3.0/v3/guides/best-practices-for-integrators": "/enterprise-server@3.0/rest/guides/best-practices-for-integrators", + "/enterprise/v3/guides/best-practices-for-integrators": "/enterprise-server@latest/rest/guides/best-practices-for-integrators", + "/enterprise/2.20/rest/guides/best-practices-for-integrators": "/enterprise-server@2.20/rest/guides/best-practices-for-integrators", + "/enterprise-server@2.20/v3/guides/best-practices-for-integrators": "/enterprise-server@2.20/rest/guides/best-practices-for-integrators", + "/enterprise/2.20/v3/guides/best-practices-for-integrators": "/enterprise-server@2.20/rest/guides/best-practices-for-integrators", + "/github-ae@latest/v3/guides/best-practices-for-integrators": "/github-ae@latest/rest/guides/best-practices-for-integrators", + "/free-pro-team@latest/rest/guides/building-a-ci-server": "/rest/guides/building-a-ci-server", + "/v3/guides/building-a-ci-server": "/rest/guides/building-a-ci-server", + "/free-pro-team@latest/v3/guides/building-a-ci-server": "/rest/guides/building-a-ci-server", + "/enterprise/3.0/rest/guides/building-a-ci-server": "/enterprise-server@3.0/rest/guides/building-a-ci-server", + "/enterprise/rest/guides/building-a-ci-server": "/enterprise-server@latest/rest/guides/building-a-ci-server", + "/enterprise-server@3.0/v3/guides/building-a-ci-server": "/enterprise-server@3.0/rest/guides/building-a-ci-server", + "/enterprise/3.0/v3/guides/building-a-ci-server": "/enterprise-server@3.0/rest/guides/building-a-ci-server", + "/enterprise/v3/guides/building-a-ci-server": "/enterprise-server@latest/rest/guides/building-a-ci-server", + "/enterprise/2.20/rest/guides/building-a-ci-server": "/enterprise-server@2.20/rest/guides/building-a-ci-server", + "/enterprise-server@2.20/v3/guides/building-a-ci-server": "/enterprise-server@2.20/rest/guides/building-a-ci-server", + "/enterprise/2.20/v3/guides/building-a-ci-server": "/enterprise-server@2.20/rest/guides/building-a-ci-server", + "/github-ae@latest/v3/guides/building-a-ci-server": "/github-ae@latest/rest/guides/building-a-ci-server", + "/free-pro-team@latest/rest/guides/delivering-deployments": "/rest/guides/delivering-deployments", + "/v3/guides/delivering-deployments": "/rest/guides/delivering-deployments", + "/free-pro-team@latest/v3/guides/delivering-deployments": "/rest/guides/delivering-deployments", + "/enterprise/3.0/rest/guides/delivering-deployments": "/enterprise-server@3.0/rest/guides/delivering-deployments", + "/enterprise/rest/guides/delivering-deployments": "/enterprise-server@latest/rest/guides/delivering-deployments", + "/enterprise-server@3.0/v3/guides/delivering-deployments": "/enterprise-server@3.0/rest/guides/delivering-deployments", + "/enterprise/3.0/v3/guides/delivering-deployments": "/enterprise-server@3.0/rest/guides/delivering-deployments", + "/enterprise/v3/guides/delivering-deployments": "/enterprise-server@latest/rest/guides/delivering-deployments", + "/enterprise/2.20/rest/guides/delivering-deployments": "/enterprise-server@2.20/rest/guides/delivering-deployments", + "/enterprise-server@2.20/v3/guides/delivering-deployments": "/enterprise-server@2.20/rest/guides/delivering-deployments", + "/enterprise/2.20/v3/guides/delivering-deployments": "/enterprise-server@2.20/rest/guides/delivering-deployments", + "/github-ae@latest/v3/guides/delivering-deployments": "/github-ae@latest/rest/guides/delivering-deployments", + "/free-pro-team@latest/rest/guides/discovering-resources-for-a-user": "/rest/guides/discovering-resources-for-a-user", + "/v3/guides/discovering-resources-for-a-user": "/rest/guides/discovering-resources-for-a-user", + "/free-pro-team@latest/v3/guides/discovering-resources-for-a-user": "/rest/guides/discovering-resources-for-a-user", + "/enterprise/3.0/rest/guides/discovering-resources-for-a-user": "/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", + "/enterprise/rest/guides/discovering-resources-for-a-user": "/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", + "/enterprise-server@3.0/v3/guides/discovering-resources-for-a-user": "/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", + "/enterprise/3.0/v3/guides/discovering-resources-for-a-user": "/enterprise-server@3.0/rest/guides/discovering-resources-for-a-user", + "/enterprise/v3/guides/discovering-resources-for-a-user": "/enterprise-server@latest/rest/guides/discovering-resources-for-a-user", + "/enterprise/2.20/rest/guides/discovering-resources-for-a-user": "/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", + "/enterprise-server@2.20/v3/guides/discovering-resources-for-a-user": "/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", + "/enterprise/2.20/v3/guides/discovering-resources-for-a-user": "/enterprise-server@2.20/rest/guides/discovering-resources-for-a-user", + "/github-ae@latest/v3/guides/discovering-resources-for-a-user": "/github-ae@latest/rest/guides/discovering-resources-for-a-user", + "/free-pro-team@latest/rest/guides/getting-started-with-the-checks-api": "/rest/guides/getting-started-with-the-checks-api", + "/enterprise/3.0/rest/guides/getting-started-with-the-checks-api": "/enterprise-server@3.0/rest/guides/getting-started-with-the-checks-api", + "/enterprise/rest/guides/getting-started-with-the-checks-api": "/enterprise-server@latest/rest/guides/getting-started-with-the-checks-api", + "/enterprise/2.20/rest/guides/getting-started-with-the-checks-api": "/enterprise-server@2.20/rest/guides/getting-started-with-the-checks-api", + "/free-pro-team@latest/rest/guides/getting-started-with-the-git-database-api": "/rest/guides/getting-started-with-the-git-database-api", + "/enterprise/3.0/rest/guides/getting-started-with-the-git-database-api": "/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api", + "/enterprise/rest/guides/getting-started-with-the-git-database-api": "/enterprise-server@latest/rest/guides/getting-started-with-the-git-database-api", + "/enterprise/2.20/rest/guides/getting-started-with-the-git-database-api": "/enterprise-server@2.20/rest/guides/getting-started-with-the-git-database-api", + "/free-pro-team@latest/rest/guides/getting-started-with-the-rest-api": "/rest/guides/getting-started-with-the-rest-api", + "/v3/guides/getting-started": "/rest/guides/getting-started-with-the-rest-api", + "/free-pro-team@latest/v3/guides/getting-started": "/rest/guides/getting-started-with-the-rest-api", + "/enterprise/3.0/rest/guides/getting-started-with-the-rest-api": "/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", + "/enterprise/rest/guides/getting-started-with-the-rest-api": "/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", + "/enterprise-server@3.0/v3/guides/getting-started": "/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", + "/enterprise/3.0/v3/guides/getting-started": "/enterprise-server@3.0/rest/guides/getting-started-with-the-rest-api", + "/enterprise/v3/guides/getting-started": "/enterprise-server@latest/rest/guides/getting-started-with-the-rest-api", + "/enterprise/2.20/rest/guides/getting-started-with-the-rest-api": "/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", + "/enterprise-server@2.20/v3/guides/getting-started": "/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", + "/enterprise/2.20/v3/guides/getting-started": "/enterprise-server@2.20/rest/guides/getting-started-with-the-rest-api", + "/github-ae@latest/v3/guides/getting-started": "/github-ae@latest/rest/guides/getting-started-with-the-rest-api", + "/free-pro-team@latest/rest/guides": "/rest/guides", + "/v3/guides": "/rest/guides", + "/free-pro-team@latest/v3/guides": "/rest/guides", + "/enterprise/3.0/rest/guides": "/enterprise-server@3.0/rest/guides", + "/enterprise/rest/guides": "/enterprise-server@latest/rest/guides", + "/enterprise-server@3.0/v3/guides": "/enterprise-server@3.0/rest/guides", + "/enterprise/3.0/v3/guides": "/enterprise-server@3.0/rest/guides", + "/enterprise/v3/guides": "/enterprise-server@latest/rest/guides", + "/enterprise/2.20/rest/guides": "/enterprise-server@2.20/rest/guides", + "/enterprise-server@2.20/v3/guides": "/enterprise-server@2.20/rest/guides", + "/enterprise/2.20/v3/guides": "/enterprise-server@2.20/rest/guides", + "/github-ae@latest/v3/guides": "/github-ae@latest/rest/guides", + "/free-pro-team@latest/rest/guides/rendering-data-as-graphs": "/rest/guides/rendering-data-as-graphs", + "/v3/guides/rendering-data-as-graphs": "/rest/guides/rendering-data-as-graphs", + "/free-pro-team@latest/v3/guides/rendering-data-as-graphs": "/rest/guides/rendering-data-as-graphs", + "/enterprise/3.0/rest/guides/rendering-data-as-graphs": "/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", + "/enterprise/rest/guides/rendering-data-as-graphs": "/enterprise-server@latest/rest/guides/rendering-data-as-graphs", + "/enterprise-server@3.0/v3/guides/rendering-data-as-graphs": "/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", + "/enterprise/3.0/v3/guides/rendering-data-as-graphs": "/enterprise-server@3.0/rest/guides/rendering-data-as-graphs", + "/enterprise/v3/guides/rendering-data-as-graphs": "/enterprise-server@latest/rest/guides/rendering-data-as-graphs", + "/enterprise/2.20/rest/guides/rendering-data-as-graphs": "/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", + "/enterprise-server@2.20/v3/guides/rendering-data-as-graphs": "/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", + "/enterprise/2.20/v3/guides/rendering-data-as-graphs": "/enterprise-server@2.20/rest/guides/rendering-data-as-graphs", + "/github-ae@latest/v3/guides/rendering-data-as-graphs": "/github-ae@latest/rest/guides/rendering-data-as-graphs", + "/free-pro-team@latest/rest/guides/traversing-with-pagination": "/rest/guides/traversing-with-pagination", + "/v3/guides/traversing-with-pagination": "/rest/guides/traversing-with-pagination", + "/free-pro-team@latest/v3/guides/traversing-with-pagination": "/rest/guides/traversing-with-pagination", + "/enterprise/3.0/rest/guides/traversing-with-pagination": "/enterprise-server@3.0/rest/guides/traversing-with-pagination", + "/enterprise/rest/guides/traversing-with-pagination": "/enterprise-server@latest/rest/guides/traversing-with-pagination", + "/enterprise-server@3.0/v3/guides/traversing-with-pagination": "/enterprise-server@3.0/rest/guides/traversing-with-pagination", + "/enterprise/3.0/v3/guides/traversing-with-pagination": "/enterprise-server@3.0/rest/guides/traversing-with-pagination", + "/enterprise/v3/guides/traversing-with-pagination": "/enterprise-server@latest/rest/guides/traversing-with-pagination", + "/enterprise/2.20/rest/guides/traversing-with-pagination": "/enterprise-server@2.20/rest/guides/traversing-with-pagination", + "/enterprise-server@2.20/v3/guides/traversing-with-pagination": "/enterprise-server@2.20/rest/guides/traversing-with-pagination", + "/enterprise/2.20/v3/guides/traversing-with-pagination": "/enterprise-server@2.20/rest/guides/traversing-with-pagination", + "/github-ae@latest/v3/guides/traversing-with-pagination": "/github-ae@latest/rest/guides/traversing-with-pagination", + "/free-pro-team@latest/rest/guides/working-with-comments": "/rest/guides/working-with-comments", + "/v3/guides/working-with-comments": "/rest/guides/working-with-comments", + "/free-pro-team@latest/v3/guides/working-with-comments": "/rest/guides/working-with-comments", + "/enterprise/3.0/rest/guides/working-with-comments": "/enterprise-server@3.0/rest/guides/working-with-comments", + "/enterprise/rest/guides/working-with-comments": "/enterprise-server@latest/rest/guides/working-with-comments", + "/enterprise-server@3.0/v3/guides/working-with-comments": "/enterprise-server@3.0/rest/guides/working-with-comments", + "/enterprise/3.0/v3/guides/working-with-comments": "/enterprise-server@3.0/rest/guides/working-with-comments", + "/enterprise/v3/guides/working-with-comments": "/enterprise-server@latest/rest/guides/working-with-comments", + "/enterprise/2.20/rest/guides/working-with-comments": "/enterprise-server@2.20/rest/guides/working-with-comments", + "/enterprise-server@2.20/v3/guides/working-with-comments": "/enterprise-server@2.20/rest/guides/working-with-comments", + "/enterprise/2.20/v3/guides/working-with-comments": "/enterprise-server@2.20/rest/guides/working-with-comments", + "/github-ae@latest/v3/guides/working-with-comments": "/github-ae@latest/rest/guides/working-with-comments", + "/free-pro-team@latest/rest": "/rest", + "/v3": "/rest", + "/free-pro-team@latest/v3": "/rest", + "/enterprise/3.0/rest": "/enterprise-server@3.0/rest", + "/enterprise/rest": "/enterprise-server@latest/rest", + "/enterprise-server@3.0/v3": "/enterprise-server@3.0/rest", + "/enterprise/3.0/v3": "/enterprise-server@3.0/rest", + "/enterprise/v3": "/enterprise-server@latest/rest", + "/enterprise/2.20/rest": "/enterprise-server@2.20/rest", + "/enterprise-server@2.20/v3": "/enterprise-server@2.20/rest", + "/enterprise/2.20/v3": "/enterprise-server@2.20/rest", + "/github-ae@latest/v3": "/github-ae@latest/rest", + "/free-pro-team@latest/rest/overview/api-previews": "/rest/overview/api-previews", + "/v3/previews": "/rest/overview/api-previews", + "/free-pro-team@latest/v3/previews": "/rest/overview/api-previews", + "/enterprise/3.0/rest/overview/api-previews": "/enterprise-server@3.0/rest/overview/api-previews", + "/enterprise/rest/overview/api-previews": "/enterprise-server@latest/rest/overview/api-previews", + "/enterprise-server@3.0/v3/previews": "/enterprise-server@3.0/rest/overview/api-previews", + "/enterprise/3.0/v3/previews": "/enterprise-server@3.0/rest/overview/api-previews", + "/enterprise/v3/previews": "/enterprise-server@latest/rest/overview/api-previews", + "/enterprise/2.20/rest/overview/api-previews": "/enterprise-server@2.20/rest/overview/api-previews", + "/enterprise-server@2.20/v3/previews": "/enterprise-server@2.20/rest/overview/api-previews", + "/enterprise/2.20/v3/previews": "/enterprise-server@2.20/rest/overview/api-previews", + "/github-ae@latest/v3/previews": "/github-ae@latest/rest/overview/api-previews", + "/free-pro-team@latest/rest/overview/endpoints-available-for-github-apps": "/rest/overview/endpoints-available-for-github-apps", + "/v3/apps/available-endpoints": "/rest/overview/endpoints-available-for-github-apps", + "/free-pro-team@latest/v3/apps/available-endpoints": "/rest/overview/endpoints-available-for-github-apps", + "/rest/reference/endpoints-available-for-github-apps": "/rest/overview/endpoints-available-for-github-apps", + "/free-pro-team@latest/rest/reference/endpoints-available-for-github-apps": "/rest/overview/endpoints-available-for-github-apps", + "/enterprise/3.0/rest/overview/endpoints-available-for-github-apps": "/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", + "/enterprise/rest/overview/endpoints-available-for-github-apps": "/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", + "/enterprise-server@3.0/v3/apps/available-endpoints": "/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", + "/enterprise/3.0/v3/apps/available-endpoints": "/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", + "/enterprise/v3/apps/available-endpoints": "/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", + "/enterprise-server@3.0/rest/reference/endpoints-available-for-github-apps": "/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", + "/enterprise/3.0/rest/reference/endpoints-available-for-github-apps": "/enterprise-server@3.0/rest/overview/endpoints-available-for-github-apps", + "/enterprise/rest/reference/endpoints-available-for-github-apps": "/enterprise-server@latest/rest/overview/endpoints-available-for-github-apps", + "/enterprise/2.20/rest/overview/endpoints-available-for-github-apps": "/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", + "/enterprise-server@2.20/v3/apps/available-endpoints": "/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", + "/enterprise/2.20/v3/apps/available-endpoints": "/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", + "/enterprise-server@2.20/rest/reference/endpoints-available-for-github-apps": "/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", + "/enterprise/2.20/rest/reference/endpoints-available-for-github-apps": "/enterprise-server@2.20/rest/overview/endpoints-available-for-github-apps", + "/github-ae@latest/v3/apps/available-endpoints": "/github-ae@latest/rest/overview/endpoints-available-for-github-apps", + "/github-ae@latest/rest/reference/endpoints-available-for-github-apps": "/github-ae@latest/rest/overview/endpoints-available-for-github-apps", + "/free-pro-team@latest/rest/overview": "/rest/overview", + "/enterprise/3.0/rest/overview": "/enterprise-server@3.0/rest/overview", + "/enterprise/rest/overview": "/enterprise-server@latest/rest/overview", + "/enterprise/2.20/rest/overview": "/enterprise-server@2.20/rest/overview", + "/free-pro-team@latest/rest/overview/libraries": "/rest/overview/libraries", + "/v3/libraries": "/rest/overview/libraries", + "/free-pro-team@latest/v3/libraries": "/rest/overview/libraries", + "/enterprise/3.0/rest/overview/libraries": "/enterprise-server@3.0/rest/overview/libraries", + "/enterprise/rest/overview/libraries": "/enterprise-server@latest/rest/overview/libraries", + "/enterprise-server@3.0/v3/libraries": "/enterprise-server@3.0/rest/overview/libraries", + "/enterprise/3.0/v3/libraries": "/enterprise-server@3.0/rest/overview/libraries", + "/enterprise/v3/libraries": "/enterprise-server@latest/rest/overview/libraries", + "/enterprise/2.20/rest/overview/libraries": "/enterprise-server@2.20/rest/overview/libraries", + "/enterprise-server@2.20/v3/libraries": "/enterprise-server@2.20/rest/overview/libraries", + "/enterprise/2.20/v3/libraries": "/enterprise-server@2.20/rest/overview/libraries", + "/github-ae@latest/v3/libraries": "/github-ae@latest/rest/overview/libraries", + "/free-pro-team@latest/rest/overview/media-types": "/rest/overview/media-types", + "/v3/media": "/rest/overview/media-types", + "/free-pro-team@latest/v3/media": "/rest/overview/media-types", + "/enterprise/3.0/rest/overview/media-types": "/enterprise-server@3.0/rest/overview/media-types", + "/enterprise/rest/overview/media-types": "/enterprise-server@latest/rest/overview/media-types", + "/enterprise-server@3.0/v3/media": "/enterprise-server@3.0/rest/overview/media-types", + "/enterprise/3.0/v3/media": "/enterprise-server@3.0/rest/overview/media-types", + "/enterprise/v3/media": "/enterprise-server@latest/rest/overview/media-types", + "/enterprise/2.20/rest/overview/media-types": "/enterprise-server@2.20/rest/overview/media-types", + "/enterprise-server@2.20/v3/media": "/enterprise-server@2.20/rest/overview/media-types", + "/enterprise/2.20/v3/media": "/enterprise-server@2.20/rest/overview/media-types", + "/github-ae@latest/v3/media": "/github-ae@latest/rest/overview/media-types", + "/free-pro-team@latest/rest/overview/openapi-description": "/rest/overview/openapi-description", + "/enterprise/3.0/rest/overview/openapi-description": "/enterprise-server@3.0/rest/overview/openapi-description", + "/enterprise/rest/overview/openapi-description": "/enterprise-server@latest/rest/overview/openapi-description", + "/enterprise/2.20/rest/overview/openapi-description": "/enterprise-server@2.20/rest/overview/openapi-description", + "/free-pro-team@latest/rest/overview/other-authentication-methods": "/rest/overview/other-authentication-methods", + "/v3/auth": "/rest/overview/other-authentication-methods", + "/free-pro-team@latest/v3/auth": "/rest/overview/other-authentication-methods", + "/enterprise/3.0/rest/overview/other-authentication-methods": "/enterprise-server@3.0/rest/overview/other-authentication-methods", + "/enterprise/rest/overview/other-authentication-methods": "/enterprise-server@latest/rest/overview/other-authentication-methods", + "/enterprise-server@3.0/v3/auth": "/enterprise-server@3.0/rest/overview/other-authentication-methods", + "/enterprise/3.0/v3/auth": "/enterprise-server@3.0/rest/overview/other-authentication-methods", + "/enterprise/v3/auth": "/enterprise-server@latest/rest/overview/other-authentication-methods", + "/enterprise/2.20/rest/overview/other-authentication-methods": "/enterprise-server@2.20/rest/overview/other-authentication-methods", + "/enterprise-server@2.20/v3/auth": "/enterprise-server@2.20/rest/overview/other-authentication-methods", + "/enterprise/2.20/v3/auth": "/enterprise-server@2.20/rest/overview/other-authentication-methods", + "/github-ae@latest/v3/auth": "/github-ae@latest/rest/overview/other-authentication-methods", + "/free-pro-team@latest/rest/overview/resources-in-the-rest-api": "/rest/overview/resources-in-the-rest-api", + "/rest/initialize-the-repo": "/rest/overview/resources-in-the-rest-api", + "/free-pro-team@latest/rest/initialize-the-repo": "/rest/overview/resources-in-the-rest-api", + "/enterprise/3.0/rest/overview/resources-in-the-rest-api": "/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", + "/enterprise/rest/overview/resources-in-the-rest-api": "/enterprise-server@latest/rest/overview/resources-in-the-rest-api", + "/enterprise-server@3.0/rest/initialize-the-repo": "/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", + "/enterprise/3.0/rest/initialize-the-repo": "/enterprise-server@3.0/rest/overview/resources-in-the-rest-api", + "/enterprise/rest/initialize-the-repo": "/enterprise-server@latest/rest/overview/resources-in-the-rest-api", + "/enterprise/2.20/rest/overview/resources-in-the-rest-api": "/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", + "/enterprise-server@2.20/rest/initialize-the-repo": "/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", + "/enterprise/2.20/rest/initialize-the-repo": "/enterprise-server@2.20/rest/overview/resources-in-the-rest-api", + "/github-ae@latest/rest/initialize-the-repo": "/github-ae@latest/rest/overview/resources-in-the-rest-api", + "/free-pro-team@latest/rest/overview/troubleshooting": "/rest/overview/troubleshooting", + "/v3/troubleshooting": "/rest/overview/troubleshooting", + "/free-pro-team@latest/v3/troubleshooting": "/rest/overview/troubleshooting", + "/enterprise/3.0/rest/overview/troubleshooting": "/enterprise-server@3.0/rest/overview/troubleshooting", + "/enterprise/rest/overview/troubleshooting": "/enterprise-server@latest/rest/overview/troubleshooting", + "/enterprise-server@3.0/v3/troubleshooting": "/enterprise-server@3.0/rest/overview/troubleshooting", + "/enterprise/3.0/v3/troubleshooting": "/enterprise-server@3.0/rest/overview/troubleshooting", + "/enterprise/v3/troubleshooting": "/enterprise-server@latest/rest/overview/troubleshooting", + "/enterprise/2.20/rest/overview/troubleshooting": "/enterprise-server@2.20/rest/overview/troubleshooting", + "/enterprise-server@2.20/v3/troubleshooting": "/enterprise-server@2.20/rest/overview/troubleshooting", + "/enterprise/2.20/v3/troubleshooting": "/enterprise-server@2.20/rest/overview/troubleshooting", + "/github-ae@latest/v3/troubleshooting": "/github-ae@latest/rest/overview/troubleshooting", + "/free-pro-team@latest/rest/reference/actions": "/rest/reference/actions", + "/v3/actions": "/rest/reference/actions", + "/free-pro-team@latest/v3/actions": "/rest/reference/actions", + "/enterprise/3.0/rest/reference/actions": "/enterprise-server@3.0/rest/reference/actions", + "/enterprise/rest/reference/actions": "/enterprise-server@latest/rest/reference/actions", + "/enterprise-server@3.0/v3/actions": "/enterprise-server@3.0/rest/reference/actions", + "/enterprise/3.0/v3/actions": "/enterprise-server@3.0/rest/reference/actions", + "/enterprise/v3/actions": "/enterprise-server@latest/rest/reference/actions", + "/free-pro-team@latest/rest/reference/activity": "/rest/reference/activity", + "/v3/activity": "/rest/reference/activity", + "/free-pro-team@latest/v3/activity": "/rest/reference/activity", + "/enterprise/3.0/rest/reference/activity": "/enterprise-server@3.0/rest/reference/activity", + "/enterprise/rest/reference/activity": "/enterprise-server@latest/rest/reference/activity", + "/enterprise-server@3.0/v3/activity": "/enterprise-server@3.0/rest/reference/activity", + "/enterprise/3.0/v3/activity": "/enterprise-server@3.0/rest/reference/activity", + "/enterprise/v3/activity": "/enterprise-server@latest/rest/reference/activity", + "/enterprise/2.20/rest/reference/activity": "/enterprise-server@2.20/rest/reference/activity", + "/enterprise-server@2.20/v3/activity": "/enterprise-server@2.20/rest/reference/activity", + "/enterprise/2.20/v3/activity": "/enterprise-server@2.20/rest/reference/activity", + "/github-ae@latest/v3/activity": "/github-ae@latest/rest/reference/activity", + "/free-pro-team@latest/rest/reference/apps": "/rest/reference/apps", + "/v3/apps": "/rest/reference/apps", + "/free-pro-team@latest/v3/apps": "/rest/reference/apps", + "/enterprise/3.0/rest/reference/apps": "/enterprise-server@3.0/rest/reference/apps", + "/enterprise/rest/reference/apps": "/enterprise-server@latest/rest/reference/apps", + "/enterprise-server@3.0/v3/apps": "/enterprise-server@3.0/rest/reference/apps", + "/enterprise/3.0/v3/apps": "/enterprise-server@3.0/rest/reference/apps", + "/enterprise/v3/apps": "/enterprise-server@latest/rest/reference/apps", + "/enterprise/2.20/rest/reference/apps": "/enterprise-server@2.20/rest/reference/apps", + "/enterprise-server@2.20/v3/apps": "/enterprise-server@2.20/rest/reference/apps", + "/enterprise/2.20/v3/apps": "/enterprise-server@2.20/rest/reference/apps", + "/github-ae@latest/v3/apps": "/github-ae@latest/rest/reference/apps", + "/free-pro-team@latest/rest/reference/billing": "/rest/reference/billing", + "/free-pro-team@latest/rest/reference/checks": "/rest/reference/checks", + "/v3/checks": "/rest/reference/checks", + "/free-pro-team@latest/v3/checks": "/rest/reference/checks", + "/enterprise/3.0/rest/reference/checks": "/enterprise-server@3.0/rest/reference/checks", + "/enterprise/rest/reference/checks": "/enterprise-server@latest/rest/reference/checks", + "/enterprise-server@3.0/v3/checks": "/enterprise-server@3.0/rest/reference/checks", + "/enterprise/3.0/v3/checks": "/enterprise-server@3.0/rest/reference/checks", + "/enterprise/v3/checks": "/enterprise-server@latest/rest/reference/checks", + "/enterprise/2.20/rest/reference/checks": "/enterprise-server@2.20/rest/reference/checks", + "/enterprise-server@2.20/v3/checks": "/enterprise-server@2.20/rest/reference/checks", + "/enterprise/2.20/v3/checks": "/enterprise-server@2.20/rest/reference/checks", + "/github-ae@latest/v3/checks": "/github-ae@latest/rest/reference/checks", + "/free-pro-team@latest/rest/reference/code-scanning": "/rest/reference/code-scanning", + "/v3/code-scanning": "/rest/reference/code-scanning", + "/free-pro-team@latest/v3/code-scanning": "/rest/reference/code-scanning", + "/enterprise/3.0/rest/reference/code-scanning": "/enterprise-server@3.0/rest/reference/code-scanning", + "/enterprise/rest/reference/code-scanning": "/enterprise-server@latest/rest/reference/code-scanning", + "/enterprise-server@3.0/v3/code-scanning": "/enterprise-server@3.0/rest/reference/code-scanning", + "/enterprise/3.0/v3/code-scanning": "/enterprise-server@3.0/rest/reference/code-scanning", + "/enterprise/v3/code-scanning": "/enterprise-server@latest/rest/reference/code-scanning", + "/free-pro-team@latest/rest/reference/codes-of-conduct": "/rest/reference/codes-of-conduct", + "/v3/codes_of_conduct": "/rest/reference/codes-of-conduct", + "/free-pro-team@latest/v3/codes_of_conduct": "/rest/reference/codes-of-conduct", + "/v3/codes-of-conduct": "/rest/reference/codes-of-conduct", + "/free-pro-team@latest/v3/codes-of-conduct": "/rest/reference/codes-of-conduct", + "/enterprise/3.0/rest/reference/codes-of-conduct": "/enterprise-server@3.0/rest/reference/codes-of-conduct", + "/enterprise/rest/reference/codes-of-conduct": "/enterprise-server@latest/rest/reference/codes-of-conduct", + "/enterprise-server@3.0/v3/codes_of_conduct": "/enterprise-server@3.0/rest/reference/codes-of-conduct", + "/enterprise/3.0/v3/codes_of_conduct": "/enterprise-server@3.0/rest/reference/codes-of-conduct", + "/enterprise/v3/codes_of_conduct": "/enterprise-server@latest/rest/reference/codes-of-conduct", + "/enterprise-server@3.0/v3/codes-of-conduct": "/enterprise-server@3.0/rest/reference/codes-of-conduct", + "/enterprise/3.0/v3/codes-of-conduct": "/enterprise-server@3.0/rest/reference/codes-of-conduct", + "/enterprise/v3/codes-of-conduct": "/enterprise-server@latest/rest/reference/codes-of-conduct", + "/enterprise/2.20/rest/reference/codes-of-conduct": "/enterprise-server@2.20/rest/reference/codes-of-conduct", + "/enterprise-server@2.20/v3/codes_of_conduct": "/enterprise-server@2.20/rest/reference/codes-of-conduct", + "/enterprise/2.20/v3/codes_of_conduct": "/enterprise-server@2.20/rest/reference/codes-of-conduct", + "/enterprise-server@2.20/v3/codes-of-conduct": "/enterprise-server@2.20/rest/reference/codes-of-conduct", + "/enterprise/2.20/v3/codes-of-conduct": "/enterprise-server@2.20/rest/reference/codes-of-conduct", + "/github-ae@latest/v3/codes_of_conduct": "/github-ae@latest/rest/reference/codes-of-conduct", + "/github-ae@latest/v3/codes-of-conduct": "/github-ae@latest/rest/reference/codes-of-conduct", + "/free-pro-team@latest/rest/reference/emojis": "/rest/reference/emojis", + "/v3/emojis": "/rest/reference/emojis", + "/free-pro-team@latest/v3/emojis": "/rest/reference/emojis", + "/v3/misc": "/rest/reference/emojis", + "/free-pro-team@latest/v3/misc": "/rest/reference/emojis", + "/enterprise/3.0/rest/reference/emojis": "/enterprise-server@3.0/rest/reference/emojis", + "/enterprise/rest/reference/emojis": "/enterprise-server@latest/rest/reference/emojis", + "/enterprise-server@3.0/v3/emojis": "/enterprise-server@3.0/rest/reference/emojis", + "/enterprise/3.0/v3/emojis": "/enterprise-server@3.0/rest/reference/emojis", + "/enterprise/v3/emojis": "/enterprise-server@latest/rest/reference/emojis", + "/enterprise-server@3.0/v3/misc": "/enterprise-server@3.0/rest/reference/emojis", + "/enterprise/3.0/v3/misc": "/enterprise-server@3.0/rest/reference/emojis", + "/enterprise/v3/misc": "/enterprise-server@latest/rest/reference/emojis", + "/enterprise/2.20/rest/reference/emojis": "/enterprise-server@2.20/rest/reference/emojis", + "/enterprise-server@2.20/v3/emojis": "/enterprise-server@2.20/rest/reference/emojis", + "/enterprise/2.20/v3/emojis": "/enterprise-server@2.20/rest/reference/emojis", + "/enterprise-server@2.20/v3/misc": "/enterprise-server@2.20/rest/reference/emojis", + "/enterprise/2.20/v3/misc": "/enterprise-server@2.20/rest/reference/emojis", + "/github-ae@latest/v3/emojis": "/github-ae@latest/rest/reference/emojis", + "/github-ae@latest/v3/misc": "/github-ae@latest/rest/reference/emojis", + "/free-pro-team@latest/rest/reference/enterprise-admin": "/rest/reference/enterprise-admin", + "/v3/enterprise-admin": "/rest/reference/enterprise-admin", + "/free-pro-team@latest/v3/enterprise-admin": "/rest/reference/enterprise-admin", + "/v3/enterprise": "/rest/reference/enterprise-admin", + "/free-pro-team@latest/v3/enterprise": "/rest/reference/enterprise-admin", + "/enterprise/3.0/rest/reference/enterprise-admin": "/enterprise-server@3.0/rest/reference/enterprise-admin", + "/enterprise/rest/reference/enterprise-admin": "/enterprise-server@latest/rest/reference/enterprise-admin", + "/enterprise-server@3.0/v3/enterprise-admin": "/enterprise-server@3.0/rest/reference/enterprise-admin", + "/enterprise/3.0/v3/enterprise-admin": "/enterprise-server@3.0/rest/reference/enterprise-admin", + "/enterprise/v3/enterprise-admin": "/enterprise-server@latest/rest/reference/enterprise-admin", + "/enterprise-server@3.0/v3/enterprise": "/enterprise-server@3.0/rest/reference/enterprise-admin", + "/enterprise/3.0/v3/enterprise": "/enterprise-server@3.0/rest/reference/enterprise-admin", + "/enterprise/v3/enterprise": "/enterprise-server@latest/rest/reference/enterprise-admin", + "/enterprise/2.20/rest/reference/enterprise-admin": "/enterprise-server@2.20/rest/reference/enterprise-admin", + "/enterprise-server@2.20/v3/enterprise-admin": "/enterprise-server@2.20/rest/reference/enterprise-admin", + "/enterprise/2.20/v3/enterprise-admin": "/enterprise-server@2.20/rest/reference/enterprise-admin", + "/enterprise-server@2.20/v3/enterprise": "/enterprise-server@2.20/rest/reference/enterprise-admin", + "/enterprise/2.20/v3/enterprise": "/enterprise-server@2.20/rest/reference/enterprise-admin", + "/github-ae@latest/v3/enterprise-admin": "/github-ae@latest/rest/reference/enterprise-admin", + "/github-ae@latest/v3/enterprise": "/github-ae@latest/rest/reference/enterprise-admin", + "/free-pro-team@latest/rest/reference/gists": "/rest/reference/gists", + "/v3/gists": "/rest/reference/gists", + "/free-pro-team@latest/v3/gists": "/rest/reference/gists", + "/enterprise/3.0/rest/reference/gists": "/enterprise-server@3.0/rest/reference/gists", + "/enterprise/rest/reference/gists": "/enterprise-server@latest/rest/reference/gists", + "/enterprise-server@3.0/v3/gists": "/enterprise-server@3.0/rest/reference/gists", + "/enterprise/3.0/v3/gists": "/enterprise-server@3.0/rest/reference/gists", + "/enterprise/v3/gists": "/enterprise-server@latest/rest/reference/gists", + "/enterprise/2.20/rest/reference/gists": "/enterprise-server@2.20/rest/reference/gists", + "/enterprise-server@2.20/v3/gists": "/enterprise-server@2.20/rest/reference/gists", + "/enterprise/2.20/v3/gists": "/enterprise-server@2.20/rest/reference/gists", + "/github-ae@latest/v3/gists": "/github-ae@latest/rest/reference/gists", + "/free-pro-team@latest/rest/reference/git": "/rest/reference/git", + "/v3/git": "/rest/reference/git", + "/free-pro-team@latest/v3/git": "/rest/reference/git", + "/enterprise/3.0/rest/reference/git": "/enterprise-server@3.0/rest/reference/git", + "/enterprise/rest/reference/git": "/enterprise-server@latest/rest/reference/git", + "/enterprise-server@3.0/v3/git": "/enterprise-server@3.0/rest/reference/git", + "/enterprise/3.0/v3/git": "/enterprise-server@3.0/rest/reference/git", + "/enterprise/v3/git": "/enterprise-server@latest/rest/reference/git", + "/enterprise/2.20/rest/reference/git": "/enterprise-server@2.20/rest/reference/git", + "/enterprise-server@2.20/v3/git": "/enterprise-server@2.20/rest/reference/git", + "/enterprise/2.20/v3/git": "/enterprise-server@2.20/rest/reference/git", + "/github-ae@latest/v3/git": "/github-ae@latest/rest/reference/git", + "/free-pro-team@latest/rest/reference/gitignore": "/rest/reference/gitignore", + "/v3/gitignore": "/rest/reference/gitignore", + "/free-pro-team@latest/v3/gitignore": "/rest/reference/gitignore", + "/enterprise/3.0/rest/reference/gitignore": "/enterprise-server@3.0/rest/reference/gitignore", + "/enterprise/rest/reference/gitignore": "/enterprise-server@latest/rest/reference/gitignore", + "/enterprise-server@3.0/v3/gitignore": "/enterprise-server@3.0/rest/reference/gitignore", + "/enterprise/3.0/v3/gitignore": "/enterprise-server@3.0/rest/reference/gitignore", + "/enterprise/v3/gitignore": "/enterprise-server@latest/rest/reference/gitignore", + "/enterprise/2.20/rest/reference/gitignore": "/enterprise-server@2.20/rest/reference/gitignore", + "/enterprise-server@2.20/v3/gitignore": "/enterprise-server@2.20/rest/reference/gitignore", + "/enterprise/2.20/v3/gitignore": "/enterprise-server@2.20/rest/reference/gitignore", + "/github-ae@latest/v3/gitignore": "/github-ae@latest/rest/reference/gitignore", + "/free-pro-team@latest/rest/reference": "/rest/reference", + "/enterprise/3.0/rest/reference": "/enterprise-server@3.0/rest/reference", + "/enterprise/rest/reference": "/enterprise-server@latest/rest/reference", + "/enterprise/2.20/rest/reference": "/enterprise-server@2.20/rest/reference", + "/free-pro-team@latest/rest/reference/interactions": "/rest/reference/interactions", + "/v3/interactions": "/rest/reference/interactions", + "/free-pro-team@latest/v3/interactions": "/rest/reference/interactions", + "/free-pro-team@latest/rest/reference/issues": "/rest/reference/issues", + "/v3/issues": "/rest/reference/issues", + "/free-pro-team@latest/v3/issues": "/rest/reference/issues", + "/enterprise/3.0/rest/reference/issues": "/enterprise-server@3.0/rest/reference/issues", + "/enterprise/rest/reference/issues": "/enterprise-server@latest/rest/reference/issues", + "/enterprise-server@3.0/v3/issues": "/enterprise-server@3.0/rest/reference/issues", + "/enterprise/3.0/v3/issues": "/enterprise-server@3.0/rest/reference/issues", + "/enterprise/v3/issues": "/enterprise-server@latest/rest/reference/issues", + "/enterprise/2.20/rest/reference/issues": "/enterprise-server@2.20/rest/reference/issues", + "/enterprise-server@2.20/v3/issues": "/enterprise-server@2.20/rest/reference/issues", + "/enterprise/2.20/v3/issues": "/enterprise-server@2.20/rest/reference/issues", + "/github-ae@latest/v3/issues": "/github-ae@latest/rest/reference/issues", + "/free-pro-team@latest/rest/reference/licenses": "/rest/reference/licenses", + "/v3/licenses": "/rest/reference/licenses", + "/free-pro-team@latest/v3/licenses": "/rest/reference/licenses", + "/enterprise/3.0/rest/reference/licenses": "/enterprise-server@3.0/rest/reference/licenses", + "/enterprise/rest/reference/licenses": "/enterprise-server@latest/rest/reference/licenses", + "/enterprise-server@3.0/v3/licenses": "/enterprise-server@3.0/rest/reference/licenses", + "/enterprise/3.0/v3/licenses": "/enterprise-server@3.0/rest/reference/licenses", + "/enterprise/v3/licenses": "/enterprise-server@latest/rest/reference/licenses", + "/enterprise/2.20/rest/reference/licenses": "/enterprise-server@2.20/rest/reference/licenses", + "/enterprise-server@2.20/v3/licenses": "/enterprise-server@2.20/rest/reference/licenses", + "/enterprise/2.20/v3/licenses": "/enterprise-server@2.20/rest/reference/licenses", + "/github-ae@latest/v3/licenses": "/github-ae@latest/rest/reference/licenses", + "/free-pro-team@latest/rest/reference/markdown": "/rest/reference/markdown", + "/v3/markdown": "/rest/reference/markdown", + "/free-pro-team@latest/v3/markdown": "/rest/reference/markdown", + "/enterprise/3.0/rest/reference/markdown": "/enterprise-server@3.0/rest/reference/markdown", + "/enterprise/rest/reference/markdown": "/enterprise-server@latest/rest/reference/markdown", + "/enterprise-server@3.0/v3/markdown": "/enterprise-server@3.0/rest/reference/markdown", + "/enterprise/3.0/v3/markdown": "/enterprise-server@3.0/rest/reference/markdown", + "/enterprise/v3/markdown": "/enterprise-server@latest/rest/reference/markdown", + "/enterprise/2.20/rest/reference/markdown": "/enterprise-server@2.20/rest/reference/markdown", + "/enterprise-server@2.20/v3/markdown": "/enterprise-server@2.20/rest/reference/markdown", + "/enterprise/2.20/v3/markdown": "/enterprise-server@2.20/rest/reference/markdown", + "/github-ae@latest/v3/markdown": "/github-ae@latest/rest/reference/markdown", + "/free-pro-team@latest/rest/reference/meta": "/rest/reference/meta", + "/v3/meta": "/rest/reference/meta", + "/free-pro-team@latest/v3/meta": "/rest/reference/meta", + "/enterprise/3.0/rest/reference/meta": "/enterprise-server@3.0/rest/reference/meta", + "/enterprise/rest/reference/meta": "/enterprise-server@latest/rest/reference/meta", + "/enterprise-server@3.0/v3/meta": "/enterprise-server@3.0/rest/reference/meta", + "/enterprise/3.0/v3/meta": "/enterprise-server@3.0/rest/reference/meta", + "/enterprise/v3/meta": "/enterprise-server@latest/rest/reference/meta", + "/enterprise/2.20/rest/reference/meta": "/enterprise-server@2.20/rest/reference/meta", + "/enterprise-server@2.20/v3/meta": "/enterprise-server@2.20/rest/reference/meta", + "/enterprise/2.20/v3/meta": "/enterprise-server@2.20/rest/reference/meta", + "/github-ae@latest/v3/meta": "/github-ae@latest/rest/reference/meta", + "/free-pro-team@latest/rest/reference/migrations": "/rest/reference/migrations", + "/v3/migrations": "/rest/reference/migrations", + "/free-pro-team@latest/v3/migrations": "/rest/reference/migrations", + "/v3/migration": "/rest/reference/migrations", + "/free-pro-team@latest/v3/migration": "/rest/reference/migrations", + "/v3/migration/migrations": "/rest/reference/migrations", + "/free-pro-team@latest/v3/migration/migrations": "/rest/reference/migrations", + "/enterprise/3.0/rest/reference/oauth-authorizations": "/enterprise-server@3.0/rest/reference/oauth-authorizations", + "/enterprise/rest/reference/oauth-authorizations": "/enterprise-server@latest/rest/reference/oauth-authorizations", + "/enterprise-server@3.0/v3/oauth_authorizations": "/enterprise-server@3.0/rest/reference/oauth-authorizations", + "/enterprise/3.0/v3/oauth_authorizations": "/enterprise-server@3.0/rest/reference/oauth-authorizations", + "/enterprise/v3/oauth_authorizations": "/enterprise-server@latest/rest/reference/oauth-authorizations", + "/enterprise-server@3.0/v3/oauth-authorizations": "/enterprise-server@3.0/rest/reference/oauth-authorizations", + "/enterprise/3.0/v3/oauth-authorizations": "/enterprise-server@3.0/rest/reference/oauth-authorizations", + "/enterprise/v3/oauth-authorizations": "/enterprise-server@latest/rest/reference/oauth-authorizations", + "/enterprise/2.20/rest/reference/oauth-authorizations": "/enterprise-server@2.20/rest/reference/oauth-authorizations", + "/enterprise-server@2.20/v3/oauth_authorizations": "/enterprise-server@2.20/rest/reference/oauth-authorizations", + "/enterprise/2.20/v3/oauth_authorizations": "/enterprise-server@2.20/rest/reference/oauth-authorizations", + "/enterprise-server@2.20/v3/oauth-authorizations": "/enterprise-server@2.20/rest/reference/oauth-authorizations", + "/enterprise/2.20/v3/oauth-authorizations": "/enterprise-server@2.20/rest/reference/oauth-authorizations", + "/free-pro-team@latest/rest/reference/orgs": "/rest/reference/orgs", + "/v3/orgs": "/rest/reference/orgs", + "/free-pro-team@latest/v3/orgs": "/rest/reference/orgs", + "/enterprise/3.0/rest/reference/orgs": "/enterprise-server@3.0/rest/reference/orgs", + "/enterprise/rest/reference/orgs": "/enterprise-server@latest/rest/reference/orgs", + "/enterprise-server@3.0/v3/orgs": "/enterprise-server@3.0/rest/reference/orgs", + "/enterprise/3.0/v3/orgs": "/enterprise-server@3.0/rest/reference/orgs", + "/enterprise/v3/orgs": "/enterprise-server@latest/rest/reference/orgs", + "/enterprise/2.20/rest/reference/orgs": "/enterprise-server@2.20/rest/reference/orgs", + "/enterprise-server@2.20/v3/orgs": "/enterprise-server@2.20/rest/reference/orgs", + "/enterprise/2.20/v3/orgs": "/enterprise-server@2.20/rest/reference/orgs", + "/github-ae@latest/v3/orgs": "/github-ae@latest/rest/reference/orgs", + "/free-pro-team@latest/rest/reference/permissions-required-for-github-apps": "/rest/reference/permissions-required-for-github-apps", + "/v3/apps/permissions": "/rest/reference/permissions-required-for-github-apps", + "/free-pro-team@latest/v3/apps/permissions": "/rest/reference/permissions-required-for-github-apps", + "/enterprise/3.0/rest/reference/permissions-required-for-github-apps": "/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", + "/enterprise/rest/reference/permissions-required-for-github-apps": "/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", + "/enterprise-server@3.0/v3/apps/permissions": "/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", + "/enterprise/3.0/v3/apps/permissions": "/enterprise-server@3.0/rest/reference/permissions-required-for-github-apps", + "/enterprise/v3/apps/permissions": "/enterprise-server@latest/rest/reference/permissions-required-for-github-apps", + "/enterprise/2.20/rest/reference/permissions-required-for-github-apps": "/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", + "/enterprise-server@2.20/v3/apps/permissions": "/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", + "/enterprise/2.20/v3/apps/permissions": "/enterprise-server@2.20/rest/reference/permissions-required-for-github-apps", + "/github-ae@latest/v3/apps/permissions": "/github-ae@latest/rest/reference/permissions-required-for-github-apps", + "/free-pro-team@latest/rest/reference/projects": "/rest/reference/projects", + "/v3/projects": "/rest/reference/projects", + "/free-pro-team@latest/v3/projects": "/rest/reference/projects", + "/enterprise/3.0/rest/reference/projects": "/enterprise-server@3.0/rest/reference/projects", + "/enterprise/rest/reference/projects": "/enterprise-server@latest/rest/reference/projects", + "/enterprise-server@3.0/v3/projects": "/enterprise-server@3.0/rest/reference/projects", + "/enterprise/3.0/v3/projects": "/enterprise-server@3.0/rest/reference/projects", + "/enterprise/v3/projects": "/enterprise-server@latest/rest/reference/projects", + "/enterprise/2.20/rest/reference/projects": "/enterprise-server@2.20/rest/reference/projects", + "/enterprise-server@2.20/v3/projects": "/enterprise-server@2.20/rest/reference/projects", + "/enterprise/2.20/v3/projects": "/enterprise-server@2.20/rest/reference/projects", + "/github-ae@latest/v3/projects": "/github-ae@latest/rest/reference/projects", + "/free-pro-team@latest/rest/reference/pulls": "/rest/reference/pulls", + "/v3/pulls": "/rest/reference/pulls", + "/free-pro-team@latest/v3/pulls": "/rest/reference/pulls", + "/enterprise/3.0/rest/reference/pulls": "/enterprise-server@3.0/rest/reference/pulls", + "/enterprise/rest/reference/pulls": "/enterprise-server@latest/rest/reference/pulls", + "/enterprise-server@3.0/v3/pulls": "/enterprise-server@3.0/rest/reference/pulls", + "/enterprise/3.0/v3/pulls": "/enterprise-server@3.0/rest/reference/pulls", + "/enterprise/v3/pulls": "/enterprise-server@latest/rest/reference/pulls", + "/enterprise/2.20/rest/reference/pulls": "/enterprise-server@2.20/rest/reference/pulls", + "/enterprise-server@2.20/v3/pulls": "/enterprise-server@2.20/rest/reference/pulls", + "/enterprise/2.20/v3/pulls": "/enterprise-server@2.20/rest/reference/pulls", + "/github-ae@latest/v3/pulls": "/github-ae@latest/rest/reference/pulls", + "/free-pro-team@latest/rest/reference/rate-limit": "/rest/reference/rate-limit", + "/v3/rate_limit": "/rest/reference/rate-limit", + "/free-pro-team@latest/v3/rate_limit": "/rest/reference/rate-limit", + "/v3/rate-limit": "/rest/reference/rate-limit", + "/free-pro-team@latest/v3/rate-limit": "/rest/reference/rate-limit", + "/enterprise/3.0/rest/reference/rate-limit": "/enterprise-server@3.0/rest/reference/rate-limit", + "/enterprise/rest/reference/rate-limit": "/enterprise-server@latest/rest/reference/rate-limit", + "/enterprise-server@3.0/v3/rate_limit": "/enterprise-server@3.0/rest/reference/rate-limit", + "/enterprise/3.0/v3/rate_limit": "/enterprise-server@3.0/rest/reference/rate-limit", + "/enterprise/v3/rate_limit": "/enterprise-server@latest/rest/reference/rate-limit", + "/enterprise-server@3.0/v3/rate-limit": "/enterprise-server@3.0/rest/reference/rate-limit", + "/enterprise/3.0/v3/rate-limit": "/enterprise-server@3.0/rest/reference/rate-limit", + "/enterprise/v3/rate-limit": "/enterprise-server@latest/rest/reference/rate-limit", + "/enterprise/2.20/rest/reference/rate-limit": "/enterprise-server@2.20/rest/reference/rate-limit", + "/enterprise-server@2.20/v3/rate_limit": "/enterprise-server@2.20/rest/reference/rate-limit", + "/enterprise/2.20/v3/rate_limit": "/enterprise-server@2.20/rest/reference/rate-limit", + "/enterprise-server@2.20/v3/rate-limit": "/enterprise-server@2.20/rest/reference/rate-limit", + "/enterprise/2.20/v3/rate-limit": "/enterprise-server@2.20/rest/reference/rate-limit", + "/github-ae@latest/v3/rate_limit": "/github-ae@latest/rest/reference/rate-limit", + "/github-ae@latest/v3/rate-limit": "/github-ae@latest/rest/reference/rate-limit", + "/free-pro-team@latest/rest/reference/reactions": "/rest/reference/reactions", + "/v3/reactions": "/rest/reference/reactions", + "/free-pro-team@latest/v3/reactions": "/rest/reference/reactions", + "/enterprise/3.0/rest/reference/reactions": "/enterprise-server@3.0/rest/reference/reactions", + "/enterprise/rest/reference/reactions": "/enterprise-server@latest/rest/reference/reactions", + "/enterprise-server@3.0/v3/reactions": "/enterprise-server@3.0/rest/reference/reactions", + "/enterprise/3.0/v3/reactions": "/enterprise-server@3.0/rest/reference/reactions", + "/enterprise/v3/reactions": "/enterprise-server@latest/rest/reference/reactions", + "/enterprise/2.20/rest/reference/reactions": "/enterprise-server@2.20/rest/reference/reactions", + "/enterprise-server@2.20/v3/reactions": "/enterprise-server@2.20/rest/reference/reactions", + "/enterprise/2.20/v3/reactions": "/enterprise-server@2.20/rest/reference/reactions", + "/github-ae@latest/v3/reactions": "/github-ae@latest/rest/reference/reactions", + "/free-pro-team@latest/rest/reference/repos": "/rest/reference/repos", + "/v3/repos": "/rest/reference/repos", + "/free-pro-team@latest/v3/repos": "/rest/reference/repos", + "/enterprise/3.0/rest/reference/repos": "/enterprise-server@3.0/rest/reference/repos", + "/enterprise/rest/reference/repos": "/enterprise-server@latest/rest/reference/repos", + "/enterprise-server@3.0/v3/repos": "/enterprise-server@3.0/rest/reference/repos", + "/enterprise/3.0/v3/repos": "/enterprise-server@3.0/rest/reference/repos", + "/enterprise/v3/repos": "/enterprise-server@latest/rest/reference/repos", + "/enterprise/2.20/rest/reference/repos": "/enterprise-server@2.20/rest/reference/repos", + "/enterprise-server@2.20/v3/repos": "/enterprise-server@2.20/rest/reference/repos", + "/enterprise/2.20/v3/repos": "/enterprise-server@2.20/rest/reference/repos", + "/github-ae@latest/v3/repos": "/github-ae@latest/rest/reference/repos", + "/free-pro-team@latest/rest/reference/scim": "/rest/reference/scim", + "/v3/scim": "/rest/reference/scim", + "/free-pro-team@latest/v3/scim": "/rest/reference/scim", + "/free-pro-team@latest/rest/reference/search": "/rest/reference/search", + "/v3/search": "/rest/reference/search", + "/free-pro-team@latest/v3/search": "/rest/reference/search", + "/enterprise/3.0/rest/reference/search": "/enterprise-server@3.0/rest/reference/search", + "/enterprise/rest/reference/search": "/enterprise-server@latest/rest/reference/search", + "/enterprise-server@3.0/v3/search": "/enterprise-server@3.0/rest/reference/search", + "/enterprise/3.0/v3/search": "/enterprise-server@3.0/rest/reference/search", + "/enterprise/v3/search": "/enterprise-server@latest/rest/reference/search", + "/enterprise/2.20/rest/reference/search": "/enterprise-server@2.20/rest/reference/search", + "/enterprise-server@2.20/v3/search": "/enterprise-server@2.20/rest/reference/search", + "/enterprise/2.20/v3/search": "/enterprise-server@2.20/rest/reference/search", + "/github-ae@latest/v3/search": "/github-ae@latest/rest/reference/search", + "/free-pro-team@latest/rest/reference/secret-scanning": "/rest/reference/secret-scanning", + "/free-pro-team@latest/rest/reference/teams": "/rest/reference/teams", + "/v3/teams": "/rest/reference/teams", + "/free-pro-team@latest/v3/teams": "/rest/reference/teams", + "/enterprise/3.0/rest/reference/teams": "/enterprise-server@3.0/rest/reference/teams", + "/enterprise/rest/reference/teams": "/enterprise-server@latest/rest/reference/teams", + "/enterprise-server@3.0/v3/teams": "/enterprise-server@3.0/rest/reference/teams", + "/enterprise/3.0/v3/teams": "/enterprise-server@3.0/rest/reference/teams", + "/enterprise/v3/teams": "/enterprise-server@latest/rest/reference/teams", + "/enterprise/2.20/rest/reference/teams": "/enterprise-server@2.20/rest/reference/teams", + "/enterprise-server@2.20/v3/teams": "/enterprise-server@2.20/rest/reference/teams", + "/enterprise/2.20/v3/teams": "/enterprise-server@2.20/rest/reference/teams", + "/github-ae@latest/v3/teams": "/github-ae@latest/rest/reference/teams", + "/free-pro-team@latest/rest/reference/users": "/rest/reference/users", + "/v3/users": "/rest/reference/users", + "/free-pro-team@latest/v3/users": "/rest/reference/users", + "/enterprise/3.0/rest/reference/users": "/enterprise-server@3.0/rest/reference/users", + "/enterprise/rest/reference/users": "/enterprise-server@latest/rest/reference/users", + "/enterprise-server@3.0/v3/users": "/enterprise-server@3.0/rest/reference/users", + "/enterprise/3.0/v3/users": "/enterprise-server@3.0/rest/reference/users", + "/enterprise/v3/users": "/enterprise-server@latest/rest/reference/users", + "/enterprise/2.20/rest/reference/users": "/enterprise-server@2.20/rest/reference/users", + "/enterprise-server@2.20/v3/users": "/enterprise-server@2.20/rest/reference/users", + "/enterprise/2.20/v3/users": "/enterprise-server@2.20/rest/reference/users", + "/github-ae@latest/v3/users": "/github-ae@latest/rest/reference/users", + "/enterprise/2.20/v3/activity/events": "/enterprise-server@2.20/rest/reference/activity#events", + "/enterprise/2.20/v3/activity/feeds": "/enterprise-server@2.20/rest/reference/activity#feeds", + "/enterprise/2.20/v3/activity/notifications": "/enterprise-server@2.20/rest/reference/activity#notifications", + "/enterprise/2.20/v3/activity/starring": "/enterprise-server@2.20/rest/reference/activity#starring", + "/enterprise/2.20/v3/activity/watching": "/enterprise-server@2.20/rest/reference/activity#watching", + "/enterprise/2.20/v3/apps/installations": "/enterprise-server@2.20/rest/reference/apps#installations", + "/enterprise/2.20/v3/apps/oauth_applications": "/enterprise-server@2.20/rest/reference/apps#oauth-applications", + "/enterprise/2.20/v3/checks/runs": "/enterprise-server@2.20/rest/reference/checks#runs", + "/enterprise/2.20/v3/checks/suites": "/enterprise-server@2.20/rest/reference/checks#suites", + "/enterprise/2.20/v3/enterprise-admin/admin_stats": "/enterprise-server@2.20/rest/reference/enterprise-admin#admin-stats", + "/enterprise/2.20/v3/enterprise-admin/global_webhooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#global-webhooks", + "/enterprise/2.20/v3/enterprise-admin/ldap": "/enterprise-server@2.20/rest/reference/enterprise-admin#ldap", + "/enterprise/2.20/v3/enterprise-admin/license": "/enterprise-server@2.20/rest/reference/enterprise-admin#license", + "/enterprise/2.20/v3/enterprise-admin/management_console": "/enterprise-server@2.20/rest/reference/enterprise-admin#management-console", + "/enterprise/2.20/v3/enterprise-admin/org_pre_receive_hooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#organization-pre-receive-hooks", + "/enterprise/2.20/v3/enterprise-admin/orgs": "/enterprise-server@2.20/rest/reference/enterprise-admin#orgs", + "/enterprise/2.20/v3/enterprise-admin/pre_receive_environments": "/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-environments", + "/enterprise/2.20/v3/enterprise-admin/pre_receive_hooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-hooks", + "/enterprise/2.20/v3/enterprise-admin/repo_pre_receive_hooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#repository-pre-receive-hooks", + "/enterprise/2.20/v3/enterprise-admin/search_indexing": "/enterprise-server@2.20/rest/reference/enterprise-admin#search-indexing", + "/enterprise/2.20/v3/enterprise-admin/users": "/enterprise-server@2.20/rest/reference/enterprise-admin#users", + "/enterprise/2.20/v3/enterprise/admin_stats": "/enterprise-server@2.20/rest/reference/enterprise-admin#admin-stats", + "/enterprise/2.20/v3/enterprise/ldap": "/enterprise-server@2.20/rest/reference/enterprise-admin#ldap", + "/enterprise/2.20/v3/enterprise/license": "/enterprise-server@2.20/rest/reference/enterprise-admin#license", + "/enterprise/2.20/v3/enterprise/management_console": "/enterprise-server@2.20/rest/reference/enterprise-admin#management-console", + "/enterprise/2.20/v3/enterprise/orgs": "/enterprise-server@2.20/rest/reference/enterprise-admin#orgs", + "/enterprise/2.20/v3/enterprise/pre_receive_environments": "/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-environments", + "/enterprise/2.20/v3/enterprise/pre_receive_hooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#pre-receive-hooks", + "/enterprise/2.20/v3/enterprise/search_indexing": "/enterprise-server@2.20/rest/reference/enterprise-admin#search-indexing", + "/enterprise/2.20/v3/gists/comments": "/enterprise-server@2.20/rest/reference/gists#comments", + "/enterprise/2.20/v3/git/blobs": "/enterprise-server@2.20/rest/reference/git#blobs", + "/enterprise/2.20/v3/git/commits": "/enterprise-server@2.20/rest/reference/git#commits", + "/enterprise/2.20/v3/git/refs": "/enterprise-server@2.20/rest/reference/git#refs", + "/enterprise/2.20/v3/git/tags": "/enterprise-server@2.20/rest/reference/git#tags", + "/enterprise/2.20/v3/git/trees": "/enterprise-server@2.20/rest/reference/git#trees", + "/enterprise/2.20/v3/integrations/installations": "/enterprise-server@2.20/developers/apps#installations", + "/enterprise/2.20/v3/issues/assignees": "/enterprise-server@2.20/rest/reference/issues#assignees", + "/enterprise/2.20/v3/issues/comments": "/enterprise-server@2.20/rest/reference/issues#comments", + "/enterprise/2.20/v3/issues/events": "/enterprise-server@2.20/rest/reference/issues#events", + "/enterprise/2.20/v3/issues/labels": "/enterprise-server@2.20/rest/reference/issues#labels", + "/enterprise/2.20/v3/issues/milestones": "/enterprise-server@2.20/rest/reference/issues#milestones", + "/enterprise/2.20/v3/issues/timeline": "/enterprise-server@2.20/rest/reference/issues#timeline", + "/enterprise/2.20/v3/orgs/hooks": "/enterprise-server@2.20/rest/reference/orgs#webhooks", + "/enterprise/2.20/v3/orgs/members": "/enterprise-server@2.20/rest/reference/orgs#members", + "/enterprise/2.20/v3/orgs/outside_collaborators": "/enterprise-server@2.20/rest/reference/orgs#outside-collaborators", + "/enterprise/2.20/v3/orgs/pre_receive_hooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#organization-pre-receive-hooks", + "/enterprise/2.20/v3/orgs/teams": "/enterprise-server@2.20/rest/reference/orgs#teams", + "/enterprise/2.20/v3/projects/cards": "/enterprise-server@2.20/rest/reference/projects#cards", + "/enterprise/2.20/v3/projects/collaborators": "/enterprise-server@2.20/rest/reference/projects#collaborators", + "/enterprise/2.20/v3/projects/columns": "/enterprise-server@2.20/rest/reference/projects#columns", + "/enterprise/2.20/v3/pulls/comments": "/enterprise-server@2.20/rest/reference/pulls#comments", + "/enterprise/2.20/v3/pulls/review_requests": "/enterprise-server@2.20/rest/reference/pulls#review-requests", + "/enterprise/2.20/v3/pulls/reviews": "/enterprise-server@2.20/rest/reference/pulls#reviews", + "/enterprise/2.20/v3/repos/branches": "/enterprise-server@2.20/rest/reference/repos#branches", + "/enterprise/2.20/v3/repos/collaborators": "/enterprise-server@2.20/rest/reference/repos#collaborators", + "/enterprise/2.20/v3/repos/comments": "/enterprise-server@2.20/rest/reference/repos#comments", + "/enterprise/2.20/v3/repos/commits": "/enterprise-server@2.20/rest/reference/repos#commits", + "/enterprise/2.20/v3/repos/contents": "/enterprise-server@2.20/rest/reference/repos#contents", + "/enterprise/2.20/v3/repos/deployments": "/enterprise-server@2.20/rest/reference/repos#deployments", + "/enterprise/2.20/v3/repos/downloads": "/enterprise-server@2.20/rest/reference/repos#downloads", + "/enterprise/2.20/v3/repos/forks": "/enterprise-server@2.20/rest/reference/repos#forks", + "/enterprise/2.20/v3/repos/hooks": "/enterprise-server@2.20/rest/reference/repos#webhooks", + "/enterprise/2.20/v3/repos/invitations": "/enterprise-server@2.20/rest/reference/repos#invitations", + "/enterprise/2.20/v3/repos/keys": "/enterprise-server@2.20/rest/reference/repos#keys", + "/enterprise/2.20/v3/repos/merging": "/enterprise-server@2.20/rest/reference/repos#merging", + "/enterprise/2.20/v3/repos/pages": "/enterprise-server@2.20/rest/reference/repos#pages", + "/enterprise/2.20/v3/repos/pre_receive_hooks": "/enterprise-server@2.20/rest/reference/enterprise-admin#repository-pre-receive-hooks", + "/enterprise/2.20/v3/repos/releases": "/enterprise-server@2.20/rest/reference/repos#releases", + "/enterprise/2.20/v3/repos/statistics": "/enterprise-server@2.20/rest/reference/repos#statistics", + "/enterprise/2.20/v3/repos/statuses": "/enterprise-server@2.20/rest/reference/repos#statuses", + "/enterprise/2.20/v3/teams/discussion_comments": "/enterprise-server@2.20/rest/reference/teams#discussion-comments", + "/enterprise/2.20/v3/teams/discussions": "/enterprise-server@2.20/rest/reference/teams#discussions", + "/enterprise/2.20/v3/teams/members": "/enterprise-server@2.20/rest/reference/teams#members", + "/enterprise/2.20/v3/users/administration": "/enterprise-server@2.20/rest/reference/users#administration", + "/enterprise/2.20/v3/users/emails": "/enterprise-server@2.20/rest/reference/users#emails", + "/enterprise/2.20/v3/users/followers": "/enterprise-server@2.20/rest/reference/users#followers", + "/enterprise/2.20/v3/users/gpg_keys": "/enterprise-server@2.20/rest/reference/users#gpg-keys", + "/enterprise/2.20/v3/users/keys": "/enterprise-server@2.20/rest/reference/users#keys", + "/enterprise/2.20/v4/enum/__directivelocation": "/enterprise-server@2.20/graphql/reference/enums#__directivelocation", + "/enterprise/2.20/v4/enum/__typekind": "/enterprise-server@2.20/graphql/reference/enums#__typekind", + "/enterprise/2.20/v4/enum/actionexecutioncapabilitysetting": "/enterprise-server@2.20/graphql/reference/enums#actionexecutioncapabilitysetting", + "/enterprise/2.20/v4/enum/auditlogorderfield": "/enterprise-server@2.20/graphql/reference/enums#auditlogorderfield", + "/enterprise/2.20/v4/enum/checkannotationlevel": "/enterprise-server@2.20/graphql/reference/enums#checkannotationlevel", + "/enterprise/2.20/v4/enum/checkconclusionstate": "/enterprise-server@2.20/graphql/reference/enums#checkconclusionstate", + "/enterprise/2.20/v4/enum/checkruntype": "/enterprise-server@2.20/graphql/reference/enums#checkruntype", + "/enterprise/2.20/v4/enum/checkstatusstate": "/enterprise-server@2.20/graphql/reference/enums#checkstatusstate", + "/enterprise/2.20/v4/enum/collaboratoraffiliation": "/enterprise-server@2.20/graphql/reference/enums#collaboratoraffiliation", + "/enterprise/2.20/v4/enum/commentauthorassociation": "/enterprise-server@2.20/graphql/reference/enums#commentauthorassociation", + "/enterprise/2.20/v4/enum/commentcannotupdatereason": "/enterprise-server@2.20/graphql/reference/enums#commentcannotupdatereason", + "/enterprise/2.20/v4/enum/commitcontributionorderfield": "/enterprise-server@2.20/graphql/reference/enums#commitcontributionorderfield", + "/enterprise/2.20/v4/enum/contributionorderfield": "/enterprise-server@2.20/graphql/reference/enums#contributionorderfield", + "/enterprise/2.20/v4/enum/defaultrepositorypermissionfield": "/enterprise-server@2.20/graphql/reference/enums#defaultrepositorypermissionfield", + "/enterprise/2.20/v4/enum/deploymentorderfield": "/enterprise-server@2.20/graphql/reference/enums#deploymentorderfield", + "/enterprise/2.20/v4/enum/deploymentstate": "/enterprise-server@2.20/graphql/reference/enums#deploymentstate", + "/enterprise/2.20/v4/enum/deploymentstatusstate": "/enterprise-server@2.20/graphql/reference/enums#deploymentstatusstate", + "/enterprise/2.20/v4/enum/diffside": "/enterprise-server@2.20/graphql/reference/enums#diffside", + "/enterprise/2.20/v4/enum/enterpriseadministratorinvitationorderfield": "/enterprise-server@2.20/graphql/reference/enums#enterpriseadministratorinvitationorderfield", + "/enterprise/2.20/v4/enum/enterpriseadministratorrole": "/enterprise-server@2.20/graphql/reference/enums#enterpriseadministratorrole", + "/enterprise/2.20/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/enterprise-server@2.20/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", + "/enterprise/2.20/v4/enum/enterpriseenableddisabledsettingvalue": "/enterprise-server@2.20/graphql/reference/enums#enterpriseenableddisabledsettingvalue", + "/enterprise/2.20/v4/enum/enterpriseenabledsettingvalue": "/enterprise-server@2.20/graphql/reference/enums#enterpriseenabledsettingvalue", + "/enterprise/2.20/v4/enum/enterprisememberorderfield": "/enterprise-server@2.20/graphql/reference/enums#enterprisememberorderfield", + "/enterprise/2.20/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/enterprise-server@2.20/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", + "/enterprise/2.20/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/enterprise-server@2.20/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", + "/enterprise/2.20/v4/enum/enterpriseserveruseraccountemailorderfield": "/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", + "/enterprise/2.20/v4/enum/enterpriseserveruseraccountorderfield": "/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountorderfield", + "/enterprise/2.20/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", + "/enterprise/2.20/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/enterprise-server@2.20/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", + "/enterprise/2.20/v4/enum/enterpriseuseraccountmembershiprole": "/enterprise-server@2.20/graphql/reference/enums#enterpriseuseraccountmembershiprole", + "/enterprise/2.20/v4/enum/enterpriseuserdeployment": "/enterprise-server@2.20/graphql/reference/enums#enterpriseuserdeployment", + "/enterprise/2.20/v4/enum/gistorderfield": "/enterprise-server@2.20/graphql/reference/enums#gistorderfield", + "/enterprise/2.20/v4/enum/gistprivacy": "/enterprise-server@2.20/graphql/reference/enums#gistprivacy", + "/enterprise/2.20/v4/enum/gitsignaturestate": "/enterprise-server@2.20/graphql/reference/enums#gitsignaturestate", + "/enterprise/2.20/v4/enum/identityproviderconfigurationstate": "/enterprise-server@2.20/graphql/reference/enums#identityproviderconfigurationstate", + "/enterprise/2.20/v4/enum/issueorderfield": "/enterprise-server@2.20/graphql/reference/enums#issueorderfield", + "/enterprise/2.20/v4/enum/issuestate": "/enterprise-server@2.20/graphql/reference/enums#issuestate", + "/enterprise/2.20/v4/enum/issuetimelineitemsitemtype": "/enterprise-server@2.20/graphql/reference/enums#issuetimelineitemsitemtype", + "/enterprise/2.20/v4/enum/labelorderfield": "/enterprise-server@2.20/graphql/reference/enums#labelorderfield", + "/enterprise/2.20/v4/enum/languageorderfield": "/enterprise-server@2.20/graphql/reference/enums#languageorderfield", + "/enterprise/2.20/v4/enum/lockreason": "/enterprise-server@2.20/graphql/reference/enums#lockreason", + "/enterprise/2.20/v4/enum/mergeablestate": "/enterprise-server@2.20/graphql/reference/enums#mergeablestate", + "/enterprise/2.20/v4/enum/mergestatestatus": "/enterprise-server@2.20/graphql/reference/enums#mergestatestatus", + "/enterprise/2.20/v4/enum/milestoneorderfield": "/enterprise-server@2.20/graphql/reference/enums#milestoneorderfield", + "/enterprise/2.20/v4/enum/milestonestate": "/enterprise-server@2.20/graphql/reference/enums#milestonestate", + "/enterprise/2.20/v4/enum/oauthapplicationcreateauditentrystate": "/enterprise-server@2.20/graphql/reference/enums#oauthapplicationcreateauditentrystate", + "/enterprise/2.20/v4/enum/operationtype": "/enterprise-server@2.20/graphql/reference/enums#operationtype", + "/enterprise/2.20/v4/enum/orderdirection": "/enterprise-server@2.20/graphql/reference/enums#orderdirection", + "/enterprise/2.20/v4/enum/orgaddmemberauditentrypermission": "/enterprise-server@2.20/graphql/reference/enums#orgaddmemberauditentrypermission", + "/enterprise/2.20/v4/enum/organizationinvitationrole": "/enterprise-server@2.20/graphql/reference/enums#organizationinvitationrole", + "/enterprise/2.20/v4/enum/organizationinvitationtype": "/enterprise-server@2.20/graphql/reference/enums#organizationinvitationtype", + "/enterprise/2.20/v4/enum/organizationmemberrole": "/enterprise-server@2.20/graphql/reference/enums#organizationmemberrole", + "/enterprise/2.20/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/enterprise-server@2.20/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", + "/enterprise/2.20/v4/enum/organizationorderfield": "/enterprise-server@2.20/graphql/reference/enums#organizationorderfield", + "/enterprise/2.20/v4/enum/orgcreateauditentrybillingplan": "/enterprise-server@2.20/graphql/reference/enums#orgcreateauditentrybillingplan", + "/enterprise/2.20/v4/enum/orgremovebillingmanagerauditentryreason": "/enterprise-server@2.20/graphql/reference/enums#orgremovebillingmanagerauditentryreason", + "/enterprise/2.20/v4/enum/orgremovememberauditentrymembershiptype": "/enterprise-server@2.20/graphql/reference/enums#orgremovememberauditentrymembershiptype", + "/enterprise/2.20/v4/enum/orgremovememberauditentryreason": "/enterprise-server@2.20/graphql/reference/enums#orgremovememberauditentryreason", + "/enterprise/2.20/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/enterprise-server@2.20/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", + "/enterprise/2.20/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/enterprise-server@2.20/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", + "/enterprise/2.20/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/enterprise-server@2.20/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", + "/enterprise/2.20/v4/enum/orgupdatememberauditentrypermission": "/enterprise-server@2.20/graphql/reference/enums#orgupdatememberauditentrypermission", + "/enterprise/2.20/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", + "/enterprise/2.20/v4/enum/packagefileorderfield": "/enterprise-server@2.20/graphql/reference/enums#packagefileorderfield", + "/enterprise/2.20/v4/enum/packageorderfield": "/enterprise-server@2.20/graphql/reference/enums#packageorderfield", + "/enterprise/2.20/v4/enum/packageversionorderfield": "/enterprise-server@2.20/graphql/reference/enums#packageversionorderfield", + "/enterprise/2.20/v4/enum/pinnableitemtype": "/enterprise-server@2.20/graphql/reference/enums#pinnableitemtype", + "/enterprise/2.20/v4/enum/projectcardarchivedstate": "/enterprise-server@2.20/graphql/reference/enums#projectcardarchivedstate", + "/enterprise/2.20/v4/enum/projectcardstate": "/enterprise-server@2.20/graphql/reference/enums#projectcardstate", + "/enterprise/2.20/v4/enum/projectcolumnpurpose": "/enterprise-server@2.20/graphql/reference/enums#projectcolumnpurpose", + "/enterprise/2.20/v4/enum/projectorderfield": "/enterprise-server@2.20/graphql/reference/enums#projectorderfield", + "/enterprise/2.20/v4/enum/projectstate": "/enterprise-server@2.20/graphql/reference/enums#projectstate", + "/enterprise/2.20/v4/enum/projecttemplate": "/enterprise-server@2.20/graphql/reference/enums#projecttemplate", + "/enterprise/2.20/v4/enum/pullrequestmergemethod": "/enterprise-server@2.20/graphql/reference/enums#pullrequestmergemethod", + "/enterprise/2.20/v4/enum/pullrequestorderfield": "/enterprise-server@2.20/graphql/reference/enums#pullrequestorderfield", + "/enterprise/2.20/v4/enum/pullrequestreviewcommentstate": "/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewcommentstate", + "/enterprise/2.20/v4/enum/pullrequestreviewevent": "/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewevent", + "/enterprise/2.20/v4/enum/pullrequestreviewstate": "/enterprise-server@2.20/graphql/reference/enums#pullrequestreviewstate", + "/enterprise/2.20/v4/enum/pullrequeststate": "/enterprise-server@2.20/graphql/reference/enums#pullrequeststate", + "/enterprise/2.20/v4/enum/pullrequesttimelineitemsitemtype": "/enterprise-server@2.20/graphql/reference/enums#pullrequesttimelineitemsitemtype", + "/enterprise/2.20/v4/enum/pullrequestupdatestate": "/enterprise-server@2.20/graphql/reference/enums#pullrequestupdatestate", + "/enterprise/2.20/v4/enum/reactioncontent": "/enterprise-server@2.20/graphql/reference/enums#reactioncontent", + "/enterprise/2.20/v4/enum/reactionorderfield": "/enterprise-server@2.20/graphql/reference/enums#reactionorderfield", + "/enterprise/2.20/v4/enum/reforderfield": "/enterprise-server@2.20/graphql/reference/enums#reforderfield", + "/enterprise/2.20/v4/enum/registrypackagedependencytype": "/enterprise-server@2.20/graphql/reference/enums#registrypackagedependencytype", + "/enterprise/2.20/v4/enum/registrypackagetype": "/enterprise-server@2.20/graphql/reference/enums#registrypackagetype", + "/enterprise/2.20/v4/enum/releaseorderfield": "/enterprise-server@2.20/graphql/reference/enums#releaseorderfield", + "/enterprise/2.20/v4/enum/repoaccessauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#repoaccessauditentryvisibility", + "/enterprise/2.20/v4/enum/repoaddmemberauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#repoaddmemberauditentryvisibility", + "/enterprise/2.20/v4/enum/repoarchivedauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#repoarchivedauditentryvisibility", + "/enterprise/2.20/v4/enum/repochangemergesettingauditentrymergetype": "/enterprise-server@2.20/graphql/reference/enums#repochangemergesettingauditentrymergetype", + "/enterprise/2.20/v4/enum/repocreateauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#repocreateauditentryvisibility", + "/enterprise/2.20/v4/enum/repodestroyauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#repodestroyauditentryvisibility", + "/enterprise/2.20/v4/enum/reporemovememberauditentryvisibility": "/enterprise-server@2.20/graphql/reference/enums#reporemovememberauditentryvisibility", + "/enterprise/2.20/v4/enum/reportedcontentclassifiers": "/enterprise-server@2.20/graphql/reference/enums#reportedcontentclassifiers", + "/enterprise/2.20/v4/enum/repositoryaffiliation": "/enterprise-server@2.20/graphql/reference/enums#repositoryaffiliation", + "/enterprise/2.20/v4/enum/repositorycontributiontype": "/enterprise-server@2.20/graphql/reference/enums#repositorycontributiontype", + "/enterprise/2.20/v4/enum/repositoryinvitationorderfield": "/enterprise-server@2.20/graphql/reference/enums#repositoryinvitationorderfield", + "/enterprise/2.20/v4/enum/repositorylockreason": "/enterprise-server@2.20/graphql/reference/enums#repositorylockreason", + "/enterprise/2.20/v4/enum/repositoryorderfield": "/enterprise-server@2.20/graphql/reference/enums#repositoryorderfield", + "/enterprise/2.20/v4/enum/repositorypermission": "/enterprise-server@2.20/graphql/reference/enums#repositorypermission", + "/enterprise/2.20/v4/enum/repositoryprivacy": "/enterprise-server@2.20/graphql/reference/enums#repositoryprivacy", + "/enterprise/2.20/v4/enum/repositoryvisibility": "/enterprise-server@2.20/graphql/reference/enums#repositoryvisibility", + "/enterprise/2.20/v4/enum/requestablecheckstatusstate": "/enterprise-server@2.20/graphql/reference/enums#requestablecheckstatusstate", + "/enterprise/2.20/v4/enum/samldigestalgorithm": "/enterprise-server@2.20/graphql/reference/enums#samldigestalgorithm", + "/enterprise/2.20/v4/enum/samlsignaturealgorithm": "/enterprise-server@2.20/graphql/reference/enums#samlsignaturealgorithm", + "/enterprise/2.20/v4/enum/savedreplyorderfield": "/enterprise-server@2.20/graphql/reference/enums#savedreplyorderfield", + "/enterprise/2.20/v4/enum/searchtype": "/enterprise-server@2.20/graphql/reference/enums#searchtype", + "/enterprise/2.20/v4/enum/securityadvisoryecosystem": "/enterprise-server@2.20/graphql/reference/enums#securityadvisoryecosystem", + "/enterprise/2.20/v4/enum/securityadvisoryseverity": "/enterprise-server@2.20/graphql/reference/enums#securityadvisoryseverity", + "/enterprise/2.20/v4/enum/sponsorshipprivacy": "/enterprise-server@2.20/graphql/reference/enums#sponsorshipprivacy", + "/enterprise/2.20/v4/enum/starorderfield": "/enterprise-server@2.20/graphql/reference/enums#starorderfield", + "/enterprise/2.20/v4/enum/statusstate": "/enterprise-server@2.20/graphql/reference/enums#statusstate", + "/enterprise/2.20/v4/enum/subscriptionstate": "/enterprise-server@2.20/graphql/reference/enums#subscriptionstate", + "/enterprise/2.20/v4/enum/teamdiscussioncommentorderfield": "/enterprise-server@2.20/graphql/reference/enums#teamdiscussioncommentorderfield", + "/enterprise/2.20/v4/enum/teamdiscussionorderfield": "/enterprise-server@2.20/graphql/reference/enums#teamdiscussionorderfield", + "/enterprise/2.20/v4/enum/teammemberorderfield": "/enterprise-server@2.20/graphql/reference/enums#teammemberorderfield", + "/enterprise/2.20/v4/enum/teammemberrole": "/enterprise-server@2.20/graphql/reference/enums#teammemberrole", + "/enterprise/2.20/v4/enum/teammembershiptype": "/enterprise-server@2.20/graphql/reference/enums#teammembershiptype", + "/enterprise/2.20/v4/enum/teamorderfield": "/enterprise-server@2.20/graphql/reference/enums#teamorderfield", + "/enterprise/2.20/v4/enum/teamprivacy": "/enterprise-server@2.20/graphql/reference/enums#teamprivacy", + "/enterprise/2.20/v4/enum/teamrepositoryorderfield": "/enterprise-server@2.20/graphql/reference/enums#teamrepositoryorderfield", + "/enterprise/2.20/v4/enum/teamreviewassignmentalgorithm": "/enterprise-server@2.20/graphql/reference/enums#teamreviewassignmentalgorithm", + "/enterprise/2.20/v4/enum/teamrole": "/enterprise-server@2.20/graphql/reference/enums#teamrole", + "/enterprise/2.20/v4/enum/userblockduration": "/enterprise-server@2.20/graphql/reference/enums#userblockduration", + "/enterprise/2.20/v4/enum/userstatusorderfield": "/enterprise-server@2.20/graphql/reference/enums#userstatusorderfield", + "/enterprise/2.20/v4/input_object/addassigneestoassignableinput": "/enterprise-server@2.20/graphql/reference/input-objects#addassigneestoassignableinput", + "/enterprise/2.20/v4/input_object/addcommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#addcommentinput", + "/enterprise/2.20/v4/input_object/addenterpriseadmininput": "/enterprise-server@2.20/graphql/reference/input-objects#addenterpriseadmininput", + "/enterprise/2.20/v4/input_object/addlabelstolabelableinput": "/enterprise-server@2.20/graphql/reference/input-objects#addlabelstolabelableinput", + "/enterprise/2.20/v4/input_object/addprojectcardinput": "/enterprise-server@2.20/graphql/reference/input-objects#addprojectcardinput", + "/enterprise/2.20/v4/input_object/addprojectcolumninput": "/enterprise-server@2.20/graphql/reference/input-objects#addprojectcolumninput", + "/enterprise/2.20/v4/input_object/addpullrequestreviewcommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewcommentinput", + "/enterprise/2.20/v4/input_object/addpullrequestreviewinput": "/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewinput", + "/enterprise/2.20/v4/input_object/addpullrequestreviewthreadinput": "/enterprise-server@2.20/graphql/reference/input-objects#addpullrequestreviewthreadinput", + "/enterprise/2.20/v4/input_object/addreactioninput": "/enterprise-server@2.20/graphql/reference/input-objects#addreactioninput", + "/enterprise/2.20/v4/input_object/addstarinput": "/enterprise-server@2.20/graphql/reference/input-objects#addstarinput", + "/enterprise/2.20/v4/input_object/archiverepositoryinput": "/enterprise-server@2.20/graphql/reference/input-objects#archiverepositoryinput", + "/enterprise/2.20/v4/input_object/auditlogorder": "/enterprise-server@2.20/graphql/reference/input-objects#auditlogorder", + "/enterprise/2.20/v4/input_object/changeuserstatusinput": "/enterprise-server@2.20/graphql/reference/input-objects#changeuserstatusinput", + "/enterprise/2.20/v4/input_object/checkannotationdata": "/enterprise-server@2.20/graphql/reference/input-objects#checkannotationdata", + "/enterprise/2.20/v4/input_object/checkannotationrange": "/enterprise-server@2.20/graphql/reference/input-objects#checkannotationrange", + "/enterprise/2.20/v4/input_object/checkrunaction": "/enterprise-server@2.20/graphql/reference/input-objects#checkrunaction", + "/enterprise/2.20/v4/input_object/checkrunfilter": "/enterprise-server@2.20/graphql/reference/input-objects#checkrunfilter", + "/enterprise/2.20/v4/input_object/checkrunoutput": "/enterprise-server@2.20/graphql/reference/input-objects#checkrunoutput", + "/enterprise/2.20/v4/input_object/checkrunoutputimage": "/enterprise-server@2.20/graphql/reference/input-objects#checkrunoutputimage", + "/enterprise/2.20/v4/input_object/checksuiteautotriggerpreference": "/enterprise-server@2.20/graphql/reference/input-objects#checksuiteautotriggerpreference", + "/enterprise/2.20/v4/input_object/checksuitefilter": "/enterprise-server@2.20/graphql/reference/input-objects#checksuitefilter", + "/enterprise/2.20/v4/input_object/clearlabelsfromlabelableinput": "/enterprise-server@2.20/graphql/reference/input-objects#clearlabelsfromlabelableinput", + "/enterprise/2.20/v4/input_object/cloneprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#cloneprojectinput", + "/enterprise/2.20/v4/input_object/clonetemplaterepositoryinput": "/enterprise-server@2.20/graphql/reference/input-objects#clonetemplaterepositoryinput", + "/enterprise/2.20/v4/input_object/closeissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#closeissueinput", + "/enterprise/2.20/v4/input_object/closepullrequestinput": "/enterprise-server@2.20/graphql/reference/input-objects#closepullrequestinput", + "/enterprise/2.20/v4/input_object/commitauthor": "/enterprise-server@2.20/graphql/reference/input-objects#commitauthor", + "/enterprise/2.20/v4/input_object/commitcontributionorder": "/enterprise-server@2.20/graphql/reference/input-objects#commitcontributionorder", + "/enterprise/2.20/v4/input_object/contributionorder": "/enterprise-server@2.20/graphql/reference/input-objects#contributionorder", + "/enterprise/2.20/v4/input_object/convertprojectcardnotetoissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#convertprojectcardnotetoissueinput", + "/enterprise/2.20/v4/input_object/createbranchprotectionruleinput": "/enterprise-server@2.20/graphql/reference/input-objects#createbranchprotectionruleinput", + "/enterprise/2.20/v4/input_object/createcheckruninput": "/enterprise-server@2.20/graphql/reference/input-objects#createcheckruninput", + "/enterprise/2.20/v4/input_object/createchecksuiteinput": "/enterprise-server@2.20/graphql/reference/input-objects#createchecksuiteinput", + "/enterprise/2.20/v4/input_object/createcontentattachmentinput": "/enterprise-server@2.20/graphql/reference/input-objects#createcontentattachmentinput", + "/enterprise/2.20/v4/input_object/createdeploymentinput": "/enterprise-server@2.20/graphql/reference/input-objects#createdeploymentinput", + "/enterprise/2.20/v4/input_object/createdeploymentstatusinput": "/enterprise-server@2.20/graphql/reference/input-objects#createdeploymentstatusinput", + "/enterprise/2.20/v4/input_object/createissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#createissueinput", + "/enterprise/2.20/v4/input_object/createlabelinput": "/enterprise-server@2.20/graphql/reference/input-objects#createlabelinput", + "/enterprise/2.20/v4/input_object/createprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#createprojectinput", + "/enterprise/2.20/v4/input_object/createpullrequestinput": "/enterprise-server@2.20/graphql/reference/input-objects#createpullrequestinput", + "/enterprise/2.20/v4/input_object/createrefinput": "/enterprise-server@2.20/graphql/reference/input-objects#createrefinput", + "/enterprise/2.20/v4/input_object/createrepositoryinput": "/enterprise-server@2.20/graphql/reference/input-objects#createrepositoryinput", + "/enterprise/2.20/v4/input_object/createteamdiscussioncommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#createteamdiscussioncommentinput", + "/enterprise/2.20/v4/input_object/createteamdiscussioninput": "/enterprise-server@2.20/graphql/reference/input-objects#createteamdiscussioninput", + "/enterprise/2.20/v4/input_object/deletebranchprotectionruleinput": "/enterprise-server@2.20/graphql/reference/input-objects#deletebranchprotectionruleinput", + "/enterprise/2.20/v4/input_object/deleteissuecommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteissuecommentinput", + "/enterprise/2.20/v4/input_object/deleteissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteissueinput", + "/enterprise/2.20/v4/input_object/deletelabelinput": "/enterprise-server@2.20/graphql/reference/input-objects#deletelabelinput", + "/enterprise/2.20/v4/input_object/deleteprojectcardinput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectcardinput", + "/enterprise/2.20/v4/input_object/deleteprojectcolumninput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectcolumninput", + "/enterprise/2.20/v4/input_object/deleteprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteprojectinput", + "/enterprise/2.20/v4/input_object/deletepullrequestreviewcommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#deletepullrequestreviewcommentinput", + "/enterprise/2.20/v4/input_object/deletepullrequestreviewinput": "/enterprise-server@2.20/graphql/reference/input-objects#deletepullrequestreviewinput", + "/enterprise/2.20/v4/input_object/deleterefinput": "/enterprise-server@2.20/graphql/reference/input-objects#deleterefinput", + "/enterprise/2.20/v4/input_object/deleteteamdiscussioncommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteteamdiscussioncommentinput", + "/enterprise/2.20/v4/input_object/deleteteamdiscussioninput": "/enterprise-server@2.20/graphql/reference/input-objects#deleteteamdiscussioninput", + "/enterprise/2.20/v4/input_object/deploymentorder": "/enterprise-server@2.20/graphql/reference/input-objects#deploymentorder", + "/enterprise/2.20/v4/input_object/dismisspullrequestreviewinput": "/enterprise-server@2.20/graphql/reference/input-objects#dismisspullrequestreviewinput", + "/enterprise/2.20/v4/input_object/draftpullrequestreviewcomment": "/enterprise-server@2.20/graphql/reference/input-objects#draftpullrequestreviewcomment", + "/enterprise/2.20/v4/input_object/draftpullrequestreviewthread": "/enterprise-server@2.20/graphql/reference/input-objects#draftpullrequestreviewthread", + "/enterprise/2.20/v4/input_object/enterpriseadministratorinvitationorder": "/enterprise-server@2.20/graphql/reference/input-objects#enterpriseadministratorinvitationorder", + "/enterprise/2.20/v4/input_object/enterprisememberorder": "/enterprise-server@2.20/graphql/reference/input-objects#enterprisememberorder", + "/enterprise/2.20/v4/input_object/enterpriseserveruseraccountemailorder": "/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", + "/enterprise/2.20/v4/input_object/enterpriseserveruseraccountorder": "/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountorder", + "/enterprise/2.20/v4/input_object/enterpriseserveruseraccountsuploadorder": "/enterprise-server@2.20/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", + "/enterprise/2.20/v4/input_object/followuserinput": "/enterprise-server@2.20/graphql/reference/input-objects#followuserinput", + "/enterprise/2.20/v4/input_object/gistorder": "/enterprise-server@2.20/graphql/reference/input-objects#gistorder", + "/enterprise/2.20/v4/input_object/importprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#importprojectinput", + "/enterprise/2.20/v4/input_object/issuefilters": "/enterprise-server@2.20/graphql/reference/input-objects#issuefilters", + "/enterprise/2.20/v4/input_object/issueorder": "/enterprise-server@2.20/graphql/reference/input-objects#issueorder", + "/enterprise/2.20/v4/input_object/labelorder": "/enterprise-server@2.20/graphql/reference/input-objects#labelorder", + "/enterprise/2.20/v4/input_object/languageorder": "/enterprise-server@2.20/graphql/reference/input-objects#languageorder", + "/enterprise/2.20/v4/input_object/linkrepositorytoprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#linkrepositorytoprojectinput", + "/enterprise/2.20/v4/input_object/locklockableinput": "/enterprise-server@2.20/graphql/reference/input-objects#locklockableinput", + "/enterprise/2.20/v4/input_object/markpullrequestreadyforreviewinput": "/enterprise-server@2.20/graphql/reference/input-objects#markpullrequestreadyforreviewinput", + "/enterprise/2.20/v4/input_object/mergebranchinput": "/enterprise-server@2.20/graphql/reference/input-objects#mergebranchinput", + "/enterprise/2.20/v4/input_object/mergepullrequestinput": "/enterprise-server@2.20/graphql/reference/input-objects#mergepullrequestinput", + "/enterprise/2.20/v4/input_object/milestoneorder": "/enterprise-server@2.20/graphql/reference/input-objects#milestoneorder", + "/enterprise/2.20/v4/input_object/minimizecommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#minimizecommentinput", + "/enterprise/2.20/v4/input_object/moveprojectcardinput": "/enterprise-server@2.20/graphql/reference/input-objects#moveprojectcardinput", + "/enterprise/2.20/v4/input_object/moveprojectcolumninput": "/enterprise-server@2.20/graphql/reference/input-objects#moveprojectcolumninput", + "/enterprise/2.20/v4/input_object/organizationorder": "/enterprise-server@2.20/graphql/reference/input-objects#organizationorder", + "/enterprise/2.20/v4/input_object/packagefileorder": "/enterprise-server@2.20/graphql/reference/input-objects#packagefileorder", + "/enterprise/2.20/v4/input_object/packageorder": "/enterprise-server@2.20/graphql/reference/input-objects#packageorder", + "/enterprise/2.20/v4/input_object/packageversionorder": "/enterprise-server@2.20/graphql/reference/input-objects#packageversionorder", + "/enterprise/2.20/v4/input_object/pinissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#pinissueinput", + "/enterprise/2.20/v4/input_object/projectcardimport": "/enterprise-server@2.20/graphql/reference/input-objects#projectcardimport", + "/enterprise/2.20/v4/input_object/projectcolumnimport": "/enterprise-server@2.20/graphql/reference/input-objects#projectcolumnimport", + "/enterprise/2.20/v4/input_object/projectorder": "/enterprise-server@2.20/graphql/reference/input-objects#projectorder", + "/enterprise/2.20/v4/input_object/pullrequestorder": "/enterprise-server@2.20/graphql/reference/input-objects#pullrequestorder", + "/enterprise/2.20/v4/input_object/reactionorder": "/enterprise-server@2.20/graphql/reference/input-objects#reactionorder", + "/enterprise/2.20/v4/input_object/reforder": "/enterprise-server@2.20/graphql/reference/input-objects#reforder", + "/enterprise/2.20/v4/input_object/refupdate": "/enterprise-server@2.20/graphql/reference/input-objects#refupdate", + "/enterprise/2.20/v4/input_object/registrypackagemetadatum": "/enterprise-server@2.20/graphql/reference/input-objects#registrypackagemetadatum", + "/enterprise/2.20/v4/input_object/releaseorder": "/enterprise-server@2.20/graphql/reference/input-objects#releaseorder", + "/enterprise/2.20/v4/input_object/removeassigneesfromassignableinput": "/enterprise-server@2.20/graphql/reference/input-objects#removeassigneesfromassignableinput", + "/enterprise/2.20/v4/input_object/removeenterpriseadmininput": "/enterprise-server@2.20/graphql/reference/input-objects#removeenterpriseadmininput", + "/enterprise/2.20/v4/input_object/removelabelsfromlabelableinput": "/enterprise-server@2.20/graphql/reference/input-objects#removelabelsfromlabelableinput", + "/enterprise/2.20/v4/input_object/removeoutsidecollaboratorinput": "/enterprise-server@2.20/graphql/reference/input-objects#removeoutsidecollaboratorinput", + "/enterprise/2.20/v4/input_object/removereactioninput": "/enterprise-server@2.20/graphql/reference/input-objects#removereactioninput", + "/enterprise/2.20/v4/input_object/removestarinput": "/enterprise-server@2.20/graphql/reference/input-objects#removestarinput", + "/enterprise/2.20/v4/input_object/reopenissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#reopenissueinput", + "/enterprise/2.20/v4/input_object/reopenpullrequestinput": "/enterprise-server@2.20/graphql/reference/input-objects#reopenpullrequestinput", + "/enterprise/2.20/v4/input_object/repositoryinvitationorder": "/enterprise-server@2.20/graphql/reference/input-objects#repositoryinvitationorder", + "/enterprise/2.20/v4/input_object/repositoryorder": "/enterprise-server@2.20/graphql/reference/input-objects#repositoryorder", + "/enterprise/2.20/v4/input_object/requestreviewsinput": "/enterprise-server@2.20/graphql/reference/input-objects#requestreviewsinput", + "/enterprise/2.20/v4/input_object/rerequestchecksuiteinput": "/enterprise-server@2.20/graphql/reference/input-objects#rerequestchecksuiteinput", + "/enterprise/2.20/v4/input_object/resolvereviewthreadinput": "/enterprise-server@2.20/graphql/reference/input-objects#resolvereviewthreadinput", + "/enterprise/2.20/v4/input_object/savedreplyorder": "/enterprise-server@2.20/graphql/reference/input-objects#savedreplyorder", + "/enterprise/2.20/v4/input_object/sponsorshiporder": "/enterprise-server@2.20/graphql/reference/input-objects#sponsorshiporder", + "/enterprise/2.20/v4/input_object/starorder": "/enterprise-server@2.20/graphql/reference/input-objects#starorder", + "/enterprise/2.20/v4/input_object/submitpullrequestreviewinput": "/enterprise-server@2.20/graphql/reference/input-objects#submitpullrequestreviewinput", + "/enterprise/2.20/v4/input_object/teamdiscussioncommentorder": "/enterprise-server@2.20/graphql/reference/input-objects#teamdiscussioncommentorder", + "/enterprise/2.20/v4/input_object/teamdiscussionorder": "/enterprise-server@2.20/graphql/reference/input-objects#teamdiscussionorder", + "/enterprise/2.20/v4/input_object/teammemberorder": "/enterprise-server@2.20/graphql/reference/input-objects#teammemberorder", + "/enterprise/2.20/v4/input_object/teamorder": "/enterprise-server@2.20/graphql/reference/input-objects#teamorder", + "/enterprise/2.20/v4/input_object/teamrepositoryorder": "/enterprise-server@2.20/graphql/reference/input-objects#teamrepositoryorder", + "/enterprise/2.20/v4/input_object/transferissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#transferissueinput", + "/enterprise/2.20/v4/input_object/unarchiverepositoryinput": "/enterprise-server@2.20/graphql/reference/input-objects#unarchiverepositoryinput", + "/enterprise/2.20/v4/input_object/unfollowuserinput": "/enterprise-server@2.20/graphql/reference/input-objects#unfollowuserinput", + "/enterprise/2.20/v4/input_object/unlinkrepositoryfromprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", + "/enterprise/2.20/v4/input_object/unlocklockableinput": "/enterprise-server@2.20/graphql/reference/input-objects#unlocklockableinput", + "/enterprise/2.20/v4/input_object/unmarkissueasduplicateinput": "/enterprise-server@2.20/graphql/reference/input-objects#unmarkissueasduplicateinput", + "/enterprise/2.20/v4/input_object/unminimizecommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#unminimizecommentinput", + "/enterprise/2.20/v4/input_object/unpinissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#unpinissueinput", + "/enterprise/2.20/v4/input_object/unresolvereviewthreadinput": "/enterprise-server@2.20/graphql/reference/input-objects#unresolvereviewthreadinput", + "/enterprise/2.20/v4/input_object/updatebranchprotectionruleinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatebranchprotectionruleinput", + "/enterprise/2.20/v4/input_object/updatecheckruninput": "/enterprise-server@2.20/graphql/reference/input-objects#updatecheckruninput", + "/enterprise/2.20/v4/input_object/updatechecksuitepreferencesinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatechecksuitepreferencesinput", + "/enterprise/2.20/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", + "/enterprise/2.20/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", + "/enterprise/2.20/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", + "/enterprise/2.20/v4/input_object/updateenterpriseprofileinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseprofileinput", + "/enterprise/2.20/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", + "/enterprise/2.20/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", + "/enterprise/2.20/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/enterprise-server@2.20/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", + "/enterprise/2.20/v4/input_object/updateissuecommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateissuecommentinput", + "/enterprise/2.20/v4/input_object/updateissueinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateissueinput", + "/enterprise/2.20/v4/input_object/updatelabelinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatelabelinput", + "/enterprise/2.20/v4/input_object/updateprojectcardinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateprojectcardinput", + "/enterprise/2.20/v4/input_object/updateprojectcolumninput": "/enterprise-server@2.20/graphql/reference/input-objects#updateprojectcolumninput", + "/enterprise/2.20/v4/input_object/updateprojectinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateprojectinput", + "/enterprise/2.20/v4/input_object/updatepullrequestinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestinput", + "/enterprise/2.20/v4/input_object/updatepullrequestreviewcommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestreviewcommentinput", + "/enterprise/2.20/v4/input_object/updatepullrequestreviewinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatepullrequestreviewinput", + "/enterprise/2.20/v4/input_object/updaterefinput": "/enterprise-server@2.20/graphql/reference/input-objects#updaterefinput", + "/enterprise/2.20/v4/input_object/updaterefsinput": "/enterprise-server@2.20/graphql/reference/input-objects#updaterefsinput", + "/enterprise/2.20/v4/input_object/updaterepositoryinput": "/enterprise-server@2.20/graphql/reference/input-objects#updaterepositoryinput", + "/enterprise/2.20/v4/input_object/updatesubscriptioninput": "/enterprise-server@2.20/graphql/reference/input-objects#updatesubscriptioninput", + "/enterprise/2.20/v4/input_object/updateteamdiscussioncommentinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateteamdiscussioncommentinput", + "/enterprise/2.20/v4/input_object/updateteamdiscussioninput": "/enterprise-server@2.20/graphql/reference/input-objects#updateteamdiscussioninput", + "/enterprise/2.20/v4/input_object/updateteamreviewassignmentinput": "/enterprise-server@2.20/graphql/reference/input-objects#updateteamreviewassignmentinput", + "/enterprise/2.20/v4/input_object/updatetopicsinput": "/enterprise-server@2.20/graphql/reference/input-objects#updatetopicsinput", + "/enterprise/2.20/v4/input_object/userstatusorder": "/enterprise-server@2.20/graphql/reference/input-objects#userstatusorder", + "/enterprise/2.20/v4/interface/actor": "/enterprise-server@2.20/graphql/reference/interfaces#actor", + "/enterprise/2.20/v4/interface/assignable": "/enterprise-server@2.20/graphql/reference/interfaces#assignable", + "/enterprise/2.20/v4/interface/auditentry": "/enterprise-server@2.20/graphql/reference/interfaces#auditentry", + "/enterprise/2.20/v4/interface/closable": "/enterprise-server@2.20/graphql/reference/interfaces#closable", + "/enterprise/2.20/v4/interface/comment": "/enterprise-server@2.20/graphql/reference/interfaces#comment", + "/enterprise/2.20/v4/interface/contribution": "/enterprise-server@2.20/graphql/reference/interfaces#contribution", + "/enterprise/2.20/v4/interface/deletable": "/enterprise-server@2.20/graphql/reference/interfaces#deletable", + "/enterprise/2.20/v4/interface/enterpriseauditentrydata": "/enterprise-server@2.20/graphql/reference/interfaces#enterpriseauditentrydata", + "/enterprise/2.20/v4/interface/gitobject": "/enterprise-server@2.20/graphql/reference/interfaces#gitobject", + "/enterprise/2.20/v4/interface/gitsignature": "/enterprise-server@2.20/graphql/reference/interfaces#gitsignature", + "/enterprise/2.20/v4/interface/hovercardcontext": "/enterprise-server@2.20/graphql/reference/interfaces#hovercardcontext", + "/enterprise/2.20/v4/interface/labelable": "/enterprise-server@2.20/graphql/reference/interfaces#labelable", + "/enterprise/2.20/v4/interface/lockable": "/enterprise-server@2.20/graphql/reference/interfaces#lockable", + "/enterprise/2.20/v4/interface/memberstatusable": "/enterprise-server@2.20/graphql/reference/interfaces#memberstatusable", + "/enterprise/2.20/v4/interface/minimizable": "/enterprise-server@2.20/graphql/reference/interfaces#minimizable", + "/enterprise/2.20/v4/interface/node": "/enterprise-server@2.20/graphql/reference/interfaces#node", + "/enterprise/2.20/v4/interface/oauthapplicationauditentrydata": "/enterprise-server@2.20/graphql/reference/interfaces#oauthapplicationauditentrydata", + "/enterprise/2.20/v4/interface/organizationauditentrydata": "/enterprise-server@2.20/graphql/reference/interfaces#organizationauditentrydata", + "/enterprise/2.20/v4/interface/packageowner": "/enterprise-server@2.20/graphql/reference/interfaces#packageowner", + "/enterprise/2.20/v4/interface/profileowner": "/enterprise-server@2.20/graphql/reference/interfaces#profileowner", + "/enterprise/2.20/v4/interface/projectowner": "/enterprise-server@2.20/graphql/reference/interfaces#projectowner", + "/enterprise/2.20/v4/interface/reactable": "/enterprise-server@2.20/graphql/reference/interfaces#reactable", + "/enterprise/2.20/v4/interface/registrypackageowner": "/enterprise-server@2.20/graphql/reference/interfaces#registrypackageowner", + "/enterprise/2.20/v4/interface/registrypackagesearch": "/enterprise-server@2.20/graphql/reference/interfaces#registrypackagesearch", + "/enterprise/2.20/v4/interface/repositoryauditentrydata": "/enterprise-server@2.20/graphql/reference/interfaces#repositoryauditentrydata", + "/enterprise/2.20/v4/interface/repositoryinfo": "/enterprise-server@2.20/graphql/reference/interfaces#repositoryinfo", + "/enterprise/2.20/v4/interface/repositorynode": "/enterprise-server@2.20/graphql/reference/interfaces#repositorynode", + "/enterprise/2.20/v4/interface/repositoryowner": "/enterprise-server@2.20/graphql/reference/interfaces#repositoryowner", + "/enterprise/2.20/v4/interface/starrable": "/enterprise-server@2.20/graphql/reference/interfaces#starrable", + "/enterprise/2.20/v4/interface/subscribable": "/enterprise-server@2.20/graphql/reference/interfaces#subscribable", + "/enterprise/2.20/v4/interface/teamauditentrydata": "/enterprise-server@2.20/graphql/reference/interfaces#teamauditentrydata", + "/enterprise/2.20/v4/interface/topicauditentrydata": "/enterprise-server@2.20/graphql/reference/interfaces#topicauditentrydata", + "/enterprise/2.20/v4/interface/uniformresourcelocatable": "/enterprise-server@2.20/graphql/reference/interfaces#uniformresourcelocatable", + "/enterprise/2.20/v4/interface/updatable": "/enterprise-server@2.20/graphql/reference/interfaces#updatable", + "/enterprise/2.20/v4/interface/updatablecomment": "/enterprise-server@2.20/graphql/reference/interfaces#updatablecomment", + "/enterprise/2.20/v4/mutation/addassigneestoassignable": "/enterprise-server@2.20/graphql/reference/mutations#addassigneestoassignable", + "/enterprise/2.20/v4/mutation/addcomment": "/enterprise-server@2.20/graphql/reference/mutations#addcomment", + "/enterprise/2.20/v4/mutation/addenterpriseadmin": "/enterprise-server@2.20/graphql/reference/mutations#addenterpriseadmin", + "/enterprise/2.20/v4/mutation/addlabelstolabelable": "/enterprise-server@2.20/graphql/reference/mutations#addlabelstolabelable", + "/enterprise/2.20/v4/mutation/addprojectcard": "/enterprise-server@2.20/graphql/reference/mutations#addprojectcard", + "/enterprise/2.20/v4/mutation/addprojectcolumn": "/enterprise-server@2.20/graphql/reference/mutations#addprojectcolumn", + "/enterprise/2.20/v4/mutation/addpullrequestreview": "/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreview", + "/enterprise/2.20/v4/mutation/addpullrequestreviewcomment": "/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreviewcomment", + "/enterprise/2.20/v4/mutation/addpullrequestreviewthread": "/enterprise-server@2.20/graphql/reference/mutations#addpullrequestreviewthread", + "/enterprise/2.20/v4/mutation/addreaction": "/enterprise-server@2.20/graphql/reference/mutations#addreaction", + "/enterprise/2.20/v4/mutation/addstar": "/enterprise-server@2.20/graphql/reference/mutations#addstar", + "/enterprise/2.20/v4/mutation/archiverepository": "/enterprise-server@2.20/graphql/reference/mutations#archiverepository", + "/enterprise/2.20/v4/mutation/changeuserstatus": "/enterprise-server@2.20/graphql/reference/mutations#changeuserstatus", + "/enterprise/2.20/v4/mutation/clearlabelsfromlabelable": "/enterprise-server@2.20/graphql/reference/mutations#clearlabelsfromlabelable", + "/enterprise/2.20/v4/mutation/cloneproject": "/enterprise-server@2.20/graphql/reference/mutations#cloneproject", + "/enterprise/2.20/v4/mutation/clonetemplaterepository": "/enterprise-server@2.20/graphql/reference/mutations#clonetemplaterepository", + "/enterprise/2.20/v4/mutation/closeissue": "/enterprise-server@2.20/graphql/reference/mutations#closeissue", + "/enterprise/2.20/v4/mutation/closepullrequest": "/enterprise-server@2.20/graphql/reference/mutations#closepullrequest", + "/enterprise/2.20/v4/mutation/convertprojectcardnotetoissue": "/enterprise-server@2.20/graphql/reference/mutations#convertprojectcardnotetoissue", + "/enterprise/2.20/v4/mutation/createbranchprotectionrule": "/enterprise-server@2.20/graphql/reference/mutations#createbranchprotectionrule", + "/enterprise/2.20/v4/mutation/createcheckrun": "/enterprise-server@2.20/graphql/reference/mutations#createcheckrun", + "/enterprise/2.20/v4/mutation/createchecksuite": "/enterprise-server@2.20/graphql/reference/mutations#createchecksuite", + "/enterprise/2.20/v4/mutation/createcontentattachment": "/enterprise-server@2.20/graphql/reference/mutations#createcontentattachment", + "/enterprise/2.20/v4/mutation/createdeployment": "/enterprise-server@2.20/graphql/reference/mutations#createdeployment", + "/enterprise/2.20/v4/mutation/createdeploymentstatus": "/enterprise-server@2.20/graphql/reference/mutations#createdeploymentstatus", + "/enterprise/2.20/v4/mutation/createissue": "/enterprise-server@2.20/graphql/reference/mutations#createissue", + "/enterprise/2.20/v4/mutation/createlabel": "/enterprise-server@2.20/graphql/reference/mutations#createlabel", + "/enterprise/2.20/v4/mutation/createproject": "/enterprise-server@2.20/graphql/reference/mutations#createproject", + "/enterprise/2.20/v4/mutation/createpullrequest": "/enterprise-server@2.20/graphql/reference/mutations#createpullrequest", + "/enterprise/2.20/v4/mutation/createref": "/enterprise-server@2.20/graphql/reference/mutations#createref", + "/enterprise/2.20/v4/mutation/createrepository": "/enterprise-server@2.20/graphql/reference/mutations#createrepository", + "/enterprise/2.20/v4/mutation/createteamdiscussion": "/enterprise-server@2.20/graphql/reference/mutations#createteamdiscussion", + "/enterprise/2.20/v4/mutation/createteamdiscussioncomment": "/enterprise-server@2.20/graphql/reference/mutations#createteamdiscussioncomment", + "/enterprise/2.20/v4/mutation/deletebranchprotectionrule": "/enterprise-server@2.20/graphql/reference/mutations#deletebranchprotectionrule", + "/enterprise/2.20/v4/mutation/deleteissue": "/enterprise-server@2.20/graphql/reference/mutations#deleteissue", + "/enterprise/2.20/v4/mutation/deleteissuecomment": "/enterprise-server@2.20/graphql/reference/mutations#deleteissuecomment", + "/enterprise/2.20/v4/mutation/deletelabel": "/enterprise-server@2.20/graphql/reference/mutations#deletelabel", + "/enterprise/2.20/v4/mutation/deleteproject": "/enterprise-server@2.20/graphql/reference/mutations#deleteproject", + "/enterprise/2.20/v4/mutation/deleteprojectcard": "/enterprise-server@2.20/graphql/reference/mutations#deleteprojectcard", + "/enterprise/2.20/v4/mutation/deleteprojectcolumn": "/enterprise-server@2.20/graphql/reference/mutations#deleteprojectcolumn", + "/enterprise/2.20/v4/mutation/deletepullrequestreview": "/enterprise-server@2.20/graphql/reference/mutations#deletepullrequestreview", + "/enterprise/2.20/v4/mutation/deletepullrequestreviewcomment": "/enterprise-server@2.20/graphql/reference/mutations#deletepullrequestreviewcomment", + "/enterprise/2.20/v4/mutation/deleteref": "/enterprise-server@2.20/graphql/reference/mutations#deleteref", + "/enterprise/2.20/v4/mutation/deleteteamdiscussion": "/enterprise-server@2.20/graphql/reference/mutations#deleteteamdiscussion", + "/enterprise/2.20/v4/mutation/deleteteamdiscussioncomment": "/enterprise-server@2.20/graphql/reference/mutations#deleteteamdiscussioncomment", + "/enterprise/2.20/v4/mutation/dismisspullrequestreview": "/enterprise-server@2.20/graphql/reference/mutations#dismisspullrequestreview", + "/enterprise/2.20/v4/mutation/followuser": "/enterprise-server@2.20/graphql/reference/mutations#followuser", + "/enterprise/2.20/v4/mutation/importproject": "/enterprise-server@2.20/graphql/reference/mutations#importproject", + "/enterprise/2.20/v4/mutation/linkrepositorytoproject": "/enterprise-server@2.20/graphql/reference/mutations#linkrepositorytoproject", + "/enterprise/2.20/v4/mutation/locklockable": "/enterprise-server@2.20/graphql/reference/mutations#locklockable", + "/enterprise/2.20/v4/mutation/markpullrequestreadyforreview": "/enterprise-server@2.20/graphql/reference/mutations#markpullrequestreadyforreview", + "/enterprise/2.20/v4/mutation/mergebranch": "/enterprise-server@2.20/graphql/reference/mutations#mergebranch", + "/enterprise/2.20/v4/mutation/mergepullrequest": "/enterprise-server@2.20/graphql/reference/mutations#mergepullrequest", + "/enterprise/2.20/v4/mutation/minimizecomment": "/enterprise-server@2.20/graphql/reference/mutations#minimizecomment", + "/enterprise/2.20/v4/mutation/moveprojectcard": "/enterprise-server@2.20/graphql/reference/mutations#moveprojectcard", + "/enterprise/2.20/v4/mutation/moveprojectcolumn": "/enterprise-server@2.20/graphql/reference/mutations#moveprojectcolumn", + "/enterprise/2.20/v4/mutation/pinissue": "/enterprise-server@2.20/graphql/reference/mutations#pinissue", + "/enterprise/2.20/v4/mutation/removeassigneesfromassignable": "/enterprise-server@2.20/graphql/reference/mutations#removeassigneesfromassignable", + "/enterprise/2.20/v4/mutation/removeenterpriseadmin": "/enterprise-server@2.20/graphql/reference/mutations#removeenterpriseadmin", + "/enterprise/2.20/v4/mutation/removelabelsfromlabelable": "/enterprise-server@2.20/graphql/reference/mutations#removelabelsfromlabelable", + "/enterprise/2.20/v4/mutation/removeoutsidecollaborator": "/enterprise-server@2.20/graphql/reference/mutations#removeoutsidecollaborator", + "/enterprise/2.20/v4/mutation/removereaction": "/enterprise-server@2.20/graphql/reference/mutations#removereaction", + "/enterprise/2.20/v4/mutation/removestar": "/enterprise-server@2.20/graphql/reference/mutations#removestar", + "/enterprise/2.20/v4/mutation/reopenissue": "/enterprise-server@2.20/graphql/reference/mutations#reopenissue", + "/enterprise/2.20/v4/mutation/reopenpullrequest": "/enterprise-server@2.20/graphql/reference/mutations#reopenpullrequest", + "/enterprise/2.20/v4/mutation/requestreviews": "/enterprise-server@2.20/graphql/reference/mutations#requestreviews", + "/enterprise/2.20/v4/mutation/rerequestchecksuite": "/enterprise-server@2.20/graphql/reference/mutations#rerequestchecksuite", + "/enterprise/2.20/v4/mutation/resolvereviewthread": "/enterprise-server@2.20/graphql/reference/mutations#resolvereviewthread", + "/enterprise/2.20/v4/mutation/submitpullrequestreview": "/enterprise-server@2.20/graphql/reference/mutations#submitpullrequestreview", + "/enterprise/2.20/v4/mutation/transferissue": "/enterprise-server@2.20/graphql/reference/mutations#transferissue", + "/enterprise/2.20/v4/mutation/unarchiverepository": "/enterprise-server@2.20/graphql/reference/mutations#unarchiverepository", + "/enterprise/2.20/v4/mutation/unfollowuser": "/enterprise-server@2.20/graphql/reference/mutations#unfollowuser", + "/enterprise/2.20/v4/mutation/unlinkrepositoryfromproject": "/enterprise-server@2.20/graphql/reference/mutations#unlinkrepositoryfromproject", + "/enterprise/2.20/v4/mutation/unlocklockable": "/enterprise-server@2.20/graphql/reference/mutations#unlocklockable", + "/enterprise/2.20/v4/mutation/unmarkissueasduplicate": "/enterprise-server@2.20/graphql/reference/mutations#unmarkissueasduplicate", + "/enterprise/2.20/v4/mutation/unminimizecomment": "/enterprise-server@2.20/graphql/reference/mutations#unminimizecomment", + "/enterprise/2.20/v4/mutation/unpinissue": "/enterprise-server@2.20/graphql/reference/mutations#unpinissue", + "/enterprise/2.20/v4/mutation/unresolvereviewthread": "/enterprise-server@2.20/graphql/reference/mutations#unresolvereviewthread", + "/enterprise/2.20/v4/mutation/updatebranchprotectionrule": "/enterprise-server@2.20/graphql/reference/mutations#updatebranchprotectionrule", + "/enterprise/2.20/v4/mutation/updatecheckrun": "/enterprise-server@2.20/graphql/reference/mutations#updatecheckrun", + "/enterprise/2.20/v4/mutation/updatechecksuitepreferences": "/enterprise-server@2.20/graphql/reference/mutations#updatechecksuitepreferences", + "/enterprise/2.20/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", + "/enterprise/2.20/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", + "/enterprise/2.20/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscandeleteissuessetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", + "/enterprise/2.20/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", + "/enterprise/2.20/v4/mutation/updateenterpriseorganizationprojectssetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", + "/enterprise/2.20/v4/mutation/updateenterpriseprofile": "/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseprofile", + "/enterprise/2.20/v4/mutation/updateenterpriserepositoryprojectssetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", + "/enterprise/2.20/v4/mutation/updateenterpriseteamdiscussionssetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", + "/enterprise/2.20/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/enterprise-server@2.20/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", + "/enterprise/2.20/v4/mutation/updateissue": "/enterprise-server@2.20/graphql/reference/mutations#updateissue", + "/enterprise/2.20/v4/mutation/updateissuecomment": "/enterprise-server@2.20/graphql/reference/mutations#updateissuecomment", + "/enterprise/2.20/v4/mutation/updatelabel": "/enterprise-server@2.20/graphql/reference/mutations#updatelabel", + "/enterprise/2.20/v4/mutation/updateproject": "/enterprise-server@2.20/graphql/reference/mutations#updateproject", + "/enterprise/2.20/v4/mutation/updateprojectcard": "/enterprise-server@2.20/graphql/reference/mutations#updateprojectcard", + "/enterprise/2.20/v4/mutation/updateprojectcolumn": "/enterprise-server@2.20/graphql/reference/mutations#updateprojectcolumn", + "/enterprise/2.20/v4/mutation/updatepullrequest": "/enterprise-server@2.20/graphql/reference/mutations#updatepullrequest", + "/enterprise/2.20/v4/mutation/updatepullrequestreview": "/enterprise-server@2.20/graphql/reference/mutations#updatepullrequestreview", + "/enterprise/2.20/v4/mutation/updatepullrequestreviewcomment": "/enterprise-server@2.20/graphql/reference/mutations#updatepullrequestreviewcomment", + "/enterprise/2.20/v4/mutation/updateref": "/enterprise-server@2.20/graphql/reference/mutations#updateref", + "/enterprise/2.20/v4/mutation/updaterefs": "/enterprise-server@2.20/graphql/reference/mutations#updaterefs", + "/enterprise/2.20/v4/mutation/updaterepository": "/enterprise-server@2.20/graphql/reference/mutations#updaterepository", + "/enterprise/2.20/v4/mutation/updatesubscription": "/enterprise-server@2.20/graphql/reference/mutations#updatesubscription", + "/enterprise/2.20/v4/mutation/updateteamdiscussion": "/enterprise-server@2.20/graphql/reference/mutations#updateteamdiscussion", + "/enterprise/2.20/v4/mutation/updateteamdiscussioncomment": "/enterprise-server@2.20/graphql/reference/mutations#updateteamdiscussioncomment", + "/enterprise/2.20/v4/mutation/updateteamreviewassignment": "/enterprise-server@2.20/graphql/reference/mutations#updateteamreviewassignment", + "/enterprise/2.20/v4/mutation/updatetopics": "/enterprise-server@2.20/graphql/reference/mutations#updatetopics", + "/enterprise/2.20/v4/object/__directive": "/enterprise-server@2.20/graphql/reference/objects#__directive", + "/enterprise/2.20/v4/object/__enumvalue": "/enterprise-server@2.20/graphql/reference/objects#__enumvalue", + "/enterprise/2.20/v4/object/__field": "/enterprise-server@2.20/graphql/reference/objects#__field", + "/enterprise/2.20/v4/object/__inputvalue": "/enterprise-server@2.20/graphql/reference/objects#__inputvalue", + "/enterprise/2.20/v4/object/__schema": "/enterprise-server@2.20/graphql/reference/objects#__schema", + "/enterprise/2.20/v4/object/__type": "/enterprise-server@2.20/graphql/reference/objects#__type", + "/enterprise/2.20/v4/object/actorlocation": "/enterprise-server@2.20/graphql/reference/objects#actorlocation", + "/enterprise/2.20/v4/object/addassigneestoassignablepayload": "/enterprise-server@2.20/graphql/reference/objects#addassigneestoassignablepayload", + "/enterprise/2.20/v4/object/addcommentpayload": "/enterprise-server@2.20/graphql/reference/objects#addcommentpayload", + "/enterprise/2.20/v4/object/addedtoprojectevent": "/enterprise-server@2.20/graphql/reference/objects#addedtoprojectevent", + "/enterprise/2.20/v4/object/addenterpriseadminpayload": "/enterprise-server@2.20/graphql/reference/objects#addenterpriseadminpayload", + "/enterprise/2.20/v4/object/addlabelstolabelablepayload": "/enterprise-server@2.20/graphql/reference/objects#addlabelstolabelablepayload", + "/enterprise/2.20/v4/object/addprojectcardpayload": "/enterprise-server@2.20/graphql/reference/objects#addprojectcardpayload", + "/enterprise/2.20/v4/object/addprojectcolumnpayload": "/enterprise-server@2.20/graphql/reference/objects#addprojectcolumnpayload", + "/enterprise/2.20/v4/object/addpullrequestreviewcommentpayload": "/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewcommentpayload", + "/enterprise/2.20/v4/object/addpullrequestreviewpayload": "/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewpayload", + "/enterprise/2.20/v4/object/addpullrequestreviewthreadpayload": "/enterprise-server@2.20/graphql/reference/objects#addpullrequestreviewthreadpayload", + "/enterprise/2.20/v4/object/addreactionpayload": "/enterprise-server@2.20/graphql/reference/objects#addreactionpayload", + "/enterprise/2.20/v4/object/addstarpayload": "/enterprise-server@2.20/graphql/reference/objects#addstarpayload", + "/enterprise/2.20/v4/object/app": "/enterprise-server@2.20/graphql/reference/objects#app", + "/enterprise/2.20/v4/object/archiverepositorypayload": "/enterprise-server@2.20/graphql/reference/objects#archiverepositorypayload", + "/enterprise/2.20/v4/object/assignedevent": "/enterprise-server@2.20/graphql/reference/objects#assignedevent", + "/enterprise/2.20/v4/object/baserefchangedevent": "/enterprise-server@2.20/graphql/reference/objects#baserefchangedevent", + "/enterprise/2.20/v4/object/baserefforcepushedevent": "/enterprise-server@2.20/graphql/reference/objects#baserefforcepushedevent", + "/enterprise/2.20/v4/object/blame": "/enterprise-server@2.20/graphql/reference/objects#blame", + "/enterprise/2.20/v4/object/blamerange": "/enterprise-server@2.20/graphql/reference/objects#blamerange", + "/enterprise/2.20/v4/object/blob": "/enterprise-server@2.20/graphql/reference/objects#blob", + "/enterprise/2.20/v4/object/bot": "/enterprise-server@2.20/graphql/reference/objects#bot", + "/enterprise/2.20/v4/object/branchprotectionrule": "/enterprise-server@2.20/graphql/reference/objects#branchprotectionrule", + "/enterprise/2.20/v4/object/branchprotectionruleconflict": "/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflict", + "/enterprise/2.20/v4/object/branchprotectionruleconflictconnection": "/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflictconnection", + "/enterprise/2.20/v4/object/branchprotectionruleconflictedge": "/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconflictedge", + "/enterprise/2.20/v4/object/branchprotectionruleconnection": "/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleconnection", + "/enterprise/2.20/v4/object/branchprotectionruleedge": "/enterprise-server@2.20/graphql/reference/objects#branchprotectionruleedge", + "/enterprise/2.20/v4/object/changeuserstatuspayload": "/enterprise-server@2.20/graphql/reference/objects#changeuserstatuspayload", + "/enterprise/2.20/v4/object/checkannotation": "/enterprise-server@2.20/graphql/reference/objects#checkannotation", + "/enterprise/2.20/v4/object/checkannotationconnection": "/enterprise-server@2.20/graphql/reference/objects#checkannotationconnection", + "/enterprise/2.20/v4/object/checkannotationedge": "/enterprise-server@2.20/graphql/reference/objects#checkannotationedge", + "/enterprise/2.20/v4/object/checkannotationposition": "/enterprise-server@2.20/graphql/reference/objects#checkannotationposition", + "/enterprise/2.20/v4/object/checkannotationspan": "/enterprise-server@2.20/graphql/reference/objects#checkannotationspan", + "/enterprise/2.20/v4/object/checkrun": "/enterprise-server@2.20/graphql/reference/objects#checkrun", + "/enterprise/2.20/v4/object/checkrunconnection": "/enterprise-server@2.20/graphql/reference/objects#checkrunconnection", + "/enterprise/2.20/v4/object/checkrunedge": "/enterprise-server@2.20/graphql/reference/objects#checkrunedge", + "/enterprise/2.20/v4/object/checksuite": "/enterprise-server@2.20/graphql/reference/objects#checksuite", + "/enterprise/2.20/v4/object/checksuiteconnection": "/enterprise-server@2.20/graphql/reference/objects#checksuiteconnection", + "/enterprise/2.20/v4/object/checksuiteedge": "/enterprise-server@2.20/graphql/reference/objects#checksuiteedge", + "/enterprise/2.20/v4/object/clearlabelsfromlabelablepayload": "/enterprise-server@2.20/graphql/reference/objects#clearlabelsfromlabelablepayload", + "/enterprise/2.20/v4/object/cloneprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#cloneprojectpayload", + "/enterprise/2.20/v4/object/clonetemplaterepositorypayload": "/enterprise-server@2.20/graphql/reference/objects#clonetemplaterepositorypayload", + "/enterprise/2.20/v4/object/closedevent": "/enterprise-server@2.20/graphql/reference/objects#closedevent", + "/enterprise/2.20/v4/object/closeissuepayload": "/enterprise-server@2.20/graphql/reference/objects#closeissuepayload", + "/enterprise/2.20/v4/object/closepullrequestpayload": "/enterprise-server@2.20/graphql/reference/objects#closepullrequestpayload", + "/enterprise/2.20/v4/object/codeofconduct": "/enterprise-server@2.20/graphql/reference/objects#codeofconduct", + "/enterprise/2.20/v4/object/commentdeletedevent": "/enterprise-server@2.20/graphql/reference/objects#commentdeletedevent", + "/enterprise/2.20/v4/object/commit": "/enterprise-server@2.20/graphql/reference/objects#commit", + "/enterprise/2.20/v4/object/commitcomment": "/enterprise-server@2.20/graphql/reference/objects#commitcomment", + "/enterprise/2.20/v4/object/commitcommentconnection": "/enterprise-server@2.20/graphql/reference/objects#commitcommentconnection", + "/enterprise/2.20/v4/object/commitcommentedge": "/enterprise-server@2.20/graphql/reference/objects#commitcommentedge", + "/enterprise/2.20/v4/object/commitcommentthread": "/enterprise-server@2.20/graphql/reference/objects#commitcommentthread", + "/enterprise/2.20/v4/object/commitconnection": "/enterprise-server@2.20/graphql/reference/objects#commitconnection", + "/enterprise/2.20/v4/object/commitcontributionsbyrepository": "/enterprise-server@2.20/graphql/reference/objects#commitcontributionsbyrepository", + "/enterprise/2.20/v4/object/commitedge": "/enterprise-server@2.20/graphql/reference/objects#commitedge", + "/enterprise/2.20/v4/object/commithistoryconnection": "/enterprise-server@2.20/graphql/reference/objects#commithistoryconnection", + "/enterprise/2.20/v4/object/contentattachment": "/enterprise-server@2.20/graphql/reference/objects#contentattachment", + "/enterprise/2.20/v4/object/contentreference": "/enterprise-server@2.20/graphql/reference/objects#contentreference", + "/enterprise/2.20/v4/object/contributioncalendar": "/enterprise-server@2.20/graphql/reference/objects#contributioncalendar", + "/enterprise/2.20/v4/object/contributioncalendarday": "/enterprise-server@2.20/graphql/reference/objects#contributioncalendarday", + "/enterprise/2.20/v4/object/contributioncalendarmonth": "/enterprise-server@2.20/graphql/reference/objects#contributioncalendarmonth", + "/enterprise/2.20/v4/object/contributioncalendarweek": "/enterprise-server@2.20/graphql/reference/objects#contributioncalendarweek", + "/enterprise/2.20/v4/object/contributionscollection": "/enterprise-server@2.20/graphql/reference/objects#contributionscollection", + "/enterprise/2.20/v4/object/convertednotetoissueevent": "/enterprise-server@2.20/graphql/reference/objects#convertednotetoissueevent", + "/enterprise/2.20/v4/object/convertprojectcardnotetoissuepayload": "/enterprise-server@2.20/graphql/reference/objects#convertprojectcardnotetoissuepayload", + "/enterprise/2.20/v4/object/createbranchprotectionrulepayload": "/enterprise-server@2.20/graphql/reference/objects#createbranchprotectionrulepayload", + "/enterprise/2.20/v4/object/createcheckrunpayload": "/enterprise-server@2.20/graphql/reference/objects#createcheckrunpayload", + "/enterprise/2.20/v4/object/createchecksuitepayload": "/enterprise-server@2.20/graphql/reference/objects#createchecksuitepayload", + "/enterprise/2.20/v4/object/createcontentattachmentpayload": "/enterprise-server@2.20/graphql/reference/objects#createcontentattachmentpayload", + "/enterprise/2.20/v4/object/createdcommitcontribution": "/enterprise-server@2.20/graphql/reference/objects#createdcommitcontribution", + "/enterprise/2.20/v4/object/createdcommitcontributionconnection": "/enterprise-server@2.20/graphql/reference/objects#createdcommitcontributionconnection", + "/enterprise/2.20/v4/object/createdcommitcontributionedge": "/enterprise-server@2.20/graphql/reference/objects#createdcommitcontributionedge", + "/enterprise/2.20/v4/object/createdeploymentpayload": "/enterprise-server@2.20/graphql/reference/objects#createdeploymentpayload", + "/enterprise/2.20/v4/object/createdeploymentstatuspayload": "/enterprise-server@2.20/graphql/reference/objects#createdeploymentstatuspayload", + "/enterprise/2.20/v4/object/createdissuecontribution": "/enterprise-server@2.20/graphql/reference/objects#createdissuecontribution", + "/enterprise/2.20/v4/object/createdissuecontributionconnection": "/enterprise-server@2.20/graphql/reference/objects#createdissuecontributionconnection", + "/enterprise/2.20/v4/object/createdissuecontributionedge": "/enterprise-server@2.20/graphql/reference/objects#createdissuecontributionedge", + "/enterprise/2.20/v4/object/createdpullrequestcontribution": "/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontribution", + "/enterprise/2.20/v4/object/createdpullrequestcontributionconnection": "/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontributionconnection", + "/enterprise/2.20/v4/object/createdpullrequestcontributionedge": "/enterprise-server@2.20/graphql/reference/objects#createdpullrequestcontributionedge", + "/enterprise/2.20/v4/object/createdpullrequestreviewcontribution": "/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontribution", + "/enterprise/2.20/v4/object/createdpullrequestreviewcontributionconnection": "/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontributionconnection", + "/enterprise/2.20/v4/object/createdpullrequestreviewcontributionedge": "/enterprise-server@2.20/graphql/reference/objects#createdpullrequestreviewcontributionedge", + "/enterprise/2.20/v4/object/createdrepositorycontribution": "/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontribution", + "/enterprise/2.20/v4/object/createdrepositorycontributionconnection": "/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontributionconnection", + "/enterprise/2.20/v4/object/createdrepositorycontributionedge": "/enterprise-server@2.20/graphql/reference/objects#createdrepositorycontributionedge", + "/enterprise/2.20/v4/object/createissuepayload": "/enterprise-server@2.20/graphql/reference/objects#createissuepayload", + "/enterprise/2.20/v4/object/createlabelpayload": "/enterprise-server@2.20/graphql/reference/objects#createlabelpayload", + "/enterprise/2.20/v4/object/createprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#createprojectpayload", + "/enterprise/2.20/v4/object/createpullrequestpayload": "/enterprise-server@2.20/graphql/reference/objects#createpullrequestpayload", + "/enterprise/2.20/v4/object/createrefpayload": "/enterprise-server@2.20/graphql/reference/objects#createrefpayload", + "/enterprise/2.20/v4/object/createrepositorypayload": "/enterprise-server@2.20/graphql/reference/objects#createrepositorypayload", + "/enterprise/2.20/v4/object/createteamdiscussioncommentpayload": "/enterprise-server@2.20/graphql/reference/objects#createteamdiscussioncommentpayload", + "/enterprise/2.20/v4/object/createteamdiscussionpayload": "/enterprise-server@2.20/graphql/reference/objects#createteamdiscussionpayload", + "/enterprise/2.20/v4/object/crossreferencedevent": "/enterprise-server@2.20/graphql/reference/objects#crossreferencedevent", + "/enterprise/2.20/v4/object/deletebranchprotectionrulepayload": "/enterprise-server@2.20/graphql/reference/objects#deletebranchprotectionrulepayload", + "/enterprise/2.20/v4/object/deleteissuecommentpayload": "/enterprise-server@2.20/graphql/reference/objects#deleteissuecommentpayload", + "/enterprise/2.20/v4/object/deleteissuepayload": "/enterprise-server@2.20/graphql/reference/objects#deleteissuepayload", + "/enterprise/2.20/v4/object/deletelabelpayload": "/enterprise-server@2.20/graphql/reference/objects#deletelabelpayload", + "/enterprise/2.20/v4/object/deleteprojectcardpayload": "/enterprise-server@2.20/graphql/reference/objects#deleteprojectcardpayload", + "/enterprise/2.20/v4/object/deleteprojectcolumnpayload": "/enterprise-server@2.20/graphql/reference/objects#deleteprojectcolumnpayload", + "/enterprise/2.20/v4/object/deleteprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#deleteprojectpayload", + "/enterprise/2.20/v4/object/deletepullrequestreviewcommentpayload": "/enterprise-server@2.20/graphql/reference/objects#deletepullrequestreviewcommentpayload", + "/enterprise/2.20/v4/object/deletepullrequestreviewpayload": "/enterprise-server@2.20/graphql/reference/objects#deletepullrequestreviewpayload", + "/enterprise/2.20/v4/object/deleterefpayload": "/enterprise-server@2.20/graphql/reference/objects#deleterefpayload", + "/enterprise/2.20/v4/object/deleteteamdiscussioncommentpayload": "/enterprise-server@2.20/graphql/reference/objects#deleteteamdiscussioncommentpayload", + "/enterprise/2.20/v4/object/deleteteamdiscussionpayload": "/enterprise-server@2.20/graphql/reference/objects#deleteteamdiscussionpayload", + "/enterprise/2.20/v4/object/demilestonedevent": "/enterprise-server@2.20/graphql/reference/objects#demilestonedevent", + "/enterprise/2.20/v4/object/deployedevent": "/enterprise-server@2.20/graphql/reference/objects#deployedevent", + "/enterprise/2.20/v4/object/deploykey": "/enterprise-server@2.20/graphql/reference/objects#deploykey", + "/enterprise/2.20/v4/object/deploykeyconnection": "/enterprise-server@2.20/graphql/reference/objects#deploykeyconnection", + "/enterprise/2.20/v4/object/deploykeyedge": "/enterprise-server@2.20/graphql/reference/objects#deploykeyedge", + "/enterprise/2.20/v4/object/deployment": "/enterprise-server@2.20/graphql/reference/objects#deployment", + "/enterprise/2.20/v4/object/deploymentconnection": "/enterprise-server@2.20/graphql/reference/objects#deploymentconnection", + "/enterprise/2.20/v4/object/deploymentedge": "/enterprise-server@2.20/graphql/reference/objects#deploymentedge", + "/enterprise/2.20/v4/object/deploymentenvironmentchangedevent": "/enterprise-server@2.20/graphql/reference/objects#deploymentenvironmentchangedevent", + "/enterprise/2.20/v4/object/deploymentstatus": "/enterprise-server@2.20/graphql/reference/objects#deploymentstatus", + "/enterprise/2.20/v4/object/deploymentstatusconnection": "/enterprise-server@2.20/graphql/reference/objects#deploymentstatusconnection", + "/enterprise/2.20/v4/object/deploymentstatusedge": "/enterprise-server@2.20/graphql/reference/objects#deploymentstatusedge", + "/enterprise/2.20/v4/object/dismisspullrequestreviewpayload": "/enterprise-server@2.20/graphql/reference/objects#dismisspullrequestreviewpayload", + "/enterprise/2.20/v4/object/enterprise": "/enterprise-server@2.20/graphql/reference/objects#enterprise", + "/enterprise/2.20/v4/object/enterpriseadministratorconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorconnection", + "/enterprise/2.20/v4/object/enterpriseadministratoredge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratoredge", + "/enterprise/2.20/v4/object/enterpriseadministratorinvitation": "/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitation", + "/enterprise/2.20/v4/object/enterpriseadministratorinvitationconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitationconnection", + "/enterprise/2.20/v4/object/enterpriseadministratorinvitationedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseadministratorinvitationedge", + "/enterprise/2.20/v4/object/enterprisebillinginfo": "/enterprise-server@2.20/graphql/reference/objects#enterprisebillinginfo", + "/enterprise/2.20/v4/object/enterpriseidentityprovider": "/enterprise-server@2.20/graphql/reference/objects#enterpriseidentityprovider", + "/enterprise/2.20/v4/object/enterprisememberconnection": "/enterprise-server@2.20/graphql/reference/objects#enterprisememberconnection", + "/enterprise/2.20/v4/object/enterprisememberedge": "/enterprise-server@2.20/graphql/reference/objects#enterprisememberedge", + "/enterprise/2.20/v4/object/enterpriseorganizationmembershipconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseorganizationmembershipconnection", + "/enterprise/2.20/v4/object/enterpriseorganizationmembershipedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseorganizationmembershipedge", + "/enterprise/2.20/v4/object/enterpriseoutsidecollaboratorconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", + "/enterprise/2.20/v4/object/enterpriseoutsidecollaboratoredge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseoutsidecollaboratoredge", + "/enterprise/2.20/v4/object/enterpriseownerinfo": "/enterprise-server@2.20/graphql/reference/objects#enterpriseownerinfo", + "/enterprise/2.20/v4/object/enterprisependingcollaboratorconnection": "/enterprise-server@2.20/graphql/reference/objects#enterprisependingcollaboratorconnection", + "/enterprise/2.20/v4/object/enterprisependingcollaboratoredge": "/enterprise-server@2.20/graphql/reference/objects#enterprisependingcollaboratoredge", + "/enterprise/2.20/v4/object/enterprisependingmemberinvitationconnection": "/enterprise-server@2.20/graphql/reference/objects#enterprisependingmemberinvitationconnection", + "/enterprise/2.20/v4/object/enterprisependingmemberinvitationedge": "/enterprise-server@2.20/graphql/reference/objects#enterprisependingmemberinvitationedge", + "/enterprise/2.20/v4/object/enterpriserepositoryinfo": "/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfo", + "/enterprise/2.20/v4/object/enterpriserepositoryinfoconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfoconnection", + "/enterprise/2.20/v4/object/enterpriserepositoryinfoedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriserepositoryinfoedge", + "/enterprise/2.20/v4/object/enterpriseserverinstallation": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserverinstallation", + "/enterprise/2.20/v4/object/enterpriseserveruseraccount": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccount", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountconnection", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountedge", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountemail": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemail", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountemailconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemailconnection", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountemailedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountemailedge", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountsupload": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsupload", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountsuploadconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", + "/enterprise/2.20/v4/object/enterpriseserveruseraccountsuploadedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", + "/enterprise/2.20/v4/object/enterpriseuseraccount": "/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccount", + "/enterprise/2.20/v4/object/enterpriseuseraccountconnection": "/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccountconnection", + "/enterprise/2.20/v4/object/enterpriseuseraccountedge": "/enterprise-server@2.20/graphql/reference/objects#enterpriseuseraccountedge", + "/enterprise/2.20/v4/object/externalidentity": "/enterprise-server@2.20/graphql/reference/objects#externalidentity", + "/enterprise/2.20/v4/object/externalidentityconnection": "/enterprise-server@2.20/graphql/reference/objects#externalidentityconnection", + "/enterprise/2.20/v4/object/externalidentityedge": "/enterprise-server@2.20/graphql/reference/objects#externalidentityedge", + "/enterprise/2.20/v4/object/externalidentitysamlattributes": "/enterprise-server@2.20/graphql/reference/objects#externalidentitysamlattributes", + "/enterprise/2.20/v4/object/externalidentityscimattributes": "/enterprise-server@2.20/graphql/reference/objects#externalidentityscimattributes", + "/enterprise/2.20/v4/object/followerconnection": "/enterprise-server@2.20/graphql/reference/objects#followerconnection", + "/enterprise/2.20/v4/object/followingconnection": "/enterprise-server@2.20/graphql/reference/objects#followingconnection", + "/enterprise/2.20/v4/object/followuserpayload": "/enterprise-server@2.20/graphql/reference/objects#followuserpayload", + "/enterprise/2.20/v4/object/generichovercardcontext": "/enterprise-server@2.20/graphql/reference/objects#generichovercardcontext", + "/enterprise/2.20/v4/object/gist": "/enterprise-server@2.20/graphql/reference/objects#gist", + "/enterprise/2.20/v4/object/gistcomment": "/enterprise-server@2.20/graphql/reference/objects#gistcomment", + "/enterprise/2.20/v4/object/gistcommentconnection": "/enterprise-server@2.20/graphql/reference/objects#gistcommentconnection", + "/enterprise/2.20/v4/object/gistcommentedge": "/enterprise-server@2.20/graphql/reference/objects#gistcommentedge", + "/enterprise/2.20/v4/object/gistconnection": "/enterprise-server@2.20/graphql/reference/objects#gistconnection", + "/enterprise/2.20/v4/object/gistedge": "/enterprise-server@2.20/graphql/reference/objects#gistedge", + "/enterprise/2.20/v4/object/gistfile": "/enterprise-server@2.20/graphql/reference/objects#gistfile", + "/enterprise/2.20/v4/object/gitactor": "/enterprise-server@2.20/graphql/reference/objects#gitactor", + "/enterprise/2.20/v4/object/githubmetadata": "/enterprise-server@2.20/graphql/reference/objects#githubmetadata", + "/enterprise/2.20/v4/object/gpgsignature": "/enterprise-server@2.20/graphql/reference/objects#gpgsignature", + "/enterprise/2.20/v4/object/headrefdeletedevent": "/enterprise-server@2.20/graphql/reference/objects#headrefdeletedevent", + "/enterprise/2.20/v4/object/headrefforcepushedevent": "/enterprise-server@2.20/graphql/reference/objects#headrefforcepushedevent", + "/enterprise/2.20/v4/object/headrefrestoredevent": "/enterprise-server@2.20/graphql/reference/objects#headrefrestoredevent", + "/enterprise/2.20/v4/object/hovercard": "/enterprise-server@2.20/graphql/reference/objects#hovercard", + "/enterprise/2.20/v4/object/importprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#importprojectpayload", + "/enterprise/2.20/v4/object/issue": "/enterprise-server@2.20/graphql/reference/objects#issue", + "/enterprise/2.20/v4/object/issuecomment": "/enterprise-server@2.20/graphql/reference/objects#issuecomment", + "/enterprise/2.20/v4/object/issuecommentconnection": "/enterprise-server@2.20/graphql/reference/objects#issuecommentconnection", + "/enterprise/2.20/v4/object/issuecommentedge": "/enterprise-server@2.20/graphql/reference/objects#issuecommentedge", + "/enterprise/2.20/v4/object/issueconnection": "/enterprise-server@2.20/graphql/reference/objects#issueconnection", + "/enterprise/2.20/v4/object/issuecontributionsbyrepository": "/enterprise-server@2.20/graphql/reference/objects#issuecontributionsbyrepository", + "/enterprise/2.20/v4/object/issueedge": "/enterprise-server@2.20/graphql/reference/objects#issueedge", + "/enterprise/2.20/v4/object/issuetimelineconnection": "/enterprise-server@2.20/graphql/reference/objects#issuetimelineconnection", + "/enterprise/2.20/v4/object/issuetimelineitemedge": "/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemedge", + "/enterprise/2.20/v4/object/issuetimelineitemsconnection": "/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemsconnection", + "/enterprise/2.20/v4/object/issuetimelineitemsedge": "/enterprise-server@2.20/graphql/reference/objects#issuetimelineitemsedge", + "/enterprise/2.20/v4/object/joinedgithubcontribution": "/enterprise-server@2.20/graphql/reference/objects#joinedgithubcontribution", + "/enterprise/2.20/v4/object/label": "/enterprise-server@2.20/graphql/reference/objects#label", + "/enterprise/2.20/v4/object/labelconnection": "/enterprise-server@2.20/graphql/reference/objects#labelconnection", + "/enterprise/2.20/v4/object/labeledevent": "/enterprise-server@2.20/graphql/reference/objects#labeledevent", + "/enterprise/2.20/v4/object/labeledge": "/enterprise-server@2.20/graphql/reference/objects#labeledge", + "/enterprise/2.20/v4/object/language": "/enterprise-server@2.20/graphql/reference/objects#language", + "/enterprise/2.20/v4/object/languageconnection": "/enterprise-server@2.20/graphql/reference/objects#languageconnection", + "/enterprise/2.20/v4/object/languageedge": "/enterprise-server@2.20/graphql/reference/objects#languageedge", + "/enterprise/2.20/v4/object/license": "/enterprise-server@2.20/graphql/reference/objects#license", + "/enterprise/2.20/v4/object/licenserule": "/enterprise-server@2.20/graphql/reference/objects#licenserule", + "/enterprise/2.20/v4/object/linkrepositorytoprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#linkrepositorytoprojectpayload", + "/enterprise/2.20/v4/object/lockedevent": "/enterprise-server@2.20/graphql/reference/objects#lockedevent", + "/enterprise/2.20/v4/object/locklockablepayload": "/enterprise-server@2.20/graphql/reference/objects#locklockablepayload", + "/enterprise/2.20/v4/object/mannequin": "/enterprise-server@2.20/graphql/reference/objects#mannequin", + "/enterprise/2.20/v4/object/markedasduplicateevent": "/enterprise-server@2.20/graphql/reference/objects#markedasduplicateevent", + "/enterprise/2.20/v4/object/markpullrequestreadyforreviewpayload": "/enterprise-server@2.20/graphql/reference/objects#markpullrequestreadyforreviewpayload", + "/enterprise/2.20/v4/object/memberscandeletereposclearauditentry": "/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposclearauditentry", + "/enterprise/2.20/v4/object/memberscandeletereposdisableauditentry": "/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposdisableauditentry", + "/enterprise/2.20/v4/object/memberscandeletereposenableauditentry": "/enterprise-server@2.20/graphql/reference/objects#memberscandeletereposenableauditentry", + "/enterprise/2.20/v4/object/mentionedevent": "/enterprise-server@2.20/graphql/reference/objects#mentionedevent", + "/enterprise/2.20/v4/object/mergebranchpayload": "/enterprise-server@2.20/graphql/reference/objects#mergebranchpayload", + "/enterprise/2.20/v4/object/mergedevent": "/enterprise-server@2.20/graphql/reference/objects#mergedevent", + "/enterprise/2.20/v4/object/mergepullrequestpayload": "/enterprise-server@2.20/graphql/reference/objects#mergepullrequestpayload", + "/enterprise/2.20/v4/object/milestone": "/enterprise-server@2.20/graphql/reference/objects#milestone", + "/enterprise/2.20/v4/object/milestoneconnection": "/enterprise-server@2.20/graphql/reference/objects#milestoneconnection", + "/enterprise/2.20/v4/object/milestonedevent": "/enterprise-server@2.20/graphql/reference/objects#milestonedevent", + "/enterprise/2.20/v4/object/milestoneedge": "/enterprise-server@2.20/graphql/reference/objects#milestoneedge", + "/enterprise/2.20/v4/object/minimizecommentpayload": "/enterprise-server@2.20/graphql/reference/objects#minimizecommentpayload", + "/enterprise/2.20/v4/object/movedcolumnsinprojectevent": "/enterprise-server@2.20/graphql/reference/objects#movedcolumnsinprojectevent", + "/enterprise/2.20/v4/object/moveprojectcardpayload": "/enterprise-server@2.20/graphql/reference/objects#moveprojectcardpayload", + "/enterprise/2.20/v4/object/moveprojectcolumnpayload": "/enterprise-server@2.20/graphql/reference/objects#moveprojectcolumnpayload", + "/enterprise/2.20/v4/object/oauthapplicationcreateauditentry": "/enterprise-server@2.20/graphql/reference/objects#oauthapplicationcreateauditentry", + "/enterprise/2.20/v4/object/orgaddbillingmanagerauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgaddbillingmanagerauditentry", + "/enterprise/2.20/v4/object/orgaddmemberauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgaddmemberauditentry", + "/enterprise/2.20/v4/object/organization": "/enterprise-server@2.20/graphql/reference/objects#organization", + "/enterprise/2.20/v4/object/organizationauditentryconnection": "/enterprise-server@2.20/graphql/reference/objects#organizationauditentryconnection", + "/enterprise/2.20/v4/object/organizationauditentryedge": "/enterprise-server@2.20/graphql/reference/objects#organizationauditentryedge", + "/enterprise/2.20/v4/object/organizationconnection": "/enterprise-server@2.20/graphql/reference/objects#organizationconnection", + "/enterprise/2.20/v4/object/organizationedge": "/enterprise-server@2.20/graphql/reference/objects#organizationedge", + "/enterprise/2.20/v4/object/organizationidentityprovider": "/enterprise-server@2.20/graphql/reference/objects#organizationidentityprovider", + "/enterprise/2.20/v4/object/organizationinvitation": "/enterprise-server@2.20/graphql/reference/objects#organizationinvitation", + "/enterprise/2.20/v4/object/organizationinvitationconnection": "/enterprise-server@2.20/graphql/reference/objects#organizationinvitationconnection", + "/enterprise/2.20/v4/object/organizationinvitationedge": "/enterprise-server@2.20/graphql/reference/objects#organizationinvitationedge", + "/enterprise/2.20/v4/object/organizationmemberconnection": "/enterprise-server@2.20/graphql/reference/objects#organizationmemberconnection", + "/enterprise/2.20/v4/object/organizationmemberedge": "/enterprise-server@2.20/graphql/reference/objects#organizationmemberedge", + "/enterprise/2.20/v4/object/organizationshovercardcontext": "/enterprise-server@2.20/graphql/reference/objects#organizationshovercardcontext", + "/enterprise/2.20/v4/object/organizationteamshovercardcontext": "/enterprise-server@2.20/graphql/reference/objects#organizationteamshovercardcontext", + "/enterprise/2.20/v4/object/orgblockuserauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgblockuserauditentry", + "/enterprise/2.20/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", + "/enterprise/2.20/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", + "/enterprise/2.20/v4/object/orgcreateauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgcreateauditentry", + "/enterprise/2.20/v4/object/orgdisableoauthapprestrictionsauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", + "/enterprise/2.20/v4/object/orgdisablesamlauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgdisablesamlauditentry", + "/enterprise/2.20/v4/object/orgdisabletwofactorrequirementauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", + "/enterprise/2.20/v4/object/orgenableoauthapprestrictionsauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", + "/enterprise/2.20/v4/object/orgenablesamlauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgenablesamlauditentry", + "/enterprise/2.20/v4/object/orgenabletwofactorrequirementauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgenabletwofactorrequirementauditentry", + "/enterprise/2.20/v4/object/orginvitememberauditentry": "/enterprise-server@2.20/graphql/reference/objects#orginvitememberauditentry", + "/enterprise/2.20/v4/object/orginvitetobusinessauditentry": "/enterprise-server@2.20/graphql/reference/objects#orginvitetobusinessauditentry", + "/enterprise/2.20/v4/object/orgoauthappaccessapprovedauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessapprovedauditentry", + "/enterprise/2.20/v4/object/orgoauthappaccessdeniedauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessdeniedauditentry", + "/enterprise/2.20/v4/object/orgoauthappaccessrequestedauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgoauthappaccessrequestedauditentry", + "/enterprise/2.20/v4/object/orgremovebillingmanagerauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgremovebillingmanagerauditentry", + "/enterprise/2.20/v4/object/orgremovememberauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgremovememberauditentry", + "/enterprise/2.20/v4/object/orgremoveoutsidecollaboratorauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", + "/enterprise/2.20/v4/object/orgrestorememberauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgrestorememberauditentry", + "/enterprise/2.20/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", + "/enterprise/2.20/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", + "/enterprise/2.20/v4/object/orgrestoremembermembershipteamauditentrydata": "/enterprise-server@2.20/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", + "/enterprise/2.20/v4/object/orgunblockuserauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgunblockuserauditentry", + "/enterprise/2.20/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", + "/enterprise/2.20/v4/object/orgupdatememberauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgupdatememberauditentry", + "/enterprise/2.20/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", + "/enterprise/2.20/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/enterprise-server@2.20/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", + "/enterprise/2.20/v4/object/package": "/enterprise-server@2.20/graphql/reference/objects#package", + "/enterprise/2.20/v4/object/packageconnection": "/enterprise-server@2.20/graphql/reference/objects#packageconnection", + "/enterprise/2.20/v4/object/packageedge": "/enterprise-server@2.20/graphql/reference/objects#packageedge", + "/enterprise/2.20/v4/object/packagefile": "/enterprise-server@2.20/graphql/reference/objects#packagefile", + "/enterprise/2.20/v4/object/packagefileconnection": "/enterprise-server@2.20/graphql/reference/objects#packagefileconnection", + "/enterprise/2.20/v4/object/packagefileedge": "/enterprise-server@2.20/graphql/reference/objects#packagefileedge", + "/enterprise/2.20/v4/object/packagestatistics": "/enterprise-server@2.20/graphql/reference/objects#packagestatistics", + "/enterprise/2.20/v4/object/packagetag": "/enterprise-server@2.20/graphql/reference/objects#packagetag", + "/enterprise/2.20/v4/object/packageversion": "/enterprise-server@2.20/graphql/reference/objects#packageversion", + "/enterprise/2.20/v4/object/packageversionconnection": "/enterprise-server@2.20/graphql/reference/objects#packageversionconnection", + "/enterprise/2.20/v4/object/packageversionedge": "/enterprise-server@2.20/graphql/reference/objects#packageversionedge", + "/enterprise/2.20/v4/object/packageversionstatistics": "/enterprise-server@2.20/graphql/reference/objects#packageversionstatistics", + "/enterprise/2.20/v4/object/pageinfo": "/enterprise-server@2.20/graphql/reference/objects#pageinfo", + "/enterprise/2.20/v4/object/permissionsource": "/enterprise-server@2.20/graphql/reference/objects#permissionsource", + "/enterprise/2.20/v4/object/pinissuepayload": "/enterprise-server@2.20/graphql/reference/objects#pinissuepayload", + "/enterprise/2.20/v4/object/pinnableitemconnection": "/enterprise-server@2.20/graphql/reference/objects#pinnableitemconnection", + "/enterprise/2.20/v4/object/pinnableitemedge": "/enterprise-server@2.20/graphql/reference/objects#pinnableitemedge", + "/enterprise/2.20/v4/object/pinnedevent": "/enterprise-server@2.20/graphql/reference/objects#pinnedevent", + "/enterprise/2.20/v4/object/pinnedissue": "/enterprise-server@2.20/graphql/reference/objects#pinnedissue", + "/enterprise/2.20/v4/object/pinnedissueconnection": "/enterprise-server@2.20/graphql/reference/objects#pinnedissueconnection", + "/enterprise/2.20/v4/object/pinnedissueedge": "/enterprise-server@2.20/graphql/reference/objects#pinnedissueedge", + "/enterprise/2.20/v4/object/privaterepositoryforkingdisableauditentry": "/enterprise-server@2.20/graphql/reference/objects#privaterepositoryforkingdisableauditentry", + "/enterprise/2.20/v4/object/privaterepositoryforkingenableauditentry": "/enterprise-server@2.20/graphql/reference/objects#privaterepositoryforkingenableauditentry", + "/enterprise/2.20/v4/object/profileitemshowcase": "/enterprise-server@2.20/graphql/reference/objects#profileitemshowcase", + "/enterprise/2.20/v4/object/project": "/enterprise-server@2.20/graphql/reference/objects#project", + "/enterprise/2.20/v4/object/projectcard": "/enterprise-server@2.20/graphql/reference/objects#projectcard", + "/enterprise/2.20/v4/object/projectcardconnection": "/enterprise-server@2.20/graphql/reference/objects#projectcardconnection", + "/enterprise/2.20/v4/object/projectcardedge": "/enterprise-server@2.20/graphql/reference/objects#projectcardedge", + "/enterprise/2.20/v4/object/projectcolumn": "/enterprise-server@2.20/graphql/reference/objects#projectcolumn", + "/enterprise/2.20/v4/object/projectcolumnconnection": "/enterprise-server@2.20/graphql/reference/objects#projectcolumnconnection", + "/enterprise/2.20/v4/object/projectcolumnedge": "/enterprise-server@2.20/graphql/reference/objects#projectcolumnedge", + "/enterprise/2.20/v4/object/projectconnection": "/enterprise-server@2.20/graphql/reference/objects#projectconnection", + "/enterprise/2.20/v4/object/projectedge": "/enterprise-server@2.20/graphql/reference/objects#projectedge", + "/enterprise/2.20/v4/object/publickey": "/enterprise-server@2.20/graphql/reference/objects#publickey", + "/enterprise/2.20/v4/object/publickeyconnection": "/enterprise-server@2.20/graphql/reference/objects#publickeyconnection", + "/enterprise/2.20/v4/object/publickeyedge": "/enterprise-server@2.20/graphql/reference/objects#publickeyedge", + "/enterprise/2.20/v4/object/pullrequest": "/enterprise-server@2.20/graphql/reference/objects#pullrequest", + "/enterprise/2.20/v4/object/pullrequestchangedfile": "/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfile", + "/enterprise/2.20/v4/object/pullrequestchangedfileconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfileconnection", + "/enterprise/2.20/v4/object/pullrequestchangedfileedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequestchangedfileedge", + "/enterprise/2.20/v4/object/pullrequestcommit": "/enterprise-server@2.20/graphql/reference/objects#pullrequestcommit", + "/enterprise/2.20/v4/object/pullrequestcommitcommentthread": "/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitcommentthread", + "/enterprise/2.20/v4/object/pullrequestcommitconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitconnection", + "/enterprise/2.20/v4/object/pullrequestcommitedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequestcommitedge", + "/enterprise/2.20/v4/object/pullrequestconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequestconnection", + "/enterprise/2.20/v4/object/pullrequestcontributionsbyrepository": "/enterprise-server@2.20/graphql/reference/objects#pullrequestcontributionsbyrepository", + "/enterprise/2.20/v4/object/pullrequestedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequestedge", + "/enterprise/2.20/v4/object/pullrequestreview": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreview", + "/enterprise/2.20/v4/object/pullrequestreviewcomment": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcomment", + "/enterprise/2.20/v4/object/pullrequestreviewcommentconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcommentconnection", + "/enterprise/2.20/v4/object/pullrequestreviewcommentedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcommentedge", + "/enterprise/2.20/v4/object/pullrequestreviewconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewconnection", + "/enterprise/2.20/v4/object/pullrequestreviewcontributionsbyrepository": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", + "/enterprise/2.20/v4/object/pullrequestreviewedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewedge", + "/enterprise/2.20/v4/object/pullrequestreviewthread": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthread", + "/enterprise/2.20/v4/object/pullrequestreviewthreadconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthreadconnection", + "/enterprise/2.20/v4/object/pullrequestreviewthreadedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequestreviewthreadedge", + "/enterprise/2.20/v4/object/pullrequestrevisionmarker": "/enterprise-server@2.20/graphql/reference/objects#pullrequestrevisionmarker", + "/enterprise/2.20/v4/object/pullrequesttimelineconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineconnection", + "/enterprise/2.20/v4/object/pullrequesttimelineitemedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemedge", + "/enterprise/2.20/v4/object/pullrequesttimelineitemsconnection": "/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemsconnection", + "/enterprise/2.20/v4/object/pullrequesttimelineitemsedge": "/enterprise-server@2.20/graphql/reference/objects#pullrequesttimelineitemsedge", + "/enterprise/2.20/v4/object/push": "/enterprise-server@2.20/graphql/reference/objects#push", + "/enterprise/2.20/v4/object/pushallowance": "/enterprise-server@2.20/graphql/reference/objects#pushallowance", + "/enterprise/2.20/v4/object/pushallowanceconnection": "/enterprise-server@2.20/graphql/reference/objects#pushallowanceconnection", + "/enterprise/2.20/v4/object/pushallowanceedge": "/enterprise-server@2.20/graphql/reference/objects#pushallowanceedge", + "/enterprise/2.20/v4/object/ratelimit": "/enterprise-server@2.20/graphql/reference/objects#ratelimit", + "/enterprise/2.20/v4/object/reactinguserconnection": "/enterprise-server@2.20/graphql/reference/objects#reactinguserconnection", + "/enterprise/2.20/v4/object/reactinguseredge": "/enterprise-server@2.20/graphql/reference/objects#reactinguseredge", + "/enterprise/2.20/v4/object/reaction": "/enterprise-server@2.20/graphql/reference/objects#reaction", + "/enterprise/2.20/v4/object/reactionconnection": "/enterprise-server@2.20/graphql/reference/objects#reactionconnection", + "/enterprise/2.20/v4/object/reactionedge": "/enterprise-server@2.20/graphql/reference/objects#reactionedge", + "/enterprise/2.20/v4/object/reactiongroup": "/enterprise-server@2.20/graphql/reference/objects#reactiongroup", + "/enterprise/2.20/v4/object/readyforreviewevent": "/enterprise-server@2.20/graphql/reference/objects#readyforreviewevent", + "/enterprise/2.20/v4/object/ref": "/enterprise-server@2.20/graphql/reference/objects#ref", + "/enterprise/2.20/v4/object/refconnection": "/enterprise-server@2.20/graphql/reference/objects#refconnection", + "/enterprise/2.20/v4/object/refedge": "/enterprise-server@2.20/graphql/reference/objects#refedge", + "/enterprise/2.20/v4/object/referencedevent": "/enterprise-server@2.20/graphql/reference/objects#referencedevent", + "/enterprise/2.20/v4/object/registrypackage": "/enterprise-server@2.20/graphql/reference/objects#registrypackage", + "/enterprise/2.20/v4/object/registrypackageconnection": "/enterprise-server@2.20/graphql/reference/objects#registrypackageconnection", + "/enterprise/2.20/v4/object/registrypackagedependency": "/enterprise-server@2.20/graphql/reference/objects#registrypackagedependency", + "/enterprise/2.20/v4/object/registrypackagedependencyconnection": "/enterprise-server@2.20/graphql/reference/objects#registrypackagedependencyconnection", + "/enterprise/2.20/v4/object/registrypackagedependencyedge": "/enterprise-server@2.20/graphql/reference/objects#registrypackagedependencyedge", + "/enterprise/2.20/v4/object/registrypackageedge": "/enterprise-server@2.20/graphql/reference/objects#registrypackageedge", + "/enterprise/2.20/v4/object/registrypackagefile": "/enterprise-server@2.20/graphql/reference/objects#registrypackagefile", + "/enterprise/2.20/v4/object/registrypackagefileconnection": "/enterprise-server@2.20/graphql/reference/objects#registrypackagefileconnection", + "/enterprise/2.20/v4/object/registrypackagefileedge": "/enterprise-server@2.20/graphql/reference/objects#registrypackagefileedge", + "/enterprise/2.20/v4/object/registrypackagestatistics": "/enterprise-server@2.20/graphql/reference/objects#registrypackagestatistics", + "/enterprise/2.20/v4/object/registrypackagetag": "/enterprise-server@2.20/graphql/reference/objects#registrypackagetag", + "/enterprise/2.20/v4/object/registrypackagetagconnection": "/enterprise-server@2.20/graphql/reference/objects#registrypackagetagconnection", + "/enterprise/2.20/v4/object/registrypackagetagedge": "/enterprise-server@2.20/graphql/reference/objects#registrypackagetagedge", + "/enterprise/2.20/v4/object/registrypackageversion": "/enterprise-server@2.20/graphql/reference/objects#registrypackageversion", + "/enterprise/2.20/v4/object/registrypackageversionconnection": "/enterprise-server@2.20/graphql/reference/objects#registrypackageversionconnection", + "/enterprise/2.20/v4/object/registrypackageversionedge": "/enterprise-server@2.20/graphql/reference/objects#registrypackageversionedge", + "/enterprise/2.20/v4/object/registrypackageversionstatistics": "/enterprise-server@2.20/graphql/reference/objects#registrypackageversionstatistics", + "/enterprise/2.20/v4/object/release": "/enterprise-server@2.20/graphql/reference/objects#release", + "/enterprise/2.20/v4/object/releaseasset": "/enterprise-server@2.20/graphql/reference/objects#releaseasset", + "/enterprise/2.20/v4/object/releaseassetconnection": "/enterprise-server@2.20/graphql/reference/objects#releaseassetconnection", + "/enterprise/2.20/v4/object/releaseassetedge": "/enterprise-server@2.20/graphql/reference/objects#releaseassetedge", + "/enterprise/2.20/v4/object/releaseconnection": "/enterprise-server@2.20/graphql/reference/objects#releaseconnection", + "/enterprise/2.20/v4/object/releaseedge": "/enterprise-server@2.20/graphql/reference/objects#releaseedge", + "/enterprise/2.20/v4/object/removeassigneesfromassignablepayload": "/enterprise-server@2.20/graphql/reference/objects#removeassigneesfromassignablepayload", + "/enterprise/2.20/v4/object/removedfromprojectevent": "/enterprise-server@2.20/graphql/reference/objects#removedfromprojectevent", + "/enterprise/2.20/v4/object/removeenterpriseadminpayload": "/enterprise-server@2.20/graphql/reference/objects#removeenterpriseadminpayload", + "/enterprise/2.20/v4/object/removelabelsfromlabelablepayload": "/enterprise-server@2.20/graphql/reference/objects#removelabelsfromlabelablepayload", + "/enterprise/2.20/v4/object/removeoutsidecollaboratorpayload": "/enterprise-server@2.20/graphql/reference/objects#removeoutsidecollaboratorpayload", + "/enterprise/2.20/v4/object/removereactionpayload": "/enterprise-server@2.20/graphql/reference/objects#removereactionpayload", + "/enterprise/2.20/v4/object/removestarpayload": "/enterprise-server@2.20/graphql/reference/objects#removestarpayload", + "/enterprise/2.20/v4/object/renamedtitleevent": "/enterprise-server@2.20/graphql/reference/objects#renamedtitleevent", + "/enterprise/2.20/v4/object/reopenedevent": "/enterprise-server@2.20/graphql/reference/objects#reopenedevent", + "/enterprise/2.20/v4/object/reopenissuepayload": "/enterprise-server@2.20/graphql/reference/objects#reopenissuepayload", + "/enterprise/2.20/v4/object/reopenpullrequestpayload": "/enterprise-server@2.20/graphql/reference/objects#reopenpullrequestpayload", + "/enterprise/2.20/v4/object/repoaccessauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoaccessauditentry", + "/enterprise/2.20/v4/object/repoaddmemberauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoaddmemberauditentry", + "/enterprise/2.20/v4/object/repoaddtopicauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoaddtopicauditentry", + "/enterprise/2.20/v4/object/repoarchivedauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoarchivedauditentry", + "/enterprise/2.20/v4/object/repochangemergesettingauditentry": "/enterprise-server@2.20/graphql/reference/objects#repochangemergesettingauditentry", + "/enterprise/2.20/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", + "/enterprise/2.20/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", + "/enterprise/2.20/v4/object/repoconfigdisablecontributorsonlyauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", + "/enterprise/2.20/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", + "/enterprise/2.20/v4/object/repoconfigenableanonymousgitaccessauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", + "/enterprise/2.20/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", + "/enterprise/2.20/v4/object/repoconfigenablecontributorsonlyauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", + "/enterprise/2.20/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", + "/enterprise/2.20/v4/object/repoconfiglockanonymousgitaccessauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", + "/enterprise/2.20/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/enterprise-server@2.20/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", + "/enterprise/2.20/v4/object/repocreateauditentry": "/enterprise-server@2.20/graphql/reference/objects#repocreateauditentry", + "/enterprise/2.20/v4/object/repodestroyauditentry": "/enterprise-server@2.20/graphql/reference/objects#repodestroyauditentry", + "/enterprise/2.20/v4/object/reporemovememberauditentry": "/enterprise-server@2.20/graphql/reference/objects#reporemovememberauditentry", + "/enterprise/2.20/v4/object/reporemovetopicauditentry": "/enterprise-server@2.20/graphql/reference/objects#reporemovetopicauditentry", + "/enterprise/2.20/v4/object/repository": "/enterprise-server@2.20/graphql/reference/objects#repository", + "/enterprise/2.20/v4/object/repositorycollaboratorconnection": "/enterprise-server@2.20/graphql/reference/objects#repositorycollaboratorconnection", + "/enterprise/2.20/v4/object/repositorycollaboratoredge": "/enterprise-server@2.20/graphql/reference/objects#repositorycollaboratoredge", + "/enterprise/2.20/v4/object/repositoryconnection": "/enterprise-server@2.20/graphql/reference/objects#repositoryconnection", + "/enterprise/2.20/v4/object/repositoryedge": "/enterprise-server@2.20/graphql/reference/objects#repositoryedge", + "/enterprise/2.20/v4/object/repositoryinvitation": "/enterprise-server@2.20/graphql/reference/objects#repositoryinvitation", + "/enterprise/2.20/v4/object/repositorytopic": "/enterprise-server@2.20/graphql/reference/objects#repositorytopic", + "/enterprise/2.20/v4/object/repositorytopicconnection": "/enterprise-server@2.20/graphql/reference/objects#repositorytopicconnection", + "/enterprise/2.20/v4/object/repositorytopicedge": "/enterprise-server@2.20/graphql/reference/objects#repositorytopicedge", + "/enterprise/2.20/v4/object/repositoryvisibilitychangedisableauditentry": "/enterprise-server@2.20/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", + "/enterprise/2.20/v4/object/repositoryvisibilitychangeenableauditentry": "/enterprise-server@2.20/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", + "/enterprise/2.20/v4/object/repositoryvulnerabilityalert": "/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalert", + "/enterprise/2.20/v4/object/repositoryvulnerabilityalertconnection": "/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalertconnection", + "/enterprise/2.20/v4/object/repositoryvulnerabilityalertedge": "/enterprise-server@2.20/graphql/reference/objects#repositoryvulnerabilityalertedge", + "/enterprise/2.20/v4/object/requestreviewspayload": "/enterprise-server@2.20/graphql/reference/objects#requestreviewspayload", + "/enterprise/2.20/v4/object/rerequestchecksuitepayload": "/enterprise-server@2.20/graphql/reference/objects#rerequestchecksuitepayload", + "/enterprise/2.20/v4/object/resolvereviewthreadpayload": "/enterprise-server@2.20/graphql/reference/objects#resolvereviewthreadpayload", + "/enterprise/2.20/v4/object/restrictedcontribution": "/enterprise-server@2.20/graphql/reference/objects#restrictedcontribution", + "/enterprise/2.20/v4/object/reviewdismissalallowance": "/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowance", + "/enterprise/2.20/v4/object/reviewdismissalallowanceconnection": "/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowanceconnection", + "/enterprise/2.20/v4/object/reviewdismissalallowanceedge": "/enterprise-server@2.20/graphql/reference/objects#reviewdismissalallowanceedge", + "/enterprise/2.20/v4/object/reviewdismissedevent": "/enterprise-server@2.20/graphql/reference/objects#reviewdismissedevent", + "/enterprise/2.20/v4/object/reviewrequest": "/enterprise-server@2.20/graphql/reference/objects#reviewrequest", + "/enterprise/2.20/v4/object/reviewrequestconnection": "/enterprise-server@2.20/graphql/reference/objects#reviewrequestconnection", + "/enterprise/2.20/v4/object/reviewrequestedevent": "/enterprise-server@2.20/graphql/reference/objects#reviewrequestedevent", + "/enterprise/2.20/v4/object/reviewrequestedge": "/enterprise-server@2.20/graphql/reference/objects#reviewrequestedge", + "/enterprise/2.20/v4/object/reviewrequestremovedevent": "/enterprise-server@2.20/graphql/reference/objects#reviewrequestremovedevent", + "/enterprise/2.20/v4/object/reviewstatushovercardcontext": "/enterprise-server@2.20/graphql/reference/objects#reviewstatushovercardcontext", + "/enterprise/2.20/v4/object/savedreply": "/enterprise-server@2.20/graphql/reference/objects#savedreply", + "/enterprise/2.20/v4/object/savedreplyconnection": "/enterprise-server@2.20/graphql/reference/objects#savedreplyconnection", + "/enterprise/2.20/v4/object/savedreplyedge": "/enterprise-server@2.20/graphql/reference/objects#savedreplyedge", + "/enterprise/2.20/v4/object/searchresultitemconnection": "/enterprise-server@2.20/graphql/reference/objects#searchresultitemconnection", + "/enterprise/2.20/v4/object/searchresultitemedge": "/enterprise-server@2.20/graphql/reference/objects#searchresultitemedge", + "/enterprise/2.20/v4/object/securityadvisory": "/enterprise-server@2.20/graphql/reference/objects#securityadvisory", + "/enterprise/2.20/v4/object/securityadvisoryconnection": "/enterprise-server@2.20/graphql/reference/objects#securityadvisoryconnection", + "/enterprise/2.20/v4/object/securityadvisoryedge": "/enterprise-server@2.20/graphql/reference/objects#securityadvisoryedge", + "/enterprise/2.20/v4/object/securityadvisoryidentifier": "/enterprise-server@2.20/graphql/reference/objects#securityadvisoryidentifier", + "/enterprise/2.20/v4/object/securityadvisorypackage": "/enterprise-server@2.20/graphql/reference/objects#securityadvisorypackage", + "/enterprise/2.20/v4/object/securityadvisorypackageversion": "/enterprise-server@2.20/graphql/reference/objects#securityadvisorypackageversion", + "/enterprise/2.20/v4/object/securityadvisoryreference": "/enterprise-server@2.20/graphql/reference/objects#securityadvisoryreference", + "/enterprise/2.20/v4/object/securityvulnerability": "/enterprise-server@2.20/graphql/reference/objects#securityvulnerability", + "/enterprise/2.20/v4/object/securityvulnerabilityconnection": "/enterprise-server@2.20/graphql/reference/objects#securityvulnerabilityconnection", + "/enterprise/2.20/v4/object/securityvulnerabilityedge": "/enterprise-server@2.20/graphql/reference/objects#securityvulnerabilityedge", + "/enterprise/2.20/v4/object/smimesignature": "/enterprise-server@2.20/graphql/reference/objects#smimesignature", + "/enterprise/2.20/v4/object/sponsorship": "/enterprise-server@2.20/graphql/reference/objects#sponsorship", + "/enterprise/2.20/v4/object/sponsorshipconnection": "/enterprise-server@2.20/graphql/reference/objects#sponsorshipconnection", + "/enterprise/2.20/v4/object/sponsorshipedge": "/enterprise-server@2.20/graphql/reference/objects#sponsorshipedge", + "/enterprise/2.20/v4/object/stargazerconnection": "/enterprise-server@2.20/graphql/reference/objects#stargazerconnection", + "/enterprise/2.20/v4/object/stargazeredge": "/enterprise-server@2.20/graphql/reference/objects#stargazeredge", + "/enterprise/2.20/v4/object/starredrepositoryconnection": "/enterprise-server@2.20/graphql/reference/objects#starredrepositoryconnection", + "/enterprise/2.20/v4/object/starredrepositoryedge": "/enterprise-server@2.20/graphql/reference/objects#starredrepositoryedge", + "/enterprise/2.20/v4/object/status": "/enterprise-server@2.20/graphql/reference/objects#status", + "/enterprise/2.20/v4/object/statuscontext": "/enterprise-server@2.20/graphql/reference/objects#statuscontext", + "/enterprise/2.20/v4/object/submitpullrequestreviewpayload": "/enterprise-server@2.20/graphql/reference/objects#submitpullrequestreviewpayload", + "/enterprise/2.20/v4/object/subscribedevent": "/enterprise-server@2.20/graphql/reference/objects#subscribedevent", + "/enterprise/2.20/v4/object/suggestedreviewer": "/enterprise-server@2.20/graphql/reference/objects#suggestedreviewer", + "/enterprise/2.20/v4/object/tag": "/enterprise-server@2.20/graphql/reference/objects#tag", + "/enterprise/2.20/v4/object/team": "/enterprise-server@2.20/graphql/reference/objects#team", + "/enterprise/2.20/v4/object/teamaddmemberauditentry": "/enterprise-server@2.20/graphql/reference/objects#teamaddmemberauditentry", + "/enterprise/2.20/v4/object/teamaddrepositoryauditentry": "/enterprise-server@2.20/graphql/reference/objects#teamaddrepositoryauditentry", + "/enterprise/2.20/v4/object/teamchangeparentteamauditentry": "/enterprise-server@2.20/graphql/reference/objects#teamchangeparentteamauditentry", + "/enterprise/2.20/v4/object/teamconnection": "/enterprise-server@2.20/graphql/reference/objects#teamconnection", + "/enterprise/2.20/v4/object/teamdiscussion": "/enterprise-server@2.20/graphql/reference/objects#teamdiscussion", + "/enterprise/2.20/v4/object/teamdiscussioncomment": "/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncomment", + "/enterprise/2.20/v4/object/teamdiscussioncommentconnection": "/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncommentconnection", + "/enterprise/2.20/v4/object/teamdiscussioncommentedge": "/enterprise-server@2.20/graphql/reference/objects#teamdiscussioncommentedge", + "/enterprise/2.20/v4/object/teamdiscussionconnection": "/enterprise-server@2.20/graphql/reference/objects#teamdiscussionconnection", + "/enterprise/2.20/v4/object/teamdiscussionedge": "/enterprise-server@2.20/graphql/reference/objects#teamdiscussionedge", + "/enterprise/2.20/v4/object/teamedge": "/enterprise-server@2.20/graphql/reference/objects#teamedge", + "/enterprise/2.20/v4/object/teammemberconnection": "/enterprise-server@2.20/graphql/reference/objects#teammemberconnection", + "/enterprise/2.20/v4/object/teammemberedge": "/enterprise-server@2.20/graphql/reference/objects#teammemberedge", + "/enterprise/2.20/v4/object/teamremovememberauditentry": "/enterprise-server@2.20/graphql/reference/objects#teamremovememberauditentry", + "/enterprise/2.20/v4/object/teamremoverepositoryauditentry": "/enterprise-server@2.20/graphql/reference/objects#teamremoverepositoryauditentry", + "/enterprise/2.20/v4/object/teamrepositoryconnection": "/enterprise-server@2.20/graphql/reference/objects#teamrepositoryconnection", + "/enterprise/2.20/v4/object/teamrepositoryedge": "/enterprise-server@2.20/graphql/reference/objects#teamrepositoryedge", + "/enterprise/2.20/v4/object/textmatch": "/enterprise-server@2.20/graphql/reference/objects#textmatch", + "/enterprise/2.20/v4/object/textmatchhighlight": "/enterprise-server@2.20/graphql/reference/objects#textmatchhighlight", + "/enterprise/2.20/v4/object/topic": "/enterprise-server@2.20/graphql/reference/objects#topic", + "/enterprise/2.20/v4/object/topicconnection": "/enterprise-server@2.20/graphql/reference/objects#topicconnection", + "/enterprise/2.20/v4/object/topicedge": "/enterprise-server@2.20/graphql/reference/objects#topicedge", + "/enterprise/2.20/v4/object/transferissuepayload": "/enterprise-server@2.20/graphql/reference/objects#transferissuepayload", + "/enterprise/2.20/v4/object/transferredevent": "/enterprise-server@2.20/graphql/reference/objects#transferredevent", + "/enterprise/2.20/v4/object/tree": "/enterprise-server@2.20/graphql/reference/objects#tree", + "/enterprise/2.20/v4/object/treeentry": "/enterprise-server@2.20/graphql/reference/objects#treeentry", + "/enterprise/2.20/v4/object/unarchiverepositorypayload": "/enterprise-server@2.20/graphql/reference/objects#unarchiverepositorypayload", + "/enterprise/2.20/v4/object/unassignedevent": "/enterprise-server@2.20/graphql/reference/objects#unassignedevent", + "/enterprise/2.20/v4/object/unfollowuserpayload": "/enterprise-server@2.20/graphql/reference/objects#unfollowuserpayload", + "/enterprise/2.20/v4/object/unknownsignature": "/enterprise-server@2.20/graphql/reference/objects#unknownsignature", + "/enterprise/2.20/v4/object/unlabeledevent": "/enterprise-server@2.20/graphql/reference/objects#unlabeledevent", + "/enterprise/2.20/v4/object/unlinkrepositoryfromprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#unlinkrepositoryfromprojectpayload", + "/enterprise/2.20/v4/object/unlockedevent": "/enterprise-server@2.20/graphql/reference/objects#unlockedevent", + "/enterprise/2.20/v4/object/unlocklockablepayload": "/enterprise-server@2.20/graphql/reference/objects#unlocklockablepayload", + "/enterprise/2.20/v4/object/unmarkissueasduplicatepayload": "/enterprise-server@2.20/graphql/reference/objects#unmarkissueasduplicatepayload", + "/enterprise/2.20/v4/object/unminimizecommentpayload": "/enterprise-server@2.20/graphql/reference/objects#unminimizecommentpayload", + "/enterprise/2.20/v4/object/unpinissuepayload": "/enterprise-server@2.20/graphql/reference/objects#unpinissuepayload", + "/enterprise/2.20/v4/object/unpinnedevent": "/enterprise-server@2.20/graphql/reference/objects#unpinnedevent", + "/enterprise/2.20/v4/object/unresolvereviewthreadpayload": "/enterprise-server@2.20/graphql/reference/objects#unresolvereviewthreadpayload", + "/enterprise/2.20/v4/object/unsubscribedevent": "/enterprise-server@2.20/graphql/reference/objects#unsubscribedevent", + "/enterprise/2.20/v4/object/updatebranchprotectionrulepayload": "/enterprise-server@2.20/graphql/reference/objects#updatebranchprotectionrulepayload", + "/enterprise/2.20/v4/object/updatecheckrunpayload": "/enterprise-server@2.20/graphql/reference/objects#updatecheckrunpayload", + "/enterprise/2.20/v4/object/updatechecksuitepreferencespayload": "/enterprise-server@2.20/graphql/reference/objects#updatechecksuitepreferencespayload", + "/enterprise/2.20/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", + "/enterprise/2.20/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", + "/enterprise/2.20/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", + "/enterprise/2.20/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", + "/enterprise/2.20/v4/object/updateenterpriseorganizationprojectssettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", + "/enterprise/2.20/v4/object/updateenterpriseprofilepayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterpriseprofilepayload", + "/enterprise/2.20/v4/object/updateenterpriserepositoryprojectssettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", + "/enterprise/2.20/v4/object/updateenterpriseteamdiscussionssettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", + "/enterprise/2.20/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/enterprise-server@2.20/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", + "/enterprise/2.20/v4/object/updateissuecommentpayload": "/enterprise-server@2.20/graphql/reference/objects#updateissuecommentpayload", + "/enterprise/2.20/v4/object/updateissuepayload": "/enterprise-server@2.20/graphql/reference/objects#updateissuepayload", + "/enterprise/2.20/v4/object/updatelabelpayload": "/enterprise-server@2.20/graphql/reference/objects#updatelabelpayload", + "/enterprise/2.20/v4/object/updateprojectcardpayload": "/enterprise-server@2.20/graphql/reference/objects#updateprojectcardpayload", + "/enterprise/2.20/v4/object/updateprojectcolumnpayload": "/enterprise-server@2.20/graphql/reference/objects#updateprojectcolumnpayload", + "/enterprise/2.20/v4/object/updateprojectpayload": "/enterprise-server@2.20/graphql/reference/objects#updateprojectpayload", + "/enterprise/2.20/v4/object/updatepullrequestpayload": "/enterprise-server@2.20/graphql/reference/objects#updatepullrequestpayload", + "/enterprise/2.20/v4/object/updatepullrequestreviewcommentpayload": "/enterprise-server@2.20/graphql/reference/objects#updatepullrequestreviewcommentpayload", + "/enterprise/2.20/v4/object/updatepullrequestreviewpayload": "/enterprise-server@2.20/graphql/reference/objects#updatepullrequestreviewpayload", + "/enterprise/2.20/v4/object/updaterefpayload": "/enterprise-server@2.20/graphql/reference/objects#updaterefpayload", + "/enterprise/2.20/v4/object/updaterefspayload": "/enterprise-server@2.20/graphql/reference/objects#updaterefspayload", + "/enterprise/2.20/v4/object/updaterepositorypayload": "/enterprise-server@2.20/graphql/reference/objects#updaterepositorypayload", + "/enterprise/2.20/v4/object/updatesubscriptionpayload": "/enterprise-server@2.20/graphql/reference/objects#updatesubscriptionpayload", + "/enterprise/2.20/v4/object/updateteamdiscussioncommentpayload": "/enterprise-server@2.20/graphql/reference/objects#updateteamdiscussioncommentpayload", + "/enterprise/2.20/v4/object/updateteamdiscussionpayload": "/enterprise-server@2.20/graphql/reference/objects#updateteamdiscussionpayload", + "/enterprise/2.20/v4/object/updateteamreviewassignmentpayload": "/enterprise-server@2.20/graphql/reference/objects#updateteamreviewassignmentpayload", + "/enterprise/2.20/v4/object/updatetopicspayload": "/enterprise-server@2.20/graphql/reference/objects#updatetopicspayload", + "/enterprise/2.20/v4/object/user": "/enterprise-server@2.20/graphql/reference/objects#user", + "/enterprise/2.20/v4/object/userblockedevent": "/enterprise-server@2.20/graphql/reference/objects#userblockedevent", + "/enterprise/2.20/v4/object/userconnection": "/enterprise-server@2.20/graphql/reference/objects#userconnection", + "/enterprise/2.20/v4/object/usercontentedit": "/enterprise-server@2.20/graphql/reference/objects#usercontentedit", + "/enterprise/2.20/v4/object/usercontenteditconnection": "/enterprise-server@2.20/graphql/reference/objects#usercontenteditconnection", + "/enterprise/2.20/v4/object/usercontenteditedge": "/enterprise-server@2.20/graphql/reference/objects#usercontenteditedge", + "/enterprise/2.20/v4/object/useredge": "/enterprise-server@2.20/graphql/reference/objects#useredge", + "/enterprise/2.20/v4/object/userstatus": "/enterprise-server@2.20/graphql/reference/objects#userstatus", + "/enterprise/2.20/v4/object/userstatusconnection": "/enterprise-server@2.20/graphql/reference/objects#userstatusconnection", + "/enterprise/2.20/v4/object/userstatusedge": "/enterprise-server@2.20/graphql/reference/objects#userstatusedge", + "/enterprise/2.20/v4/object/viewerhovercardcontext": "/enterprise-server@2.20/graphql/reference/objects#viewerhovercardcontext", + "/enterprise/2.20/v4/scalar/boolean": "/enterprise-server@2.20/graphql/reference/scalars#boolean", + "/enterprise/2.20/v4/scalar/date": "/enterprise-server@2.20/graphql/reference/scalars#date", + "/enterprise/2.20/v4/scalar/datetime": "/enterprise-server@2.20/graphql/reference/scalars#datetime", + "/enterprise/2.20/v4/scalar/float": "/enterprise-server@2.20/graphql/reference/scalars#float", + "/enterprise/2.20/v4/scalar/gitobjectid": "/enterprise-server@2.20/graphql/reference/scalars#gitobjectid", + "/enterprise/2.20/v4/scalar/gitrefname": "/enterprise-server@2.20/graphql/reference/scalars#gitrefname", + "/enterprise/2.20/v4/scalar/gitsshremote": "/enterprise-server@2.20/graphql/reference/scalars#gitsshremote", + "/enterprise/2.20/v4/scalar/gittimestamp": "/enterprise-server@2.20/graphql/reference/scalars#gittimestamp", + "/enterprise/2.20/v4/scalar/html": "/enterprise-server@2.20/graphql/reference/scalars#html", + "/enterprise/2.20/v4/scalar/id": "/enterprise-server@2.20/graphql/reference/scalars#id", + "/enterprise/2.20/v4/scalar/int": "/enterprise-server@2.20/graphql/reference/scalars#int", + "/enterprise/2.20/v4/scalar/precisedatetime": "/enterprise-server@2.20/graphql/reference/scalars#precisedatetime", + "/enterprise/2.20/v4/scalar/string": "/enterprise-server@2.20/graphql/reference/scalars#string", + "/enterprise/2.20/v4/scalar/uri": "/enterprise-server@2.20/graphql/reference/scalars#uri", + "/enterprise/2.20/v4/scalar/x509certificate": "/enterprise-server@2.20/graphql/reference/scalars#x509certificate", + "/enterprise/2.20/v4/union/assignee": "/enterprise-server@2.20/graphql/reference/unions#assignee", + "/enterprise/2.20/v4/union/auditentryactor": "/enterprise-server@2.20/graphql/reference/unions#auditentryactor", + "/enterprise/2.20/v4/union/closer": "/enterprise-server@2.20/graphql/reference/unions#closer", + "/enterprise/2.20/v4/union/createdissueorrestrictedcontribution": "/enterprise-server@2.20/graphql/reference/unions#createdissueorrestrictedcontribution", + "/enterprise/2.20/v4/union/createdpullrequestorrestrictedcontribution": "/enterprise-server@2.20/graphql/reference/unions#createdpullrequestorrestrictedcontribution", + "/enterprise/2.20/v4/union/createdrepositoryorrestrictedcontribution": "/enterprise-server@2.20/graphql/reference/unions#createdrepositoryorrestrictedcontribution", + "/enterprise/2.20/v4/union/enterprisemember": "/enterprise-server@2.20/graphql/reference/unions#enterprisemember", + "/enterprise/2.20/v4/union/issueorpullrequest": "/enterprise-server@2.20/graphql/reference/unions#issueorpullrequest", + "/enterprise/2.20/v4/union/issuetimelineitem": "/enterprise-server@2.20/graphql/reference/unions#issuetimelineitem", + "/enterprise/2.20/v4/union/issuetimelineitems": "/enterprise-server@2.20/graphql/reference/unions#issuetimelineitems", + "/enterprise/2.20/v4/union/milestoneitem": "/enterprise-server@2.20/graphql/reference/unions#milestoneitem", + "/enterprise/2.20/v4/union/organizationauditentry": "/enterprise-server@2.20/graphql/reference/unions#organizationauditentry", + "/enterprise/2.20/v4/union/orgrestorememberauditentrymembership": "/enterprise-server@2.20/graphql/reference/unions#orgrestorememberauditentrymembership", + "/enterprise/2.20/v4/union/permissiongranter": "/enterprise-server@2.20/graphql/reference/unions#permissiongranter", + "/enterprise/2.20/v4/union/pinnableitem": "/enterprise-server@2.20/graphql/reference/unions#pinnableitem", + "/enterprise/2.20/v4/union/projectcarditem": "/enterprise-server@2.20/graphql/reference/unions#projectcarditem", + "/enterprise/2.20/v4/union/pullrequesttimelineitem": "/enterprise-server@2.20/graphql/reference/unions#pullrequesttimelineitem", + "/enterprise/2.20/v4/union/pullrequesttimelineitems": "/enterprise-server@2.20/graphql/reference/unions#pullrequesttimelineitems", + "/enterprise/2.20/v4/union/pushallowanceactor": "/enterprise-server@2.20/graphql/reference/unions#pushallowanceactor", + "/enterprise/2.20/v4/union/referencedsubject": "/enterprise-server@2.20/graphql/reference/unions#referencedsubject", + "/enterprise/2.20/v4/union/renamedtitlesubject": "/enterprise-server@2.20/graphql/reference/unions#renamedtitlesubject", + "/enterprise/2.20/v4/union/requestedreviewer": "/enterprise-server@2.20/graphql/reference/unions#requestedreviewer", + "/enterprise/2.20/v4/union/reviewdismissalallowanceactor": "/enterprise-server@2.20/graphql/reference/unions#reviewdismissalallowanceactor", + "/enterprise/2.20/v4/union/searchresultitem": "/enterprise-server@2.20/graphql/reference/unions#searchresultitem", + "/enterprise/v3/activity/events": "/enterprise-server@latest/rest/reference/activity#events", + "/enterprise/v3/activity/feeds": "/enterprise-server@latest/rest/reference/activity#feeds", + "/enterprise/v3/activity/notifications": "/enterprise-server@latest/rest/reference/activity#notifications", + "/enterprise/v3/activity/starring": "/enterprise-server@latest/rest/reference/activity#starring", + "/enterprise/v3/activity/watching": "/enterprise-server@latest/rest/reference/activity#watching", + "/enterprise/v3/apps/installations": "/enterprise-server@latest/rest/reference/apps#installations", + "/enterprise/v3/apps/oauth_applications": "/enterprise-server@latest/rest/reference/apps#oauth-applications", + "/enterprise/v3/checks/runs": "/enterprise-server@latest/rest/reference/checks#runs", + "/enterprise/v3/checks/suites": "/enterprise-server@latest/rest/reference/checks#suites", + "/enterprise/v3/enterprise-admin/admin_stats": "/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", + "/enterprise/v3/enterprise-admin/global_webhooks": "/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", + "/enterprise/v3/enterprise-admin/ldap": "/enterprise-server@latest/rest/reference/enterprise-admin#ldap", + "/enterprise/v3/enterprise-admin/license": "/enterprise-server@latest/rest/reference/enterprise-admin#license", + "/enterprise/v3/enterprise-admin/management_console": "/enterprise-server@latest/rest/reference/enterprise-admin#management-console", + "/enterprise/v3/enterprise-admin/org_pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", + "/enterprise/v3/enterprise-admin/orgs": "/enterprise-server@latest/rest/reference/enterprise-admin#orgs", + "/enterprise/v3/enterprise-admin/pre_receive_environments": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", + "/enterprise/v3/enterprise-admin/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", + "/enterprise/v3/enterprise-admin/repo_pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", + "/enterprise/v3/enterprise-admin/search_indexing": "/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", + "/enterprise/v3/enterprise-admin/users": "/enterprise-server@latest/rest/reference/enterprise-admin#users", + "/enterprise/v3/enterprise/admin_stats": "/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", + "/enterprise/v3/enterprise/ldap": "/enterprise-server@latest/rest/reference/enterprise-admin#ldap", + "/enterprise/v3/enterprise/license": "/enterprise-server@latest/rest/reference/enterprise-admin#license", + "/enterprise/v3/enterprise/management_console": "/enterprise-server@latest/rest/reference/enterprise-admin#management-console", + "/enterprise/v3/enterprise/orgs": "/enterprise-server@latest/rest/reference/enterprise-admin#orgs", + "/enterprise/v3/enterprise/pre_receive_environments": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", + "/enterprise/v3/enterprise/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", + "/enterprise/v3/enterprise/search_indexing": "/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", + "/enterprise/v3/gists/comments": "/enterprise-server@latest/rest/reference/gists#comments", + "/enterprise/v3/git/blobs": "/enterprise-server@latest/rest/reference/git#blobs", + "/enterprise/v3/git/commits": "/enterprise-server@latest/rest/reference/git#commits", + "/enterprise/v3/git/refs": "/enterprise-server@latest/rest/reference/git#refs", + "/enterprise/v3/git/tags": "/enterprise-server@latest/rest/reference/git#tags", + "/enterprise/v3/git/trees": "/enterprise-server@latest/rest/reference/git#trees", + "/enterprise/v3/integrations/installations": "/enterprise-server@latest/developers/apps#installations", + "/enterprise/v3/issues/assignees": "/enterprise-server@latest/rest/reference/issues#assignees", + "/enterprise/v3/issues/comments": "/enterprise-server@latest/rest/reference/issues#comments", + "/enterprise/v3/issues/events": "/enterprise-server@latest/rest/reference/issues#events", + "/enterprise/v3/issues/labels": "/enterprise-server@latest/rest/reference/issues#labels", + "/enterprise/v3/issues/milestones": "/enterprise-server@latest/rest/reference/issues#milestones", + "/enterprise/v3/issues/timeline": "/enterprise-server@latest/rest/reference/issues#timeline", + "/enterprise/v3/orgs/hooks": "/enterprise-server@latest/rest/reference/orgs#webhooks", + "/enterprise/v3/orgs/members": "/enterprise-server@latest/rest/reference/orgs#members", + "/enterprise/v3/orgs/outside_collaborators": "/enterprise-server@latest/rest/reference/orgs#outside-collaborators", + "/enterprise/v3/orgs/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", + "/enterprise/v3/orgs/teams": "/enterprise-server@latest/rest/reference/orgs#teams", + "/enterprise/v3/projects/cards": "/enterprise-server@latest/rest/reference/projects#cards", + "/enterprise/v3/projects/collaborators": "/enterprise-server@latest/rest/reference/projects#collaborators", + "/enterprise/v3/projects/columns": "/enterprise-server@latest/rest/reference/projects#columns", + "/enterprise/v3/pulls/comments": "/enterprise-server@latest/rest/reference/pulls#comments", + "/enterprise/v3/pulls/review_requests": "/enterprise-server@latest/rest/reference/pulls#review-requests", + "/enterprise/v3/pulls/reviews": "/enterprise-server@latest/rest/reference/pulls#reviews", + "/enterprise/v3/repos/branches": "/enterprise-server@latest/rest/reference/repos#branches", + "/enterprise/v3/repos/collaborators": "/enterprise-server@latest/rest/reference/repos#collaborators", + "/enterprise/v3/repos/comments": "/enterprise-server@latest/rest/reference/repos#comments", + "/enterprise/v3/repos/commits": "/enterprise-server@latest/rest/reference/repos#commits", + "/enterprise/v3/repos/contents": "/enterprise-server@latest/rest/reference/repos#contents", + "/enterprise/v3/repos/deployments": "/enterprise-server@latest/rest/reference/repos#deployments", + "/enterprise/v3/repos/downloads": "/enterprise-server@latest/rest/reference/repos#downloads", + "/enterprise/v3/repos/forks": "/enterprise-server@latest/rest/reference/repos#forks", + "/enterprise/v3/repos/hooks": "/enterprise-server@latest/rest/reference/repos#webhooks", + "/enterprise/v3/repos/invitations": "/enterprise-server@latest/rest/reference/repos#invitations", + "/enterprise/v3/repos/keys": "/enterprise-server@latest/rest/reference/repos#keys", + "/enterprise/v3/repos/merging": "/enterprise-server@latest/rest/reference/repos#merging", + "/enterprise/v3/repos/pages": "/enterprise-server@latest/rest/reference/repos#pages", + "/enterprise/v3/repos/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", + "/enterprise/v3/repos/releases": "/enterprise-server@latest/rest/reference/repos#releases", + "/enterprise/v3/repos/statistics": "/enterprise-server@latest/rest/reference/repos#statistics", + "/enterprise/v3/repos/statuses": "/enterprise-server@latest/rest/reference/repos#statuses", + "/enterprise/v3/teams/discussion_comments": "/enterprise-server@latest/rest/reference/teams#discussion-comments", + "/enterprise/v3/teams/discussions": "/enterprise-server@latest/rest/reference/teams#discussions", + "/enterprise/v3/teams/members": "/enterprise-server@latest/rest/reference/teams#members", + "/enterprise/v3/users/administration": "/enterprise-server@latest/rest/reference/users#administration", + "/enterprise/v3/users/emails": "/enterprise-server@latest/rest/reference/users#emails", + "/enterprise/v3/users/followers": "/enterprise-server@latest/rest/reference/users#followers", + "/enterprise/v3/users/gpg_keys": "/enterprise-server@latest/rest/reference/users#gpg-keys", + "/enterprise/v3/users/keys": "/enterprise-server@latest/rest/reference/users#keys", + "/enterprise/v4/enum/__directivelocation": "/enterprise-server@latest/graphql/reference/enums#__directivelocation", + "/enterprise/v4/enum/__typekind": "/enterprise-server@latest/graphql/reference/enums#__typekind", + "/enterprise/v4/enum/actionexecutioncapabilitysetting": "/enterprise-server@latest/graphql/reference/enums#actionexecutioncapabilitysetting", + "/enterprise/v4/enum/auditlogorderfield": "/enterprise-server@latest/graphql/reference/enums#auditlogorderfield", + "/enterprise/v4/enum/checkannotationlevel": "/enterprise-server@latest/graphql/reference/enums#checkannotationlevel", + "/enterprise/v4/enum/checkconclusionstate": "/enterprise-server@latest/graphql/reference/enums#checkconclusionstate", + "/enterprise/v4/enum/checkruntype": "/enterprise-server@latest/graphql/reference/enums#checkruntype", + "/enterprise/v4/enum/checkstatusstate": "/enterprise-server@latest/graphql/reference/enums#checkstatusstate", + "/enterprise/v4/enum/collaboratoraffiliation": "/enterprise-server@latest/graphql/reference/enums#collaboratoraffiliation", + "/enterprise/v4/enum/commentauthorassociation": "/enterprise-server@latest/graphql/reference/enums#commentauthorassociation", + "/enterprise/v4/enum/commentcannotupdatereason": "/enterprise-server@latest/graphql/reference/enums#commentcannotupdatereason", + "/enterprise/v4/enum/commitcontributionorderfield": "/enterprise-server@latest/graphql/reference/enums#commitcontributionorderfield", + "/enterprise/v4/enum/contributionorderfield": "/enterprise-server@latest/graphql/reference/enums#contributionorderfield", + "/enterprise/v4/enum/defaultrepositorypermissionfield": "/enterprise-server@latest/graphql/reference/enums#defaultrepositorypermissionfield", + "/enterprise/v4/enum/deploymentorderfield": "/enterprise-server@latest/graphql/reference/enums#deploymentorderfield", + "/enterprise/v4/enum/deploymentstate": "/enterprise-server@latest/graphql/reference/enums#deploymentstate", + "/enterprise/v4/enum/deploymentstatusstate": "/enterprise-server@latest/graphql/reference/enums#deploymentstatusstate", + "/enterprise/v4/enum/diffside": "/enterprise-server@latest/graphql/reference/enums#diffside", + "/enterprise/v4/enum/enterpriseadministratorinvitationorderfield": "/enterprise-server@latest/graphql/reference/enums#enterpriseadministratorinvitationorderfield", + "/enterprise/v4/enum/enterpriseadministratorrole": "/enterprise-server@latest/graphql/reference/enums#enterpriseadministratorrole", + "/enterprise/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/enterprise-server@latest/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", + "/enterprise/v4/enum/enterpriseenableddisabledsettingvalue": "/enterprise-server@latest/graphql/reference/enums#enterpriseenableddisabledsettingvalue", + "/enterprise/v4/enum/enterpriseenabledsettingvalue": "/enterprise-server@latest/graphql/reference/enums#enterpriseenabledsettingvalue", + "/enterprise/v4/enum/enterprisememberorderfield": "/enterprise-server@latest/graphql/reference/enums#enterprisememberorderfield", + "/enterprise/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/enterprise-server@latest/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", + "/enterprise/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/enterprise-server@latest/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", + "/enterprise/v4/enum/enterpriseserveruseraccountemailorderfield": "/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", + "/enterprise/v4/enum/enterpriseserveruseraccountorderfield": "/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountorderfield", + "/enterprise/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", + "/enterprise/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/enterprise-server@latest/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", + "/enterprise/v4/enum/enterpriseuseraccountmembershiprole": "/enterprise-server@latest/graphql/reference/enums#enterpriseuseraccountmembershiprole", + "/enterprise/v4/enum/enterpriseuserdeployment": "/enterprise-server@latest/graphql/reference/enums#enterpriseuserdeployment", + "/enterprise/v4/enum/gistorderfield": "/enterprise-server@latest/graphql/reference/enums#gistorderfield", + "/enterprise/v4/enum/gistprivacy": "/enterprise-server@latest/graphql/reference/enums#gistprivacy", + "/enterprise/v4/enum/gitsignaturestate": "/enterprise-server@latest/graphql/reference/enums#gitsignaturestate", + "/enterprise/v4/enum/identityproviderconfigurationstate": "/enterprise-server@latest/graphql/reference/enums#identityproviderconfigurationstate", + "/enterprise/v4/enum/ipallowlistenabledsettingvalue": "/enterprise-server@latest/graphql/reference/enums#ipallowlistenabledsettingvalue", + "/enterprise/v4/enum/ipallowlistentryorderfield": "/enterprise-server@latest/graphql/reference/enums#ipallowlistentryorderfield", + "/enterprise/v4/enum/issueorderfield": "/enterprise-server@latest/graphql/reference/enums#issueorderfield", + "/enterprise/v4/enum/issuestate": "/enterprise-server@latest/graphql/reference/enums#issuestate", + "/enterprise/v4/enum/issuetimelineitemsitemtype": "/enterprise-server@latest/graphql/reference/enums#issuetimelineitemsitemtype", + "/enterprise/v4/enum/labelorderfield": "/enterprise-server@latest/graphql/reference/enums#labelorderfield", + "/enterprise/v4/enum/languageorderfield": "/enterprise-server@latest/graphql/reference/enums#languageorderfield", + "/enterprise/v4/enum/lockreason": "/enterprise-server@latest/graphql/reference/enums#lockreason", + "/enterprise/v4/enum/mergeablestate": "/enterprise-server@latest/graphql/reference/enums#mergeablestate", + "/enterprise/v4/enum/mergestatestatus": "/enterprise-server@latest/graphql/reference/enums#mergestatestatus", + "/enterprise/v4/enum/milestoneorderfield": "/enterprise-server@latest/graphql/reference/enums#milestoneorderfield", + "/enterprise/v4/enum/milestonestate": "/enterprise-server@latest/graphql/reference/enums#milestonestate", + "/enterprise/v4/enum/oauthapplicationcreateauditentrystate": "/enterprise-server@latest/graphql/reference/enums#oauthapplicationcreateauditentrystate", + "/enterprise/v4/enum/operationtype": "/enterprise-server@latest/graphql/reference/enums#operationtype", + "/enterprise/v4/enum/orderdirection": "/enterprise-server@latest/graphql/reference/enums#orderdirection", + "/enterprise/v4/enum/orgaddmemberauditentrypermission": "/enterprise-server@latest/graphql/reference/enums#orgaddmemberauditentrypermission", + "/enterprise/v4/enum/organizationinvitationrole": "/enterprise-server@latest/graphql/reference/enums#organizationinvitationrole", + "/enterprise/v4/enum/organizationinvitationtype": "/enterprise-server@latest/graphql/reference/enums#organizationinvitationtype", + "/enterprise/v4/enum/organizationmemberrole": "/enterprise-server@latest/graphql/reference/enums#organizationmemberrole", + "/enterprise/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/enterprise-server@latest/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", + "/enterprise/v4/enum/organizationorderfield": "/enterprise-server@latest/graphql/reference/enums#organizationorderfield", + "/enterprise/v4/enum/orgcreateauditentrybillingplan": "/enterprise-server@latest/graphql/reference/enums#orgcreateauditentrybillingplan", + "/enterprise/v4/enum/orgremovebillingmanagerauditentryreason": "/enterprise-server@latest/graphql/reference/enums#orgremovebillingmanagerauditentryreason", + "/enterprise/v4/enum/orgremovememberauditentrymembershiptype": "/enterprise-server@latest/graphql/reference/enums#orgremovememberauditentrymembershiptype", + "/enterprise/v4/enum/orgremovememberauditentryreason": "/enterprise-server@latest/graphql/reference/enums#orgremovememberauditentryreason", + "/enterprise/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/enterprise-server@latest/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", + "/enterprise/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/enterprise-server@latest/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", + "/enterprise/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/enterprise-server@latest/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", + "/enterprise/v4/enum/orgupdatememberauditentrypermission": "/enterprise-server@latest/graphql/reference/enums#orgupdatememberauditentrypermission", + "/enterprise/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", + "/enterprise/v4/enum/packagefileorderfield": "/enterprise-server@latest/graphql/reference/enums#packagefileorderfield", + "/enterprise/v4/enum/packageorderfield": "/enterprise-server@latest/graphql/reference/enums#packageorderfield", + "/enterprise/v4/enum/packagetype": "/enterprise-server@latest/graphql/reference/enums#packagetype", + "/enterprise/v4/enum/packageversionorderfield": "/enterprise-server@latest/graphql/reference/enums#packageversionorderfield", + "/enterprise/v4/enum/pinnableitemtype": "/enterprise-server@latest/graphql/reference/enums#pinnableitemtype", + "/enterprise/v4/enum/projectcardarchivedstate": "/enterprise-server@latest/graphql/reference/enums#projectcardarchivedstate", + "/enterprise/v4/enum/projectcardstate": "/enterprise-server@latest/graphql/reference/enums#projectcardstate", + "/enterprise/v4/enum/projectcolumnpurpose": "/enterprise-server@latest/graphql/reference/enums#projectcolumnpurpose", + "/enterprise/v4/enum/projectorderfield": "/enterprise-server@latest/graphql/reference/enums#projectorderfield", + "/enterprise/v4/enum/projectstate": "/enterprise-server@latest/graphql/reference/enums#projectstate", + "/enterprise/v4/enum/projecttemplate": "/enterprise-server@latest/graphql/reference/enums#projecttemplate", + "/enterprise/v4/enum/pullrequestmergemethod": "/enterprise-server@latest/graphql/reference/enums#pullrequestmergemethod", + "/enterprise/v4/enum/pullrequestorderfield": "/enterprise-server@latest/graphql/reference/enums#pullrequestorderfield", + "/enterprise/v4/enum/pullrequestreviewcommentstate": "/enterprise-server@latest/graphql/reference/enums#pullrequestreviewcommentstate", + "/enterprise/v4/enum/pullrequestreviewdecision": "/enterprise-server@latest/graphql/reference/enums#pullrequestreviewdecision", + "/enterprise/v4/enum/pullrequestreviewevent": "/enterprise-server@latest/graphql/reference/enums#pullrequestreviewevent", + "/enterprise/v4/enum/pullrequestreviewstate": "/enterprise-server@latest/graphql/reference/enums#pullrequestreviewstate", + "/enterprise/v4/enum/pullrequeststate": "/enterprise-server@latest/graphql/reference/enums#pullrequeststate", + "/enterprise/v4/enum/pullrequesttimelineitemsitemtype": "/enterprise-server@latest/graphql/reference/enums#pullrequesttimelineitemsitemtype", + "/enterprise/v4/enum/pullrequestupdatestate": "/enterprise-server@latest/graphql/reference/enums#pullrequestupdatestate", + "/enterprise/v4/enum/reactioncontent": "/enterprise-server@latest/graphql/reference/enums#reactioncontent", + "/enterprise/v4/enum/reactionorderfield": "/enterprise-server@latest/graphql/reference/enums#reactionorderfield", + "/enterprise/v4/enum/reforderfield": "/enterprise-server@latest/graphql/reference/enums#reforderfield", + "/enterprise/v4/enum/registrypackagedependencytype": "/enterprise-server@latest/graphql/reference/enums#registrypackagedependencytype", + "/enterprise/v4/enum/registrypackagetype": "/enterprise-server@latest/graphql/reference/enums#registrypackagetype", + "/enterprise/v4/enum/releaseorderfield": "/enterprise-server@latest/graphql/reference/enums#releaseorderfield", + "/enterprise/v4/enum/repoaccessauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#repoaccessauditentryvisibility", + "/enterprise/v4/enum/repoaddmemberauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#repoaddmemberauditentryvisibility", + "/enterprise/v4/enum/repoarchivedauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#repoarchivedauditentryvisibility", + "/enterprise/v4/enum/repochangemergesettingauditentrymergetype": "/enterprise-server@latest/graphql/reference/enums#repochangemergesettingauditentrymergetype", + "/enterprise/v4/enum/repocreateauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#repocreateauditentryvisibility", + "/enterprise/v4/enum/repodestroyauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#repodestroyauditentryvisibility", + "/enterprise/v4/enum/reporemovememberauditentryvisibility": "/enterprise-server@latest/graphql/reference/enums#reporemovememberauditentryvisibility", + "/enterprise/v4/enum/reportedcontentclassifiers": "/enterprise-server@latest/graphql/reference/enums#reportedcontentclassifiers", + "/enterprise/v4/enum/repositoryaffiliation": "/enterprise-server@latest/graphql/reference/enums#repositoryaffiliation", + "/enterprise/v4/enum/repositorycontributiontype": "/enterprise-server@latest/graphql/reference/enums#repositorycontributiontype", + "/enterprise/v4/enum/repositoryinvitationorderfield": "/enterprise-server@latest/graphql/reference/enums#repositoryinvitationorderfield", + "/enterprise/v4/enum/repositorylockreason": "/enterprise-server@latest/graphql/reference/enums#repositorylockreason", + "/enterprise/v4/enum/repositoryorderfield": "/enterprise-server@latest/graphql/reference/enums#repositoryorderfield", + "/enterprise/v4/enum/repositorypermission": "/enterprise-server@latest/graphql/reference/enums#repositorypermission", + "/enterprise/v4/enum/repositoryprivacy": "/enterprise-server@latest/graphql/reference/enums#repositoryprivacy", + "/enterprise/v4/enum/repositoryvisibility": "/enterprise-server@latest/graphql/reference/enums#repositoryvisibility", + "/enterprise/v4/enum/requestablecheckstatusstate": "/enterprise-server@latest/graphql/reference/enums#requestablecheckstatusstate", + "/enterprise/v4/enum/samldigestalgorithm": "/enterprise-server@latest/graphql/reference/enums#samldigestalgorithm", + "/enterprise/v4/enum/samlsignaturealgorithm": "/enterprise-server@latest/graphql/reference/enums#samlsignaturealgorithm", + "/enterprise/v4/enum/savedreplyorderfield": "/enterprise-server@latest/graphql/reference/enums#savedreplyorderfield", + "/enterprise/v4/enum/searchtype": "/enterprise-server@latest/graphql/reference/enums#searchtype", + "/enterprise/v4/enum/securityadvisoryecosystem": "/enterprise-server@latest/graphql/reference/enums#securityadvisoryecosystem", + "/enterprise/v4/enum/securityadvisoryseverity": "/enterprise-server@latest/graphql/reference/enums#securityadvisoryseverity", + "/enterprise/v4/enum/sponsorshipprivacy": "/enterprise-server@latest/graphql/reference/enums#sponsorshipprivacy", + "/enterprise/v4/enum/starorderfield": "/enterprise-server@latest/graphql/reference/enums#starorderfield", + "/enterprise/v4/enum/statusstate": "/enterprise-server@latest/graphql/reference/enums#statusstate", + "/enterprise/v4/enum/subscriptionstate": "/enterprise-server@latest/graphql/reference/enums#subscriptionstate", + "/enterprise/v4/enum/teamdiscussioncommentorderfield": "/enterprise-server@latest/graphql/reference/enums#teamdiscussioncommentorderfield", + "/enterprise/v4/enum/teamdiscussionorderfield": "/enterprise-server@latest/graphql/reference/enums#teamdiscussionorderfield", + "/enterprise/v4/enum/teammemberorderfield": "/enterprise-server@latest/graphql/reference/enums#teammemberorderfield", + "/enterprise/v4/enum/teammemberrole": "/enterprise-server@latest/graphql/reference/enums#teammemberrole", + "/enterprise/v4/enum/teammembershiptype": "/enterprise-server@latest/graphql/reference/enums#teammembershiptype", + "/enterprise/v4/enum/teamorderfield": "/enterprise-server@latest/graphql/reference/enums#teamorderfield", + "/enterprise/v4/enum/teamprivacy": "/enterprise-server@latest/graphql/reference/enums#teamprivacy", + "/enterprise/v4/enum/teamrepositoryorderfield": "/enterprise-server@latest/graphql/reference/enums#teamrepositoryorderfield", + "/enterprise/v4/enum/teamreviewassignmentalgorithm": "/enterprise-server@latest/graphql/reference/enums#teamreviewassignmentalgorithm", + "/enterprise/v4/enum/teamrole": "/enterprise-server@latest/graphql/reference/enums#teamrole", + "/enterprise/v4/enum/userblockduration": "/enterprise-server@latest/graphql/reference/enums#userblockduration", + "/enterprise/v4/enum/userstatusorderfield": "/enterprise-server@latest/graphql/reference/enums#userstatusorderfield", + "/enterprise/v4/input_object/addassigneestoassignableinput": "/enterprise-server@latest/graphql/reference/input-objects#addassigneestoassignableinput", + "/enterprise/v4/input_object/addcommentinput": "/enterprise-server@latest/graphql/reference/input-objects#addcommentinput", + "/enterprise/v4/input_object/addenterpriseadmininput": "/enterprise-server@latest/graphql/reference/input-objects#addenterpriseadmininput", + "/enterprise/v4/input_object/addlabelstolabelableinput": "/enterprise-server@latest/graphql/reference/input-objects#addlabelstolabelableinput", + "/enterprise/v4/input_object/addprojectcardinput": "/enterprise-server@latest/graphql/reference/input-objects#addprojectcardinput", + "/enterprise/v4/input_object/addprojectcolumninput": "/enterprise-server@latest/graphql/reference/input-objects#addprojectcolumninput", + "/enterprise/v4/input_object/addpullrequestreviewcommentinput": "/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewcommentinput", + "/enterprise/v4/input_object/addpullrequestreviewinput": "/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewinput", + "/enterprise/v4/input_object/addpullrequestreviewthreadinput": "/enterprise-server@latest/graphql/reference/input-objects#addpullrequestreviewthreadinput", + "/enterprise/v4/input_object/addreactioninput": "/enterprise-server@latest/graphql/reference/input-objects#addreactioninput", + "/enterprise/v4/input_object/addstarinput": "/enterprise-server@latest/graphql/reference/input-objects#addstarinput", + "/enterprise/v4/input_object/archiverepositoryinput": "/enterprise-server@latest/graphql/reference/input-objects#archiverepositoryinput", + "/enterprise/v4/input_object/auditlogorder": "/enterprise-server@latest/graphql/reference/input-objects#auditlogorder", + "/enterprise/v4/input_object/changeuserstatusinput": "/enterprise-server@latest/graphql/reference/input-objects#changeuserstatusinput", + "/enterprise/v4/input_object/checkannotationdata": "/enterprise-server@latest/graphql/reference/input-objects#checkannotationdata", + "/enterprise/v4/input_object/checkannotationrange": "/enterprise-server@latest/graphql/reference/input-objects#checkannotationrange", + "/enterprise/v4/input_object/checkrunaction": "/enterprise-server@latest/graphql/reference/input-objects#checkrunaction", + "/enterprise/v4/input_object/checkrunfilter": "/enterprise-server@latest/graphql/reference/input-objects#checkrunfilter", + "/enterprise/v4/input_object/checkrunoutput": "/enterprise-server@latest/graphql/reference/input-objects#checkrunoutput", + "/enterprise/v4/input_object/checkrunoutputimage": "/enterprise-server@latest/graphql/reference/input-objects#checkrunoutputimage", + "/enterprise/v4/input_object/checksuiteautotriggerpreference": "/enterprise-server@latest/graphql/reference/input-objects#checksuiteautotriggerpreference", + "/enterprise/v4/input_object/checksuitefilter": "/enterprise-server@latest/graphql/reference/input-objects#checksuitefilter", + "/enterprise/v4/input_object/clearlabelsfromlabelableinput": "/enterprise-server@latest/graphql/reference/input-objects#clearlabelsfromlabelableinput", + "/enterprise/v4/input_object/cloneprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#cloneprojectinput", + "/enterprise/v4/input_object/clonetemplaterepositoryinput": "/enterprise-server@latest/graphql/reference/input-objects#clonetemplaterepositoryinput", + "/enterprise/v4/input_object/closeissueinput": "/enterprise-server@latest/graphql/reference/input-objects#closeissueinput", + "/enterprise/v4/input_object/closepullrequestinput": "/enterprise-server@latest/graphql/reference/input-objects#closepullrequestinput", + "/enterprise/v4/input_object/commitauthor": "/enterprise-server@latest/graphql/reference/input-objects#commitauthor", + "/enterprise/v4/input_object/commitcontributionorder": "/enterprise-server@latest/graphql/reference/input-objects#commitcontributionorder", + "/enterprise/v4/input_object/contributionorder": "/enterprise-server@latest/graphql/reference/input-objects#contributionorder", + "/enterprise/v4/input_object/convertprojectcardnotetoissueinput": "/enterprise-server@latest/graphql/reference/input-objects#convertprojectcardnotetoissueinput", + "/enterprise/v4/input_object/createbranchprotectionruleinput": "/enterprise-server@latest/graphql/reference/input-objects#createbranchprotectionruleinput", + "/enterprise/v4/input_object/createcheckruninput": "/enterprise-server@latest/graphql/reference/input-objects#createcheckruninput", + "/enterprise/v4/input_object/createchecksuiteinput": "/enterprise-server@latest/graphql/reference/input-objects#createchecksuiteinput", + "/enterprise/v4/input_object/createcontentattachmentinput": "/enterprise-server@latest/graphql/reference/input-objects#createcontentattachmentinput", + "/enterprise/v4/input_object/createdeploymentinput": "/enterprise-server@latest/graphql/reference/input-objects#createdeploymentinput", + "/enterprise/v4/input_object/createdeploymentstatusinput": "/enterprise-server@latest/graphql/reference/input-objects#createdeploymentstatusinput", + "/enterprise/v4/input_object/createipallowlistentryinput": "/enterprise-server@latest/graphql/reference/input-objects#createipallowlistentryinput", + "/enterprise/v4/input_object/createissueinput": "/enterprise-server@latest/graphql/reference/input-objects#createissueinput", + "/enterprise/v4/input_object/createlabelinput": "/enterprise-server@latest/graphql/reference/input-objects#createlabelinput", + "/enterprise/v4/input_object/createprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#createprojectinput", + "/enterprise/v4/input_object/createpullrequestinput": "/enterprise-server@latest/graphql/reference/input-objects#createpullrequestinput", + "/enterprise/v4/input_object/createrefinput": "/enterprise-server@latest/graphql/reference/input-objects#createrefinput", + "/enterprise/v4/input_object/createrepositoryinput": "/enterprise-server@latest/graphql/reference/input-objects#createrepositoryinput", + "/enterprise/v4/input_object/createteamdiscussioncommentinput": "/enterprise-server@latest/graphql/reference/input-objects#createteamdiscussioncommentinput", + "/enterprise/v4/input_object/createteamdiscussioninput": "/enterprise-server@latest/graphql/reference/input-objects#createteamdiscussioninput", + "/enterprise/v4/input_object/deletebranchprotectionruleinput": "/enterprise-server@latest/graphql/reference/input-objects#deletebranchprotectionruleinput", + "/enterprise/v4/input_object/deletedeploymentinput": "/enterprise-server@latest/graphql/reference/input-objects#deletedeploymentinput", + "/enterprise/v4/input_object/deleteipallowlistentryinput": "/enterprise-server@latest/graphql/reference/input-objects#deleteipallowlistentryinput", + "/enterprise/v4/input_object/deleteissuecommentinput": "/enterprise-server@latest/graphql/reference/input-objects#deleteissuecommentinput", + "/enterprise/v4/input_object/deleteissueinput": "/enterprise-server@latest/graphql/reference/input-objects#deleteissueinput", + "/enterprise/v4/input_object/deletelabelinput": "/enterprise-server@latest/graphql/reference/input-objects#deletelabelinput", + "/enterprise/v4/input_object/deletepackageversioninput": "/enterprise-server@latest/graphql/reference/input-objects#deletepackageversioninput", + "/enterprise/v4/input_object/deleteprojectcardinput": "/enterprise-server@latest/graphql/reference/input-objects#deleteprojectcardinput", + "/enterprise/v4/input_object/deleteprojectcolumninput": "/enterprise-server@latest/graphql/reference/input-objects#deleteprojectcolumninput", + "/enterprise/v4/input_object/deleteprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#deleteprojectinput", + "/enterprise/v4/input_object/deletepullrequestreviewcommentinput": "/enterprise-server@latest/graphql/reference/input-objects#deletepullrequestreviewcommentinput", + "/enterprise/v4/input_object/deletepullrequestreviewinput": "/enterprise-server@latest/graphql/reference/input-objects#deletepullrequestreviewinput", + "/enterprise/v4/input_object/deleterefinput": "/enterprise-server@latest/graphql/reference/input-objects#deleterefinput", + "/enterprise/v4/input_object/deleteteamdiscussioncommentinput": "/enterprise-server@latest/graphql/reference/input-objects#deleteteamdiscussioncommentinput", + "/enterprise/v4/input_object/deleteteamdiscussioninput": "/enterprise-server@latest/graphql/reference/input-objects#deleteteamdiscussioninput", + "/enterprise/v4/input_object/deploymentorder": "/enterprise-server@latest/graphql/reference/input-objects#deploymentorder", + "/enterprise/v4/input_object/dismisspullrequestreviewinput": "/enterprise-server@latest/graphql/reference/input-objects#dismisspullrequestreviewinput", + "/enterprise/v4/input_object/draftpullrequestreviewcomment": "/enterprise-server@latest/graphql/reference/input-objects#draftpullrequestreviewcomment", + "/enterprise/v4/input_object/draftpullrequestreviewthread": "/enterprise-server@latest/graphql/reference/input-objects#draftpullrequestreviewthread", + "/enterprise/v4/input_object/enterpriseadministratorinvitationorder": "/enterprise-server@latest/graphql/reference/input-objects#enterpriseadministratorinvitationorder", + "/enterprise/v4/input_object/enterprisememberorder": "/enterprise-server@latest/graphql/reference/input-objects#enterprisememberorder", + "/enterprise/v4/input_object/enterpriseserveruseraccountemailorder": "/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", + "/enterprise/v4/input_object/enterpriseserveruseraccountorder": "/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountorder", + "/enterprise/v4/input_object/enterpriseserveruseraccountsuploadorder": "/enterprise-server@latest/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", + "/enterprise/v4/input_object/followuserinput": "/enterprise-server@latest/graphql/reference/input-objects#followuserinput", + "/enterprise/v4/input_object/gistorder": "/enterprise-server@latest/graphql/reference/input-objects#gistorder", + "/enterprise/v4/input_object/importprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#importprojectinput", + "/enterprise/v4/input_object/ipallowlistentryorder": "/enterprise-server@latest/graphql/reference/input-objects#ipallowlistentryorder", + "/enterprise/v4/input_object/issuefilters": "/enterprise-server@latest/graphql/reference/input-objects#issuefilters", + "/enterprise/v4/input_object/issueorder": "/enterprise-server@latest/graphql/reference/input-objects#issueorder", + "/enterprise/v4/input_object/labelorder": "/enterprise-server@latest/graphql/reference/input-objects#labelorder", + "/enterprise/v4/input_object/languageorder": "/enterprise-server@latest/graphql/reference/input-objects#languageorder", + "/enterprise/v4/input_object/linkrepositorytoprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#linkrepositorytoprojectinput", + "/enterprise/v4/input_object/locklockableinput": "/enterprise-server@latest/graphql/reference/input-objects#locklockableinput", + "/enterprise/v4/input_object/markpullrequestreadyforreviewinput": "/enterprise-server@latest/graphql/reference/input-objects#markpullrequestreadyforreviewinput", + "/enterprise/v4/input_object/mergebranchinput": "/enterprise-server@latest/graphql/reference/input-objects#mergebranchinput", + "/enterprise/v4/input_object/mergepullrequestinput": "/enterprise-server@latest/graphql/reference/input-objects#mergepullrequestinput", + "/enterprise/v4/input_object/milestoneorder": "/enterprise-server@latest/graphql/reference/input-objects#milestoneorder", + "/enterprise/v4/input_object/minimizecommentinput": "/enterprise-server@latest/graphql/reference/input-objects#minimizecommentinput", + "/enterprise/v4/input_object/moveprojectcardinput": "/enterprise-server@latest/graphql/reference/input-objects#moveprojectcardinput", + "/enterprise/v4/input_object/moveprojectcolumninput": "/enterprise-server@latest/graphql/reference/input-objects#moveprojectcolumninput", + "/enterprise/v4/input_object/organizationorder": "/enterprise-server@latest/graphql/reference/input-objects#organizationorder", + "/enterprise/v4/input_object/packagefileorder": "/enterprise-server@latest/graphql/reference/input-objects#packagefileorder", + "/enterprise/v4/input_object/packageorder": "/enterprise-server@latest/graphql/reference/input-objects#packageorder", + "/enterprise/v4/input_object/packageversionorder": "/enterprise-server@latest/graphql/reference/input-objects#packageversionorder", + "/enterprise/v4/input_object/pinissueinput": "/enterprise-server@latest/graphql/reference/input-objects#pinissueinput", + "/enterprise/v4/input_object/projectcardimport": "/enterprise-server@latest/graphql/reference/input-objects#projectcardimport", + "/enterprise/v4/input_object/projectcolumnimport": "/enterprise-server@latest/graphql/reference/input-objects#projectcolumnimport", + "/enterprise/v4/input_object/projectorder": "/enterprise-server@latest/graphql/reference/input-objects#projectorder", + "/enterprise/v4/input_object/pullrequestorder": "/enterprise-server@latest/graphql/reference/input-objects#pullrequestorder", + "/enterprise/v4/input_object/reactionorder": "/enterprise-server@latest/graphql/reference/input-objects#reactionorder", + "/enterprise/v4/input_object/reforder": "/enterprise-server@latest/graphql/reference/input-objects#reforder", + "/enterprise/v4/input_object/refupdate": "/enterprise-server@latest/graphql/reference/input-objects#refupdate", + "/enterprise/v4/input_object/registrypackagemetadatum": "/enterprise-server@latest/graphql/reference/input-objects#registrypackagemetadatum", + "/enterprise/v4/input_object/releaseorder": "/enterprise-server@latest/graphql/reference/input-objects#releaseorder", + "/enterprise/v4/input_object/removeassigneesfromassignableinput": "/enterprise-server@latest/graphql/reference/input-objects#removeassigneesfromassignableinput", + "/enterprise/v4/input_object/removeenterpriseadmininput": "/enterprise-server@latest/graphql/reference/input-objects#removeenterpriseadmininput", + "/enterprise/v4/input_object/removelabelsfromlabelableinput": "/enterprise-server@latest/graphql/reference/input-objects#removelabelsfromlabelableinput", + "/enterprise/v4/input_object/removeoutsidecollaboratorinput": "/enterprise-server@latest/graphql/reference/input-objects#removeoutsidecollaboratorinput", + "/enterprise/v4/input_object/removereactioninput": "/enterprise-server@latest/graphql/reference/input-objects#removereactioninput", + "/enterprise/v4/input_object/removestarinput": "/enterprise-server@latest/graphql/reference/input-objects#removestarinput", + "/enterprise/v4/input_object/reopenissueinput": "/enterprise-server@latest/graphql/reference/input-objects#reopenissueinput", + "/enterprise/v4/input_object/reopenpullrequestinput": "/enterprise-server@latest/graphql/reference/input-objects#reopenpullrequestinput", + "/enterprise/v4/input_object/repositoryinvitationorder": "/enterprise-server@latest/graphql/reference/input-objects#repositoryinvitationorder", + "/enterprise/v4/input_object/repositoryorder": "/enterprise-server@latest/graphql/reference/input-objects#repositoryorder", + "/enterprise/v4/input_object/requestreviewsinput": "/enterprise-server@latest/graphql/reference/input-objects#requestreviewsinput", + "/enterprise/v4/input_object/rerequestchecksuiteinput": "/enterprise-server@latest/graphql/reference/input-objects#rerequestchecksuiteinput", + "/enterprise/v4/input_object/resolvereviewthreadinput": "/enterprise-server@latest/graphql/reference/input-objects#resolvereviewthreadinput", + "/enterprise/v4/input_object/savedreplyorder": "/enterprise-server@latest/graphql/reference/input-objects#savedreplyorder", + "/enterprise/v4/input_object/sponsorshiporder": "/enterprise-server@latest/graphql/reference/input-objects#sponsorshiporder", + "/enterprise/v4/input_object/starorder": "/enterprise-server@latest/graphql/reference/input-objects#starorder", + "/enterprise/v4/input_object/submitpullrequestreviewinput": "/enterprise-server@latest/graphql/reference/input-objects#submitpullrequestreviewinput", + "/enterprise/v4/input_object/teamdiscussioncommentorder": "/enterprise-server@latest/graphql/reference/input-objects#teamdiscussioncommentorder", + "/enterprise/v4/input_object/teamdiscussionorder": "/enterprise-server@latest/graphql/reference/input-objects#teamdiscussionorder", + "/enterprise/v4/input_object/teammemberorder": "/enterprise-server@latest/graphql/reference/input-objects#teammemberorder", + "/enterprise/v4/input_object/teamorder": "/enterprise-server@latest/graphql/reference/input-objects#teamorder", + "/enterprise/v4/input_object/teamrepositoryorder": "/enterprise-server@latest/graphql/reference/input-objects#teamrepositoryorder", + "/enterprise/v4/input_object/transferissueinput": "/enterprise-server@latest/graphql/reference/input-objects#transferissueinput", + "/enterprise/v4/input_object/unarchiverepositoryinput": "/enterprise-server@latest/graphql/reference/input-objects#unarchiverepositoryinput", + "/enterprise/v4/input_object/unfollowuserinput": "/enterprise-server@latest/graphql/reference/input-objects#unfollowuserinput", + "/enterprise/v4/input_object/unlinkrepositoryfromprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", + "/enterprise/v4/input_object/unlocklockableinput": "/enterprise-server@latest/graphql/reference/input-objects#unlocklockableinput", + "/enterprise/v4/input_object/unmarkissueasduplicateinput": "/enterprise-server@latest/graphql/reference/input-objects#unmarkissueasduplicateinput", + "/enterprise/v4/input_object/unminimizecommentinput": "/enterprise-server@latest/graphql/reference/input-objects#unminimizecommentinput", + "/enterprise/v4/input_object/unpinissueinput": "/enterprise-server@latest/graphql/reference/input-objects#unpinissueinput", + "/enterprise/v4/input_object/unresolvereviewthreadinput": "/enterprise-server@latest/graphql/reference/input-objects#unresolvereviewthreadinput", + "/enterprise/v4/input_object/updatebranchprotectionruleinput": "/enterprise-server@latest/graphql/reference/input-objects#updatebranchprotectionruleinput", + "/enterprise/v4/input_object/updatecheckruninput": "/enterprise-server@latest/graphql/reference/input-objects#updatecheckruninput", + "/enterprise/v4/input_object/updatechecksuitepreferencesinput": "/enterprise-server@latest/graphql/reference/input-objects#updatechecksuitepreferencesinput", + "/enterprise/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", + "/enterprise/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", + "/enterprise/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", + "/enterprise/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", + "/enterprise/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", + "/enterprise/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", + "/enterprise/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", + "/enterprise/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", + "/enterprise/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", + "/enterprise/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", + "/enterprise/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", + "/enterprise/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", + "/enterprise/v4/input_object/updateenterpriseprofileinput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseprofileinput", + "/enterprise/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", + "/enterprise/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", + "/enterprise/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", + "/enterprise/v4/input_object/updateipallowlistenabledsettinginput": "/enterprise-server@latest/graphql/reference/input-objects#updateipallowlistenabledsettinginput", + "/enterprise/v4/input_object/updateipallowlistentryinput": "/enterprise-server@latest/graphql/reference/input-objects#updateipallowlistentryinput", + "/enterprise/v4/input_object/updateissuecommentinput": "/enterprise-server@latest/graphql/reference/input-objects#updateissuecommentinput", + "/enterprise/v4/input_object/updateissueinput": "/enterprise-server@latest/graphql/reference/input-objects#updateissueinput", + "/enterprise/v4/input_object/updatelabelinput": "/enterprise-server@latest/graphql/reference/input-objects#updatelabelinput", + "/enterprise/v4/input_object/updateprojectcardinput": "/enterprise-server@latest/graphql/reference/input-objects#updateprojectcardinput", + "/enterprise/v4/input_object/updateprojectcolumninput": "/enterprise-server@latest/graphql/reference/input-objects#updateprojectcolumninput", + "/enterprise/v4/input_object/updateprojectinput": "/enterprise-server@latest/graphql/reference/input-objects#updateprojectinput", + "/enterprise/v4/input_object/updatepullrequestinput": "/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestinput", + "/enterprise/v4/input_object/updatepullrequestreviewcommentinput": "/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestreviewcommentinput", + "/enterprise/v4/input_object/updatepullrequestreviewinput": "/enterprise-server@latest/graphql/reference/input-objects#updatepullrequestreviewinput", + "/enterprise/v4/input_object/updaterefinput": "/enterprise-server@latest/graphql/reference/input-objects#updaterefinput", + "/enterprise/v4/input_object/updaterefsinput": "/enterprise-server@latest/graphql/reference/input-objects#updaterefsinput", + "/enterprise/v4/input_object/updaterepositoryinput": "/enterprise-server@latest/graphql/reference/input-objects#updaterepositoryinput", + "/enterprise/v4/input_object/updatesubscriptioninput": "/enterprise-server@latest/graphql/reference/input-objects#updatesubscriptioninput", + "/enterprise/v4/input_object/updateteamdiscussioncommentinput": "/enterprise-server@latest/graphql/reference/input-objects#updateteamdiscussioncommentinput", + "/enterprise/v4/input_object/updateteamdiscussioninput": "/enterprise-server@latest/graphql/reference/input-objects#updateteamdiscussioninput", + "/enterprise/v4/input_object/updateteamreviewassignmentinput": "/enterprise-server@latest/graphql/reference/input-objects#updateteamreviewassignmentinput", + "/enterprise/v4/input_object/updatetopicsinput": "/enterprise-server@latest/graphql/reference/input-objects#updatetopicsinput", + "/enterprise/v4/input_object/userstatusorder": "/enterprise-server@latest/graphql/reference/input-objects#userstatusorder", + "/enterprise/v4/interface/actor": "/enterprise-server@latest/graphql/reference/interfaces#actor", + "/enterprise/v4/interface/assignable": "/enterprise-server@latest/graphql/reference/interfaces#assignable", + "/enterprise/v4/interface/auditentry": "/enterprise-server@latest/graphql/reference/interfaces#auditentry", + "/enterprise/v4/interface/closable": "/enterprise-server@latest/graphql/reference/interfaces#closable", + "/enterprise/v4/interface/comment": "/enterprise-server@latest/graphql/reference/interfaces#comment", + "/enterprise/v4/interface/contribution": "/enterprise-server@latest/graphql/reference/interfaces#contribution", + "/enterprise/v4/interface/deletable": "/enterprise-server@latest/graphql/reference/interfaces#deletable", + "/enterprise/v4/interface/enterpriseauditentrydata": "/enterprise-server@latest/graphql/reference/interfaces#enterpriseauditentrydata", + "/enterprise/v4/interface/gitobject": "/enterprise-server@latest/graphql/reference/interfaces#gitobject", + "/enterprise/v4/interface/gitsignature": "/enterprise-server@latest/graphql/reference/interfaces#gitsignature", + "/enterprise/v4/interface/hovercardcontext": "/enterprise-server@latest/graphql/reference/interfaces#hovercardcontext", + "/enterprise/v4/interface/labelable": "/enterprise-server@latest/graphql/reference/interfaces#labelable", + "/enterprise/v4/interface/lockable": "/enterprise-server@latest/graphql/reference/interfaces#lockable", + "/enterprise/v4/interface/memberstatusable": "/enterprise-server@latest/graphql/reference/interfaces#memberstatusable", + "/enterprise/v4/interface/minimizable": "/enterprise-server@latest/graphql/reference/interfaces#minimizable", + "/enterprise/v4/interface/node": "/enterprise-server@latest/graphql/reference/interfaces#node", + "/enterprise/v4/interface/oauthapplicationauditentrydata": "/enterprise-server@latest/graphql/reference/interfaces#oauthapplicationauditentrydata", + "/enterprise/v4/interface/organizationauditentrydata": "/enterprise-server@latest/graphql/reference/interfaces#organizationauditentrydata", + "/enterprise/v4/interface/packageowner": "/enterprise-server@latest/graphql/reference/interfaces#packageowner", + "/enterprise/v4/interface/profileowner": "/enterprise-server@latest/graphql/reference/interfaces#profileowner", + "/enterprise/v4/interface/projectowner": "/enterprise-server@latest/graphql/reference/interfaces#projectowner", + "/enterprise/v4/interface/reactable": "/enterprise-server@latest/graphql/reference/interfaces#reactable", + "/enterprise/v4/interface/registrypackageowner": "/enterprise-server@latest/graphql/reference/interfaces#registrypackageowner", + "/enterprise/v4/interface/registrypackagesearch": "/enterprise-server@latest/graphql/reference/interfaces#registrypackagesearch", + "/enterprise/v4/interface/repositoryauditentrydata": "/enterprise-server@latest/graphql/reference/interfaces#repositoryauditentrydata", + "/enterprise/v4/interface/repositoryinfo": "/enterprise-server@latest/graphql/reference/interfaces#repositoryinfo", + "/enterprise/v4/interface/repositorynode": "/enterprise-server@latest/graphql/reference/interfaces#repositorynode", + "/enterprise/v4/interface/repositoryowner": "/enterprise-server@latest/graphql/reference/interfaces#repositoryowner", + "/enterprise/v4/interface/starrable": "/enterprise-server@latest/graphql/reference/interfaces#starrable", + "/enterprise/v4/interface/subscribable": "/enterprise-server@latest/graphql/reference/interfaces#subscribable", + "/enterprise/v4/interface/teamauditentrydata": "/enterprise-server@latest/graphql/reference/interfaces#teamauditentrydata", + "/enterprise/v4/interface/topicauditentrydata": "/enterprise-server@latest/graphql/reference/interfaces#topicauditentrydata", + "/enterprise/v4/interface/uniformresourcelocatable": "/enterprise-server@latest/graphql/reference/interfaces#uniformresourcelocatable", + "/enterprise/v4/interface/updatable": "/enterprise-server@latest/graphql/reference/interfaces#updatable", + "/enterprise/v4/interface/updatablecomment": "/enterprise-server@latest/graphql/reference/interfaces#updatablecomment", + "/enterprise/v4/mutation/addassigneestoassignable": "/enterprise-server@latest/graphql/reference/mutations#addassigneestoassignable", + "/enterprise/v4/mutation/addcomment": "/enterprise-server@latest/graphql/reference/mutations#addcomment", + "/enterprise/v4/mutation/addenterpriseadmin": "/enterprise-server@latest/graphql/reference/mutations#addenterpriseadmin", + "/enterprise/v4/mutation/addlabelstolabelable": "/enterprise-server@latest/graphql/reference/mutations#addlabelstolabelable", + "/enterprise/v4/mutation/addprojectcard": "/enterprise-server@latest/graphql/reference/mutations#addprojectcard", + "/enterprise/v4/mutation/addprojectcolumn": "/enterprise-server@latest/graphql/reference/mutations#addprojectcolumn", + "/enterprise/v4/mutation/addpullrequestreview": "/enterprise-server@latest/graphql/reference/mutations#addpullrequestreview", + "/enterprise/v4/mutation/addpullrequestreviewcomment": "/enterprise-server@latest/graphql/reference/mutations#addpullrequestreviewcomment", + "/enterprise/v4/mutation/addpullrequestreviewthread": "/enterprise-server@latest/graphql/reference/mutations#addpullrequestreviewthread", + "/enterprise/v4/mutation/addreaction": "/enterprise-server@latest/graphql/reference/mutations#addreaction", + "/enterprise/v4/mutation/addstar": "/enterprise-server@latest/graphql/reference/mutations#addstar", + "/enterprise/v4/mutation/archiverepository": "/enterprise-server@latest/graphql/reference/mutations#archiverepository", + "/enterprise/v4/mutation/changeuserstatus": "/enterprise-server@latest/graphql/reference/mutations#changeuserstatus", + "/enterprise/v4/mutation/clearlabelsfromlabelable": "/enterprise-server@latest/graphql/reference/mutations#clearlabelsfromlabelable", + "/enterprise/v4/mutation/cloneproject": "/enterprise-server@latest/graphql/reference/mutations#cloneproject", + "/enterprise/v4/mutation/clonetemplaterepository": "/enterprise-server@latest/graphql/reference/mutations#clonetemplaterepository", + "/enterprise/v4/mutation/closeissue": "/enterprise-server@latest/graphql/reference/mutations#closeissue", + "/enterprise/v4/mutation/closepullrequest": "/enterprise-server@latest/graphql/reference/mutations#closepullrequest", + "/enterprise/v4/mutation/convertprojectcardnotetoissue": "/enterprise-server@latest/graphql/reference/mutations#convertprojectcardnotetoissue", + "/enterprise/v4/mutation/createbranchprotectionrule": "/enterprise-server@latest/graphql/reference/mutations#createbranchprotectionrule", + "/enterprise/v4/mutation/createcheckrun": "/enterprise-server@latest/graphql/reference/mutations#createcheckrun", + "/enterprise/v4/mutation/createchecksuite": "/enterprise-server@latest/graphql/reference/mutations#createchecksuite", + "/enterprise/v4/mutation/createcontentattachment": "/enterprise-server@latest/graphql/reference/mutations#createcontentattachment", + "/enterprise/v4/mutation/createdeployment": "/enterprise-server@latest/graphql/reference/mutations#createdeployment", + "/enterprise/v4/mutation/createdeploymentstatus": "/enterprise-server@latest/graphql/reference/mutations#createdeploymentstatus", + "/enterprise/v4/mutation/createipallowlistentry": "/enterprise-server@latest/graphql/reference/mutations#createipallowlistentry", + "/enterprise/v4/mutation/createissue": "/enterprise-server@latest/graphql/reference/mutations#createissue", + "/enterprise/v4/mutation/createlabel": "/enterprise-server@latest/graphql/reference/mutations#createlabel", + "/enterprise/v4/mutation/createproject": "/enterprise-server@latest/graphql/reference/mutations#createproject", + "/enterprise/v4/mutation/createpullrequest": "/enterprise-server@latest/graphql/reference/mutations#createpullrequest", + "/enterprise/v4/mutation/createref": "/enterprise-server@latest/graphql/reference/mutations#createref", + "/enterprise/v4/mutation/createrepository": "/enterprise-server@latest/graphql/reference/mutations#createrepository", + "/enterprise/v4/mutation/createteamdiscussion": "/enterprise-server@latest/graphql/reference/mutations#createteamdiscussion", + "/enterprise/v4/mutation/createteamdiscussioncomment": "/enterprise-server@latest/graphql/reference/mutations#createteamdiscussioncomment", + "/enterprise/v4/mutation/deletebranchprotectionrule": "/enterprise-server@latest/graphql/reference/mutations#deletebranchprotectionrule", + "/enterprise/v4/mutation/deletedeployment": "/enterprise-server@latest/graphql/reference/mutations#deletedeployment", + "/enterprise/v4/mutation/deleteipallowlistentry": "/enterprise-server@latest/graphql/reference/mutations#deleteipallowlistentry", + "/enterprise/v4/mutation/deleteissue": "/enterprise-server@latest/graphql/reference/mutations#deleteissue", + "/enterprise/v4/mutation/deleteissuecomment": "/enterprise-server@latest/graphql/reference/mutations#deleteissuecomment", + "/enterprise/v4/mutation/deletelabel": "/enterprise-server@latest/graphql/reference/mutations#deletelabel", + "/enterprise/v4/mutation/deletepackageversion": "/enterprise-server@latest/graphql/reference/mutations#deletepackageversion", + "/enterprise/v4/mutation/deleteproject": "/enterprise-server@latest/graphql/reference/mutations#deleteproject", + "/enterprise/v4/mutation/deleteprojectcard": "/enterprise-server@latest/graphql/reference/mutations#deleteprojectcard", + "/enterprise/v4/mutation/deleteprojectcolumn": "/enterprise-server@latest/graphql/reference/mutations#deleteprojectcolumn", + "/enterprise/v4/mutation/deletepullrequestreview": "/enterprise-server@latest/graphql/reference/mutations#deletepullrequestreview", + "/enterprise/v4/mutation/deletepullrequestreviewcomment": "/enterprise-server@latest/graphql/reference/mutations#deletepullrequestreviewcomment", + "/enterprise/v4/mutation/deleteref": "/enterprise-server@latest/graphql/reference/mutations#deleteref", + "/enterprise/v4/mutation/deleteteamdiscussion": "/enterprise-server@latest/graphql/reference/mutations#deleteteamdiscussion", + "/enterprise/v4/mutation/deleteteamdiscussioncomment": "/enterprise-server@latest/graphql/reference/mutations#deleteteamdiscussioncomment", + "/enterprise/v4/mutation/dismisspullrequestreview": "/enterprise-server@latest/graphql/reference/mutations#dismisspullrequestreview", + "/enterprise/v4/mutation/followuser": "/enterprise-server@latest/graphql/reference/mutations#followuser", + "/enterprise/v4/mutation/importproject": "/enterprise-server@latest/graphql/reference/mutations#importproject", + "/enterprise/v4/mutation/linkrepositorytoproject": "/enterprise-server@latest/graphql/reference/mutations#linkrepositorytoproject", + "/enterprise/v4/mutation/locklockable": "/enterprise-server@latest/graphql/reference/mutations#locklockable", + "/enterprise/v4/mutation/markpullrequestreadyforreview": "/enterprise-server@latest/graphql/reference/mutations#markpullrequestreadyforreview", + "/enterprise/v4/mutation/mergebranch": "/enterprise-server@latest/graphql/reference/mutations#mergebranch", + "/enterprise/v4/mutation/mergepullrequest": "/enterprise-server@latest/graphql/reference/mutations#mergepullrequest", + "/enterprise/v4/mutation/minimizecomment": "/enterprise-server@latest/graphql/reference/mutations#minimizecomment", + "/enterprise/v4/mutation/moveprojectcard": "/enterprise-server@latest/graphql/reference/mutations#moveprojectcard", + "/enterprise/v4/mutation/moveprojectcolumn": "/enterprise-server@latest/graphql/reference/mutations#moveprojectcolumn", + "/enterprise/v4/mutation/pinissue": "/enterprise-server@latest/graphql/reference/mutations#pinissue", + "/enterprise/v4/mutation/removeassigneesfromassignable": "/enterprise-server@latest/graphql/reference/mutations#removeassigneesfromassignable", + "/enterprise/v4/mutation/removeenterpriseadmin": "/enterprise-server@latest/graphql/reference/mutations#removeenterpriseadmin", + "/enterprise/v4/mutation/removelabelsfromlabelable": "/enterprise-server@latest/graphql/reference/mutations#removelabelsfromlabelable", + "/enterprise/v4/mutation/removeoutsidecollaborator": "/enterprise-server@latest/graphql/reference/mutations#removeoutsidecollaborator", + "/enterprise/v4/mutation/removereaction": "/enterprise-server@latest/graphql/reference/mutations#removereaction", + "/enterprise/v4/mutation/removestar": "/enterprise-server@latest/graphql/reference/mutations#removestar", + "/enterprise/v4/mutation/reopenissue": "/enterprise-server@latest/graphql/reference/mutations#reopenissue", + "/enterprise/v4/mutation/reopenpullrequest": "/enterprise-server@latest/graphql/reference/mutations#reopenpullrequest", + "/enterprise/v4/mutation/requestreviews": "/enterprise-server@latest/graphql/reference/mutations#requestreviews", + "/enterprise/v4/mutation/rerequestchecksuite": "/enterprise-server@latest/graphql/reference/mutations#rerequestchecksuite", + "/enterprise/v4/mutation/resolvereviewthread": "/enterprise-server@latest/graphql/reference/mutations#resolvereviewthread", + "/enterprise/v4/mutation/submitpullrequestreview": "/enterprise-server@latest/graphql/reference/mutations#submitpullrequestreview", + "/enterprise/v4/mutation/transferissue": "/enterprise-server@latest/graphql/reference/mutations#transferissue", + "/enterprise/v4/mutation/unarchiverepository": "/enterprise-server@latest/graphql/reference/mutations#unarchiverepository", + "/enterprise/v4/mutation/unfollowuser": "/enterprise-server@latest/graphql/reference/mutations#unfollowuser", + "/enterprise/v4/mutation/unlinkrepositoryfromproject": "/enterprise-server@latest/graphql/reference/mutations#unlinkrepositoryfromproject", + "/enterprise/v4/mutation/unlocklockable": "/enterprise-server@latest/graphql/reference/mutations#unlocklockable", + "/enterprise/v4/mutation/unmarkissueasduplicate": "/enterprise-server@latest/graphql/reference/mutations#unmarkissueasduplicate", + "/enterprise/v4/mutation/unminimizecomment": "/enterprise-server@latest/graphql/reference/mutations#unminimizecomment", + "/enterprise/v4/mutation/unpinissue": "/enterprise-server@latest/graphql/reference/mutations#unpinissue", + "/enterprise/v4/mutation/unresolvereviewthread": "/enterprise-server@latest/graphql/reference/mutations#unresolvereviewthread", + "/enterprise/v4/mutation/updatebranchprotectionrule": "/enterprise-server@latest/graphql/reference/mutations#updatebranchprotectionrule", + "/enterprise/v4/mutation/updatecheckrun": "/enterprise-server@latest/graphql/reference/mutations#updatecheckrun", + "/enterprise/v4/mutation/updatechecksuitepreferences": "/enterprise-server@latest/graphql/reference/mutations#updatechecksuitepreferences", + "/enterprise/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", + "/enterprise/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", + "/enterprise/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", + "/enterprise/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", + "/enterprise/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", + "/enterprise/v4/mutation/updateenterprisememberscandeleteissuessetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", + "/enterprise/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", + "/enterprise/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", + "/enterprise/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", + "/enterprise/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", + "/enterprise/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", + "/enterprise/v4/mutation/updateenterpriseorganizationprojectssetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", + "/enterprise/v4/mutation/updateenterpriseprofile": "/enterprise-server@latest/graphql/reference/mutations#updateenterpriseprofile", + "/enterprise/v4/mutation/updateenterpriserepositoryprojectssetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", + "/enterprise/v4/mutation/updateenterpriseteamdiscussionssetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", + "/enterprise/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/enterprise-server@latest/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", + "/enterprise/v4/mutation/updateipallowlistenabledsetting": "/enterprise-server@latest/graphql/reference/mutations#updateipallowlistenabledsetting", + "/enterprise/v4/mutation/updateipallowlistentry": "/enterprise-server@latest/graphql/reference/mutations#updateipallowlistentry", + "/enterprise/v4/mutation/updateissue": "/enterprise-server@latest/graphql/reference/mutations#updateissue", + "/enterprise/v4/mutation/updateissuecomment": "/enterprise-server@latest/graphql/reference/mutations#updateissuecomment", + "/enterprise/v4/mutation/updatelabel": "/enterprise-server@latest/graphql/reference/mutations#updatelabel", + "/enterprise/v4/mutation/updateproject": "/enterprise-server@latest/graphql/reference/mutations#updateproject", + "/enterprise/v4/mutation/updateprojectcard": "/enterprise-server@latest/graphql/reference/mutations#updateprojectcard", + "/enterprise/v4/mutation/updateprojectcolumn": "/enterprise-server@latest/graphql/reference/mutations#updateprojectcolumn", + "/enterprise/v4/mutation/updatepullrequest": "/enterprise-server@latest/graphql/reference/mutations#updatepullrequest", + "/enterprise/v4/mutation/updatepullrequestreview": "/enterprise-server@latest/graphql/reference/mutations#updatepullrequestreview", + "/enterprise/v4/mutation/updatepullrequestreviewcomment": "/enterprise-server@latest/graphql/reference/mutations#updatepullrequestreviewcomment", + "/enterprise/v4/mutation/updateref": "/enterprise-server@latest/graphql/reference/mutations#updateref", + "/enterprise/v4/mutation/updaterefs": "/enterprise-server@latest/graphql/reference/mutations#updaterefs", + "/enterprise/v4/mutation/updaterepository": "/enterprise-server@latest/graphql/reference/mutations#updaterepository", + "/enterprise/v4/mutation/updatesubscription": "/enterprise-server@latest/graphql/reference/mutations#updatesubscription", + "/enterprise/v4/mutation/updateteamdiscussion": "/enterprise-server@latest/graphql/reference/mutations#updateteamdiscussion", + "/enterprise/v4/mutation/updateteamdiscussioncomment": "/enterprise-server@latest/graphql/reference/mutations#updateteamdiscussioncomment", + "/enterprise/v4/mutation/updateteamreviewassignment": "/enterprise-server@latest/graphql/reference/mutations#updateteamreviewassignment", + "/enterprise/v4/mutation/updatetopics": "/enterprise-server@latest/graphql/reference/mutations#updatetopics", + "/enterprise/v4/object/__directive": "/enterprise-server@latest/graphql/reference/objects#__directive", + "/enterprise/v4/object/__enumvalue": "/enterprise-server@latest/graphql/reference/objects#__enumvalue", + "/enterprise/v4/object/__field": "/enterprise-server@latest/graphql/reference/objects#__field", + "/enterprise/v4/object/__inputvalue": "/enterprise-server@latest/graphql/reference/objects#__inputvalue", + "/enterprise/v4/object/__schema": "/enterprise-server@latest/graphql/reference/objects#__schema", + "/enterprise/v4/object/__type": "/enterprise-server@latest/graphql/reference/objects#__type", + "/enterprise/v4/object/actorlocation": "/enterprise-server@latest/graphql/reference/objects#actorlocation", + "/enterprise/v4/object/addassigneestoassignablepayload": "/enterprise-server@latest/graphql/reference/objects#addassigneestoassignablepayload", + "/enterprise/v4/object/addcommentpayload": "/enterprise-server@latest/graphql/reference/objects#addcommentpayload", + "/enterprise/v4/object/addedtoprojectevent": "/enterprise-server@latest/graphql/reference/objects#addedtoprojectevent", + "/enterprise/v4/object/addenterpriseadminpayload": "/enterprise-server@latest/graphql/reference/objects#addenterpriseadminpayload", + "/enterprise/v4/object/addlabelstolabelablepayload": "/enterprise-server@latest/graphql/reference/objects#addlabelstolabelablepayload", + "/enterprise/v4/object/addprojectcardpayload": "/enterprise-server@latest/graphql/reference/objects#addprojectcardpayload", + "/enterprise/v4/object/addprojectcolumnpayload": "/enterprise-server@latest/graphql/reference/objects#addprojectcolumnpayload", + "/enterprise/v4/object/addpullrequestreviewcommentpayload": "/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewcommentpayload", + "/enterprise/v4/object/addpullrequestreviewpayload": "/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewpayload", + "/enterprise/v4/object/addpullrequestreviewthreadpayload": "/enterprise-server@latest/graphql/reference/objects#addpullrequestreviewthreadpayload", + "/enterprise/v4/object/addreactionpayload": "/enterprise-server@latest/graphql/reference/objects#addreactionpayload", + "/enterprise/v4/object/addstarpayload": "/enterprise-server@latest/graphql/reference/objects#addstarpayload", + "/enterprise/v4/object/app": "/enterprise-server@latest/graphql/reference/objects#app", + "/enterprise/v4/object/archiverepositorypayload": "/enterprise-server@latest/graphql/reference/objects#archiverepositorypayload", + "/enterprise/v4/object/assignedevent": "/enterprise-server@latest/graphql/reference/objects#assignedevent", + "/enterprise/v4/object/baserefchangedevent": "/enterprise-server@latest/graphql/reference/objects#baserefchangedevent", + "/enterprise/v4/object/baserefforcepushedevent": "/enterprise-server@latest/graphql/reference/objects#baserefforcepushedevent", + "/enterprise/v4/object/blame": "/enterprise-server@latest/graphql/reference/objects#blame", + "/enterprise/v4/object/blamerange": "/enterprise-server@latest/graphql/reference/objects#blamerange", + "/enterprise/v4/object/blob": "/enterprise-server@latest/graphql/reference/objects#blob", + "/enterprise/v4/object/bot": "/enterprise-server@latest/graphql/reference/objects#bot", + "/enterprise/v4/object/branchprotectionrule": "/enterprise-server@latest/graphql/reference/objects#branchprotectionrule", + "/enterprise/v4/object/branchprotectionruleconflict": "/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflict", + "/enterprise/v4/object/branchprotectionruleconflictconnection": "/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflictconnection", + "/enterprise/v4/object/branchprotectionruleconflictedge": "/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconflictedge", + "/enterprise/v4/object/branchprotectionruleconnection": "/enterprise-server@latest/graphql/reference/objects#branchprotectionruleconnection", + "/enterprise/v4/object/branchprotectionruleedge": "/enterprise-server@latest/graphql/reference/objects#branchprotectionruleedge", + "/enterprise/v4/object/changeuserstatuspayload": "/enterprise-server@latest/graphql/reference/objects#changeuserstatuspayload", + "/enterprise/v4/object/checkannotation": "/enterprise-server@latest/graphql/reference/objects#checkannotation", + "/enterprise/v4/object/checkannotationconnection": "/enterprise-server@latest/graphql/reference/objects#checkannotationconnection", + "/enterprise/v4/object/checkannotationedge": "/enterprise-server@latest/graphql/reference/objects#checkannotationedge", + "/enterprise/v4/object/checkannotationposition": "/enterprise-server@latest/graphql/reference/objects#checkannotationposition", + "/enterprise/v4/object/checkannotationspan": "/enterprise-server@latest/graphql/reference/objects#checkannotationspan", + "/enterprise/v4/object/checkrun": "/enterprise-server@latest/graphql/reference/objects#checkrun", + "/enterprise/v4/object/checkrunconnection": "/enterprise-server@latest/graphql/reference/objects#checkrunconnection", + "/enterprise/v4/object/checkrunedge": "/enterprise-server@latest/graphql/reference/objects#checkrunedge", + "/enterprise/v4/object/checksuite": "/enterprise-server@latest/graphql/reference/objects#checksuite", + "/enterprise/v4/object/checksuiteconnection": "/enterprise-server@latest/graphql/reference/objects#checksuiteconnection", + "/enterprise/v4/object/checksuiteedge": "/enterprise-server@latest/graphql/reference/objects#checksuiteedge", + "/enterprise/v4/object/clearlabelsfromlabelablepayload": "/enterprise-server@latest/graphql/reference/objects#clearlabelsfromlabelablepayload", + "/enterprise/v4/object/cloneprojectpayload": "/enterprise-server@latest/graphql/reference/objects#cloneprojectpayload", + "/enterprise/v4/object/clonetemplaterepositorypayload": "/enterprise-server@latest/graphql/reference/objects#clonetemplaterepositorypayload", + "/enterprise/v4/object/closedevent": "/enterprise-server@latest/graphql/reference/objects#closedevent", + "/enterprise/v4/object/closeissuepayload": "/enterprise-server@latest/graphql/reference/objects#closeissuepayload", + "/enterprise/v4/object/closepullrequestpayload": "/enterprise-server@latest/graphql/reference/objects#closepullrequestpayload", + "/enterprise/v4/object/codeofconduct": "/enterprise-server@latest/graphql/reference/objects#codeofconduct", + "/enterprise/v4/object/commentdeletedevent": "/enterprise-server@latest/graphql/reference/objects#commentdeletedevent", + "/enterprise/v4/object/commit": "/enterprise-server@latest/graphql/reference/objects#commit", + "/enterprise/v4/object/commitcomment": "/enterprise-server@latest/graphql/reference/objects#commitcomment", + "/enterprise/v4/object/commitcommentconnection": "/enterprise-server@latest/graphql/reference/objects#commitcommentconnection", + "/enterprise/v4/object/commitcommentedge": "/enterprise-server@latest/graphql/reference/objects#commitcommentedge", + "/enterprise/v4/object/commitcommentthread": "/enterprise-server@latest/graphql/reference/objects#commitcommentthread", + "/enterprise/v4/object/commitconnection": "/enterprise-server@latest/graphql/reference/objects#commitconnection", + "/enterprise/v4/object/commitcontributionsbyrepository": "/enterprise-server@latest/graphql/reference/objects#commitcontributionsbyrepository", + "/enterprise/v4/object/commitedge": "/enterprise-server@latest/graphql/reference/objects#commitedge", + "/enterprise/v4/object/commithistoryconnection": "/enterprise-server@latest/graphql/reference/objects#commithistoryconnection", + "/enterprise/v4/object/connectedevent": "/enterprise-server@latest/graphql/reference/objects#connectedevent", + "/enterprise/v4/object/contentattachment": "/enterprise-server@latest/graphql/reference/objects#contentattachment", + "/enterprise/v4/object/contentreference": "/enterprise-server@latest/graphql/reference/objects#contentreference", + "/enterprise/v4/object/contributioncalendar": "/enterprise-server@latest/graphql/reference/objects#contributioncalendar", + "/enterprise/v4/object/contributioncalendarday": "/enterprise-server@latest/graphql/reference/objects#contributioncalendarday", + "/enterprise/v4/object/contributioncalendarmonth": "/enterprise-server@latest/graphql/reference/objects#contributioncalendarmonth", + "/enterprise/v4/object/contributioncalendarweek": "/enterprise-server@latest/graphql/reference/objects#contributioncalendarweek", + "/enterprise/v4/object/contributionscollection": "/enterprise-server@latest/graphql/reference/objects#contributionscollection", + "/enterprise/v4/object/convertednotetoissueevent": "/enterprise-server@latest/graphql/reference/objects#convertednotetoissueevent", + "/enterprise/v4/object/convertprojectcardnotetoissuepayload": "/enterprise-server@latest/graphql/reference/objects#convertprojectcardnotetoissuepayload", + "/enterprise/v4/object/converttodraftevent": "/enterprise-server@latest/graphql/reference/objects#converttodraftevent", + "/enterprise/v4/object/createbranchprotectionrulepayload": "/enterprise-server@latest/graphql/reference/objects#createbranchprotectionrulepayload", + "/enterprise/v4/object/createcheckrunpayload": "/enterprise-server@latest/graphql/reference/objects#createcheckrunpayload", + "/enterprise/v4/object/createchecksuitepayload": "/enterprise-server@latest/graphql/reference/objects#createchecksuitepayload", + "/enterprise/v4/object/createcontentattachmentpayload": "/enterprise-server@latest/graphql/reference/objects#createcontentattachmentpayload", + "/enterprise/v4/object/createdcommitcontribution": "/enterprise-server@latest/graphql/reference/objects#createdcommitcontribution", + "/enterprise/v4/object/createdcommitcontributionconnection": "/enterprise-server@latest/graphql/reference/objects#createdcommitcontributionconnection", + "/enterprise/v4/object/createdcommitcontributionedge": "/enterprise-server@latest/graphql/reference/objects#createdcommitcontributionedge", + "/enterprise/v4/object/createdeploymentpayload": "/enterprise-server@latest/graphql/reference/objects#createdeploymentpayload", + "/enterprise/v4/object/createdeploymentstatuspayload": "/enterprise-server@latest/graphql/reference/objects#createdeploymentstatuspayload", + "/enterprise/v4/object/createdissuecontribution": "/enterprise-server@latest/graphql/reference/objects#createdissuecontribution", + "/enterprise/v4/object/createdissuecontributionconnection": "/enterprise-server@latest/graphql/reference/objects#createdissuecontributionconnection", + "/enterprise/v4/object/createdissuecontributionedge": "/enterprise-server@latest/graphql/reference/objects#createdissuecontributionedge", + "/enterprise/v4/object/createdpullrequestcontribution": "/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontribution", + "/enterprise/v4/object/createdpullrequestcontributionconnection": "/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontributionconnection", + "/enterprise/v4/object/createdpullrequestcontributionedge": "/enterprise-server@latest/graphql/reference/objects#createdpullrequestcontributionedge", + "/enterprise/v4/object/createdpullrequestreviewcontribution": "/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontribution", + "/enterprise/v4/object/createdpullrequestreviewcontributionconnection": "/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontributionconnection", + "/enterprise/v4/object/createdpullrequestreviewcontributionedge": "/enterprise-server@latest/graphql/reference/objects#createdpullrequestreviewcontributionedge", + "/enterprise/v4/object/createdrepositorycontribution": "/enterprise-server@latest/graphql/reference/objects#createdrepositorycontribution", + "/enterprise/v4/object/createdrepositorycontributionconnection": "/enterprise-server@latest/graphql/reference/objects#createdrepositorycontributionconnection", + "/enterprise/v4/object/createdrepositorycontributionedge": "/enterprise-server@latest/graphql/reference/objects#createdrepositorycontributionedge", + "/enterprise/v4/object/createipallowlistentrypayload": "/enterprise-server@latest/graphql/reference/objects#createipallowlistentrypayload", + "/enterprise/v4/object/createissuepayload": "/enterprise-server@latest/graphql/reference/objects#createissuepayload", + "/enterprise/v4/object/createlabelpayload": "/enterprise-server@latest/graphql/reference/objects#createlabelpayload", + "/enterprise/v4/object/createprojectpayload": "/enterprise-server@latest/graphql/reference/objects#createprojectpayload", + "/enterprise/v4/object/createpullrequestpayload": "/enterprise-server@latest/graphql/reference/objects#createpullrequestpayload", + "/enterprise/v4/object/createrefpayload": "/enterprise-server@latest/graphql/reference/objects#createrefpayload", + "/enterprise/v4/object/createrepositorypayload": "/enterprise-server@latest/graphql/reference/objects#createrepositorypayload", + "/enterprise/v4/object/createteamdiscussioncommentpayload": "/enterprise-server@latest/graphql/reference/objects#createteamdiscussioncommentpayload", + "/enterprise/v4/object/createteamdiscussionpayload": "/enterprise-server@latest/graphql/reference/objects#createteamdiscussionpayload", + "/enterprise/v4/object/crossreferencedevent": "/enterprise-server@latest/graphql/reference/objects#crossreferencedevent", + "/enterprise/v4/object/deletebranchprotectionrulepayload": "/enterprise-server@latest/graphql/reference/objects#deletebranchprotectionrulepayload", + "/enterprise/v4/object/deletedeploymentpayload": "/enterprise-server@latest/graphql/reference/objects#deletedeploymentpayload", + "/enterprise/v4/object/deleteipallowlistentrypayload": "/enterprise-server@latest/graphql/reference/objects#deleteipallowlistentrypayload", + "/enterprise/v4/object/deleteissuecommentpayload": "/enterprise-server@latest/graphql/reference/objects#deleteissuecommentpayload", + "/enterprise/v4/object/deleteissuepayload": "/enterprise-server@latest/graphql/reference/objects#deleteissuepayload", + "/enterprise/v4/object/deletelabelpayload": "/enterprise-server@latest/graphql/reference/objects#deletelabelpayload", + "/enterprise/v4/object/deletepackageversionpayload": "/enterprise-server@latest/graphql/reference/objects#deletepackageversionpayload", + "/enterprise/v4/object/deleteprojectcardpayload": "/enterprise-server@latest/graphql/reference/objects#deleteprojectcardpayload", + "/enterprise/v4/object/deleteprojectcolumnpayload": "/enterprise-server@latest/graphql/reference/objects#deleteprojectcolumnpayload", + "/enterprise/v4/object/deleteprojectpayload": "/enterprise-server@latest/graphql/reference/objects#deleteprojectpayload", + "/enterprise/v4/object/deletepullrequestreviewcommentpayload": "/enterprise-server@latest/graphql/reference/objects#deletepullrequestreviewcommentpayload", + "/enterprise/v4/object/deletepullrequestreviewpayload": "/enterprise-server@latest/graphql/reference/objects#deletepullrequestreviewpayload", + "/enterprise/v4/object/deleterefpayload": "/enterprise-server@latest/graphql/reference/objects#deleterefpayload", + "/enterprise/v4/object/deleteteamdiscussioncommentpayload": "/enterprise-server@latest/graphql/reference/objects#deleteteamdiscussioncommentpayload", + "/enterprise/v4/object/deleteteamdiscussionpayload": "/enterprise-server@latest/graphql/reference/objects#deleteteamdiscussionpayload", + "/enterprise/v4/object/demilestonedevent": "/enterprise-server@latest/graphql/reference/objects#demilestonedevent", + "/enterprise/v4/object/deployedevent": "/enterprise-server@latest/graphql/reference/objects#deployedevent", + "/enterprise/v4/object/deploykey": "/enterprise-server@latest/graphql/reference/objects#deploykey", + "/enterprise/v4/object/deploykeyconnection": "/enterprise-server@latest/graphql/reference/objects#deploykeyconnection", + "/enterprise/v4/object/deploykeyedge": "/enterprise-server@latest/graphql/reference/objects#deploykeyedge", + "/enterprise/v4/object/deployment": "/enterprise-server@latest/graphql/reference/objects#deployment", + "/enterprise/v4/object/deploymentconnection": "/enterprise-server@latest/graphql/reference/objects#deploymentconnection", + "/enterprise/v4/object/deploymentedge": "/enterprise-server@latest/graphql/reference/objects#deploymentedge", + "/enterprise/v4/object/deploymentenvironmentchangedevent": "/enterprise-server@latest/graphql/reference/objects#deploymentenvironmentchangedevent", + "/enterprise/v4/object/deploymentstatus": "/enterprise-server@latest/graphql/reference/objects#deploymentstatus", + "/enterprise/v4/object/deploymentstatusconnection": "/enterprise-server@latest/graphql/reference/objects#deploymentstatusconnection", + "/enterprise/v4/object/deploymentstatusedge": "/enterprise-server@latest/graphql/reference/objects#deploymentstatusedge", + "/enterprise/v4/object/disconnectedevent": "/enterprise-server@latest/graphql/reference/objects#disconnectedevent", + "/enterprise/v4/object/dismisspullrequestreviewpayload": "/enterprise-server@latest/graphql/reference/objects#dismisspullrequestreviewpayload", + "/enterprise/v4/object/enterprise": "/enterprise-server@latest/graphql/reference/objects#enterprise", + "/enterprise/v4/object/enterpriseadministratorconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorconnection", + "/enterprise/v4/object/enterpriseadministratoredge": "/enterprise-server@latest/graphql/reference/objects#enterpriseadministratoredge", + "/enterprise/v4/object/enterpriseadministratorinvitation": "/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitation", + "/enterprise/v4/object/enterpriseadministratorinvitationconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitationconnection", + "/enterprise/v4/object/enterpriseadministratorinvitationedge": "/enterprise-server@latest/graphql/reference/objects#enterpriseadministratorinvitationedge", + "/enterprise/v4/object/enterprisebillinginfo": "/enterprise-server@latest/graphql/reference/objects#enterprisebillinginfo", + "/enterprise/v4/object/enterpriseidentityprovider": "/enterprise-server@latest/graphql/reference/objects#enterpriseidentityprovider", + "/enterprise/v4/object/enterprisememberconnection": "/enterprise-server@latest/graphql/reference/objects#enterprisememberconnection", + "/enterprise/v4/object/enterprisememberedge": "/enterprise-server@latest/graphql/reference/objects#enterprisememberedge", + "/enterprise/v4/object/enterpriseorganizationmembershipconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseorganizationmembershipconnection", + "/enterprise/v4/object/enterpriseorganizationmembershipedge": "/enterprise-server@latest/graphql/reference/objects#enterpriseorganizationmembershipedge", + "/enterprise/v4/object/enterpriseoutsidecollaboratorconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", + "/enterprise/v4/object/enterpriseoutsidecollaboratoredge": "/enterprise-server@latest/graphql/reference/objects#enterpriseoutsidecollaboratoredge", + "/enterprise/v4/object/enterpriseownerinfo": "/enterprise-server@latest/graphql/reference/objects#enterpriseownerinfo", + "/enterprise/v4/object/enterprisependingcollaboratorconnection": "/enterprise-server@latest/graphql/reference/objects#enterprisependingcollaboratorconnection", + "/enterprise/v4/object/enterprisependingcollaboratoredge": "/enterprise-server@latest/graphql/reference/objects#enterprisependingcollaboratoredge", + "/enterprise/v4/object/enterprisependingmemberinvitationconnection": "/enterprise-server@latest/graphql/reference/objects#enterprisependingmemberinvitationconnection", + "/enterprise/v4/object/enterprisependingmemberinvitationedge": "/enterprise-server@latest/graphql/reference/objects#enterprisependingmemberinvitationedge", + "/enterprise/v4/object/enterpriserepositoryinfo": "/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfo", + "/enterprise/v4/object/enterpriserepositoryinfoconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfoconnection", + "/enterprise/v4/object/enterpriserepositoryinfoedge": "/enterprise-server@latest/graphql/reference/objects#enterpriserepositoryinfoedge", + "/enterprise/v4/object/enterpriseserverinstallation": "/enterprise-server@latest/graphql/reference/objects#enterpriseserverinstallation", + "/enterprise/v4/object/enterpriseserveruseraccount": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccount", + "/enterprise/v4/object/enterpriseserveruseraccountconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountconnection", + "/enterprise/v4/object/enterpriseserveruseraccountedge": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountedge", + "/enterprise/v4/object/enterpriseserveruseraccountemail": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemail", + "/enterprise/v4/object/enterpriseserveruseraccountemailconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemailconnection", + "/enterprise/v4/object/enterpriseserveruseraccountemailedge": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountemailedge", + "/enterprise/v4/object/enterpriseserveruseraccountsupload": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsupload", + "/enterprise/v4/object/enterpriseserveruseraccountsuploadconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", + "/enterprise/v4/object/enterpriseserveruseraccountsuploadedge": "/enterprise-server@latest/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", + "/enterprise/v4/object/enterpriseuseraccount": "/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccount", + "/enterprise/v4/object/enterpriseuseraccountconnection": "/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccountconnection", + "/enterprise/v4/object/enterpriseuseraccountedge": "/enterprise-server@latest/graphql/reference/objects#enterpriseuseraccountedge", + "/enterprise/v4/object/externalidentity": "/enterprise-server@latest/graphql/reference/objects#externalidentity", + "/enterprise/v4/object/externalidentityconnection": "/enterprise-server@latest/graphql/reference/objects#externalidentityconnection", + "/enterprise/v4/object/externalidentityedge": "/enterprise-server@latest/graphql/reference/objects#externalidentityedge", + "/enterprise/v4/object/externalidentitysamlattributes": "/enterprise-server@latest/graphql/reference/objects#externalidentitysamlattributes", + "/enterprise/v4/object/externalidentityscimattributes": "/enterprise-server@latest/graphql/reference/objects#externalidentityscimattributes", + "/enterprise/v4/object/followerconnection": "/enterprise-server@latest/graphql/reference/objects#followerconnection", + "/enterprise/v4/object/followingconnection": "/enterprise-server@latest/graphql/reference/objects#followingconnection", + "/enterprise/v4/object/followuserpayload": "/enterprise-server@latest/graphql/reference/objects#followuserpayload", + "/enterprise/v4/object/generichovercardcontext": "/enterprise-server@latest/graphql/reference/objects#generichovercardcontext", + "/enterprise/v4/object/gist": "/enterprise-server@latest/graphql/reference/objects#gist", + "/enterprise/v4/object/gistcomment": "/enterprise-server@latest/graphql/reference/objects#gistcomment", + "/enterprise/v4/object/gistcommentconnection": "/enterprise-server@latest/graphql/reference/objects#gistcommentconnection", + "/enterprise/v4/object/gistcommentedge": "/enterprise-server@latest/graphql/reference/objects#gistcommentedge", + "/enterprise/v4/object/gistconnection": "/enterprise-server@latest/graphql/reference/objects#gistconnection", + "/enterprise/v4/object/gistedge": "/enterprise-server@latest/graphql/reference/objects#gistedge", + "/enterprise/v4/object/gistfile": "/enterprise-server@latest/graphql/reference/objects#gistfile", + "/enterprise/v4/object/gitactor": "/enterprise-server@latest/graphql/reference/objects#gitactor", + "/enterprise/v4/object/githubmetadata": "/enterprise-server@latest/graphql/reference/objects#githubmetadata", + "/enterprise/v4/object/gpgsignature": "/enterprise-server@latest/graphql/reference/objects#gpgsignature", + "/enterprise/v4/object/headrefdeletedevent": "/enterprise-server@latest/graphql/reference/objects#headrefdeletedevent", + "/enterprise/v4/object/headrefforcepushedevent": "/enterprise-server@latest/graphql/reference/objects#headrefforcepushedevent", + "/enterprise/v4/object/headrefrestoredevent": "/enterprise-server@latest/graphql/reference/objects#headrefrestoredevent", + "/enterprise/v4/object/hovercard": "/enterprise-server@latest/graphql/reference/objects#hovercard", + "/enterprise/v4/object/importprojectpayload": "/enterprise-server@latest/graphql/reference/objects#importprojectpayload", + "/enterprise/v4/object/ipallowlistentry": "/enterprise-server@latest/graphql/reference/objects#ipallowlistentry", + "/enterprise/v4/object/ipallowlistentryconnection": "/enterprise-server@latest/graphql/reference/objects#ipallowlistentryconnection", + "/enterprise/v4/object/ipallowlistentryedge": "/enterprise-server@latest/graphql/reference/objects#ipallowlistentryedge", + "/enterprise/v4/object/issue": "/enterprise-server@latest/graphql/reference/objects#issue", + "/enterprise/v4/object/issuecomment": "/enterprise-server@latest/graphql/reference/objects#issuecomment", + "/enterprise/v4/object/issuecommentconnection": "/enterprise-server@latest/graphql/reference/objects#issuecommentconnection", + "/enterprise/v4/object/issuecommentedge": "/enterprise-server@latest/graphql/reference/objects#issuecommentedge", + "/enterprise/v4/object/issueconnection": "/enterprise-server@latest/graphql/reference/objects#issueconnection", + "/enterprise/v4/object/issuecontributionsbyrepository": "/enterprise-server@latest/graphql/reference/objects#issuecontributionsbyrepository", + "/enterprise/v4/object/issueedge": "/enterprise-server@latest/graphql/reference/objects#issueedge", + "/enterprise/v4/object/issuetimelineconnection": "/enterprise-server@latest/graphql/reference/objects#issuetimelineconnection", + "/enterprise/v4/object/issuetimelineitemedge": "/enterprise-server@latest/graphql/reference/objects#issuetimelineitemedge", + "/enterprise/v4/object/issuetimelineitemsconnection": "/enterprise-server@latest/graphql/reference/objects#issuetimelineitemsconnection", + "/enterprise/v4/object/issuetimelineitemsedge": "/enterprise-server@latest/graphql/reference/objects#issuetimelineitemsedge", + "/enterprise/v4/object/joinedgithubcontribution": "/enterprise-server@latest/graphql/reference/objects#joinedgithubcontribution", + "/enterprise/v4/object/label": "/enterprise-server@latest/graphql/reference/objects#label", + "/enterprise/v4/object/labelconnection": "/enterprise-server@latest/graphql/reference/objects#labelconnection", + "/enterprise/v4/object/labeledevent": "/enterprise-server@latest/graphql/reference/objects#labeledevent", + "/enterprise/v4/object/labeledge": "/enterprise-server@latest/graphql/reference/objects#labeledge", + "/enterprise/v4/object/language": "/enterprise-server@latest/graphql/reference/objects#language", + "/enterprise/v4/object/languageconnection": "/enterprise-server@latest/graphql/reference/objects#languageconnection", + "/enterprise/v4/object/languageedge": "/enterprise-server@latest/graphql/reference/objects#languageedge", + "/enterprise/v4/object/license": "/enterprise-server@latest/graphql/reference/objects#license", + "/enterprise/v4/object/licenserule": "/enterprise-server@latest/graphql/reference/objects#licenserule", + "/enterprise/v4/object/linkrepositorytoprojectpayload": "/enterprise-server@latest/graphql/reference/objects#linkrepositorytoprojectpayload", + "/enterprise/v4/object/lockedevent": "/enterprise-server@latest/graphql/reference/objects#lockedevent", + "/enterprise/v4/object/locklockablepayload": "/enterprise-server@latest/graphql/reference/objects#locklockablepayload", + "/enterprise/v4/object/mannequin": "/enterprise-server@latest/graphql/reference/objects#mannequin", + "/enterprise/v4/object/markedasduplicateevent": "/enterprise-server@latest/graphql/reference/objects#markedasduplicateevent", + "/enterprise/v4/object/markpullrequestreadyforreviewpayload": "/enterprise-server@latest/graphql/reference/objects#markpullrequestreadyforreviewpayload", + "/enterprise/v4/object/memberscandeletereposclearauditentry": "/enterprise-server@latest/graphql/reference/objects#memberscandeletereposclearauditentry", + "/enterprise/v4/object/memberscandeletereposdisableauditentry": "/enterprise-server@latest/graphql/reference/objects#memberscandeletereposdisableauditentry", + "/enterprise/v4/object/memberscandeletereposenableauditentry": "/enterprise-server@latest/graphql/reference/objects#memberscandeletereposenableauditentry", + "/enterprise/v4/object/mentionedevent": "/enterprise-server@latest/graphql/reference/objects#mentionedevent", + "/enterprise/v4/object/mergebranchpayload": "/enterprise-server@latest/graphql/reference/objects#mergebranchpayload", + "/enterprise/v4/object/mergedevent": "/enterprise-server@latest/graphql/reference/objects#mergedevent", + "/enterprise/v4/object/mergepullrequestpayload": "/enterprise-server@latest/graphql/reference/objects#mergepullrequestpayload", + "/enterprise/v4/object/milestone": "/enterprise-server@latest/graphql/reference/objects#milestone", + "/enterprise/v4/object/milestoneconnection": "/enterprise-server@latest/graphql/reference/objects#milestoneconnection", + "/enterprise/v4/object/milestonedevent": "/enterprise-server@latest/graphql/reference/objects#milestonedevent", + "/enterprise/v4/object/milestoneedge": "/enterprise-server@latest/graphql/reference/objects#milestoneedge", + "/enterprise/v4/object/minimizecommentpayload": "/enterprise-server@latest/graphql/reference/objects#minimizecommentpayload", + "/enterprise/v4/object/movedcolumnsinprojectevent": "/enterprise-server@latest/graphql/reference/objects#movedcolumnsinprojectevent", + "/enterprise/v4/object/moveprojectcardpayload": "/enterprise-server@latest/graphql/reference/objects#moveprojectcardpayload", + "/enterprise/v4/object/moveprojectcolumnpayload": "/enterprise-server@latest/graphql/reference/objects#moveprojectcolumnpayload", + "/enterprise/v4/object/oauthapplicationcreateauditentry": "/enterprise-server@latest/graphql/reference/objects#oauthapplicationcreateauditentry", + "/enterprise/v4/object/orgaddbillingmanagerauditentry": "/enterprise-server@latest/graphql/reference/objects#orgaddbillingmanagerauditentry", + "/enterprise/v4/object/orgaddmemberauditentry": "/enterprise-server@latest/graphql/reference/objects#orgaddmemberauditentry", + "/enterprise/v4/object/organization": "/enterprise-server@latest/graphql/reference/objects#organization", + "/enterprise/v4/object/organizationauditentryconnection": "/enterprise-server@latest/graphql/reference/objects#organizationauditentryconnection", + "/enterprise/v4/object/organizationauditentryedge": "/enterprise-server@latest/graphql/reference/objects#organizationauditentryedge", + "/enterprise/v4/object/organizationconnection": "/enterprise-server@latest/graphql/reference/objects#organizationconnection", + "/enterprise/v4/object/organizationedge": "/enterprise-server@latest/graphql/reference/objects#organizationedge", + "/enterprise/v4/object/organizationidentityprovider": "/enterprise-server@latest/graphql/reference/objects#organizationidentityprovider", + "/enterprise/v4/object/organizationinvitation": "/enterprise-server@latest/graphql/reference/objects#organizationinvitation", + "/enterprise/v4/object/organizationinvitationconnection": "/enterprise-server@latest/graphql/reference/objects#organizationinvitationconnection", + "/enterprise/v4/object/organizationinvitationedge": "/enterprise-server@latest/graphql/reference/objects#organizationinvitationedge", + "/enterprise/v4/object/organizationmemberconnection": "/enterprise-server@latest/graphql/reference/objects#organizationmemberconnection", + "/enterprise/v4/object/organizationmemberedge": "/enterprise-server@latest/graphql/reference/objects#organizationmemberedge", + "/enterprise/v4/object/organizationshovercardcontext": "/enterprise-server@latest/graphql/reference/objects#organizationshovercardcontext", + "/enterprise/v4/object/organizationteamshovercardcontext": "/enterprise-server@latest/graphql/reference/objects#organizationteamshovercardcontext", + "/enterprise/v4/object/orgblockuserauditentry": "/enterprise-server@latest/graphql/reference/objects#orgblockuserauditentry", + "/enterprise/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/enterprise-server@latest/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", + "/enterprise/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/enterprise-server@latest/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", + "/enterprise/v4/object/orgcreateauditentry": "/enterprise-server@latest/graphql/reference/objects#orgcreateauditentry", + "/enterprise/v4/object/orgdisableoauthapprestrictionsauditentry": "/enterprise-server@latest/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", + "/enterprise/v4/object/orgdisablesamlauditentry": "/enterprise-server@latest/graphql/reference/objects#orgdisablesamlauditentry", + "/enterprise/v4/object/orgdisabletwofactorrequirementauditentry": "/enterprise-server@latest/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", + "/enterprise/v4/object/orgenableoauthapprestrictionsauditentry": "/enterprise-server@latest/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", + "/enterprise/v4/object/orgenablesamlauditentry": "/enterprise-server@latest/graphql/reference/objects#orgenablesamlauditentry", + "/enterprise/v4/object/orgenabletwofactorrequirementauditentry": "/enterprise-server@latest/graphql/reference/objects#orgenabletwofactorrequirementauditentry", + "/enterprise/v4/object/orginvitememberauditentry": "/enterprise-server@latest/graphql/reference/objects#orginvitememberauditentry", + "/enterprise/v4/object/orginvitetobusinessauditentry": "/enterprise-server@latest/graphql/reference/objects#orginvitetobusinessauditentry", + "/enterprise/v4/object/orgoauthappaccessapprovedauditentry": "/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessapprovedauditentry", + "/enterprise/v4/object/orgoauthappaccessdeniedauditentry": "/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessdeniedauditentry", + "/enterprise/v4/object/orgoauthappaccessrequestedauditentry": "/enterprise-server@latest/graphql/reference/objects#orgoauthappaccessrequestedauditentry", + "/enterprise/v4/object/orgremovebillingmanagerauditentry": "/enterprise-server@latest/graphql/reference/objects#orgremovebillingmanagerauditentry", + "/enterprise/v4/object/orgremovememberauditentry": "/enterprise-server@latest/graphql/reference/objects#orgremovememberauditentry", + "/enterprise/v4/object/orgremoveoutsidecollaboratorauditentry": "/enterprise-server@latest/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", + "/enterprise/v4/object/orgrestorememberauditentry": "/enterprise-server@latest/graphql/reference/objects#orgrestorememberauditentry", + "/enterprise/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", + "/enterprise/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", + "/enterprise/v4/object/orgrestoremembermembershipteamauditentrydata": "/enterprise-server@latest/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", + "/enterprise/v4/object/orgunblockuserauditentry": "/enterprise-server@latest/graphql/reference/objects#orgunblockuserauditentry", + "/enterprise/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/enterprise-server@latest/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", + "/enterprise/v4/object/orgupdatememberauditentry": "/enterprise-server@latest/graphql/reference/objects#orgupdatememberauditentry", + "/enterprise/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/enterprise-server@latest/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", + "/enterprise/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/enterprise-server@latest/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", + "/enterprise/v4/object/package": "/enterprise-server@latest/graphql/reference/objects#package", + "/enterprise/v4/object/packageconnection": "/enterprise-server@latest/graphql/reference/objects#packageconnection", + "/enterprise/v4/object/packageedge": "/enterprise-server@latest/graphql/reference/objects#packageedge", + "/enterprise/v4/object/packagefile": "/enterprise-server@latest/graphql/reference/objects#packagefile", + "/enterprise/v4/object/packagefileconnection": "/enterprise-server@latest/graphql/reference/objects#packagefileconnection", + "/enterprise/v4/object/packagefileedge": "/enterprise-server@latest/graphql/reference/objects#packagefileedge", + "/enterprise/v4/object/packagestatistics": "/enterprise-server@latest/graphql/reference/objects#packagestatistics", + "/enterprise/v4/object/packagetag": "/enterprise-server@latest/graphql/reference/objects#packagetag", + "/enterprise/v4/object/packageversion": "/enterprise-server@latest/graphql/reference/objects#packageversion", + "/enterprise/v4/object/packageversionconnection": "/enterprise-server@latest/graphql/reference/objects#packageversionconnection", + "/enterprise/v4/object/packageversionedge": "/enterprise-server@latest/graphql/reference/objects#packageversionedge", + "/enterprise/v4/object/packageversionstatistics": "/enterprise-server@latest/graphql/reference/objects#packageversionstatistics", + "/enterprise/v4/object/pageinfo": "/enterprise-server@latest/graphql/reference/objects#pageinfo", + "/enterprise/v4/object/permissionsource": "/enterprise-server@latest/graphql/reference/objects#permissionsource", + "/enterprise/v4/object/pinissuepayload": "/enterprise-server@latest/graphql/reference/objects#pinissuepayload", + "/enterprise/v4/object/pinnableitemconnection": "/enterprise-server@latest/graphql/reference/objects#pinnableitemconnection", + "/enterprise/v4/object/pinnableitemedge": "/enterprise-server@latest/graphql/reference/objects#pinnableitemedge", + "/enterprise/v4/object/pinnedevent": "/enterprise-server@latest/graphql/reference/objects#pinnedevent", + "/enterprise/v4/object/pinnedissue": "/enterprise-server@latest/graphql/reference/objects#pinnedissue", + "/enterprise/v4/object/pinnedissueconnection": "/enterprise-server@latest/graphql/reference/objects#pinnedissueconnection", + "/enterprise/v4/object/pinnedissueedge": "/enterprise-server@latest/graphql/reference/objects#pinnedissueedge", + "/enterprise/v4/object/privaterepositoryforkingdisableauditentry": "/enterprise-server@latest/graphql/reference/objects#privaterepositoryforkingdisableauditentry", + "/enterprise/v4/object/privaterepositoryforkingenableauditentry": "/enterprise-server@latest/graphql/reference/objects#privaterepositoryforkingenableauditentry", + "/enterprise/v4/object/profileitemshowcase": "/enterprise-server@latest/graphql/reference/objects#profileitemshowcase", + "/enterprise/v4/object/project": "/enterprise-server@latest/graphql/reference/objects#project", + "/enterprise/v4/object/projectcard": "/enterprise-server@latest/graphql/reference/objects#projectcard", + "/enterprise/v4/object/projectcardconnection": "/enterprise-server@latest/graphql/reference/objects#projectcardconnection", + "/enterprise/v4/object/projectcardedge": "/enterprise-server@latest/graphql/reference/objects#projectcardedge", + "/enterprise/v4/object/projectcolumn": "/enterprise-server@latest/graphql/reference/objects#projectcolumn", + "/enterprise/v4/object/projectcolumnconnection": "/enterprise-server@latest/graphql/reference/objects#projectcolumnconnection", + "/enterprise/v4/object/projectcolumnedge": "/enterprise-server@latest/graphql/reference/objects#projectcolumnedge", + "/enterprise/v4/object/projectconnection": "/enterprise-server@latest/graphql/reference/objects#projectconnection", + "/enterprise/v4/object/projectedge": "/enterprise-server@latest/graphql/reference/objects#projectedge", + "/enterprise/v4/object/publickey": "/enterprise-server@latest/graphql/reference/objects#publickey", + "/enterprise/v4/object/publickeyconnection": "/enterprise-server@latest/graphql/reference/objects#publickeyconnection", + "/enterprise/v4/object/publickeyedge": "/enterprise-server@latest/graphql/reference/objects#publickeyedge", + "/enterprise/v4/object/pullrequest": "/enterprise-server@latest/graphql/reference/objects#pullrequest", + "/enterprise/v4/object/pullrequestchangedfile": "/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfile", + "/enterprise/v4/object/pullrequestchangedfileconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfileconnection", + "/enterprise/v4/object/pullrequestchangedfileedge": "/enterprise-server@latest/graphql/reference/objects#pullrequestchangedfileedge", + "/enterprise/v4/object/pullrequestcommit": "/enterprise-server@latest/graphql/reference/objects#pullrequestcommit", + "/enterprise/v4/object/pullrequestcommitcommentthread": "/enterprise-server@latest/graphql/reference/objects#pullrequestcommitcommentthread", + "/enterprise/v4/object/pullrequestcommitconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequestcommitconnection", + "/enterprise/v4/object/pullrequestcommitedge": "/enterprise-server@latest/graphql/reference/objects#pullrequestcommitedge", + "/enterprise/v4/object/pullrequestconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequestconnection", + "/enterprise/v4/object/pullrequestcontributionsbyrepository": "/enterprise-server@latest/graphql/reference/objects#pullrequestcontributionsbyrepository", + "/enterprise/v4/object/pullrequestedge": "/enterprise-server@latest/graphql/reference/objects#pullrequestedge", + "/enterprise/v4/object/pullrequestreview": "/enterprise-server@latest/graphql/reference/objects#pullrequestreview", + "/enterprise/v4/object/pullrequestreviewcomment": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcomment", + "/enterprise/v4/object/pullrequestreviewcommentconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcommentconnection", + "/enterprise/v4/object/pullrequestreviewcommentedge": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcommentedge", + "/enterprise/v4/object/pullrequestreviewconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewconnection", + "/enterprise/v4/object/pullrequestreviewcontributionsbyrepository": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", + "/enterprise/v4/object/pullrequestreviewedge": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewedge", + "/enterprise/v4/object/pullrequestreviewthread": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthread", + "/enterprise/v4/object/pullrequestreviewthreadconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthreadconnection", + "/enterprise/v4/object/pullrequestreviewthreadedge": "/enterprise-server@latest/graphql/reference/objects#pullrequestreviewthreadedge", + "/enterprise/v4/object/pullrequestrevisionmarker": "/enterprise-server@latest/graphql/reference/objects#pullrequestrevisionmarker", + "/enterprise/v4/object/pullrequesttimelineconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineconnection", + "/enterprise/v4/object/pullrequesttimelineitemedge": "/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemedge", + "/enterprise/v4/object/pullrequesttimelineitemsconnection": "/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemsconnection", + "/enterprise/v4/object/pullrequesttimelineitemsedge": "/enterprise-server@latest/graphql/reference/objects#pullrequesttimelineitemsedge", + "/enterprise/v4/object/push": "/enterprise-server@latest/graphql/reference/objects#push", + "/enterprise/v4/object/pushallowance": "/enterprise-server@latest/graphql/reference/objects#pushallowance", + "/enterprise/v4/object/pushallowanceconnection": "/enterprise-server@latest/graphql/reference/objects#pushallowanceconnection", + "/enterprise/v4/object/pushallowanceedge": "/enterprise-server@latest/graphql/reference/objects#pushallowanceedge", + "/enterprise/v4/object/ratelimit": "/enterprise-server@latest/graphql/reference/objects#ratelimit", + "/enterprise/v4/object/reactinguserconnection": "/enterprise-server@latest/graphql/reference/objects#reactinguserconnection", + "/enterprise/v4/object/reactinguseredge": "/enterprise-server@latest/graphql/reference/objects#reactinguseredge", + "/enterprise/v4/object/reaction": "/enterprise-server@latest/graphql/reference/objects#reaction", + "/enterprise/v4/object/reactionconnection": "/enterprise-server@latest/graphql/reference/objects#reactionconnection", + "/enterprise/v4/object/reactionedge": "/enterprise-server@latest/graphql/reference/objects#reactionedge", + "/enterprise/v4/object/reactiongroup": "/enterprise-server@latest/graphql/reference/objects#reactiongroup", + "/enterprise/v4/object/readyforreviewevent": "/enterprise-server@latest/graphql/reference/objects#readyforreviewevent", + "/enterprise/v4/object/ref": "/enterprise-server@latest/graphql/reference/objects#ref", + "/enterprise/v4/object/refconnection": "/enterprise-server@latest/graphql/reference/objects#refconnection", + "/enterprise/v4/object/refedge": "/enterprise-server@latest/graphql/reference/objects#refedge", + "/enterprise/v4/object/referencedevent": "/enterprise-server@latest/graphql/reference/objects#referencedevent", + "/enterprise/v4/object/registrypackage": "/enterprise-server@latest/graphql/reference/objects#registrypackage", + "/enterprise/v4/object/registrypackageconnection": "/enterprise-server@latest/graphql/reference/objects#registrypackageconnection", + "/enterprise/v4/object/registrypackagedependency": "/enterprise-server@latest/graphql/reference/objects#registrypackagedependency", + "/enterprise/v4/object/registrypackagedependencyconnection": "/enterprise-server@latest/graphql/reference/objects#registrypackagedependencyconnection", + "/enterprise/v4/object/registrypackagedependencyedge": "/enterprise-server@latest/graphql/reference/objects#registrypackagedependencyedge", + "/enterprise/v4/object/registrypackageedge": "/enterprise-server@latest/graphql/reference/objects#registrypackageedge", + "/enterprise/v4/object/registrypackagefile": "/enterprise-server@latest/graphql/reference/objects#registrypackagefile", + "/enterprise/v4/object/registrypackagefileconnection": "/enterprise-server@latest/graphql/reference/objects#registrypackagefileconnection", + "/enterprise/v4/object/registrypackagefileedge": "/enterprise-server@latest/graphql/reference/objects#registrypackagefileedge", + "/enterprise/v4/object/registrypackagestatistics": "/enterprise-server@latest/graphql/reference/objects#registrypackagestatistics", + "/enterprise/v4/object/registrypackagetag": "/enterprise-server@latest/graphql/reference/objects#registrypackagetag", + "/enterprise/v4/object/registrypackagetagconnection": "/enterprise-server@latest/graphql/reference/objects#registrypackagetagconnection", + "/enterprise/v4/object/registrypackagetagedge": "/enterprise-server@latest/graphql/reference/objects#registrypackagetagedge", + "/enterprise/v4/object/registrypackageversion": "/enterprise-server@latest/graphql/reference/objects#registrypackageversion", + "/enterprise/v4/object/registrypackageversionconnection": "/enterprise-server@latest/graphql/reference/objects#registrypackageversionconnection", + "/enterprise/v4/object/registrypackageversionedge": "/enterprise-server@latest/graphql/reference/objects#registrypackageversionedge", + "/enterprise/v4/object/registrypackageversionstatistics": "/enterprise-server@latest/graphql/reference/objects#registrypackageversionstatistics", + "/enterprise/v4/object/release": "/enterprise-server@latest/graphql/reference/objects#release", + "/enterprise/v4/object/releaseasset": "/enterprise-server@latest/graphql/reference/objects#releaseasset", + "/enterprise/v4/object/releaseassetconnection": "/enterprise-server@latest/graphql/reference/objects#releaseassetconnection", + "/enterprise/v4/object/releaseassetedge": "/enterprise-server@latest/graphql/reference/objects#releaseassetedge", + "/enterprise/v4/object/releaseconnection": "/enterprise-server@latest/graphql/reference/objects#releaseconnection", + "/enterprise/v4/object/releaseedge": "/enterprise-server@latest/graphql/reference/objects#releaseedge", + "/enterprise/v4/object/removeassigneesfromassignablepayload": "/enterprise-server@latest/graphql/reference/objects#removeassigneesfromassignablepayload", + "/enterprise/v4/object/removedfromprojectevent": "/enterprise-server@latest/graphql/reference/objects#removedfromprojectevent", + "/enterprise/v4/object/removeenterpriseadminpayload": "/enterprise-server@latest/graphql/reference/objects#removeenterpriseadminpayload", + "/enterprise/v4/object/removelabelsfromlabelablepayload": "/enterprise-server@latest/graphql/reference/objects#removelabelsfromlabelablepayload", + "/enterprise/v4/object/removeoutsidecollaboratorpayload": "/enterprise-server@latest/graphql/reference/objects#removeoutsidecollaboratorpayload", + "/enterprise/v4/object/removereactionpayload": "/enterprise-server@latest/graphql/reference/objects#removereactionpayload", + "/enterprise/v4/object/removestarpayload": "/enterprise-server@latest/graphql/reference/objects#removestarpayload", + "/enterprise/v4/object/renamedtitleevent": "/enterprise-server@latest/graphql/reference/objects#renamedtitleevent", + "/enterprise/v4/object/reopenedevent": "/enterprise-server@latest/graphql/reference/objects#reopenedevent", + "/enterprise/v4/object/reopenissuepayload": "/enterprise-server@latest/graphql/reference/objects#reopenissuepayload", + "/enterprise/v4/object/reopenpullrequestpayload": "/enterprise-server@latest/graphql/reference/objects#reopenpullrequestpayload", + "/enterprise/v4/object/repoaccessauditentry": "/enterprise-server@latest/graphql/reference/objects#repoaccessauditentry", + "/enterprise/v4/object/repoaddmemberauditentry": "/enterprise-server@latest/graphql/reference/objects#repoaddmemberauditentry", + "/enterprise/v4/object/repoaddtopicauditentry": "/enterprise-server@latest/graphql/reference/objects#repoaddtopicauditentry", + "/enterprise/v4/object/repoarchivedauditentry": "/enterprise-server@latest/graphql/reference/objects#repoarchivedauditentry", + "/enterprise/v4/object/repochangemergesettingauditentry": "/enterprise-server@latest/graphql/reference/objects#repochangemergesettingauditentry", + "/enterprise/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", + "/enterprise/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", + "/enterprise/v4/object/repoconfigdisablecontributorsonlyauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", + "/enterprise/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", + "/enterprise/v4/object/repoconfigenableanonymousgitaccessauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", + "/enterprise/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", + "/enterprise/v4/object/repoconfigenablecontributorsonlyauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", + "/enterprise/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", + "/enterprise/v4/object/repoconfiglockanonymousgitaccessauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", + "/enterprise/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/enterprise-server@latest/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", + "/enterprise/v4/object/repocreateauditentry": "/enterprise-server@latest/graphql/reference/objects#repocreateauditentry", + "/enterprise/v4/object/repodestroyauditentry": "/enterprise-server@latest/graphql/reference/objects#repodestroyauditentry", + "/enterprise/v4/object/reporemovememberauditentry": "/enterprise-server@latest/graphql/reference/objects#reporemovememberauditentry", + "/enterprise/v4/object/reporemovetopicauditentry": "/enterprise-server@latest/graphql/reference/objects#reporemovetopicauditentry", + "/enterprise/v4/object/repository": "/enterprise-server@latest/graphql/reference/objects#repository", + "/enterprise/v4/object/repositorycollaboratorconnection": "/enterprise-server@latest/graphql/reference/objects#repositorycollaboratorconnection", + "/enterprise/v4/object/repositorycollaboratoredge": "/enterprise-server@latest/graphql/reference/objects#repositorycollaboratoredge", + "/enterprise/v4/object/repositoryconnection": "/enterprise-server@latest/graphql/reference/objects#repositoryconnection", + "/enterprise/v4/object/repositoryedge": "/enterprise-server@latest/graphql/reference/objects#repositoryedge", + "/enterprise/v4/object/repositoryinvitation": "/enterprise-server@latest/graphql/reference/objects#repositoryinvitation", + "/enterprise/v4/object/repositorytopic": "/enterprise-server@latest/graphql/reference/objects#repositorytopic", + "/enterprise/v4/object/repositorytopicconnection": "/enterprise-server@latest/graphql/reference/objects#repositorytopicconnection", + "/enterprise/v4/object/repositorytopicedge": "/enterprise-server@latest/graphql/reference/objects#repositorytopicedge", + "/enterprise/v4/object/repositoryvisibilitychangedisableauditentry": "/enterprise-server@latest/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", + "/enterprise/v4/object/repositoryvisibilitychangeenableauditentry": "/enterprise-server@latest/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", + "/enterprise/v4/object/repositoryvulnerabilityalert": "/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalert", + "/enterprise/v4/object/repositoryvulnerabilityalertconnection": "/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalertconnection", + "/enterprise/v4/object/repositoryvulnerabilityalertedge": "/enterprise-server@latest/graphql/reference/objects#repositoryvulnerabilityalertedge", + "/enterprise/v4/object/requestreviewspayload": "/enterprise-server@latest/graphql/reference/objects#requestreviewspayload", + "/enterprise/v4/object/rerequestchecksuitepayload": "/enterprise-server@latest/graphql/reference/objects#rerequestchecksuitepayload", + "/enterprise/v4/object/resolvereviewthreadpayload": "/enterprise-server@latest/graphql/reference/objects#resolvereviewthreadpayload", + "/enterprise/v4/object/restrictedcontribution": "/enterprise-server@latest/graphql/reference/objects#restrictedcontribution", + "/enterprise/v4/object/reviewdismissalallowance": "/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowance", + "/enterprise/v4/object/reviewdismissalallowanceconnection": "/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowanceconnection", + "/enterprise/v4/object/reviewdismissalallowanceedge": "/enterprise-server@latest/graphql/reference/objects#reviewdismissalallowanceedge", + "/enterprise/v4/object/reviewdismissedevent": "/enterprise-server@latest/graphql/reference/objects#reviewdismissedevent", + "/enterprise/v4/object/reviewrequest": "/enterprise-server@latest/graphql/reference/objects#reviewrequest", + "/enterprise/v4/object/reviewrequestconnection": "/enterprise-server@latest/graphql/reference/objects#reviewrequestconnection", + "/enterprise/v4/object/reviewrequestedevent": "/enterprise-server@latest/graphql/reference/objects#reviewrequestedevent", + "/enterprise/v4/object/reviewrequestedge": "/enterprise-server@latest/graphql/reference/objects#reviewrequestedge", + "/enterprise/v4/object/reviewrequestremovedevent": "/enterprise-server@latest/graphql/reference/objects#reviewrequestremovedevent", + "/enterprise/v4/object/reviewstatushovercardcontext": "/enterprise-server@latest/graphql/reference/objects#reviewstatushovercardcontext", + "/enterprise/v4/object/savedreply": "/enterprise-server@latest/graphql/reference/objects#savedreply", + "/enterprise/v4/object/savedreplyconnection": "/enterprise-server@latest/graphql/reference/objects#savedreplyconnection", + "/enterprise/v4/object/savedreplyedge": "/enterprise-server@latest/graphql/reference/objects#savedreplyedge", + "/enterprise/v4/object/searchresultitemconnection": "/enterprise-server@latest/graphql/reference/objects#searchresultitemconnection", + "/enterprise/v4/object/searchresultitemedge": "/enterprise-server@latest/graphql/reference/objects#searchresultitemedge", + "/enterprise/v4/object/securityadvisory": "/enterprise-server@latest/graphql/reference/objects#securityadvisory", + "/enterprise/v4/object/securityadvisoryconnection": "/enterprise-server@latest/graphql/reference/objects#securityadvisoryconnection", + "/enterprise/v4/object/securityadvisoryedge": "/enterprise-server@latest/graphql/reference/objects#securityadvisoryedge", + "/enterprise/v4/object/securityadvisoryidentifier": "/enterprise-server@latest/graphql/reference/objects#securityadvisoryidentifier", + "/enterprise/v4/object/securityadvisorypackage": "/enterprise-server@latest/graphql/reference/objects#securityadvisorypackage", + "/enterprise/v4/object/securityadvisorypackageversion": "/enterprise-server@latest/graphql/reference/objects#securityadvisorypackageversion", + "/enterprise/v4/object/securityadvisoryreference": "/enterprise-server@latest/graphql/reference/objects#securityadvisoryreference", + "/enterprise/v4/object/securityvulnerability": "/enterprise-server@latest/graphql/reference/objects#securityvulnerability", + "/enterprise/v4/object/securityvulnerabilityconnection": "/enterprise-server@latest/graphql/reference/objects#securityvulnerabilityconnection", + "/enterprise/v4/object/securityvulnerabilityedge": "/enterprise-server@latest/graphql/reference/objects#securityvulnerabilityedge", + "/enterprise/v4/object/smimesignature": "/enterprise-server@latest/graphql/reference/objects#smimesignature", + "/enterprise/v4/object/sponsorship": "/enterprise-server@latest/graphql/reference/objects#sponsorship", + "/enterprise/v4/object/sponsorshipconnection": "/enterprise-server@latest/graphql/reference/objects#sponsorshipconnection", + "/enterprise/v4/object/sponsorshipedge": "/enterprise-server@latest/graphql/reference/objects#sponsorshipedge", + "/enterprise/v4/object/stargazerconnection": "/enterprise-server@latest/graphql/reference/objects#stargazerconnection", + "/enterprise/v4/object/stargazeredge": "/enterprise-server@latest/graphql/reference/objects#stargazeredge", + "/enterprise/v4/object/starredrepositoryconnection": "/enterprise-server@latest/graphql/reference/objects#starredrepositoryconnection", + "/enterprise/v4/object/starredrepositoryedge": "/enterprise-server@latest/graphql/reference/objects#starredrepositoryedge", + "/enterprise/v4/object/status": "/enterprise-server@latest/graphql/reference/objects#status", + "/enterprise/v4/object/statuscheckrollup": "/enterprise-server@latest/graphql/reference/objects#statuscheckrollup", + "/enterprise/v4/object/statuscheckrollupcontextconnection": "/enterprise-server@latest/graphql/reference/objects#statuscheckrollupcontextconnection", + "/enterprise/v4/object/statuscheckrollupcontextedge": "/enterprise-server@latest/graphql/reference/objects#statuscheckrollupcontextedge", + "/enterprise/v4/object/statuscontext": "/enterprise-server@latest/graphql/reference/objects#statuscontext", + "/enterprise/v4/object/submitpullrequestreviewpayload": "/enterprise-server@latest/graphql/reference/objects#submitpullrequestreviewpayload", + "/enterprise/v4/object/submodule": "/enterprise-server@latest/graphql/reference/objects#submodule", + "/enterprise/v4/object/submoduleconnection": "/enterprise-server@latest/graphql/reference/objects#submoduleconnection", + "/enterprise/v4/object/submoduleedge": "/enterprise-server@latest/graphql/reference/objects#submoduleedge", + "/enterprise/v4/object/subscribedevent": "/enterprise-server@latest/graphql/reference/objects#subscribedevent", + "/enterprise/v4/object/suggestedreviewer": "/enterprise-server@latest/graphql/reference/objects#suggestedreviewer", + "/enterprise/v4/object/tag": "/enterprise-server@latest/graphql/reference/objects#tag", + "/enterprise/v4/object/team": "/enterprise-server@latest/graphql/reference/objects#team", + "/enterprise/v4/object/teamaddmemberauditentry": "/enterprise-server@latest/graphql/reference/objects#teamaddmemberauditentry", + "/enterprise/v4/object/teamaddrepositoryauditentry": "/enterprise-server@latest/graphql/reference/objects#teamaddrepositoryauditentry", + "/enterprise/v4/object/teamchangeparentteamauditentry": "/enterprise-server@latest/graphql/reference/objects#teamchangeparentteamauditentry", + "/enterprise/v4/object/teamconnection": "/enterprise-server@latest/graphql/reference/objects#teamconnection", + "/enterprise/v4/object/teamdiscussion": "/enterprise-server@latest/graphql/reference/objects#teamdiscussion", + "/enterprise/v4/object/teamdiscussioncomment": "/enterprise-server@latest/graphql/reference/objects#teamdiscussioncomment", + "/enterprise/v4/object/teamdiscussioncommentconnection": "/enterprise-server@latest/graphql/reference/objects#teamdiscussioncommentconnection", + "/enterprise/v4/object/teamdiscussioncommentedge": "/enterprise-server@latest/graphql/reference/objects#teamdiscussioncommentedge", + "/enterprise/v4/object/teamdiscussionconnection": "/enterprise-server@latest/graphql/reference/objects#teamdiscussionconnection", + "/enterprise/v4/object/teamdiscussionedge": "/enterprise-server@latest/graphql/reference/objects#teamdiscussionedge", + "/enterprise/v4/object/teamedge": "/enterprise-server@latest/graphql/reference/objects#teamedge", + "/enterprise/v4/object/teammemberconnection": "/enterprise-server@latest/graphql/reference/objects#teammemberconnection", + "/enterprise/v4/object/teammemberedge": "/enterprise-server@latest/graphql/reference/objects#teammemberedge", + "/enterprise/v4/object/teamremovememberauditentry": "/enterprise-server@latest/graphql/reference/objects#teamremovememberauditentry", + "/enterprise/v4/object/teamremoverepositoryauditentry": "/enterprise-server@latest/graphql/reference/objects#teamremoverepositoryauditentry", + "/enterprise/v4/object/teamrepositoryconnection": "/enterprise-server@latest/graphql/reference/objects#teamrepositoryconnection", + "/enterprise/v4/object/teamrepositoryedge": "/enterprise-server@latest/graphql/reference/objects#teamrepositoryedge", + "/enterprise/v4/object/textmatch": "/enterprise-server@latest/graphql/reference/objects#textmatch", + "/enterprise/v4/object/textmatchhighlight": "/enterprise-server@latest/graphql/reference/objects#textmatchhighlight", + "/enterprise/v4/object/topic": "/enterprise-server@latest/graphql/reference/objects#topic", + "/enterprise/v4/object/topicconnection": "/enterprise-server@latest/graphql/reference/objects#topicconnection", + "/enterprise/v4/object/topicedge": "/enterprise-server@latest/graphql/reference/objects#topicedge", + "/enterprise/v4/object/transferissuepayload": "/enterprise-server@latest/graphql/reference/objects#transferissuepayload", + "/enterprise/v4/object/transferredevent": "/enterprise-server@latest/graphql/reference/objects#transferredevent", + "/enterprise/v4/object/tree": "/enterprise-server@latest/graphql/reference/objects#tree", + "/enterprise/v4/object/treeentry": "/enterprise-server@latest/graphql/reference/objects#treeentry", + "/enterprise/v4/object/unarchiverepositorypayload": "/enterprise-server@latest/graphql/reference/objects#unarchiverepositorypayload", + "/enterprise/v4/object/unassignedevent": "/enterprise-server@latest/graphql/reference/objects#unassignedevent", + "/enterprise/v4/object/unfollowuserpayload": "/enterprise-server@latest/graphql/reference/objects#unfollowuserpayload", + "/enterprise/v4/object/unknownsignature": "/enterprise-server@latest/graphql/reference/objects#unknownsignature", + "/enterprise/v4/object/unlabeledevent": "/enterprise-server@latest/graphql/reference/objects#unlabeledevent", + "/enterprise/v4/object/unlinkrepositoryfromprojectpayload": "/enterprise-server@latest/graphql/reference/objects#unlinkrepositoryfromprojectpayload", + "/enterprise/v4/object/unlockedevent": "/enterprise-server@latest/graphql/reference/objects#unlockedevent", + "/enterprise/v4/object/unlocklockablepayload": "/enterprise-server@latest/graphql/reference/objects#unlocklockablepayload", + "/enterprise/v4/object/unmarkedasduplicateevent": "/enterprise-server@latest/graphql/reference/objects#unmarkedasduplicateevent", + "/enterprise/v4/object/unmarkissueasduplicatepayload": "/enterprise-server@latest/graphql/reference/objects#unmarkissueasduplicatepayload", + "/enterprise/v4/object/unminimizecommentpayload": "/enterprise-server@latest/graphql/reference/objects#unminimizecommentpayload", + "/enterprise/v4/object/unpinissuepayload": "/enterprise-server@latest/graphql/reference/objects#unpinissuepayload", + "/enterprise/v4/object/unpinnedevent": "/enterprise-server@latest/graphql/reference/objects#unpinnedevent", + "/enterprise/v4/object/unresolvereviewthreadpayload": "/enterprise-server@latest/graphql/reference/objects#unresolvereviewthreadpayload", + "/enterprise/v4/object/unsubscribedevent": "/enterprise-server@latest/graphql/reference/objects#unsubscribedevent", + "/enterprise/v4/object/updatebranchprotectionrulepayload": "/enterprise-server@latest/graphql/reference/objects#updatebranchprotectionrulepayload", + "/enterprise/v4/object/updatecheckrunpayload": "/enterprise-server@latest/graphql/reference/objects#updatecheckrunpayload", + "/enterprise/v4/object/updatechecksuitepreferencespayload": "/enterprise-server@latest/graphql/reference/objects#updatechecksuitepreferencespayload", + "/enterprise/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", + "/enterprise/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", + "/enterprise/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", + "/enterprise/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", + "/enterprise/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", + "/enterprise/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", + "/enterprise/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", + "/enterprise/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", + "/enterprise/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", + "/enterprise/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", + "/enterprise/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", + "/enterprise/v4/object/updateenterpriseorganizationprojectssettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", + "/enterprise/v4/object/updateenterpriseprofilepayload": "/enterprise-server@latest/graphql/reference/objects#updateenterpriseprofilepayload", + "/enterprise/v4/object/updateenterpriserepositoryprojectssettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", + "/enterprise/v4/object/updateenterpriseteamdiscussionssettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", + "/enterprise/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", + "/enterprise/v4/object/updateipallowlistenabledsettingpayload": "/enterprise-server@latest/graphql/reference/objects#updateipallowlistenabledsettingpayload", + "/enterprise/v4/object/updateipallowlistentrypayload": "/enterprise-server@latest/graphql/reference/objects#updateipallowlistentrypayload", + "/enterprise/v4/object/updateissuecommentpayload": "/enterprise-server@latest/graphql/reference/objects#updateissuecommentpayload", + "/enterprise/v4/object/updateissuepayload": "/enterprise-server@latest/graphql/reference/objects#updateissuepayload", + "/enterprise/v4/object/updatelabelpayload": "/enterprise-server@latest/graphql/reference/objects#updatelabelpayload", + "/enterprise/v4/object/updateprojectcardpayload": "/enterprise-server@latest/graphql/reference/objects#updateprojectcardpayload", + "/enterprise/v4/object/updateprojectcolumnpayload": "/enterprise-server@latest/graphql/reference/objects#updateprojectcolumnpayload", + "/enterprise/v4/object/updateprojectpayload": "/enterprise-server@latest/graphql/reference/objects#updateprojectpayload", + "/enterprise/v4/object/updatepullrequestpayload": "/enterprise-server@latest/graphql/reference/objects#updatepullrequestpayload", + "/enterprise/v4/object/updatepullrequestreviewcommentpayload": "/enterprise-server@latest/graphql/reference/objects#updatepullrequestreviewcommentpayload", + "/enterprise/v4/object/updatepullrequestreviewpayload": "/enterprise-server@latest/graphql/reference/objects#updatepullrequestreviewpayload", + "/enterprise/v4/object/updaterefpayload": "/enterprise-server@latest/graphql/reference/objects#updaterefpayload", + "/enterprise/v4/object/updaterefspayload": "/enterprise-server@latest/graphql/reference/objects#updaterefspayload", + "/enterprise/v4/object/updaterepositorypayload": "/enterprise-server@latest/graphql/reference/objects#updaterepositorypayload", + "/enterprise/v4/object/updatesubscriptionpayload": "/enterprise-server@latest/graphql/reference/objects#updatesubscriptionpayload", + "/enterprise/v4/object/updateteamdiscussioncommentpayload": "/enterprise-server@latest/graphql/reference/objects#updateteamdiscussioncommentpayload", + "/enterprise/v4/object/updateteamdiscussionpayload": "/enterprise-server@latest/graphql/reference/objects#updateteamdiscussionpayload", + "/enterprise/v4/object/updateteamreviewassignmentpayload": "/enterprise-server@latest/graphql/reference/objects#updateteamreviewassignmentpayload", + "/enterprise/v4/object/updatetopicspayload": "/enterprise-server@latest/graphql/reference/objects#updatetopicspayload", + "/enterprise/v4/object/user": "/enterprise-server@latest/graphql/reference/objects#user", + "/enterprise/v4/object/userblockedevent": "/enterprise-server@latest/graphql/reference/objects#userblockedevent", + "/enterprise/v4/object/userconnection": "/enterprise-server@latest/graphql/reference/objects#userconnection", + "/enterprise/v4/object/usercontentedit": "/enterprise-server@latest/graphql/reference/objects#usercontentedit", + "/enterprise/v4/object/usercontenteditconnection": "/enterprise-server@latest/graphql/reference/objects#usercontenteditconnection", + "/enterprise/v4/object/usercontenteditedge": "/enterprise-server@latest/graphql/reference/objects#usercontenteditedge", + "/enterprise/v4/object/useredge": "/enterprise-server@latest/graphql/reference/objects#useredge", + "/enterprise/v4/object/userstatus": "/enterprise-server@latest/graphql/reference/objects#userstatus", + "/enterprise/v4/object/userstatusconnection": "/enterprise-server@latest/graphql/reference/objects#userstatusconnection", + "/enterprise/v4/object/userstatusedge": "/enterprise-server@latest/graphql/reference/objects#userstatusedge", + "/enterprise/v4/object/viewerhovercardcontext": "/enterprise-server@latest/graphql/reference/objects#viewerhovercardcontext", + "/enterprise/v4/scalar/boolean": "/enterprise-server@latest/graphql/reference/scalars#boolean", + "/enterprise/v4/scalar/date": "/enterprise-server@latest/graphql/reference/scalars#date", + "/enterprise/v4/scalar/datetime": "/enterprise-server@latest/graphql/reference/scalars#datetime", + "/enterprise/v4/scalar/float": "/enterprise-server@latest/graphql/reference/scalars#float", + "/enterprise/v4/scalar/gitobjectid": "/enterprise-server@latest/graphql/reference/scalars#gitobjectid", + "/enterprise/v4/scalar/gitrefname": "/enterprise-server@latest/graphql/reference/scalars#gitrefname", + "/enterprise/v4/scalar/gitsshremote": "/enterprise-server@latest/graphql/reference/scalars#gitsshremote", + "/enterprise/v4/scalar/gittimestamp": "/enterprise-server@latest/graphql/reference/scalars#gittimestamp", + "/enterprise/v4/scalar/html": "/enterprise-server@latest/graphql/reference/scalars#html", + "/enterprise/v4/scalar/id": "/enterprise-server@latest/graphql/reference/scalars#id", + "/enterprise/v4/scalar/int": "/enterprise-server@latest/graphql/reference/scalars#int", + "/enterprise/v4/scalar/precisedatetime": "/enterprise-server@latest/graphql/reference/scalars#precisedatetime", + "/enterprise/v4/scalar/string": "/enterprise-server@latest/graphql/reference/scalars#string", + "/enterprise/v4/scalar/uri": "/enterprise-server@latest/graphql/reference/scalars#uri", + "/enterprise/v4/scalar/x509certificate": "/enterprise-server@latest/graphql/reference/scalars#x509certificate", + "/enterprise/v4/union/assignee": "/enterprise-server@latest/graphql/reference/unions#assignee", + "/enterprise/v4/union/auditentryactor": "/enterprise-server@latest/graphql/reference/unions#auditentryactor", + "/enterprise/v4/union/closer": "/enterprise-server@latest/graphql/reference/unions#closer", + "/enterprise/v4/union/createdissueorrestrictedcontribution": "/enterprise-server@latest/graphql/reference/unions#createdissueorrestrictedcontribution", + "/enterprise/v4/union/createdpullrequestorrestrictedcontribution": "/enterprise-server@latest/graphql/reference/unions#createdpullrequestorrestrictedcontribution", + "/enterprise/v4/union/createdrepositoryorrestrictedcontribution": "/enterprise-server@latest/graphql/reference/unions#createdrepositoryorrestrictedcontribution", + "/enterprise/v4/union/enterprisemember": "/enterprise-server@latest/graphql/reference/unions#enterprisemember", + "/enterprise/v4/union/ipallowlistowner": "/enterprise-server@latest/graphql/reference/unions#ipallowlistowner", + "/enterprise/v4/union/issueorpullrequest": "/enterprise-server@latest/graphql/reference/unions#issueorpullrequest", + "/enterprise/v4/union/issuetimelineitem": "/enterprise-server@latest/graphql/reference/unions#issuetimelineitem", + "/enterprise/v4/union/issuetimelineitems": "/enterprise-server@latest/graphql/reference/unions#issuetimelineitems", + "/enterprise/v4/union/milestoneitem": "/enterprise-server@latest/graphql/reference/unions#milestoneitem", + "/enterprise/v4/union/organizationauditentry": "/enterprise-server@latest/graphql/reference/unions#organizationauditentry", + "/enterprise/v4/union/orgrestorememberauditentrymembership": "/enterprise-server@latest/graphql/reference/unions#orgrestorememberauditentrymembership", + "/enterprise/v4/union/permissiongranter": "/enterprise-server@latest/graphql/reference/unions#permissiongranter", + "/enterprise/v4/union/pinnableitem": "/enterprise-server@latest/graphql/reference/unions#pinnableitem", + "/enterprise/v4/union/projectcarditem": "/enterprise-server@latest/graphql/reference/unions#projectcarditem", + "/enterprise/v4/union/pullrequesttimelineitem": "/enterprise-server@latest/graphql/reference/unions#pullrequesttimelineitem", + "/enterprise/v4/union/pullrequesttimelineitems": "/enterprise-server@latest/graphql/reference/unions#pullrequesttimelineitems", + "/enterprise/v4/union/pushallowanceactor": "/enterprise-server@latest/graphql/reference/unions#pushallowanceactor", + "/enterprise/v4/union/referencedsubject": "/enterprise-server@latest/graphql/reference/unions#referencedsubject", + "/enterprise/v4/union/renamedtitlesubject": "/enterprise-server@latest/graphql/reference/unions#renamedtitlesubject", + "/enterprise/v4/union/requestedreviewer": "/enterprise-server@latest/graphql/reference/unions#requestedreviewer", + "/enterprise/v4/union/reviewdismissalallowanceactor": "/enterprise-server@latest/graphql/reference/unions#reviewdismissalallowanceactor", + "/enterprise/v4/union/searchresultitem": "/enterprise-server@latest/graphql/reference/unions#searchresultitem", + "/enterprise/v4/union/statuscheckrollupcontext": "/enterprise-server@latest/graphql/reference/unions#statuscheckrollupcontext", + "/v3/actions/artifacts": "/rest/reference/actions#artifacts", + "/v3/actions/secrets": "/rest/reference/actions#secrets", + "/v3/actions/self-hosted-runners": "/rest/reference/actions#self-hosted-runners", + "/v3/actions/self_hosted_runners": "/rest/reference/actions#self-hosted-runners", + "/v3/actions/workflow-jobs": "/rest/reference/actions#workflow-jobs", + "/v3/actions/workflow-runs": "/rest/reference/actions#workflow-runs", + "/v3/actions/workflow_jobs": "/rest/reference/actions#workflow-jobs", + "/v3/actions/workflow_runs": "/rest/reference/actions#workflow-runs", + "/v3/actions/workflows": "/rest/reference/actions#workflows", + "/v3/activity/events": "/rest/reference/activity#events", + "/v3/activity/feeds": "/rest/reference/activity#feeds", + "/v3/activity/notifications": "/rest/reference/activity#notifications", + "/v3/activity/starring": "/rest/reference/activity#starring", + "/v3/activity/watching": "/rest/reference/activity#watching", + "/v3/apps/installations": "/rest/reference/apps#installations", + "/v3/apps/marketplace": "/rest/reference/apps#marketplace", + "/v3/apps/oauth_applications": "/rest/reference/apps#oauth-applications", + "/v3/checks/runs": "/rest/reference/checks#runs", + "/v3/checks/suites": "/rest/reference/checks#suites", + "/v3/enterprise-admin/admin_stats": "/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", + "/v3/enterprise-admin/global_webhooks": "/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", + "/v3/enterprise-admin/ldap": "/enterprise-server@latest/rest/reference/enterprise-admin#ldap", + "/v3/enterprise-admin/license": "/enterprise-server@latest/rest/reference/enterprise-admin#license", + "/v3/enterprise-admin/management_console": "/enterprise-server@latest/rest/reference/enterprise-admin#management-console", + "/v3/enterprise-admin/orgs": "/enterprise-server@latest/rest/reference/enterprise-admin#orgs", + "/v3/enterprise-admin/pre_receive_environments": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", + "/v3/enterprise-admin/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", + "/v3/enterprise-admin/search_indexing": "/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", + "/v3/enterprise-admin/users": "/enterprise-server@latest/rest/reference/enterprise-admin#users", + "/v3/enterprise/admin_stats": "/enterprise-server@latest/rest/reference/enterprise-admin#admin-stats", + "/v3/enterprise/global_webhooks": "/enterprise-server@latest/rest/reference/enterprise-admin#global-webhooks", + "/v3/enterprise/ldap": "/enterprise-server@latest/rest/reference/enterprise-admin#ldap", + "/v3/enterprise/license": "/enterprise-server@latest/rest/reference/enterprise-admin#license", + "/v3/enterprise/management_console": "/enterprise-server@latest/rest/reference/enterprise-admin#management-console", + "/v3/enterprise/org_pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", + "/v3/enterprise/orgs": "/enterprise-server@latest/rest/reference/enterprise-admin#orgs", + "/v3/enterprise/pre_receive_environments": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-environments", + "/v3/enterprise/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#pre-receive-hooks", + "/v3/enterprise/repo_pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", + "/v3/enterprise/search_indexing": "/enterprise-server@latest/rest/reference/enterprise-admin#search-indexing", + "/v3/enterprise/users": "/enterprise-server@latest/rest/reference/enterprise-admin#users", + "/v3/gists/comments": "/rest/reference/gists#comments", + "/v3/git/blobs": "/rest/reference/git#blobs", + "/v3/git/commits": "/rest/reference/git#commits", + "/v3/git/refs": "/rest/reference/git#refs", + "/v3/git/tags": "/rest/reference/git#tags", + "/v3/git/trees": "/rest/reference/git#trees", + "/v3/integrations/installations": "/developers/apps#installations", + "/v3/interactions/orgs": "/rest/reference/interactions#orgs", + "/v3/interactions/repos": "/rest/reference/interactions#repos", + "/v3/issues/assignees": "/rest/reference/issues#assignees", + "/v3/issues/comments": "/rest/reference/issues#comments", + "/v3/issues/events": "/rest/reference/issues#events", + "/v3/issues/labels": "/rest/reference/issues#labels", + "/v3/issues/milestones": "/rest/reference/issues#milestones", + "/v3/issues/timeline": "/rest/reference/issues#timeline", + "/v3/migration/source_imports": "/rest/reference/migrations#source-imports", + "/v3/migrations/orgs": "/rest/reference/migrations#orgs", + "/v3/migrations/source_imports": "/rest/reference/migrations#source-imports", + "/v3/migrations/users": "/rest/reference/migrations#users", + "/v3/oauth_authorizations": "/enterprise-server@latest/rest/reference/oauth-authorizations", + "/v3/orgs/blocking": "/rest/reference/orgs#blocking", + "/v3/orgs/hooks": "/rest/reference/orgs#webhooks", + "/v3/orgs/members": "/rest/reference/orgs#members", + "/v3/orgs/migrations": "/rest/reference/orgs#migrations", + "/v3/orgs/outside_collaborators": "/rest/reference/orgs#outside-collaborators", + "/v3/orgs/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#organization-pre-receive-hooks", + "/v3/orgs/teams": "/rest/reference/orgs#teams", + "/v3/projects/cards": "/rest/reference/projects#cards", + "/v3/projects/collaborators": "/rest/reference/projects#collaborators", + "/v3/projects/columns": "/rest/reference/projects#columns", + "/v3/pulls/comments": "/rest/reference/pulls#comments", + "/v3/pulls/review_requests": "/rest/reference/pulls#review-requests", + "/v3/pulls/reviews": "/rest/reference/pulls#reviews", + "/v3/repos/branches": "/rest/reference/repos#branches", + "/v3/repos/collaborators": "/rest/reference/repos#collaborators", + "/v3/repos/comments": "/rest/reference/repos#comments", + "/v3/repos/commits": "/rest/reference/repos#commits", + "/v3/repos/community": "/rest/reference/repos#community", + "/v3/repos/contents": "/rest/reference/repos#contents", + "/v3/repos/deployments": "/rest/reference/repos#deployments", + "/v3/repos/downloads": "/rest/reference/repos#downloads", + "/v3/repos/forks": "/rest/reference/repos#forks", + "/v3/repos/hooks": "/rest/reference/repos#webhooks", + "/v3/repos/invitations": "/rest/reference/repos#invitations", + "/v3/repos/keys": "/rest/reference/repos#keys", + "/v3/repos/merging": "/rest/reference/repos#merging", + "/v3/repos/pages": "/rest/reference/repos#pages", + "/v3/repos/pre_receive_hooks": "/enterprise-server@latest/rest/reference/enterprise-admin#repository-pre-receive-hooks", + "/v3/repos/releases": "/rest/reference/repos#releases", + "/v3/repos/statistics": "/rest/reference/repos#statistics", + "/v3/repos/statuses": "/rest/reference/repos#statuses", + "/v3/repos/traffic": "/rest/reference/repos#traffic", + "/v3/teams/discussion_comments": "/rest/reference/teams#discussion-comments", + "/v3/teams/discussions": "/rest/reference/teams#discussions", + "/v3/teams/members": "/rest/reference/teams#members", + "/v3/teams/team_sync": "/rest/reference/teams#team-sync", + "/v3/users/blocking": "/rest/reference/users#blocking", + "/v3/users/emails": "/rest/reference/users#emails", + "/v3/users/followers": "/rest/reference/users#followers", + "/v3/users/gpg_keys": "/rest/reference/users#gpg-keys", + "/v3/users/keys": "/rest/reference/users#keys", + "/v4/enum/__directivelocation": "/graphql/reference/enums#__directivelocation", + "/v4/enum/__typekind": "/graphql/reference/enums#__typekind", + "/v4/enum/actionexecutioncapabilitysetting": "/graphql/reference/enums#actionexecutioncapabilitysetting", + "/v4/enum/auditlogorderfield": "/graphql/reference/enums#auditlogorderfield", + "/v4/enum/checkannotationlevel": "/graphql/reference/enums#checkannotationlevel", + "/v4/enum/checkconclusionstate": "/graphql/reference/enums#checkconclusionstate", + "/v4/enum/checkruntype": "/graphql/reference/enums#checkruntype", + "/v4/enum/checkstatusstate": "/graphql/reference/enums#checkstatusstate", + "/v4/enum/collaboratoraffiliation": "/graphql/reference/enums#collaboratoraffiliation", + "/v4/enum/commentauthorassociation": "/graphql/reference/enums#commentauthorassociation", + "/v4/enum/commentcannotupdatereason": "/graphql/reference/enums#commentcannotupdatereason", + "/v4/enum/commitcontributionorderfield": "/graphql/reference/enums#commitcontributionorderfield", + "/v4/enum/defaultrepositorypermissionfield": "/graphql/reference/enums#defaultrepositorypermissionfield", + "/v4/enum/deploymentorderfield": "/graphql/reference/enums#deploymentorderfield", + "/v4/enum/deploymentstate": "/graphql/reference/enums#deploymentstate", + "/v4/enum/deploymentstatusstate": "/graphql/reference/enums#deploymentstatusstate", + "/v4/enum/diffside": "/graphql/reference/enums#diffside", + "/v4/enum/enterpriseadministratorinvitationorderfield": "/graphql/reference/enums#enterpriseadministratorinvitationorderfield", + "/v4/enum/enterpriseadministratorrole": "/graphql/reference/enums#enterpriseadministratorrole", + "/v4/enum/enterprisedefaultrepositorypermissionsettingvalue": "/graphql/reference/enums#enterprisedefaultrepositorypermissionsettingvalue", + "/v4/enum/enterpriseenableddisabledsettingvalue": "/graphql/reference/enums#enterpriseenableddisabledsettingvalue", + "/v4/enum/enterpriseenabledsettingvalue": "/graphql/reference/enums#enterpriseenabledsettingvalue", + "/v4/enum/enterprisememberorderfield": "/graphql/reference/enums#enterprisememberorderfield", + "/v4/enum/enterprisememberscancreaterepositoriessettingvalue": "/graphql/reference/enums#enterprisememberscancreaterepositoriessettingvalue", + "/v4/enum/enterprisememberscanmakepurchasessettingvalue": "/graphql/reference/enums#enterprisememberscanmakepurchasessettingvalue", + "/v4/enum/enterpriseserverinstallationorderfield": "/graphql/reference/enums#enterpriseserverinstallationorderfield", + "/v4/enum/enterpriseserveruseraccountemailorderfield": "/graphql/reference/enums#enterpriseserveruseraccountemailorderfield", + "/v4/enum/enterpriseserveruseraccountorderfield": "/graphql/reference/enums#enterpriseserveruseraccountorderfield", + "/v4/enum/enterpriseserveruseraccountsuploadorderfield": "/graphql/reference/enums#enterpriseserveruseraccountsuploadorderfield", + "/v4/enum/enterpriseserveruseraccountsuploadsyncstate": "/graphql/reference/enums#enterpriseserveruseraccountsuploadsyncstate", + "/v4/enum/enterpriseuseraccountmembershiprole": "/graphql/reference/enums#enterpriseuseraccountmembershiprole", + "/v4/enum/enterpriseuserdeployment": "/graphql/reference/enums#enterpriseuserdeployment", + "/v4/enum/fundingplatform": "/graphql/reference/enums#fundingplatform", + "/v4/enum/gistorderfield": "/graphql/reference/enums#gistorderfield", + "/v4/enum/gistprivacy": "/graphql/reference/enums#gistprivacy", + "/v4/enum/gitsignaturestate": "/graphql/reference/enums#gitsignaturestate", + "/v4/enum/identityproviderconfigurationstate": "/graphql/reference/enums#identityproviderconfigurationstate", + "/v4/enum/ipallowlistenabledsettingvalue": "/graphql/reference/enums#ipallowlistenabledsettingvalue", + "/v4/enum/ipallowlistentryorderfield": "/graphql/reference/enums#ipallowlistentryorderfield", + "/v4/enum/issueorderfield": "/graphql/reference/enums#issueorderfield", + "/v4/enum/issuestate": "/graphql/reference/enums#issuestate", + "/v4/enum/issuetimelineitemsitemtype": "/graphql/reference/enums#issuetimelineitemsitemtype", + "/v4/enum/labelorderfield": "/graphql/reference/enums#labelorderfield", + "/v4/enum/languageorderfield": "/graphql/reference/enums#languageorderfield", + "/v4/enum/lockreason": "/graphql/reference/enums#lockreason", + "/v4/enum/mergeablestate": "/graphql/reference/enums#mergeablestate", + "/v4/enum/mergestatestatus": "/graphql/reference/enums#mergestatestatus", + "/v4/enum/milestoneorderfield": "/graphql/reference/enums#milestoneorderfield", + "/v4/enum/milestonestate": "/graphql/reference/enums#milestonestate", + "/v4/enum/oauthapplicationcreateauditentrystate": "/graphql/reference/enums#oauthapplicationcreateauditentrystate", + "/v4/enum/operationtype": "/graphql/reference/enums#operationtype", + "/v4/enum/orderdirection": "/graphql/reference/enums#orderdirection", + "/v4/enum/orgaddmemberauditentrypermission": "/graphql/reference/enums#orgaddmemberauditentrypermission", + "/v4/enum/organizationinvitationrole": "/graphql/reference/enums#organizationinvitationrole", + "/v4/enum/organizationinvitationtype": "/graphql/reference/enums#organizationinvitationtype", + "/v4/enum/organizationmemberrole": "/graphql/reference/enums#organizationmemberrole", + "/v4/enum/organizationmemberscancreaterepositoriessettingvalue": "/graphql/reference/enums#organizationmemberscancreaterepositoriessettingvalue", + "/v4/enum/organizationorderfield": "/graphql/reference/enums#organizationorderfield", + "/v4/enum/orgcreateauditentrybillingplan": "/graphql/reference/enums#orgcreateauditentrybillingplan", + "/v4/enum/orgremovebillingmanagerauditentryreason": "/graphql/reference/enums#orgremovebillingmanagerauditentryreason", + "/v4/enum/orgremovememberauditentrymembershiptype": "/graphql/reference/enums#orgremovememberauditentrymembershiptype", + "/v4/enum/orgremovememberauditentryreason": "/graphql/reference/enums#orgremovememberauditentryreason", + "/v4/enum/orgremoveoutsidecollaboratorauditentrymembershiptype": "/graphql/reference/enums#orgremoveoutsidecollaboratorauditentrymembershiptype", + "/v4/enum/orgremoveoutsidecollaboratorauditentryreason": "/graphql/reference/enums#orgremoveoutsidecollaboratorauditentryreason", + "/v4/enum/orgupdatedefaultrepositorypermissionauditentrypermission": "/graphql/reference/enums#orgupdatedefaultrepositorypermissionauditentrypermission", + "/v4/enum/orgupdatememberauditentrypermission": "/graphql/reference/enums#orgupdatememberauditentrypermission", + "/v4/enum/orgupdatememberrepositorycreationpermissionauditentryvisibility": "/graphql/reference/enums#orgupdatememberrepositorycreationpermissionauditentryvisibility", + "/v4/enum/packagefileorderfield": "/graphql/reference/enums#packagefileorderfield", + "/v4/enum/packageorderfield": "/graphql/reference/enums#packageorderfield", + "/v4/enum/packagetype": "/graphql/reference/enums#packagetype", + "/v4/enum/packageversionorderfield": "/graphql/reference/enums#packageversionorderfield", + "/v4/enum/pinnableitemtype": "/graphql/reference/enums#pinnableitemtype", + "/v4/enum/projectcardarchivedstate": "/graphql/reference/enums#projectcardarchivedstate", + "/v4/enum/projectcardstate": "/graphql/reference/enums#projectcardstate", + "/v4/enum/projectcolumnpurpose": "/graphql/reference/enums#projectcolumnpurpose", + "/v4/enum/projectorderfield": "/graphql/reference/enums#projectorderfield", + "/v4/enum/projectstate": "/graphql/reference/enums#projectstate", + "/v4/enum/projecttemplate": "/graphql/reference/enums#projecttemplate", + "/v4/enum/pullrequestmergemethod": "/graphql/reference/enums#pullrequestmergemethod", + "/v4/enum/pullrequestorderfield": "/graphql/reference/enums#pullrequestorderfield", + "/v4/enum/pullrequestreviewcommentstate": "/graphql/reference/enums#pullrequestreviewcommentstate", + "/v4/enum/pullrequestreviewdecision": "/graphql/reference/enums#pullrequestreviewdecision", + "/v4/enum/pullrequestreviewevent": "/graphql/reference/enums#pullrequestreviewevent", + "/v4/enum/pullrequestreviewstate": "/graphql/reference/enums#pullrequestreviewstate", + "/v4/enum/pullrequeststate": "/graphql/reference/enums#pullrequeststate", + "/v4/enum/pullrequesttimelineitemsitemtype": "/graphql/reference/enums#pullrequesttimelineitemsitemtype", + "/v4/enum/pullrequestupdatestate": "/graphql/reference/enums#pullrequestupdatestate", + "/v4/enum/reactioncontent": "/graphql/reference/enums#reactioncontent", + "/v4/enum/reactionorderfield": "/graphql/reference/enums#reactionorderfield", + "/v4/enum/reforderfield": "/graphql/reference/enums#reforderfield", + "/v4/enum/releaseorderfield": "/graphql/reference/enums#releaseorderfield", + "/v4/enum/repoaccessauditentryvisibility": "/graphql/reference/enums#repoaccessauditentryvisibility", + "/v4/enum/repoaddmemberauditentryvisibility": "/graphql/reference/enums#repoaddmemberauditentryvisibility", + "/v4/enum/repoarchivedauditentryvisibility": "/graphql/reference/enums#repoarchivedauditentryvisibility", + "/v4/enum/repochangemergesettingauditentrymergetype": "/graphql/reference/enums#repochangemergesettingauditentrymergetype", + "/v4/enum/repocreateauditentryvisibility": "/graphql/reference/enums#repocreateauditentryvisibility", + "/v4/enum/repodestroyauditentryvisibility": "/graphql/reference/enums#repodestroyauditentryvisibility", + "/v4/enum/reporemovememberauditentryvisibility": "/graphql/reference/enums#reporemovememberauditentryvisibility", + "/v4/enum/reportedcontentclassifiers": "/graphql/reference/enums#reportedcontentclassifiers", + "/v4/enum/repositoryaffiliation": "/graphql/reference/enums#repositoryaffiliation", + "/v4/enum/repositorycontributiontype": "/graphql/reference/enums#repositorycontributiontype", + "/v4/enum/repositoryinvitationorderfield": "/graphql/reference/enums#repositoryinvitationorderfield", + "/v4/enum/repositorylockreason": "/graphql/reference/enums#repositorylockreason", + "/v4/enum/repositoryorderfield": "/graphql/reference/enums#repositoryorderfield", + "/v4/enum/repositorypermission": "/graphql/reference/enums#repositorypermission", + "/v4/enum/repositoryprivacy": "/graphql/reference/enums#repositoryprivacy", + "/v4/enum/repositoryvisibility": "/graphql/reference/enums#repositoryvisibility", + "/v4/enum/requestablecheckstatusstate": "/graphql/reference/enums#requestablecheckstatusstate", + "/v4/enum/samldigestalgorithm": "/graphql/reference/enums#samldigestalgorithm", + "/v4/enum/samlsignaturealgorithm": "/graphql/reference/enums#samlsignaturealgorithm", + "/v4/enum/savedreplyorderfield": "/graphql/reference/enums#savedreplyorderfield", + "/v4/enum/searchtype": "/graphql/reference/enums#searchtype", + "/v4/enum/securityadvisoryecosystem": "/graphql/reference/enums#securityadvisoryecosystem", + "/v4/enum/securityadvisoryidentifiertype": "/graphql/reference/enums#securityadvisoryidentifiertype", + "/v4/enum/securityadvisoryorderfield": "/graphql/reference/enums#securityadvisoryorderfield", + "/v4/enum/securityadvisoryseverity": "/graphql/reference/enums#securityadvisoryseverity", + "/v4/enum/securityvulnerabilityorderfield": "/graphql/reference/enums#securityvulnerabilityorderfield", + "/v4/enum/sponsorshiporderfield": "/graphql/reference/enums#sponsorshiporderfield", + "/v4/enum/sponsorshipprivacy": "/graphql/reference/enums#sponsorshipprivacy", + "/v4/enum/sponsorstierorderfield": "/graphql/reference/enums#sponsorstierorderfield", + "/v4/enum/starorderfield": "/graphql/reference/enums#starorderfield", + "/v4/enum/statusstate": "/graphql/reference/enums#statusstate", + "/v4/enum/subscriptionstate": "/graphql/reference/enums#subscriptionstate", + "/v4/enum/teamdiscussioncommentorderfield": "/graphql/reference/enums#teamdiscussioncommentorderfield", + "/v4/enum/teamdiscussionorderfield": "/graphql/reference/enums#teamdiscussionorderfield", + "/v4/enum/teammemberorderfield": "/graphql/reference/enums#teammemberorderfield", + "/v4/enum/teammemberrole": "/graphql/reference/enums#teammemberrole", + "/v4/enum/teammembershiptype": "/graphql/reference/enums#teammembershiptype", + "/v4/enum/teamorderfield": "/graphql/reference/enums#teamorderfield", + "/v4/enum/teamprivacy": "/graphql/reference/enums#teamprivacy", + "/v4/enum/teamrepositoryorderfield": "/graphql/reference/enums#teamrepositoryorderfield", + "/v4/enum/teamreviewassignmentalgorithm": "/graphql/reference/enums#teamreviewassignmentalgorithm", + "/v4/enum/teamrole": "/graphql/reference/enums#teamrole", + "/v4/enum/topicsuggestiondeclinereason": "/graphql/reference/enums#topicsuggestiondeclinereason", + "/v4/enum/userblockduration": "/graphql/reference/enums#userblockduration", + "/v4/enum/userstatusorderfield": "/graphql/reference/enums#userstatusorderfield", + "/v4/input_object/acceptenterpriseadministratorinvitationinput": "/graphql/reference/input-objects#acceptenterpriseadministratorinvitationinput", + "/v4/input_object/accepttopicsuggestioninput": "/graphql/reference/input-objects#accepttopicsuggestioninput", + "/v4/input_object/addassigneestoassignableinput": "/graphql/reference/input-objects#addassigneestoassignableinput", + "/v4/input_object/addcommentinput": "/graphql/reference/input-objects#addcommentinput", + "/v4/input_object/addlabelstolabelableinput": "/graphql/reference/input-objects#addlabelstolabelableinput", + "/v4/input_object/addprojectcardinput": "/graphql/reference/input-objects#addprojectcardinput", + "/v4/input_object/addprojectcolumninput": "/graphql/reference/input-objects#addprojectcolumninput", + "/v4/input_object/addpullrequestreviewcommentinput": "/graphql/reference/input-objects#addpullrequestreviewcommentinput", + "/v4/input_object/addpullrequestreviewinput": "/graphql/reference/input-objects#addpullrequestreviewinput", + "/v4/input_object/addpullrequestreviewthreadinput": "/graphql/reference/input-objects#addpullrequestreviewthreadinput", + "/v4/input_object/addreactioninput": "/graphql/reference/input-objects#addreactioninput", + "/v4/input_object/addstarinput": "/graphql/reference/input-objects#addstarinput", + "/v4/input_object/archiverepositoryinput": "/graphql/reference/input-objects#archiverepositoryinput", + "/v4/input_object/auditlogorder": "/graphql/reference/input-objects#auditlogorder", + "/v4/input_object/cancelenterpriseadmininvitationinput": "/graphql/reference/input-objects#cancelenterpriseadmininvitationinput", + "/v4/input_object/changeuserstatusinput": "/graphql/reference/input-objects#changeuserstatusinput", + "/v4/input_object/checkannotationdata": "/graphql/reference/input-objects#checkannotationdata", + "/v4/input_object/checkannotationrange": "/graphql/reference/input-objects#checkannotationrange", + "/v4/input_object/checkrunaction": "/graphql/reference/input-objects#checkrunaction", + "/v4/input_object/checkrunfilter": "/graphql/reference/input-objects#checkrunfilter", + "/v4/input_object/checkrunoutput": "/graphql/reference/input-objects#checkrunoutput", + "/v4/input_object/checkrunoutputimage": "/graphql/reference/input-objects#checkrunoutputimage", + "/v4/input_object/checksuiteautotriggerpreference": "/graphql/reference/input-objects#checksuiteautotriggerpreference", + "/v4/input_object/checksuitefilter": "/graphql/reference/input-objects#checksuitefilter", + "/v4/input_object/clearlabelsfromlabelableinput": "/graphql/reference/input-objects#clearlabelsfromlabelableinput", + "/v4/input_object/cloneprojectinput": "/graphql/reference/input-objects#cloneprojectinput", + "/v4/input_object/clonetemplaterepositoryinput": "/graphql/reference/input-objects#clonetemplaterepositoryinput", + "/v4/input_object/closeissueinput": "/graphql/reference/input-objects#closeissueinput", + "/v4/input_object/closepullrequestinput": "/graphql/reference/input-objects#closepullrequestinput", + "/v4/input_object/commitauthor": "/graphql/reference/input-objects#commitauthor", + "/v4/input_object/commitcontributionorder": "/graphql/reference/input-objects#commitcontributionorder", + "/v4/input_object/contributionorder": "/graphql/reference/input-objects#contributionorder", + "/v4/input_object/convertprojectcardnotetoissueinput": "/graphql/reference/input-objects#convertprojectcardnotetoissueinput", + "/v4/input_object/createbranchprotectionruleinput": "/graphql/reference/input-objects#createbranchprotectionruleinput", + "/v4/input_object/createcheckruninput": "/graphql/reference/input-objects#createcheckruninput", + "/v4/input_object/createchecksuiteinput": "/graphql/reference/input-objects#createchecksuiteinput", + "/v4/input_object/createcontentattachmentinput": "/graphql/reference/input-objects#createcontentattachmentinput", + "/v4/input_object/createdeploymentinput": "/graphql/reference/input-objects#createdeploymentinput", + "/v4/input_object/createdeploymentstatusinput": "/graphql/reference/input-objects#createdeploymentstatusinput", + "/v4/input_object/createenterpriseorganizationinput": "/graphql/reference/input-objects#createenterpriseorganizationinput", + "/v4/input_object/createipallowlistentryinput": "/graphql/reference/input-objects#createipallowlistentryinput", + "/v4/input_object/createissueinput": "/graphql/reference/input-objects#createissueinput", + "/v4/input_object/createlabelinput": "/graphql/reference/input-objects#createlabelinput", + "/v4/input_object/createprojectinput": "/graphql/reference/input-objects#createprojectinput", + "/v4/input_object/createpullrequestinput": "/graphql/reference/input-objects#createpullrequestinput", + "/v4/input_object/createrefinput": "/graphql/reference/input-objects#createrefinput", + "/v4/input_object/createrepositoryinput": "/graphql/reference/input-objects#createrepositoryinput", + "/v4/input_object/createteamdiscussioncommentinput": "/graphql/reference/input-objects#createteamdiscussioncommentinput", + "/v4/input_object/createteamdiscussioninput": "/graphql/reference/input-objects#createteamdiscussioninput", + "/v4/input_object/declinetopicsuggestioninput": "/graphql/reference/input-objects#declinetopicsuggestioninput", + "/v4/input_object/deletebranchprotectionruleinput": "/graphql/reference/input-objects#deletebranchprotectionruleinput", + "/v4/input_object/deletedeploymentinput": "/graphql/reference/input-objects#deletedeploymentinput", + "/v4/input_object/deleteipallowlistentryinput": "/graphql/reference/input-objects#deleteipallowlistentryinput", + "/v4/input_object/deleteissuecommentinput": "/graphql/reference/input-objects#deleteissuecommentinput", + "/v4/input_object/deleteissueinput": "/graphql/reference/input-objects#deleteissueinput", + "/v4/input_object/deletelabelinput": "/graphql/reference/input-objects#deletelabelinput", + "/v4/input_object/deletepackageversioninput": "/graphql/reference/input-objects#deletepackageversioninput", + "/v4/input_object/deleteprojectcardinput": "/graphql/reference/input-objects#deleteprojectcardinput", + "/v4/input_object/deleteprojectcolumninput": "/graphql/reference/input-objects#deleteprojectcolumninput", + "/v4/input_object/deleteprojectinput": "/graphql/reference/input-objects#deleteprojectinput", + "/v4/input_object/deletepullrequestreviewcommentinput": "/graphql/reference/input-objects#deletepullrequestreviewcommentinput", + "/v4/input_object/deletepullrequestreviewinput": "/graphql/reference/input-objects#deletepullrequestreviewinput", + "/v4/input_object/deleterefinput": "/graphql/reference/input-objects#deleterefinput", + "/v4/input_object/deleteteamdiscussioncommentinput": "/graphql/reference/input-objects#deleteteamdiscussioncommentinput", + "/v4/input_object/deleteteamdiscussioninput": "/graphql/reference/input-objects#deleteteamdiscussioninput", + "/v4/input_object/deploymentorder": "/graphql/reference/input-objects#deploymentorder", + "/v4/input_object/dismisspullrequestreviewinput": "/graphql/reference/input-objects#dismisspullrequestreviewinput", + "/v4/input_object/draftpullrequestreviewcomment": "/graphql/reference/input-objects#draftpullrequestreviewcomment", + "/v4/input_object/draftpullrequestreviewthread": "/graphql/reference/input-objects#draftpullrequestreviewthread", + "/v4/input_object/enterpriseadministratorinvitationorder": "/graphql/reference/input-objects#enterpriseadministratorinvitationorder", + "/v4/input_object/enterprisememberorder": "/graphql/reference/input-objects#enterprisememberorder", + "/v4/input_object/enterpriseserverinstallationorder": "/graphql/reference/input-objects#enterpriseserverinstallationorder", + "/v4/input_object/enterpriseserveruseraccountemailorder": "/graphql/reference/input-objects#enterpriseserveruseraccountemailorder", + "/v4/input_object/enterpriseserveruseraccountorder": "/graphql/reference/input-objects#enterpriseserveruseraccountorder", + "/v4/input_object/enterpriseserveruseraccountsuploadorder": "/graphql/reference/input-objects#enterpriseserveruseraccountsuploadorder", + "/v4/input_object/followuserinput": "/graphql/reference/input-objects#followuserinput", + "/v4/input_object/gistorder": "/graphql/reference/input-objects#gistorder", + "/v4/input_object/importprojectinput": "/graphql/reference/input-objects#importprojectinput", + "/v4/input_object/inviteenterpriseadmininput": "/graphql/reference/input-objects#inviteenterpriseadmininput", + "/v4/input_object/ipallowlistentryorder": "/graphql/reference/input-objects#ipallowlistentryorder", + "/v4/input_object/issuefilters": "/graphql/reference/input-objects#issuefilters", + "/v4/input_object/issueorder": "/graphql/reference/input-objects#issueorder", + "/v4/input_object/labelorder": "/graphql/reference/input-objects#labelorder", + "/v4/input_object/languageorder": "/graphql/reference/input-objects#languageorder", + "/v4/input_object/linkrepositorytoprojectinput": "/graphql/reference/input-objects#linkrepositorytoprojectinput", + "/v4/input_object/locklockableinput": "/graphql/reference/input-objects#locklockableinput", + "/v4/input_object/markpullrequestreadyforreviewinput": "/graphql/reference/input-objects#markpullrequestreadyforreviewinput", + "/v4/input_object/mergebranchinput": "/graphql/reference/input-objects#mergebranchinput", + "/v4/input_object/mergepullrequestinput": "/graphql/reference/input-objects#mergepullrequestinput", + "/v4/input_object/milestoneorder": "/graphql/reference/input-objects#milestoneorder", + "/v4/input_object/minimizecommentinput": "/graphql/reference/input-objects#minimizecommentinput", + "/v4/input_object/moveprojectcardinput": "/graphql/reference/input-objects#moveprojectcardinput", + "/v4/input_object/moveprojectcolumninput": "/graphql/reference/input-objects#moveprojectcolumninput", + "/v4/input_object/organizationorder": "/graphql/reference/input-objects#organizationorder", + "/v4/input_object/packagefileorder": "/graphql/reference/input-objects#packagefileorder", + "/v4/input_object/packageorder": "/graphql/reference/input-objects#packageorder", + "/v4/input_object/packageversionorder": "/graphql/reference/input-objects#packageversionorder", + "/v4/input_object/pinissueinput": "/graphql/reference/input-objects#pinissueinput", + "/v4/input_object/projectcardimport": "/graphql/reference/input-objects#projectcardimport", + "/v4/input_object/projectcolumnimport": "/graphql/reference/input-objects#projectcolumnimport", + "/v4/input_object/projectorder": "/graphql/reference/input-objects#projectorder", + "/v4/input_object/pullrequestorder": "/graphql/reference/input-objects#pullrequestorder", + "/v4/input_object/reactionorder": "/graphql/reference/input-objects#reactionorder", + "/v4/input_object/reforder": "/graphql/reference/input-objects#reforder", + "/v4/input_object/refupdate": "/graphql/reference/input-objects#refupdate", + "/v4/input_object/regenerateenterpriseidentityproviderrecoverycodesinput": "/graphql/reference/input-objects#regenerateenterpriseidentityproviderrecoverycodesinput", + "/v4/input_object/releaseorder": "/graphql/reference/input-objects#releaseorder", + "/v4/input_object/removeassigneesfromassignableinput": "/graphql/reference/input-objects#removeassigneesfromassignableinput", + "/v4/input_object/removeenterpriseadmininput": "/graphql/reference/input-objects#removeenterpriseadmininput", + "/v4/input_object/removeenterpriseidentityproviderinput": "/graphql/reference/input-objects#removeenterpriseidentityproviderinput", + "/v4/input_object/removeenterpriseorganizationinput": "/graphql/reference/input-objects#removeenterpriseorganizationinput", + "/v4/input_object/removelabelsfromlabelableinput": "/graphql/reference/input-objects#removelabelsfromlabelableinput", + "/v4/input_object/removeoutsidecollaboratorinput": "/graphql/reference/input-objects#removeoutsidecollaboratorinput", + "/v4/input_object/removereactioninput": "/graphql/reference/input-objects#removereactioninput", + "/v4/input_object/removestarinput": "/graphql/reference/input-objects#removestarinput", + "/v4/input_object/reopenissueinput": "/graphql/reference/input-objects#reopenissueinput", + "/v4/input_object/reopenpullrequestinput": "/graphql/reference/input-objects#reopenpullrequestinput", + "/v4/input_object/repositoryinvitationorder": "/graphql/reference/input-objects#repositoryinvitationorder", + "/v4/input_object/repositoryorder": "/graphql/reference/input-objects#repositoryorder", + "/v4/input_object/requestreviewsinput": "/graphql/reference/input-objects#requestreviewsinput", + "/v4/input_object/rerequestchecksuiteinput": "/graphql/reference/input-objects#rerequestchecksuiteinput", + "/v4/input_object/resolvereviewthreadinput": "/graphql/reference/input-objects#resolvereviewthreadinput", + "/v4/input_object/savedreplyorder": "/graphql/reference/input-objects#savedreplyorder", + "/v4/input_object/securityadvisoryidentifierfilter": "/graphql/reference/input-objects#securityadvisoryidentifierfilter", + "/v4/input_object/securityadvisoryorder": "/graphql/reference/input-objects#securityadvisoryorder", + "/v4/input_object/securityvulnerabilityorder": "/graphql/reference/input-objects#securityvulnerabilityorder", + "/v4/input_object/setenterpriseidentityproviderinput": "/graphql/reference/input-objects#setenterpriseidentityproviderinput", + "/v4/input_object/sponsorshiporder": "/graphql/reference/input-objects#sponsorshiporder", + "/v4/input_object/sponsorstierorder": "/graphql/reference/input-objects#sponsorstierorder", + "/v4/input_object/starorder": "/graphql/reference/input-objects#starorder", + "/v4/input_object/submitpullrequestreviewinput": "/graphql/reference/input-objects#submitpullrequestreviewinput", + "/v4/input_object/teamdiscussioncommentorder": "/graphql/reference/input-objects#teamdiscussioncommentorder", + "/v4/input_object/teamdiscussionorder": "/graphql/reference/input-objects#teamdiscussionorder", + "/v4/input_object/teammemberorder": "/graphql/reference/input-objects#teammemberorder", + "/v4/input_object/teamorder": "/graphql/reference/input-objects#teamorder", + "/v4/input_object/teamrepositoryorder": "/graphql/reference/input-objects#teamrepositoryorder", + "/v4/input_object/transferissueinput": "/graphql/reference/input-objects#transferissueinput", + "/v4/input_object/unarchiverepositoryinput": "/graphql/reference/input-objects#unarchiverepositoryinput", + "/v4/input_object/unfollowuserinput": "/graphql/reference/input-objects#unfollowuserinput", + "/v4/input_object/unlinkrepositoryfromprojectinput": "/graphql/reference/input-objects#unlinkrepositoryfromprojectinput", + "/v4/input_object/unlocklockableinput": "/graphql/reference/input-objects#unlocklockableinput", + "/v4/input_object/unmarkissueasduplicateinput": "/graphql/reference/input-objects#unmarkissueasduplicateinput", + "/v4/input_object/unminimizecommentinput": "/graphql/reference/input-objects#unminimizecommentinput", + "/v4/input_object/unpinissueinput": "/graphql/reference/input-objects#unpinissueinput", + "/v4/input_object/unresolvereviewthreadinput": "/graphql/reference/input-objects#unresolvereviewthreadinput", + "/v4/input_object/updatebranchprotectionruleinput": "/graphql/reference/input-objects#updatebranchprotectionruleinput", + "/v4/input_object/updatecheckruninput": "/graphql/reference/input-objects#updatecheckruninput", + "/v4/input_object/updatechecksuitepreferencesinput": "/graphql/reference/input-objects#updatechecksuitepreferencesinput", + "/v4/input_object/updateenterpriseactionexecutioncapabilitysettinginput": "/graphql/reference/input-objects#updateenterpriseactionexecutioncapabilitysettinginput", + "/v4/input_object/updateenterpriseadministratorroleinput": "/graphql/reference/input-objects#updateenterpriseadministratorroleinput", + "/v4/input_object/updateenterpriseallowprivaterepositoryforkingsettinginput": "/graphql/reference/input-objects#updateenterpriseallowprivaterepositoryforkingsettinginput", + "/v4/input_object/updateenterprisedefaultrepositorypermissionsettinginput": "/graphql/reference/input-objects#updateenterprisedefaultrepositorypermissionsettinginput", + "/v4/input_object/updateenterprisememberscanchangerepositoryvisibilitysettinginput": "/graphql/reference/input-objects#updateenterprisememberscanchangerepositoryvisibilitysettinginput", + "/v4/input_object/updateenterprisememberscancreaterepositoriessettinginput": "/graphql/reference/input-objects#updateenterprisememberscancreaterepositoriessettinginput", + "/v4/input_object/updateenterprisememberscandeleteissuessettinginput": "/graphql/reference/input-objects#updateenterprisememberscandeleteissuessettinginput", + "/v4/input_object/updateenterprisememberscandeleterepositoriessettinginput": "/graphql/reference/input-objects#updateenterprisememberscandeleterepositoriessettinginput", + "/v4/input_object/updateenterprisememberscaninvitecollaboratorssettinginput": "/graphql/reference/input-objects#updateenterprisememberscaninvitecollaboratorssettinginput", + "/v4/input_object/updateenterprisememberscanmakepurchasessettinginput": "/graphql/reference/input-objects#updateenterprisememberscanmakepurchasessettinginput", + "/v4/input_object/updateenterprisememberscanupdateprotectedbranchessettinginput": "/graphql/reference/input-objects#updateenterprisememberscanupdateprotectedbranchessettinginput", + "/v4/input_object/updateenterprisememberscanviewdependencyinsightssettinginput": "/graphql/reference/input-objects#updateenterprisememberscanviewdependencyinsightssettinginput", + "/v4/input_object/updateenterpriseorganizationprojectssettinginput": "/graphql/reference/input-objects#updateenterpriseorganizationprojectssettinginput", + "/v4/input_object/updateenterpriseprofileinput": "/graphql/reference/input-objects#updateenterpriseprofileinput", + "/v4/input_object/updateenterpriserepositoryprojectssettinginput": "/graphql/reference/input-objects#updateenterpriserepositoryprojectssettinginput", + "/v4/input_object/updateenterpriseteamdiscussionssettinginput": "/graphql/reference/input-objects#updateenterpriseteamdiscussionssettinginput", + "/v4/input_object/updateenterprisetwofactorauthenticationrequiredsettinginput": "/graphql/reference/input-objects#updateenterprisetwofactorauthenticationrequiredsettinginput", + "/v4/input_object/updateipallowlistenabledsettinginput": "/graphql/reference/input-objects#updateipallowlistenabledsettinginput", + "/v4/input_object/updateipallowlistentryinput": "/graphql/reference/input-objects#updateipallowlistentryinput", + "/v4/input_object/updateissuecommentinput": "/graphql/reference/input-objects#updateissuecommentinput", + "/v4/input_object/updateissueinput": "/graphql/reference/input-objects#updateissueinput", + "/v4/input_object/updatelabelinput": "/graphql/reference/input-objects#updatelabelinput", + "/v4/input_object/updateprojectcardinput": "/graphql/reference/input-objects#updateprojectcardinput", + "/v4/input_object/updateprojectcolumninput": "/graphql/reference/input-objects#updateprojectcolumninput", + "/v4/input_object/updateprojectinput": "/graphql/reference/input-objects#updateprojectinput", + "/v4/input_object/updatepullrequestinput": "/graphql/reference/input-objects#updatepullrequestinput", + "/v4/input_object/updatepullrequestreviewcommentinput": "/graphql/reference/input-objects#updatepullrequestreviewcommentinput", + "/v4/input_object/updatepullrequestreviewinput": "/graphql/reference/input-objects#updatepullrequestreviewinput", + "/v4/input_object/updaterefinput": "/graphql/reference/input-objects#updaterefinput", + "/v4/input_object/updaterefsinput": "/graphql/reference/input-objects#updaterefsinput", + "/v4/input_object/updaterepositoryinput": "/graphql/reference/input-objects#updaterepositoryinput", + "/v4/input_object/updatesubscriptioninput": "/graphql/reference/input-objects#updatesubscriptioninput", + "/v4/input_object/updateteamdiscussioncommentinput": "/graphql/reference/input-objects#updateteamdiscussioncommentinput", + "/v4/input_object/updateteamdiscussioninput": "/graphql/reference/input-objects#updateteamdiscussioninput", + "/v4/input_object/updateteamreviewassignmentinput": "/graphql/reference/input-objects#updateteamreviewassignmentinput", + "/v4/input_object/updatetopicsinput": "/graphql/reference/input-objects#updatetopicsinput", + "/v4/input_object/userstatusorder": "/graphql/reference/input-objects#userstatusorder", + "/v4/interface/actor": "/graphql/reference/interfaces#actor", + "/v4/interface/assignable": "/graphql/reference/interfaces#assignable", + "/v4/interface/auditentry": "/graphql/reference/interfaces#auditentry", + "/v4/interface/closable": "/graphql/reference/interfaces#closable", + "/v4/interface/comment": "/graphql/reference/interfaces#comment", + "/v4/interface/contribution": "/graphql/reference/interfaces#contribution", + "/v4/interface/deletable": "/graphql/reference/interfaces#deletable", + "/v4/interface/enterpriseauditentrydata": "/graphql/reference/interfaces#enterpriseauditentrydata", + "/v4/interface/gitobject": "/graphql/reference/interfaces#gitobject", + "/v4/interface/gitsignature": "/graphql/reference/interfaces#gitsignature", + "/v4/interface/hovercardcontext": "/graphql/reference/interfaces#hovercardcontext", + "/v4/interface/labelable": "/graphql/reference/interfaces#labelable", + "/v4/interface/lockable": "/graphql/reference/interfaces#lockable", + "/v4/interface/memberstatusable": "/graphql/reference/interfaces#memberstatusable", + "/v4/interface/minimizable": "/graphql/reference/interfaces#minimizable", + "/v4/interface/node": "/graphql/reference/interfaces#node", + "/v4/interface/oauthapplicationauditentrydata": "/graphql/reference/interfaces#oauthapplicationauditentrydata", + "/v4/interface/organizationauditentrydata": "/graphql/reference/interfaces#organizationauditentrydata", + "/v4/interface/packageowner": "/graphql/reference/interfaces#packageowner", + "/v4/interface/profileowner": "/graphql/reference/interfaces#profileowner", + "/v4/interface/projectowner": "/graphql/reference/interfaces#projectowner", + "/v4/interface/reactable": "/graphql/reference/interfaces#reactable", + "/v4/interface/repositoryauditentrydata": "/graphql/reference/interfaces#repositoryauditentrydata", + "/v4/interface/repositoryinfo": "/graphql/reference/interfaces#repositoryinfo", + "/v4/interface/repositorynode": "/graphql/reference/interfaces#repositorynode", + "/v4/interface/repositoryowner": "/graphql/reference/interfaces#repositoryowner", + "/v4/interface/sponsorable": "/graphql/reference/interfaces#sponsorable", + "/v4/interface/starrable": "/graphql/reference/interfaces#starrable", + "/v4/interface/subscribable": "/graphql/reference/interfaces#subscribable", + "/v4/interface/teamauditentrydata": "/graphql/reference/interfaces#teamauditentrydata", + "/v4/interface/topicauditentrydata": "/graphql/reference/interfaces#topicauditentrydata", + "/v4/interface/uniformresourcelocatable": "/graphql/reference/interfaces#uniformresourcelocatable", + "/v4/interface/updatable": "/graphql/reference/interfaces#updatable", + "/v4/interface/updatablecomment": "/graphql/reference/interfaces#updatablecomment", + "/v4/mutation/acceptenterpriseadministratorinvitation": "/graphql/reference/mutations#acceptenterpriseadministratorinvitation", + "/v4/mutation/accepttopicsuggestion": "/graphql/reference/mutations#accepttopicsuggestion", + "/v4/mutation/addassigneestoassignable": "/graphql/reference/mutations#addassigneestoassignable", + "/v4/mutation/addcomment": "/graphql/reference/mutations#addcomment", + "/v4/mutation/addlabelstolabelable": "/graphql/reference/mutations#addlabelstolabelable", + "/v4/mutation/addprojectcard": "/graphql/reference/mutations#addprojectcard", + "/v4/mutation/addprojectcolumn": "/graphql/reference/mutations#addprojectcolumn", + "/v4/mutation/addpullrequestreview": "/graphql/reference/mutations#addpullrequestreview", + "/v4/mutation/addpullrequestreviewcomment": "/graphql/reference/mutations#addpullrequestreviewcomment", + "/v4/mutation/addpullrequestreviewthread": "/graphql/reference/mutations#addpullrequestreviewthread", + "/v4/mutation/addreaction": "/graphql/reference/mutations#addreaction", + "/v4/mutation/addstar": "/graphql/reference/mutations#addstar", + "/v4/mutation/archiverepository": "/graphql/reference/mutations#archiverepository", + "/v4/mutation/cancelenterpriseadmininvitation": "/graphql/reference/mutations#cancelenterpriseadmininvitation", + "/v4/mutation/changeuserstatus": "/graphql/reference/mutations#changeuserstatus", + "/v4/mutation/clearlabelsfromlabelable": "/graphql/reference/mutations#clearlabelsfromlabelable", + "/v4/mutation/cloneproject": "/graphql/reference/mutations#cloneproject", + "/v4/mutation/clonetemplaterepository": "/graphql/reference/mutations#clonetemplaterepository", + "/v4/mutation/closeissue": "/graphql/reference/mutations#closeissue", + "/v4/mutation/closepullrequest": "/graphql/reference/mutations#closepullrequest", + "/v4/mutation/convertprojectcardnotetoissue": "/graphql/reference/mutations#convertprojectcardnotetoissue", + "/v4/mutation/createbranchprotectionrule": "/graphql/reference/mutations#createbranchprotectionrule", + "/v4/mutation/createcheckrun": "/graphql/reference/mutations#createcheckrun", + "/v4/mutation/createchecksuite": "/graphql/reference/mutations#createchecksuite", + "/v4/mutation/createcontentattachment": "/graphql/reference/mutations#createcontentattachment", + "/v4/mutation/createdeployment": "/graphql/reference/mutations#createdeployment", + "/v4/mutation/createdeploymentstatus": "/graphql/reference/mutations#createdeploymentstatus", + "/v4/mutation/createenterpriseorganization": "/graphql/reference/mutations#createenterpriseorganization", + "/v4/mutation/createipallowlistentry": "/graphql/reference/mutations#createipallowlistentry", + "/v4/mutation/createissue": "/graphql/reference/mutations#createissue", + "/v4/mutation/createlabel": "/graphql/reference/mutations#createlabel", + "/v4/mutation/createproject": "/graphql/reference/mutations#createproject", + "/v4/mutation/createpullrequest": "/graphql/reference/mutations#createpullrequest", + "/v4/mutation/createref": "/graphql/reference/mutations#createref", + "/v4/mutation/createrepository": "/graphql/reference/mutations#createrepository", + "/v4/mutation/createteamdiscussion": "/graphql/reference/mutations#createteamdiscussion", + "/v4/mutation/createteamdiscussioncomment": "/graphql/reference/mutations#createteamdiscussioncomment", + "/v4/mutation/declinetopicsuggestion": "/graphql/reference/mutations#declinetopicsuggestion", + "/v4/mutation/deletebranchprotectionrule": "/graphql/reference/mutations#deletebranchprotectionrule", + "/v4/mutation/deletedeployment": "/graphql/reference/mutations#deletedeployment", + "/v4/mutation/deleteipallowlistentry": "/graphql/reference/mutations#deleteipallowlistentry", + "/v4/mutation/deleteissue": "/graphql/reference/mutations#deleteissue", + "/v4/mutation/deleteissuecomment": "/graphql/reference/mutations#deleteissuecomment", + "/v4/mutation/deletelabel": "/graphql/reference/mutations#deletelabel", + "/v4/mutation/deletepackageversion": "/graphql/reference/mutations#deletepackageversion", + "/v4/mutation/deleteproject": "/graphql/reference/mutations#deleteproject", + "/v4/mutation/deleteprojectcard": "/graphql/reference/mutations#deleteprojectcard", + "/v4/mutation/deleteprojectcolumn": "/graphql/reference/mutations#deleteprojectcolumn", + "/v4/mutation/deletepullrequestreview": "/graphql/reference/mutations#deletepullrequestreview", + "/v4/mutation/deletepullrequestreviewcomment": "/graphql/reference/mutations#deletepullrequestreviewcomment", + "/v4/mutation/deleteref": "/graphql/reference/mutations#deleteref", + "/v4/mutation/deleteteamdiscussion": "/graphql/reference/mutations#deleteteamdiscussion", + "/v4/mutation/deleteteamdiscussioncomment": "/graphql/reference/mutations#deleteteamdiscussioncomment", + "/v4/mutation/dismisspullrequestreview": "/graphql/reference/mutations#dismisspullrequestreview", + "/v4/mutation/followuser": "/graphql/reference/mutations#followuser", + "/v4/mutation/importproject": "/graphql/reference/mutations#importproject", + "/v4/mutation/inviteenterpriseadmin": "/graphql/reference/mutations#inviteenterpriseadmin", + "/v4/mutation/linkrepositorytoproject": "/graphql/reference/mutations#linkrepositorytoproject", + "/v4/mutation/locklockable": "/graphql/reference/mutations#locklockable", + "/v4/mutation/markpullrequestreadyforreview": "/graphql/reference/mutations#markpullrequestreadyforreview", + "/v4/mutation/mergebranch": "/graphql/reference/mutations#mergebranch", + "/v4/mutation/mergepullrequest": "/graphql/reference/mutations#mergepullrequest", + "/v4/mutation/minimizecomment": "/graphql/reference/mutations#minimizecomment", + "/v4/mutation/moveprojectcard": "/graphql/reference/mutations#moveprojectcard", + "/v4/mutation/moveprojectcolumn": "/graphql/reference/mutations#moveprojectcolumn", + "/v4/mutation/pinissue": "/graphql/reference/mutations#pinissue", + "/v4/mutation/regenerateenterpriseidentityproviderrecoverycodes": "/graphql/reference/mutations#regenerateenterpriseidentityproviderrecoverycodes", + "/v4/mutation/removeassigneesfromassignable": "/graphql/reference/mutations#removeassigneesfromassignable", + "/v4/mutation/removeenterpriseadmin": "/graphql/reference/mutations#removeenterpriseadmin", + "/v4/mutation/removeenterpriseidentityprovider": "/graphql/reference/mutations#removeenterpriseidentityprovider", + "/v4/mutation/removeenterpriseorganization": "/graphql/reference/mutations#removeenterpriseorganization", + "/v4/mutation/removelabelsfromlabelable": "/graphql/reference/mutations#removelabelsfromlabelable", + "/v4/mutation/removeoutsidecollaborator": "/graphql/reference/mutations#removeoutsidecollaborator", + "/v4/mutation/removereaction": "/graphql/reference/mutations#removereaction", + "/v4/mutation/removestar": "/graphql/reference/mutations#removestar", + "/v4/mutation/reopenissue": "/graphql/reference/mutations#reopenissue", + "/v4/mutation/reopenpullrequest": "/graphql/reference/mutations#reopenpullrequest", + "/v4/mutation/requestreviews": "/graphql/reference/mutations#requestreviews", + "/v4/mutation/rerequestchecksuite": "/graphql/reference/mutations#rerequestchecksuite", + "/v4/mutation/resolvereviewthread": "/graphql/reference/mutations#resolvereviewthread", + "/v4/mutation/setenterpriseidentityprovider": "/graphql/reference/mutations#setenterpriseidentityprovider", + "/v4/mutation/submitpullrequestreview": "/graphql/reference/mutations#submitpullrequestreview", + "/v4/mutation/transferissue": "/graphql/reference/mutations#transferissue", + "/v4/mutation/unarchiverepository": "/graphql/reference/mutations#unarchiverepository", + "/v4/mutation/unfollowuser": "/graphql/reference/mutations#unfollowuser", + "/v4/mutation/unlinkrepositoryfromproject": "/graphql/reference/mutations#unlinkrepositoryfromproject", + "/v4/mutation/unlocklockable": "/graphql/reference/mutations#unlocklockable", + "/v4/mutation/unmarkissueasduplicate": "/graphql/reference/mutations#unmarkissueasduplicate", + "/v4/mutation/unminimizecomment": "/graphql/reference/mutations#unminimizecomment", + "/v4/mutation/unpinissue": "/graphql/reference/mutations#unpinissue", + "/v4/mutation/unresolvereviewthread": "/graphql/reference/mutations#unresolvereviewthread", + "/v4/mutation/updatebranchprotectionrule": "/graphql/reference/mutations#updatebranchprotectionrule", + "/v4/mutation/updatecheckrun": "/graphql/reference/mutations#updatecheckrun", + "/v4/mutation/updatechecksuitepreferences": "/graphql/reference/mutations#updatechecksuitepreferences", + "/v4/mutation/updateenterpriseactionexecutioncapabilitysetting": "/graphql/reference/mutations#updateenterpriseactionexecutioncapabilitysetting", + "/v4/mutation/updateenterpriseadministratorrole": "/graphql/reference/mutations#updateenterpriseadministratorrole", + "/v4/mutation/updateenterpriseallowprivaterepositoryforkingsetting": "/graphql/reference/mutations#updateenterpriseallowprivaterepositoryforkingsetting", + "/v4/mutation/updateenterprisedefaultrepositorypermissionsetting": "/graphql/reference/mutations#updateenterprisedefaultrepositorypermissionsetting", + "/v4/mutation/updateenterprisememberscanchangerepositoryvisibilitysetting": "/graphql/reference/mutations#updateenterprisememberscanchangerepositoryvisibilitysetting", + "/v4/mutation/updateenterprisememberscancreaterepositoriessetting": "/graphql/reference/mutations#updateenterprisememberscancreaterepositoriessetting", + "/v4/mutation/updateenterprisememberscandeleteissuessetting": "/graphql/reference/mutations#updateenterprisememberscandeleteissuessetting", + "/v4/mutation/updateenterprisememberscandeleterepositoriessetting": "/graphql/reference/mutations#updateenterprisememberscandeleterepositoriessetting", + "/v4/mutation/updateenterprisememberscaninvitecollaboratorssetting": "/graphql/reference/mutations#updateenterprisememberscaninvitecollaboratorssetting", + "/v4/mutation/updateenterprisememberscanmakepurchasessetting": "/graphql/reference/mutations#updateenterprisememberscanmakepurchasessetting", + "/v4/mutation/updateenterprisememberscanupdateprotectedbranchessetting": "/graphql/reference/mutations#updateenterprisememberscanupdateprotectedbranchessetting", + "/v4/mutation/updateenterprisememberscanviewdependencyinsightssetting": "/graphql/reference/mutations#updateenterprisememberscanviewdependencyinsightssetting", + "/v4/mutation/updateenterpriseorganizationprojectssetting": "/graphql/reference/mutations#updateenterpriseorganizationprojectssetting", + "/v4/mutation/updateenterpriseprofile": "/graphql/reference/mutations#updateenterpriseprofile", + "/v4/mutation/updateenterpriserepositoryprojectssetting": "/graphql/reference/mutations#updateenterpriserepositoryprojectssetting", + "/v4/mutation/updateenterpriseteamdiscussionssetting": "/graphql/reference/mutations#updateenterpriseteamdiscussionssetting", + "/v4/mutation/updateenterprisetwofactorauthenticationrequiredsetting": "/graphql/reference/mutations#updateenterprisetwofactorauthenticationrequiredsetting", + "/v4/mutation/updateipallowlistenabledsetting": "/graphql/reference/mutations#updateipallowlistenabledsetting", + "/v4/mutation/updateipallowlistentry": "/graphql/reference/mutations#updateipallowlistentry", + "/v4/mutation/updateissue": "/graphql/reference/mutations#updateissue", + "/v4/mutation/updateissuecomment": "/graphql/reference/mutations#updateissuecomment", + "/v4/mutation/updatelabel": "/graphql/reference/mutations#updatelabel", + "/v4/mutation/updateproject": "/graphql/reference/mutations#updateproject", + "/v4/mutation/updateprojectcard": "/graphql/reference/mutations#updateprojectcard", + "/v4/mutation/updateprojectcolumn": "/graphql/reference/mutations#updateprojectcolumn", + "/v4/mutation/updatepullrequest": "/graphql/reference/mutations#updatepullrequest", + "/v4/mutation/updatepullrequestreview": "/graphql/reference/mutations#updatepullrequestreview", + "/v4/mutation/updatepullrequestreviewcomment": "/graphql/reference/mutations#updatepullrequestreviewcomment", + "/v4/mutation/updateref": "/graphql/reference/mutations#updateref", + "/v4/mutation/updaterefs": "/graphql/reference/mutations#updaterefs", + "/v4/mutation/updaterepository": "/graphql/reference/mutations#updaterepository", + "/v4/mutation/updatesubscription": "/graphql/reference/mutations#updatesubscription", + "/v4/mutation/updateteamdiscussion": "/graphql/reference/mutations#updateteamdiscussion", + "/v4/mutation/updateteamdiscussioncomment": "/graphql/reference/mutations#updateteamdiscussioncomment", + "/v4/mutation/updateteamreviewassignment": "/graphql/reference/mutations#updateteamreviewassignment", + "/v4/mutation/updatetopics": "/graphql/reference/mutations#updatetopics", + "/v4/object/__directive": "/graphql/reference/objects#__directive", + "/v4/object/__enumvalue": "/graphql/reference/objects#__enumvalue", + "/v4/object/__field": "/graphql/reference/objects#__field", + "/v4/object/__inputvalue": "/graphql/reference/objects#__inputvalue", + "/v4/object/__schema": "/graphql/reference/objects#__schema", + "/v4/object/__type": "/graphql/reference/objects#__type", + "/v4/object/acceptenterpriseadministratorinvitationpayload": "/graphql/reference/objects#acceptenterpriseadministratorinvitationpayload", + "/v4/object/accepttopicsuggestionpayload": "/graphql/reference/objects#accepttopicsuggestionpayload", + "/v4/object/actorlocation": "/graphql/reference/objects#actorlocation", + "/v4/object/addassigneestoassignablepayload": "/graphql/reference/objects#addassigneestoassignablepayload", + "/v4/object/addcommentpayload": "/graphql/reference/objects#addcommentpayload", + "/v4/object/addedtoprojectevent": "/graphql/reference/objects#addedtoprojectevent", + "/v4/object/addlabelstolabelablepayload": "/graphql/reference/objects#addlabelstolabelablepayload", + "/v4/object/addprojectcardpayload": "/graphql/reference/objects#addprojectcardpayload", + "/v4/object/addprojectcolumnpayload": "/graphql/reference/objects#addprojectcolumnpayload", + "/v4/object/addpullrequestreviewcommentpayload": "/graphql/reference/objects#addpullrequestreviewcommentpayload", + "/v4/object/addpullrequestreviewpayload": "/graphql/reference/objects#addpullrequestreviewpayload", + "/v4/object/addpullrequestreviewthreadpayload": "/graphql/reference/objects#addpullrequestreviewthreadpayload", + "/v4/object/addreactionpayload": "/graphql/reference/objects#addreactionpayload", + "/v4/object/addstarpayload": "/graphql/reference/objects#addstarpayload", + "/v4/object/app": "/graphql/reference/objects#app", + "/v4/object/archiverepositorypayload": "/graphql/reference/objects#archiverepositorypayload", + "/v4/object/assignedevent": "/graphql/reference/objects#assignedevent", + "/v4/object/automaticbasechangefailedevent": "/graphql/reference/objects#automaticbasechangefailedevent", + "/v4/object/automaticbasechangesucceededevent": "/graphql/reference/objects#automaticbasechangesucceededevent", + "/v4/object/baserefchangedevent": "/graphql/reference/objects#baserefchangedevent", + "/v4/object/baserefforcepushedevent": "/graphql/reference/objects#baserefforcepushedevent", + "/v4/object/blame": "/graphql/reference/objects#blame", + "/v4/object/blamerange": "/graphql/reference/objects#blamerange", + "/v4/object/blob": "/graphql/reference/objects#blob", + "/v4/object/bot": "/graphql/reference/objects#bot", + "/v4/object/branchprotectionrule": "/graphql/reference/objects#branchprotectionrule", + "/v4/object/branchprotectionruleconflict": "/graphql/reference/objects#branchprotectionruleconflict", + "/v4/object/branchprotectionruleconflictconnection": "/graphql/reference/objects#branchprotectionruleconflictconnection", + "/v4/object/branchprotectionruleconflictedge": "/graphql/reference/objects#branchprotectionruleconflictedge", + "/v4/object/branchprotectionruleconnection": "/graphql/reference/objects#branchprotectionruleconnection", + "/v4/object/branchprotectionruleedge": "/graphql/reference/objects#branchprotectionruleedge", + "/v4/object/cancelenterpriseadmininvitationpayload": "/graphql/reference/objects#cancelenterpriseadmininvitationpayload", + "/v4/object/changeuserstatuspayload": "/graphql/reference/objects#changeuserstatuspayload", + "/v4/object/checkannotation": "/graphql/reference/objects#checkannotation", + "/v4/object/checkannotationconnection": "/graphql/reference/objects#checkannotationconnection", + "/v4/object/checkannotationedge": "/graphql/reference/objects#checkannotationedge", + "/v4/object/checkannotationposition": "/graphql/reference/objects#checkannotationposition", + "/v4/object/checkannotationspan": "/graphql/reference/objects#checkannotationspan", + "/v4/object/checkrun": "/graphql/reference/objects#checkrun", + "/v4/object/checkrunconnection": "/graphql/reference/objects#checkrunconnection", + "/v4/object/checkrunedge": "/graphql/reference/objects#checkrunedge", + "/v4/object/checksuite": "/graphql/reference/objects#checksuite", + "/v4/object/checksuiteconnection": "/graphql/reference/objects#checksuiteconnection", + "/v4/object/checksuiteedge": "/graphql/reference/objects#checksuiteedge", + "/v4/object/clearlabelsfromlabelablepayload": "/graphql/reference/objects#clearlabelsfromlabelablepayload", + "/v4/object/cloneprojectpayload": "/graphql/reference/objects#cloneprojectpayload", + "/v4/object/clonetemplaterepositorypayload": "/graphql/reference/objects#clonetemplaterepositorypayload", + "/v4/object/closedevent": "/graphql/reference/objects#closedevent", + "/v4/object/closeissuepayload": "/graphql/reference/objects#closeissuepayload", + "/v4/object/closepullrequestpayload": "/graphql/reference/objects#closepullrequestpayload", + "/v4/object/codeofconduct": "/graphql/reference/objects#codeofconduct", + "/v4/object/commentdeletedevent": "/graphql/reference/objects#commentdeletedevent", + "/v4/object/commit": "/graphql/reference/objects#commit", + "/v4/object/commitcomment": "/graphql/reference/objects#commitcomment", + "/v4/object/commitcommentconnection": "/graphql/reference/objects#commitcommentconnection", + "/v4/object/commitcommentedge": "/graphql/reference/objects#commitcommentedge", + "/v4/object/commitcommentthread": "/graphql/reference/objects#commitcommentthread", + "/v4/object/commitconnection": "/graphql/reference/objects#commitconnection", + "/v4/object/commitcontributionsbyrepository": "/graphql/reference/objects#commitcontributionsbyrepository", + "/v4/object/commitedge": "/graphql/reference/objects#commitedge", + "/v4/object/commithistoryconnection": "/graphql/reference/objects#commithistoryconnection", + "/v4/object/connectedevent": "/graphql/reference/objects#connectedevent", + "/v4/object/contentattachment": "/graphql/reference/objects#contentattachment", + "/v4/object/contentreference": "/graphql/reference/objects#contentreference", + "/v4/object/contributioncalendar": "/graphql/reference/objects#contributioncalendar", + "/v4/object/contributioncalendarday": "/graphql/reference/objects#contributioncalendarday", + "/v4/object/contributioncalendarmonth": "/graphql/reference/objects#contributioncalendarmonth", + "/v4/object/contributioncalendarweek": "/graphql/reference/objects#contributioncalendarweek", + "/v4/object/contributionscollection": "/graphql/reference/objects#contributionscollection", + "/v4/object/convertednotetoissueevent": "/graphql/reference/objects#convertednotetoissueevent", + "/v4/object/convertprojectcardnotetoissuepayload": "/graphql/reference/objects#convertprojectcardnotetoissuepayload", + "/v4/object/converttodraftevent": "/graphql/reference/objects#converttodraftevent", + "/v4/object/createbranchprotectionrulepayload": "/graphql/reference/objects#createbranchprotectionrulepayload", + "/v4/object/createcheckrunpayload": "/graphql/reference/objects#createcheckrunpayload", + "/v4/object/createchecksuitepayload": "/graphql/reference/objects#createchecksuitepayload", + "/v4/object/createcontentattachmentpayload": "/graphql/reference/objects#createcontentattachmentpayload", + "/v4/object/createdcommitcontribution": "/graphql/reference/objects#createdcommitcontribution", + "/v4/object/createdcommitcontributionconnection": "/graphql/reference/objects#createdcommitcontributionconnection", + "/v4/object/createdcommitcontributionedge": "/graphql/reference/objects#createdcommitcontributionedge", + "/v4/object/createdeploymentpayload": "/graphql/reference/objects#createdeploymentpayload", + "/v4/object/createdeploymentstatuspayload": "/graphql/reference/objects#createdeploymentstatuspayload", + "/v4/object/createdissuecontribution": "/graphql/reference/objects#createdissuecontribution", + "/v4/object/createdissuecontributionconnection": "/graphql/reference/objects#createdissuecontributionconnection", + "/v4/object/createdissuecontributionedge": "/graphql/reference/objects#createdissuecontributionedge", + "/v4/object/createdpullrequestcontribution": "/graphql/reference/objects#createdpullrequestcontribution", + "/v4/object/createdpullrequestcontributionconnection": "/graphql/reference/objects#createdpullrequestcontributionconnection", + "/v4/object/createdpullrequestcontributionedge": "/graphql/reference/objects#createdpullrequestcontributionedge", + "/v4/object/createdpullrequestreviewcontribution": "/graphql/reference/objects#createdpullrequestreviewcontribution", + "/v4/object/createdpullrequestreviewcontributionconnection": "/graphql/reference/objects#createdpullrequestreviewcontributionconnection", + "/v4/object/createdpullrequestreviewcontributionedge": "/graphql/reference/objects#createdpullrequestreviewcontributionedge", + "/v4/object/createdrepositorycontribution": "/graphql/reference/objects#createdrepositorycontribution", + "/v4/object/createdrepositorycontributionconnection": "/graphql/reference/objects#createdrepositorycontributionconnection", + "/v4/object/createdrepositorycontributionedge": "/graphql/reference/objects#createdrepositorycontributionedge", + "/v4/object/createenterpriseorganizationpayload": "/graphql/reference/objects#createenterpriseorganizationpayload", + "/v4/object/createipallowlistentrypayload": "/graphql/reference/objects#createipallowlistentrypayload", + "/v4/object/createissuepayload": "/graphql/reference/objects#createissuepayload", + "/v4/object/createlabelpayload": "/graphql/reference/objects#createlabelpayload", + "/v4/object/createprojectpayload": "/graphql/reference/objects#createprojectpayload", + "/v4/object/createpullrequestpayload": "/graphql/reference/objects#createpullrequestpayload", + "/v4/object/createrefpayload": "/graphql/reference/objects#createrefpayload", + "/v4/object/createrepositorypayload": "/graphql/reference/objects#createrepositorypayload", + "/v4/object/createteamdiscussioncommentpayload": "/graphql/reference/objects#createteamdiscussioncommentpayload", + "/v4/object/createteamdiscussionpayload": "/graphql/reference/objects#createteamdiscussionpayload", + "/v4/object/crossreferencedevent": "/graphql/reference/objects#crossreferencedevent", + "/v4/object/declinetopicsuggestionpayload": "/graphql/reference/objects#declinetopicsuggestionpayload", + "/v4/object/deletebranchprotectionrulepayload": "/graphql/reference/objects#deletebranchprotectionrulepayload", + "/v4/object/deletedeploymentpayload": "/graphql/reference/objects#deletedeploymentpayload", + "/v4/object/deleteipallowlistentrypayload": "/graphql/reference/objects#deleteipallowlistentrypayload", + "/v4/object/deleteissuecommentpayload": "/graphql/reference/objects#deleteissuecommentpayload", + "/v4/object/deleteissuepayload": "/graphql/reference/objects#deleteissuepayload", + "/v4/object/deletelabelpayload": "/graphql/reference/objects#deletelabelpayload", + "/v4/object/deletepackageversionpayload": "/graphql/reference/objects#deletepackageversionpayload", + "/v4/object/deleteprojectcardpayload": "/graphql/reference/objects#deleteprojectcardpayload", + "/v4/object/deleteprojectcolumnpayload": "/graphql/reference/objects#deleteprojectcolumnpayload", + "/v4/object/deleteprojectpayload": "/graphql/reference/objects#deleteprojectpayload", + "/v4/object/deletepullrequestreviewcommentpayload": "/graphql/reference/objects#deletepullrequestreviewcommentpayload", + "/v4/object/deletepullrequestreviewpayload": "/graphql/reference/objects#deletepullrequestreviewpayload", + "/v4/object/deleterefpayload": "/graphql/reference/objects#deleterefpayload", + "/v4/object/deleteteamdiscussioncommentpayload": "/graphql/reference/objects#deleteteamdiscussioncommentpayload", + "/v4/object/deleteteamdiscussionpayload": "/graphql/reference/objects#deleteteamdiscussionpayload", + "/v4/object/demilestonedevent": "/graphql/reference/objects#demilestonedevent", + "/v4/object/dependencygraphdependency": "/graphql/reference/objects#dependencygraphdependency", + "/v4/object/dependencygraphdependencyconnection": "/graphql/reference/objects#dependencygraphdependencyconnection", + "/v4/object/dependencygraphdependencyedge": "/graphql/reference/objects#dependencygraphdependencyedge", + "/v4/object/dependencygraphmanifest": "/graphql/reference/objects#dependencygraphmanifest", + "/v4/object/dependencygraphmanifestconnection": "/graphql/reference/objects#dependencygraphmanifestconnection", + "/v4/object/dependencygraphmanifestedge": "/graphql/reference/objects#dependencygraphmanifestedge", + "/v4/object/deployedevent": "/graphql/reference/objects#deployedevent", + "/v4/object/deploykey": "/graphql/reference/objects#deploykey", + "/v4/object/deploykeyconnection": "/graphql/reference/objects#deploykeyconnection", + "/v4/object/deploykeyedge": "/graphql/reference/objects#deploykeyedge", + "/v4/object/deployment": "/graphql/reference/objects#deployment", + "/v4/object/deploymentconnection": "/graphql/reference/objects#deploymentconnection", + "/v4/object/deploymentedge": "/graphql/reference/objects#deploymentedge", + "/v4/object/deploymentenvironmentchangedevent": "/graphql/reference/objects#deploymentenvironmentchangedevent", + "/v4/object/deploymentstatus": "/graphql/reference/objects#deploymentstatus", + "/v4/object/deploymentstatusconnection": "/graphql/reference/objects#deploymentstatusconnection", + "/v4/object/deploymentstatusedge": "/graphql/reference/objects#deploymentstatusedge", + "/v4/object/disconnectedevent": "/graphql/reference/objects#disconnectedevent", + "/v4/object/dismisspullrequestreviewpayload": "/graphql/reference/objects#dismisspullrequestreviewpayload", + "/v4/object/enterprise": "/graphql/reference/objects#enterprise", + "/v4/object/enterpriseadministratorconnection": "/graphql/reference/objects#enterpriseadministratorconnection", + "/v4/object/enterpriseadministratoredge": "/graphql/reference/objects#enterpriseadministratoredge", + "/v4/object/enterpriseadministratorinvitation": "/graphql/reference/objects#enterpriseadministratorinvitation", + "/v4/object/enterpriseadministratorinvitationconnection": "/graphql/reference/objects#enterpriseadministratorinvitationconnection", + "/v4/object/enterpriseadministratorinvitationedge": "/graphql/reference/objects#enterpriseadministratorinvitationedge", + "/v4/object/enterprisebillinginfo": "/graphql/reference/objects#enterprisebillinginfo", + "/v4/object/enterpriseidentityprovider": "/graphql/reference/objects#enterpriseidentityprovider", + "/v4/object/enterprisememberconnection": "/graphql/reference/objects#enterprisememberconnection", + "/v4/object/enterprisememberedge": "/graphql/reference/objects#enterprisememberedge", + "/v4/object/enterpriseorganizationmembershipconnection": "/graphql/reference/objects#enterpriseorganizationmembershipconnection", + "/v4/object/enterpriseorganizationmembershipedge": "/graphql/reference/objects#enterpriseorganizationmembershipedge", + "/v4/object/enterpriseoutsidecollaboratorconnection": "/graphql/reference/objects#enterpriseoutsidecollaboratorconnection", + "/v4/object/enterpriseoutsidecollaboratoredge": "/graphql/reference/objects#enterpriseoutsidecollaboratoredge", + "/v4/object/enterpriseownerinfo": "/graphql/reference/objects#enterpriseownerinfo", + "/v4/object/enterprisependingcollaboratorconnection": "/graphql/reference/objects#enterprisependingcollaboratorconnection", + "/v4/object/enterprisependingcollaboratoredge": "/graphql/reference/objects#enterprisependingcollaboratoredge", + "/v4/object/enterprisependingmemberinvitationconnection": "/graphql/reference/objects#enterprisependingmemberinvitationconnection", + "/v4/object/enterprisependingmemberinvitationedge": "/graphql/reference/objects#enterprisependingmemberinvitationedge", + "/v4/object/enterpriserepositoryinfo": "/graphql/reference/objects#enterpriserepositoryinfo", + "/v4/object/enterpriserepositoryinfoconnection": "/graphql/reference/objects#enterpriserepositoryinfoconnection", + "/v4/object/enterpriserepositoryinfoedge": "/graphql/reference/objects#enterpriserepositoryinfoedge", + "/v4/object/enterpriseserverinstallation": "/graphql/reference/objects#enterpriseserverinstallation", + "/v4/object/enterpriseserverinstallationconnection": "/graphql/reference/objects#enterpriseserverinstallationconnection", + "/v4/object/enterpriseserverinstallationedge": "/graphql/reference/objects#enterpriseserverinstallationedge", + "/v4/object/enterpriseserveruseraccount": "/graphql/reference/objects#enterpriseserveruseraccount", + "/v4/object/enterpriseserveruseraccountconnection": "/graphql/reference/objects#enterpriseserveruseraccountconnection", + "/v4/object/enterpriseserveruseraccountedge": "/graphql/reference/objects#enterpriseserveruseraccountedge", + "/v4/object/enterpriseserveruseraccountemail": "/graphql/reference/objects#enterpriseserveruseraccountemail", + "/v4/object/enterpriseserveruseraccountemailconnection": "/graphql/reference/objects#enterpriseserveruseraccountemailconnection", + "/v4/object/enterpriseserveruseraccountemailedge": "/graphql/reference/objects#enterpriseserveruseraccountemailedge", + "/v4/object/enterpriseserveruseraccountsupload": "/graphql/reference/objects#enterpriseserveruseraccountsupload", + "/v4/object/enterpriseserveruseraccountsuploadconnection": "/graphql/reference/objects#enterpriseserveruseraccountsuploadconnection", + "/v4/object/enterpriseserveruseraccountsuploadedge": "/graphql/reference/objects#enterpriseserveruseraccountsuploadedge", + "/v4/object/enterpriseuseraccount": "/graphql/reference/objects#enterpriseuseraccount", + "/v4/object/enterpriseuseraccountconnection": "/graphql/reference/objects#enterpriseuseraccountconnection", + "/v4/object/enterpriseuseraccountedge": "/graphql/reference/objects#enterpriseuseraccountedge", + "/v4/object/externalidentity": "/graphql/reference/objects#externalidentity", + "/v4/object/externalidentityconnection": "/graphql/reference/objects#externalidentityconnection", + "/v4/object/externalidentityedge": "/graphql/reference/objects#externalidentityedge", + "/v4/object/externalidentitysamlattributes": "/graphql/reference/objects#externalidentitysamlattributes", + "/v4/object/externalidentityscimattributes": "/graphql/reference/objects#externalidentityscimattributes", + "/v4/object/followerconnection": "/graphql/reference/objects#followerconnection", + "/v4/object/followingconnection": "/graphql/reference/objects#followingconnection", + "/v4/object/followuserpayload": "/graphql/reference/objects#followuserpayload", + "/v4/object/fundinglink": "/graphql/reference/objects#fundinglink", + "/v4/object/generichovercardcontext": "/graphql/reference/objects#generichovercardcontext", + "/v4/object/gist": "/graphql/reference/objects#gist", + "/v4/object/gistcomment": "/graphql/reference/objects#gistcomment", + "/v4/object/gistcommentconnection": "/graphql/reference/objects#gistcommentconnection", + "/v4/object/gistcommentedge": "/graphql/reference/objects#gistcommentedge", + "/v4/object/gistconnection": "/graphql/reference/objects#gistconnection", + "/v4/object/gistedge": "/graphql/reference/objects#gistedge", + "/v4/object/gistfile": "/graphql/reference/objects#gistfile", + "/v4/object/gitactor": "/graphql/reference/objects#gitactor", + "/v4/object/githubmetadata": "/graphql/reference/objects#githubmetadata", + "/v4/object/gpgsignature": "/graphql/reference/objects#gpgsignature", + "/v4/object/headrefdeletedevent": "/graphql/reference/objects#headrefdeletedevent", + "/v4/object/headrefforcepushedevent": "/graphql/reference/objects#headrefforcepushedevent", + "/v4/object/headrefrestoredevent": "/graphql/reference/objects#headrefrestoredevent", + "/v4/object/hovercard": "/graphql/reference/objects#hovercard", + "/v4/object/importprojectpayload": "/graphql/reference/objects#importprojectpayload", + "/v4/object/inviteenterpriseadminpayload": "/graphql/reference/objects#inviteenterpriseadminpayload", + "/v4/object/ipallowlistentry": "/graphql/reference/objects#ipallowlistentry", + "/v4/object/ipallowlistentryconnection": "/graphql/reference/objects#ipallowlistentryconnection", + "/v4/object/ipallowlistentryedge": "/graphql/reference/objects#ipallowlistentryedge", + "/v4/object/issue": "/graphql/reference/objects#issue", + "/v4/object/issuecomment": "/graphql/reference/objects#issuecomment", + "/v4/object/issuecommentconnection": "/graphql/reference/objects#issuecommentconnection", + "/v4/object/issuecommentedge": "/graphql/reference/objects#issuecommentedge", + "/v4/object/issueconnection": "/graphql/reference/objects#issueconnection", + "/v4/object/issuecontributionsbyrepository": "/graphql/reference/objects#issuecontributionsbyrepository", + "/v4/object/issueedge": "/graphql/reference/objects#issueedge", + "/v4/object/issuetimelineconnection": "/graphql/reference/objects#issuetimelineconnection", + "/v4/object/issuetimelineitemedge": "/graphql/reference/objects#issuetimelineitemedge", + "/v4/object/issuetimelineitemsconnection": "/graphql/reference/objects#issuetimelineitemsconnection", + "/v4/object/issuetimelineitemsedge": "/graphql/reference/objects#issuetimelineitemsedge", + "/v4/object/joinedgithubcontribution": "/graphql/reference/objects#joinedgithubcontribution", + "/v4/object/label": "/graphql/reference/objects#label", + "/v4/object/labelconnection": "/graphql/reference/objects#labelconnection", + "/v4/object/labeledevent": "/graphql/reference/objects#labeledevent", + "/v4/object/labeledge": "/graphql/reference/objects#labeledge", + "/v4/object/language": "/graphql/reference/objects#language", + "/v4/object/languageconnection": "/graphql/reference/objects#languageconnection", + "/v4/object/languageedge": "/graphql/reference/objects#languageedge", + "/v4/object/license": "/graphql/reference/objects#license", + "/v4/object/licenserule": "/graphql/reference/objects#licenserule", + "/v4/object/linkrepositorytoprojectpayload": "/graphql/reference/objects#linkrepositorytoprojectpayload", + "/v4/object/lockedevent": "/graphql/reference/objects#lockedevent", + "/v4/object/locklockablepayload": "/graphql/reference/objects#locklockablepayload", + "/v4/object/mannequin": "/graphql/reference/objects#mannequin", + "/v4/object/markedasduplicateevent": "/graphql/reference/objects#markedasduplicateevent", + "/v4/object/marketplacecategory": "/graphql/reference/objects#marketplacecategory", + "/v4/object/marketplacelisting": "/graphql/reference/objects#marketplacelisting", + "/v4/object/marketplacelistingconnection": "/graphql/reference/objects#marketplacelistingconnection", + "/v4/object/marketplacelistingedge": "/graphql/reference/objects#marketplacelistingedge", + "/v4/object/markpullrequestreadyforreviewpayload": "/graphql/reference/objects#markpullrequestreadyforreviewpayload", + "/v4/object/memberscandeletereposclearauditentry": "/graphql/reference/objects#memberscandeletereposclearauditentry", + "/v4/object/memberscandeletereposdisableauditentry": "/graphql/reference/objects#memberscandeletereposdisableauditentry", + "/v4/object/memberscandeletereposenableauditentry": "/graphql/reference/objects#memberscandeletereposenableauditentry", + "/v4/object/mentionedevent": "/graphql/reference/objects#mentionedevent", + "/v4/object/mergebranchpayload": "/graphql/reference/objects#mergebranchpayload", + "/v4/object/mergedevent": "/graphql/reference/objects#mergedevent", + "/v4/object/mergepullrequestpayload": "/graphql/reference/objects#mergepullrequestpayload", + "/v4/object/milestone": "/graphql/reference/objects#milestone", + "/v4/object/milestoneconnection": "/graphql/reference/objects#milestoneconnection", + "/v4/object/milestonedevent": "/graphql/reference/objects#milestonedevent", + "/v4/object/milestoneedge": "/graphql/reference/objects#milestoneedge", + "/v4/object/minimizecommentpayload": "/graphql/reference/objects#minimizecommentpayload", + "/v4/object/movedcolumnsinprojectevent": "/graphql/reference/objects#movedcolumnsinprojectevent", + "/v4/object/moveprojectcardpayload": "/graphql/reference/objects#moveprojectcardpayload", + "/v4/object/moveprojectcolumnpayload": "/graphql/reference/objects#moveprojectcolumnpayload", + "/v4/object/oauthapplicationcreateauditentry": "/graphql/reference/objects#oauthapplicationcreateauditentry", + "/v4/object/orgaddbillingmanagerauditentry": "/graphql/reference/objects#orgaddbillingmanagerauditentry", + "/v4/object/orgaddmemberauditentry": "/graphql/reference/objects#orgaddmemberauditentry", + "/v4/object/organization": "/graphql/reference/objects#organization", + "/v4/object/organizationauditentryconnection": "/graphql/reference/objects#organizationauditentryconnection", + "/v4/object/organizationauditentryedge": "/graphql/reference/objects#organizationauditentryedge", + "/v4/object/organizationconnection": "/graphql/reference/objects#organizationconnection", + "/v4/object/organizationedge": "/graphql/reference/objects#organizationedge", + "/v4/object/organizationidentityprovider": "/graphql/reference/objects#organizationidentityprovider", + "/v4/object/organizationinvitation": "/graphql/reference/objects#organizationinvitation", + "/v4/object/organizationinvitationconnection": "/graphql/reference/objects#organizationinvitationconnection", + "/v4/object/organizationinvitationedge": "/graphql/reference/objects#organizationinvitationedge", + "/v4/object/organizationmemberconnection": "/graphql/reference/objects#organizationmemberconnection", + "/v4/object/organizationmemberedge": "/graphql/reference/objects#organizationmemberedge", + "/v4/object/organizationshovercardcontext": "/graphql/reference/objects#organizationshovercardcontext", + "/v4/object/organizationteamshovercardcontext": "/graphql/reference/objects#organizationteamshovercardcontext", + "/v4/object/orgblockuserauditentry": "/graphql/reference/objects#orgblockuserauditentry", + "/v4/object/orgconfigdisablecollaboratorsonlyauditentry": "/graphql/reference/objects#orgconfigdisablecollaboratorsonlyauditentry", + "/v4/object/orgconfigenablecollaboratorsonlyauditentry": "/graphql/reference/objects#orgconfigenablecollaboratorsonlyauditentry", + "/v4/object/orgcreateauditentry": "/graphql/reference/objects#orgcreateauditentry", + "/v4/object/orgdisableoauthapprestrictionsauditentry": "/graphql/reference/objects#orgdisableoauthapprestrictionsauditentry", + "/v4/object/orgdisablesamlauditentry": "/graphql/reference/objects#orgdisablesamlauditentry", + "/v4/object/orgdisabletwofactorrequirementauditentry": "/graphql/reference/objects#orgdisabletwofactorrequirementauditentry", + "/v4/object/orgenableoauthapprestrictionsauditentry": "/graphql/reference/objects#orgenableoauthapprestrictionsauditentry", + "/v4/object/orgenablesamlauditentry": "/graphql/reference/objects#orgenablesamlauditentry", + "/v4/object/orgenabletwofactorrequirementauditentry": "/graphql/reference/objects#orgenabletwofactorrequirementauditentry", + "/v4/object/orginvitememberauditentry": "/graphql/reference/objects#orginvitememberauditentry", + "/v4/object/orginvitetobusinessauditentry": "/graphql/reference/objects#orginvitetobusinessauditentry", + "/v4/object/orgoauthappaccessapprovedauditentry": "/graphql/reference/objects#orgoauthappaccessapprovedauditentry", + "/v4/object/orgoauthappaccessdeniedauditentry": "/graphql/reference/objects#orgoauthappaccessdeniedauditentry", + "/v4/object/orgoauthappaccessrequestedauditentry": "/graphql/reference/objects#orgoauthappaccessrequestedauditentry", + "/v4/object/orgremovebillingmanagerauditentry": "/graphql/reference/objects#orgremovebillingmanagerauditentry", + "/v4/object/orgremovememberauditentry": "/graphql/reference/objects#orgremovememberauditentry", + "/v4/object/orgremoveoutsidecollaboratorauditentry": "/graphql/reference/objects#orgremoveoutsidecollaboratorauditentry", + "/v4/object/orgrestorememberauditentry": "/graphql/reference/objects#orgrestorememberauditentry", + "/v4/object/orgrestoremembermembershiporganizationauditentrydata": "/graphql/reference/objects#orgrestoremembermembershiporganizationauditentrydata", + "/v4/object/orgrestoremembermembershiprepositoryauditentrydata": "/graphql/reference/objects#orgrestoremembermembershiprepositoryauditentrydata", + "/v4/object/orgrestoremembermembershipteamauditentrydata": "/graphql/reference/objects#orgrestoremembermembershipteamauditentrydata", + "/v4/object/orgunblockuserauditentry": "/graphql/reference/objects#orgunblockuserauditentry", + "/v4/object/orgupdatedefaultrepositorypermissionauditentry": "/graphql/reference/objects#orgupdatedefaultrepositorypermissionauditentry", + "/v4/object/orgupdatememberauditentry": "/graphql/reference/objects#orgupdatememberauditentry", + "/v4/object/orgupdatememberrepositorycreationpermissionauditentry": "/graphql/reference/objects#orgupdatememberrepositorycreationpermissionauditentry", + "/v4/object/orgupdatememberrepositoryinvitationpermissionauditentry": "/graphql/reference/objects#orgupdatememberrepositoryinvitationpermissionauditentry", + "/v4/object/package": "/graphql/reference/objects#package", + "/v4/object/packageconnection": "/graphql/reference/objects#packageconnection", + "/v4/object/packageedge": "/graphql/reference/objects#packageedge", + "/v4/object/packagefile": "/graphql/reference/objects#packagefile", + "/v4/object/packagefileconnection": "/graphql/reference/objects#packagefileconnection", + "/v4/object/packagefileedge": "/graphql/reference/objects#packagefileedge", + "/v4/object/packagestatistics": "/graphql/reference/objects#packagestatistics", + "/v4/object/packagetag": "/graphql/reference/objects#packagetag", + "/v4/object/packageversion": "/graphql/reference/objects#packageversion", + "/v4/object/packageversionconnection": "/graphql/reference/objects#packageversionconnection", + "/v4/object/packageversionedge": "/graphql/reference/objects#packageversionedge", + "/v4/object/packageversionstatistics": "/graphql/reference/objects#packageversionstatistics", + "/v4/object/pageinfo": "/graphql/reference/objects#pageinfo", + "/v4/object/permissionsource": "/graphql/reference/objects#permissionsource", + "/v4/object/pinissuepayload": "/graphql/reference/objects#pinissuepayload", + "/v4/object/pinnableitemconnection": "/graphql/reference/objects#pinnableitemconnection", + "/v4/object/pinnableitemedge": "/graphql/reference/objects#pinnableitemedge", + "/v4/object/pinnedevent": "/graphql/reference/objects#pinnedevent", + "/v4/object/pinnedissue": "/graphql/reference/objects#pinnedissue", + "/v4/object/pinnedissueconnection": "/graphql/reference/objects#pinnedissueconnection", + "/v4/object/pinnedissueedge": "/graphql/reference/objects#pinnedissueedge", + "/v4/object/privaterepositoryforkingdisableauditentry": "/graphql/reference/objects#privaterepositoryforkingdisableauditentry", + "/v4/object/privaterepositoryforkingenableauditentry": "/graphql/reference/objects#privaterepositoryforkingenableauditentry", + "/v4/object/profileitemshowcase": "/graphql/reference/objects#profileitemshowcase", + "/v4/object/project": "/graphql/reference/objects#project", + "/v4/object/projectcard": "/graphql/reference/objects#projectcard", + "/v4/object/projectcardconnection": "/graphql/reference/objects#projectcardconnection", + "/v4/object/projectcardedge": "/graphql/reference/objects#projectcardedge", + "/v4/object/projectcolumn": "/graphql/reference/objects#projectcolumn", + "/v4/object/projectcolumnconnection": "/graphql/reference/objects#projectcolumnconnection", + "/v4/object/projectcolumnedge": "/graphql/reference/objects#projectcolumnedge", + "/v4/object/projectconnection": "/graphql/reference/objects#projectconnection", + "/v4/object/projectedge": "/graphql/reference/objects#projectedge", + "/v4/object/publickey": "/graphql/reference/objects#publickey", + "/v4/object/publickeyconnection": "/graphql/reference/objects#publickeyconnection", + "/v4/object/publickeyedge": "/graphql/reference/objects#publickeyedge", + "/v4/object/pullrequest": "/graphql/reference/objects#pullrequest", + "/v4/object/pullrequestchangedfile": "/graphql/reference/objects#pullrequestchangedfile", + "/v4/object/pullrequestchangedfileconnection": "/graphql/reference/objects#pullrequestchangedfileconnection", + "/v4/object/pullrequestchangedfileedge": "/graphql/reference/objects#pullrequestchangedfileedge", + "/v4/object/pullrequestcommit": "/graphql/reference/objects#pullrequestcommit", + "/v4/object/pullrequestcommitcommentthread": "/graphql/reference/objects#pullrequestcommitcommentthread", + "/v4/object/pullrequestcommitconnection": "/graphql/reference/objects#pullrequestcommitconnection", + "/v4/object/pullrequestcommitedge": "/graphql/reference/objects#pullrequestcommitedge", + "/v4/object/pullrequestconnection": "/graphql/reference/objects#pullrequestconnection", + "/v4/object/pullrequestcontributionsbyrepository": "/graphql/reference/objects#pullrequestcontributionsbyrepository", + "/v4/object/pullrequestedge": "/graphql/reference/objects#pullrequestedge", + "/v4/object/pullrequestreview": "/graphql/reference/objects#pullrequestreview", + "/v4/object/pullrequestreviewcomment": "/graphql/reference/objects#pullrequestreviewcomment", + "/v4/object/pullrequestreviewcommentconnection": "/graphql/reference/objects#pullrequestreviewcommentconnection", + "/v4/object/pullrequestreviewcommentedge": "/graphql/reference/objects#pullrequestreviewcommentedge", + "/v4/object/pullrequestreviewconnection": "/graphql/reference/objects#pullrequestreviewconnection", + "/v4/object/pullrequestreviewcontributionsbyrepository": "/graphql/reference/objects#pullrequestreviewcontributionsbyrepository", + "/v4/object/pullrequestreviewedge": "/graphql/reference/objects#pullrequestreviewedge", + "/v4/object/pullrequestreviewthread": "/graphql/reference/objects#pullrequestreviewthread", + "/v4/object/pullrequestreviewthreadconnection": "/graphql/reference/objects#pullrequestreviewthreadconnection", + "/v4/object/pullrequestreviewthreadedge": "/graphql/reference/objects#pullrequestreviewthreadedge", + "/v4/object/pullrequestrevisionmarker": "/graphql/reference/objects#pullrequestrevisionmarker", + "/v4/object/pullrequesttimelineconnection": "/graphql/reference/objects#pullrequesttimelineconnection", + "/v4/object/pullrequesttimelineitemedge": "/graphql/reference/objects#pullrequesttimelineitemedge", + "/v4/object/pullrequesttimelineitemsconnection": "/graphql/reference/objects#pullrequesttimelineitemsconnection", + "/v4/object/pullrequesttimelineitemsedge": "/graphql/reference/objects#pullrequesttimelineitemsedge", + "/v4/object/push": "/graphql/reference/objects#push", + "/v4/object/pushallowance": "/graphql/reference/objects#pushallowance", + "/v4/object/pushallowanceconnection": "/graphql/reference/objects#pushallowanceconnection", + "/v4/object/pushallowanceedge": "/graphql/reference/objects#pushallowanceedge", + "/v4/object/ratelimit": "/graphql/reference/objects#ratelimit", + "/v4/object/reactinguserconnection": "/graphql/reference/objects#reactinguserconnection", + "/v4/object/reactinguseredge": "/graphql/reference/objects#reactinguseredge", + "/v4/object/reaction": "/graphql/reference/objects#reaction", + "/v4/object/reactionconnection": "/graphql/reference/objects#reactionconnection", + "/v4/object/reactionedge": "/graphql/reference/objects#reactionedge", + "/v4/object/reactiongroup": "/graphql/reference/objects#reactiongroup", + "/v4/object/readyforreviewevent": "/graphql/reference/objects#readyforreviewevent", + "/v4/object/ref": "/graphql/reference/objects#ref", + "/v4/object/refconnection": "/graphql/reference/objects#refconnection", + "/v4/object/refedge": "/graphql/reference/objects#refedge", + "/v4/object/referencedevent": "/graphql/reference/objects#referencedevent", + "/v4/object/regenerateenterpriseidentityproviderrecoverycodespayload": "/graphql/reference/objects#regenerateenterpriseidentityproviderrecoverycodespayload", + "/v4/object/release": "/graphql/reference/objects#release", + "/v4/object/releaseasset": "/graphql/reference/objects#releaseasset", + "/v4/object/releaseassetconnection": "/graphql/reference/objects#releaseassetconnection", + "/v4/object/releaseassetedge": "/graphql/reference/objects#releaseassetedge", + "/v4/object/releaseconnection": "/graphql/reference/objects#releaseconnection", + "/v4/object/releaseedge": "/graphql/reference/objects#releaseedge", + "/v4/object/removeassigneesfromassignablepayload": "/graphql/reference/objects#removeassigneesfromassignablepayload", + "/v4/object/removedfromprojectevent": "/graphql/reference/objects#removedfromprojectevent", + "/v4/object/removeenterpriseadminpayload": "/graphql/reference/objects#removeenterpriseadminpayload", + "/v4/object/removeenterpriseidentityproviderpayload": "/graphql/reference/objects#removeenterpriseidentityproviderpayload", + "/v4/object/removeenterpriseorganizationpayload": "/graphql/reference/objects#removeenterpriseorganizationpayload", + "/v4/object/removelabelsfromlabelablepayload": "/graphql/reference/objects#removelabelsfromlabelablepayload", + "/v4/object/removeoutsidecollaboratorpayload": "/graphql/reference/objects#removeoutsidecollaboratorpayload", + "/v4/object/removereactionpayload": "/graphql/reference/objects#removereactionpayload", + "/v4/object/removestarpayload": "/graphql/reference/objects#removestarpayload", + "/v4/object/renamedtitleevent": "/graphql/reference/objects#renamedtitleevent", + "/v4/object/reopenedevent": "/graphql/reference/objects#reopenedevent", + "/v4/object/reopenissuepayload": "/graphql/reference/objects#reopenissuepayload", + "/v4/object/reopenpullrequestpayload": "/graphql/reference/objects#reopenpullrequestpayload", + "/v4/object/repoaccessauditentry": "/graphql/reference/objects#repoaccessauditentry", + "/v4/object/repoaddmemberauditentry": "/graphql/reference/objects#repoaddmemberauditentry", + "/v4/object/repoaddtopicauditentry": "/graphql/reference/objects#repoaddtopicauditentry", + "/v4/object/repoarchivedauditentry": "/graphql/reference/objects#repoarchivedauditentry", + "/v4/object/repochangemergesettingauditentry": "/graphql/reference/objects#repochangemergesettingauditentry", + "/v4/object/repoconfigdisableanonymousgitaccessauditentry": "/graphql/reference/objects#repoconfigdisableanonymousgitaccessauditentry", + "/v4/object/repoconfigdisablecollaboratorsonlyauditentry": "/graphql/reference/objects#repoconfigdisablecollaboratorsonlyauditentry", + "/v4/object/repoconfigdisablecontributorsonlyauditentry": "/graphql/reference/objects#repoconfigdisablecontributorsonlyauditentry", + "/v4/object/repoconfigdisablesockpuppetdisallowedauditentry": "/graphql/reference/objects#repoconfigdisablesockpuppetdisallowedauditentry", + "/v4/object/repoconfigenableanonymousgitaccessauditentry": "/graphql/reference/objects#repoconfigenableanonymousgitaccessauditentry", + "/v4/object/repoconfigenablecollaboratorsonlyauditentry": "/graphql/reference/objects#repoconfigenablecollaboratorsonlyauditentry", + "/v4/object/repoconfigenablecontributorsonlyauditentry": "/graphql/reference/objects#repoconfigenablecontributorsonlyauditentry", + "/v4/object/repoconfigenablesockpuppetdisallowedauditentry": "/graphql/reference/objects#repoconfigenablesockpuppetdisallowedauditentry", + "/v4/object/repoconfiglockanonymousgitaccessauditentry": "/graphql/reference/objects#repoconfiglockanonymousgitaccessauditentry", + "/v4/object/repoconfigunlockanonymousgitaccessauditentry": "/graphql/reference/objects#repoconfigunlockanonymousgitaccessauditentry", + "/v4/object/repocreateauditentry": "/graphql/reference/objects#repocreateauditentry", + "/v4/object/repodestroyauditentry": "/graphql/reference/objects#repodestroyauditentry", + "/v4/object/reporemovememberauditentry": "/graphql/reference/objects#reporemovememberauditentry", + "/v4/object/reporemovetopicauditentry": "/graphql/reference/objects#reporemovetopicauditentry", + "/v4/object/repository": "/graphql/reference/objects#repository", + "/v4/object/repositorycollaboratorconnection": "/graphql/reference/objects#repositorycollaboratorconnection", + "/v4/object/repositorycollaboratoredge": "/graphql/reference/objects#repositorycollaboratoredge", + "/v4/object/repositoryconnection": "/graphql/reference/objects#repositoryconnection", + "/v4/object/repositoryedge": "/graphql/reference/objects#repositoryedge", + "/v4/object/repositoryinvitation": "/graphql/reference/objects#repositoryinvitation", + "/v4/object/repositoryinvitationconnection": "/graphql/reference/objects#repositoryinvitationconnection", + "/v4/object/repositoryinvitationedge": "/graphql/reference/objects#repositoryinvitationedge", + "/v4/object/repositorytopic": "/graphql/reference/objects#repositorytopic", + "/v4/object/repositorytopicconnection": "/graphql/reference/objects#repositorytopicconnection", + "/v4/object/repositorytopicedge": "/graphql/reference/objects#repositorytopicedge", + "/v4/object/repositoryvisibilitychangedisableauditentry": "/graphql/reference/objects#repositoryvisibilitychangedisableauditentry", + "/v4/object/repositoryvisibilitychangeenableauditentry": "/graphql/reference/objects#repositoryvisibilitychangeenableauditentry", + "/v4/object/repositoryvulnerabilityalert": "/graphql/reference/objects#repositoryvulnerabilityalert", + "/v4/object/repositoryvulnerabilityalertconnection": "/graphql/reference/objects#repositoryvulnerabilityalertconnection", + "/v4/object/repositoryvulnerabilityalertedge": "/graphql/reference/objects#repositoryvulnerabilityalertedge", + "/v4/object/requestreviewspayload": "/graphql/reference/objects#requestreviewspayload", + "/v4/object/rerequestchecksuitepayload": "/graphql/reference/objects#rerequestchecksuitepayload", + "/v4/object/resolvereviewthreadpayload": "/graphql/reference/objects#resolvereviewthreadpayload", + "/v4/object/restrictedcontribution": "/graphql/reference/objects#restrictedcontribution", + "/v4/object/reviewdismissalallowance": "/graphql/reference/objects#reviewdismissalallowance", + "/v4/object/reviewdismissalallowanceconnection": "/graphql/reference/objects#reviewdismissalallowanceconnection", + "/v4/object/reviewdismissalallowanceedge": "/graphql/reference/objects#reviewdismissalallowanceedge", + "/v4/object/reviewdismissedevent": "/graphql/reference/objects#reviewdismissedevent", + "/v4/object/reviewrequest": "/graphql/reference/objects#reviewrequest", + "/v4/object/reviewrequestconnection": "/graphql/reference/objects#reviewrequestconnection", + "/v4/object/reviewrequestedevent": "/graphql/reference/objects#reviewrequestedevent", + "/v4/object/reviewrequestedge": "/graphql/reference/objects#reviewrequestedge", + "/v4/object/reviewrequestremovedevent": "/graphql/reference/objects#reviewrequestremovedevent", + "/v4/object/reviewstatushovercardcontext": "/graphql/reference/objects#reviewstatushovercardcontext", + "/v4/object/savedreply": "/graphql/reference/objects#savedreply", + "/v4/object/savedreplyconnection": "/graphql/reference/objects#savedreplyconnection", + "/v4/object/savedreplyedge": "/graphql/reference/objects#savedreplyedge", + "/v4/object/searchresultitemconnection": "/graphql/reference/objects#searchresultitemconnection", + "/v4/object/searchresultitemedge": "/graphql/reference/objects#searchresultitemedge", + "/v4/object/securityadvisory": "/graphql/reference/objects#securityadvisory", + "/v4/object/securityadvisoryconnection": "/graphql/reference/objects#securityadvisoryconnection", + "/v4/object/securityadvisoryedge": "/graphql/reference/objects#securityadvisoryedge", + "/v4/object/securityadvisoryidentifier": "/graphql/reference/objects#securityadvisoryidentifier", + "/v4/object/securityadvisorypackage": "/graphql/reference/objects#securityadvisorypackage", + "/v4/object/securityadvisorypackageversion": "/graphql/reference/objects#securityadvisorypackageversion", + "/v4/object/securityadvisoryreference": "/graphql/reference/objects#securityadvisoryreference", + "/v4/object/securityvulnerability": "/graphql/reference/objects#securityvulnerability", + "/v4/object/securityvulnerabilityconnection": "/graphql/reference/objects#securityvulnerabilityconnection", + "/v4/object/securityvulnerabilityedge": "/graphql/reference/objects#securityvulnerabilityedge", + "/v4/object/setenterpriseidentityproviderpayload": "/graphql/reference/objects#setenterpriseidentityproviderpayload", + "/v4/object/smimesignature": "/graphql/reference/objects#smimesignature", + "/v4/object/sponsorship": "/graphql/reference/objects#sponsorship", + "/v4/object/sponsorshipconnection": "/graphql/reference/objects#sponsorshipconnection", + "/v4/object/sponsorshipedge": "/graphql/reference/objects#sponsorshipedge", + "/v4/object/sponsorslisting": "/graphql/reference/objects#sponsorslisting", + "/v4/object/sponsorstier": "/graphql/reference/objects#sponsorstier", + "/v4/object/sponsorstieradmininfo": "/graphql/reference/objects#sponsorstieradmininfo", + "/v4/object/sponsorstierconnection": "/graphql/reference/objects#sponsorstierconnection", + "/v4/object/sponsorstieredge": "/graphql/reference/objects#sponsorstieredge", + "/v4/object/stargazerconnection": "/graphql/reference/objects#stargazerconnection", + "/v4/object/stargazeredge": "/graphql/reference/objects#stargazeredge", + "/v4/object/starredrepositoryconnection": "/graphql/reference/objects#starredrepositoryconnection", + "/v4/object/starredrepositoryedge": "/graphql/reference/objects#starredrepositoryedge", + "/v4/object/status": "/graphql/reference/objects#status", + "/v4/object/statuscheckrollup": "/graphql/reference/objects#statuscheckrollup", + "/v4/object/statuscheckrollupcontextconnection": "/graphql/reference/objects#statuscheckrollupcontextconnection", + "/v4/object/statuscheckrollupcontextedge": "/graphql/reference/objects#statuscheckrollupcontextedge", + "/v4/object/statuscontext": "/graphql/reference/objects#statuscontext", + "/v4/object/submitpullrequestreviewpayload": "/graphql/reference/objects#submitpullrequestreviewpayload", + "/v4/object/submodule": "/graphql/reference/objects#submodule", + "/v4/object/submoduleconnection": "/graphql/reference/objects#submoduleconnection", + "/v4/object/submoduleedge": "/graphql/reference/objects#submoduleedge", + "/v4/object/subscribedevent": "/graphql/reference/objects#subscribedevent", + "/v4/object/suggestedreviewer": "/graphql/reference/objects#suggestedreviewer", + "/v4/object/tag": "/graphql/reference/objects#tag", + "/v4/object/team": "/graphql/reference/objects#team", + "/v4/object/teamaddmemberauditentry": "/graphql/reference/objects#teamaddmemberauditentry", + "/v4/object/teamaddrepositoryauditentry": "/graphql/reference/objects#teamaddrepositoryauditentry", + "/v4/object/teamchangeparentteamauditentry": "/graphql/reference/objects#teamchangeparentteamauditentry", + "/v4/object/teamconnection": "/graphql/reference/objects#teamconnection", + "/v4/object/teamdiscussion": "/graphql/reference/objects#teamdiscussion", + "/v4/object/teamdiscussioncomment": "/graphql/reference/objects#teamdiscussioncomment", + "/v4/object/teamdiscussioncommentconnection": "/graphql/reference/objects#teamdiscussioncommentconnection", + "/v4/object/teamdiscussioncommentedge": "/graphql/reference/objects#teamdiscussioncommentedge", + "/v4/object/teamdiscussionconnection": "/graphql/reference/objects#teamdiscussionconnection", + "/v4/object/teamdiscussionedge": "/graphql/reference/objects#teamdiscussionedge", + "/v4/object/teamedge": "/graphql/reference/objects#teamedge", + "/v4/object/teammemberconnection": "/graphql/reference/objects#teammemberconnection", + "/v4/object/teammemberedge": "/graphql/reference/objects#teammemberedge", + "/v4/object/teamremovememberauditentry": "/graphql/reference/objects#teamremovememberauditentry", + "/v4/object/teamremoverepositoryauditentry": "/graphql/reference/objects#teamremoverepositoryauditentry", + "/v4/object/teamrepositoryconnection": "/graphql/reference/objects#teamrepositoryconnection", + "/v4/object/teamrepositoryedge": "/graphql/reference/objects#teamrepositoryedge", + "/v4/object/textmatch": "/graphql/reference/objects#textmatch", + "/v4/object/textmatchhighlight": "/graphql/reference/objects#textmatchhighlight", + "/v4/object/topic": "/graphql/reference/objects#topic", + "/v4/object/transferissuepayload": "/graphql/reference/objects#transferissuepayload", + "/v4/object/transferredevent": "/graphql/reference/objects#transferredevent", + "/v4/object/tree": "/graphql/reference/objects#tree", + "/v4/object/treeentry": "/graphql/reference/objects#treeentry", + "/v4/object/unarchiverepositorypayload": "/graphql/reference/objects#unarchiverepositorypayload", + "/v4/object/unassignedevent": "/graphql/reference/objects#unassignedevent", + "/v4/object/unfollowuserpayload": "/graphql/reference/objects#unfollowuserpayload", + "/v4/object/unknownsignature": "/graphql/reference/objects#unknownsignature", + "/v4/object/unlabeledevent": "/graphql/reference/objects#unlabeledevent", + "/v4/object/unlinkrepositoryfromprojectpayload": "/graphql/reference/objects#unlinkrepositoryfromprojectpayload", + "/v4/object/unlockedevent": "/graphql/reference/objects#unlockedevent", + "/v4/object/unlocklockablepayload": "/graphql/reference/objects#unlocklockablepayload", + "/v4/object/unmarkedasduplicateevent": "/graphql/reference/objects#unmarkedasduplicateevent", + "/v4/object/unmarkissueasduplicatepayload": "/graphql/reference/objects#unmarkissueasduplicatepayload", + "/v4/object/unminimizecommentpayload": "/graphql/reference/objects#unminimizecommentpayload", + "/v4/object/unpinissuepayload": "/graphql/reference/objects#unpinissuepayload", + "/v4/object/unpinnedevent": "/graphql/reference/objects#unpinnedevent", + "/v4/object/unresolvereviewthreadpayload": "/graphql/reference/objects#unresolvereviewthreadpayload", + "/v4/object/unsubscribedevent": "/graphql/reference/objects#unsubscribedevent", + "/v4/object/updatebranchprotectionrulepayload": "/graphql/reference/objects#updatebranchprotectionrulepayload", + "/v4/object/updatecheckrunpayload": "/graphql/reference/objects#updatecheckrunpayload", + "/v4/object/updatechecksuitepreferencespayload": "/graphql/reference/objects#updatechecksuitepreferencespayload", + "/v4/object/updateenterpriseactionexecutioncapabilitysettingpayload": "/graphql/reference/objects#updateenterpriseactionexecutioncapabilitysettingpayload", + "/v4/object/updateenterpriseadministratorrolepayload": "/graphql/reference/objects#updateenterpriseadministratorrolepayload", + "/v4/object/updateenterpriseallowprivaterepositoryforkingsettingpayload": "/graphql/reference/objects#updateenterpriseallowprivaterepositoryforkingsettingpayload", + "/v4/object/updateenterprisedefaultrepositorypermissionsettingpayload": "/graphql/reference/objects#updateenterprisedefaultrepositorypermissionsettingpayload", + "/v4/object/updateenterprisememberscanchangerepositoryvisibilitysettingpayload": "/graphql/reference/objects#updateenterprisememberscanchangerepositoryvisibilitysettingpayload", + "/v4/object/updateenterprisememberscancreaterepositoriessettingpayload": "/graphql/reference/objects#updateenterprisememberscancreaterepositoriessettingpayload", + "/v4/object/updateenterprisememberscandeleteissuessettingpayload": "/graphql/reference/objects#updateenterprisememberscandeleteissuessettingpayload", + "/v4/object/updateenterprisememberscandeleterepositoriessettingpayload": "/graphql/reference/objects#updateenterprisememberscandeleterepositoriessettingpayload", + "/v4/object/updateenterprisememberscaninvitecollaboratorssettingpayload": "/graphql/reference/objects#updateenterprisememberscaninvitecollaboratorssettingpayload", + "/v4/object/updateenterprisememberscanmakepurchasessettingpayload": "/graphql/reference/objects#updateenterprisememberscanmakepurchasessettingpayload", + "/v4/object/updateenterprisememberscanupdateprotectedbranchessettingpayload": "/graphql/reference/objects#updateenterprisememberscanupdateprotectedbranchessettingpayload", + "/v4/object/updateenterprisememberscanviewdependencyinsightssettingpayload": "/graphql/reference/objects#updateenterprisememberscanviewdependencyinsightssettingpayload", + "/v4/object/updateenterpriseorganizationprojectssettingpayload": "/graphql/reference/objects#updateenterpriseorganizationprojectssettingpayload", + "/v4/object/updateenterpriseprofilepayload": "/graphql/reference/objects#updateenterpriseprofilepayload", + "/v4/object/updateenterpriserepositoryprojectssettingpayload": "/graphql/reference/objects#updateenterpriserepositoryprojectssettingpayload", + "/v4/object/updateenterpriseteamdiscussionssettingpayload": "/graphql/reference/objects#updateenterpriseteamdiscussionssettingpayload", + "/v4/object/updateenterprisetwofactorauthenticationrequiredsettingpayload": "/graphql/reference/objects#updateenterprisetwofactorauthenticationrequiredsettingpayload", + "/v4/object/updateipallowlistenabledsettingpayload": "/graphql/reference/objects#updateipallowlistenabledsettingpayload", + "/v4/object/updateipallowlistentrypayload": "/graphql/reference/objects#updateipallowlistentrypayload", + "/v4/object/updateissuecommentpayload": "/graphql/reference/objects#updateissuecommentpayload", + "/v4/object/updateissuepayload": "/graphql/reference/objects#updateissuepayload", + "/v4/object/updatelabelpayload": "/graphql/reference/objects#updatelabelpayload", + "/v4/object/updateprojectcardpayload": "/graphql/reference/objects#updateprojectcardpayload", + "/v4/object/updateprojectcolumnpayload": "/graphql/reference/objects#updateprojectcolumnpayload", + "/v4/object/updateprojectpayload": "/graphql/reference/objects#updateprojectpayload", + "/v4/object/updatepullrequestpayload": "/graphql/reference/objects#updatepullrequestpayload", + "/v4/object/updatepullrequestreviewcommentpayload": "/graphql/reference/objects#updatepullrequestreviewcommentpayload", + "/v4/object/updatepullrequestreviewpayload": "/graphql/reference/objects#updatepullrequestreviewpayload", + "/v4/object/updaterefpayload": "/graphql/reference/objects#updaterefpayload", + "/v4/object/updaterefspayload": "/graphql/reference/objects#updaterefspayload", + "/v4/object/updaterepositorypayload": "/graphql/reference/objects#updaterepositorypayload", + "/v4/object/updatesubscriptionpayload": "/graphql/reference/objects#updatesubscriptionpayload", + "/v4/object/updateteamdiscussioncommentpayload": "/graphql/reference/objects#updateteamdiscussioncommentpayload", + "/v4/object/updateteamdiscussionpayload": "/graphql/reference/objects#updateteamdiscussionpayload", + "/v4/object/updateteamreviewassignmentpayload": "/graphql/reference/objects#updateteamreviewassignmentpayload", + "/v4/object/updatetopicspayload": "/graphql/reference/objects#updatetopicspayload", + "/v4/object/user": "/graphql/reference/objects#user", + "/v4/object/userblockedevent": "/graphql/reference/objects#userblockedevent", + "/v4/object/userconnection": "/graphql/reference/objects#userconnection", + "/v4/object/usercontentedit": "/graphql/reference/objects#usercontentedit", + "/v4/object/usercontenteditconnection": "/graphql/reference/objects#usercontenteditconnection", + "/v4/object/usercontenteditedge": "/graphql/reference/objects#usercontenteditedge", + "/v4/object/useredge": "/graphql/reference/objects#useredge", + "/v4/object/userstatus": "/graphql/reference/objects#userstatus", + "/v4/object/userstatusconnection": "/graphql/reference/objects#userstatusconnection", + "/v4/object/userstatusedge": "/graphql/reference/objects#userstatusedge", + "/v4/object/viewerhovercardcontext": "/graphql/reference/objects#viewerhovercardcontext", + "/v4/scalar/boolean": "/graphql/reference/scalars#boolean", + "/v4/scalar/date": "/graphql/reference/scalars#date", + "/v4/scalar/datetime": "/graphql/reference/scalars#datetime", + "/v4/scalar/float": "/graphql/reference/scalars#float", + "/v4/scalar/gitobjectid": "/graphql/reference/scalars#gitobjectid", + "/v4/scalar/gitrefname": "/graphql/reference/scalars#gitrefname", + "/v4/scalar/gitsshremote": "/graphql/reference/scalars#gitsshremote", + "/v4/scalar/gittimestamp": "/graphql/reference/scalars#gittimestamp", + "/v4/scalar/html": "/graphql/reference/scalars#html", + "/v4/scalar/id": "/graphql/reference/scalars#id", + "/v4/scalar/int": "/graphql/reference/scalars#int", + "/v4/scalar/precisedatetime": "/graphql/reference/scalars#precisedatetime", + "/v4/scalar/string": "/graphql/reference/scalars#string", + "/v4/scalar/uri": "/graphql/reference/scalars#uri", + "/v4/scalar/x509certificate": "/graphql/reference/scalars#x509certificate", + "/v4/union/assignee": "/graphql/reference/unions#assignee", + "/v4/union/auditentryactor": "/graphql/reference/unions#auditentryactor", + "/v4/union/closer": "/graphql/reference/unions#closer", + "/v4/union/createdissueorrestrictedcontribution": "/graphql/reference/unions#createdissueorrestrictedcontribution", + "/v4/union/createdpullrequestorrestrictedcontribution": "/graphql/reference/unions#createdpullrequestorrestrictedcontribution", + "/v4/union/createdrepositoryorrestrictedcontribution": "/graphql/reference/unions#createdrepositoryorrestrictedcontribution", + "/v4/union/enterprisemember": "/graphql/reference/unions#enterprisemember", + "/v4/union/ipallowlistowner": "/graphql/reference/unions#ipallowlistowner", + "/v4/union/issueorpullrequest": "/graphql/reference/unions#issueorpullrequest", + "/v4/union/issuetimelineitem": "/graphql/reference/unions#issuetimelineitem", + "/v4/union/issuetimelineitems": "/graphql/reference/unions#issuetimelineitems", + "/v4/union/milestoneitem": "/graphql/reference/unions#milestoneitem", + "/v4/union/organizationauditentry": "/graphql/reference/unions#organizationauditentry", + "/v4/union/orgrestorememberauditentrymembership": "/graphql/reference/unions#orgrestorememberauditentrymembership", + "/v4/union/permissiongranter": "/graphql/reference/unions#permissiongranter", + "/v4/union/pinnableitem": "/graphql/reference/unions#pinnableitem", + "/v4/union/projectcarditem": "/graphql/reference/unions#projectcarditem", + "/v4/union/pullrequesttimelineitem": "/graphql/reference/unions#pullrequesttimelineitem", + "/v4/union/pullrequesttimelineitems": "/graphql/reference/unions#pullrequesttimelineitems", + "/v4/union/pushallowanceactor": "/graphql/reference/unions#pushallowanceactor", + "/v4/union/referencedsubject": "/graphql/reference/unions#referencedsubject", + "/v4/union/renamedtitlesubject": "/graphql/reference/unions#renamedtitlesubject", + "/v4/union/requestedreviewer": "/graphql/reference/unions#requestedreviewer", + "/v4/union/reviewdismissalallowanceactor": "/graphql/reference/unions#reviewdismissalallowanceactor", + "/v4/union/searchresultitem": "/graphql/reference/unions#searchresultitem", + "/v4/union/sponsor": "/graphql/reference/unions#sponsor", + "/v4/union/statuscheckrollupcontext": "/graphql/reference/unions#statuscheckrollupcontext" } diff --git a/lib/render-content/plugins/rewrite-local-links.js b/lib/render-content/plugins/rewrite-local-links.js index b3c9e9859c..b2b6fe2a5d 100644 --- a/lib/render-content/plugins/rewrite-local-links.js +++ b/lib/render-content/plugins/rewrite-local-links.js @@ -8,8 +8,8 @@ import nonEnterpriseDefaultVersion from '../../non-enterprise-default-version.js import { allVersions } from '../../all-versions.js' import removeFPTFromPath from '../../remove-fpt-from-path.js' import readJsonFile from '../../read-json-file.js' -const supportedVersions = Object.keys(allVersions) -const supportedPlans = Object.values(allVersions).map((v) => v.plan) + +const supportedPlans = new Set(Object.values(allVersions).map((v) => v.plan)) const externalRedirects = readJsonFile('./lib/redirects/external-sites.json') // Matches any tags with an href that starts with `/` @@ -36,18 +36,6 @@ export default function rewriteLocalLinks({ languageCode, version }) { } } -// The versions that some links might start with, which we need to know -// because if it's the case, we inject the language into the link as -// the first prefix. -// E.g. It can turn `/enterprise-cloud@latest/foo` -// into `/en/enterprise-cloud@latest/foo`. -// Using a Set to turn any lookups on this into a O(1) operation. -const allSupportedVersionsPrefixes = new Set([ - ...supportedPlans, - ...supportedVersions, - 'enterprise-server@latest', -]) - function getNewHref(node, languageCode, version) { const { href } = node.properties // Exceptions to link rewriting @@ -62,7 +50,7 @@ function getNewHref(node, languageCode, version) { // /enterprise-server/rest/reference/oauth-authorizations (this redirects to the latest version) // /enterprise-server@latest/rest/reference/oauth-authorizations (this redirects to the latest version) const firstLinkSegment = href.split('/')[1] - if (allSupportedVersionsPrefixes.has(firstLinkSegment)) { + if (supportedPlans.has(firstLinkSegment.split('@')[0])) { newHref = path.posix.join('/', languageCode, href) } diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index 16403520cd..3cfcfdb339 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -5244,7 +5244,7 @@ } ], "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -5264,7 +5264,7 @@ "categoryLabel": "Apps", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", + "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -5409,7 +5409,7 @@ } ], "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub will discontinue the [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub will discontinue the [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -5509,7 +5509,7 @@ "categoryLabel": "Oauth authorizations", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: GitHub will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", + "descriptionHTML": "

Deprecation Notice: GitHub will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", "bodyParameters": [ { "description": "

A list of scopes that this authorization is in.

", @@ -9839,7 +9839,7 @@ } ], "summary": "Get GitHub Actions billing for an enterprise", - "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nThe authenticated user must be an enterprise admin.", + "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nThe authenticated user must be an enterprise admin.", "operationId": "billing/get-github-actions-billing-ghe", "tags": [ "billing" @@ -9861,7 +9861,7 @@ "subcategoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the summary of the free and paid GitHub Actions minutes used.

\n

Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

The authenticated user must be an enterprise admin.

", + "descriptionHTML": "

Gets the summary of the free and paid GitHub Actions minutes used.

\n

Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

The authenticated user must be an enterprise admin.

", "responses": [ { "httpStatusCode": "200", @@ -9986,7 +9986,7 @@ } ], "summary": "Get GitHub Packages billing for an enterprise", - "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", + "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", "operationId": "billing/get-github-packages-billing-ghe", "tags": [ "billing" @@ -10008,7 +10008,7 @@ "subcategoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the free and paid storage used for GitHub Packages in gigabytes.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

The authenticated user must be an enterprise admin.

", + "descriptionHTML": "

Gets the free and paid storage used for GitHub Packages in gigabytes.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

The authenticated user must be an enterprise admin.

", "responses": [ { "httpStatusCode": "200", @@ -10047,7 +10047,7 @@ } ], "summary": "Get shared storage billing for an enterprise", - "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", + "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", "operationId": "billing/get-shared-storage-billing-ghe", "tags": [ "billing" @@ -10069,7 +10069,7 @@ "subcategoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

The authenticated user must be an enterprise admin.

", + "descriptionHTML": "

Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

The authenticated user must be an enterprise admin.

", "responses": [ { "httpStatusCode": "200", @@ -13496,7 +13496,7 @@ } ], "summary": "Get GitHub meta information", - "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://help.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", + "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://docs.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", "tags": [ "meta" ], @@ -13516,7 +13516,7 @@ "categoryLabel": "Meta", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"About GitHub's IP addresses.\"

\n

Note: The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.

", + "descriptionHTML": "

Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"About GitHub's IP addresses.\"

\n

Note: The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.

", "responses": [ { "httpStatusCode": "200", @@ -14591,7 +14591,7 @@ } ], "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub plan information' below.\"", "tags": [ "orgs" ], @@ -14611,7 +14611,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub plan information' below.\"

", + "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub plan information' below.\"

", "responses": [ { "httpStatusCode": "200", @@ -14779,29 +14779,29 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_private_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_public_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_allowed_repository_creation_type": { @@ -15006,29 +15006,29 @@ }, { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -19557,7 +19557,7 @@ }, { "name": "state", - "description": "Set to `open`, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", + "description": "Set to `open`, `closed, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", "in": "query", "required": false, "schema": { @@ -19570,7 +19570,7 @@ "fixed" ] }, - "descriptionHTML": "

Set to open, fixed, or dismissed to list code scanning alerts in a specific state.

" + "descriptionHTML": "

Set to open, closed, fixed, or dismissed` to list code scanning alerts in a specific state.

" }, { "name": "sort", @@ -19601,7 +19601,7 @@ } ], "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.", + "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 or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `security_events` read permission to use this endpoint.", "tags": [ "code-scanning" ], @@ -19621,7 +19621,7 @@ "categoryLabel": "Code scanning", "notes": [], "bodyParameters": [], - "descriptionHTML": "

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

GitHub Apps must have the code_scanning_alerts read permission to use this endpoint.

", + "descriptionHTML": "

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 or security manager for the organization, and you must use an access token with the repo scope or security_events scope.

\n

GitHub Apps must have the security_events read permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -19702,7 +19702,7 @@ } ], "summary": "List SAML SSO authorizations for an organization", - "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `read:org` scope can list all credential authorizations for an organization that uses SAML single sign-on (SSO). The credentials are either personal access tokens or SSH keys that organization members have authorized for the organization. For more information, see [About authentication with SAML single sign-on](https://help.github.com/en/articles/about-authentication-with-saml-single-sign-on).", + "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `read:org` scope can list all credential authorizations for an organization that uses SAML single sign-on (SSO). The credentials are either personal access tokens or SSH keys that organization members have authorized for the organization. For more information, see [About authentication with SAML single sign-on](https://docs.github.com/en/articles/about-authentication-with-saml-single-sign-on).", "tags": [ "orgs" ], @@ -19722,7 +19722,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see GitHub's products.

\n

An authenticated organization owner with the read:org scope can list all credential authorizations for an organization that uses SAML single sign-on (SSO). The credentials are either personal access tokens or SSH keys that organization members have authorized for the organization. For more information, see About authentication with SAML single sign-on.

", + "descriptionHTML": "

Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see GitHub's products.

\n

An authenticated organization owner with the read:org scope can list all credential authorizations for an organization that uses SAML single sign-on (SSO). The credentials are either personal access tokens or SSH keys that organization members have authorized for the organization. For more information, see About authentication with SAML single sign-on.

", "responses": [ { "httpStatusCode": "200", @@ -19769,7 +19769,7 @@ } ], "summary": "Remove a SAML SSO authorization for an organization", - "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `admin:org` scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.", + "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `admin:org` scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.", "tags": [ "orgs" ], @@ -19789,7 +19789,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see GitHub's products.

\n

An authenticated organization owner with the admin:org scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.

", + "descriptionHTML": "

Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see GitHub's products.

\n

An authenticated organization owner with the admin:org scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.

", "responses": [ { "httpStatusCode": "204", @@ -25125,7 +25125,7 @@ } ], "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -25147,7 +25147,7 @@ "subcategoryLabel": "Outside collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", + "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", "responses": [ { "httpStatusCode": "202", @@ -26838,7 +26838,7 @@ }, "visibility": { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -26847,7 +26847,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "has_issues": { @@ -26920,11 +26920,11 @@ }, "license_template": { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, "allow_squash_merge": { @@ -27046,7 +27046,7 @@ }, { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -27055,7 +27055,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -27128,11 +27128,11 @@ }, { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, { @@ -27287,7 +27287,7 @@ } ], "summary": "List secret scanning alerts for an organization", - "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\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 `secret_scanning_alerts` read permission to use this endpoint.", + "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\nTo use this endpoint, you must be an administrator or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `secret_scanning_alerts` read permission to use this endpoint.", "tags": [ "secret-scanning" ], @@ -27307,7 +27307,7 @@ "categoryLabel": "Secret scanning", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\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

GitHub Apps must have the secret_scanning_alerts read permission to use this endpoint.

", + "descriptionHTML": "

Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\nTo use this endpoint, you must be an administrator or security manager for the organization, and you must use an access token with the repo scope or security_events scope.

\n

GitHub Apps must have the secret_scanning_alerts read permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -27355,7 +27355,7 @@ } ], "summary": "Get GitHub Actions billing for an organization", - "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `repo` or `admin:org` scope.", + "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `repo` or `admin:org` scope.", "operationId": "billing/get-github-actions-billing-org", "tags": [ "billing" @@ -27375,7 +27375,7 @@ "categoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the summary of the free and paid GitHub Actions minutes used.

\n

Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

Access tokens must have the repo or admin:org scope.

", + "descriptionHTML": "

Gets the summary of the free and paid GitHub Actions minutes used.

\n

Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

Access tokens must have the repo or admin:org scope.

", "responses": [ { "httpStatusCode": "200", @@ -27496,7 +27496,7 @@ } ], "summary": "Get GitHub Packages billing for an organization", - "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", + "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", "operationId": "billing/get-github-packages-billing-org", "tags": [ "billing" @@ -27516,7 +27516,7 @@ "categoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the free and paid storage used for GitHub Packages in gigabytes.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the repo or admin:org scope.

", + "descriptionHTML": "

Gets the free and paid storage used for GitHub Packages in gigabytes.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the repo or admin:org scope.

", "responses": [ { "httpStatusCode": "200", @@ -27554,7 +27554,7 @@ } ], "summary": "Get shared storage billing for an organization", - "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", + "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", "operationId": "billing/get-shared-storage-billing-org", "tags": [ "billing" @@ -27574,7 +27574,7 @@ "categoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the repo or admin:org scope.

", + "descriptionHTML": "

Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the repo or admin:org scope.

", "responses": [ { "httpStatusCode": "200", @@ -27631,7 +27631,7 @@ } ], "summary": "List IdP groups for an organization", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups available in an organization. You can limit your page results using the `per_page` parameter. GitHub generates a url-encoded `page` token using a cursor value for where the next page begins. For more information on cursor pagination, see \"[Offset and Cursor Pagination explained](https://dev.to/jackmarchant/offset-and-cursor-pagination-explained-b89).\"", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups available in an organization. You can limit your page results using the `per_page` parameter. GitHub generates a url-encoded `page` token using a cursor value for where the next page begins. For more information on cursor pagination, see \"[Offset and Cursor Pagination explained](https://dev.to/jackmarchant/offset-and-cursor-pagination-explained-b89).\"", "tags": [ "teams" ], @@ -27653,7 +27653,7 @@ "subcategoryLabel": "Team sync", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

List IdP groups available in an organization. You can limit your page results using the per_page parameter. GitHub generates a url-encoded page token using a cursor value for where the next page begins. For more information on cursor pagination, see \"Offset and Cursor Pagination explained.\"

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

List IdP groups available in an organization. You can limit your page results using the per_page parameter. GitHub generates a url-encoded page token using a cursor value for where the next page begins. For more information on cursor pagination, see \"Offset and Cursor Pagination explained.\"

", "responses": [ { "httpStatusCode": "200", @@ -27774,7 +27774,7 @@ } ], "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -27893,7 +27893,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", + "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", "bodyParameters": [ { "type": "string", @@ -30637,7 +30637,7 @@ } ], "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -30685,7 +30685,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "bodyParameters": [ { "type": "string", @@ -30768,7 +30768,7 @@ } ], "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -30790,7 +30790,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "responses": [ { "httpStatusCode": "204", @@ -31415,7 +31415,7 @@ } ], "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -31464,7 +31464,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", + "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", "responses": [ { "httpStatusCode": "204", @@ -31615,7 +31615,7 @@ } ], "summary": "List IdP groups for a team", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `GET /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `GET /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", "tags": [ "teams" ], @@ -31637,7 +31637,7 @@ "subcategoryLabel": "Team sync", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

List IdP groups connected to a team on GitHub.

\n

Note: You can also specify a team by org_id and team_id using the route GET /organizations/{org_id}/team/{team_id}/team-sync/group-mappings.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

List IdP groups connected to a team on GitHub.

\n

Note: You can also specify a team by org_id and team_id using the route GET /organizations/{org_id}/team/{team_id}/team-sync/group-mappings.

", "responses": [ { "httpStatusCode": "200", @@ -31685,7 +31685,7 @@ } ], "summary": "Create or update IdP group connections", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PATCH /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PATCH /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", "tags": [ "teams" ], @@ -31810,7 +31810,7 @@ "subcategoryLabel": "Team sync", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Creates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty groups array will remove all connections for a team.

\n

Note: You can also specify a team by org_id and team_id using the route PATCH /organizations/{org_id}/team/{team_id}/team-sync/group-mappings.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Creates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty groups array will remove all connections for a team.

\n

Note: You can also specify a team by org_id and team_id using the route PATCH /organizations/{org_id}/team/{team_id}/team-sync/group-mappings.

", "responses": [ { "httpStatusCode": "200", @@ -34221,86 +34221,6 @@ } ] }, - { - "verb": "delete", - "requestPath": "/reactions/{reaction_id}", - "serverUrl": "https://api.github.com", - "parameters": [ - { - "name": "reaction_id", - "in": "path", - "required": true, - "schema": { - "type": "integer" - }, - "descriptionHTML": "" - } - ], - "x-codeSamples": [ - { - "lang": "Shell", - "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/reactions/42", - "html": "
curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/reactions/42
" - }, - { - "lang": "JavaScript", - "source": "await octokit.request('DELETE /reactions/{reaction_id}', {\n reaction_id: 42\n})", - "html": "
await octokit.request('DELETE /reactions/{reaction_id}', {\n  reaction_id: 42\n})\n
" - } - ], - "summary": "Delete a reaction (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/rest/reference/teams#discussion-comments).", - "tags": [ - "reactions" - ], - "operationId": "reactions/delete-legacy", - "externalDocs": { - "description": "API method documentation", - "url": "https://docs.github.com/rest/reference/reactions/#delete-a-reaction-legacy" - }, - "x-github": { - "githubCloudOnly": false, - "enabledForGitHubApps": true, - "removalDate": "2021-02-21", - "deprecationDate": "2020-02-26", - "category": "reactions", - "subcategory": null - }, - "deprecated": true, - "slug": "delete-a-reaction-legacy", - "category": "reactions", - "categoryLabel": "Reactions", - "notes": [], - "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this blog post.

\n

OAuth access tokens require the write:discussion scope, when deleting a team discussion or team discussion comment.

", - "responses": [ - { - "httpStatusCode": "204", - "httpStatusMessage": "No Content", - "description": "

Response

" - }, - { - "httpStatusCode": "304", - "httpStatusMessage": "Not Modified", - "description": "

Not modified

" - }, - { - "httpStatusCode": "401", - "httpStatusMessage": "Unauthorized", - "description": "

Requires authentication

" - }, - { - "httpStatusCode": "403", - "httpStatusMessage": "Forbidden", - "description": "

Forbidden

" - }, - { - "httpStatusCode": "410", - "httpStatusMessage": "Gone", - "description": "

Gone

" - } - ] - }, { "verb": "get", "requestPath": "/repos/{owner}/{repo}", @@ -34465,12 +34385,12 @@ }, "private": { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, "visibility": { @@ -34890,12 +34810,12 @@ }, { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, { @@ -37277,13 +37197,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -38887,7 +38807,7 @@ } ], "summary": "Get workflow run usage", - "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", + "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", "tags": [ "actions" ], @@ -38909,7 +38829,7 @@ "subcategoryLabel": "Workflow runs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

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.

", + "descriptionHTML": "

Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

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.

", "responses": [ { "httpStatusCode": "200", @@ -39687,7 +39607,7 @@ } ], "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -39753,7 +39673,7 @@ "subcategoryLabel": "Workflows", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", + "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", "responses": [ { "httpStatusCode": "204", @@ -39933,13 +39853,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -40117,7 +40037,7 @@ } ], "summary": "Get workflow usage", - "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", + "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", "tags": [ "actions" ], @@ -40139,7 +40059,7 @@ "subcategoryLabel": "Workflows", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

You can replace workflow_id with the workflow file name. For example, you could use main.yaml. 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.

", + "descriptionHTML": "

Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

You can replace workflow_id with the workflow file name. For example, you could use main.yaml. 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.

", "responses": [ { "httpStatusCode": "200", @@ -40206,7 +40126,7 @@ } ], "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -40228,7 +40148,7 @@ "subcategoryLabel": "Assignees", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the available assignees for issues in a repository.

", + "descriptionHTML": "

Lists the available assignees for issues in a repository.

", "responses": [ { "httpStatusCode": "200", @@ -40740,7 +40660,7 @@ } ], "summary": "Enable automated security fixes", - "description": "Enables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://help.github.com/en/articles/configuring-automated-security-fixes)\".", + "description": "Enables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://docs.github.com/en/articles/configuring-automated-security-fixes)\".", "tags": [ "repos" ], @@ -40760,7 +40680,7 @@ "categoryLabel": "Repos", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Enables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"Configuring automated security fixes\".

", + "descriptionHTML": "

Enables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"Configuring automated security fixes\".

", "responses": [ { "httpStatusCode": "204", @@ -40806,7 +40726,7 @@ } ], "summary": "Disable automated security fixes", - "description": "Disables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://help.github.com/en/articles/configuring-automated-security-fixes)\".", + "description": "Disables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://docs.github.com/en/articles/configuring-automated-security-fixes)\".", "tags": [ "repos" ], @@ -40826,7 +40746,7 @@ "categoryLabel": "Repos", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Disables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"Configuring automated security fixes\".

", + "descriptionHTML": "

Disables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"Configuring automated security fixes\".

", "responses": [ { "httpStatusCode": "204", @@ -41077,7 +40997,7 @@ } ], "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -41099,7 +41019,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -41162,7 +41082,7 @@ } ], "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -41486,11 +41406,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -41659,11 +41579,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -41907,30 +41827,30 @@ }, "required_linear_history": { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "allow_force_pushes": { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, "allow_deletions": { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "required_conversation_resolution": { @@ -42011,7 +41931,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", "responses": [ { "httpStatusCode": "200", @@ -42343,11 +42263,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -42516,11 +42436,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -42764,30 +42684,30 @@ }, { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -42849,7 +42769,7 @@ } ], "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -42871,7 +42791,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -42933,7 +42853,7 @@ } ], "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -42955,7 +42875,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -43013,7 +42933,7 @@ } ], "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -43035,7 +42955,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -43093,7 +43013,7 @@ } ], "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -43115,7 +43035,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "204", @@ -43177,7 +43097,7 @@ } ], "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -43199,7 +43119,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -43257,7 +43177,7 @@ } ], "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -43351,11 +43271,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -43474,7 +43394,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", "responses": [ { "httpStatusCode": "200", @@ -43567,11 +43487,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, { @@ -43701,7 +43621,7 @@ } ], "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -43723,7 +43643,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -43785,7 +43705,7 @@ } ], "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -43807,7 +43727,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -43870,7 +43790,7 @@ } ], "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -43892,7 +43812,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -43955,7 +43875,7 @@ } ], "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -43977,7 +43897,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "204", @@ -44039,7 +43959,7 @@ } ], "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -44061,7 +43981,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -44124,7 +44044,7 @@ } ], "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -44247,7 +44167,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -44400,7 +44320,7 @@ } ], "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -44422,7 +44342,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -44479,7 +44399,7 @@ } ], "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -44501,7 +44421,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -44564,7 +44484,7 @@ } ], "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -44630,7 +44550,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -44717,7 +44637,7 @@ } ], "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -44783,7 +44703,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -44865,7 +44785,7 @@ } ], "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -44930,7 +44850,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -45012,7 +44932,7 @@ } ], "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -45034,7 +44954,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", "responses": [ { "httpStatusCode": "200", @@ -45097,7 +45017,7 @@ } ], "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -45119,7 +45039,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", "responses": [ { "httpStatusCode": "204", @@ -45176,7 +45096,7 @@ } ], "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -45198,7 +45118,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", "responses": [ { "httpStatusCode": "200", @@ -45261,7 +45181,7 @@ } ], "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -45326,7 +45246,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -45403,7 +45323,7 @@ } ], "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -45468,7 +45388,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -45545,7 +45465,7 @@ } ], "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -45609,7 +45529,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -45686,7 +45606,7 @@ } ], "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -45708,7 +45628,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", "responses": [ { "httpStatusCode": "200", @@ -45771,7 +45691,7 @@ } ], "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -45837,7 +45757,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -45914,7 +45834,7 @@ } ], "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -45980,7 +45900,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -46057,7 +45977,7 @@ } ], "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -46122,7 +46042,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -46199,7 +46119,7 @@ } ], "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -46221,7 +46141,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", "responses": [ { "httpStatusCode": "200", @@ -46284,7 +46204,7 @@ } ], "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -46349,7 +46269,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -46426,7 +46346,7 @@ } ], "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -46491,7 +46411,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -46568,7 +46488,7 @@ } ], "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -46632,7 +46552,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -46970,7 +46890,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -47073,7 +46993,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -47296,7 +47216,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -47399,7 +47319,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -48045,7 +47965,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -48148,7 +48068,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -48371,7 +48291,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -48474,7 +48394,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -49129,7 +49049,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -49232,7 +49152,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -49454,7 +49374,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -49557,7 +49477,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -50160,7 +50080,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -50263,7 +50183,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -50485,7 +50405,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -50588,7 +50508,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -51916,7 +51836,7 @@ }, { "name": "state", - "description": "Set to `open`, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", + "description": "Set to `open`, `closed, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", "in": "query", "required": false, "schema": { @@ -51929,7 +51849,7 @@ "fixed" ] }, - "descriptionHTML": "

Set to open, fixed, or dismissed to list code scanning alerts in a specific state.

" + "descriptionHTML": "

Set to open, closed, fixed, or dismissed` to list code scanning alerts in a specific state.

" } ], "x-codeSamples": [ @@ -53541,7 +53461,7 @@ } ], "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -53561,7 +53481,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must have push access to the repository in order to list collaborators.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "200", @@ -53622,7 +53542,7 @@ } ], "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -53642,7 +53562,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "204", @@ -53702,7 +53622,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -53761,7 +53681,7 @@ "categoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", "bodyParameters": [ { "type": "string", @@ -54913,7 +54833,7 @@ } ], "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -54933,7 +54853,7 @@ "categoryLabel": "Commits", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", "responses": [ { "httpStatusCode": "200", @@ -58838,7 +58758,7 @@ } ], "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -58902,7 +58822,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", + "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", "responses": [ { "httpStatusCode": "204", @@ -65043,7 +64963,7 @@ } ], "summary": "Update Git LFS preference", - "description": "You can import repositories from Subversion, Mercurial, and TFS that include files larger than 100MB. This ability is powered by [Git LFS](https://git-lfs.github.com). You can learn more about our LFS feature and working with large files [on our help site](https://help.github.com/articles/versioning-large-files/).", + "description": "You can import repositories from Subversion, Mercurial, and TFS that include files larger than 100MB. This ability is powered by [Git LFS](https://git-lfs.github.com). You can learn more about our LFS feature and working with large files [on our help site](https://docs.github.com/articles/versioning-large-files/).", "tags": [ "migrations" ], @@ -65096,7 +65016,7 @@ "subcategoryLabel": "Source imports", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can import repositories from Subversion, Mercurial, and TFS that include files larger than 100MB. This ability is powered by Git LFS. You can learn more about our LFS feature and working with large files on our help site.

", + "descriptionHTML": "

You can import repositories from Subversion, Mercurial, and TFS that include files larger than 100MB. This ability is powered by Git LFS. You can learn more about our LFS feature and working with large files on our help site.

", "bodyParameters": [ { "type": "string", @@ -66041,7 +65961,7 @@ } ], "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -66187,7 +66107,7 @@ "categoryLabel": "Issues", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "oneOf": [ @@ -67333,7 +67253,7 @@ } ], "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -67353,7 +67273,7 @@ "categoryLabel": "Issues", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", + "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -69859,11 +69779,11 @@ }, "read_only": { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } }, @@ -69914,11 +69834,11 @@ }, { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } ], @@ -72597,12 +72517,12 @@ "properties": { "cname": { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, "https_enforced": { @@ -72729,12 +72649,12 @@ "bodyParameters": [ { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, { @@ -73658,7 +73578,7 @@ } ], "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -73678,7 +73598,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -73735,7 +73655,7 @@ } ], "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -73789,20 +73709,20 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, "draft": { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, "issue": { @@ -73841,7 +73761,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "type": "string", @@ -73881,20 +73801,20 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, { @@ -74737,7 +74657,7 @@ } ], "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/rest/reference/pulls#update-a-pull-request) a pull request, GitHub creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/rest/reference/pulls#update-a-pull-request) a pull request, GitHub creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -74757,7 +74677,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", "responses": [ { "httpStatusCode": "200", @@ -74828,7 +74748,7 @@ } ], "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -74886,11 +74806,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } } @@ -74915,7 +74835,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", "bodyParameters": [ { "type": "string", @@ -74959,11 +74879,11 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } ], @@ -75414,7 +75334,7 @@ }, "side": { "type": "string", - "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -75422,7 +75342,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "line": { @@ -75436,16 +75356,16 @@ }, "start_line": { "type": "integer", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "start_side": { "type": "string", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -75454,7 +75374,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, "in_reply_to": { @@ -75553,7 +75473,7 @@ }, { "type": "string", - "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -75561,7 +75481,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -75575,16 +75495,16 @@ }, { "type": "integer", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "string", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -75593,7 +75513,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, { @@ -82422,7 +82342,7 @@ } ], "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -82485,7 +82405,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", + "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", "bodyParameters": [ { "type": "string", @@ -82555,7 +82475,7 @@ } ], "summary": "Check if vulnerability alerts are enabled for a repository", - "description": "Shows whether dependency alerts are enabled or disabled for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://help.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", + "description": "Shows whether dependency alerts are enabled or disabled for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://docs.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", "tags": [ "repos" ], @@ -82575,7 +82495,7 @@ "categoryLabel": "Repos", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Shows whether dependency alerts are enabled or disabled for a repository. The authenticated user must have admin access to the repository. For more information, see \"About security alerts for vulnerable dependencies\".

", + "descriptionHTML": "

Shows whether dependency alerts are enabled or disabled for a repository. The authenticated user must have admin access to the repository. For more information, see \"About security alerts for vulnerable dependencies\".

", "responses": [ { "httpStatusCode": "204", @@ -82626,7 +82546,7 @@ } ], "summary": "Enable vulnerability alerts", - "description": "Enables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://help.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", + "description": "Enables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://docs.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", "tags": [ "repos" ], @@ -82646,7 +82566,7 @@ "categoryLabel": "Repos", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Enables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"About security alerts for vulnerable dependencies\".

", + "descriptionHTML": "

Enables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"About security alerts for vulnerable dependencies\".

", "responses": [ { "httpStatusCode": "204", @@ -82692,7 +82612,7 @@ } ], "summary": "Disable vulnerability alerts", - "description": "Disables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://help.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", + "description": "Disables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://docs.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", "tags": [ "repos" ], @@ -82712,7 +82632,7 @@ "categoryLabel": "Repos", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Disables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"About security alerts for vulnerable dependencies\".

", + "descriptionHTML": "

Disables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"About security alerts for vulnerable dependencies\".

", "responses": [ { "httpStatusCode": "204", @@ -87759,13 +87679,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -87886,13 +87806,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -87999,13 +87919,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -88274,13 +88194,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -88441,7 +88361,7 @@ } ], "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -88461,7 +88381,7 @@ "categoryLabel": "Search", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", + "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", "responses": [ { "httpStatusCode": "200", @@ -88483,13 +88403,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -90752,7 +90672,7 @@ } ], "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -90777,7 +90697,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -90838,7 +90758,7 @@ } ], "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -90863,7 +90783,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

", + "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

", "responses": [ { "httpStatusCode": "204", @@ -90991,7 +90911,7 @@ } ], "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -91042,7 +90962,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", "bodyParameters": [ { "type": "string", @@ -91120,7 +91040,7 @@ } ], "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -91145,7 +91065,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub.\"

", "responses": [ { "httpStatusCode": "204", @@ -91942,7 +91862,7 @@ } ], "summary": "List IdP groups for a team (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`List IdP groups for a team`](https://docs.github.com/rest/reference/teams#list-idp-groups-for-a-team) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`List IdP groups for a team`](https://docs.github.com/rest/reference/teams#list-idp-groups-for-a-team) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.", "tags": [ "teams" ], @@ -91967,7 +91887,7 @@ "subcategoryLabel": "Team sync", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new List IdP groups for a team endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

List IdP groups connected to a team on GitHub.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new List IdP groups for a team endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

List IdP groups connected to a team on GitHub.

", "responses": [ { "httpStatusCode": "200", @@ -92015,7 +91935,7 @@ } ], "summary": "Create or update IdP group connections (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`Create or update IdP group connections`](https://docs.github.com/rest/reference/teams#create-or-update-idp-group-connections) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`Create or update IdP group connections`](https://docs.github.com/rest/reference/teams#create-or-update-idp-group-connections) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.", "tags": [ "teams" ], @@ -92209,7 +92129,7 @@ "subcategoryLabel": "Team sync", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Create or update IdP group connections endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Creates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty groups array will remove all connections for a team.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Create or update IdP group connections endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Creates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty groups array will remove all connections for a team.

", "responses": [ { "httpStatusCode": "200", @@ -102372,7 +102292,7 @@ } ], "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -102392,7 +102312,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", + "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", "responses": [ { "httpStatusCode": "200", @@ -103626,7 +103546,7 @@ } ], "summary": "Get GitHub Actions billing for a user", - "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `user` scope.", + "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `user` scope.", "operationId": "billing/get-github-actions-billing-user", "tags": [ "billing" @@ -103646,7 +103566,7 @@ "categoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the summary of the free and paid GitHub Actions minutes used.

\n

Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

Access tokens must have the user scope.

", + "descriptionHTML": "

Gets the summary of the free and paid GitHub Actions minutes used.

\n

Paid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

Access tokens must have the user scope.

", "responses": [ { "httpStatusCode": "200", @@ -103684,7 +103604,7 @@ } ], "summary": "Get GitHub Packages billing for a user", - "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", + "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", "operationId": "billing/get-github-packages-billing-user", "tags": [ "billing" @@ -103704,7 +103624,7 @@ "categoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the free and paid storage used for GitHub Packages in gigabytes.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the user scope.

", + "descriptionHTML": "

Gets the free and paid storage used for GitHub Packages in gigabytes.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the user scope.

", "responses": [ { "httpStatusCode": "200", @@ -103742,7 +103662,7 @@ } ], "summary": "Get shared storage billing for a user", - "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", + "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", "operationId": "billing/get-shared-storage-billing-user", "tags": [ "billing" @@ -103762,7 +103682,7 @@ "categoryLabel": "Billing", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the user scope.

", + "descriptionHTML": "

Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.

\n

Paid minutes only apply to packages stored for private repositories. For more information, see \"Managing billing for GitHub Packages.\"

\n

Access tokens must have the user scope.

", "responses": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.0.json b/lib/rest/static/decorated/ghes-3.0.json index 66025d6593..1457e9fe0d 100644 --- a/lib/rest/static/decorated/ghes-3.0.json +++ b/lib/rest/static/decorated/ghes-3.0.json @@ -1244,7 +1244,7 @@ } ], "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.0/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.0/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -1300,7 +1300,7 @@ "subcategoryLabel": "Ldap", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

\n

If you pass the hellcat-preview media type, you can also update the LDAP mapping of a child team.

", + "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

\n

If you pass the hellcat-preview media type, you can also update the LDAP mapping of a child team.

", "bodyParameters": [ { "type": "string", @@ -3216,11 +3216,11 @@ }, "email": { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } }, @@ -3261,11 +3261,11 @@ }, { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } ], @@ -8970,7 +8970,7 @@ } ], "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -8990,7 +8990,7 @@ "categoryLabel": "Apps", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", + "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -9135,7 +9135,7 @@ } ], "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.0/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.0/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.0/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.0/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -9235,7 +9235,7 @@ "categoryLabel": "Oauth authorizations", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", + "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", "bodyParameters": [ { "description": "

A list of scopes that this authorization is in.

", @@ -17386,7 +17386,7 @@ } ], "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -17412,7 +17412,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", + "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", "responses": [ { "httpStatusCode": "200", @@ -17580,29 +17580,29 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_private_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_public_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_allowed_repository_creation_type": { @@ -17793,29 +17793,29 @@ }, { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -23663,7 +23663,7 @@ } ], "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -23685,7 +23685,7 @@ "subcategoryLabel": "Outside collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", + "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", "responses": [ { "httpStatusCode": "202", @@ -24952,7 +24952,7 @@ }, "visibility": { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", "enum": [ "public", "private", @@ -24961,7 +24961,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", "childParamsGroups": [] }, "has_issues": { @@ -25034,11 +25034,11 @@ }, "license_template": { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, "allow_squash_merge": { @@ -25161,7 +25161,7 @@ }, { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", "enum": [ "public", "private", @@ -25170,7 +25170,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", "childParamsGroups": [] }, { @@ -25243,11 +25243,11 @@ }, { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, { @@ -25421,7 +25421,7 @@ } ], "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -25549,7 +25549,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", + "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", "bodyParameters": [ { "type": "string", @@ -28125,7 +28125,7 @@ } ], "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28173,7 +28173,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "bodyParameters": [ { "type": "string", @@ -28256,7 +28256,7 @@ } ], "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28278,7 +28278,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "responses": [ { "httpStatusCode": "204", @@ -28921,7 +28921,7 @@ } ], "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -28970,7 +28970,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", + "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", "responses": [ { "httpStatusCode": "204", @@ -31798,12 +31798,12 @@ }, "private": { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, "visibility": { @@ -31996,12 +31996,12 @@ }, { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, { @@ -33640,13 +33640,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -35234,7 +35234,7 @@ } ], "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -35300,7 +35300,7 @@ "subcategoryLabel": "Workflows", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", + "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", "responses": [ { "httpStatusCode": "204", @@ -35480,13 +35480,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -35658,7 +35658,7 @@ } ], "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -35680,7 +35680,7 @@ "subcategoryLabel": "Assignees", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the available assignees for issues in a repository.

", + "descriptionHTML": "

Lists the available assignees for issues in a repository.

", "responses": [ { "httpStatusCode": "200", @@ -36019,7 +36019,7 @@ } ], "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -36048,7 +36048,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -36111,7 +36111,7 @@ } ], "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -36435,11 +36435,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -36540,11 +36540,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -36689,30 +36689,30 @@ }, "required_linear_history": { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "allow_force_pushes": { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, "allow_deletions": { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "required_conversation_resolution": { @@ -36812,7 +36812,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", "responses": [ { "httpStatusCode": "200", @@ -37144,11 +37144,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -37249,11 +37249,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -37398,30 +37398,30 @@ }, { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -37495,7 +37495,7 @@ } ], "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37517,7 +37517,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -37579,7 +37579,7 @@ } ], "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37601,7 +37601,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -37659,7 +37659,7 @@ } ], "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -37681,7 +37681,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -37739,7 +37739,7 @@ } ], "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -37761,7 +37761,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "204", @@ -37823,7 +37823,7 @@ } ], "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37852,7 +37852,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -37910,7 +37910,7 @@ } ], "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -38004,11 +38004,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -38066,7 +38066,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", "responses": [ { "httpStatusCode": "200", @@ -38159,11 +38159,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, { @@ -38225,7 +38225,7 @@ } ], "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38247,7 +38247,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -38309,7 +38309,7 @@ } ], "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -38338,7 +38338,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -38401,7 +38401,7 @@ } ], "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -38430,7 +38430,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -38493,7 +38493,7 @@ } ], "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -38522,7 +38522,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "204", @@ -38584,7 +38584,7 @@ } ], "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38606,7 +38606,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -38669,7 +38669,7 @@ } ], "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -38731,7 +38731,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", "bodyParameters": [ { "type": "boolean", @@ -38823,7 +38823,7 @@ } ], "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38845,7 +38845,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -38902,7 +38902,7 @@ } ], "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38924,7 +38924,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -38987,7 +38987,7 @@ } ], "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39053,7 +39053,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -39140,7 +39140,7 @@ } ], "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39206,7 +39206,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -39288,7 +39288,7 @@ } ], "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39353,7 +39353,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -39435,7 +39435,7 @@ } ], "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -39457,7 +39457,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", "responses": [ { "httpStatusCode": "200", @@ -39520,7 +39520,7 @@ } ], "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -39542,7 +39542,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", "responses": [ { "httpStatusCode": "204", @@ -39599,7 +39599,7 @@ } ], "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -39621,7 +39621,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", "responses": [ { "httpStatusCode": "200", @@ -39684,7 +39684,7 @@ } ], "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -39749,7 +39749,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -39826,7 +39826,7 @@ } ], "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -39891,7 +39891,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -39968,7 +39968,7 @@ } ], "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40032,7 +40032,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40109,7 +40109,7 @@ } ], "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -40131,7 +40131,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", "responses": [ { "httpStatusCode": "200", @@ -40194,7 +40194,7 @@ } ], "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40260,7 +40260,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40337,7 +40337,7 @@ } ], "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40403,7 +40403,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40480,7 +40480,7 @@ } ], "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40545,7 +40545,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40622,7 +40622,7 @@ } ], "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -40644,7 +40644,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", "responses": [ { "httpStatusCode": "200", @@ -40707,7 +40707,7 @@ } ], "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40772,7 +40772,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40849,7 +40849,7 @@ } ], "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40914,7 +40914,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40991,7 +40991,7 @@ } ], "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41055,7 +41055,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41262,7 +41262,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -41365,7 +41365,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -41588,7 +41588,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -41691,7 +41691,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -42337,7 +42337,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -42440,7 +42440,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -42663,7 +42663,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -42766,7 +42766,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -43421,7 +43421,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -43524,7 +43524,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -43746,7 +43746,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -43849,7 +43849,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -44452,7 +44452,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -44555,7 +44555,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -44777,7 +44777,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -44880,7 +44880,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -46874,7 +46874,7 @@ } ], "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -46894,7 +46894,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must have push access to the repository in order to list collaborators.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "200", @@ -46955,7 +46955,7 @@ } ], "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -46975,7 +46975,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "204", @@ -47035,7 +47035,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -47094,7 +47094,7 @@ "categoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", "bodyParameters": [ { "type": "string", @@ -48278,7 +48278,7 @@ } ], "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -48305,7 +48305,7 @@ "categoryLabel": "Commits", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", "responses": [ { "httpStatusCode": "200", @@ -51923,7 +51923,7 @@ } ], "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -51987,7 +51987,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", + "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", "responses": [ { "httpStatusCode": "204", @@ -56990,7 +56990,7 @@ } ], "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -57136,7 +57136,7 @@ "categoryLabel": "Issues", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "oneOf": [ @@ -58159,8 +58159,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -58249,8 +58249,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -58333,7 +58333,7 @@ } ], "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -58359,7 +58359,7 @@ "categoryLabel": "Issues", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", + "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -59344,8 +59344,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -60716,8 +60716,8 @@ }, { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -60909,11 +60909,11 @@ }, "read_only": { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } }, @@ -60964,11 +60964,11 @@ }, { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } ], @@ -63398,12 +63398,12 @@ "properties": { "cname": { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, "https_enforced": { @@ -63530,12 +63530,12 @@ "bodyParameters": [ { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, { @@ -64819,7 +64819,7 @@ } ], "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -64839,7 +64839,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -64896,7 +64896,7 @@ } ], "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -64950,20 +64950,20 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, "draft": { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, "issue": { @@ -65002,7 +65002,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "type": "string", @@ -65042,20 +65042,20 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, { @@ -65947,7 +65947,7 @@ } ], "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -65967,7 +65967,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", "responses": [ { "httpStatusCode": "200", @@ -66038,7 +66038,7 @@ } ], "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -66096,11 +66096,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } } @@ -66125,7 +66125,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", "bodyParameters": [ { "type": "string", @@ -66169,11 +66169,11 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } ], @@ -66446,7 +66446,7 @@ }, "side": { "type": "string", - "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -66454,7 +66454,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "line": { @@ -66468,16 +66468,16 @@ }, "start_line": { "type": "integer", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "start_side": { "type": "string", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -66486,7 +66486,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, "in_reply_to": { @@ -66592,7 +66592,7 @@ }, { "type": "string", - "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -66600,7 +66600,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -66614,16 +66614,16 @@ }, { "type": "integer", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "string", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -66632,7 +66632,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, { @@ -72277,7 +72277,7 @@ } ], "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -72340,7 +72340,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", + "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", "bodyParameters": [ { "type": "string", @@ -72733,13 +72733,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -72860,13 +72860,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -72979,13 +72979,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -73254,13 +73254,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -73427,7 +73427,7 @@ } ], "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.0/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.0/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -73453,7 +73453,7 @@ "categoryLabel": "Search", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", + "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", "responses": [ { "httpStatusCode": "200", @@ -73480,13 +73480,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -76546,7 +76546,7 @@ } ], "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -76571,7 +76571,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -76632,7 +76632,7 @@ } ], "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -76657,7 +76657,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -76785,7 +76785,7 @@ } ], "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -76836,7 +76836,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", "bodyParameters": [ { "type": "string", @@ -76914,7 +76914,7 @@ } ], "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -76939,7 +76939,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -83338,7 +83338,7 @@ } ], "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.0/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.0/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -83358,7 +83358,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", + "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", "responses": [ { "httpStatusCode": "200", @@ -84098,7 +84098,7 @@ } ], "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -84116,11 +84116,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -84141,7 +84141,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -84152,11 +84152,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] @@ -84189,7 +84189,7 @@ } ], "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -84207,11 +84207,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -84232,7 +84232,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", "responses": [ { "httpStatusCode": "204", @@ -84243,11 +84243,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json index 71638a9512..94a9b3d1d0 100644 --- a/lib/rest/static/decorated/ghes-3.1.json +++ b/lib/rest/static/decorated/ghes-3.1.json @@ -1244,7 +1244,7 @@ } ], "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.1/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.1/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -1300,7 +1300,7 @@ "subcategoryLabel": "Ldap", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

\n

If you pass the hellcat-preview media type, you can also update the LDAP mapping of a child team.

", + "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

\n

If you pass the hellcat-preview media type, you can also update the LDAP mapping of a child team.

", "bodyParameters": [ { "type": "string", @@ -3216,11 +3216,11 @@ }, "email": { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } }, @@ -3261,11 +3261,11 @@ }, { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } ], @@ -8970,7 +8970,7 @@ } ], "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -8990,7 +8990,7 @@ "categoryLabel": "Apps", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", + "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -9135,7 +9135,7 @@ } ], "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.1/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.1/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.1/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.1/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -9235,7 +9235,7 @@ "categoryLabel": "Oauth authorizations", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", + "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", "bodyParameters": [ { "description": "

A list of scopes that this authorization is in.

", @@ -17386,7 +17386,7 @@ } ], "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -17412,7 +17412,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", + "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", "responses": [ { "httpStatusCode": "200", @@ -17580,29 +17580,29 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_private_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_public_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_allowed_repository_creation_type": { @@ -17793,29 +17793,29 @@ }, { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -23663,7 +23663,7 @@ } ], "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -23685,7 +23685,7 @@ "subcategoryLabel": "Outside collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", + "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", "responses": [ { "httpStatusCode": "202", @@ -24952,7 +24952,7 @@ }, "visibility": { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", "enum": [ "public", "private", @@ -24961,7 +24961,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", "childParamsGroups": [] }, "has_issues": { @@ -25034,11 +25034,11 @@ }, "license_template": { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, "allow_squash_merge": { @@ -25161,7 +25161,7 @@ }, { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.
\nThe visibility parameter overrides the private parameter when you use both parameters with the nebula-preview preview header.

", "enum": [ "public", "private", @@ -25170,7 +25170,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", "childParamsGroups": [] }, { @@ -25243,11 +25243,11 @@ }, { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, { @@ -25421,7 +25421,7 @@ } ], "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -25549,7 +25549,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", + "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", "bodyParameters": [ { "type": "string", @@ -28125,7 +28125,7 @@ } ], "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28173,7 +28173,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "bodyParameters": [ { "type": "string", @@ -28256,7 +28256,7 @@ } ], "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28278,7 +28278,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "responses": [ { "httpStatusCode": "204", @@ -28921,7 +28921,7 @@ } ], "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -28970,7 +28970,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", + "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", "responses": [ { "httpStatusCode": "204", @@ -31798,12 +31798,12 @@ }, "private": { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, "visibility": { @@ -31996,12 +31996,12 @@ }, { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, { @@ -33640,13 +33640,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -35234,7 +35234,7 @@ } ], "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -35300,7 +35300,7 @@ "subcategoryLabel": "Workflows", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", + "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", "responses": [ { "httpStatusCode": "204", @@ -35480,13 +35480,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -35658,7 +35658,7 @@ } ], "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -35680,7 +35680,7 @@ "subcategoryLabel": "Assignees", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the available assignees for issues in a repository.

", + "descriptionHTML": "

Lists the available assignees for issues in a repository.

", "responses": [ { "httpStatusCode": "200", @@ -36019,7 +36019,7 @@ } ], "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -36048,7 +36048,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -36111,7 +36111,7 @@ } ], "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -36435,11 +36435,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -36540,11 +36540,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -36689,30 +36689,30 @@ }, "required_linear_history": { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "allow_force_pushes": { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, "allow_deletions": { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "required_conversation_resolution": { @@ -36812,7 +36812,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", "responses": [ { "httpStatusCode": "200", @@ -37144,11 +37144,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -37249,11 +37249,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -37398,30 +37398,30 @@ }, { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -37495,7 +37495,7 @@ } ], "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37517,7 +37517,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -37579,7 +37579,7 @@ } ], "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37601,7 +37601,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -37659,7 +37659,7 @@ } ], "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -37681,7 +37681,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -37739,7 +37739,7 @@ } ], "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -37761,7 +37761,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "204", @@ -37823,7 +37823,7 @@ } ], "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37852,7 +37852,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -37910,7 +37910,7 @@ } ], "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -38004,11 +38004,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -38066,7 +38066,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", "responses": [ { "httpStatusCode": "200", @@ -38159,11 +38159,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, { @@ -38225,7 +38225,7 @@ } ], "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38247,7 +38247,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -38309,7 +38309,7 @@ } ], "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -38338,7 +38338,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -38401,7 +38401,7 @@ } ], "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -38430,7 +38430,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -38493,7 +38493,7 @@ } ], "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -38522,7 +38522,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "204", @@ -38584,7 +38584,7 @@ } ], "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38606,7 +38606,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -38669,7 +38669,7 @@ } ], "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -38731,7 +38731,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", "bodyParameters": [ { "type": "boolean", @@ -38823,7 +38823,7 @@ } ], "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38845,7 +38845,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -38902,7 +38902,7 @@ } ], "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38924,7 +38924,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -38987,7 +38987,7 @@ } ], "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39053,7 +39053,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -39140,7 +39140,7 @@ } ], "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39206,7 +39206,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -39288,7 +39288,7 @@ } ], "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39353,7 +39353,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -39435,7 +39435,7 @@ } ], "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -39457,7 +39457,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", "responses": [ { "httpStatusCode": "200", @@ -39520,7 +39520,7 @@ } ], "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -39542,7 +39542,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", "responses": [ { "httpStatusCode": "204", @@ -39599,7 +39599,7 @@ } ], "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -39621,7 +39621,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", "responses": [ { "httpStatusCode": "200", @@ -39684,7 +39684,7 @@ } ], "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -39749,7 +39749,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -39826,7 +39826,7 @@ } ], "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -39891,7 +39891,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -39968,7 +39968,7 @@ } ], "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40032,7 +40032,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40109,7 +40109,7 @@ } ], "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -40131,7 +40131,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", "responses": [ { "httpStatusCode": "200", @@ -40194,7 +40194,7 @@ } ], "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40260,7 +40260,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40337,7 +40337,7 @@ } ], "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40403,7 +40403,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40480,7 +40480,7 @@ } ], "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40545,7 +40545,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40622,7 +40622,7 @@ } ], "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -40644,7 +40644,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", "responses": [ { "httpStatusCode": "200", @@ -40707,7 +40707,7 @@ } ], "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40772,7 +40772,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40849,7 +40849,7 @@ } ], "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40914,7 +40914,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -40991,7 +40991,7 @@ } ], "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41055,7 +41055,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41393,7 +41393,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -41496,7 +41496,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -41719,7 +41719,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -41822,7 +41822,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -42468,7 +42468,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -42571,7 +42571,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -42794,7 +42794,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -42897,7 +42897,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -43552,7 +43552,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -43655,7 +43655,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -43877,7 +43877,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -43980,7 +43980,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -44583,7 +44583,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -44686,7 +44686,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -44908,7 +44908,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -45011,7 +45011,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -47419,7 +47419,7 @@ } ], "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -47439,7 +47439,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must have push access to the repository in order to list collaborators.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "200", @@ -47500,7 +47500,7 @@ } ], "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -47520,7 +47520,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "204", @@ -47580,7 +47580,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -47639,7 +47639,7 @@ "categoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", "bodyParameters": [ { "type": "string", @@ -48823,7 +48823,7 @@ } ], "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -48850,7 +48850,7 @@ "categoryLabel": "Commits", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", "responses": [ { "httpStatusCode": "200", @@ -52468,7 +52468,7 @@ } ], "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -52532,7 +52532,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", + "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", "responses": [ { "httpStatusCode": "204", @@ -57535,7 +57535,7 @@ } ], "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -57681,7 +57681,7 @@ "categoryLabel": "Issues", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "oneOf": [ @@ -58704,8 +58704,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -58794,8 +58794,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -58878,7 +58878,7 @@ } ], "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -58904,7 +58904,7 @@ "categoryLabel": "Issues", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", + "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -59889,8 +59889,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -61261,8 +61261,8 @@ }, { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -61454,11 +61454,11 @@ }, "read_only": { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } }, @@ -61509,11 +61509,11 @@ }, { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } ], @@ -63943,12 +63943,12 @@ "properties": { "cname": { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, "https_enforced": { @@ -64075,12 +64075,12 @@ "bodyParameters": [ { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, { @@ -65364,7 +65364,7 @@ } ], "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -65384,7 +65384,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -65441,7 +65441,7 @@ } ], "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -65495,20 +65495,20 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, "draft": { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, "issue": { @@ -65547,7 +65547,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "type": "string", @@ -65587,20 +65587,20 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, { @@ -66492,7 +66492,7 @@ } ], "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.1/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.1/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -66512,7 +66512,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", "responses": [ { "httpStatusCode": "200", @@ -66583,7 +66583,7 @@ } ], "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -66641,11 +66641,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } } @@ -66670,7 +66670,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", "bodyParameters": [ { "type": "string", @@ -66714,11 +66714,11 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } ], @@ -66991,7 +66991,7 @@ }, "side": { "type": "string", - "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -66999,7 +66999,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "line": { @@ -67013,16 +67013,16 @@ }, "start_line": { "type": "integer", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "start_side": { "type": "string", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -67031,7 +67031,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, "in_reply_to": { @@ -67137,7 +67137,7 @@ }, { "type": "string", - "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -67145,7 +67145,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -67159,16 +67159,16 @@ }, { "type": "integer", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "string", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -67177,7 +67177,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, { @@ -73221,7 +73221,7 @@ } ], "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -73284,7 +73284,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", + "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", "bodyParameters": [ { "type": "string", @@ -73677,13 +73677,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -73804,13 +73804,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -73923,13 +73923,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -74198,13 +74198,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -74371,7 +74371,7 @@ } ], "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.1/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.1/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -74397,7 +74397,7 @@ "categoryLabel": "Search", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", + "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", "responses": [ { "httpStatusCode": "200", @@ -74424,13 +74424,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -77490,7 +77490,7 @@ } ], "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -77515,7 +77515,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -77576,7 +77576,7 @@ } ], "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -77601,7 +77601,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -77729,7 +77729,7 @@ } ], "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -77780,7 +77780,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", "bodyParameters": [ { "type": "string", @@ -77858,7 +77858,7 @@ } ], "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -77883,7 +77883,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -84282,7 +84282,7 @@ } ], "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.1/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.1/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -84302,7 +84302,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", + "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", "responses": [ { "httpStatusCode": "200", @@ -85042,7 +85042,7 @@ } ], "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -85060,11 +85060,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -85085,7 +85085,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -85096,11 +85096,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] @@ -85133,7 +85133,7 @@ } ], "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -85151,11 +85151,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -85176,7 +85176,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", "responses": [ { "httpStatusCode": "204", @@ -85187,11 +85187,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index b471b6efe7..2e42b338ee 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -1244,7 +1244,7 @@ } ], "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.2/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.2/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -1300,7 +1300,7 @@ "subcategoryLabel": "Ldap", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

\n

If you pass the hellcat-preview media type, you can also update the LDAP mapping of a child team.

", + "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

\n

If you pass the hellcat-preview media type, you can also update the LDAP mapping of a child team.

", "bodyParameters": [ { "type": "string", @@ -3216,11 +3216,11 @@ }, "email": { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } }, @@ -3261,11 +3261,11 @@ }, { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } ], @@ -9190,7 +9190,7 @@ } ], "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -9210,7 +9210,7 @@ "categoryLabel": "Apps", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", + "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -9355,7 +9355,7 @@ } ], "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.2/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.2/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.2/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.2/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -9455,7 +9455,7 @@ "categoryLabel": "Oauth authorizations", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", + "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", "bodyParameters": [ { "description": "

A list of scopes that this authorization is in.

", @@ -17606,7 +17606,7 @@ } ], "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -17632,7 +17632,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", + "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", "responses": [ { "httpStatusCode": "200", @@ -17800,29 +17800,29 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_private_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_public_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_allowed_repository_creation_type": { @@ -18013,29 +18013,29 @@ }, { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -24157,7 +24157,7 @@ } ], "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -24179,7 +24179,7 @@ "subcategoryLabel": "Outside collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", + "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", "responses": [ { "httpStatusCode": "202", @@ -25446,7 +25446,7 @@ }, "visibility": { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -25455,7 +25455,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "has_issues": { @@ -25528,11 +25528,11 @@ }, "license_template": { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, "allow_squash_merge": { @@ -25654,7 +25654,7 @@ }, { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -25663,7 +25663,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -25736,11 +25736,11 @@ }, { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, { @@ -25924,7 +25924,7 @@ } ], "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -26052,7 +26052,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", + "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", "bodyParameters": [ { "type": "string", @@ -28628,7 +28628,7 @@ } ], "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28676,7 +28676,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "bodyParameters": [ { "type": "string", @@ -28759,7 +28759,7 @@ } ], "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28781,7 +28781,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "responses": [ { "httpStatusCode": "204", @@ -29424,7 +29424,7 @@ } ], "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -29473,7 +29473,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", + "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", "responses": [ { "httpStatusCode": "204", @@ -32301,12 +32301,12 @@ }, "private": { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, "visibility": { @@ -32726,12 +32726,12 @@ }, { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, { @@ -34552,13 +34552,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -36484,7 +36484,7 @@ } ], "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -36550,7 +36550,7 @@ "subcategoryLabel": "Workflows", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", + "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", "responses": [ { "httpStatusCode": "204", @@ -36730,13 +36730,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -36908,7 +36908,7 @@ } ], "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -36930,7 +36930,7 @@ "subcategoryLabel": "Assignees", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the available assignees for issues in a repository.

", + "descriptionHTML": "

Lists the available assignees for issues in a repository.

", "responses": [ { "httpStatusCode": "200", @@ -37269,7 +37269,7 @@ } ], "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37298,7 +37298,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -37361,7 +37361,7 @@ } ], "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -37685,11 +37685,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -37790,11 +37790,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -37939,30 +37939,30 @@ }, "required_linear_history": { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "allow_force_pushes": { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, "allow_deletions": { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "required_conversation_resolution": { @@ -38062,7 +38062,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", "responses": [ { "httpStatusCode": "200", @@ -38394,11 +38394,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -38499,11 +38499,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -38648,30 +38648,30 @@ }, { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -38745,7 +38745,7 @@ } ], "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38767,7 +38767,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -38829,7 +38829,7 @@ } ], "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -38851,7 +38851,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -38909,7 +38909,7 @@ } ], "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -38931,7 +38931,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -38989,7 +38989,7 @@ } ], "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -39011,7 +39011,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "204", @@ -39073,7 +39073,7 @@ } ], "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39102,7 +39102,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -39160,7 +39160,7 @@ } ], "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -39254,11 +39254,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -39316,7 +39316,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", "responses": [ { "httpStatusCode": "200", @@ -39409,11 +39409,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, { @@ -39475,7 +39475,7 @@ } ], "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39497,7 +39497,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -39559,7 +39559,7 @@ } ], "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -39588,7 +39588,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -39651,7 +39651,7 @@ } ], "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -39680,7 +39680,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -39743,7 +39743,7 @@ } ], "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -39772,7 +39772,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "204", @@ -39834,7 +39834,7 @@ } ], "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39856,7 +39856,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -39919,7 +39919,7 @@ } ], "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -39981,7 +39981,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", "bodyParameters": [ { "type": "boolean", @@ -40073,7 +40073,7 @@ } ], "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40095,7 +40095,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -40152,7 +40152,7 @@ } ], "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40174,7 +40174,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -40237,7 +40237,7 @@ } ], "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40303,7 +40303,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -40390,7 +40390,7 @@ } ], "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40456,7 +40456,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -40538,7 +40538,7 @@ } ], "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40603,7 +40603,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -40685,7 +40685,7 @@ } ], "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -40707,7 +40707,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", "responses": [ { "httpStatusCode": "200", @@ -40770,7 +40770,7 @@ } ], "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -40792,7 +40792,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", "responses": [ { "httpStatusCode": "204", @@ -40849,7 +40849,7 @@ } ], "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -40871,7 +40871,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", "responses": [ { "httpStatusCode": "200", @@ -40934,7 +40934,7 @@ } ], "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -40999,7 +40999,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41076,7 +41076,7 @@ } ], "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41141,7 +41141,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41218,7 +41218,7 @@ } ], "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41282,7 +41282,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41359,7 +41359,7 @@ } ], "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -41381,7 +41381,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", "responses": [ { "httpStatusCode": "200", @@ -41444,7 +41444,7 @@ } ], "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41510,7 +41510,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41587,7 +41587,7 @@ } ], "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41653,7 +41653,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41730,7 +41730,7 @@ } ], "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41795,7 +41795,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41872,7 +41872,7 @@ } ], "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -41894,7 +41894,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", "responses": [ { "httpStatusCode": "200", @@ -41957,7 +41957,7 @@ } ], "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42022,7 +42022,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42099,7 +42099,7 @@ } ], "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42164,7 +42164,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42241,7 +42241,7 @@ } ], "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42305,7 +42305,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42643,7 +42643,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -42746,7 +42746,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -42969,7 +42969,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -43072,7 +43072,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -43718,7 +43718,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -43821,7 +43821,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -44044,7 +44044,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -44147,7 +44147,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -44802,7 +44802,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -44905,7 +44905,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -45127,7 +45127,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -45230,7 +45230,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -45833,7 +45833,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -45936,7 +45936,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -46158,7 +46158,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -46261,7 +46261,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -48669,7 +48669,7 @@ } ], "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -48689,7 +48689,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must have push access to the repository in order to list collaborators.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "200", @@ -48750,7 +48750,7 @@ } ], "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -48770,7 +48770,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "204", @@ -48830,7 +48830,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -48889,7 +48889,7 @@ "categoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", "bodyParameters": [ { "type": "string", @@ -50073,7 +50073,7 @@ } ], "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -50100,7 +50100,7 @@ "categoryLabel": "Commits", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", "responses": [ { "httpStatusCode": "200", @@ -53738,7 +53738,7 @@ } ], "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -53802,7 +53802,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", + "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", "responses": [ { "httpStatusCode": "204", @@ -59714,7 +59714,7 @@ } ], "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -59860,7 +59860,7 @@ "categoryLabel": "Issues", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "oneOf": [ @@ -60883,8 +60883,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -60973,8 +60973,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -61057,7 +61057,7 @@ } ], "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -61083,7 +61083,7 @@ "categoryLabel": "Issues", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", + "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -62068,8 +62068,8 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -63440,8 +63440,8 @@ }, { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", - "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```", + "html": "

Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the blog post.

\n

To receive the project_card attribute, project boards must be enabled for a repository, and you must provide a custom media type in the Accept header:

\n
application/vnd.github.starfox-preview+json
" } ] }, @@ -63633,11 +63633,11 @@ }, "read_only": { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } }, @@ -63688,11 +63688,11 @@ }, { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } ], @@ -66122,12 +66122,12 @@ "properties": { "cname": { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, "https_enforced": { @@ -66254,12 +66254,12 @@ "bodyParameters": [ { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, { @@ -67543,7 +67543,7 @@ } ], "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -67563,7 +67563,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -67620,7 +67620,7 @@ } ], "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -67674,20 +67674,20 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, "draft": { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, "issue": { @@ -67726,7 +67726,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "type": "string", @@ -67766,20 +67766,20 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, { @@ -68671,7 +68671,7 @@ } ], "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.2/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.2/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -68691,7 +68691,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", "responses": [ { "httpStatusCode": "200", @@ -68762,7 +68762,7 @@ } ], "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -68820,11 +68820,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } } @@ -68849,7 +68849,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", "bodyParameters": [ { "type": "string", @@ -68893,11 +68893,11 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } ], @@ -69170,7 +69170,7 @@ }, "side": { "type": "string", - "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -69178,7 +69178,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "line": { @@ -69192,16 +69192,16 @@ }, "start_line": { "type": "integer", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "start_side": { "type": "string", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -69210,7 +69210,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, "in_reply_to": { @@ -69316,7 +69316,7 @@ }, { "type": "string", - "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -69324,7 +69324,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -69338,16 +69338,16 @@ }, { "type": "integer", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "string", - "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -69356,7 +69356,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, { @@ -75548,7 +75548,7 @@ } ], "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -75611,7 +75611,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", + "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", "bodyParameters": [ { "type": "string", @@ -76467,13 +76467,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -76594,13 +76594,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -76713,13 +76713,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -76988,13 +76988,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -77161,7 +77161,7 @@ } ], "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.2/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.2/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -77187,7 +77187,7 @@ "categoryLabel": "Search", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", + "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", "responses": [ { "httpStatusCode": "200", @@ -77214,13 +77214,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -80280,7 +80280,7 @@ } ], "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -80305,7 +80305,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -80366,7 +80366,7 @@ } ], "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -80391,7 +80391,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -80519,7 +80519,7 @@ } ], "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -80570,7 +80570,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", "bodyParameters": [ { "type": "string", @@ -80648,7 +80648,7 @@ } ], "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -80673,7 +80673,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -87083,7 +87083,7 @@ } ], "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.2/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.2/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -87103,7 +87103,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", + "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", "responses": [ { "httpStatusCode": "200", @@ -87843,7 +87843,7 @@ } ], "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -87861,11 +87861,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -87886,7 +87886,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -87897,11 +87897,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] @@ -87934,7 +87934,7 @@ } ], "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -87952,11 +87952,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -87977,7 +87977,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", "responses": [ { "httpStatusCode": "204", @@ -87988,11 +87988,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json index f6a85a9ac6..dac14684ca 100644 --- a/lib/rest/static/decorated/ghes-3.3.json +++ b/lib/rest/static/decorated/ghes-3.3.json @@ -1168,7 +1168,7 @@ } ], "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.3/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.3/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -1217,7 +1217,7 @@ "subcategoryLabel": "Ldap", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

", + "descriptionHTML": "

Updates the distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the Create a team endpoint to create a team with LDAP mapping.

", "bodyParameters": [ { "type": "string", @@ -3049,11 +3049,11 @@ }, "email": { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } }, @@ -3094,11 +3094,11 @@ }, { "type": "string", - "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", + "description": "

Required for built-in authentication. The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the GitHub authentication guide.

", "name": "email", "in": "body", "rawType": "string", - "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", + "rawDescription": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/).", "childParamsGroups": [] } ], @@ -9023,7 +9023,7 @@ } ], "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -9043,7 +9043,7 @@ "categoryLabel": "Apps", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", + "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -9188,7 +9188,7 @@ } ], "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.3/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.3/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.3/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.3/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -9288,7 +9288,7 @@ "categoryLabel": "Oauth authorizations", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", + "descriptionHTML": "

Deprecation Notice: GitHub Enterprise Server will discontinue the OAuth Authorizations API, which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our web application flow. The OAuth Authorizations API will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the blog post.

\n

Warning: Apps must use the web application flow to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the blog post.

\n

Creates OAuth tokens using Basic Authentication. If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"Working with two-factor authentication.\"

\n

To create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use fingerprint to differentiate between them.

\n

You can also create tokens on GitHub Enterprise Server from the personal access tokens settings page. Read more about these tokens in the GitHub Help documentation.

\n

Organizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in the GitHub Help documentation.

", "bodyParameters": [ { "description": "

A list of scopes that this authorization is in.

", @@ -17546,7 +17546,7 @@ } ], "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -17566,7 +17566,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", + "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"

", "responses": [ { "httpStatusCode": "200", @@ -17734,29 +17734,29 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_private_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_public_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_allowed_repository_creation_type": { @@ -17941,29 +17941,29 @@ }, { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -24196,7 +24196,7 @@ } ], "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -24218,7 +24218,7 @@ "subcategoryLabel": "Outside collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", + "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", "responses": [ { "httpStatusCode": "202", @@ -25434,7 +25434,7 @@ }, "visibility": { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -25443,7 +25443,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "has_issues": { @@ -25516,11 +25516,11 @@ }, "license_template": { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, "allow_squash_merge": { @@ -25642,7 +25642,7 @@ }, { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -25651,7 +25651,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -25724,11 +25724,11 @@ }, { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, { @@ -25883,7 +25883,7 @@ } ], "summary": "List secret scanning alerts for an organization", - "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\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 `secret_scanning_alerts` read permission to use this endpoint.", + "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\nTo use this endpoint, you must be an administrator or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `secret_scanning_alerts` read permission to use this endpoint.", "tags": [ "secret-scanning" ], @@ -25903,7 +25903,7 @@ "categoryLabel": "Secret scanning", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\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

GitHub Apps must have the secret_scanning_alerts read permission to use this endpoint.

", + "descriptionHTML": "

Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\nTo use this endpoint, you must be an administrator or security manager for the organization, and you must use an access token with the repo scope or security_events scope.

\n

GitHub Apps must have the secret_scanning_alerts read permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -26034,7 +26034,7 @@ } ], "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -26162,7 +26162,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", + "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", "bodyParameters": [ { "type": "string", @@ -28646,7 +28646,7 @@ } ], "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28694,7 +28694,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "bodyParameters": [ { "type": "string", @@ -28777,7 +28777,7 @@ } ], "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -28799,7 +28799,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "responses": [ { "httpStatusCode": "204", @@ -29424,7 +29424,7 @@ } ], "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -29473,7 +29473,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", + "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", "responses": [ { "httpStatusCode": "204", @@ -32148,12 +32148,12 @@ }, "private": { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, "visibility": { @@ -32573,12 +32573,12 @@ }, { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, { @@ -34399,13 +34399,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -34866,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": "

The id of the workflow run.

" - }, - { - "name": "attempt_number", - "description": "The attempt number of the workflow run.", - "in": "path", - "required": true, - "schema": { - "type": "integer" - }, - "descriptionHTML": "

The attempt number of the workflow run.

" - }, - { - "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": "

If true pull requests are omitted from the response (empty array).

" - } - ], - "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": "
curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42
" - }, - { - "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": "
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})\n
" - } - ], - "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": "

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.

", - "responses": [ - { - "httpStatusCode": "200", - "httpStatusMessage": "OK", - "description": "

Response

", - "payload": "
{\n  \"id\": 30433642,\n  \"name\": \"Build\",\n  \"node_id\": \"MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==\",\n  \"check_suite_id\": 42,\n  \"check_suite_node_id\": \"MDEwOkNoZWNrU3VpdGU0Mg==\",\n  \"head_branch\": \"master\",\n  \"head_sha\": \"acb5820ced9479c074f688cc328bf03f341a511d\",\n  \"run_number\": 562,\n  \"event\": \"push\",\n  \"status\": \"queued\",\n  \"conclusion\": null,\n  \"workflow_id\": 159038,\n  \"url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642\",\n  \"html_url\": \"https://github.com/octo-org/octo-repo/actions/runs/30433642\",\n  \"pull_requests\": [],\n  \"created_at\": \"2020-01-22T19:33:08Z\",\n  \"updated_at\": \"2020-01-22T19:33:08Z\",\n  \"jobs_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/jobs\",\n  \"logs_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/logs\",\n  \"check_suite_url\": \"https://api.github.com/repos/octo-org/octo-repo/check-suites/414944374\",\n  \"artifacts_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/artifacts\",\n  \"cancel_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/cancel\",\n  \"rerun_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/rerun\",\n  \"workflow_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038\",\n  \"head_commit\": {\n    \"id\": \"acb5820ced9479c074f688cc328bf03f341a511d\",\n    \"tree_id\": \"d23f6eedb1e1b9610bbc754ddb5197bfe7271223\",\n    \"message\": \"Create linter.yaml\",\n    \"timestamp\": \"2020-01-22T19:33:05Z\",\n    \"author\": {\n      \"name\": \"Octo Cat\",\n      \"email\": \"octocat@github.com\"\n    },\n    \"committer\": {\n      \"name\": \"GitHub\",\n      \"email\": \"noreply@github.com\"\n    }\n  },\n  \"repository\": {\n    \"id\": 1296269,\n    \"node_id\": \"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\",\n    \"name\": \"Hello-World\",\n    \"full_name\": \"octocat/Hello-World\",\n    \"owner\": {\n      \"login\": \"octocat\",\n      \"id\": 1,\n      \"node_id\": \"MDQ6VXNlcjE=\",\n      \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n      \"gravatar_id\": \"\",\n      \"url\": \"https://api.github.com/users/octocat\",\n      \"html_url\": \"https://github.com/octocat\",\n      \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n      \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n      \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n      \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n      \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n      \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n      \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n      \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n      \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n      \"type\": \"User\",\n      \"site_admin\": false\n    },\n    \"private\": false,\n    \"html_url\": \"https://github.com/octocat/Hello-World\",\n    \"description\": \"This your first repo!\",\n    \"fork\": false,\n    \"url\": \"https://api.github.com/repos/octocat/Hello-World\",\n    \"archive_url\": \"https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}\",\n    \"assignees_url\": \"https://api.github.com/repos/octocat/Hello-World/assignees{/user}\",\n    \"blobs_url\": \"https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}\",\n    \"branches_url\": \"https://api.github.com/repos/octocat/Hello-World/branches{/branch}\",\n    \"collaborators_url\": \"https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}\",\n    \"comments_url\": \"https://api.github.com/repos/octocat/Hello-World/comments{/number}\",\n    \"commits_url\": \"https://api.github.com/repos/octocat/Hello-World/commits{/sha}\",\n    \"compare_url\": \"https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}\",\n    \"contents_url\": \"https://api.github.com/repos/octocat/Hello-World/contents/{+path}\",\n    \"contributors_url\": \"https://api.github.com/repos/octocat/Hello-World/contributors\",\n    \"deployments_url\": \"https://api.github.com/repos/octocat/Hello-World/deployments\",\n    \"downloads_url\": \"https://api.github.com/repos/octocat/Hello-World/downloads\",\n    \"events_url\": \"https://api.github.com/repos/octocat/Hello-World/events\",\n    \"forks_url\": \"https://api.github.com/repos/octocat/Hello-World/forks\",\n    \"git_commits_url\": \"https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}\",\n    \"git_refs_url\": \"https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}\",\n    \"git_tags_url\": \"https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}\",\n    \"git_url\": \"git:github.com/octocat/Hello-World.git\",\n    \"issue_comment_url\": \"https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}\",\n    \"issue_events_url\": \"https://api.github.com/repos/octocat/Hello-World/issues/events{/number}\",\n    \"issues_url\": \"https://api.github.com/repos/octocat/Hello-World/issues{/number}\",\n    \"keys_url\": \"https://api.github.com/repos/octocat/Hello-World/keys{/key_id}\",\n    \"labels_url\": \"https://api.github.com/repos/octocat/Hello-World/labels{/name}\",\n    \"languages_url\": \"https://api.github.com/repos/octocat/Hello-World/languages\",\n    \"merges_url\": \"https://api.github.com/repos/octocat/Hello-World/merges\",\n    \"milestones_url\": \"https://api.github.com/repos/octocat/Hello-World/milestones{/number}\",\n    \"notifications_url\": \"https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}\",\n    \"pulls_url\": \"https://api.github.com/repos/octocat/Hello-World/pulls{/number}\",\n    \"releases_url\": \"https://api.github.com/repos/octocat/Hello-World/releases{/id}\",\n    \"ssh_url\": \"git@github.com:octocat/Hello-World.git\",\n    \"stargazers_url\": \"https://api.github.com/repos/octocat/Hello-World/stargazers\",\n    \"statuses_url\": \"https://api.github.com/repos/octocat/Hello-World/statuses/{sha}\",\n    \"subscribers_url\": \"https://api.github.com/repos/octocat/Hello-World/subscribers\",\n    \"subscription_url\": \"https://api.github.com/repos/octocat/Hello-World/subscription\",\n    \"tags_url\": \"https://api.github.com/repos/octocat/Hello-World/tags\",\n    \"teams_url\": \"https://api.github.com/repos/octocat/Hello-World/teams\",\n    \"trees_url\": \"https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}\",\n    \"hooks_url\": \"http://api.github.com/repos/octocat/Hello-World/hooks\"\n  },\n  \"head_repository\": {\n    \"id\": 217723378,\n    \"node_id\": \"MDEwOlJlcG9zaXRvcnkyMTc3MjMzNzg=\",\n    \"name\": \"octo-repo\",\n    \"full_name\": \"octo-org/octo-repo\",\n    \"private\": true,\n    \"owner\": {\n      \"login\": \"octocat\",\n      \"id\": 1,\n      \"node_id\": \"MDQ6VXNlcjE=\",\n      \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n      \"gravatar_id\": \"\",\n      \"url\": \"https://api.github.com/users/octocat\",\n      \"html_url\": \"https://github.com/octocat\",\n      \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n      \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n      \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n      \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n      \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n      \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n      \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n      \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n      \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n      \"type\": \"User\",\n      \"site_admin\": false\n    },\n    \"html_url\": \"https://github.com/octo-org/octo-repo\",\n    \"description\": null,\n    \"fork\": false,\n    \"url\": \"https://api.github.com/repos/octo-org/octo-repo\",\n    \"forks_url\": \"https://api.github.com/repos/octo-org/octo-repo/forks\",\n    \"keys_url\": \"https://api.github.com/repos/octo-org/octo-repo/keys{/key_id}\",\n    \"collaborators_url\": \"https://api.github.com/repos/octo-org/octo-repo/collaborators{/collaborator}\",\n    \"teams_url\": \"https://api.github.com/repos/octo-org/octo-repo/teams\",\n    \"hooks_url\": \"https://api.github.com/repos/octo-org/octo-repo/hooks\",\n    \"issue_events_url\": \"https://api.github.com/repos/octo-org/octo-repo/issues/events{/number}\",\n    \"events_url\": \"https://api.github.com/repos/octo-org/octo-repo/events\",\n    \"assignees_url\": \"https://api.github.com/repos/octo-org/octo-repo/assignees{/user}\",\n    \"branches_url\": \"https://api.github.com/repos/octo-org/octo-repo/branches{/branch}\",\n    \"tags_url\": \"https://api.github.com/repos/octo-org/octo-repo/tags\",\n    \"blobs_url\": \"https://api.github.com/repos/octo-org/octo-repo/git/blobs{/sha}\",\n    \"git_tags_url\": \"https://api.github.com/repos/octo-org/octo-repo/git/tags{/sha}\",\n    \"git_refs_url\": \"https://api.github.com/repos/octo-org/octo-repo/git/refs{/sha}\",\n    \"trees_url\": \"https://api.github.com/repos/octo-org/octo-repo/git/trees{/sha}\",\n    \"statuses_url\": \"https://api.github.com/repos/octo-org/octo-repo/statuses/{sha}\",\n    \"languages_url\": \"https://api.github.com/repos/octo-org/octo-repo/languages\",\n    \"stargazers_url\": \"https://api.github.com/repos/octo-org/octo-repo/stargazers\",\n    \"contributors_url\": \"https://api.github.com/repos/octo-org/octo-repo/contributors\",\n    \"subscribers_url\": \"https://api.github.com/repos/octo-org/octo-repo/subscribers\",\n    \"subscription_url\": \"https://api.github.com/repos/octo-org/octo-repo/subscription\",\n    \"commits_url\": \"https://api.github.com/repos/octo-org/octo-repo/commits{/sha}\",\n    \"git_commits_url\": \"https://api.github.com/repos/octo-org/octo-repo/git/commits{/sha}\",\n    \"comments_url\": \"https://api.github.com/repos/octo-org/octo-repo/comments{/number}\",\n    \"issue_comment_url\": \"https://api.github.com/repos/octo-org/octo-repo/issues/comments{/number}\",\n    \"contents_url\": \"https://api.github.com/repos/octo-org/octo-repo/contents/{+path}\",\n    \"compare_url\": \"https://api.github.com/repos/octo-org/octo-repo/compare/{base}...{head}\",\n    \"merges_url\": \"https://api.github.com/repos/octo-org/octo-repo/merges\",\n    \"archive_url\": \"https://api.github.com/repos/octo-org/octo-repo/{archive_format}{/ref}\",\n    \"downloads_url\": \"https://api.github.com/repos/octo-org/octo-repo/downloads\",\n    \"issues_url\": \"https://api.github.com/repos/octo-org/octo-repo/issues{/number}\",\n    \"pulls_url\": \"https://api.github.com/repos/octo-org/octo-repo/pulls{/number}\",\n    \"milestones_url\": \"https://api.github.com/repos/octo-org/octo-repo/milestones{/number}\",\n    \"notifications_url\": \"https://api.github.com/repos/octo-org/octo-repo/notifications{?since,all,participating}\",\n    \"labels_url\": \"https://api.github.com/repos/octo-org/octo-repo/labels{/name}\",\n    \"releases_url\": \"https://api.github.com/repos/octo-org/octo-repo/releases{/id}\",\n    \"deployments_url\": \"https://api.github.com/repos/octo-org/octo-repo/deployments\"\n  }\n}\n
" - } - ] - }, - { - "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": "

The id of the workflow run.

" - }, - { - "name": "attempt_number", - "description": "The attempt number of the workflow run.", - "in": "path", - "required": true, - "schema": { - "type": "integer" - }, - "descriptionHTML": "

The attempt number of the workflow run.

" - }, - { - "name": "per_page", - "description": "Results per page (max 100)", - "in": "query", - "schema": { - "type": "integer", - "default": 30 - }, - "descriptionHTML": "

Results per page (max 100)

" - }, - { - "name": "page", - "description": "Page number of the results to fetch.", - "in": "query", - "schema": { - "type": "integer", - "default": 1 - }, - "descriptionHTML": "

Page number of the results to fetch.

" - } - ], - "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": "
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
" - }, - { - "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": "
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})\n
" - } - ], - "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": "

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.

", - "responses": [ - { - "httpStatusCode": "200", - "httpStatusMessage": "OK", - "description": "

Response

", - "payload": "
{\n  \"total_count\": 1,\n  \"jobs\": [\n    {\n      \"id\": 399444496,\n      \"run_id\": 29679449,\n      \"run_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449\",\n      \"node_id\": \"MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==\",\n      \"head_sha\": \"f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0\",\n      \"url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496\",\n      \"html_url\": \"https://github.com/octo-org/octo-repo/runs/399444496\",\n      \"status\": \"completed\",\n      \"conclusion\": \"success\",\n      \"started_at\": \"2020-01-20T17:42:40Z\",\n      \"completed_at\": \"2020-01-20T17:44:39Z\",\n      \"name\": \"build\",\n      \"steps\": [\n        {\n          \"name\": \"Set up job\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 1,\n          \"started_at\": \"2020-01-20T09:42:40.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:41.000-08:00\"\n        },\n        {\n          \"name\": \"Run actions/checkout@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 2,\n          \"started_at\": \"2020-01-20T09:42:41.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:45.000-08:00\"\n        },\n        {\n          \"name\": \"Set up Ruby\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 3,\n          \"started_at\": \"2020-01-20T09:42:45.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:45.000-08:00\"\n        },\n        {\n          \"name\": \"Run actions/cache@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 4,\n          \"started_at\": \"2020-01-20T09:42:45.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:48.000-08:00\"\n        },\n        {\n          \"name\": \"Install Bundler\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 5,\n          \"started_at\": \"2020-01-20T09:42:48.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:52.000-08:00\"\n        },\n        {\n          \"name\": \"Install Gems\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 6,\n          \"started_at\": \"2020-01-20T09:42:52.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:53.000-08:00\"\n        },\n        {\n          \"name\": \"Run Tests\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 7,\n          \"started_at\": \"2020-01-20T09:42:53.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:59.000-08:00\"\n        },\n        {\n          \"name\": \"Deploy to Heroku\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 8,\n          \"started_at\": \"2020-01-20T09:42:59.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        },\n        {\n          \"name\": \"Post actions/cache@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 16,\n          \"started_at\": \"2020-01-20T09:44:39.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        },\n        {\n          \"name\": \"Complete job\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 17,\n          \"started_at\": \"2020-01-20T09:44:39.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        }\n      ],\n      \"check_run_url\": \"https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496\",\n      \"labels\": [\n        \"self-hosted\",\n        \"foo\",\n        \"bar\"\n      ],\n      \"runner_id\": 1,\n      \"runner_name\": \"my runner\",\n      \"runner_group_id\": 2,\n      \"runner_group_name\": \"my runner group\"\n    }\n  ]\n}\n
" - }, - { - "httpStatusCode": "404", - "httpStatusMessage": "Not Found", - "description": "

Resource not found

" - } - ] - }, { "verb": "post", "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/cancel", @@ -36545,7 +36331,7 @@ } ], "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -36611,7 +36397,7 @@ "subcategoryLabel": "Workflows", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", + "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", "responses": [ { "httpStatusCode": "204", @@ -36791,13 +36577,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -36969,7 +36755,7 @@ } ], "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -36991,7 +36777,7 @@ "subcategoryLabel": "Assignees", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the available assignees for issues in a repository.

", + "descriptionHTML": "

Lists the available assignees for issues in a repository.

", "responses": [ { "httpStatusCode": "200", @@ -37708,7 +37494,7 @@ } ], "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -37730,7 +37516,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -37793,7 +37579,7 @@ } ], "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -38117,11 +37903,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -38222,11 +38008,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -38371,30 +38157,30 @@ }, "required_linear_history": { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "allow_force_pushes": { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, "allow_deletions": { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "required_conversation_resolution": { @@ -38487,7 +38273,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", "responses": [ { "httpStatusCode": "200", @@ -38819,11 +38605,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -38924,11 +38710,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -39073,30 +38859,30 @@ }, { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -39170,7 +38956,7 @@ } ], "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39192,7 +38978,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -39254,7 +39040,7 @@ } ], "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39276,7 +39062,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -39334,7 +39120,7 @@ } ], "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -39356,7 +39142,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -39414,7 +39200,7 @@ } ], "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -39436,7 +39222,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "204", @@ -39498,7 +39284,7 @@ } ], "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39520,7 +39306,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -39578,7 +39364,7 @@ } ], "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -39672,11 +39458,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -39727,7 +39513,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", "responses": [ { "httpStatusCode": "200", @@ -39820,11 +39606,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, { @@ -39886,7 +39672,7 @@ } ], "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -39908,7 +39694,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -39970,7 +39756,7 @@ } ], "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -39992,7 +39778,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -40055,7 +39841,7 @@ } ], "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -40077,7 +39863,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -40140,7 +39926,7 @@ } ], "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -40162,7 +39948,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "204", @@ -40224,7 +40010,7 @@ } ], "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40246,7 +40032,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -40309,7 +40095,7 @@ } ], "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -40371,7 +40157,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", "bodyParameters": [ { "type": "boolean", @@ -40463,7 +40249,7 @@ } ], "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40485,7 +40271,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -40542,7 +40328,7 @@ } ], "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40564,7 +40350,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -40627,7 +40413,7 @@ } ], "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40693,7 +40479,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -40780,7 +40566,7 @@ } ], "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40846,7 +40632,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -40928,7 +40714,7 @@ } ], "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -40993,7 +40779,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -41075,7 +40861,7 @@ } ], "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -41097,7 +40883,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", "responses": [ { "httpStatusCode": "200", @@ -41160,7 +40946,7 @@ } ], "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -41182,7 +40968,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", "responses": [ { "httpStatusCode": "204", @@ -41239,7 +41025,7 @@ } ], "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -41261,7 +41047,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", "responses": [ { "httpStatusCode": "200", @@ -41324,7 +41110,7 @@ } ], "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41389,7 +41175,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41466,7 +41252,7 @@ } ], "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41531,7 +41317,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41608,7 +41394,7 @@ } ], "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41672,7 +41458,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41749,7 +41535,7 @@ } ], "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -41771,7 +41557,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", "responses": [ { "httpStatusCode": "200", @@ -41834,7 +41620,7 @@ } ], "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -41900,7 +41686,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -41977,7 +41763,7 @@ } ], "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42043,7 +41829,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42120,7 +41906,7 @@ } ], "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42185,7 +41971,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42262,7 +42048,7 @@ } ], "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -42284,7 +42070,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", "responses": [ { "httpStatusCode": "200", @@ -42347,7 +42133,7 @@ } ], "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42412,7 +42198,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42489,7 +42275,7 @@ } ], "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42554,7 +42340,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -42631,7 +42417,7 @@ } ], "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -42695,7 +42481,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -43033,7 +42819,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -43136,7 +42922,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -43359,7 +43145,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -43462,7 +43248,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -44108,7 +43894,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -44211,7 +43997,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -44434,7 +44220,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -44537,7 +44323,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -45192,7 +44978,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -45295,7 +45081,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -45517,7 +45303,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -45620,7 +45406,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -46223,7 +46009,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -46326,7 +46112,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -46548,7 +46334,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -46651,7 +46437,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -49159,7 +48945,7 @@ } ], "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -49179,7 +48965,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must have push access to the repository in order to list collaborators.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "200", @@ -49240,7 +49026,7 @@ } ], "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -49260,7 +49046,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "204", @@ -49320,7 +49106,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -49379,7 +49165,7 @@ "categoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", "bodyParameters": [ { "type": "string", @@ -50531,7 +50317,7 @@ } ], "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -50551,7 +50337,7 @@ "categoryLabel": "Commits", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", "responses": [ { "httpStatusCode": "200", @@ -54113,7 +53899,7 @@ } ], "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -54177,7 +53963,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", + "descriptionHTML": "

You can use this endpoint to trigger a webhook event called repository_dispatch when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch event occurs. For an example repository_dispatch webhook payload, see \"RepositoryDispatchEvent.\"

\n

The client_payload parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload can be used as a test to debug your workflow.

\n

This endpoint requires write access to the repository by providing either:

\n\n

This input example shows how you can use the client_payload as a test to debug your workflow.

", "responses": [ { "httpStatusCode": "204", @@ -60078,7 +59864,7 @@ } ], "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -60224,7 +60010,7 @@ "categoryLabel": "Issues", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "oneOf": [ @@ -61370,7 +61156,7 @@ } ], "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -61390,7 +61176,7 @@ "categoryLabel": "Issues", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", + "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -63896,11 +63682,11 @@ }, "read_only": { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } }, @@ -63951,11 +63737,11 @@ }, { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } ], @@ -66634,12 +66420,12 @@ "properties": { "cname": { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, "https_enforced": { @@ -66766,12 +66552,12 @@ "bodyParameters": [ { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, { @@ -68008,7 +67794,7 @@ } ], "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -68028,7 +67814,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -68085,7 +67871,7 @@ } ], "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -68139,20 +67925,20 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, "draft": { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, "issue": { @@ -68191,7 +67977,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "type": "string", @@ -68231,20 +68017,20 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, { @@ -69087,7 +68873,7 @@ } ], "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.3/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.3/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -69107,7 +68893,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", "responses": [ { "httpStatusCode": "200", @@ -69178,7 +68964,7 @@ } ], "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -69236,11 +69022,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } } @@ -69265,7 +69051,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", "bodyParameters": [ { "type": "string", @@ -69309,11 +69095,11 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } ], @@ -69574,7 +69360,7 @@ }, "side": { "type": "string", - "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -69582,7 +69368,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "line": { @@ -69596,16 +69382,16 @@ }, "start_line": { "type": "integer", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "start_side": { "type": "string", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -69614,7 +69400,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, "in_reply_to": { @@ -69713,7 +69499,7 @@ }, { "type": "string", - "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -69721,7 +69507,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -69735,16 +69521,16 @@ }, { "type": "integer", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "string", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -69753,7 +69539,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, { @@ -76208,7 +75994,7 @@ } ], "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -76271,7 +76057,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", + "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", "bodyParameters": [ { "type": "string", @@ -77127,13 +76913,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -77254,13 +77040,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -77367,13 +77153,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -77642,13 +77428,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -77809,7 +77595,7 @@ } ], "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.3/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.3/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -77829,7 +77615,7 @@ "categoryLabel": "Search", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", + "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", "responses": [ { "httpStatusCode": "200", @@ -77851,13 +77637,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -80837,7 +80623,7 @@ } ], "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -80862,7 +80648,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -80923,7 +80709,7 @@ } ], "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -80948,7 +80734,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -81076,7 +80862,7 @@ } ], "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -81127,7 +80913,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", "bodyParameters": [ { "type": "string", @@ -81205,7 +80991,7 @@ } ], "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -81230,7 +81016,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub Enterprise Server.\"

", "responses": [ { "httpStatusCode": "204", @@ -87598,7 +87384,7 @@ } ], "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.3/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.3/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -87618,7 +87404,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", + "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", "responses": [ { "httpStatusCode": "200", @@ -88346,7 +88132,7 @@ } ], "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -88364,11 +88150,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -88389,7 +88175,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -88400,11 +88186,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] @@ -88437,7 +88223,7 @@ } ], "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -88455,11 +88241,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -88480,7 +88266,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", "responses": [ { "httpStatusCode": "204", @@ -88491,11 +88277,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index 939569c1c6..99d15bcf4c 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -5477,7 +5477,7 @@ } ], "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -5497,7 +5497,7 @@ "categoryLabel": "Apps", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", + "descriptionHTML": "

Note: The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

\n

If the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a personal access token or an installation access token to access this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -11186,7 +11186,7 @@ } ], "summary": "Get GitHub AE meta information", - "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://help.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", + "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://docs.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", "tags": [ "meta" ], @@ -11206,7 +11206,7 @@ "categoryLabel": "Meta", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"About GitHub's IP addresses.\"

\n

Note: The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.

", + "descriptionHTML": "

Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"About GitHub's IP addresses.\"

\n

Note: The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.

", "responses": [ { "httpStatusCode": "200", @@ -12113,7 +12113,7 @@ } ], "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub AE plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub AE plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub AE plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub AE plan information' below.\"", "tags": [ "orgs" ], @@ -12133,7 +12133,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub AE plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub AE plan information' below.\"

", + "descriptionHTML": "

To see many of the organization response values, you need to be an authenticated organization owner with the admin:org scope. When the value of two_factor_requirement_enabled is true, the organization requires all members, billing managers, and outside collaborators to enable two-factor authentication.

\n

GitHub Apps with the Organization plan permission can use this endpoint to retrieve information about an organization's GitHub AE plan. See \"Authenticating with GitHub Apps\" for details. For an example response, see 'Response with GitHub AE plan information' below.\"

", "responses": [ { "httpStatusCode": "200", @@ -12301,29 +12301,29 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_private_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_can_create_public_repositories": { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "members_allowed_repository_creation_type": { @@ -12528,29 +12528,29 @@ }, { "type": "boolean", - "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of:
\n* true - all organization members can create internal repositories.
\n* false - only organization owners can create internal repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_internal_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of:
\n* true - all organization members can create private repositories.
\n* false - only organization owners can create private repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_private_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", + "description": "

Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of:
\n* true - all organization members can create public repositories.
\n* false - only organization owners can create public repositories.
\nDefault: true. For more information, see \"Restricting repository creation in your organization\" in the GitHub Help documentation.

", "name": "members_can_create_public_repositories", "in": "body", "rawType": "boolean", - "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", + "rawDescription": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -17887,7 +17887,7 @@ } ], "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -17909,7 +17909,7 @@ "subcategoryLabel": "Outside collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", + "descriptionHTML": "

When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"Converting an organization member to an outside collaborator\".

", "responses": [ { "httpStatusCode": "202", @@ -18457,7 +18457,7 @@ }, "visibility": { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -18466,7 +18466,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "has_issues": { @@ -18539,11 +18539,11 @@ }, "license_template": { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, "allow_squash_merge": { @@ -18665,7 +18665,7 @@ }, { "type": "string", - "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", + "description": "

Can be public or private. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"Creating an internal repository\" in the GitHub Help documentation.

", "enum": [ "public", "private", @@ -18674,7 +18674,7 @@ "name": "visibility", "in": "body", "rawType": "string", - "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "rawDescription": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -18747,11 +18747,11 @@ }, { "type": "string", - "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", + "description": "

Choose an open source license template that best suits your needs, and then use the license keyword as the license_template string. For example, \"mit\" or \"mpl-2.0\".

", "name": "license_template", "in": "body", "rawType": "string", - "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", + "rawDescription": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\".", "childParamsGroups": [] }, { @@ -18935,7 +18935,7 @@ } ], "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -19054,7 +19054,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", + "descriptionHTML": "

To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"Setting team creation permissions.\"

\n

When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see \"About teams\".

", "bodyParameters": [ { "type": "string", @@ -21708,7 +21708,7 @@ } ], "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -21756,7 +21756,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

An organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "bodyParameters": [ { "type": "string", @@ -21839,7 +21839,7 @@ } ], "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -21861,7 +21861,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", + "descriptionHTML": "

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

Note: You can also specify a team by org_id and team_id using the route DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}.

", "responses": [ { "httpStatusCode": "204", @@ -22486,7 +22486,7 @@ } ], "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -22535,7 +22535,7 @@ "categoryLabel": "Teams", "contentType": "application/json", "notes": [], - "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", + "descriptionHTML": "

To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

Note: You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

\n

For more information about the permission levels, see \"Repository permission levels for an organization\".

", "responses": [ { "httpStatusCode": "204", @@ -24966,86 +24966,6 @@ } ] }, - { - "verb": "delete", - "requestPath": "/reactions/{reaction_id}", - "serverUrl": "https://{hostname}/api/v3", - "parameters": [ - { - "name": "reaction_id", - "in": "path", - "required": true, - "schema": { - "type": "integer" - }, - "descriptionHTML": "" - } - ], - "x-codeSamples": [ - { - "lang": "Shell", - "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/reactions/42", - "html": "
curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/reactions/42
" - }, - { - "lang": "JavaScript", - "source": "await octokit.request('DELETE /reactions/{reaction_id}', {\n reaction_id: 42\n})", - "html": "
await octokit.request('DELETE /reactions/{reaction_id}', {\n  reaction_id: 42\n})\n
" - } - ], - "summary": "Delete a reaction (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/github-ae@latest/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/github-ae@latest/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/github-ae@latest/rest/reference/teams#discussion-comments).", - "tags": [ - "reactions" - ], - "operationId": "reactions/delete-legacy", - "externalDocs": { - "description": "API method documentation", - "url": "https://docs.github.com/github-ae@latest/rest/reference/reactions/#delete-a-reaction-legacy" - }, - "x-github": { - "githubCloudOnly": false, - "enabledForGitHubApps": true, - "removalDate": "2021-02-21", - "deprecationDate": "2020-02-26", - "category": "reactions", - "subcategory": null - }, - "deprecated": true, - "slug": "delete-a-reaction-legacy", - "category": "reactions", - "categoryLabel": "Reactions", - "notes": [], - "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this blog post.

\n

OAuth access tokens require the write:discussion scope, when deleting a team discussion or team discussion comment.

", - "responses": [ - { - "httpStatusCode": "204", - "httpStatusMessage": "No Content", - "description": "

Response

" - }, - { - "httpStatusCode": "304", - "httpStatusMessage": "Not Modified", - "description": "

Not modified

" - }, - { - "httpStatusCode": "401", - "httpStatusMessage": "Unauthorized", - "description": "

Requires authentication

" - }, - { - "httpStatusCode": "403", - "httpStatusMessage": "Forbidden", - "description": "

Forbidden

" - }, - { - "httpStatusCode": "410", - "httpStatusMessage": "Gone", - "description": "

Gone

" - } - ] - }, { "verb": "get", "requestPath": "/repos/{owner}/{repo}", @@ -25210,12 +25130,12 @@ }, "private": { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, "visibility": { @@ -25635,12 +25555,12 @@ }, { "type": "boolean", - "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", + "description": "

Either true to make the repository private or false to make it public. Default: false.
\nNote: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private. Note: You will get a 422 error if the organization restricts changing repository visibility to organization owners and a non-owner tries to change the value of private.

", "default": false, "name": "private", "in": "body", "rawType": "boolean", - "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "rawDescription": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "childParamsGroups": [] }, { @@ -27189,13 +27109,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -28364,7 +28284,7 @@ } ], "summary": "Get workflow run usage", - "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", + "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", "tags": [ "actions" ], @@ -28386,7 +28306,7 @@ "subcategoryLabel": "Workflow runs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

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.

", + "descriptionHTML": "

Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

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.

", "responses": [ { "httpStatusCode": "200", @@ -29164,7 +29084,7 @@ } ], "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -29230,7 +29150,7 @@ "subcategoryLabel": "Workflows", "contentType": "application/json", "notes": [], - "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", + "descriptionHTML": "

You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.

\n

You must configure your GitHub Actions workflow to run when the workflow_dispatch webhook event occurs. The inputs are configured in the workflow file. For more information about how to configure the workflow_dispatch event in the workflow file, see \"Events that trigger workflows.\"

\n

You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the actions:write permission to use this endpoint. For more information, see \"Creating a personal access token for the command line.\"

", "responses": [ { "httpStatusCode": "204", @@ -29410,13 +29330,13 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { "type": "string" }, - "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" + "descriptionHTML": "

Returns workflow run triggered by the event you specify. For example, push, pull_request or issue. For more information, see \"Events that trigger workflows.\"

" }, { "name": "status", @@ -29585,7 +29505,7 @@ } ], "summary": "Get workflow usage", - "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", + "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", "tags": [ "actions" ], @@ -29607,7 +29527,7 @@ "subcategoryLabel": "Workflows", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

You can replace workflow_id with the workflow file name. For example, you could use main.yaml. 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.

", + "descriptionHTML": "

Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"Managing billing for GitHub Actions\".

\n

You can replace workflow_id with the workflow file name. For example, you could use main.yaml. 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.

", "responses": [ { "httpStatusCode": "200", @@ -29674,7 +29594,7 @@ } ], "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -29696,7 +29616,7 @@ "subcategoryLabel": "Assignees", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the available assignees for issues in a repository.

", + "descriptionHTML": "

Lists the available assignees for issues in a repository.

", "responses": [ { "httpStatusCode": "200", @@ -30413,7 +30333,7 @@ } ], "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -30435,7 +30355,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -30498,7 +30418,7 @@ } ], "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -30822,11 +30742,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -30995,11 +30915,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -31243,30 +31163,30 @@ }, "required_linear_history": { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "allow_force_pushes": { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, "allow_deletions": { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "required_conversation_resolution": { @@ -31347,7 +31267,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Protecting a branch requires admin or owner permissions to the repository.

\n

Note: Passing new arrays of users and teams replaces their previous values.

\n

Note: The list of users, apps, and teams in total is limited to 100 items.

", "responses": [ { "httpStatusCode": "200", @@ -31679,11 +31599,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -31852,11 +31772,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners review them.

", + "description": "

Blocks merging pull requests until code owners review them.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them.", "childParamsGroups": [] }, { @@ -32100,30 +32020,30 @@ }, { "type": "boolean", - "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", + "description": "

Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to true to enforce a linear commit history. Set to false to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: false. For more information, see \"Requiring a linear commit history\" in the GitHub Help documentation.

", "name": "required_linear_history", "in": "body", "rawType": "boolean", - "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", + "rawDescription": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "boolean or nullable", - "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", + "description": "

Permits force pushes to the protected branch by anyone with write access to the repository. Set to true to allow force pushes. Set to false or null to block force pushes. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.\"

", "nullable": true, "name": "allow_force_pushes", "in": "body", "rawType": "boolean", - "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "rawDescription": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", + "description": "

Allows deletion of the protected branch by anyone with write access to the repository. Set to false to prevent deletion of the protected branch. Default: false. For more information, see \"Enabling force pushes to a protected branch\" in the GitHub Help documentation.

", "name": "allow_deletions", "in": "body", "rawType": "boolean", - "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", + "rawDescription": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -32185,7 +32105,7 @@ } ], "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -32207,7 +32127,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -32269,7 +32189,7 @@ } ], "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -32291,7 +32211,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -32349,7 +32269,7 @@ } ], "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -32371,7 +32291,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -32429,7 +32349,7 @@ } ], "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -32451,7 +32371,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removing admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "204", @@ -32513,7 +32433,7 @@ } ], "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -32535,7 +32455,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -32593,7 +32513,7 @@ } ], "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -32687,11 +32607,11 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, "required_approving_review_count": { @@ -32810,7 +32730,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.

\n

Note: Passing new arrays of users and teams replaces their previous values.

", "responses": [ { "httpStatusCode": "200", @@ -32903,11 +32823,11 @@ }, { "type": "boolean", - "description": "

Blocks merging pull requests until code owners have reviewed.

", + "description": "

Blocks merging pull requests until code owners have reviewed.

", "name": "require_code_owner_reviews", "in": "body", "rawType": "boolean", - "rawDescription": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed.", + "rawDescription": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed.", "childParamsGroups": [] }, { @@ -33037,7 +32957,7 @@ } ], "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -33059,7 +32979,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -33121,7 +33041,7 @@ } ], "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -33143,7 +33063,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of true indicates you must sign commits on this branch. For more information, see Signing commits with GPG in GitHub Help.

\n

Note: You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -33206,7 +33126,7 @@ } ], "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -33228,7 +33148,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "200", @@ -33291,7 +33211,7 @@ } ], "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -33313,7 +33233,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

When authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.

", "responses": [ { "httpStatusCode": "204", @@ -33375,7 +33295,7 @@ } ], "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -33397,7 +33317,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -33460,7 +33380,7 @@ } ], "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -33583,7 +33503,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.

", "responses": [ { "httpStatusCode": "200", @@ -33736,7 +33656,7 @@ } ], "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -33758,7 +33678,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "204", @@ -33815,7 +33735,7 @@ } ], "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -33837,7 +33757,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -33900,7 +33820,7 @@ } ], "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -33966,7 +33886,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -34053,7 +33973,7 @@ } ], "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -34119,7 +34039,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -34201,7 +34121,7 @@ } ], "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -34266,7 +34186,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

", "bodyParameters": [ { "type": "array of strings", @@ -34348,7 +34268,7 @@ } ], "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -34370,7 +34290,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists who has access to this protected branch.

\n

Note: Users, apps, and teams restrictions are only available for organization-owned repositories.

", "responses": [ { "httpStatusCode": "200", @@ -34433,7 +34353,7 @@ } ], "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -34455,7 +34375,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Disables the ability to restrict who can push to this branch.

", "responses": [ { "httpStatusCode": "204", @@ -34512,7 +34432,7 @@ } ], "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -34534,7 +34454,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

", "responses": [ { "httpStatusCode": "200", @@ -34597,7 +34517,7 @@ } ], "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -34662,7 +34582,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified apps push access for this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -34739,7 +34659,7 @@ } ], "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -34804,7 +34724,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -34881,7 +34801,7 @@ } ], "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -34945,7 +34865,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of an app to push to this branch. Only installed GitHub Apps with write access to the contents permission can be added as authorized actors on a protected branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe GitHub Apps that have push access to this branch. Use the app's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -35022,7 +34942,7 @@ } ], "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -35044,7 +34964,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the teams who have push access to this branch. The list includes child teams.

", "responses": [ { "httpStatusCode": "200", @@ -35107,7 +35027,7 @@ } ], "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -35173,7 +35093,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified teams push access for this branch. You can also give push access to child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -35250,7 +35170,7 @@ } ], "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -35316,7 +35236,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayThe teams that can have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -35393,7 +35313,7 @@ } ], "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -35458,7 +35378,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a team to push to this branch. You can also remove push access for child teams.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayTeams that should no longer have push access. Use the team's slug. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -35535,7 +35455,7 @@ } ], "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -35557,7 +35477,7 @@ "subcategoryLabel": "Branch protection", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists the people who have push access to this branch.

", "responses": [ { "httpStatusCode": "200", @@ -35620,7 +35540,7 @@ } ], "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -35685,7 +35605,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Grants the specified people push access for this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -35762,7 +35682,7 @@ } ], "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -35827,7 +35747,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames for people who can have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -35904,7 +35824,7 @@ } ], "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -35968,7 +35888,7 @@ "subcategoryLabel": "Branch protection", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Removes the ability of a user to push to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDescription
arrayUsernames of the people who should no longer have push access. Note: The list of users, apps, and teams in total is limited to 100 items.
", "bodyParameters": [ { "type": "array of strings", @@ -36175,7 +36095,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -36278,7 +36198,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -36501,7 +36421,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -36604,7 +36524,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -37250,7 +37170,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -37353,7 +37273,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -37576,7 +37496,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the Checks and Files changed tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"About status checks\". See the annotations object description for details about how to use this parameter.

", "maxItems": 50, "items": { "type": "object", @@ -37679,7 +37599,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "childParamsGroups": [ { "parentName": "annotations", @@ -38334,7 +38254,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -38437,7 +38357,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -38659,7 +38579,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -38762,7 +38682,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -39365,7 +39285,7 @@ }, "annotations": { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -39468,7 +39388,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -39690,7 +39610,7 @@ }, { "type": "array of objects", - "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", + "description": "

Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the Update a check run endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"About status checks\". See the annotations object description for details.

", "maxItems": 50, "items": { "type": "object", @@ -39793,7 +39713,7 @@ "name": "annotations", "in": "body", "rawType": "array", - "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", + "rawDescription": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", "childParamsGroups": [ { "parentName": "annotations", @@ -42294,7 +42214,7 @@ } ], "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -42314,7 +42234,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must have push access to the repository in order to list collaborators.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "200", @@ -42375,7 +42295,7 @@ } ], "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -42395,7 +42315,7 @@ "categoryLabel": "Collaborators", "notes": [], "bodyParameters": [], - "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

", + "descriptionHTML": "

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

\n

Team members will include the members of child teams.

\n

You must authenticate using an access token with the read:org and repo scopes with push access to use this\nendpoint. GitHub Apps must have the members organization permission and metadata repository permission to use this\nendpoint.

", "responses": [ { "httpStatusCode": "204", @@ -42455,7 +42375,7 @@ } ], "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -42514,7 +42434,7 @@ "categoryLabel": "Collaborators", "contentType": "application/json", "notes": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

For more information on permission levels, see \"Repository permission levels for an organization\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:

\n
Cannot assign {member} permission of {role name}\n
\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

\n

The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the repository invitations API endpoints.

\n

Rate limits

\n

You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.

", "bodyParameters": [ { "type": "string", @@ -43666,7 +43586,7 @@ } ], "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -43686,7 +43606,7 @@ "categoryLabel": "Commits", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", + "descriptionHTML": "

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see GitHub's products in the GitHub Help documentation.

\n

Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.

", "responses": [ { "httpStatusCode": "200", @@ -52286,7 +52206,7 @@ } ], "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -52432,7 +52352,7 @@ "categoryLabel": "Issues", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "oneOf": [ @@ -53578,7 +53498,7 @@ } ], "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/github-ae@latest/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/github-ae@latest/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/github-ae@latest/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/github-ae@latest/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -53598,7 +53518,7 @@ "categoryLabel": "Issues", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", + "descriptionHTML": "

The API returns a 301 Moved Permanently status if the issue was\ntransferred to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a 404 Not Found status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a 410 Gone status. To receive webhook events for transferred and deleted issues, subscribe\nto the issues webhook.

\n

Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe pull_request key. Be aware that the id of a pull request returned from \"Issues\" endpoints will be an issue id. To find out the pull\nrequest id, use the \"List pull requests\" endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -56104,11 +56024,11 @@ }, "read_only": { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } }, @@ -56159,11 +56079,11 @@ }, { "type": "boolean", - "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", + "description": "

If true, the key will only be able to read repository contents. Otherwise, the key will be able to read and write.

\n

Deploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"Repository permission levels for an organization\" and \"Permission levels for a user account repository.\"

", "name": "read_only", "in": "body", "rawType": "boolean", - "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"", + "rawDescription": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"", "childParamsGroups": [] } ], @@ -58849,12 +58769,12 @@ "properties": { "cname": { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, "https_enforced": { @@ -58981,12 +58901,12 @@ "bodyParameters": [ { "type": "string or nullable", - "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", + "description": "

Specify a custom domain for the repository. Sending a null value will remove the custom domain. For more about custom domains, see \"Using a custom domain with GitHub Pages.\"

", "nullable": true, "name": "cname", "in": "body", "rawType": "string", - "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "rawDescription": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "childParamsGroups": [] }, { @@ -59830,7 +59750,7 @@ } ], "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -59850,7 +59770,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

", "responses": [ { "httpStatusCode": "200", @@ -59907,7 +59827,7 @@ } ], "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -59961,20 +59881,20 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, "draft": { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, "issue": { @@ -60013,7 +59933,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

\n

You can create a new pull request.

\n

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

", "bodyParameters": [ { "type": "string", @@ -60053,20 +59973,20 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] }, { "type": "boolean", - "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", + "description": "

Indicates whether the pull request is a draft. See \"Draft Pull Requests\" in the GitHub Help documentation to learn more.

", "name": "draft", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", + "rawDescription": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.", "childParamsGroups": [] }, { @@ -60909,7 +60829,7 @@ } ], "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/github-ae@latest/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/github-ae@latest/rest/reference/pulls#update-a-pull-request) a pull request, GitHub AE creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub AE has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/github-ae@latest/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/github-ae@latest/rest/reference/pulls#update-a-pull-request) a pull request, GitHub AE creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub AE has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -60929,7 +60849,7 @@ "categoryLabel": "Pulls", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub AE creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub AE has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

Lists details of a pull request by providing its number.

\n

When you get, create, or edit a pull request, GitHub AE creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the mergeable key. For more information, see \"Checking mergeability of pull requests\".

\n

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub AE has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.

\n

The value of the merge_commit_sha attribute changes depending on the state of the pull request. Before merging a pull request, the merge_commit_sha attribute holds the SHA of the test merge commit. After merging a pull request, the merge_commit_sha attribute changes depending on how you merged the pull request:

\n
    \n
  • If merged as a merge commit, merge_commit_sha represents the SHA of the merge commit.
    • \n
  • If merged via a squash, merge_commit_sha represents the SHA of the squashed commit on the base branch.
    • \n
  • If rebased, merge_commit_sha represents the commit that the base branch was updated to.
    • \n
\n

Pass the appropriate media type to fetch diff and patch formats.

", "responses": [ { "httpStatusCode": "200", @@ -61000,7 +60920,7 @@ } ], "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -61058,11 +60978,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } } @@ -61087,7 +61007,7 @@ "categoryLabel": "Pulls", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", + "descriptionHTML": "

Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.

", "bodyParameters": [ { "type": "string", @@ -61131,11 +61051,11 @@ }, { "type": "boolean", - "description": "

Indicates whether maintainers can modify the pull request.

", + "description": "

Indicates whether maintainers can modify the pull request.

", "name": "maintainer_can_modify", "in": "body", "rawType": "boolean", - "rawDescription": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", + "rawDescription": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.", "childParamsGroups": [] } ], @@ -61396,7 +61316,7 @@ }, "side": { "type": "string", - "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -61404,7 +61324,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "line": { @@ -61418,16 +61338,16 @@ }, "start_line": { "type": "integer", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, "start_side": { "type": "string", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -61436,7 +61356,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, "in_reply_to": { @@ -61535,7 +61455,7 @@ }, { "type": "string", - "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", + "description": "

Required with comfort-fade preview unless using in_reply_to. In a split diff view, the side of the diff that the pull request's changes appear on. Can be LEFT or RIGHT. Use LEFT for deletions that appear in red. Use RIGHT for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"Diff view options\" in the GitHub Help documentation.

", "enum": [ "LEFT", "RIGHT" @@ -61543,7 +61463,7 @@ "name": "side", "in": "body", "rawType": "string", - "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "rawDescription": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { @@ -61557,16 +61477,16 @@ }, { "type": "integer", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_line is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation.

", "name": "start_line", "in": "body", "rawType": "integer", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation.", "childParamsGroups": [] }, { "type": "string", - "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", + "description": "

Required when using multi-line comments unless using in_reply_to. To create multi-line comments, you must use the comfort-fade preview header. The start_side is the starting side of the diff that the comment applies to. Can be LEFT or RIGHT. To learn more about multi-line comments, see \"Commenting on a pull request\" in the GitHub Help documentation. See side in this table for additional context.

", "enum": [ "LEFT", "RIGHT", @@ -61575,7 +61495,7 @@ "name": "start_side", "in": "body", "rawType": "string", - "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "rawDescription": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "childParamsGroups": [] }, { @@ -67733,7 +67653,7 @@ } ], "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -67796,7 +67716,7 @@ "categoryLabel": "Repos", "contentType": "application/json", "notes": [], - "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", + "descriptionHTML": "

A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original owner, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see about repository transfers.

", "bodyParameters": [ { "type": "string", @@ -69107,13 +69027,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching code\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -69234,13 +69154,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching commits\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -69347,13 +69267,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching issues and pull requests\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -69622,13 +69542,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching for repositories\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -69789,7 +69709,7 @@ } ], "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/github-ae@latest/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/github-ae@latest/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -69809,7 +69729,7 @@ "categoryLabel": "Search", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", + "descriptionHTML": "

Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See \"Searching topics\" for a detailed list of qualifiers.

\n

When searching for topics, you can get text match metadata for the topic's short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.

\n

For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:

\n

q=ruby+is:featured

\n

This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.

", "responses": [ { "httpStatusCode": "200", @@ -69831,13 +69751,13 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { "type": "string" }, - "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" + "descriptionHTML": "

The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See \"Searching users\" for a detailed list of qualifiers.

" }, { "name": "sort", @@ -72017,7 +71937,7 @@ } ], "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -72042,7 +71962,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

The \"Add team member\" endpoint (described below) is deprecated.

\n

We recommend using the Add or update team membership for a user endpoint instead. It allows you to invite new organization members to your teams.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -72103,7 +72023,7 @@ } ], "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -72128,7 +72048,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

", + "descriptionHTML": "

The \"Remove team member\" endpoint (described below) is deprecated.

\n

We recommend using the Remove team membership for a user endpoint instead. It allows you to remove both active and pending memberships.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

", "responses": [ { "httpStatusCode": "204", @@ -72256,7 +72176,7 @@ } ], "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -72307,7 +72227,7 @@ "subcategoryLabel": "Members", "contentType": "application/json", "notes": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Add or update team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

If the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

\n

If the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.

\n

If the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.

", "bodyParameters": [ { "type": "string", @@ -72385,7 +72305,7 @@ } ], "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -72410,7 +72330,7 @@ "subcategoryLabel": "Members", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

", + "descriptionHTML": "

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove team membership for a user endpoint.

\n

Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see GitHub's products in the GitHub Help documentation.

\n

To remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.

\n

Note: When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"Synchronizing teams between your identity provider and GitHub AE.\"

", "responses": [ { "httpStatusCode": "204", @@ -78724,7 +78644,7 @@ } ], "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/github-ae@latest/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/github-ae@latest/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -78744,7 +78664,7 @@ "categoryLabel": "Orgs", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", + "descriptionHTML": "

List public organization memberships for the specified user.

\n

This method only lists public memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the List organizations for the authenticated user API instead.

", "responses": [ { "httpStatusCode": "200", @@ -79196,7 +79116,7 @@ } ], "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -79214,11 +79134,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -79239,7 +79159,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a 403 response.

\n

You can suspend any user account except your own.

\n

Note that, if you choose not to pass any parameters, you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see \"HTTP verbs.\"

", "responses": [ { "httpStatusCode": "204", @@ -79250,11 +79170,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being suspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Suspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] @@ -79287,7 +79207,7 @@ } ], "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -79305,11 +79225,11 @@ "properties": { "reason": { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } } @@ -79330,7 +79250,7 @@ "subcategoryLabel": "Users", "contentType": "application/json", "notes": [], - "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", + "descriptionHTML": "

If your GitHub instance uses LDAP Sync with Active Directory LDAP servers, this API is disabled and will return a 403 response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.

", "responses": [ { "httpStatusCode": "204", @@ -79341,11 +79261,11 @@ "bodyParameters": [ { "type": "string", - "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", + "description": "

The reason the user is being unsuspended. This message will be logged in the audit log. If you don't provide a reason, it will default to \"Unsuspended via API by SITE_ADMINISTRATOR\", where SITE_ADMINISTRATOR is the person who performed the action.

", "name": "reason", "in": "body", "rawType": "string", - "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action.", "childParamsGroups": [] } ] diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 2de5b76484..16f9f63854 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -9791,7 +9791,7 @@ "/apps/{app_slug}": { "get": { "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -11004,7 +11004,7 @@ }, "post": { "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub will discontinue the [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub will discontinue the [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -25408,7 +25408,7 @@ "/enterprises/{enterprise}/settings/billing/actions": { "get": { "summary": "Get GitHub Actions billing for an enterprise", - "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nThe authenticated user must be an enterprise admin.", + "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nThe authenticated user must be an enterprise admin.", "operationId": "billing/get-github-actions-billing-ghe", "tags": [ "billing" @@ -25671,7 +25671,7 @@ "/enterprises/{enterprise}/settings/billing/packages": { "get": { "summary": "Get GitHub Packages billing for an enterprise", - "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", + "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", "operationId": "billing/get-github-packages-billing-ghe", "tags": [ "billing" @@ -25742,7 +25742,7 @@ "/enterprises/{enterprise}/settings/billing/shared-storage": { "get": { "summary": "Get shared storage billing for an enterprise", - "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", + "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nThe authenticated user must be an enterprise admin.", "operationId": "billing/get-shared-storage-billing-ghe", "tags": [ "billing" @@ -46137,7 +46137,7 @@ "/meta": { "get": { "summary": "Get GitHub meta information", - "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://help.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", + "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://docs.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", "tags": [ "meta" ], @@ -54420,7 +54420,7 @@ "/orgs/{org}": { "get": { "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub plan information' below.\"", "tags": [ "orgs" ], @@ -54878,15 +54878,15 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_private_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_public_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_allowed_repository_creation_type": { "type": "string", @@ -67410,7 +67410,7 @@ "/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.", + "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 or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `security_events` read permission to use this endpoint.", "tags": [ "code-scanning" ], @@ -67480,7 +67480,7 @@ }, { "name": "state", - "description": "Set to `open`, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", + "description": "Set to `open`, `closed, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", "in": "query", "required": false, "schema": { @@ -70218,7 +70218,7 @@ "/orgs/{org}/credential-authorizations": { "get": { "summary": "List SAML SSO authorizations for an organization", - "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `read:org` scope can list all credential authorizations for an organization that uses SAML single sign-on (SSO). The credentials are either personal access tokens or SSH keys that organization members have authorized for the organization. For more information, see [About authentication with SAML single sign-on](https://help.github.com/en/articles/about-authentication-with-saml-single-sign-on).", + "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `read:org` scope can list all credential authorizations for an organization that uses SAML single sign-on (SSO). The credentials are either personal access tokens or SSH keys that organization members have authorized for the organization. For more information, see [About authentication with SAML single sign-on](https://docs.github.com/en/articles/about-authentication-with-saml-single-sign-on).", "tags": [ "orgs" ], @@ -70401,7 +70401,7 @@ "/orgs/{org}/credential-authorizations/{credential_id}": { "delete": { "summary": "Remove a SAML SSO authorization for an organization", - "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `admin:org` scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.", + "description": "Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products).\n\nAn authenticated organization owner with the `admin:org` scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.", "tags": [ "orgs" ], @@ -93148,7 +93148,7 @@ "/orgs/{org}/outside_collaborators/{username}": { "put": { "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -101540,7 +101540,7 @@ }, "visibility": { "type": "string", - "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "enum": [ "public", "private", @@ -101582,7 +101582,7 @@ }, "license_template": { "type": "string", - "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." + "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." }, "allow_squash_merge": { "type": "boolean", @@ -102979,7 +102979,7 @@ "/orgs/{org}/secret-scanning/alerts": { "get": { "summary": "List secret scanning alerts for an organization", - "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\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 `secret_scanning_alerts` read permission to use this endpoint.", + "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\nTo use this endpoint, you must be an administrator or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `secret_scanning_alerts` read permission to use this endpoint.", "tags": [ "secret-scanning" ], @@ -105484,7 +105484,7 @@ "/orgs/{org}/settings/billing/actions": { "get": { "summary": "Get GitHub Actions billing for an organization", - "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `repo` or `admin:org` scope.", + "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `repo` or `admin:org` scope.", "operationId": "billing/get-github-actions-billing-org", "tags": [ "billing" @@ -105745,7 +105745,7 @@ "/orgs/{org}/settings/billing/packages": { "get": { "summary": "Get GitHub Packages billing for an organization", - "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", + "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", "operationId": "billing/get-github-packages-billing-org", "tags": [ "billing" @@ -105815,7 +105815,7 @@ "/orgs/{org}/settings/billing/shared-storage": { "get": { "summary": "Get shared storage billing for an organization", - "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", + "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `repo` or `admin:org` scope.", "operationId": "billing/get-shared-storage-billing-org", "tags": [ "billing" @@ -105885,7 +105885,7 @@ "/orgs/{org}/team-sync/groups": { "get": { "summary": "List IdP groups for an organization", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups available in an organization. You can limit your page results using the `per_page` parameter. GitHub generates a url-encoded `page` token using a cursor value for where the next page begins. For more information on cursor pagination, see \"[Offset and Cursor Pagination explained](https://dev.to/jackmarchant/offset-and-cursor-pagination-explained-b89).\"", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups available in an organization. You can limit your page results using the `per_page` parameter. GitHub generates a url-encoded `page` token using a cursor value for where the next page begins. For more information on cursor pagination, see \"[Offset and Cursor Pagination explained](https://dev.to/jackmarchant/offset-and-cursor-pagination-explained-b89).\"", "tags": [ "teams" ], @@ -106302,7 +106302,7 @@ }, "post": { "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -113983,7 +113983,7 @@ }, "put": { "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -114108,7 +114108,7 @@ }, "delete": { "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -118890,7 +118890,7 @@ }, "put": { "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -119032,7 +119032,7 @@ "/orgs/{org}/teams/{team_slug}/team-sync/group-mappings": { "get": { "summary": "List IdP groups for a team", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `GET /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `GET /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", "tags": [ "teams" ], @@ -119155,7 +119155,7 @@ }, "patch": { "summary": "Create or update IdP group connections", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PATCH /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PATCH /organizations/{org_id}/team/{team_id}/team-sync/group-mappings`.", "tags": [ "teams" ], @@ -125023,125 +125023,6 @@ } } }, - "/reactions/{reaction_id}": { - "delete": { - "summary": "Delete a reaction (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/rest/reference/teams#discussion-comments).", - "tags": [ - "reactions" - ], - "operationId": "reactions/delete-legacy", - "externalDocs": { - "description": "API method documentation", - "url": "https://docs.github.com/rest/reference/reactions/#delete-a-reaction-legacy" - }, - "parameters": [ - { - "name": "reaction_id", - "in": "path", - "required": true, - "schema": { - "type": "integer" - } - } - ], - "responses": { - "204": { - "description": "Response" - }, - "304": { - "description": "Not modified" - }, - "403": { - "description": "Forbidden", - "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" - } - } - } - } - } - }, - "401": { - "description": "Requires authentication", - "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" - } - } - } - } - } - }, - "410": { - "description": "Gone", - "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, - "removalDate": "2021-02-21", - "deprecationDate": "2020-02-26", - "category": "reactions", - "subcategory": null - }, - "deprecated": true - } - }, "/repos/{owner}/{repo}": { "get": { "summary": "Get a repository", @@ -129953,7 +129834,7 @@ }, "private": { "type": "boolean", - "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "default": false }, "visibility": { @@ -140056,7 +139937,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -154818,7 +154699,7 @@ "/repos/{owner}/{repo}/actions/runs/{run_id}/timing": { "get": { "summary": "Get workflow run usage", - "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", + "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", "tags": [ "actions" ], @@ -155903,7 +155784,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches": { "post": { "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -156117,7 +155998,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -160086,7 +159967,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/timing": { "get": { "summary": "Get workflow usage", - "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", + "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub-hosted runners. Usage is listed for each GitHub-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", "tags": [ "actions" ], @@ -160205,7 +160086,7 @@ "/repos/{owner}/{repo}/assignees": { "get": { "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -161003,7 +160884,7 @@ "/repos/{owner}/{repo}/automated-security-fixes": { "put": { "summary": "Enable automated security fixes", - "description": "Enables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://help.github.com/en/articles/configuring-automated-security-fixes)\".", + "description": "Enables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://docs.github.com/en/articles/configuring-automated-security-fixes)\".", "tags": [ "repos" ], @@ -161044,7 +160925,7 @@ }, "delete": { "summary": "Disable automated security fixes", - "description": "Disables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://help.github.com/en/articles/configuring-automated-security-fixes)\".", + "description": "Disables automated security fixes for a repository. The authenticated user must have admin access to the repository. For more information, see \"[Configuring automated security fixes](https://docs.github.com/en/articles/configuring-automated-security-fixes)\".", "tags": [ "repos" ], @@ -164064,7 +163945,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection": { "get": { "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -165364,7 +165245,7 @@ }, "put": { "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -165487,7 +165368,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them." }, "required_approving_review_count": { "type": "integer", @@ -165550,16 +165431,16 @@ }, "required_linear_history": { "type": "boolean", - "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." + "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." }, "allow_force_pushes": { "type": "boolean", - "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "nullable": true }, "allow_deletions": { "type": "boolean", - "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." + "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." }, "required_conversation_resolution": { "type": "boolean", @@ -166787,7 +166668,7 @@ }, "delete": { "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -166866,7 +166747,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/enforce_admins": { "get": { "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -166949,7 +166830,7 @@ }, "post": { "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -167032,7 +166913,7 @@ }, "delete": { "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -167111,7 +166992,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_pull_request_reviews": { "get": { "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -167855,7 +167736,7 @@ }, "patch": { "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -167925,7 +167806,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed." }, "required_approving_review_count": { "type": "integer", @@ -168754,7 +168635,7 @@ }, "delete": { "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -168833,7 +168714,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_signatures": { "get": { "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -168942,7 +168823,7 @@ }, "post": { "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -169051,7 +168932,7 @@ }, "delete": { "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -169130,7 +169011,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks": { "get": { "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -169280,7 +169161,7 @@ }, "patch": { "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -169549,7 +169430,7 @@ }, "delete": { "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -169602,7 +169483,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks/contexts": { "get": { "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -169692,7 +169573,7 @@ }, "post": { "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -169917,7 +169798,7 @@ }, "put": { "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -170115,7 +169996,7 @@ }, "delete": { "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -170314,7 +170195,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions": { "get": { "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -170763,7 +170644,7 @@ }, "delete": { "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -170816,7 +170697,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/apps": { "get": { "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -171192,7 +171073,7 @@ }, "post": { "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -171649,7 +171530,7 @@ }, "put": { "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -172106,7 +171987,7 @@ }, "delete": { "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -172564,7 +172445,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/teams": { "get": { "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -172832,7 +172713,7 @@ }, "post": { "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -173182,7 +173063,7 @@ }, "put": { "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -173532,7 +173413,7 @@ }, "delete": { "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -173883,7 +173764,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/users": { "get": { "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -174112,7 +173993,7 @@ }, "post": { "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -174422,7 +174303,7 @@ }, "put": { "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -174732,7 +174613,7 @@ }, "delete": { "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -177066,7 +176947,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "maxItems": 50, "items": { "type": "object", @@ -179278,7 +179159,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/rest/reference/checks#annotations-object-1) description for details.", "maxItems": 50, "items": { "type": "object", @@ -191528,7 +191409,7 @@ }, { "name": "state", - "description": "Set to `open`, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", + "description": "Set to `open`, `closed, `fixed`, or `dismissed` to list code scanning alerts in a specific state.", "in": "query", "required": false, "schema": { @@ -202423,7 +202304,7 @@ "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -202719,7 +202600,7 @@ "/repos/{owner}/{repo}/collaborators/{username}": { "get": { "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -202771,7 +202652,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -208362,7 +208243,7 @@ "/repos/{owner}/{repo}/commits/{commit_sha}/branches-where-head": { "get": { "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -229430,7 +229311,7 @@ "/repos/{owner}/{repo}/dispatches": { "post": { "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -248763,7 +248644,7 @@ "/repos/{owner}/{repo}/import/lfs": { "patch": { "summary": "Update Git LFS preference", - "description": "You can import repositories from Subversion, Mercurial, and TFS that include files larger than 100MB. This ability is powered by [Git LFS](https://git-lfs.github.com). You can learn more about our LFS feature and working with large files [on our help site](https://help.github.com/articles/versioning-large-files/).", + "description": "You can import repositories from Subversion, Mercurial, and TFS that include files larger than 100MB. This ability is powered by [Git LFS](https://git-lfs.github.com). You can learn more about our LFS feature and working with large files [on our help site](https://docs.github.com/articles/versioning-large-files/).", "tags": [ "migrations" ], @@ -257313,7 +257194,7 @@ }, "post": { "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -270784,7 +270665,7 @@ "/repos/{owner}/{repo}/issues/{issue_number}": { "get": { "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -304711,7 +304592,7 @@ }, "read_only": { "type": "boolean", - "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"" + "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"" } }, "required": [ @@ -311513,7 +311394,7 @@ "properties": { "cname": { "type": "string", - "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "nullable": true }, "https_enforced": { @@ -314061,7 +313942,7 @@ "/repos/{owner}/{repo}/pulls": { "get": { "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -318636,7 +318517,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -318688,11 +318569,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." }, "draft": { "type": "boolean", - "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." + "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." }, "issue": { "type": "integer", @@ -324680,7 +324561,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}": { "get": { "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/rest/reference/pulls#update-a-pull-request) a pull request, GitHub creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/rest/reference/pulls#update-a-pull-request) a pull request, GitHub creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -327997,7 +327878,7 @@ }, "patch": { "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -328061,7 +327942,7 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." } } }, @@ -336816,7 +336697,7 @@ }, "side": { "type": "string", - "description": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "description": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "enum": [ "LEFT", "RIGHT" @@ -336828,11 +336709,11 @@ }, "start_line": { "type": "integer", - "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." + "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." }, "start_side": { "type": "string", - "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "enum": [ "LEFT", "RIGHT", @@ -363128,7 +363009,7 @@ "/repos/{owner}/{repo}/transfer": { "post": { "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -365109,7 +364990,7 @@ "/repos/{owner}/{repo}/vulnerability-alerts": { "get": { "summary": "Check if vulnerability alerts are enabled for a repository", - "description": "Shows whether dependency alerts are enabled or disabled for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://help.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", + "description": "Shows whether dependency alerts are enabled or disabled for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://docs.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", "tags": [ "repos" ], @@ -365153,7 +365034,7 @@ }, "put": { "summary": "Enable vulnerability alerts", - "description": "Enables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://help.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", + "description": "Enables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://docs.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", "tags": [ "repos" ], @@ -365194,7 +365075,7 @@ }, "delete": { "summary": "Disable vulnerability alerts", - "description": "Disables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://help.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", + "description": "Disables dependency alerts and the dependency graph for a repository. The authenticated user must have admin access to the repository. For more information, see \"[About security alerts for vulnerable dependencies](https://docs.github.com/en/articles/about-security-alerts-for-vulnerable-dependencies)\".", "tags": [ "repos" ], @@ -374305,7 +374186,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -376385,7 +376266,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -378638,7 +378519,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -381540,7 +381421,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -382429,7 +382310,7 @@ "/search/topics": { "get": { "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -382769,7 +382650,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -389949,7 +389830,7 @@ }, "put": { "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -390025,7 +389906,7 @@ }, "delete": { "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -390192,7 +390073,7 @@ }, "put": { "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -390337,7 +390218,7 @@ }, "delete": { "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -395562,7 +395443,7 @@ "/teams/{team_id}/team-sync/group-mappings": { "get": { "summary": "List IdP groups for a team (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`List IdP groups for a team`](https://docs.github.com/rest/reference/teams#list-idp-groups-for-a-team) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`List IdP groups for a team`](https://docs.github.com/rest/reference/teams#list-idp-groups-for-a-team) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nList IdP groups connected to a team on GitHub.", "tags": [ "teams" ], @@ -395731,7 +395612,7 @@ }, "patch": { "summary": "Create or update IdP group connections (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`Create or update IdP group connections`](https://docs.github.com/rest/reference/teams#create-or-update-idp-group-connections) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [`Create or update IdP group connections`](https://docs.github.com/rest/reference/teams#create-or-update-idp-group-connections) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nCreates, updates, or removes a connection between a team and an IdP group. When adding groups to a team, you must include all new and existing groups to avoid replacing existing groups with the new ones. Specifying an empty `groups` array will remove all connections for a team.", "tags": [ "teams" ], @@ -467449,7 +467330,7 @@ "/users/{username}/orgs": { "get": { "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -481129,7 +481010,7 @@ "/users/{username}/settings/billing/actions": { "get": { "summary": "Get GitHub Actions billing for a user", - "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `user` scope.", + "description": "Gets the summary of the free and paid GitHub Actions minutes used.\n\nPaid minutes only apply to workflows in private repositories that use GitHub-hosted runners. Minutes used is listed for each GitHub-hosted runner operating system. Any job re-runs are also included in the usage. The usage returned includes any minute multipliers for macOS and Windows runners, and is rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAccess tokens must have the `user` scope.", "operationId": "billing/get-github-actions-billing-user", "tags": [ "billing" @@ -481222,7 +481103,7 @@ "/users/{username}/settings/billing/packages": { "get": { "summary": "Get GitHub Packages billing for a user", - "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", + "description": "Gets the free and paid storage used for GitHub Packages in gigabytes.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", "operationId": "billing/get-github-packages-billing-user", "tags": [ "billing" @@ -481292,7 +481173,7 @@ "/users/{username}/settings/billing/shared-storage": { "get": { "summary": "Get shared storage billing for a user", - "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", + "description": "Gets the estimated paid and estimated total storage used for GitHub Actions and Github Packages.\n\nPaid minutes only apply to packages stored for private repositories. For more information, see \"[Managing billing for GitHub Packages](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages).\"\n\nAccess tokens must have the `user` scope.", "operationId": "billing/get-shared-storage-billing-user", "tags": [ "billing" diff --git a/lib/rest/static/dereferenced/ghes-3.0.deref.json b/lib/rest/static/dereferenced/ghes-3.0.deref.json index 233d9bd41e..fd6566beb1 100644 --- a/lib/rest/static/dereferenced/ghes-3.0.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.0.deref.json @@ -1343,7 +1343,7 @@ "/admin/ldap/teams/{team_id}/mapping": { "patch": { "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.0/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.0/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -4808,7 +4808,7 @@ }, "email": { "type": "string", - "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." + "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." } }, "required": [ @@ -15933,7 +15933,7 @@ "/apps/{app_slug}": { "get": { "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -17160,7 +17160,7 @@ }, "post": { "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.0/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.0/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.0/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.0/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.0/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.0/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -54956,7 +54956,7 @@ "/orgs/{org}": { "get": { "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.0/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -55419,15 +55419,15 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_private_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_public_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_allowed_repository_creation_type": { "type": "string", @@ -76567,7 +76567,7 @@ "/orgs/{org}/outside_collaborators/{username}": { "put": { "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -80250,7 +80250,7 @@ }, "visibility": { "type": "string", - "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", + "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", "enum": [ "public", "private", @@ -80292,7 +80292,7 @@ }, "license_template": { "type": "string", - "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." + "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." }, "allow_squash_merge": { "type": "boolean", @@ -81956,7 +81956,7 @@ }, "post": { "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -89172,7 +89172,7 @@ }, "put": { "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -89297,7 +89297,7 @@ }, "delete": { "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -94057,7 +94057,7 @@ }, "put": { "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -105388,7 +105388,7 @@ }, "private": { "type": "boolean", - "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "default": false }, "visibility": { @@ -114423,7 +114423,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -124000,7 +124000,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches": { "post": { "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -124214,7 +124214,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -128149,7 +128149,7 @@ "/repos/{owner}/{repo}/assignees": { "get": { "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -130814,7 +130814,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection": { "get": { "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -131802,7 +131802,7 @@ }, "put": { "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -131925,7 +131925,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them." }, "required_approving_review_count": { "type": "integer", @@ -131967,16 +131967,16 @@ }, "required_linear_history": { "type": "boolean", - "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." + "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." }, "allow_force_pushes": { "type": "boolean", - "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "nullable": true }, "allow_deletions": { "type": "boolean", - "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." + "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." }, "required_conversation_resolution": { "type": "boolean", @@ -132898,7 +132898,7 @@ }, "delete": { "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -132977,7 +132977,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/enforce_admins": { "get": { "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -133060,7 +133060,7 @@ }, "post": { "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -133143,7 +133143,7 @@ }, "delete": { "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -133222,7 +133222,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_pull_request_reviews": { "get": { "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -133674,7 +133674,7 @@ }, "patch": { "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -133744,7 +133744,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed." }, "required_approving_review_count": { "type": "integer", @@ -134260,7 +134260,7 @@ }, "delete": { "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -134339,7 +134339,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_signatures": { "get": { "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -134454,7 +134454,7 @@ }, "post": { "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -134569,7 +134569,7 @@ }, "delete": { "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -134654,7 +134654,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks": { "get": { "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -134783,7 +134783,7 @@ }, "patch": { "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -135011,7 +135011,7 @@ }, "delete": { "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135064,7 +135064,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks/contexts": { "get": { "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135154,7 +135154,7 @@ }, "post": { "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135379,7 +135379,7 @@ }, "put": { "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135577,7 +135577,7 @@ }, "delete": { "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135776,7 +135776,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions": { "get": { "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -136225,7 +136225,7 @@ }, "delete": { "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -136278,7 +136278,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/apps": { "get": { "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -136654,7 +136654,7 @@ }, "post": { "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -137111,7 +137111,7 @@ }, "put": { "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -137568,7 +137568,7 @@ }, "delete": { "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -138026,7 +138026,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/teams": { "get": { "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -138294,7 +138294,7 @@ }, "post": { "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -138644,7 +138644,7 @@ }, "put": { "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -138994,7 +138994,7 @@ }, "delete": { "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -139345,7 +139345,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/users": { "get": { "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -139574,7 +139574,7 @@ }, "post": { "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -139884,7 +139884,7 @@ }, "put": { "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -140194,7 +140194,7 @@ }, "delete": { "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -140609,7 +140609,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "maxItems": 50, "items": { "type": "object", @@ -142821,7 +142821,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.0/rest/reference/checks#annotations-object-1) description for details.", "maxItems": 50, "items": { "type": "object", @@ -157046,7 +157046,7 @@ "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -157334,7 +157334,7 @@ "/repos/{owner}/{repo}/collaborators/{username}": { "get": { "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -157386,7 +157386,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -162980,7 +162980,7 @@ "/repos/{owner}/{repo}/commits/{commit_sha}/branches-where-head": { "get": { "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -183456,7 +183456,7 @@ "/repos/{owner}/{repo}/dispatches": { "post": { "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -206511,7 +206511,7 @@ }, "post": { "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -216142,7 +216142,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -219989,7 +219989,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -219998,7 +219998,7 @@ "/repos/{owner}/{repo}/issues/{issue_number}": { "get": { "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.0/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -239733,7 +239733,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -253743,7 +253743,7 @@ }, { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -253922,7 +253922,7 @@ }, "read_only": { "type": "boolean", - "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"" + "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"" } }, "required": [ @@ -260518,7 +260518,7 @@ "properties": { "cname": { "type": "string", - "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "nullable": true }, "https_enforced": { @@ -263117,7 +263117,7 @@ "/repos/{owner}/{repo}/pulls": { "get": { "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -267519,7 +267519,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -267571,11 +267571,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." }, "draft": { "type": "boolean", - "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." + "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." }, "issue": { "type": "integer", @@ -273452,7 +273452,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}": { "get": { "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.0/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -276617,7 +276617,7 @@ }, "patch": { "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -276681,7 +276681,7 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." } } }, @@ -280509,7 +280509,7 @@ }, "side": { "type": "string", - "description": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "description": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "enum": [ "LEFT", "RIGHT" @@ -280521,11 +280521,11 @@ }, "start_line": { "type": "integer", - "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." + "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." }, "start_side": { "type": "string", - "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "enum": [ "LEFT", "RIGHT", @@ -303781,7 +303781,7 @@ "/repos/{owner}/{repo}/transfer": { "post": { "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -309005,7 +309005,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -311072,7 +311072,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -313317,7 +313317,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -316210,7 +316210,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -317101,7 +317101,7 @@ "/search/topics": { "get": { "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.0/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.0/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -317468,7 +317468,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.0/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -325688,7 +325688,7 @@ }, "put": { "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -325764,7 +325764,7 @@ }, "delete": { "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -325931,7 +325931,7 @@ }, "put": { "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -326076,7 +326076,7 @@ }, "delete": { "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.0/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -367058,7 +367058,7 @@ "/users/{username}/orgs": { "get": { "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.0/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.0/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -379888,7 +379888,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -379921,7 +379921,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } @@ -379937,7 +379937,7 @@ }, "delete": { "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -379970,7 +379970,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json index d462630812..a66883311d 100644 --- a/lib/rest/static/dereferenced/ghes-3.1.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json @@ -1343,7 +1343,7 @@ "/admin/ldap/teams/{team_id}/mapping": { "patch": { "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.1/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.1/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -4808,7 +4808,7 @@ }, "email": { "type": "string", - "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." + "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." } }, "required": [ @@ -15933,7 +15933,7 @@ "/apps/{app_slug}": { "get": { "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -17160,7 +17160,7 @@ }, "post": { "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.1/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.1/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.1/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.1/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.1/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.1/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -54981,7 +54981,7 @@ "/orgs/{org}": { "get": { "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.1/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -55444,15 +55444,15 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_private_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_public_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_allowed_repository_creation_type": { "type": "string", @@ -76592,7 +76592,7 @@ "/orgs/{org}/outside_collaborators/{username}": { "put": { "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -80275,7 +80275,7 @@ }, "visibility": { "type": "string", - "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", + "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation. \nThe `visibility` parameter overrides the `private` parameter when you use both parameters with the `nebula-preview` preview header.", "enum": [ "public", "private", @@ -80317,7 +80317,7 @@ }, "license_template": { "type": "string", - "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." + "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." }, "allow_squash_merge": { "type": "boolean", @@ -81981,7 +81981,7 @@ }, "post": { "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -89197,7 +89197,7 @@ }, "put": { "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -89322,7 +89322,7 @@ }, "delete": { "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -94082,7 +94082,7 @@ }, "put": { "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -105413,7 +105413,7 @@ }, "private": { "type": "boolean", - "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "default": false }, "visibility": { @@ -114448,7 +114448,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -124025,7 +124025,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches": { "post": { "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -124239,7 +124239,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -128174,7 +128174,7 @@ "/repos/{owner}/{repo}/assignees": { "get": { "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -130839,7 +130839,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection": { "get": { "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -131827,7 +131827,7 @@ }, "put": { "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -131950,7 +131950,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them." }, "required_approving_review_count": { "type": "integer", @@ -131992,16 +131992,16 @@ }, "required_linear_history": { "type": "boolean", - "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." + "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." }, "allow_force_pushes": { "type": "boolean", - "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "nullable": true }, "allow_deletions": { "type": "boolean", - "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." + "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." }, "required_conversation_resolution": { "type": "boolean", @@ -132923,7 +132923,7 @@ }, "delete": { "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -133002,7 +133002,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/enforce_admins": { "get": { "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -133085,7 +133085,7 @@ }, "post": { "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -133168,7 +133168,7 @@ }, "delete": { "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -133247,7 +133247,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_pull_request_reviews": { "get": { "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -133699,7 +133699,7 @@ }, "patch": { "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -133769,7 +133769,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed." }, "required_approving_review_count": { "type": "integer", @@ -134285,7 +134285,7 @@ }, "delete": { "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -134364,7 +134364,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_signatures": { "get": { "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -134479,7 +134479,7 @@ }, "post": { "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -134594,7 +134594,7 @@ }, "delete": { "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -134679,7 +134679,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks": { "get": { "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -134808,7 +134808,7 @@ }, "patch": { "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -135036,7 +135036,7 @@ }, "delete": { "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135089,7 +135089,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks/contexts": { "get": { "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135179,7 +135179,7 @@ }, "post": { "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135404,7 +135404,7 @@ }, "put": { "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135602,7 +135602,7 @@ }, "delete": { "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135801,7 +135801,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions": { "get": { "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -136250,7 +136250,7 @@ }, "delete": { "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -136303,7 +136303,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/apps": { "get": { "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -136679,7 +136679,7 @@ }, "post": { "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -137136,7 +137136,7 @@ }, "put": { "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -137593,7 +137593,7 @@ }, "delete": { "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -138051,7 +138051,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/teams": { "get": { "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -138319,7 +138319,7 @@ }, "post": { "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -138669,7 +138669,7 @@ }, "put": { "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -139019,7 +139019,7 @@ }, "delete": { "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -139370,7 +139370,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/users": { "get": { "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -139599,7 +139599,7 @@ }, "post": { "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -139909,7 +139909,7 @@ }, "put": { "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -140219,7 +140219,7 @@ }, "delete": { "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -142235,7 +142235,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "maxItems": 50, "items": { "type": "object", @@ -144447,7 +144447,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.1/rest/reference/checks#annotations-object-1) description for details.", "maxItems": 50, "items": { "type": "object", @@ -159592,7 +159592,7 @@ "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -159880,7 +159880,7 @@ "/repos/{owner}/{repo}/collaborators/{username}": { "get": { "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -159932,7 +159932,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -165526,7 +165526,7 @@ "/repos/{owner}/{repo}/commits/{commit_sha}/branches-where-head": { "get": { "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -186155,7 +186155,7 @@ "/repos/{owner}/{repo}/dispatches": { "post": { "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -209210,7 +209210,7 @@ }, "post": { "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -218841,7 +218841,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -222688,7 +222688,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -222697,7 +222697,7 @@ "/repos/{owner}/{repo}/issues/{issue_number}": { "get": { "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.1/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -242432,7 +242432,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -256442,7 +256442,7 @@ }, { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -256621,7 +256621,7 @@ }, "read_only": { "type": "boolean", - "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"" + "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"" } }, "required": [ @@ -263217,7 +263217,7 @@ "properties": { "cname": { "type": "string", - "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "nullable": true }, "https_enforced": { @@ -265816,7 +265816,7 @@ "/repos/{owner}/{repo}/pulls": { "get": { "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -270371,7 +270371,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -270423,11 +270423,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." }, "draft": { "type": "boolean", - "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." + "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." }, "issue": { "type": "integer", @@ -276456,7 +276456,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}": { "get": { "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.1/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.1/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -279773,7 +279773,7 @@ }, "patch": { "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -279837,7 +279837,7 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." } } }, @@ -283817,7 +283817,7 @@ }, "side": { "type": "string", - "description": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "description": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "enum": [ "LEFT", "RIGHT" @@ -283829,11 +283829,11 @@ }, "start_line": { "type": "integer", - "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." + "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." }, "start_side": { "type": "string", - "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "enum": [ "LEFT", "RIGHT", @@ -308385,7 +308385,7 @@ "/repos/{owner}/{repo}/transfer": { "post": { "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -313609,7 +313609,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -315676,7 +315676,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -317921,7 +317921,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -320814,7 +320814,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -321705,7 +321705,7 @@ "/search/topics": { "get": { "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.1/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.1/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -322072,7 +322072,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.1/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -330292,7 +330292,7 @@ }, "put": { "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -330368,7 +330368,7 @@ }, "delete": { "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -330535,7 +330535,7 @@ }, "put": { "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -330680,7 +330680,7 @@ }, "delete": { "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.1/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -371685,7 +371685,7 @@ "/users/{username}/orgs": { "get": { "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.1/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.1/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -384515,7 +384515,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -384548,7 +384548,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } @@ -384564,7 +384564,7 @@ }, "delete": { "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -384597,7 +384597,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json index 36586c388d..3cb8173e58 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -1343,7 +1343,7 @@ "/admin/ldap/teams/{team_id}/mapping": { "patch": { "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.2/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.2/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.\n\nIf you pass the `hellcat-preview` media type, you can also update the LDAP mapping of a child team.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -4813,7 +4813,7 @@ }, "email": { "type": "string", - "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." + "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." } }, "required": [ @@ -16785,7 +16785,7 @@ "/apps/{app_slug}": { "get": { "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -18017,7 +18017,7 @@ }, "post": { "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.2/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.2/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.2/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.2/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.2/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.2/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -55964,7 +55964,7 @@ "/orgs/{org}": { "get": { "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.2/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -56427,15 +56427,15 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_private_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_public_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_allowed_repository_creation_type": { "type": "string", @@ -78529,7 +78529,7 @@ "/orgs/{org}/outside_collaborators/{username}": { "put": { "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -82221,7 +82221,7 @@ }, "visibility": { "type": "string", - "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "enum": [ "public", "private", @@ -82263,7 +82263,7 @@ }, "license_template": { "type": "string", - "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." + "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." }, "allow_squash_merge": { "type": "boolean", @@ -83936,7 +83936,7 @@ }, "post": { "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -91152,7 +91152,7 @@ }, "put": { "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -91277,7 +91277,7 @@ }, "delete": { "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -96064,7 +96064,7 @@ }, "put": { "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -107472,7 +107472,7 @@ }, "private": { "type": "boolean", - "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "default": false }, "visibility": { @@ -116627,7 +116627,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -127628,7 +127628,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches": { "post": { "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -127842,7 +127842,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -131795,7 +131795,7 @@ "/repos/{owner}/{repo}/assignees": { "get": { "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -134460,7 +134460,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection": { "get": { "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -135448,7 +135448,7 @@ }, "put": { "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -135571,7 +135571,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them." }, "required_approving_review_count": { "type": "integer", @@ -135613,16 +135613,16 @@ }, "required_linear_history": { "type": "boolean", - "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." + "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." }, "allow_force_pushes": { "type": "boolean", - "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "nullable": true }, "allow_deletions": { "type": "boolean", - "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." + "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." }, "required_conversation_resolution": { "type": "boolean", @@ -136544,7 +136544,7 @@ }, "delete": { "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -136623,7 +136623,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/enforce_admins": { "get": { "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -136706,7 +136706,7 @@ }, "post": { "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -136789,7 +136789,7 @@ }, "delete": { "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -136868,7 +136868,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_pull_request_reviews": { "get": { "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -137320,7 +137320,7 @@ }, "patch": { "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -137390,7 +137390,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed." }, "required_approving_review_count": { "type": "integer", @@ -137906,7 +137906,7 @@ }, "delete": { "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -137985,7 +137985,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_signatures": { "get": { "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -138100,7 +138100,7 @@ }, "post": { "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -138215,7 +138215,7 @@ }, "delete": { "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -138300,7 +138300,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks": { "get": { "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -138429,7 +138429,7 @@ }, "patch": { "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -138657,7 +138657,7 @@ }, "delete": { "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -138710,7 +138710,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks/contexts": { "get": { "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -138800,7 +138800,7 @@ }, "post": { "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -139025,7 +139025,7 @@ }, "put": { "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -139223,7 +139223,7 @@ }, "delete": { "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -139422,7 +139422,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions": { "get": { "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -139871,7 +139871,7 @@ }, "delete": { "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -139924,7 +139924,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/apps": { "get": { "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -140300,7 +140300,7 @@ }, "post": { "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -140757,7 +140757,7 @@ }, "put": { "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -141214,7 +141214,7 @@ }, "delete": { "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -141672,7 +141672,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/teams": { "get": { "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -141940,7 +141940,7 @@ }, "post": { "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -142290,7 +142290,7 @@ }, "put": { "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -142640,7 +142640,7 @@ }, "delete": { "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -142991,7 +142991,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/users": { "get": { "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -143220,7 +143220,7 @@ }, "post": { "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -143530,7 +143530,7 @@ }, "put": { "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -143840,7 +143840,7 @@ }, "delete": { "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -145856,7 +145856,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "maxItems": 50, "items": { "type": "object", @@ -148068,7 +148068,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.2/rest/reference/checks#annotations-object-1) description for details.", "maxItems": 50, "items": { "type": "object", @@ -163283,7 +163283,7 @@ "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -163571,7 +163571,7 @@ "/repos/{owner}/{repo}/collaborators/{username}": { "get": { "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -163623,7 +163623,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -169226,7 +169226,7 @@ "/repos/{owner}/{repo}/commits/{commit_sha}/branches-where-head": { "get": { "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -189911,7 +189911,7 @@ "/repos/{owner}/{repo}/dispatches": { "post": { "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -215882,7 +215882,7 @@ }, "post": { "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -225531,7 +225531,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -229387,7 +229387,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -229396,7 +229396,7 @@ "/repos/{owner}/{repo}/issues/{issue_number}": { "get": { "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.2/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -249167,7 +249167,7 @@ "previews": [ { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -263186,7 +263186,7 @@ }, { "name": "starfox", - "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://help.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" + "note": "Project card details are now shown in REST API v3 responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events).\n\nTo receive the `project_card` attribute, project boards must be [enabled](https://docs.github.com/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.starfox-preview+json\n```" } ] } @@ -263365,7 +263365,7 @@ }, "read_only": { "type": "boolean", - "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"" + "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"" } }, "required": [ @@ -269970,7 +269970,7 @@ "properties": { "cname": { "type": "string", - "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "nullable": true }, "https_enforced": { @@ -272569,7 +272569,7 @@ "/repos/{owner}/{repo}/pulls": { "get": { "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -277144,7 +277144,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -277196,11 +277196,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." }, "draft": { "type": "boolean", - "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." + "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." }, "issue": { "type": "integer", @@ -283229,7 +283229,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}": { "get": { "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.2/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.2/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -286546,7 +286546,7 @@ }, "patch": { "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -286610,7 +286610,7 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." } } }, @@ -290590,7 +290590,7 @@ }, "side": { "type": "string", - "description": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "description": "**Required with `comfort-fade` preview**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "enum": [ "LEFT", "RIGHT" @@ -290602,11 +290602,11 @@ }, "start_line": { "type": "integer", - "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." + "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." }, "start_side": { "type": "string", - "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "description": "**Required when using multi-line comments**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "enum": [ "LEFT", "RIGHT", @@ -315770,7 +315770,7 @@ "/repos/{owner}/{repo}/transfer": { "post": { "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -321487,7 +321487,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -323563,7 +323563,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -325817,7 +325817,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -328719,7 +328719,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -329613,7 +329613,7 @@ "/search/topics": { "get": { "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.2/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.2/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -329980,7 +329980,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.2/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -338200,7 +338200,7 @@ }, "put": { "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -338276,7 +338276,7 @@ }, "delete": { "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -338443,7 +338443,7 @@ }, "put": { "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -338588,7 +338588,7 @@ }, "delete": { "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.2/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -379725,7 +379725,7 @@ "/users/{username}/orgs": { "get": { "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.2/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.2/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -392610,7 +392610,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -392643,7 +392643,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } @@ -392659,7 +392659,7 @@ }, "delete": { "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -392692,7 +392692,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json index f8a3fe298a..65ce180d4f 100644 --- a/lib/rest/static/dereferenced/ghes-3.3.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json @@ -1275,7 +1275,7 @@ "/admin/ldap/teams/{team_id}/mapping": { "patch": { "summary": "Update LDAP mapping for a team", - "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://help.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.3/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.", + "description": "Updates the [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. [LDAP synchronization](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap/#enabling-ldap-sync) must be enabled to map LDAP entries to a team. Use the [Create a team](https://docs.github.com/enterprise-server@3.3/rest/reference/teams/#create-a-team) endpoint to create a team with LDAP mapping.", "operationId": "enterprise-admin/update-ldap-mapping-for-team", "tags": [ "enterprise-admin" @@ -4667,7 +4667,7 @@ }, "email": { "type": "string", - "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://help.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." + "description": "**Required for built-in authentication.** The user's email address. This parameter can be omitted when using CAS, LDAP, or SAML. For details on built-in and centrally-managed authentication, see the the [GitHub authentication guide](https://docs.github.com/enterprise/2.18/admin/guides/user-management/authenticating-users-for-your-github-enterprise-server-instance/)." } }, "required": [ @@ -16639,7 +16639,7 @@ "/apps/{app_slug}": { "get": { "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -17871,7 +17871,7 @@ }, "post": { "summary": "Create a new authorization", - "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.3/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.3/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://help.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", + "description": "**Deprecation Notice:** GitHub Enterprise Server will discontinue the [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations), which is used by integrations to create personal access tokens and OAuth tokens, and you must now create these tokens using our [web application flow](https://docs.github.com/enterprise-server@3.3/developers/apps/authorizing-oauth-apps#web-application-flow). The [OAuth Authorizations API](https://docs.github.com/enterprise-server@3.3/rest/reference/oauth-authorizations) will be removed on November, 13, 2020. For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/).\n\n**Warning:** Apps must use the [web application flow](https://docs.github.com/enterprise-server@3.3/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to obtain OAuth tokens that work with GitHub Enterprise Server SAML organizations. OAuth tokens created using the Authorizations API will be unable to access GitHub Enterprise Server SAML organizations. For more information, see the [blog post](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api).\n\nCreates OAuth tokens using [Basic Authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#basic-authentication). If you have two-factor authentication setup, Basic Authentication for this endpoint requires that you use a one-time password (OTP) and your username and password instead of tokens. For more information, see \"[Working with two-factor authentication](https://docs.github.com/enterprise-server@3.3/rest/overview/other-authentication-methods#working-with-two-factor-authentication).\"\n\nTo create tokens for a particular OAuth application using this endpoint, you must authenticate as the user you want to create an authorization for and provide the app's client ID and secret, found on your OAuth application's settings page. If your OAuth application intends to create multiple tokens for one user, use `fingerprint` to differentiate between them.\n\nYou can also create tokens on GitHub Enterprise Server from the [personal access tokens settings](https://github.com/settings/tokens) page. Read more about these tokens in [the GitHub Help documentation](https://docs.github.com/articles/creating-an-access-token-for-command-line-use).\n\nOrganizations that enforce SAML SSO require personal access tokens to be allowed. Read more about allowing tokens in [the GitHub Help documentation](https://docs.github.com/articles/about-identity-and-access-management-with-saml-single-sign-on).", "tags": [ "oauth-authorizations" ], @@ -56199,7 +56199,7 @@ "/orgs/{org}": { "get": { "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub Enterprise Server plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/enterprise-server@3.3/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub Enterprise Server plan information' below.\"", "tags": [ "orgs" ], @@ -56657,15 +56657,15 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_private_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_public_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_allowed_repository_creation_type": { "type": "string", @@ -79140,7 +79140,7 @@ "/orgs/{org}/outside_collaborators/{username}": { "put": { "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -82789,7 +82789,7 @@ }, "visibility": { "type": "string", - "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "enum": [ "public", "private", @@ -82831,7 +82831,7 @@ }, "license_template": { "type": "string", - "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." + "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." }, "allow_squash_merge": { "type": "boolean", @@ -84228,7 +84228,7 @@ "/orgs/{org}/secret-scanning/alerts": { "get": { "summary": "List secret scanning alerts for an organization", - "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\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 `secret_scanning_alerts` read permission to use this endpoint.", + "description": "Lists secret scanning alerts for eligible repositories in an organization, from newest to oldest.\nTo use this endpoint, you must be an administrator or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `secret_scanning_alerts` read permission to use this endpoint.", "tags": [ "secret-scanning" ], @@ -87005,7 +87005,7 @@ }, "post": { "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -94143,7 +94143,7 @@ }, "put": { "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -94268,7 +94268,7 @@ }, "delete": { "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -99040,7 +99040,7 @@ }, "put": { "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -109807,7 +109807,7 @@ }, "private": { "type": "boolean", - "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "default": false }, "visibility": { @@ -119012,7 +119012,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -127398,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": "; rel=\"next\", ; 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", @@ -134414,7 +130063,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches": { "post": { "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -134628,7 +130277,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -138581,7 +134230,7 @@ "/repos/{owner}/{repo}/assignees": { "get": { "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -141720,7 +137369,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection": { "get": { "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -142702,7 +138351,7 @@ }, "put": { "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -142825,7 +138474,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them." }, "required_approving_review_count": { "type": "integer", @@ -142867,16 +138516,16 @@ }, "required_linear_history": { "type": "boolean", - "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." + "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." }, "allow_force_pushes": { "type": "boolean", - "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "nullable": true }, "allow_deletions": { "type": "boolean", - "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." + "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." }, "required_conversation_resolution": { "type": "boolean", @@ -143792,7 +139441,7 @@ }, "delete": { "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -143871,7 +139520,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/enforce_admins": { "get": { "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -143954,7 +139603,7 @@ }, "post": { "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -144037,7 +139686,7 @@ }, "delete": { "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -144116,7 +139765,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_pull_request_reviews": { "get": { "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -144562,7 +140211,7 @@ }, "patch": { "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -144632,7 +140281,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed." }, "required_approving_review_count": { "type": "integer", @@ -145142,7 +140791,7 @@ }, "delete": { "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -145221,7 +140870,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_signatures": { "get": { "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -145330,7 +140979,7 @@ }, "post": { "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -145439,7 +141088,7 @@ }, "delete": { "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -145518,7 +141167,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks": { "get": { "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -145647,7 +141296,7 @@ }, "patch": { "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -145875,7 +141524,7 @@ }, "delete": { "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -145928,7 +141577,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks/contexts": { "get": { "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -146018,7 +141667,7 @@ }, "post": { "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -146243,7 +141892,7 @@ }, "put": { "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -146441,7 +142090,7 @@ }, "delete": { "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -146640,7 +142289,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions": { "get": { "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -147089,7 +142738,7 @@ }, "delete": { "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -147142,7 +142791,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/apps": { "get": { "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -147518,7 +143167,7 @@ }, "post": { "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -147975,7 +143624,7 @@ }, "put": { "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -148432,7 +144081,7 @@ }, "delete": { "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -148890,7 +144539,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/teams": { "get": { "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -149158,7 +144807,7 @@ }, "post": { "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -149508,7 +145157,7 @@ }, "put": { "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -149858,7 +145507,7 @@ }, "delete": { "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -150209,7 +145858,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/users": { "get": { "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -150438,7 +146087,7 @@ }, "post": { "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -150748,7 +146397,7 @@ }, "put": { "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -151058,7 +146707,7 @@ }, "delete": { "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -153074,7 +148723,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "maxItems": 50, "items": { "type": "object", @@ -155286,7 +150935,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/enterprise-server@3.3/rest/reference/checks#annotations-object-1) description for details.", "maxItems": 50, "items": { "type": "object", @@ -170637,7 +166286,7 @@ "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -170925,7 +166574,7 @@ "/repos/{owner}/{repo}/collaborators/{username}": { "get": { "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -170977,7 +166626,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -176553,7 +172202,7 @@ "/repos/{owner}/{repo}/commits/{commit_sha}/branches-where-head": { "get": { "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -197168,7 +192817,7 @@ "/repos/{owner}/{repo}/dispatches": { "post": { "summary": "Create a repository dispatch event", - "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", + "description": "You can use this endpoint to trigger a webhook event called `repository_dispatch` when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the `repository_dispatch` event occurs. For an example `repository_dispatch` webhook payload, see \"[RepositoryDispatchEvent](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#repository_dispatch).\"\n\nThe `client_payload` parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the `client_payload` can include a message that a user would like to send using a GitHub Actions workflow. Or the `client_payload` can be used as a test to debug your workflow.\n\nThis endpoint requires write access to the repository by providing either:\n\n - Personal access tokens with `repo` scope. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line)\" in the GitHub Help documentation.\n - GitHub Apps with both `metadata:read` and `contents:read&write` permissions.\n\nThis input example shows how you can use the `client_payload` as a test to debug your workflow.", "tags": [ "repos" ], @@ -223130,7 +218779,7 @@ }, "post": { "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -236601,7 +232250,7 @@ "/repos/{owner}/{repo}/issues/{issue_number}": { "get": { "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/enterprise-server@3.3/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -270528,7 +266177,7 @@ }, "read_only": { "type": "boolean", - "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"" + "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"" } }, "required": [ @@ -277326,7 +272975,7 @@ "properties": { "cname": { "type": "string", - "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "nullable": true }, "https_enforced": { @@ -279885,7 +275534,7 @@ "/repos/{owner}/{repo}/pulls": { "get": { "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -284460,7 +280109,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -284512,11 +280161,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." }, "draft": { "type": "boolean", - "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." + "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." }, "issue": { "type": "integer", @@ -290504,7 +286153,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}": { "get": { "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.3/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#update-a-pull-request) a pull request, GitHub Enterprise Server creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/enterprise-server@3.3/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub Enterprise Server has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -293821,7 +289470,7 @@ }, "patch": { "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -293885,7 +289534,7 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." } } }, @@ -297855,7 +293504,7 @@ }, "side": { "type": "string", - "description": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "description": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "enum": [ "LEFT", "RIGHT" @@ -297867,11 +293516,11 @@ }, "start_line": { "type": "integer", - "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." + "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." }, "start_side": { "type": "string", - "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "enum": [ "LEFT", "RIGHT", @@ -323346,7 +318995,7 @@ "/repos/{owner}/{repo}/transfer": { "post": { "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -329063,7 +324712,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -331139,7 +326788,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -333388,7 +329037,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -336290,7 +331939,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -337179,7 +332828,7 @@ "/search/topics": { "get": { "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.3/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.3/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -337519,7 +333168,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/enterprise-server@3.3/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -345671,7 +341320,7 @@ }, "put": { "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -345747,7 +341396,7 @@ }, "delete": { "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -345914,7 +341563,7 @@ }, "put": { "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -346059,7 +341708,7 @@ }, "delete": { "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/enterprise-server@3.3/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub Enterprise Server team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub Enterprise Server](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -387161,7 +382810,7 @@ "/users/{username}/orgs": { "get": { "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.3/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/enterprise-server@3.3/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -400036,7 +395685,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -400069,7 +395718,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } @@ -400085,7 +395734,7 @@ }, "delete": { "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -400118,7 +395767,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json index b9a72632a6..05a7106f3c 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -12073,7 +12073,7 @@ "/apps/{app_slug}": { "get": { "summary": "Get an app", - "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", + "description": "**Note**: The `:app_slug` is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., `https://github.com/settings/apps/:app_slug`).\n\nIf the GitHub App you specify is public, you can access this endpoint without authenticating. If the GitHub App you specify is private, you must authenticate with a [personal access token](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line/) or an [installation access token](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) to access this endpoint.", "tags": [ "apps" ], @@ -30858,7 +30858,7 @@ "/meta": { "get": { "summary": "Get GitHub AE meta information", - "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://help.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", + "description": "Returns meta information about GitHub, including a list of GitHub's IP addresses. For more information, see \"[About GitHub's IP addresses](https://docs.github.com/articles/about-github-s-ip-addresses/).\"\n\n**Note:** The IP addresses shown in the documentation's response are only example values. You must always query the API directly to get the latest list of IP addresses.", "tags": [ "meta" ], @@ -35917,7 +35917,7 @@ "/orgs/{org}": { "get": { "summary": "Get an organization", - "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub AE plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub AE plan information' below.\"", + "description": "To see many of the organization response values, you need to be an authenticated organization owner with the `admin:org` scope. When the value of `two_factor_requirement_enabled` is `true`, the organization requires all members, billing managers, and outside collaborators to enable [two-factor authentication](https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/).\n\nGitHub Apps with the `Organization plan` permission can use this endpoint to retrieve information about an organization's GitHub AE plan. See \"[Authenticating with GitHub Apps](https://docs.github.com/github-ae@latest/apps/building-github-apps/authenticating-with-github-apps/)\" for details. For an example response, see 'Response with GitHub AE plan information' below.\"", "tags": [ "orgs" ], @@ -36375,15 +36375,15 @@ }, "members_can_create_internal_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. Can be one of: \n\\* `true` - all organization members can create internal repositories. \n\\* `false` - only organization owners can create internal repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_private_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create private repositories, which are visible to organization members with permission. Can be one of: \n\\* `true` - all organization members can create private repositories. \n\\* `false` - only organization owners can create private repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_can_create_public_repositories": { "type": "boolean", - "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://help.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." + "description": "Toggles whether organization members can create public repositories, which are visible to anyone. Can be one of: \n\\* `true` - all organization members can create public repositories. \n\\* `false` - only organization owners can create public repositories. \nDefault: `true`. For more information, see \"[Restricting repository creation in your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)\" in the GitHub Help documentation." }, "members_allowed_repository_creation_type": { "type": "string", @@ -54546,7 +54546,7 @@ "/orgs/{org}/outside_collaborators/{username}": { "put": { "summary": "Convert an organization member to outside collaborator", - "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://help.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", + "description": "When an organization member is converted to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The user will no longer be a member of the organization. For more information, see \"[Converting an organization member to an outside collaborator](https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/)\".", "tags": [ "orgs" ], @@ -57450,7 +57450,7 @@ }, "visibility": { "type": "string", - "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", + "description": "Can be `public` or `private`. If your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, `visibility` can also be `internal`. Note: For GitHub Enterprise Server and GitHub AE, this endpoint will only list repositories available to all users on the enterprise. For more information, see \"[Creating an internal repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)\" in the GitHub Help documentation.", "enum": [ "public", "private", @@ -57492,7 +57492,7 @@ }, "license_template": { "type": "string", - "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." + "description": "Choose an [open source license template](https://choosealicense.com/) that best suits your needs, and then use the [license keyword](https://docs.github.com/articles/licensing-a-repository/#searching-github-by-license-type) as the `license_template` string. For example, \"mit\" or \"mpl-2.0\"." }, "allow_squash_merge": { "type": "boolean", @@ -59165,7 +59165,7 @@ }, "post": { "summary": "Create a team", - "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://help.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", + "description": "To create a team, the authenticated user must be a member or owner of `{org}`. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see \"[Setting team creation permissions](https://docs.github.com/en/articles/setting-team-creation-permissions-in-your-organization).\"\n\nWhen you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of `maintainers`. For more information, see \"[About teams](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams)\".", "tags": [ "teams" ], @@ -66558,7 +66558,7 @@ }, "put": { "summary": "Add or update team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdds an organization member to a team. An authenticated organization owner or team maintainer can add organization members to a team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nAn organization owner can add someone who is not part of the team's organization to a team. When an organization owner adds someone to a team who is not an organization member, this endpoint will send an invitation to the person via email. This newly-created membership will be in the \"pending\" state until the person accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -66683,7 +66683,7 @@ }, "delete": { "summary": "Remove team membership for a user", - "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", + "description": "Team synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `DELETE /organizations/{org_id}/team/{team_id}/memberships/{username}`.", "tags": [ "teams" ], @@ -71455,7 +71455,7 @@ }, "put": { "summary": "Add or update team repository permissions", - "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", + "description": "To add a repository to a team or update the team's permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a `422 Unprocessable Entity` status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\n**Note:** You can also specify a team by `org_id` and `team_id` using the route `PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}`.\n\nFor more information about the permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\".", "tags": [ "teams" ], @@ -77292,125 +77292,6 @@ } } }, - "/reactions/{reaction_id}": { - "delete": { - "summary": "Delete a reaction (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this [blog post](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/).\n\nOAuth access tokens require the `write:discussion` [scope](https://docs.github.com/github-ae@latest/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), when deleting a [team discussion](https://docs.github.com/github-ae@latest/rest/reference/teams#discussions) or [team discussion comment](https://docs.github.com/github-ae@latest/rest/reference/teams#discussion-comments).", - "tags": [ - "reactions" - ], - "operationId": "reactions/delete-legacy", - "externalDocs": { - "description": "API method documentation", - "url": "https://docs.github.com/github-ae@latest/rest/reference/reactions/#delete-a-reaction-legacy" - }, - "parameters": [ - { - "name": "reaction_id", - "in": "path", - "required": true, - "schema": { - "type": "integer" - } - } - ], - "responses": { - "204": { - "description": "Response" - }, - "304": { - "description": "Not modified" - }, - "403": { - "description": "Forbidden", - "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" - } - } - } - } - } - }, - "401": { - "description": "Requires authentication", - "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" - } - } - } - } - } - }, - "410": { - "description": "Gone", - "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, - "removalDate": "2021-02-21", - "deprecationDate": "2020-02-26", - "category": "reactions", - "subcategory": null - }, - "deprecated": true - } - }, "/repos/{owner}/{repo}": { "get": { "summary": "Get a repository", @@ -82222,7 +82103,7 @@ }, "private": { "type": "boolean", - "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://help.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", + "description": "Either `true` to make the repository private or `false` to make it public. Default: `false`. \n**Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private. **Note**: You will get a `422` error if the organization restricts [changing repository visibility](https://docs.github.com/articles/repository-permission-levels-for-an-organization#changing-the-visibility-of-repositories) to organization owners and a non-owner tries to change the value of private.", "default": false }, "visibility": { @@ -88739,7 +88620,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -101965,7 +101846,7 @@ "/repos/{owner}/{repo}/actions/runs/{run_id}/timing": { "get": { "summary": "Get workflow run usage", - "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", + "description": "Gets the number of billable minutes and total run time for a specific workflow run. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nAnyone 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.", "tags": [ "actions" ], @@ -103050,7 +102931,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches": { "post": { "summary": "Create a workflow dispatch event", - "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", + "description": "You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`.\n\nYou must configure your GitHub Actions workflow to run when the [`workflow_dispatch` webhook](/developers/webhooks-and-events/webhook-events-and-payloads#workflow_dispatch) event occurs. The `inputs` are configured in the workflow file. For more information about how to configure the `workflow_dispatch` event in the workflow file, see \"[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `actions:write` permission to use this endpoint. For more information, see \"[Creating a personal access token for the command line](https://docs.github.com/articles/creating-a-personal-access-token-for-the-command-line).\"", "operationId": "actions/create-workflow-dispatch", "tags": [ "actions" @@ -103264,7 +103145,7 @@ }, { "name": "event", - "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", + "description": "Returns workflow run triggered by the event you specify. For example, `push`, `pull_request` or `issue`. For more information, see \"[Events that trigger workflows](https://docs.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows).\"", "in": "query", "required": false, "schema": { @@ -107217,7 +107098,7 @@ "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/timing": { "get": { "summary": "Get workflow usage", - "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://help.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", + "description": "Gets the number of billable minutes used by a specific workflow during the current billing cycle. Billable minutes only apply to workflows in private repositories that use GitHub AE-hosted runners. Usage is listed for each GitHub AE-hosted runner operating system in milliseconds. Any job re-runs are also included in the usage. The usage does not include the multiplier for macOS and Windows runners and is not rounded up to the nearest whole minute. For more information, see \"[Managing billing for GitHub Actions](https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)\".\n\nYou can replace `workflow_id` with the workflow file name. For example, you could use `main.yaml`. 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.", "tags": [ "actions" ], @@ -107336,7 +107217,7 @@ "/repos/{owner}/{repo}/assignees": { "get": { "summary": "List assignees", - "description": "Lists the [available assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", + "description": "Lists the [available assignees](https://docs.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users/) for issues in a repository.", "tags": [ "issues" ], @@ -111111,7 +110992,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection": { "get": { "summary": "Get branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -112411,7 +112292,7 @@ }, "put": { "summary": "Update branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nProtecting a branch requires admin or owner permissions to the repository.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.\n\n**Note**: The list of users, apps, and teams in total is limited to 100 items.", "tags": [ "repos" ], @@ -112534,7 +112415,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) review them." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) review them." }, "required_approving_review_count": { "type": "integer", @@ -112597,16 +112478,16 @@ }, "required_linear_history": { "type": "boolean", - "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://help.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." + "description": "Enforces a linear commit Git history, which prevents anyone from pushing merge commits to a branch. Set to `true` to enforce a linear commit history. Set to `false` to disable a linear commit Git history. Your repository must allow squash merging or rebase merging before you can enable a linear commit history. Default: `false`. For more information, see \"[Requiring a linear commit history](https://docs.github.com/github/administering-a-repository/requiring-a-linear-commit-history)\" in the GitHub Help documentation." }, "allow_force_pushes": { "type": "boolean", - "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", + "description": "Permits force pushes to the protected branch by anyone with write access to the repository. Set to `true` to allow force pushes. Set to `false` or `null` to block force pushes. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation.\"", "nullable": true }, "allow_deletions": { "type": "boolean", - "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://help.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." + "description": "Allows deletion of the protected branch by anyone with write access to the repository. Set to `false` to prevent deletion of the protected branch. Default: `false`. For more information, see \"[Enabling force pushes to a protected branch](https://docs.github.com/en/github/administering-a-repository/enabling-force-pushes-to-a-protected-branch)\" in the GitHub Help documentation." }, "required_conversation_resolution": { "type": "boolean", @@ -113834,7 +113715,7 @@ }, "delete": { "summary": "Delete branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -113913,7 +113794,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/enforce_admins": { "get": { "summary": "Get admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -113996,7 +113877,7 @@ }, "post": { "summary": "Set admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nAdding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -114079,7 +113960,7 @@ }, "delete": { "summary": "Delete admin branch protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoving admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -114158,7 +114039,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_pull_request_reviews": { "get": { "summary": "Get pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -114902,7 +114783,7 @@ }, "patch": { "summary": "Update pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.\n\n**Note**: Passing new arrays of `users` and `teams` replaces their previous values.", "tags": [ "repos" ], @@ -114972,7 +114853,7 @@ }, "require_code_owner_reviews": { "type": "boolean", - "description": "Blocks merging pull requests until [code owners](https://help.github.com/articles/about-code-owners/) have reviewed." + "description": "Blocks merging pull requests until [code owners](https://docs.github.com/articles/about-code-owners/) have reviewed." }, "required_approving_review_count": { "type": "integer", @@ -115801,7 +115682,7 @@ }, "delete": { "summary": "Delete pull request review protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -115880,7 +115761,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_signatures": { "get": { "summary": "Get commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://help.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of `true` indicates you must sign commits on this branch. For more information, see [Signing commits with GPG](https://docs.github.com/articles/signing-commits-with-gpg) in GitHub Help.\n\n**Note**: You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -115989,7 +115870,7 @@ }, "post": { "summary": "Create commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -116098,7 +115979,7 @@ }, "delete": { "summary": "Delete commit signature protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nWhen authenticated with admin or owner permissions to the repository, you can use this endpoint to disable required signed commits on a branch. You must enable branch protection to require signed commits.", "tags": [ "repos" ], @@ -116177,7 +116058,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks": { "get": { "summary": "Get status checks protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -116327,7 +116208,7 @@ }, "patch": { "summary": "Update status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nUpdating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.", "tags": [ "repos" ], @@ -116596,7 +116477,7 @@ }, "delete": { "summary": "Remove status check protection", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -116649,7 +116530,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/required_status_checks/contexts": { "get": { "summary": "Get all status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -116739,7 +116620,7 @@ }, "post": { "summary": "Add status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -116964,7 +116845,7 @@ }, "put": { "summary": "Set status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -117162,7 +117043,7 @@ }, "delete": { "summary": "Remove status check contexts", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "repos" ], @@ -117361,7 +117242,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions": { "get": { "summary": "Get access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists who has access to this protected branch.\n\n**Note**: Users, apps, and teams `restrictions` are only available for organization-owned repositories.", "tags": [ "repos" ], @@ -117810,7 +117691,7 @@ }, "delete": { "summary": "Delete access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nDisables the ability to restrict who can push to this branch.", "tags": [ "repos" ], @@ -117863,7 +117744,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/apps": { "get": { "summary": "Get apps with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.", "tags": [ "repos" ], @@ -118239,7 +118120,7 @@ }, "post": { "summary": "Add app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified apps push access for this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -118696,7 +118577,7 @@ }, "put": { "summary": "Set app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -119153,7 +119034,7 @@ }, "delete": { "summary": "Remove app access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of an app to push to this branch. Only installed GitHub Apps with `write` access to the `contents` permission can be added as authorized actors on a protected branch.\n\n| Type | Description |\n| ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | The GitHub Apps that have push access to this branch. Use the app's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -119611,7 +119492,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/teams": { "get": { "summary": "Get teams with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the teams who have push access to this branch. The list includes child teams.", "tags": [ "repos" ], @@ -119879,7 +119760,7 @@ }, "post": { "summary": "Add team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified teams push access for this branch. You can also give push access to child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -120229,7 +120110,7 @@ }, "put": { "summary": "Set team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.\n\n| Type | Description |\n| ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |\n| `array` | The teams that can have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -120579,7 +120460,7 @@ }, "delete": { "summary": "Remove team access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a team to push to this branch. You can also remove push access for child teams.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Teams that should no longer have push access. Use the team's `slug`. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -120930,7 +120811,7 @@ "/repos/{owner}/{repo}/branches/{branch}/protection/restrictions/users": { "get": { "summary": "Get users with access to the protected branch", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists the people who have push access to this branch.", "tags": [ "repos" ], @@ -121159,7 +121040,7 @@ }, "post": { "summary": "Add user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nGrants the specified people push access for this branch.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -121469,7 +121350,7 @@ }, "put": { "summary": "Set user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReplaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.\n\n| Type | Description |\n| ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames for people who can have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -121779,7 +121660,7 @@ }, "delete": { "summary": "Remove user access restrictions", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nRemoves the ability of a user to push to this branch.\n\n| Type | Description |\n| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- |\n| `array` | Usernames of the people who should no longer have push access. **Note**: The list of users, apps, and teams in total is limited to 100 items. |", "tags": [ "repos" ], @@ -122194,7 +122075,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible on GitHub in the **Checks** and **Files changed** tab of the pull request. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about how you can view annotations on GitHub, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object) description for details about how to use this parameter.", "maxItems": 50, "items": { "type": "object", @@ -124406,7 +124287,7 @@ }, "annotations": { "type": "array", - "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://help.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", + "description": "Adds information from your analysis to specific lines of code. Annotations are visible in GitHub's pull request UI. Annotations are visible in GitHub's pull request UI. The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](https://docs.github.com/github-ae@latest/rest/reference/checks#update-a-check-run) endpoint. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run. For details about annotations in the UI, see \"[About status checks](https://docs.github.com/articles/about-status-checks#checks)\". See the [`annotations` object](https://docs.github.com/github-ae@latest/rest/reference/checks#annotations-object-1) description for details.", "maxItems": 50, "items": { "type": "object", @@ -139761,7 +139642,7 @@ "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must have push access to the repository in order to list collaborators.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -140049,7 +139930,7 @@ "/repos/{owner}/{repo}/collaborators/{username}": { "get": { "summary": "Check if a user is a repository collaborator", - "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.", + "description": "For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.\n\nTeam members will include the members of child teams.\n\nYou must authenticate using an access token with the `read:org` and `repo` scopes with push access to use this\nendpoint. GitHub Apps must have the `members` organization permission and `metadata` repository permission to use this\nendpoint.", "tags": [ "repos" ], @@ -140101,7 +139982,7 @@ }, "put": { "summary": "Add a repository collaborator", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nFor more information on permission levels, see \"[Repository permission levels for an organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:\n\n```\nCannot assign {member} permission of {role name}\n```\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"\n\nThe invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the [repository invitations API endpoints](https://docs.github.com/github-ae@latest/rest/reference/repos#invitations).\n\n**Rate limits**\n\nYou are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.", "tags": [ "repos" ], @@ -145677,7 +145558,7 @@ "/repos/{owner}/{repo}/commits/{commit_sha}/branches-where-head": { "get": { "summary": "List branches for HEAD commit", - "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", + "description": "Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nReturns all branches where the given commit SHA is the HEAD, or latest commit for the branch.", "tags": [ "repos" ], @@ -189892,7 +189773,7 @@ }, "post": { "summary": "Create an issue", - "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", + "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://docs.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.", "tags": [ "issues" ], @@ -203363,7 +203244,7 @@ "/repos/{owner}/{repo}/issues/{issue_number}": { "get": { "summary": "Get an issue", - "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://help.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/github-ae@latest/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/github-ae@latest/rest/reference/pulls#list-pull-requests)\" endpoint.", + "description": "The API returns a [`301 Moved Permanently` status](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-redirects-redirects) if the issue was\n[transferred](https://docs.github.com/articles/transferring-an-issue-to-another-repository/) to another repository. If\nthe issue was transferred to or deleted from a repository where the authenticated user lacks read access, the API\nreturns a `404 Not Found` status. If the issue was deleted from a repository where the authenticated user has read\naccess, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe\nto the [`issues`](https://docs.github.com/github-ae@latest/webhooks/event-payloads/#issues) webhook.\n\n**Note**: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request. For this\nreason, \"Issues\" endpoints may return both issues and pull requests in the response. You can identify pull requests by\nthe `pull_request` key. Be aware that the `id` of a pull request returned from \"Issues\" endpoints will be an _issue id_. To find out the pull\nrequest id, use the \"[List pull requests](https://docs.github.com/github-ae@latest/rest/reference/pulls#list-pull-requests)\" endpoint.", "tags": [ "issues" ], @@ -237290,7 +237171,7 @@ }, "read_only": { "type": "boolean", - "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://help.github.com/articles/permission-levels-for-a-user-account-repository/).\"" + "description": "If `true`, the key will only be able to read repository contents. Otherwise, the key will be able to read and write. \n \nDeploy keys with write access can perform the same actions as an organization member with admin access, or a collaborator on a personal repository. For more information, see \"[Repository permission levels for an organization](https://docs.github.com/articles/repository-permission-levels-for-an-organization/)\" and \"[Permission levels for a user account repository](https://docs.github.com/articles/permission-levels-for-a-user-account-repository/).\"" } }, "required": [ @@ -244094,7 +243975,7 @@ "properties": { "cname": { "type": "string", - "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://help.github.com/articles/using-a-custom-domain-with-github-pages/).\"", + "description": "Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see \"[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/).\"", "nullable": true }, "https_enforced": { @@ -246266,7 +246147,7 @@ "/repos/{owner}/{repo}/pulls": { "get": { "summary": "List pull requests", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.", "tags": [ "pulls" ], @@ -250841,7 +250722,7 @@ }, "post": { "summary": "Create a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.\n\nYou can create a new pull request.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-rate-limits)\" for details.", "tags": [ "pulls" ], @@ -250893,11 +250774,11 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." }, "draft": { "type": "boolean", - "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." + "description": "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/en/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more." }, "issue": { "type": "integer", @@ -256885,7 +256766,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}": { "get": { "summary": "Get a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/github-ae@latest/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/github-ae@latest/rest/reference/pulls#update-a-pull-request) a pull request, GitHub AE creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub AE has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://help.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://help.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://help.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nLists details of a pull request by providing its number.\n\nWhen you get, [create](https://docs.github.com/github-ae@latest/rest/reference/pulls/#create-a-pull-request), or [edit](https://docs.github.com/github-ae@latest/rest/reference/pulls#update-a-pull-request) a pull request, GitHub AE creates a merge commit to test whether the pull request can be automatically merged into the base branch. This test commit is not added to the base branch or the head branch. You can review the status of the test commit using the `mergeable` key. For more information, see \"[Checking mergeability of pull requests](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests)\".\n\nThe value of the `mergeable` attribute can be `true`, `false`, or `null`. If the value is `null`, then GitHub AE has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-`null` value for the `mergeable` attribute in the response. If `mergeable` is `true`, then `merge_commit_sha` will be the SHA of the _test_ merge commit.\n\nThe value of the `merge_commit_sha` attribute changes depending on the state of the pull request. Before merging a pull request, the `merge_commit_sha` attribute holds the SHA of the _test_ merge commit. After merging a pull request, the `merge_commit_sha` attribute changes depending on how you merged the pull request:\n\n* If merged as a [merge commit](https://docs.github.com/articles/about-merge-methods-on-github/), `merge_commit_sha` represents the SHA of the merge commit.\n* If merged via a [squash](https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits), `merge_commit_sha` represents the SHA of the squashed commit on the base branch.\n* If [rebased](https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits), `merge_commit_sha` represents the commit that the base branch was updated to.\n\nPass the appropriate [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests) to fetch diff and patch formats.", "tags": [ "pulls" ], @@ -260202,7 +260083,7 @@ }, "patch": { "summary": "Update a pull request", - "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", + "description": "Draft pull requests are available in public repositories with GitHub Free and GitHub Free for organizations, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo open or update a pull request in a public repository, you must have write access to the head or the source branch. For organization-owned repositories, you must be a member of the organization that owns the repository to open or update a pull request.", "tags": [ "pulls" ], @@ -260266,7 +260147,7 @@ }, "maintainer_can_modify": { "type": "boolean", - "description": "Indicates whether [maintainers can modify](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." + "description": "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request." } } }, @@ -264236,7 +264117,7 @@ }, "side": { "type": "string", - "description": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://help.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", + "description": "**Required with `comfort-fade` preview unless using `in_reply_to`**. In a split diff view, the side of the diff that the pull request's changes appear on. Can be `LEFT` or `RIGHT`. Use `LEFT` for deletions that appear in red. Use `RIGHT` for additions that appear in green or unchanged lines that appear in white and are shown for context. For a multi-line comment, side represents whether the last line of the comment range is a deletion or addition. For more information, see \"[Diff view options](https://docs.github.com/en/articles/about-comparing-branches-in-pull-requests#diff-view-options)\" in the GitHub Help documentation.", "enum": [ "LEFT", "RIGHT" @@ -264248,11 +264129,11 @@ }, "start_line": { "type": "integer", - "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." + "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_line` is the first line in the pull request diff that your multi-line comment applies to. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation." }, "start_side": { "type": "string", - "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://help.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", + "description": "**Required when using multi-line comments unless using `in_reply_to`**. To create multi-line comments, you must use the `comfort-fade` preview header. The `start_side` is the starting side of the diff that the comment applies to. Can be `LEFT` or `RIGHT`. To learn more about multi-line comments, see \"[Commenting on a pull request](https://docs.github.com/en/articles/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)\" in the GitHub Help documentation. See `side` in this table for additional context.", "enum": [ "LEFT", "RIGHT", @@ -289376,7 +289257,7 @@ "/repos/{owner}/{repo}/transfer": { "post": { "summary": "Transfer a repository", - "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://help.github.com/articles/about-repository-transfers/).", + "description": "A transfer request will need to be accepted by the new owner when transferring a personal repository to another user. The response will contain the original `owner`, and the transfer will continue asynchronously. For more details on the requirements to transfer personal and organization-owned repositories, see [about repository transfers](https://docs.github.com/articles/about-repository-transfers/).", "tags": [ "repos" ], @@ -293736,7 +293617,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://help.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching code](https://docs.github.com/articles/searching-code/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -295812,7 +295693,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://help.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching commits](https://docs.github.com/articles/searching-commits/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -298061,7 +297942,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://help.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching issues and pull requests](https://docs.github.com/articles/searching-issues-and-pull-requests/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -300963,7 +300844,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://help.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching for repositories](https://docs.github.com/articles/searching-for-repositories/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -301852,7 +301733,7 @@ "/search/topics": { "get": { "summary": "Search topics", - "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://help.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/github-ae@latest/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", + "description": "Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results [per page](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#pagination). See \"[Searching topics](https://docs.github.com/articles/searching-topics/)\" for a detailed list of qualifiers.\n\nWhen searching for topics, you can get text match metadata for the topic's **short\\_description**, **description**, **name**, or **display\\_name** field when you pass the `text-match` media type. For more details about how to receive highlighted search results, see [Text match metadata](https://docs.github.com/github-ae@latest/rest/reference/search#text-match-metadata).\n\nFor example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:\n\n`q=ruby+is:featured`\n\nThis query searches for topics with the keyword `ruby` and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.", "tags": [ "search" ], @@ -302192,7 +302073,7 @@ "parameters": [ { "name": "q", - "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://help.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", + "description": "The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see [Constructing a search query](https://docs.github.com/github-ae@latest/rest/reference/search#constructing-a-search-query). See \"[Searching users](https://docs.github.com/articles/searching-users/)\" for a detailed list of qualifiers.", "in": "query", "required": true, "schema": { @@ -309090,7 +308971,7 @@ }, "put": { "summary": "Add team member (Legacy)", - "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "The \"Add team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint instead. It allows you to invite new organization members to your teams.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo add someone to a team, the authenticated user must be an organization owner or a team maintainer in the team they're changing. The person being added to the team must be a member of the team's organization.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nNote that you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", "tags": [ "teams" ], @@ -309166,7 +309047,7 @@ }, "delete": { "summary": "Remove team member (Legacy)", - "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "The \"Remove team member\" endpoint (described below) is deprecated.\n\nWe recommend using the [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint instead. It allows you to remove both active and pending memberships.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a team member, the authenticated user must have 'admin' permissions to the team or be an owner of the org that the team is associated with. Removing a team member does not delete the user, it just removes them from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -309333,7 +309214,7 @@ }, "put": { "summary": "Add or update team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Add or update team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#add-or-update-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nIf the user is already a member of the team's organization, this endpoint will add the user to the team. To add a membership between an organization member and a team, the authenticated user must be an organization owner or a team maintainer.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"\n\nIf the user is unaffiliated with the team's organization, this endpoint will send an invitation to the user via email. This newly-created membership will be in the \"pending\" state until the user accepts the invitation, at which point the membership will transition to the \"active\" state and the user will be added as a member of the team. To add a membership between an unaffiliated user and a team, the authenticated user must be an organization owner.\n\nIf the user is already a member of the team, this endpoint will update the role of the team member's role. To update the membership of a team member, the authenticated user must be an organization owner or a team maintainer.", "tags": [ "teams" ], @@ -309478,7 +309359,7 @@ }, "delete": { "summary": "Remove team membership for a user (Legacy)", - "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://help.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://help.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", + "description": "**Deprecation Notice:** This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new [Remove team membership for a user](https://docs.github.com/github-ae@latest/rest/reference/teams#remove-team-membership-for-a-user) endpoint.\n\nTeam synchronization is available for organizations using GitHub Enterprise Cloud. For more information, see [GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products) in the GitHub Help documentation.\n\nTo remove a membership between a user and a team, the authenticated user must have 'admin' permissions to the team or be an owner of the organization that the team is associated with. Removing team membership does not delete the user, it just removes their membership from the team.\n\n**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub AE team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see \"[Synchronizing teams between your identity provider and GitHub AE](https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/).\"", "tags": [ "teams" ], @@ -351901,7 +351782,7 @@ "/users/{username}/orgs": { "get": { "summary": "List organizations for a user", - "description": "List [public organization memberships](https://help.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/github-ae@latest/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", + "description": "List [public organization memberships](https://docs.github.com/articles/publicizing-or-concealing-organization-membership) for the specified user.\n\nThis method only lists _public_ memberships, regardless of authentication. If you need to fetch all of the organization memberships (public and private) for the authenticated user, use the [List organizations for the authenticated user](https://docs.github.com/github-ae@latest/rest/reference/orgs#list-organizations-for-the-authenticated-user) API instead.", "tags": [ "orgs" ], @@ -358654,7 +358535,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), Active Directory LDAP-authenticated users cannot be suspended through this API. If you attempt to suspend an Active Directory LDAP-authenticated user through this API, it will return a `403` response.\n\nYou can suspend any user account except your own.\n\nNote that, if you choose not to pass any parameters, you'll need to set `Content-Length` to zero when calling out to this endpoint. For more information, see \"[HTTP verbs](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -358687,7 +358568,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Suspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } @@ -358703,7 +358584,7 @@ }, "delete": { "summary": "Unsuspend a user", - "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://help.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise/admin/guides/user-management/using-ldap), this API is disabled and will return a `403` response. Active Directory LDAP-authenticated users cannot be unsuspended using the API.", "operationId": "enterprise-admin/unsuspend-user", "tags": [ "enterprise-admin" @@ -358736,7 +358617,7 @@ "properties": { "reason": { "type": "string", - "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://help.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise/admin/articles/audit-logging/). If you don't provide a `reason`, it will default to \"Unsuspended via API by _SITE\\_ADMINISTRATOR_\", where _SITE\\_ADMINISTRATOR_ is the person who performed the action." } } } 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 31ce0c4c88..7d4b330003 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:57b08a80126185059616e73f76cd4119d8b094e700905fc3e81887bfad7799a2 -size 654633 +oid sha256:0a05a5e69dfa719c8c4a0f2108f53c7b53a0626cf8dbce2cbc74430efdbf89fd +size 661125 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 45b30b8873..03c692de8d 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:af4912bc2c3e21080c3418e20f5e06edff3af893edc42dc19c718ba83b45929d -size 1357812 +oid sha256:02df778cdb25dc97d0a9c763a2b231f9847d1e7f48333f9a128165263f2d433d +size 1377783 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 c93e9e975b..21308fade1 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:413f3b76ffca633a0eb9773768ed2f1cb54a477c1af2921acd25769905337825 -size 978916 +oid sha256:1d15ef78a6d117d8886b529acdf9fd3e911a5dee450cfc30ee90e184868d4b4b +size 988608 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 4f0b7f5af0..f1fcaba47d 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:d1389f329300d497a2106e0e98d82ca3e9bd8469d720916cfeecfbb23e062635 -size 3989081 +oid sha256:8e2898b838b2c3661ed6af688ef70a016afb8802b4acdb96dbffc344e6d67920 +size 4013333 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 66e07b7f5a..00c433a0a2 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:90f18e76c6b1740907b0218f732724d8a2112509a03269008422cd1b0d41ef16 -size 614496 +oid sha256:77363332102e1fa9d5eaf97e1278935ea403309bad0bb1314abfb00423dc2215 +size 614637 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 feb2f93c20..d289c42ce6 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:ec004d4b3d139658886825c4ebbb00eee41cc9a3dc21a1cc42530651c005a9bd -size 2573311 +oid sha256:7518253b3d1951d3325333b5fe288282f3874dd9ebc03678cfddf141cb866f31 +size 2573465 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 b72cf984d3..416f64985e 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:33e579cdbb805b5dad80e7c3c59c18c3a5b5b0dfe81d4f88b6df719148c1d2d6 -size 673913 +oid sha256:fed5af1c47625a5d2f9d822286cd0c3d32462a794ba926455b59dc31365abd38 +size 680081 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 c323d2e2f7..2b1b7db496 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:ef60219b51e698b188dc664def73db5b9d5bb1c308fcd3486fb520923d51ee2d -size 3555326 +oid sha256:160d70eaf770a2845f65c3035620be22bac36a5e7a54cd83c3e505e1d45f3ed9 +size 3598019 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 2a65ee9bfb..540a2fb691 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:ea6b878b89f0ae5dbe0444df16d78feb99d8cf9e58a2a0495506a435c8e53b4c -size 606201 +oid sha256:5c31636d28b0fd5c099b8ad16f5555ad3d7b2d939d52d70a48b5d43932e817af +size 604682 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 2b2b17e790..dc0d012c85 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:45b4d1603eaa0e46118ec4374e20e5b71d383f0b399c25c9d1368c05e89d3f67 -size 2470989 +oid sha256:84cbee7d47730c5b68e8540b11152817639e4e4c5ad574b491957ef93b739529 +size 2465068 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 08d75164ed..d5a47a5ac6 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:e9aa102e7fe0b35e768d7214a24f01ef472dcb456a4e2157bd0ff12fdf846a03 -size 668363 +oid sha256:426535acb4691e4a1900ce4384db2d56585e892d9aef495576ab16d8cfa223a2 +size 674786 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 1eabf1a0a9..db671d766c 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:ac7d71272e87a8bdd8805398795c6c86c3b563684543115632744ceb10a33356 -size 1394801 +oid sha256:17f457cedfc89191fe7eed07a1d884c4fe75e3ec25bf95ba53a065a2627a2d56 +size 1413662 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 c6087aa019..ddd0b226c0 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:f92c4ddf1b7a8f7e1e412c94225c36dd2cf62ae5d0ad5e539959a80d6b26b27a -size 1005199 +oid sha256:b61494081aa6f22e417a7d3576c978e8af4496cde18e37cd635826304b71930c +size 1005197 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 a705bcc6be..178fcdebcb 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:8ff38dd98cd094cb0abc6ba25c0baaa7ff8ce186ee06b27437fad8aa13e883eb -size 4078403 +oid sha256:7b42c877bd26f900e2255d8a35fe2dcda28191bd9dadba6511b9d075ec270ae2 +size 4079117 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 711aed9a57..2bce7d6755 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:d33ecc4568a3d95116460c425bbf02e43fa955b340a535d72edbb59290229559 -size 628052 +oid sha256:5dc0d8919d89ba00244f59939dc5120efce82e33877587efe55c544407ac4dd6 +size 626414 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 866b41435a..81036c15c5 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:8f4dec250b6125808e2141c4bbd9226f16835fc783ff3f6d36eb0766e0fce719 -size 2632006 +oid sha256:e36222f5d6aa5f7759c740383924ce8c80ea0e2011fc71464625818f7a3d1395 +size 2632740 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 1cb2fb057c..bb8b88ba74 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:c95011b9be926a0ae485e8d0ceb09d1deb58cfc1a20e1fefd8ef003839b9a7cc -size 687269 +oid sha256:c9fe9261df33e6d32c87cd64b1269c247557d607496b65a25f1f179330c7c2e3 +size 693436 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 8b2541d989..b3b3febf1b 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:9e263c39435e3180477d98673d03898171a7194db3a9f7865392abcd616c679b -size 3631735 +oid sha256:fc2900838e8d0c1680639a171b3a91f541b635ea5dc26110fa12411f15f0fb38 +size 3678011 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 f4a8a06b50..fe19342be3 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:c21b4952d15c60965d9be28cbb2dd25f1eeeed8790ac2c78a7690312192ae08e -size 618082 +oid sha256:41d6417e6d31557bdb8c02f4028b854962b26251d6cdde54299b8b3f0c4d408e +size 616667 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 a8b2298def..bb11727442 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:53a83eba29840f5b3408665713d42199f5f6d25e40d95d54e516236ef81aad8b -size 2521961 +oid sha256:c46093d04b03bd4ff9c5f5dba3e9a0063bd940fd27f98ac6ed39aead759c1c54 +size 2518874 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 4f9c003bff..e7ee71957f 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:b5abfaa35aaa4510de0bdcf07c2420dd605a9012047f3b6946fa459c4ab7d9e3 -size 684182 +oid sha256:7f72f2482e1223a36b131c280c35cd1d2b7337b79f351ee90da0e1d84ce70c53 +size 691032 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 f18753b99b..78f39d00df 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:9da97ad4f792397f09b58d871580fa2c1c34a114333e0c469921a6a1e82faeab -size 1426747 +oid sha256:c5644106795c8973f3aabf724d8d2385384c025fac1bba36bc3603e07d61e7ad +size 1446786 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 193405be85..a44ad8c6ab 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:7110981d3f8a7eb2e5c5fc196129702df816bf531ea9952d99478d4aa28d08a1 -size 1039455 +oid sha256:1e1412527bda6aebcc44494e3c154895df04b0f34cdd9cd4f8e32ff841e5b206 +size 1038035 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 910646f1d1..0badfb7cb2 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:22262c5d28bd86e936b5b72d15e2fd58b70ac8caf23002329de08a6c1284f975 -size 4214372 +oid sha256:42af444264c45e00e6ca70585983d7f71a8579ef0e204a9c921219db26d1006e +size 4212871 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 74e1e4ddc8..135a80a64b 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:93872369abecc795d6db31d1463b7d59c1b5844b9d137cb66a2d839a43861399 -size 641318 +oid sha256:e9fa5d29b8471b659163b5f20f39c5c62fd187321c839180e3afdabd201df466 +size 640384 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 b7dc7f9b9d..6cbd403c1d 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:c9ed5e37f3e7e3bb8dbd3500c2351e6044639aaa6a7e26a9bca2938ff1a221fc -size 2696062 +oid sha256:bbc4f0accba5404de8a7ca0e0244a7135f4849dec4bdff4f583dd0a628d5dce6 +size 2693877 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 3ec9313d65..3fc4fd14c3 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:837660ddc9eb8705faefa40f1e7941e64be9370b502c426ace9287aee6d7b3ba -size 700129 +oid sha256:0f3ae3105ecc41f4e3bdddb51d00af88ee2723b890cef64849dd7777e3e56815 +size 707961 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 1913057de5..93df0b4b40 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:9f149c637ed4a9d0c0bbefdddc6559e14571594c2eb611caff3743555fa0019e -size 3710624 +oid sha256:9a899d6d63c338da9e3b4a73aa1a8830ec8b313353337da9f167a423a7b26d17 +size 3759340 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 f4d8bbf81a..aa70d239dd 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:1fae72e2e6e7b4ae02158809002ac0b4733b511879ad6e94503873dba3567ea8 -size 632444 +oid sha256:3b0929f81211a80f9fb4057351675aa7b339feffc39b2c1ba03c35613db36f31 +size 631179 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 b03975b414..504e5ca2a2 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:dff8717b619614a2814c16265bfebc691d5830cc414b0466a21245780f5c7fdb -size 2579101 +oid sha256:6b907e68197390a390c890787936939e694be916428a54362cb4597f981fb0ba +size 2576478 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 d29287f159..2cff6cf182 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:8c14e99f9f965535531a9a1d6f9e09a943bc1cccd98edd02a397fec6c67334c0 -size 705842 +oid sha256:8a4c6e440403f50d00d0741cb52c809c08f4376069fdc9e1a5b83a757af491a0 +size 713783 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 ee31800225..4aa061a157 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:119e047916ab4d05b6583a3beef0eb37e7495216f15694cbac39d0f0b2b1dea5 -size 1485642 +oid sha256:e62cb33a5c0181af5ff141fd7515df618418c119a476d61b60dbdc8e8ec49d1a +size 1506655 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 991e60e6d7..bab6706312 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:6e0cb2157d0636b1410b2b0a23361adb3ad9907d4ca67153ca5aeb1f537e3fc8 -size 1078339 +oid sha256:0f5a0c3c54518e838eedfff952ffd56211666e0ba68378d8d9f58fe14201b7e5 +size 1073431 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 b3c64648a2..95870af46a 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:c1302f784858ce5dd12eff39d0a40deea009116d528027ac186b9d3948d265da -size 4317644 +oid sha256:7b8cbfdf2b4c95bc4994dd9769ee79320ca3cadbe63619da16f9087e7e4eb8f5 +size 4311639 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 2589c0d26b..68c8226079 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:b4e9c35c832f7d1e08407bec62010dab2b22d17ead9952d3cdd064ada57b7c06 -size 661736 +oid sha256:7dc6e725012cf617236504d79d00d188e8b628fad214cccf50c2f113b2986e29 +size 661272 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 165da9673e..1a8a9ee61a 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:7d24be684040053fabdcd49cd4d0c17031d72a51213d817bb8aec89505475467 -size 2799986 +oid sha256:c44f5ba138e1e00e58ff77c5d885eda4e2729eb2200ace6d501498b8de152e78 +size 2797946 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 9339be7d76..95d5587f28 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:7845f464092b2cf6a42727cfeb4068eedacaafa0c18d482be4088492403b738d -size 725030 +oid sha256:494241eb356f652da4fd4098731eca4fb65521a85b83c83f1e81776bec458fad +size 731026 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 0ddd6d9c58..1050a72c6f 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:bf398f47196d4bac9a9803d740a626b029eb2b6d2a803474634d6aaf6bbb5147 -size 3838682 +oid sha256:3ffd0bcc97b5ac3bac16a29df0cadbb1e83bb2aa2cdfbb6c536cf4766d6140a3 +size 3887621 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 0a987530fe..82ac2185d9 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:89f92c9c2c73c9632d54f3ee7d6d6b4cc45679ab6cdc7e590852eb163dc42f7f -size 650715 +oid sha256:7fd11d5d9154f3c3f90c8455fc61f3d13ac6b8a0882cba251763e7ad4b3374f2 +size 649539 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 2835d8a1eb..ace0ed5110 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:d0635df51a9655c9cc2e9bc506839beb31376a30bf11d682118fc9cedee919b3 -size 2661453 +oid sha256:6b936c5def6d4a8bc6c00e987a30f6cc77a0d74ead5eae4bf3a6e356814dc12d +size 2658586 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 9a288b75c6..461b01cc04 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:c6ff3b108aa49b9c34960abf726cea9829e033f9fabd1605b3a2b25f9e5eafb9 -size 899011 +oid sha256:7fd69ce20e614734e4140f3cc32e2fc15c5e8521367cca0df32b028874c2577d +size 913056 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 6d72a0763c..b087135b5f 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:fb1c4f3fc29e0e7ba7c27b261b8ce6bb5218b6c24e3da1773d8a3f97a4b72213 -size 1634320 +oid sha256:2f790abfb5ed2ae58ffd2c2ea7e4442aa46b4aba13c1e5a4936b40849b754923 +size 1682802 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 39c6546f84..920ec0d132 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:e78da569cd6daae764599bff8075835abae4de05bd5426ac062c865a20b4249d -size 1364819 +oid sha256:68ccaa29cf16c38d5843e6ed43b45206f88c2501312702d1818e69626ee21a68 +size 1357570 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 7366f79d2b..dc45d7bb08 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:45bf552ac98b3d5cfc41d6de3f779ca0e0d310757937ce059ae4caa2b991c08e -size 5201274 +oid sha256:ec4dd35e0de4507ee3265ecbd3b12a98c35dee6eed09adc0417937d8a9053e90 +size 5201564 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 d375a2ee4a..233ab933b2 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:bdb108fba3396dae357bdc9c8dad028a4b7c4ff4e6a752b9f3072583ec90dacc -size 831243 +oid sha256:54be8f8cc2105d7ca6902b9f097278470e97dd43d2094cc627374c06b5649e95 +size 829474 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 564a44b9eb..7ddbe15bdf 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:84e9e1d9184de99d780847503d5b180728653f325e5841936d83fbab8481acac -size 3350703 +oid sha256:86a11338827726a6253e4286b22bc5cf38eed1bed9125d4bd827d56047ca1995 +size 3349733 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 ce0f262e33..fbbc8b89ad 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:0ccc8ecb2f65605c40efba35b7d48b297c9e757fc9e0618fa1e5a895419997ce -size 917377 +oid sha256:fd30ac9b5bd7bda07da870cfebf293e7b88ce7a0162a4d4934403faac635ad59 +size 932843 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 3f87054608..577cbbaf7c 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:240cd4484288fd15b77a6446c277c7f23834b5e00854d49ff3b56bda39381322 -size 4649765 +oid sha256:961f4bda202abc0b62317041dad706150e92cc9cb5fb0054b93a3b6145bc8386 +size 4746726 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 61abc5c2c8..59db35d4cd 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:6967ec82b2a59c7784b7856fe975b8d75da2a510ebf3cf88e98452c93f29daf2 -size 819973 +oid sha256:1803e3d8401dd36e8c623cb8c3f06dcf1b5da3dbcc5cb2c53981bf0a7c5bf036 +size 819754 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 9e20202ac1..3802b4944f 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:c4899cb65d2f92b2d5f25109c094b39d20e2fea913bcdce28c0471d7bd0daf6e -size 3196486 +oid sha256:a2d9d02676cbc8b4aafd4266b30afd1d8bc898609d5d5772485be5435695bcd7 +size 3194696 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 272272f6bb..5746c94ee7 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:6509d44af83b0cf60a946f5899e987b88dcca48c561b9ad350a84818c912160a -size 551071 +oid sha256:782e5ace120cdf396351b33765c5013652ca954628ffbcb41de6232022500184 +size 558731 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 712a644605..89557ad71e 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:a086601307cfc562c256fba580b909f8efb2d92d828380bd022c9f0ee957b44b -size 1105230 +oid sha256:778d56054f4700668696827ae2c181a6f74ba0cf8f884ea2234e9f46f65119b2 +size 1127823 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 b24163610f..ffc8caa7e4 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:7db0ddfd91782f36d0918cbdf63bbc123c0e8c7b9791879d6c2914503a80341c -size 858066 +oid sha256:bdba2755ced54d96e34e8db8ace3f228e7af0fbaa79ac7f5fd226429bba7e24a +size 856618 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 61b7d6b5a1..7f82f7912a 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:ef678a07280c70cd501685f3968b01a8f745b0ae253daca731a5c9f0054fcd66 -size 3436947 +oid sha256:e8f24d13a71cd7ec356a6910f6a799885007e45227f4111577e67aaa41a32be3 +size 3432376 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 b986835074..f07a891752 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:ec455d7e1f241108602545bf8f129a320607466db4be66d536a02e8ace07b941 -size 521060 +oid sha256:878ee6513e893f022f3f9ba1dcacfd1513dbde0e8468458d646914bfdae43e05 +size 519598 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 78861c7450..b15556a2e4 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:4e22656a9f675eba962d71caf593089d28f6720b9a5d43aab4706c8f17d408ca -size 2118360 +oid sha256:a9d3d5ee7c607dc521558f6cf08315536c58472d89a80c977858617a876abb1d +size 2116740 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 3d61e7a6ce..dde328d20b 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:b7e9530df6e871d5359697c75d1fb103b0ef365463e04357b7a58fc21618894c -size 564829 +oid sha256:6fdcffb0d4ebe6b7d3aff86e152d08e9e99693caad53dafecf1a6c2fff3f6989 +size 572126 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 5c7cf3e061..d5362422be 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:3a26b71841f99da2a7662c2f35dbe132985bc2e047a435fb3af7ef56a87d82ca -size 2880351 +oid sha256:7f7100f3ff88d340d34aa053e5cb66277e158166f3a5feb4f1a76e6f7476e960 +size 2931598 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 6dc2f2d658..f6c08aef4a 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:3a37a9a5ca2eecb69b4590595372c0b4af02fdc8a95911cce1b2a9a5d0e6af31 -size 513015 +oid sha256:be4c4355124907c20e40164149321c7e0b3064515cb8c17b19d0af28743c4c83 +size 512214 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 9ee8a5191f..d7a2ce4bd7 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:92008317f00fcfb2bb5a0d6b73989d3909bf151582ca913d26ea116c408e322a -size 2010316 +oid sha256:9d60277b482678053e5c0d6d8e6997eb69beff530dd89abc2a5ceb0a3280421b +size 2009015 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 754ba6d89d..5f28434214 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:b3398db307809b1d87d4b1427de7ffd1947fdd6be1ead4261e8cf4931e8cf559 -size 823889 +oid sha256:bfbed58e60cbaeb556981c4e4c2268d1decec131bab2ac91a30bb49b066e169f +size 841311 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 51a21acd33..5927077dd2 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:8356ea868e0ac02cb6e65708b2a5a859101de6608bdf6613b9c3328d973ff16a -size 1693739 +oid sha256:2960bdd80dac034f60d5254f6e12db36999dae070439610cef63425e56e3708d +size 1752068 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 fcdbe4ed39..1362d07deb 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:b6464b6cd475c3b1f95ac2a6ad3969b4acd5fc7a1b8a38979e167bfe04ecb182 -size 1239596 +oid sha256:216cf5a99c341d18915748ee69e4cb0aff6edcf990737e64425ce023ef8ea937 +size 1241938 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index c10f84ce99..e1f0a26c10 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:ded3905499bc94084ef76c3daa68ff64beadafd41c281d1ddaa652ec4ae33ba6 -size 4984939 +oid sha256:e603590a4359904cd02283c3b547cbc25dd469ed9c23dc7285270a97804fc8c4 +size 4985635 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 1cb13d1e9d..b0e47bc0b3 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:7c311b2bdadf672931e5aa1c3b8e8d8c14e67316314033947e19e5f916c4a07e -size 787375 +oid sha256:24cc667fabd6f8d76672dde4b8da2ef2efcaa84b4076a81842657f879bdc6901 +size 788447 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index 43fc9f02e0..fec4c9cb2c 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:da1248a08071627919bf4baecc16b44fc64685de7a99f5ce5c2ce3abb8a29b5e -size 3335936 +oid sha256:45ec821144ff554b802e4661e8524639290cfc4ef01f069b8bccce34f8c019fa +size 3340247 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 216e6c3678..ef33101e1f 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:2edaa7095ec9af4beb751b337f5f7469a502f06356974ae108f4b29388844ca2 -size 845688 +oid sha256:394b037f209f09489727efdb761f9c6685c5209954746ec00f0d00cff09e7954 +size 862336 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 54d4647a5b..334470cda7 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:b050d083128f013b4a356eaf17f4be664ca2ac2ff1b9049c814d65aa31511cd4 -size 4503558 +oid sha256:628c78b14e47ed3ed7afd71b7e9c31ef80921e7f11fa2bafc55d562c7e5c5ef4 +size 4617016 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 3faf0cc9de..2dfc382852 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:ce3ab1587bc067f597e54b6d7a22b93200af44bbf1b0f04ce6395d423b4a7335 -size 775835 +oid sha256:7d0e68afb76dc8b498fd70445d0216d6e622f0d16dd9686b8a71fe3600da24e9 +size 777153 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index ee8df4bf3f..2c416cd3bb 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:2f0b51cbf8197fdda3282a66a39eef97032f783b3ac06578c152a1ddabea006c -size 3171176 +oid sha256:3832590ae7b1f9c8e98f84beec1a3bec6f77b3b6a8e9664f2c103182228dddd8 +size 3174270 diff --git a/middleware/archived-enterprise-versions-assets.js b/middleware/archived-enterprise-versions-assets.js index 540aab8d5d..2b36d17c5e 100644 --- a/middleware/archived-enterprise-versions-assets.js +++ b/middleware/archived-enterprise-versions-assets.js @@ -15,12 +15,37 @@ const cacheControl = cacheControlFactory(60 * 60 * 24) // See also ./archived-enterprise-versions.js for non-CSS/JS paths export default async function archivedEnterpriseVersionsAssets(req, res, next) { + // Only match asset paths + // This can be true on /enterprise/2.22/_next/static/foo.css + // or /_next/static/foo.css + if (!patterns.assetPaths.test(req.path)) return next() + + // We now know the URL is either /enterprise/2.22/_next/static/foo.css + // or the regular /_next/static/foo.css. But we're only going to + // bother looking it up on https://github.github.com/help-docs-archived-enterprise-versions + // if the URL has the enterprise bit in it, or if the path was + // /_next/static/foo.css *and* its Referrer had the enterprise + // bit in it. + if ( + !( + patterns.getEnterpriseVersionNumber.test(req.path) || + patterns.getEnterpriseServerNumber.test(req.path) || + patterns.getEnterpriseVersionNumber.test(req.get('referrer')) || + patterns.getEnterpriseServerNumber.test(req.get('referrer')) + ) + ) { + return next() + } + + // Now we know the URL is definitely not /_next/static/foo.css + // So it's probably /enterprise/2.22/_next/static/foo.css and we + // should see if we might find this in the proxied backend. + // But `isArchivedVersion()` will only return truthy if the + // Referrer header also indicates that the request for this static + // asset came from a page const { isArchived, requestedVersion } = isArchivedVersion(req) if (!isArchived) return next() - // Only match asset paths - if (!patterns.assetPaths.test(req.path)) return next() - const assetPath = req.path.replace(`/enterprise/${requestedVersion}`, '') const proxyPath = path.join('/', requestedVersion, assetPath) @@ -37,6 +62,28 @@ export default async function archivedEnterpriseVersionsAssets(req, res, next) { cacheControl(res) return res.send(r.body) } catch (err) { - return next(404) + // Primarly for the developers working on tests that mock + // requests. If you don't set up `nock` correctly, you might + // not realize that and think it failed for other reasons. + if (err.toString().includes('Nock: No match for request')) { + throw err + } + + // It's important that we don't give up on this by returning a 404 + // here. It's better to let this through in case the asset exists + // beyond the realm of archived enterprise versions. + // For example, image you load + // /enterprise-server@2.21/en/DOES/NOT/EXIST in your browser. + // Quickly, we discover that the proxying is failing because + // it didn't find a page called `/en/DOES/NOT/EXIST` over there. + // So, we proceed to render *our* 404 HTML page. + // Now, on that 404 page, it will reference static assets too. + // E.g. + // These will thus be requested, with a Referrer header that + // forces us to give it a chance, but it'll find it can't find it + // but we mustn't return a 404 yet, because that + // /_next/static/styles.css will probably still succeed because the 404 + // page is not that of the archived enterprise version. + return next() } } diff --git a/middleware/archived-enterprise-versions.js b/middleware/archived-enterprise-versions.js index 86a30831c8..056a3f65a2 100644 --- a/middleware/archived-enterprise-versions.js +++ b/middleware/archived-enterprise-versions.js @@ -13,7 +13,17 @@ import { setFastlySurrogateKey, SURROGATE_ENUMS } from './set-fastly-surrogate-k import got from 'got' import { readCompressedJsonFileFallback } from '../lib/read-json-file.js' import { cacheControlFactory } from './cache-control.js' -import { pathLanguagePrefixed } from '../lib/languages.js' +import { pathLanguagePrefixed, languagePrefixPathRegex } from '../lib/languages.js' + +function splitByLanguage(uri) { + let language = null + let withoutLanguage = uri + if (languagePrefixPathRegex.test(uri)) { + language = uri.match(languagePrefixPathRegex)[1] + withoutLanguage = uri.replace(languagePrefixPathRegex, '/') + } + return [language, withoutLanguage] +} function readJsonFileLazily(xpath) { const cache = new Map() @@ -135,10 +145,21 @@ export default async function archivedEnterpriseVersions(req, res, next) { versionSatisfiesRange(requestedVersion, `>=${firstVersionDeprecatedOnNewSite}`) && versionSatisfiesRange(requestedVersion, `<=${lastVersionWithoutArchivedRedirectsFile}`) ) { + const [language, withoutLanguagePath] = splitByLanguage(req.path) + // `archivedRedirects` is a callable because it's a lazy function // and memoized so calling it is cheap. - const redirect = archivedRedirects()[req.path] - if (redirect && redirect !== req.path) { + + const newPath = archivedRedirects()[withoutLanguagePath] + // Some entries in the lookup exists purely for the sake of injecting + // language. + // E.g. '/enterprise/2.15/user' + // URLs like this only need to redirect the original `req.path` + // didn't already have a language + if (newPath !== undefined && (newPath || !language)) { + // Construct the new URL by combining the new language and the + // new destination. + const redirect = `/${language || 'en'}${newPath || withoutLanguagePath}` cacheAggressively(res) return res.redirect(redirectCode, redirect) } diff --git a/middleware/catch-bad-accept-language.js b/middleware/catch-bad-accept-language.js deleted file mode 100644 index 4c0fc0b36a..0000000000 --- a/middleware/catch-bad-accept-language.js +++ /dev/null @@ -1,15 +0,0 @@ -import accept from '@hapi/accept' - -// Next.JS uses the @hapi/accept package to parse and detect languages. If the accept-language header is malformed -// it throws an error from within Next.JS, which results in a 500 response. This ends up being noisy because we -// track 500s. To counteract this, we'll try to catch the error first and make sure it doesn't happen -export default function catchBadAcceptLanguage(req, res, next) { - try { - accept.language(req.headers['accept-language']) - } catch (e) { - // if there's a problem with parsing 'accept-language', just clear it out. - req.headers['accept-language'] = '' - } - - return next() -} diff --git a/middleware/find-page.js b/middleware/find-page.js index 702921d15f..69446aef44 100644 --- a/middleware/find-page.js +++ b/middleware/find-page.js @@ -1,3 +1,4 @@ +import getRedirect from '../lib/get-redirect.js' // This middleware uses the request path to find a page in the preloaded context.pages object export default async function findPage(req, res, next) { @@ -16,7 +17,7 @@ export default async function findPage(req, res, next) { const englishPath = req.pagePath.replace(new RegExp(`^/${req.language}`), '/en') // NOTE the fallback page will have page.languageCode = 'en' page = req.context.pages[englishPath] - const redirectToPath = req.context.redirects[englishPath] + const redirectToPath = getRedirect(englishPath, req.context) // If the requested translated page has a 1-1 mapping in English, // redirect to that English page diff --git a/middleware/handle-errors.js b/middleware/handle-errors.js index a6fbc6f2c5..f27f60b43d 100644 --- a/middleware/handle-errors.js +++ b/middleware/handle-errors.js @@ -1,6 +1,9 @@ import FailBot from '../lib/failbot.js' -import loadSiteData from '../lib/site-data.js' import { nextApp } from './next.js' +import { setFastlySurrogateKey, SURROGATE_ENUMS } from './set-fastly-surrogate-key.js' +import { cacheControlFactory } from './cache-control.js' + +const cacheControl = cacheControlFactory(60) // 1 minute function shouldLogException(error) { const IGNORED_ERRORS = [ @@ -33,7 +36,22 @@ export default async function handleError(error, req, res, next) { // anywhere. So this is why we log it additionally. // Note, not using console.error() because it's arguably handled. // Some tests might actually expect a 500 error. - if (process.env.NODE_ENV === 'test') { + + if (req.path.startsWith('/assets') || req.path.startsWith('/_next/static')) { + // By default, Fastly will cache 404 responses unless otherwise + // told not to. + // See https://docs.fastly.com/en/guides/how-caching-and-cdns-work#http-status-codes-cached-by-default + // Let's cache our 404'ing assets conservatively. + // The Cache-Control is short, and let's use the default surrogate + // key just in case it was a mistake. + cacheControl(res) + // Undo the cookie setting that CSRF sets. + res.removeHeader('set-cookie') + // Makes sure the surrogate key is NOT the manual one if it failed. + // This basically unsets what was assumed in the beginning of + // loading all the middlewares. + setFastlySurrogateKey(res, SURROGATE_ENUMS.DEFAULT) + } else if (process.env.NODE_ENV === 'test') { console.warn('An error occurrred in some middleware handler', error) } @@ -47,14 +65,11 @@ export default async function handleError(error, req, res, next) { return next(error) } - // if the error is thrown before req.context is created (say, in the Page class), - // set req.context.site here so we can pass data/ui.yml text to the 500 layout if (!req.context) { - const site = await loadSiteData() - req.context = { site: site[req.language || 'en'].site } + req.context = {} } // display error on the page in development and staging, but not in production - if (req.context && process.env.HEROKU_PRODUCTION_APP !== 'true') { + if (process.env.HEROKU_PRODUCTION_APP !== 'true') { req.context.error = error } diff --git a/middleware/index.js b/middleware/index.js index 4a3951c374..ea3ed352f4 100644 --- a/middleware/index.js +++ b/middleware/index.js @@ -1,3 +1,6 @@ +import fs from 'fs' +import path from 'path' + import express from 'express' import instrument from '../lib/instrument-middleware.js' import haltOnDroppedConnection from './halt-on-dropped-connection.js' @@ -12,10 +15,8 @@ import csp from './csp.js' import cookieParser from './cookie-parser.js' import csrf from './csrf.js' import handleCsrfErrors from './handle-csrf-errors.js' -import compression from 'compression' 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' import recordRedirect from './record-redirect.js' import connectSlashes from 'connect-slashes' @@ -138,6 +139,11 @@ export default function (app) { // Can be aggressive because images inside the content get unique // URLs with a cache busting prefix. maxAge: '7 days', + immutable: process.env.NODE_ENV !== 'development', + // This means, that if you request a file that starts with /assets/ + // any file doesn't exist, don't bother (NextJS) rendering a + // pretty HTML error page. + fallthrough: false, }) ) app.use( @@ -146,9 +152,33 @@ export default function (app) { index: false, etag: false, maxAge: '7 days', // A bit longer since releases are more sparse + // See note about about use of 'fallthrough' + fallthrough: false, }) ) + // In development, let NextJS on-the-fly serve the static assets. + // But in production, don't let NextJS handle any static assets + // because they are costly to generate (the 404 HTML page) + // and it also means that a CSRF cookie has to be generated. + if (process.env.NODE_ENV !== 'development') { + const assetDir = path.join('.next', 'static') + if (!fs.existsSync(assetDir)) + throw new Error(`${assetDir} directory has not been generated. Run 'npm run build' first.`) + + app.use( + '/_next/static/', + express.static(assetDir, { + index: false, + etag: false, + maxAge: '365 days', + immutable: true, + // See note about about use of 'fallthrough' + fallthrough: false, + }) + ) + } + // *** Early exits *** // Don't use the proxy's IP, use the requester's for rate limiting // See https://expressjs.com/en/guide/behind-proxies.html @@ -176,8 +206,6 @@ export default function (app) { // *** Headers *** app.set('etag', false) // We will manage our own ETags if desired - app.use(compression()) - app.use(catchBadAcceptLanguage) // *** Config and context for redirects *** app.use(reqUtils) // Must come before record-redirect and events @@ -186,6 +214,10 @@ export default function (app) { app.use(asyncMiddleware(instrument(context, './context'))) // Must come before early-access-*, handle-redirects app.use(asyncMiddleware(instrument(shortVersions, './contextualizers/short-versions'))) // Support version shorthands + // Must come before handleRedirects. + // This middleware might either redirect to serve something. + app.use(asyncMiddleware(instrument(archivedEnterpriseVersions, './archived-enterprise-versions'))) + // *** Redirects, 3xx responses *** // I ordered these by use frequency app.use(connectSlashes(false)) @@ -209,7 +241,6 @@ export default function (app) { // Check for a dropped connection before proceeding (again) app.use(haltOnDroppedConnection) - app.use(asyncMiddleware(instrument(archivedEnterpriseVersions, './archived-enterprise-versions'))) app.use(instrument(robots, './robots')) app.use( /(\/.*)?\/early-access$/, diff --git a/middleware/redirects/handle-redirects.js b/middleware/redirects/handle-redirects.js index 308fd67e10..d799f161a5 100644 --- a/middleware/redirects/handle-redirects.js +++ b/middleware/redirects/handle-redirects.js @@ -1,6 +1,7 @@ import patterns from '../../lib/patterns.js' import { URL } from 'url' import languages, { pathLanguagePrefixed } from '../../lib/languages.js' +import getRedirect from '../../lib/get-redirect.js' import { cacheControlFactory } from '../cache-control.js' const cacheControl = cacheControlFactory(60 * 60 * 24) // one day @@ -52,18 +53,42 @@ export default function handleRedirects(req, res, next) { // remove query params temporarily so we can find the path in the redirects object let redirectWithoutQueryParams = removeQueryParams(redirect) - // look for a redirect in the global object - // for example, given an incoming path /v3/activity/event_types - // find /en/developers/webhooks-and-events/github-event-types - redirectWithoutQueryParams = - req.context.redirects[redirectWithoutQueryParams] || redirectWithoutQueryParams + const redirectTo = getRedirect(redirectWithoutQueryParams, req.context) + + redirectWithoutQueryParams = redirectTo || redirectWithoutQueryParams - // add query params back in redirect = queryParams ? redirectWithoutQueryParams + queryParams : redirectWithoutQueryParams + if (!redirectTo && !pathLanguagePrefixed(req.path)) { + // No redirect necessary, but perhaps it's to a known page, and the URL + // currently doesn't have a language prefix, then we need to add + // the language prefix. + // We can't always force on the language prefix because some URLs + // aren't pages. They're other middleware endpoints such as + // `/healthz` which should never redirect. + // But for example, a `/authentication/connecting-to-github-with-ssh` + // needs to become `/en/authentication/connecting-to-github-with-ssh` + const possibleRedirectTo = `/en${req.path}` + if (possibleRedirectTo in req.context.pages) { + // As of Jan 2022 we always redirect to `/en` if the URL doesn't + // specify a language. ...except for the root home page (`/`). + // It's unfortunate but that's how it currently works. + // It's tracked in #1145 + // Perhaps a more ideal solution would be to do something similar to + // the code above for `req.path === '/'` where we look at the user + // agent for a header and/or cookie. + // Note, it's important to use `req.url` here and not `req.path` + // because the full URL can contain query strings. + // E.g. `/foo?json=breadcrumbs` + redirect = `/en${req.url}` + } + } + // do not redirect a path to itself // req._parsedUrl.path includes query params whereas req.path does not - if (redirect === req._parsedUrl.path) return next() + if (redirect === req._parsedUrl.path) { + return next() + } // do not redirect if the redirected page can't be found if (!req.context.pages[removeQueryParams(redirect)]) { diff --git a/middleware/search.js b/middleware/search.js index 37939de906..0878327036 100644 --- a/middleware/search.js +++ b/middleware/search.js @@ -2,17 +2,15 @@ import express from 'express' import libLanguages from '../lib/languages.js' import searchVersions from '../lib/search/versions.js' import loadLunrResults from '../lib/search/lunr-search.js' +import { cacheControlFactory } from './cache-control.js' + const languages = new Set(Object.keys(libLanguages)) const versions = new Set(Object.values(searchVersions)) - const router = express.Router() +const cacheControl = cacheControlFactory(60 * 60 * 24) +const noCacheControl = cacheControlFactory(0) -router.get('/', async function postSearch(req, res, next) { - res.set({ - 'surrogate-control': 'private, no-store', - 'cache-control': 'private, no-store', - }) - +router.get('/', async function getSearch(req, res, next) { const { query, version, language, filters, limit: limit_ } = req.query const limit = Math.min(parseInt(limit_, 10) || 10, 100) if (!versions.has(version) || !languages.has(language)) { @@ -31,12 +29,19 @@ router.get('/', async function postSearch(req, res, next) { }) // Only reply if the headers have not been sent and the request was not aborted... if (!res.headersSent && !req.aborted) { + cacheControl(res) + + // Undo the cookie setting that CSRF sets. + // Otherwise it can't be cached in the CDN. + res.removeHeader('set-cookie') + return res.status(200).json(results) } } catch (err) { console.error(err) // Only reply if the headers have not been sent and the request was not aborted... if (!res.headersSent && !req.aborted) { + noCacheControl(res) return res.status(400).json({ error: err.toString() }) } } diff --git a/package-lock.json b/package-lock.json index bcf074e3c5..785d7798dc 100644 --- a/package-lock.json +++ b/package-lock.json @@ -8,7 +8,6 @@ "license": "(MIT AND CC-BY-4.0)", "dependencies": { "@github/failbot": "0.8.0", - "@hapi/accept": "^5.0.2", "@primer/components": "^33.1.0", "@primer/css": "^19.1.1", "@primer/octicons": "^16.3.0", @@ -19,7 +18,6 @@ "ajv-formats": "^2.1.1", "cheerio": "^1.0.0-rc.10", "classnames": "^2.3.1", - "compression": "^1.7.4", "connect-datadog": "0.0.9", "connect-slashes": "^1.4.0", "cookie-parser": "^1.4.6", @@ -137,7 +135,6 @@ "git-diff": "^2.0.6", "glob": "^7.2.0", "graphql": "^16.3.0", - "heroku-client": "^3.1.0", "http-status-code": "^2.1.0", "husky": "^7.0.4", "japanese-characters": "^1.1.0", @@ -165,15 +162,13 @@ "strip-ansi": "^7.0.1", "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" }, "optionalDependencies": { "bottleneck": "^2.19.5", - "csv-parse": "^4.16.3", "esm": "^3.2.25", "image-size": "^1.0.0", "jest-puppeteer": "^5.0.4", @@ -5340,13 +5335,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" @@ -6389,14 +6384,6 @@ "resolved": "https://registry.npmjs.org/builtin-status-codes/-/builtin-status-codes-3.0.0.tgz", "integrity": "sha1-hZgoeOIbmOHGZCXgPQF0eI9Wnug=" }, - "node_modules/bytes": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/bytes/-/bytes-3.0.0.tgz", - "integrity": "sha1-0ygVQE1olpn4Wk6k+odV3ROpYEg=", - "engines": { - "node": ">= 0.8" - } - }, "node_modules/cacheable-lookup": { "version": "5.0.4", "resolved": "https://registry.npmjs.org/cacheable-lookup/-/cacheable-lookup-5.0.4.tgz", @@ -6996,47 +6983,6 @@ "integrity": "sha512-Rd3se6QB+sO1TwqZjscQrurpEPIfO0/yYnSin6Q/rD3mOutHvUrCAhJub3r90uNb+SESBuE0QYoB90YdfatsRg==", "dev": true }, - "node_modules/compressible": { - "version": "2.0.18", - "resolved": "https://registry.npmjs.org/compressible/-/compressible-2.0.18.tgz", - "integrity": "sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==", - "dependencies": { - "mime-db": ">= 1.43.0 < 2" - }, - "engines": { - "node": ">= 0.6" - } - }, - "node_modules/compression": { - "version": "1.7.4", - "resolved": "https://registry.npmjs.org/compression/-/compression-1.7.4.tgz", - "integrity": "sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==", - "dependencies": { - "accepts": "~1.3.5", - "bytes": "3.0.0", - "compressible": "~2.0.16", - "debug": "2.6.9", - "on-headers": "~1.0.2", - "safe-buffer": "5.1.2", - "vary": "~1.1.2" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/compression/node_modules/debug": { - "version": "2.6.9", - "resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz", - "integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==", - "dependencies": { - "ms": "2.0.0" - } - }, - "node_modules/compression/node_modules/ms": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz", - "integrity": "sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=" - }, "node_modules/concat-map": { "version": "0.0.1", "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz", @@ -7243,9 +7189,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", @@ -7532,12 +7478,6 @@ "node": ">= 0.8.0" } }, - "node_modules/csv-parse": { - "version": "4.16.3", - "resolved": "https://registry.npmjs.org/csv-parse/-/csv-parse-4.16.3.tgz", - "integrity": "sha512-cO1I/zmz4w2dcKHVvpCr7JVRu8/FymG5OEpmvsZYlccYolPBLoVGKUHgNoc4ZGkFeFlWGEDmMyBM+TTqRdW/wg==", - "optional": true - }, "node_modules/cwd": { "version": "0.10.0", "resolved": "https://registry.npmjs.org/cwd/-/cwd-0.10.0.tgz", @@ -10635,19 +10575,6 @@ "node": ">=10.0.0" } }, - "node_modules/heroku-client": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/heroku-client/-/heroku-client-3.1.0.tgz", - "integrity": "sha512-UfGKwUm5duzzSVI8uUXlNAE1mus6uPxmZPji4vuG1ArV5DYL1rXsZShp0OoxraWdEwYoxCUrM6KGztC68x5EZQ==", - "dev": true, - "dependencies": { - "is-retry-allowed": "^1.0.0", - "tunnel-agent": "^0.6.0" - }, - "engines": { - "node": ">=6.0.0" - } - }, "node_modules/hexoid": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/hexoid/-/hexoid-1.0.0.tgz", @@ -11492,15 +11419,6 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/is-retry-allowed": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/is-retry-allowed/-/is-retry-allowed-1.2.0.tgz", - "integrity": "sha512-RUbUeKwvm3XG2VYamhJL1xFktgjvPzL0Hq8C+6yrWIswDy3BIXGqCxhxkc30N9jqK311gVU137K8Ei55/zVJRg==", - "dev": true, - "engines": { - "node": ">=0.10.0" - } - }, "node_modules/is-shared-array-buffer": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz", @@ -21096,18 +21014,6 @@ "node": ">=0.6.11 <=0.7.0 || >=0.7.3" } }, - "node_modules/tunnel-agent": { - "version": "0.6.0", - "resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz", - "integrity": "sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=", - "dev": true, - "dependencies": { - "safe-buffer": "^5.0.1" - }, - "engines": { - "node": "*" - } - }, "node_modules/type-check": { "version": "0.4.0", "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz", @@ -22569,12 +22475,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", @@ -26648,13 +26548,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": { @@ -27559,11 +27459,6 @@ "resolved": "https://registry.npmjs.org/builtin-status-codes/-/builtin-status-codes-3.0.0.tgz", "integrity": "sha1-hZgoeOIbmOHGZCXgPQF0eI9Wnug=" }, - "bytes": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/bytes/-/bytes-3.0.0.tgz", - "integrity": "sha1-0ygVQE1olpn4Wk6k+odV3ROpYEg=" - }, "cacheable-lookup": { "version": "5.0.4", "resolved": "https://registry.npmjs.org/cacheable-lookup/-/cacheable-lookup-5.0.4.tgz", @@ -28016,43 +27911,6 @@ "integrity": "sha512-Rd3se6QB+sO1TwqZjscQrurpEPIfO0/yYnSin6Q/rD3mOutHvUrCAhJub3r90uNb+SESBuE0QYoB90YdfatsRg==", "dev": true }, - "compressible": { - "version": "2.0.18", - "resolved": "https://registry.npmjs.org/compressible/-/compressible-2.0.18.tgz", - "integrity": "sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==", - "requires": { - "mime-db": ">= 1.43.0 < 2" - } - }, - "compression": { - "version": "1.7.4", - "resolved": "https://registry.npmjs.org/compression/-/compression-1.7.4.tgz", - "integrity": "sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==", - "requires": { - "accepts": "~1.3.5", - "bytes": "3.0.0", - "compressible": "~2.0.16", - "debug": "2.6.9", - "on-headers": "~1.0.2", - "safe-buffer": "5.1.2", - "vary": "~1.1.2" - }, - "dependencies": { - "debug": { - "version": "2.6.9", - "resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz", - "integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==", - "requires": { - "ms": "2.0.0" - } - }, - "ms": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz", - "integrity": "sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=" - } - } - }, "concat-map": { "version": "0.0.1", "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz", @@ -28221,9 +28079,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", @@ -28456,12 +28314,6 @@ "http-errors": "~1.7.3" } }, - "csv-parse": { - "version": "4.16.3", - "resolved": "https://registry.npmjs.org/csv-parse/-/csv-parse-4.16.3.tgz", - "integrity": "sha512-cO1I/zmz4w2dcKHVvpCr7JVRu8/FymG5OEpmvsZYlccYolPBLoVGKUHgNoc4ZGkFeFlWGEDmMyBM+TTqRdW/wg==", - "optional": true - }, "cwd": { "version": "0.10.0", "resolved": "https://registry.npmjs.org/cwd/-/cwd-0.10.0.tgz", @@ -30816,16 +30668,6 @@ "resolved": "https://registry.npmjs.org/helmet/-/helmet-4.6.0.tgz", "integrity": "sha512-HVqALKZlR95ROkrnesdhbbZJFi/rIVSoNq6f3jA/9u6MIbTsPh3xZwihjeI5+DO/2sOV6HMHooXcEOuwskHpTg==" }, - "heroku-client": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/heroku-client/-/heroku-client-3.1.0.tgz", - "integrity": "sha512-UfGKwUm5duzzSVI8uUXlNAE1mus6uPxmZPji4vuG1ArV5DYL1rXsZShp0OoxraWdEwYoxCUrM6KGztC68x5EZQ==", - "dev": true, - "requires": { - "is-retry-allowed": "^1.0.0", - "tunnel-agent": "^0.6.0" - } - }, "hexoid": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/hexoid/-/hexoid-1.0.0.tgz", @@ -31405,12 +31247,6 @@ "has-tostringtag": "^1.0.0" } }, - "is-retry-allowed": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/is-retry-allowed/-/is-retry-allowed-1.2.0.tgz", - "integrity": "sha512-RUbUeKwvm3XG2VYamhJL1xFktgjvPzL0Hq8C+6yrWIswDy3BIXGqCxhxkc30N9jqK311gVU137K8Ei55/zVJRg==", - "dev": true - }, "is-shared-array-buffer": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.1.tgz", @@ -38688,15 +38524,6 @@ "integrity": "sha512-1h/Lnq9yajKY2PEbBadPXj3VxsDDu844OnaAo52UVmIzIvwwtBPIuNvkjuzBlTWpfJyUbG3ez0KSBibQkj4ojg==", "dev": true }, - "tunnel-agent": { - "version": "0.6.0", - "resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz", - "integrity": "sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=", - "dev": true, - "requires": { - "safe-buffer": "^5.0.1" - } - }, "type-check": { "version": "0.4.0", "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz", @@ -39806,12 +39633,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 d68ba8e286..d4414fcf92 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,6 @@ ], "dependencies": { "@github/failbot": "0.8.0", - "@hapi/accept": "^5.0.2", "@primer/components": "^33.1.0", "@primer/css": "^19.1.1", "@primer/octicons": "^16.3.0", @@ -21,7 +20,6 @@ "ajv-formats": "^2.1.1", "cheerio": "^1.0.0-rc.10", "classnames": "^2.3.1", - "compression": "^1.7.4", "connect-datadog": "0.0.9", "connect-slashes": "^1.4.0", "cookie-parser": "^1.4.6", @@ -139,7 +137,6 @@ "git-diff": "^2.0.6", "glob": "^7.2.0", "graphql": "^16.3.0", - "heroku-client": "^3.1.0", "http-status-code": "^2.1.0", "husky": "^7.0.4", "japanese-characters": "^1.1.0", @@ -167,8 +164,7 @@ "strip-ansi": "^7.0.1", "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" @@ -178,7 +174,6 @@ "name": "docs.github.com", "optionalDependencies": { "bottleneck": "^2.19.5", - "csv-parse": "^4.16.3", "esm": "^3.2.25", "image-size": "^1.0.0", "jest-puppeteer": "^5.0.4", @@ -197,7 +192,6 @@ "build": "next build", "debug": "cross-env NODE_ENV=development ENABLED_LANGUAGES='en,ja' nodemon --inspect server.mjs", "dev": "npm start", - "heroku-postbuild": "node script/early-access/clone-for-build.js && npm run build", "lint": "eslint '**/*.{js,mjs,ts,tsx}'", "lint-translation": "cross-env NODE_OPTIONS=--experimental-vm-modules TEST_TRANSLATION=true jest tests/linting/lint-files.js", "pa11y-ci": "pa11y-ci", diff --git a/pages/[versionId]/[productId]/index.tsx b/pages/[versionId]/[productId]/index.tsx index fa563d660e..dd0393ac35 100644 --- a/pages/[versionId]/[productId]/index.tsx +++ b/pages/[versionId]/[productId]/index.tsx @@ -45,10 +45,10 @@ function initiateArticleScripts() { type Props = { mainContext: MainContextT - productLandingContext: ProductLandingContextT - productGuidesContext: ProductGuidesContextT - tocLandingContext: TocLandingContextT - articleContext: ArticleContextT + productLandingContext?: ProductLandingContextT + productGuidesContext?: ProductGuidesContextT + tocLandingContext?: TocLandingContextT + articleContext?: ArticleContextT } const GlobalPage = ({ mainContext, @@ -57,7 +57,6 @@ const GlobalPage = ({ tocLandingContext, articleContext, }: Props) => { - const { currentLayoutName, relativePath } = mainContext const router = useRouter() useEffect(() => { @@ -70,30 +69,32 @@ const GlobalPage = ({ }, [router.events]) let content - if (currentLayoutName === 'product-landing') { + if (productLandingContext) { content = ( ) - } else if (currentLayoutName === 'product-guides') { + } else if (productGuidesContext) { content = ( ) - } else if (relativePath?.endsWith('index.md')) { + } else if (tocLandingContext) { content = ( ) - } else { + } else if (articleContext) { content = ( ) + } else { + throw new Error('No context provided to page') } return {content} @@ -105,13 +106,23 @@ export const getServerSideProps: GetServerSideProps = async (context) => const req = context.req as any const res = context.res as any + const props: Props = { + mainContext: getMainContext(req, res), + } + const { currentLayoutName, relativePath } = props.mainContext + + // This looks a little funky, but it's so we only send one context's data to the client + if (currentLayoutName === 'product-landing') { + props.productLandingContext = getProductLandingContextFromRequest(req) + } else if (currentLayoutName === 'product-guides') { + props.productGuidesContext = getProductGuidesContextFromRequest(req) + } else if (relativePath?.endsWith('index.md')) { + props.tocLandingContext = getTocLandingContextFromRequest(req) + } else { + props.articleContext = getArticleContextFromRequest(req) + } + return { - props: { - mainContext: getMainContext(req, res), - productLandingContext: getProductLandingContextFromRequest(req), - productGuidesContext: getProductGuidesContextFromRequest(req), - tocLandingContext: getTocLandingContextFromRequest(req), - articleContext: getArticleContextFromRequest(req), - }, + props, } } 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/content-migrations/update-short-titles-from-csv.js b/script/content-migrations/update-short-titles-from-csv.js deleted file mode 100755 index 8fe838acc5..0000000000 --- a/script/content-migrations/update-short-titles-from-csv.js +++ /dev/null @@ -1,78 +0,0 @@ -#!/usr/bin/env node -import fs from 'fs/promises' -import path from 'path' -import { exit } from 'process' - -import csv from 'csv-parse' -// NOTE: If you get this error: -// -// Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'csv-parse' ... -// -// it's because you haven't installed all the *optional* dependencies. -// To do that, run: -// -// npm install --include=optional -// -import readFrontmatter from '../../lib/read-frontmatter.js' - -main() - -async function main() { - let fileCounter = 0 - let csvHeader = [] - const csvFileName = 'shortTitles.csv' - const filePath = path.join(process.cwd(), csvFileName) - const reader = fs.createReadStream(filePath) - - // Parse each row of the csv - reader - .pipe(csv()) - .on('data', (csvData) => { - if (csvHeader.length === 0) { - csvHeader = verifyHeader(csvData) - } else { - if (csvData[3] && csvData[4]) { - updateFrontmatter(csvData) - fileCounter++ - } - } - }) - .on('end', () => { - console.log( - `⭐ Completed updating the shortTitle frontmatter.\nUpdated ${fileCounter} files.` - ) - }) -} - -async function updateFrontmatter(csvData) { - const filePath = path.join(process.cwd(), csvData[4]) - const fileContent = await fs.readFile(filePath, 'utf8') - const { content, data } = readFrontmatter(fileContent) - data.shortTitle = csvData[3] - const newContents = readFrontmatter.stringify(content, data, { lineWidth: 10000 }) - await fs.writeFile(filePath, newContents) -} - -// Ensure the columns being read out are in the location expected -async function verifyHeader(csvData) { - const csvHeader = [] - - csvData.forEach((element) => { - csvHeader.push(element) - }) - - if (csvHeader[3] !== 'Short title') { - console.log( - `The CSV headers are malformed. Expected to see column 3 contain the header 'Short title'` - ) - exit(1) - } - if (csvHeader[4] !== 'Relative path') { - console.log( - `The CSV headers are malformed. Expected to see column 4 contain the header 'Relative path'` - ) - exit(1) - } - - return csvHeader -} 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} `, '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} ' or '${PRODUCTION_FLAG}'` - ) -} - -if (isProduction && isStaging) { - invalidateAndExit( - 'commander.conflictingArgument', - `error: must specify option '${STAGING_FLAG} ' 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/script/deployment/create-staging-app-name.js b/script/deployment/create-staging-app-name.js deleted file mode 100644 index cee33514bc..0000000000 --- a/script/deployment/create-staging-app-name.js +++ /dev/null @@ -1,18 +0,0 @@ -import GithubSlugger from 'github-slugger' -const slugify = GithubSlugger.slug - -const APP_NAME_MAX_LENGTH = 30 - -export default function ({ prefix = '', repo, pullNumber, branch }) { - return ( - `${prefix}${repo}-${pullNumber}--${slugify(branch)}` - // Shorten the string to the max allowed length - .slice(0, APP_NAME_MAX_LENGTH) - // Convert underscores to dashes - .replace(/_/g, '-') - // Remove trailing dashes - .replace(/-+$/, '') - // Make it all lowercase - .toLowerCase() - ) -} diff --git a/script/deployment/deploy-to-production.js b/script/deployment/deploy-to-production.js deleted file mode 100755 index b23482bc98..0000000000 --- a/script/deployment/deploy-to-production.js +++ /dev/null @@ -1,465 +0,0 @@ -#!/usr/bin/env node -import got from 'got' -import Heroku from 'heroku-client' -import { setOutput } from '@actions/core' - -const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms)) - -const SLEEP_INTERVAL = 5000 -const HEROKU_LOG_LINES_TO_SHOW = 25 -const DELAY_FOR_PREBOOT_SWAP = 135000 // 2:15 - -// Allow for a few 404 (Not Found), 429 (Too Many Requests), etc. responses from -// the semi-unreliable Heroku API when we're polling for status updates -const ALLOWED_MISSING_RESPONSE_COUNT = - parseInt(process.env.ALLOWED_POLLING_FAILURES_PER_PHASE, 10) || 10 -const ALLOWABLE_ERROR_CODES = [404, 429, 500, 503] - -export default async function deployToProduction({ - octokit, - includeDelayForPreboot = true, - // These parameters will only be set by Actions - sourceBlobUrl = null, - runId = null, -}) { - // Start a timer so we can report how long the deployment takes - const startTime = Date.now() - const [owner, repo, branch] = ['github', 'docs-internal', 'main'] - - let sha - try { - const { - data: { sha: latestSha }, - } = await octokit.repos.getCommit({ - owner, - repo, - ref: branch, - }) - sha = latestSha - - if (!sha) { - throw new Error('Latest commit SHA could not be found') - } - } catch (error) { - console.error(`Error: ${error}`) - console.log(`🛑 There was an error getting latest commit.`) - process.exit(1) - } - - // Put together application configuration variables - const isPrebuilt = !!sourceBlobUrl - const { DOCUBOT_REPO_PAT } = process.env - const appConfigVars = { - // Track the git branch - GIT_BRANCH: branch, - // If prebuilt: prevent the Heroku Node.js buildpack from installing devDependencies - NPM_CONFIG_PRODUCTION: isPrebuilt.toString(), - // If prebuilt: prevent the Heroku Node.js buildpack from using `npm ci` as it would - // delete all of the vendored "node_modules/" directory. - USE_NPM_INSTALL: isPrebuilt.toString(), - // If not prebuilt, include the PAT required for cloning the `docs-early-access` repo. - // Otherwise, set it to `null` to unset it from the environment for security. - DOCUBOT_REPO_PAT: (!isPrebuilt && DOCUBOT_REPO_PAT) || null, - } - - const workflowRunLog = runId ? `https://github.com/${owner}/${repo}/actions/runs/${runId}` : null - let deploymentId = null - let logUrl = workflowRunLog - - const appName = process.env.HEROKU_PRODUCTION_APP_NAME - const environment = 'production' - const homepageUrl = 'https://docs.github.com/' - - try { - const title = `branch '${branch}' at commit '${sha}' in the '${environment}' environment` - - console.log(`About to deploy ${title}...`) - - // Kick off a pending GitHub Deployment right away, so the PR author - // will have instant feedback that their work is being deployed. - const { data: deployment } = await octokit.repos.createDeployment({ - owner, - repo, - description: `Deploying ${title}`, - ref: sha, - - // In the GitHub API, there can only be one active deployment per environment. - environment, - - // The status contexts to verify against commit status checks. If you omit - // this parameter, GitHub verifies all unique contexts before creating a - // deployment. To bypass checking entirely, pass an empty array. Defaults - // to all unique contexts. - required_contexts: [], - - // Do not try to merge the base branch into the feature branch - auto_merge: false, - }) - console.log('GitHub Deployment created', deployment) - - // Store this ID for later updating - deploymentId = deployment.id - - // Set some output variables for workflow steps that run after this script - if (process.env.GITHUB_ACTIONS) { - setOutput('deploymentId', deploymentId) - setOutput('logUrl', logUrl) - } - - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deploymentId, - state: 'in_progress', - description: 'Deploying the app...', - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - console.log('🚀 Deployment status: in_progress - Preparing to deploy the app...') - - // Time to talk to Heroku... - const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) - let build = null - - if (!sourceBlobUrl) { - try { - sourceBlobUrl = await getTarballUrl({ - octokit, - owner, - repo, - sha, - }) - } catch (error) { - throw new Error(`Failed to generate source blob URL. Error: ${error}`) - } - } - - console.log('Updating Heroku app configuration variables...') - - // Reconfigure environment variables - // https://devcenter.heroku.com/articles/platform-api-reference#config-vars-update - try { - await heroku.patch(`/apps/${appName}/config-vars`, { - body: appConfigVars, - }) - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error(`Failed to update Heroku app configuration variables. Error: ${error}`) - } - - console.log('Reconfigured') - console.log('Building Heroku app...') - - try { - build = await heroku.post(`/apps/${appName}/builds`, { - body: { - source_blob: { - url: sourceBlobUrl, - }, - }, - }) - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error(`Failed to create Heroku build. Error: ${error}`) - } - - console.log('Heroku build created', build) - - const buildStartTime = Date.now() // Close enough... - const buildId = build.id - logUrl = build.output_stream_url - - console.log('🚀 Deployment status: in_progress - Building a new Heroku slug...') - - // Poll until the Build's status changes from "pending" to "succeeded" or "failed". - let buildAcceptableErrorCount = 0 - while (!build || !build.release || !build.release.id) { - await sleep(SLEEP_INTERVAL) - try { - build = await heroku.get(`/apps/${appName}/builds/${buildId}`) - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - buildAcceptableErrorCount += 1 - if (buildAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${buildAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to get build status. Error: ${error}`) - } - - if (build && build.status === 'failed') { - throw new Error( - `Failed to build after ${Math.round( - (Date.now() - buildStartTime) / 1000 - )} seconds. See Heroku logs for more information:\n${logUrl}` - ) - } - - console.log( - `Heroku build status: ${(build || {}).status} (after ${Math.round( - (Date.now() - buildStartTime) / 1000 - )} seconds)` - ) - } - - console.log( - `Finished Heroku build after ${Math.round((Date.now() - buildStartTime) / 1000)} seconds.`, - build - ) - console.log('Heroku release detected', build.release) - - const releaseStartTime = Date.now() // Close enough... - const releaseId = build.release.id - let release = null - - // Poll until the associated Release's status changes from "pending" to "succeeded" or "failed". - let releaseAcceptableErrorCount = 0 - while (!release || release.status === 'pending') { - await sleep(SLEEP_INTERVAL) - try { - const result = await heroku.get(`/apps/${appName}/releases/${releaseId}`) - - // Update the deployment status but only on the first retrieval - if (!release) { - logUrl = result.output_stream_url - - console.log('Heroku Release created', result) - - console.log('🚀 Deployment status: in_progress - Releasing the built Heroku slug...') - } - - release = result - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - releaseAcceptableErrorCount += 1 - if (releaseAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${releaseAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to get release status. Error: ${error}`) - } - - if (release && release.status === 'failed') { - throw new Error( - `Failed to release after ${Math.round( - (Date.now() - releaseStartTime) / 1000 - )} seconds. See Heroku logs for more information:\n${logUrl}` - ) - } - - console.log( - `Release status: ${(release || {}).status} (after ${Math.round( - (Date.now() - releaseStartTime) / 1000 - )} seconds)` - ) - } - - console.log( - `Finished Heroku release after ${Math.round( - (Date.now() - releaseStartTime) / 1000 - )} seconds.`, - release - ) - - // Monitor dyno state for this release to ensure it reaches "up" rather than crashing. - // This will help us catch issues with faulty startup code and/or the package manifest. - const dynoBootStartTime = Date.now() - console.log('Checking Heroku dynos...') - logUrl = workflowRunLog - - console.log('🚀 Deployment status: in_progress - Monitoring the Heroku dyno start-up...') - - // Keep checking while there are still dynos in non-terminal states - let newDynos = [] - let dynoAcceptableErrorCount = 0 - while (newDynos.length === 0 || newDynos.some((dyno) => dyno.state === 'starting')) { - await sleep(SLEEP_INTERVAL) - try { - const dynoList = await heroku.get(`/apps/${appName}/dynos`) - const dynosForThisRelease = dynoList.filter((dyno) => dyno.release.id === releaseId) - - // To track them afterward - newDynos = dynosForThisRelease - - console.log( - `Dyno states: ${JSON.stringify(newDynos.map((dyno) => dyno.state))} (after ${Math.round( - (Date.now() - dynoBootStartTime) / 1000 - )} seconds)` - ) - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - dynoAcceptableErrorCount += 1 - if (dynoAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${dynoAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to find dynos for this release. Error: ${error}`) - } - } - - const crashedDynos = newDynos.filter((dyno) => ['crashed', 'restarting'].includes(dyno.state)) - const runningDynos = newDynos.filter((dyno) => dyno.state === 'up') - - // If any dynos crashed on start-up, fail the deployment - if (crashedDynos.length > 0) { - const errorMessage = `At least ${crashedDynos.length} Heroku dyno(s) crashed on start-up!` - - console.error(errorMessage) - - // Attempt to dump some of the Heroku log here for debugging - try { - const logSession = await heroku.post(`/apps/${appName}/log-sessions`, { - body: { - dyno: crashedDynos[0].name, - lines: HEROKU_LOG_LINES_TO_SHOW, - tail: false, - }, - }) - - logUrl = logSession.logplex_url - - const logText = await got(logUrl).text() - console.error( - `Here are the last ${HEROKU_LOG_LINES_TO_SHOW} lines of the Heroku log:\n\n${logText}` - ) - } catch (error) { - announceIfHerokuIsDown(error) - // Don't fail because of this error - console.error(`Failed to retrieve the Heroku logs for the crashed dynos. Error: ${error}`) - } - - throw new Error(errorMessage) - } - - console.log( - `At least ${runningDynos.length} Heroku dyno(s) are ready after ${Math.round( - (Date.now() - dynoBootStartTime) / 1000 - )} seconds.` - ) - - // IMPORTANT: - // If Heroku Preboot is enabled, then there is an additional delay of at - // least 2 minutes before the new dynos are swapped into active serving. - // If we move off Heroku in the future, this should be revisited and - // updated/removed as relevant to align with the new hosting platform. - if (includeDelayForPreboot) { - console.log(`Waiting for Heroku Preboot to swap dynos (${DELAY_FOR_PREBOOT_SWAP} ms)...`) - await sleep(DELAY_FOR_PREBOOT_SWAP) - - // TODO: - // Is there a faster alternative than this arbitrary delay? For example, - // is there some Heroku API we can query to see when this release is - // considered to be the live one, or when the old dynos are shut down? - } else { - console.warn( - '⚠️ Bypassing the wait for Heroku Preboot....\nPlease understand that your changes will not be visible for at least another 2 minutes!' - ) - } - - // Report success! - const successMessage = `Deployment succeeded after ${Math.round( - (Date.now() - startTime) / 1000 - )} seconds.` - console.log(successMessage) - - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deploymentId, - state: 'success', - description: successMessage, - ...(logUrl && { log_url: logUrl }), - environment_url: homepageUrl, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - - console.log(`🚀 Deployment status: success - ${successMessage}`) - console.log(`Visit the newly deployed app at: ${homepageUrl}`) - } catch (error) { - // Report failure! - const failureMessage = `Deployment failed after ${Math.round( - (Date.now() - startTime) / 1000 - )} seconds. See logs for more information.` - console.error(failureMessage) - - try { - if (deploymentId) { - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deploymentId, - state: 'error', - description: failureMessage, - ...(logUrl && { log_url: logUrl }), - environment_url: homepageUrl, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - - console.log( - `🚀 Deployment status: error - ${failureMessage}` + (logUrl ? ` Logs: ${logUrl}` : '') - ) - } - } catch (error) { - console.error(`Failed to finalize GitHub Deployment Status as a failure. Error: ${error}`) - } - - // Re-throw the error to bubble up - throw error - } -} - -async function getTarballUrl({ octokit, owner, repo, sha }) { - // Get a URL for the tarballed source code bundle - const { - headers: { location: tarballUrl }, - } = await octokit.repos.downloadTarballArchive({ - owner, - repo, - ref: sha, - // Override the underlying `node-fetch` module's `redirect` option - // configuration to prevent automatically following redirects. - request: { - redirect: 'manual', - }, - }) - return tarballUrl -} - -function isAllowableHerokuError(error) { - return error && ALLOWABLE_ERROR_CODES.includes(error.statusCode) -} - -function announceIfHerokuIsDown(error) { - if (error && error.statusCode === 503) { - console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/') - } -} diff --git a/script/deployment/deploy-to-staging.js b/script/deployment/deploy-to-staging.js deleted file mode 100644 index 5e3df9a09b..0000000000 --- a/script/deployment/deploy-to-staging.js +++ /dev/null @@ -1,680 +0,0 @@ -#!/usr/bin/env node -import got from 'got' -import Heroku from 'heroku-client' -import { setOutput } from '@actions/core' -import createStagingAppName from './create-staging-app-name.js' - -// Equivalent of the 'await-sleep' module without the install -const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms)) - -const SLEEP_INTERVAL = 5000 -const HEROKU_LOG_LINES_TO_SHOW = 25 - -// Allow for a few 404 (Not Found), 429 (Too Many Requests), etc. responses from -// the semi-unreliable Heroku API when we're polling for status updates -const ALLOWED_MISSING_RESPONSE_COUNT = - parseInt(process.env.ALLOWED_POLLING_FAILURES_PER_PHASE, 10) || 10 -const ALLOWABLE_ERROR_CODES = [404, 429, 500, 503] - -export default async function deployToStaging({ - octokit, - pullRequest, - forceRebuild = false, - // These parameters will only be set by Actions - sourceBlobUrl = null, - runId = null, -}) { - // Start a timer so we can report how long the deployment takes - const startTime = Date.now() - - // Extract some important properties from the PR - const { - number: pullNumber, - base: { - repo: { - name: repo, - owner: { login: owner }, - }, - }, - state, - head: { ref: branch, sha }, - user: author, - } = pullRequest - - // Verify the PR is still open - if (state !== 'open') { - throw new Error(`This pull request is not open. State is: '${state}'`) - } - - // Put together application configuration variables - const isPrivateRepo = owner === 'github' && repo === 'docs-internal' - const isPrebuilt = !!sourceBlobUrl - const { DOCUBOT_REPO_PAT, HYDRO_ENDPOINT, HYDRO_SECRET } = process.env - const appConfigVars = { - // Track the git branch - GIT_BRANCH: branch, - // If prebuilt: prevent the Heroku Node.js buildpack from installing devDependencies - NPM_CONFIG_PRODUCTION: isPrebuilt.toString(), - // If prebuilt: prevent the Heroku Node.js buildpack from using `npm ci` as it would - // delete all of the vendored "node_modules/" directory. - USE_NPM_INSTALL: isPrebuilt.toString(), - // IMPORTANT: This secret should only be set in the private repo! - // If not prebuilt, include the PAT required for cloning the `docs-early-access` repo. - // Otherwise, set it to `null` to unset it from the environment for security. - DOCUBOT_REPO_PAT: (isPrivateRepo && !isPrebuilt && DOCUBOT_REPO_PAT) || null, - // IMPORTANT: These secrets should only be set in the private repo! - // These are required for Hydro event tracking - ...(isPrivateRepo && HYDRO_ENDPOINT && HYDRO_SECRET && { HYDRO_ENDPOINT, HYDRO_SECRET }), - } - - const workflowRunLog = runId ? `https://github.com/${owner}/${repo}/actions/runs/${runId}` : null - let deploymentId = null - let logUrl = workflowRunLog - let appIsNewlyCreated = false - - const appName = createStagingAppName({ repo, pullNumber, branch }) - const environment = appName - const homepageUrl = `https://${appName}.herokuapp.com/` - - try { - const title = `branch '${branch}' at commit '${sha}' in the '${environment}' staging environment` - - console.log(`About to deploy ${title}...`) - - // Kick off a pending GitHub Deployment right away, so the PR author - // will have instant feedback that their work is being deployed. - const { data: deployment } = await octokit.repos.createDeployment({ - owner, - repo, - - description: `Deploying ${title}`, - - // Use a commit SHA instead of a branch name as the ref for more precise - // feedback, and also because the branch may have already been deleted. - ref: sha, - - // In the GitHub API, there can only be one active deployment per environment. - // For our many staging apps, we must use the unique appName as the environment. - environment, - - // The status contexts to verify against commit status checks. If you omit - // this parameter, GitHub verifies all unique contexts before creating a - // deployment. To bypass checking entirely, pass an empty array. Defaults - // to all unique contexts. - required_contexts: [], - - // Do not try to merge the base branch into the feature branch - auto_merge: false, - }) - console.log('GitHub Deployment created', deployment) - - // Store this ID for later updating - deploymentId = deployment.id - - // Set some output variables for workflow steps that run after this script - if (process.env.GITHUB_ACTIONS) { - setOutput('deploymentId', deploymentId) - setOutput('logUrl', logUrl) - } - - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deploymentId, - state: 'in_progress', - description: 'Deploying the app...', - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - console.log('🚀 Deployment status: in_progress - Preparing to deploy the app...') - - // Time to talk to Heroku... - const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) - let appSetup = null - let build = null - - // Is there already a Heroku App for this PR? - let appExists = true - try { - await heroku.get(`/apps/${appName}`) - } catch (error) { - announceIfHerokuIsDown(error) - appExists = false - } - - // If there is an existing app but we want to forcibly rebuild, delete the app first - if (appExists && forceRebuild) { - console.log('🚀 Deployment status: in_progress - Destroying existing Heroku app...') - - try { - await heroku.delete(`/apps/${appName}`) - appExists = false - - console.log(`Heroku app '${appName}' deleted for forced rebuild`) - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error( - `Failed to delete Heroku app '${appName}' for forced rebuild. Error: ${error}` - ) - } - } - - if (!sourceBlobUrl) { - try { - sourceBlobUrl = await getTarballUrl({ - octokit, - owner, - repo, - sha, - }) - } catch (error) { - throw new Error(`Failed to generate source blob URL. Error: ${error}`) - } - } - - // If an app does not exist, create one! - // This action will also trigger a build as a by-product. - if (!appExists) { - appIsNewlyCreated = true - - console.log(`Heroku app '${appName}' does not exist. Creating a new AppSetup...`) - - console.log('🚀 Deployment status: in_progress - Creating a new Heroku app...') - - const appSetupStartTime = Date.now() - try { - appSetup = await heroku.post('/app-setups', { - body: { - app: { - name: appName, - }, - source_blob: { - url: sourceBlobUrl, - }, - - // Pass some environment variables to staging apps via Heroku - // config variables. - overrides: { - // AppSetup API cannot handle `null` values for config vars - env: removeEmptyProperties(appConfigVars), - }, - }, - }) - console.log('Heroku AppSetup created', appSetup) - - // This probably will not be available yet - build = appSetup.build - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error(`Failed to create Heroku app '${appName}'. Error: ${error}`) - } - - // Add PR author (if staff) as a collaborator on the new staging app - try { - if (author.site_admin === true) { - await heroku.post(`/apps/${appName}/collaborators`, { - body: { - user: `${author.login}@github.com`, - // We don't want an email invitation for every new staging app - silent: true, - }, - }) - console.log(`Added PR author @${author.login} as a Heroku app collaborator`) - } - } catch (error) { - announceIfHerokuIsDown(error) - // It's fine if this fails, it shouldn't block the app from deploying! - console.warn( - `Warning: failed to add PR author as a Heroku app collaborator. Error: ${error}` - ) - } - - // A new Build is created as a by-product of creating an AppSetup. - // Poll until there is a Build object attached to the AppSetup. - let setupAcceptableErrorCount = 0 - while (!appSetup || !build || !build.id) { - await sleep(SLEEP_INTERVAL) - try { - appSetup = await heroku.get(`/app-setups/${appSetup.id}`) - build = appSetup.build - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - setupAcceptableErrorCount += 1 - if (setupAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${setupAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to get AppSetup status. Error: ${error}`) - } - - if (appSetup && appSetup.status === 'failed') { - const manifestErrors = appSetup.manifest_errors || [] - const hasManifestErrors = Array.isArray(manifestErrors) && manifestErrors.length > 0 - const manifestErrorMessage = hasManifestErrors - ? `\nManifest errors:\n - ${manifestErrors.join('\n - ')}` - : '' - throw new Error( - `Failed to setup app after ${Math.round( - (Date.now() - appSetupStartTime) / 1000 - )} seconds. -Reason: ${appSetup.failure_message}${manifestErrorMessage} -See Heroku logs for more information:\n${logUrl}` - ) - } - - console.log( - `AppSetup status: ${appSetup.status} (after ${Math.round( - (Date.now() - appSetupStartTime) / 1000 - )} seconds)` - ) - } - - console.log('Heroku AppSetup finished', appSetup) - console.log('Heroku build detected', build) - } else { - // If the app does exist, just manually trigger a new build - console.log(`Heroku app '${appName}' already exists.`) - - console.log('Updating Heroku app configuration variables...') - - // Reconfigure environment variables - // https://devcenter.heroku.com/articles/platform-api-reference#config-vars-update - try { - await heroku.patch(`/apps/${appName}/config-vars`, { - body: appConfigVars, - }) - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error(`Failed to update Heroku app configuration variables. Error: ${error}`) - } - - console.log('Reconfigured') - console.log('Building Heroku app...') - - try { - build = await heroku.post(`/apps/${appName}/builds`, { - body: { - source_blob: { - url: sourceBlobUrl, - }, - }, - }) - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error(`Failed to create Heroku build. Error: ${error}`) - } - - console.log('Heroku build created', build) - } - - const buildStartTime = Date.now() // Close enough... - const buildId = build.id - logUrl = build.output_stream_url - - console.log('🚀 Deployment status: in_progress - Building a new Heroku slug...') - - // Poll until the Build's status changes from "pending" to "succeeded" or "failed". - let buildAcceptableErrorCount = 0 - while (!build || !build.release || !build.release.id) { - await sleep(SLEEP_INTERVAL) - try { - build = await heroku.get(`/apps/${appName}/builds/${buildId}`) - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - buildAcceptableErrorCount += 1 - if (buildAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${buildAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to get build status. Error: ${error}`) - } - - if (build && build.status === 'failed') { - throw new Error( - `Failed to build after ${Math.round( - (Date.now() - buildStartTime) / 1000 - )} seconds. See Heroku logs for more information:\n${logUrl}` - ) - } - - console.log( - `Heroku build status: ${(build || {}).status} (after ${Math.round( - (Date.now() - buildStartTime) / 1000 - )} seconds)` - ) - } - - console.log( - `Finished Heroku build after ${Math.round((Date.now() - buildStartTime) / 1000)} seconds.`, - build - ) - console.log('Heroku release detected', build.release) - - const releaseStartTime = Date.now() // Close enough... - let releaseId = build.release.id - let release = null - - // Poll until the associated Release's status changes from "pending" to "succeeded" or "failed". - let releaseAcceptableErrorCount = 0 - while (!release || release.status === 'pending') { - await sleep(SLEEP_INTERVAL) - try { - const result = await heroku.get(`/apps/${appName}/releases/${releaseId}`) - - // Update the deployment status but only on the first retrieval - if (!release) { - logUrl = result.output_stream_url - - console.log('Heroku Release created', result) - - console.log('🚀 Deployment status: in_progress - Releasing the built Heroku slug...') - } - - release = result - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - releaseAcceptableErrorCount += 1 - if (releaseAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${releaseAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to get release status. Error: ${error}`) - } - - if (release && release.status === 'failed') { - throw new Error( - `Failed to release after ${Math.round( - (Date.now() - releaseStartTime) / 1000 - )} seconds. See Heroku logs for more information:\n${logUrl}` - ) - } - - console.log( - `Release status: ${(release || {}).status} (after ${Math.round( - (Date.now() - releaseStartTime) / 1000 - )} seconds)` - ) - } - - console.log( - `Finished Heroku release after ${Math.round( - (Date.now() - releaseStartTime) / 1000 - )} seconds.`, - release - ) - - // Monitor dyno state for this release to ensure it reaches "up" rather than crashing. - // This will help us catch issues with faulty startup code and/or the package manifest. - const dynoBootStartTime = Date.now() - console.log('Checking Heroku dynos...') - logUrl = workflowRunLog - - console.log('🚀 Deployment status: in_progress - Monitoring the Heroku dyno start-up...') - - // Keep checking while there are still dynos in non-terminal states - let newDynos = [] - let dynoAcceptableErrorCount = 0 - while (newDynos.length === 0 || newDynos.some((dyno) => dyno.state === 'starting')) { - await sleep(SLEEP_INTERVAL) - try { - const dynoList = await heroku.get(`/apps/${appName}/dynos`) - const dynosForThisRelease = dynoList.filter((dyno) => dyno.release.id === releaseId) - - // To track them afterward - newDynos = dynosForThisRelease - - // Dynos for this release OR a newer release - const relevantDynos = dynoList.filter((dyno) => dyno.release.version >= release.version) - - // If this Heroku app was just newly created, often a secondary release - // is requested to enable automatically managed SSL certificates. The - // release description will read: - // "Enable allow-multiple-sni-endpoints feature" - // - // If that is the case, we need to update to monitor that secondary - // release instead. - if (relevantDynos.length > 0 && dynosForThisRelease.length === 0) { - // If the app is NOT newly created, fail fast! - if (!appIsNewlyCreated) { - throw new Error('The dynos for this release disappeared unexpectedly') - } - - // Check for the secondary release - let nextRelease = null - try { - nextRelease = await heroku.get(`/apps/${appName}/releases/${release.version + 1}`) - } catch (error) { - announceIfHerokuIsDown(error) - throw new Error( - `Could not find a secondary release to explain the disappearing dynos. Error: ${error}` - ) - } - - if (nextRelease) { - if (nextRelease.description === 'Enable allow-multiple-sni-endpoints feature') { - // Track dynos for the next release instead - release = nextRelease - releaseId = nextRelease.id - - console.warn('Switching to monitor secondary release...') - - // Allow the loop to repeat to fetch the dynos for the secondary release - } else { - // Otherwise, assume another release replaced this one but it - // PROBABLY would've succeeded...? - newDynos.forEach((dyno) => { - dyno.state = 'up' - }) - } - } - // else just keep monitoring and hope for the best - } - - console.log( - `Dyno states: ${JSON.stringify(newDynos.map((dyno) => dyno.state))} (after ${Math.round( - (Date.now() - dynoBootStartTime) / 1000 - )} seconds)` - ) - } catch (error) { - // Allow for a few bad responses from the Heroku API - if (isAllowableHerokuError(error)) { - dynoAcceptableErrorCount += 1 - if (dynoAcceptableErrorCount <= ALLOWED_MISSING_RESPONSE_COUNT) { - console.warn( - `Ignoring allowable Heroku error #${dynoAcceptableErrorCount}: ${error.statusCode}` - ) - continue - } - } - announceIfHerokuIsDown(error) - throw new Error(`Failed to find dynos for this release. Error: ${error}`) - } - } - - const crashedDynos = newDynos.filter((dyno) => ['crashed', 'restarting'].includes(dyno.state)) - const runningDynos = newDynos.filter((dyno) => dyno.state === 'up') - - // If any dynos crashed on start-up, fail the deployment - if (crashedDynos.length > 0) { - const errorMessage = `At least ${crashedDynos.length} Heroku dyno(s) crashed on start-up!` - - console.error(errorMessage) - - // Attempt to dump some of the Heroku log here for debugging - try { - const logSession = await heroku.post(`/apps/${appName}/log-sessions`, { - body: { - dyno: crashedDynos[0].name, - lines: HEROKU_LOG_LINES_TO_SHOW, - tail: false, - }, - }) - - logUrl = logSession.logplex_url - - const logText = await got(logUrl).text() - console.error( - `Here are the last ${HEROKU_LOG_LINES_TO_SHOW} lines of the Heroku log:\n\n${logText}` - ) - } catch (error) { - announceIfHerokuIsDown(error) - // Don't fail because of this error - console.error(`Failed to retrieve the Heroku logs for the crashed dynos. Error: ${error}`) - } - - throw new Error(errorMessage) - } - - console.log( - `At least ${runningDynos.length} Heroku dyno(s) are ready after ${Math.round( - (Date.now() - dynoBootStartTime) / 1000 - )} seconds.` - ) - - // Send a series of requests to trigger the server warmup routines - console.log('🚀 Deployment status: in_progress - Triggering server warmup routines...') - - const warmupStartTime = Date.now() - console.log(`Making warmup requests to: ${homepageUrl}`) - try { - await got(homepageUrl, { - timeout: 10000, // Maximum 10 second timeout per request - retry: { - limit: 7, // About 2 minutes 7 seconds of delay, plus active request time for 8 requests - statusCodes: [404, 421].concat(got.defaults.options.retry.statusCodes), // prepend extras - }, - hooks: { - beforeRetry: [ - (options, error = {}, retryCount = '?') => { - const statusCode = error.statusCode || (error.response || {}).statusCode || -1 - console.log( - `Retrying after warmup request attempt #${retryCount} (${statusCode}) after ${Math.round( - (Date.now() - warmupStartTime) / 1000 - )} seconds...` - ) - }, - ], - }, - }) - console.log( - `Warmup requests passed after ${Math.round((Date.now() - warmupStartTime) / 1000)} seconds` - ) - } catch (error) { - throw new Error( - `Warmup requests failed after ${Math.round( - (Date.now() - warmupStartTime) / 1000 - )} seconds. Error: ${error}` - ) - } - - // Report success! - const successMessage = `Deployment succeeded after ${Math.round( - (Date.now() - startTime) / 1000 - )} seconds.` - console.log(successMessage) - - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deploymentId, - state: 'success', - description: successMessage, - ...(logUrl && { log_url: logUrl }), - environment_url: homepageUrl, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - - console.log(`🚀 Deployment status: success - ${successMessage}`) - console.log(`Visit the newly deployed app at: ${homepageUrl}`) - } catch (error) { - // Report failure! - const failureMessage = `Deployment failed after ${Math.round( - (Date.now() - startTime) / 1000 - )} seconds. See logs for more information.` - console.error(failureMessage) - - try { - if (deploymentId) { - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deploymentId, - state: 'error', - description: failureMessage, - ...(logUrl && { log_url: logUrl }), - environment_url: homepageUrl, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - - console.log( - `🚀 Deployment status: error - ${failureMessage}` + (logUrl ? ` Logs: ${logUrl}` : '') - ) - } - } catch (error) { - console.error(`Failed to finalize GitHub DeploymentStatus as a failure. Error: ${error}`) - } - - // Re-throw the error to bubble up - throw error - } -} - -async function getTarballUrl({ octokit, owner, repo, sha }) { - // Get a URL for the tarballed source code bundle - const { - headers: { location: tarballUrl }, - } = await octokit.repos.downloadTarballArchive({ - owner, - repo, - ref: sha, - // Override the underlying `node-fetch` module's `redirect` option - // configuration to prevent automatically following redirects. - request: { - redirect: 'manual', - }, - }) - return tarballUrl -} - -function isAllowableHerokuError(error) { - return error && ALLOWABLE_ERROR_CODES.includes(error.statusCode) -} - -function announceIfHerokuIsDown(error) { - if (error && error.statusCode === 503) { - console.error('💀 Heroku may be down! Please check its Status page: https://status.heroku.com/') - } -} - -function removeEmptyProperties(obj) { - return Object.fromEntries(Object.entries(obj).filter(([key, val]) => val != null)) -} diff --git a/script/deployment/parse-pr-url.js b/script/deployment/parse-pr-url.js deleted file mode 100644 index af7f876dff..0000000000 --- a/script/deployment/parse-pr-url.js +++ /dev/null @@ -1,21 +0,0 @@ -#!/usr/bin/env node -const USERNAME_FORMAT = '([A-Za-z0-9-]+)' -const REPO_NAME_FORMAT = '([A-Za-z0-9._-]+)' -const PR_NUMBER_FORMAT = '(\\d+)' - -const ALLOWED_PR_URL_FORMAT = new RegExp( - '^' + - '[\'"]?' + - `https://github\\.com/${USERNAME_FORMAT}/${REPO_NAME_FORMAT}/pull/${PR_NUMBER_FORMAT}` + - '[\'"]?' + - '$' -) - -export default function parsePullRequestUrl(prUrl) { - const [, /* fullMatch */ owner, repo, pr] = (prUrl || '').match(ALLOWED_PR_URL_FORMAT) || [] - return { - owner, - repo, - pullNumber: parseInt(pr, 10) || undefined, - } -} diff --git a/script/early-access/clone-for-build.js b/script/early-access/clone-for-build.js deleted file mode 100755 index 5a2be19625..0000000000 --- a/script/early-access/clone-for-build.js +++ /dev/null @@ -1,140 +0,0 @@ -#!/usr/bin/env node - -// [start-readme] -// -// This script is run as a postbuild script during staging and deployments on Heroku. It clones a branch -// in the early-access repo that matches the current branch in the docs repo; if one can't be found, it -// clones the `main` branch. -// -// [end-readme] - -import dotenv from 'dotenv' -import { execSync } from 'child_process' -import rimraf from 'rimraf' -import fs from 'fs' -import path from 'path' -import os from 'os' - -dotenv.config() -const { - DOCUBOT_REPO_PAT, - HEROKU_PRODUCTION_APP, - GIT_BRANCH, // Set by Actions and/or the deployer with the name of the docs-internal branch -} = process.env - -// Exit if PAT is not found -if (!DOCUBOT_REPO_PAT) { - console.log('Skipping early access, not authorized') - process.exit(0) -} - -const EA_PRODUCTION_BRANCH = 'main' - -// If a branch name is not provided in the environment, attempt to get -// the local branch name; or default to 'main' -let currentBranch = (GIT_BRANCH || '').replace(/^refs\/heads\//, '') -if (!currentBranch) { - try { - currentBranch = execSync('git branch --show-current').toString() - } catch (err) { - // Ignore but log - console.warn('Error checking for local branch:', err.message) - } -} -if (!currentBranch) { - currentBranch = EA_PRODUCTION_BRANCH -} - -// Early Access details -const earlyAccessOwner = 'github' -const earlyAccessRepoName = 'docs-early-access' -const earlyAccessDirName = 'early-access' -const earlyAccessFullRepo = `https://${DOCUBOT_REPO_PAT}@github.com/${earlyAccessOwner}/${earlyAccessRepoName}` - -// On our Azure self-hosted runners, os.tmpdir() doesn't work reliably. On Heroku, os.homedir doesn't work reliably. -const earlyAccessCloningParentDir = process.env.CI ? os.homedir() : os.tmpdir() -const earlyAccessCloningDir = path.join(earlyAccessCloningParentDir, earlyAccessRepoName) - -const destinationDirNames = ['content', 'data', 'assets/images'] -const destinationDirsMap = destinationDirNames.reduce((map, dirName) => { - map[dirName] = path.join(process.cwd(), dirName, earlyAccessDirName) - return map -}, {}) - -// Production vs. staging environment -// TODO test that this works as expected -const environment = HEROKU_PRODUCTION_APP ? 'production' : 'staging' - -// Early access branch to clone -let earlyAccessBranch = HEROKU_PRODUCTION_APP ? EA_PRODUCTION_BRANCH : currentBranch - -// Confirm that the branch exists in the remote -let branchExists = execSync( - `git ls-remote --heads ${earlyAccessFullRepo} ${earlyAccessBranch}` -).toString() - -// If the branch did NOT exist, try checking for the default branch instead -if (!branchExists && earlyAccessBranch !== EA_PRODUCTION_BRANCH) { - console.warn( - `The branch '${earlyAccessBranch}' was not found in ${earlyAccessOwner}/${earlyAccessRepoName}!` - ) - console.warn(`Attempting the default branch ${EA_PRODUCTION_BRANCH} instead...`) - - earlyAccessBranch = EA_PRODUCTION_BRANCH - branchExists = execSync( - `git ls-remote --heads ${earlyAccessFullRepo} ${earlyAccessBranch}` - ).toString() -} - -// If no suitable branch was found, bail out now -if (!branchExists) { - console.error( - `The branch '${earlyAccessBranch}' was not found in ${earlyAccessOwner}/${earlyAccessRepoName}!` - ) - console.error('Exiting!') - process.exit(1) -} - -// Remove any previously cloned copies of the early access repo -rimraf.sync(earlyAccessCloningDir) - -// Clone the repo -console.log(`Setting up: ${earlyAccessCloningDir}`) -execSync( - `git clone --single-branch --branch ${earlyAccessBranch} ${earlyAccessFullRepo} ${earlyAccessRepoName}`, - { - cwd: earlyAccessCloningParentDir, - } -) -console.log(`Using early-access ${environment} branch: '${earlyAccessBranch}'`) - -// Remove all existing early access directories from this repo -destinationDirNames.forEach((key) => rimraf.sync(destinationDirsMap[key])) - -// Move the latest early access source directories into this repo -destinationDirNames.forEach((dirName) => { - const sourceDir = path.join(earlyAccessCloningDir, dirName) - const destDir = destinationDirsMap[dirName] - - // If the source directory doesn't exist, skip it - if (!fs.existsSync(sourceDir)) { - console.warn(`Early access directory '${dirName}' does not exist. Skipping...`) - return - } - - // Ensure the base directory exists - fs.mkdirSync(path.join(process.cwd(), dirName), { recursive: true }) - - // Move the directory from the cloned source to the destination - fs.renameSync(sourceDir, destDir) - - // Confirm the newly moved directory exist - if (fs.existsSync(destDir)) { - console.log(`Successfully moved early access directory '${dirName}' into this repo`) - } else { - throw new Error(`Failed to move early access directory '${dirName}'!`) - } -}) - -// Remove the source content again for good hygiene -rimraf.sync(earlyAccessCloningDir) diff --git a/script/ping-staging-apps.js b/script/ping-staging-apps.js deleted file mode 100755 index d919013597..0000000000 --- a/script/ping-staging-apps.js +++ /dev/null @@ -1,41 +0,0 @@ -#!/usr/bin/env node - -// [start-readme] -// -// This script finds all Heroku staging apps and pings them to make sure they're always "warmed" and responsive to requests. -// -// [end-readme] - -import dotenv from 'dotenv' -import assert from 'assert' -import got from 'got' -import { chain } from 'lodash-es' -import chalk from 'chalk' -import Heroku from 'heroku-client' - -dotenv.config() - -assert(process.env.HEROKU_API_TOKEN) - -const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) - -main() - -async function main() { - const apps = chain(await heroku.get('/apps')) - .orderBy('name') - .value() - - async function ping(app) { - // ?warmup param has no effect but makes it easier to find these requests in the logs - const url = `https://${app.name}.herokuapp.com/en?warmup` - try { - const response = await got(url) - console.log(chalk.green(url, response.statusCode)) - } catch (error) { - console.log(chalk.red(url, error.response.statusCode)) - } - } - - Promise.all(apps.map(ping)) -} diff --git a/script/remove-stale-staging-apps.js b/script/remove-stale-staging-apps.js deleted file mode 100755 index 37be1c475f..0000000000 --- a/script/remove-stale-staging-apps.js +++ /dev/null @@ -1,145 +0,0 @@ -#!/usr/bin/env node - -// [start-readme] -// -// This script removes all stale Heroku staging apps that outlasted the closure -// of their corresponding pull requests, or correspond to spammy pull requests. -// -// [end-readme] - -import dotenv from 'dotenv' -import { chain } from 'lodash-es' -import chalk from 'chalk' -import Heroku from 'heroku-client' -import getOctokit from './helpers/github.js' - -dotenv.config() - -// Check for required Heroku API token -if (!process.env.HEROKU_API_TOKEN) { - console.error( - 'Error! You must have a HEROKU_API_TOKEN environment variable for deployer-level access.' - ) - process.exit(1) -} -// Check for required GitHub PAT -if (!process.env.GITHUB_TOKEN) { - console.error('Error! You must have a GITHUB_TOKEN environment variable for repo access.') - process.exit(1) -} - -const heroku = new Heroku({ token: process.env.HEROKU_API_TOKEN }) -// This helper uses the `GITHUB_TOKEN` implicitly -const octokit = getOctokit() - -const protectedAppNames = ['help-docs'] - -main() - -async function main() { - const apps = chain(await heroku.get('/apps')) - .orderBy('name') - .value() - - const prInfoMatch = /^(?:gha-|ghd-)?(?docs(?:-internal)?)-(?\d+)--.*$/ - - const appsPlusPullIds = apps.map((app) => { - const match = prInfoMatch.exec(app.name) - const { repo, pullNumber } = (match || {}).groups || {} - - return { - app, - repo, - pullNumber: parseInt(pullNumber, 10) || null, - } - }) - - const appsWithPullIds = appsPlusPullIds.filter((appi) => appi.repo && appi.pullNumber > 0) - - const nonMatchingAppNames = appsPlusPullIds - .filter((appi) => !(appi.repo && appi.pullNumber > 0)) - .map((appi) => appi.app.name) - .filter((name) => !protectedAppNames.includes(name)) - - let staleCount = 0 - let spammyCount = 0 - for (const awpi of appsWithPullIds) { - const { isStale, isSpammy } = await assessPullRequest(awpi.repo, awpi.pullNumber) - - if (isSpammy) spammyCount++ - if (isStale) staleCount++ - - if (isSpammy || isStale) { - await deleteHerokuApp(awpi.app.name) - } - } - - const matchingCount = appsWithPullIds.length - const counts = { - total: matchingCount, - alive: matchingCount - staleCount, - stale: { - total: staleCount, - spammy: spammyCount, - closed: staleCount - spammyCount, - }, - } - console.log(`🧮 COUNTS!\n${JSON.stringify(counts, null, 2)}`) - - const nonMatchingCount = nonMatchingAppNames.length - if (nonMatchingCount > 0) { - console.log( - '⚠️ 👀', - chalk.yellow( - `Non-matching app names (${nonMatchingCount}):\n - ${nonMatchingAppNames.join('\n - ')}` - ) - ) - } -} - -function displayParams(params) { - const { owner, repo, pull_number: pullNumber } = params - return `${owner}/${repo}#${pullNumber}` -} - -async function assessPullRequest(repo, pullNumber) { - const params = { - owner: 'github', - repo: repo, - pull_number: pullNumber, - } - - let isStale = false - let isSpammy = false - try { - const { data: pullRequest } = await octokit.pulls.get(params) - - if (pullRequest && pullRequest.state === 'closed') { - isStale = true - console.debug(chalk.green(`STALE: ${displayParams(params)} is closed`)) - } - } catch (error) { - // Using a standard GitHub PAT, PRs from spammy users will respond as 404 - if (error.status === 404) { - isStale = true - isSpammy = true - console.debug(chalk.yellow(`STALE: ${displayParams(params)} is spammy or deleted`)) - } else { - console.debug(chalk.red(`ERROR: ${displayParams(params)} - ${error.message}`)) - } - } - - return { isStale, isSpammy } -} - -async function deleteHerokuApp(appName) { - try { - await heroku.delete(`/apps/${appName}`) - console.log('✅', chalk.green(`Removed stale app "${appName}"`)) - } catch (error) { - console.log( - '❌', - chalk.red(`ERROR: Failed to remove stale app "${appName}" - ${error.message}`) - ) - } -} diff --git a/script/remove-stale-staging-envs.js b/script/remove-stale-staging-envs.js deleted file mode 100755 index d10f4742fa..0000000000 --- a/script/remove-stale-staging-envs.js +++ /dev/null @@ -1,266 +0,0 @@ -#!/usr/bin/env node - -// [start-readme] -// -// This script removes all stale GitHub deployment environments that outlasted -// the closure of their corresponding pull requests, or correspond to spammy -// pull requests. -// -// [end-readme] - -import dotenv from 'dotenv' -import chalk from 'chalk' -import getOctokit from './helpers/github.js' - -dotenv.config() - -// Check for required GitHub PAT -if (!process.env.GITHUB_TOKEN) { - console.error('Error! You must have a GITHUB_TOKEN environment variable for repo access.') - process.exit(1) -} - -if (!process.env.ELEVATED_TOKEN) { - console.error( - 'Error! You must have a ELEVATED_TOKEN environment variable for removing deployment environments.' - ) - process.exit(1) -} - -if (!process.env.REPO) { - console.error('Error! You must have a REPO environment variable.') - process.exit(1) -} - -if (!process.env.RUN_ID) { - console.error('Error! You must have a RUN_ID environment variable.') - process.exit(1) -} - -// This helper uses the `GITHUB_TOKEN` implicitly -const octokit = getOctokit() - -const protectedEnvNames = ['production'] -const maxEnvironmentsToProcess = 50 - -// How long must a PR be closed without being merged to be considered stale? -const ONE_HOUR = 60 * 60 * 1000 -const prClosureStaleTime = 2 * ONE_HOUR - -main() - -async function main() { - const owner = 'github' - const [repoOwner, repo] = (process.env.REPO || '').split('/') - - if (repoOwner !== owner) { - console.error(`Error! The repository owner must be "${owner}" but was "${repoOwner}".`) - process.exit(1) - } - - const logUrl = `https://github.com/${owner}/${repo}/actions/runs/${process.env.RUN_ID}` - - const prInfoMatch = /^(?:gha-|ghd-)?(?docs(?:-internal)?)-(?\d+)--.*$/ - - let exceededLimit = false - let matchingCount = 0 - let staleCount = 0 - let spammyCount = 0 - const nonMatchingEnvNames = [] - - for await (const response of octokit.paginate.iterator(octokit.repos.getAllEnvironments, { - owner, - repo, - })) { - const { data: environments } = response - - const envsPlusPullIds = environments.map((env) => { - const match = prInfoMatch.exec(env.name) - const { repo: repoName, pullNumber } = (match || {}).groups || {} - - return { - env, - repo: repoName, - pullNumber: parseInt(pullNumber, 10) || null, - } - }) - - const envsWithPullIds = envsPlusPullIds.filter( - (eppi) => eppi.repo === repo && eppi.pullNumber > 0 - ) - matchingCount += envsWithPullIds.length - - nonMatchingEnvNames.push( - ...envsPlusPullIds - .filter((eppi) => !(eppi.repo && eppi.pullNumber > 0)) - .map((eppi) => eppi.env.name) - .filter((name) => !protectedEnvNames.includes(name)) - ) - - for (const ewpi of envsWithPullIds) { - const { isStale, isSpammy } = await assessPullRequest(ewpi.pullNumber) - - if (isSpammy) spammyCount++ - if (isStale) staleCount++ - - if (isSpammy || isStale) { - await deleteEnvironment(ewpi.env.name) - } - - if (spammyCount + staleCount >= maxEnvironmentsToProcess) { - exceededLimit = true - break - } - } - - if (exceededLimit) { - console.log( - '🛑', - chalk.bgRed(`STOP! Exceeded limit, halting after ${maxEnvironmentsToProcess}.`) - ) - break - } - } - - const counts = { - total: matchingCount, - alive: matchingCount - staleCount, - stale: { - total: staleCount, - spammy: spammyCount, - closed: staleCount - spammyCount, - }, - } - console.log(`🧮 COUNTS!\n${JSON.stringify(counts, null, 2)}`) - - const nonMatchingCount = nonMatchingEnvNames.length - if (nonMatchingCount > 0) { - console.log( - '⚠️ 👀', - chalk.yellow( - `Non-matching env names (${nonMatchingCount}):\n - ${nonMatchingEnvNames.join('\n - ')}` - ) - ) - } - - function displayParams(params) { - const { owner, repo, pull_number: pullNumber } = params - return `${owner}/${repo}#${pullNumber}` - } - - async function assessPullRequest(pullNumber) { - const params = { - owner, - repo, - pull_number: pullNumber, - } - - let isStale = false - let isSpammy = false - try { - const { data: pullRequest } = await octokit.pulls.get(params) - - if (pullRequest && pullRequest.state === 'closed') { - const isMerged = pullRequest.merged === true - const closureAge = Date.now() - Date.parse(pullRequest.closed_at) - isStale = isMerged || closureAge >= prClosureStaleTime - - if (isStale) { - console.debug(chalk.green(`STALE: ${displayParams(params)} is closed`)) - } else { - console.debug( - chalk.blue(`NOT STALE: ${displayParams(params)} is closed but not yet stale`) - ) - } - } - } catch (error) { - // Using a standard GitHub PAT, PRs from spammy users will respond as 404 - if (error.status === 404) { - isStale = true - isSpammy = true - console.debug(chalk.yellow(`STALE: ${displayParams(params)} is spammy or deleted`)) - } else { - console.debug(chalk.red(`ERROR: ${displayParams(params)} - ${error.message}`)) - } - } - - return { isStale, isSpammy } - } - - async function deleteEnvironment(envName) { - try { - let deploymentCount = 0 - - // Get all of the Deployments to signal this environment's complete deactivation - for await (const response of octokit.paginate.iterator(octokit.repos.listDeployments, { - owner, - repo, - - // In the GitHub API, there can only be one active deployment per environment. - // For our many staging apps, we must use the unique appName as the environment. - environment: envName, - })) { - const { data: deployments } = response - - // Deactivate ALL of the deployments - for (const deployment of deployments) { - // Deactivate this Deployment with an 'inactive' DeploymentStatus - await octokit.repos.createDeploymentStatus({ - owner, - repo, - deployment_id: deployment.id, - state: 'inactive', - description: 'The app was undeployed', - log_url: logUrl, - // The 'ant-man' preview is required for `state` values of 'inactive', as well as - // the use of the `log_url`, `environment_url`, and `auto_inactive` parameters. - // The 'flash' preview is required for `state` values of 'in_progress' and 'queued'. - mediaType: { - previews: ['ant-man', 'flash'], - }, - }) - - // Delete this Deployment - await octokit.repos.deleteDeployment({ - owner, - repo, - deployment_id: deployment.id, - }) - - deploymentCount++ - } - } - - // Delete this Environment - try { - await octokit.repos.deleteAnEnvironment({ - // Must use a PAT with more elevated permissions than GITHUB_TOKEN can achieve! - headers: { - authorization: `token ${process.env.ELEVATED_TOKEN}`, - }, - owner, - repo, - environment_name: envName, - }) - } catch (error) { - if (error.status !== 404) { - throw error - } - } - - console.log( - '✅', - chalk.green( - `Removed stale deployment environment "${envName}" (${deploymentCount} deployments)` - ) - ) - } catch (error) { - console.log( - '❌', - chalk.red( - `ERROR: Failed to remove stale deployment environment "${envName}" - ${error.message}` - ) - ) - } - } -} diff --git a/script/rendered-content-link-checker.mjs b/script/rendered-content-link-checker.mjs index b444b18182..dcc811fc68 100755 --- a/script/rendered-content-link-checker.mjs +++ b/script/rendered-content-link-checker.mjs @@ -16,6 +16,7 @@ import chalk from 'chalk' import shortVersions from '../middleware/contextualizers/short-versions.js' import contextualize from '../middleware/context.js' import { languageKeys } from '../lib/languages.js' +import getRedirect from '../lib/get-redirect.js' import warmServer from '../lib/warm-server.js' import renderContent from '../lib/render-content/index.js' import { deprecated } from '../lib/enterprise-server-releases.js' @@ -389,8 +390,8 @@ function checkHrefLink(href, $, redirects, pageMap, checkAnchors = false) { if (!fs.existsSync(staticFilePath)) { return { CRITICAL: `Static file not found ${staticFilePath} (${pathname})` } } - } else if (redirects[pathname]) { - return { WARNING: `Redirect to ${redirects[pathname]}` } + } else if (getRedirect(pathname, { redirects, pages: pageMap })) { + return { WARNING: `Redirect to ${getRedirect(pathname, { redirects, pages: pageMap })}` } } else if (!pageMap[pathname]) { if (deprecatedVersionPrefixesRegex.test(pathname)) { return diff --git a/script/update-internal-links.js b/script/update-internal-links.js index 0bc1b6a3d9..198b8ec0b9 100755 --- a/script/update-internal-links.js +++ b/script/update-internal-links.js @@ -28,6 +28,7 @@ import { allVersionKeys } from '../lib/all-versions.js' import frontmatter from '../lib/read-frontmatter.js' import renderContent from '../lib/render-content/index.js' import patterns from '../lib/patterns.js' +import getRedirect from '../lib/get-redirect.js' const __dirname = path.dirname(fileURLToPath(import.meta.url)) const walkFiles = (pathToWalk) => { @@ -200,10 +201,11 @@ function findPage(tryPath, pageMap, redirects) { } } - if (pageMap[redirects[tryPath]]) { + const redirect = getRedirect(tryPath, { redirects, pages: pageMap }) + if (pageMap[redirect]) { return { - title: pageMap[redirects[tryPath]].title, - path: redirects[tryPath], + title: pageMap[redirect].title, + path: redirect, } } } diff --git a/tests/content/search.js b/tests/content/search.js index e212edbbaf..50b41ebd04 100644 --- a/tests/content/search.js +++ b/tests/content/search.js @@ -60,6 +60,11 @@ describe('search middleware', () => { expect(res.statusCode).toBe(200) const results = JSON.parse(res.text) expect(Array.isArray(results)).toBeTruthy() + + // Check that it can be cached at the CDN + expect(res.headers['set-cookie']).toBeUndefined() + expect(res.headers['cache-control']).toContain('public') + expect(res.headers['cache-control']).toMatch(/max-age=\d+/) }) test('limit search', async () => { diff --git a/tests/fixtures/page-with-deprecated-enterprise-links.md b/tests/fixtures/page-with-deprecated-enterprise-links.md new file mode 100644 index 0000000000..a2dc958c7d --- /dev/null +++ b/tests/fixtures/page-with-deprecated-enterprise-links.md @@ -0,0 +1,11 @@ +--- +title: Page with deprecated enterprise links +versions: + free-pro-team: '*' + enterprise-server: '*' +--- + + +- [Version 2.22](/enterprise-server@2.22) + +- [Version 3.2](/enterprise-server@3.2) diff --git a/tests/helpers/supertest.js b/tests/helpers/supertest.js index 46c882b4b7..7623584741 100644 --- a/tests/helpers/supertest.js +++ b/tests/helpers/supertest.js @@ -6,11 +6,10 @@ import createApp from '../../lib/app.js' const app = createApp() -const helpers = {} +const requester = supertest(app) +const request = (method, route) => requester[method](route) -const request = (method, route) => supertest(app)[method](route) - -export const get = (helpers.get = async function ( +export async function get( route, opts = { followRedirects: false, followAllRedirects: false, headers: {} } ) { @@ -19,37 +18,48 @@ export const get = (helpers.get = async function ( : await request('get', route) // follow all redirects, or just follow one if (opts.followAllRedirects && [301, 302].includes(res.status)) { - res = await helpers.get(res.headers.location, opts) + res = await get(res.headers.location, opts) } else if (opts.followRedirects && [301, 302].includes(res.status)) { - res = await helpers.get(res.headers.location) + res = await get(res.headers.location) } return res -}) +} -export const head = (helpers.head = async function (route, opts = { followRedirects: false }) { +export async function head(route, opts = { followRedirects: false }) { const res = await request('head', route).redirects(opts.followRedirects ? 10 : 0) return res -}) +} -export const post = (helpers.post = (route) => request('post', route)) +export function post(route) { + return request('post', route) +} -export const getDOM = (helpers.getDOM = async function (route, headers, allow500s = false) { - const res = await helpers.get(route, { followRedirects: true, headers }) +export async function getDOM( + route, + { headers, allow500s, allow404 } = { headers: undefined, allow500s: false, allow404: false } +) { + const res = await get(route, { followRedirects: true, headers }) if (!allow500s && res.status >= 500) { throw new Error(`Server error (${res.status}) on ${route}`) } + if (!allow404 && res.status === 404) { + throw new Error(`Page not found on ${route}`) + } const $ = cheerio.load(res.text || '', { xmlMode: true }) $.res = Object.assign({}, res) return $ -}) +} // For use with the ?json query param // e.g. await getJSON('/en?json=breadcrumbs') -export const getJSON = (helpers.getJSON = async function (route) { - const res = await helpers.get(route, { followRedirects: true }) +export async function getJSON(route) { + const res = await get(route, { followRedirects: true }) if (res.status >= 500) { throw new Error(`Server error (${res.status}) on ${route}`) } + if (res.status >= 400) { + console.warn(`${res.status} on ${route} and the response might not be JSON`) + } return JSON.parse(res.text) -}) +} 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/breadcrumbs.js b/tests/rendering/breadcrumbs.js index 1f8da57935..9f1680fd9a 100644 --- a/tests/rendering/breadcrumbs.js +++ b/tests/rendering/breadcrumbs.js @@ -1,6 +1,7 @@ import { getDOM, getJSON } from '../helpers/supertest.js' import { jest } from '@jest/globals' +// TODO: Use `describeViaActionsOnly` instead. See tests/rendering/server.js const describeInternalOnly = process.env.GITHUB_REPOSITORY === 'github/docs-internal' ? describe : describe.skip // Breadcrumbs were moved to the Header and in the Menu for mobile, so there are now double the Breadcrumbs diff --git a/tests/rendering/events.js b/tests/rendering/events.js index 524b20d9e7..d06ac27196 100644 --- a/tests/rendering/events.js +++ b/tests/rendering/events.js @@ -31,6 +31,8 @@ describe('POST /events', () => { delete process.env.HYDRO_SECRET delete process.env.HYDRO_ENDPOINT csrfToken = '' + + nock.cleanAll() }) async function checkEvent(data, code) { diff --git a/tests/rendering/footer.js b/tests/rendering/footer.js index a8ae799fc0..46f5af6525 100644 --- a/tests/rendering/footer.js +++ b/tests/rendering/footer.js @@ -23,7 +23,7 @@ describe('footer', () => { }) test('leads to dotcom support on 404 pages', async () => { - const $ = await getDOM('/en/delicious-snacks/donuts.php') + const $ = await getDOM('/delicious-snacks/donuts.php', { allow404: true }) expect($('a#contact-us').attr('href')).toBe('https://support.github.com/contact') }) }) diff --git a/tests/rendering/header.js b/tests/rendering/header.js index 4f1028f342..84486b1ef8 100644 --- a/tests/rendering/header.js +++ b/tests/rendering/header.js @@ -85,54 +85,54 @@ describe('header', () => { test("renders a link to the same page in user's preferred language, if available", async () => { const headers = { 'accept-language': 'ja' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) }) test("renders a link to the same page if user's preferred language is Chinese - PRC", async () => { const headers = { 'accept-language': 'zh-CN' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) expect($('[data-testid=header-notification] a[href*="/cn"]').length).toBe(1) }) test("does not render a link when user's preferred language is Chinese - Taiwan", async () => { const headers = { 'accept-language': 'zh-TW' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification]').length).toBe(0) }) test("does not render a link when user's preferred language is English", async () => { const headers = { 'accept-language': 'en' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification]').length).toBe(0) }) test("renders a link to the same page in user's preferred language from multiple, if available", async () => { const headers = { 'accept-language': 'ja, *;q=0.9' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) }) test("renders a link to the same page in user's preferred language with weights, if available", async () => { const headers = { 'accept-language': 'ja;q=1.0, *;q=0.9' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) }) test("renders a link to the user's 2nd preferred language if 1st is not available", async () => { const headers = { 'accept-language': 'zh-TW,zh;q=0.9,ja *;q=0.8' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification][data-type=TRANSLATION]').length).toBe(1) expect($('[data-testid=header-notification] a[href*="/ja"]').length).toBe(1) }) test('renders no notices if no language preference is available', async () => { const headers = { 'accept-language': 'zh-TW,zh;q=0.9,zh-SG *;q=0.8' } - const $ = await getDOM('/en', headers) + const $ = await getDOM('/en', { headers }) expect($('[data-testid=header-notification]').length).toBe(0) }) }) diff --git a/tests/rendering/learning-tracks.js b/tests/rendering/learning-tracks.js index abe0edea64..2f9f2ce872 100644 --- a/tests/rendering/learning-tracks.js +++ b/tests/rendering/learning-tracks.js @@ -52,7 +52,7 @@ describe('navigation banner', () => { test('render navigation banner when url is a redirect to a learning track URL', async () => { const $ = await getDOM( - '/enterprise/admin/enterprise-management/enabling-automatic-update-checks?learn=upgrade_your_instance' + '/en/enterprise/admin/enterprise-management/enabling-automatic-update-checks?learn=upgrade_your_instance' ) expect($('[data-testid=learning-track-nav]')).toHaveLength(1) const $navLinks = $('[data-testid=learning-track-nav] a') diff --git a/tests/rendering/robots-txt.js b/tests/rendering/robots-txt.js index d7319d663f..c7e3871e93 100644 --- a/tests/rendering/robots-txt.js +++ b/tests/rendering/robots-txt.js @@ -35,9 +35,9 @@ describe('robots.txt', () => { }) }) - it('disallows indexing of herokuapp.com domains', async () => { + it('disallows indexing of azurecontainer.io domains', async () => { const req = { - hostname: 'docs-internal-12345--my-branch.herokuapp.com', + hostname: 'docs-internal-preview-12345-asdfz.azurecontainer.io', path: '/robots.txt', } const res = new MockExpressResponse() diff --git a/tests/rendering/server.js b/tests/rendering/server.js index c47dd24d14..a2ea23abcb 100644 --- a/tests/rendering/server.js +++ b/tests/rendering/server.js @@ -103,12 +103,6 @@ describe('server', () => { }) }) - test('uses gzip compression', async () => { - const res = await get('/en') - expect(res.headers['content-encoding']).toBe('gzip') - expect(res.headers['transfer-encoding']).toBe('chunked') - }) - test('sets Content Security Policy (CSP) headers', async () => { const res = await get('/en') expect('content-security-policy' in res.headers).toBe(true) @@ -150,7 +144,7 @@ describe('server', () => { }) test('renders a 404 page', async () => { - const $ = await getDOM('/not-a-real-page') + const $ = await getDOM('/not-a-real-page', { allow404: true }) expect($('h1').text()).toBe('Ooops!') expect($.text().includes("It looks like this page doesn't exist.")).toBe(true) expect( @@ -168,17 +162,17 @@ describe('server', () => { // see issue 12427 test('renders a 404 for leading slashes', async () => { - let $ = await getDOM('//foo.com/enterprise') + let $ = await getDOM('//foo.com/enterprise', { allow404: true }) expect($('h1').text()).toBe('Ooops!') expect($.res.statusCode).toBe(404) - $ = await getDOM('///foo.com/enterprise') + $ = await getDOM('///foo.com/enterprise', { allow404: true }) expect($('h1').text()).toBe('Ooops!') expect($.res.statusCode).toBe(404) }) test('renders a 500 page when errors are thrown', async () => { - const $ = await getDOM('/_500', undefined, true) + const $ = await getDOM('/_500', { allow500s: true }) expect($('h1').text()).toBe('Ooops!') expect($.text().includes('It looks like something went wrong.')).toBe(true) expect( @@ -584,8 +578,10 @@ describe('server', () => { test('is not displayed if ghec article has only one version', async () => { const $ = await getDOM( - '/en/enterprise-cloud@latest/admin/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users' + '/en/enterprise-cloud@latest/admin/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users', + { allow404: true } ) + expect($.res.statusCode).toBe(404) expect($('.article-versions').length).toBe(0) }) }) @@ -670,6 +666,24 @@ describe('server', () => { ) }) + // This test exists because in a previous life, our NextJS used to + // 500 if the 'Accept-Language' header was malformed. + // We *used* have a custom middleware to cope with this and force a + // fallback redirect. + // See internal issue 19909 + test('redirects /en if Accept-Language header is malformed', async () => { + const res = await get('/', { + headers: { + 'accept-language': 'ldfir;', + }, + }) + + expect(res.statusCode).toBe(302) + expect(res.headers.location).toBe('/en') + expect(res.headers['cache-control']).toBe('private, no-store') + expect(res.headers['set-cookie']).toBeUndefined() + }) + test('redirects / to /en when unsupported language preference is specified', async () => { const res = await get('/', { headers: { diff --git a/tests/rendering/static-assets.js b/tests/rendering/static-assets.js new file mode 100644 index 0000000000..285c54336a --- /dev/null +++ b/tests/rendering/static-assets.js @@ -0,0 +1,168 @@ +import fs from 'fs' +import path from 'path' + +import nock from 'nock' +import { expect, jest } from '@jest/globals' + +import { SURROGATE_ENUMS } from '../../middleware/set-fastly-surrogate-key.js' +import { get } from '../helpers/supertest.js' + +function getNextStaticAsset(directory) { + const root = path.join('.next', 'static', directory) + const files = fs.readdirSync(root) + if (!files.length) throw new Error(`Can't find any files in ${root}`) + return path.join(root, files[0]) +} + +function checkCachingHeaders(res, defaultSurrogateKey = false, minMaxAge = 60 * 60) { + expect(res.headers['set-cookie']).toBeUndefined() + expect(res.headers['cache-control']).toContain('public') + const maxAgeSeconds = parseInt(res.header['cache-control'].match(/max-age=(\d+)/)[1], 10) + // Let's not be too specific in the tests, just as long as it's testing + // that it's a reasonably large number of seconds. + expect(maxAgeSeconds).toBeGreaterThanOrEqual(minMaxAge) + // Because it doesn't have have a unique URL + expect(res.headers['surrogate-key']).toBe( + defaultSurrogateKey ? SURROGATE_ENUMS.DEFAULT : SURROGATE_ENUMS.MANUAL + ) +} + +describe('static assets', () => { + it('should serve /assets/cb-* with optimal headers', async () => { + const res = await get('/assets/cb-1234/images/site/logo.png') + expect(res.statusCode).toBe(200) + checkCachingHeaders(res) + }) + + it('should serve /assets/ with optimal headers', async () => { + const res = await get('/assets/images/site/logo.png') + expect(res.statusCode).toBe(200) + checkCachingHeaders(res, true) + }) + + it('should serve /_next/static/ with optimal headers', async () => { + // This picks the first one found. We just need it to be anything + // that actually resolves. + const filePath = getNextStaticAsset('css') + const asURL = '/' + filePath.replace('.next', '_next').split(path.sep).join('/') + const res = await get(asURL) + expect(res.statusCode).toBe(200) + checkCachingHeaders(res) + }) + + it('should 404 on /assets/cb-* with plain text', async () => { + const res = await get('/assets/cb-1234/never/heard/of.png') + expect(res.statusCode).toBe(404) + expect(res.header['content-type']).toContain('text/plain') + // Only a tiny amount of Cache-Control on these + checkCachingHeaders(res, true, 60) + }) + it('should 404 on /assets/ with plain text', async () => { + const res = await get('/assets/never/heard/of.png') + expect(res.statusCode).toBe(404) + expect(res.header['content-type']).toContain('text/plain') + checkCachingHeaders(res, true, 60) + }) + it('should 404 on /_next/static/ with plain text', async () => { + const res = await get('/_next/static/never/heard/of.css') + expect(res.statusCode).toBe(404) + expect(res.header['content-type']).toContain('text/plain') + checkCachingHeaders(res, true, 60) + }) +}) + +describe('archived enterprise static assets', () => { + // Sometimes static assets are proxied. The URL for the static asset + // might not indicate it's based on archived enterprise version. + + jest.setTimeout(60 * 1000) + + beforeAll(async () => { + // The first page load takes a long time so let's get it out of the way in + // advance to call out that problem specifically rather than misleadingly + // attributing it to the first test + // await get('/') + + const sampleCSS = '/* nice CSS */' + + nock('https://github.github.com') + .get('/help-docs-archived-enterprise-versions/2.21/_next/static/foo.css') + .reply(200, sampleCSS, { + 'content-type': 'text/css', + 'content-length': sampleCSS.length, + }) + nock('https://github.github.com') + .get('/help-docs-archived-enterprise-versions/2.21/_next/static/only-on-proxy.css') + .reply(200, sampleCSS, { + 'content-type': 'text/css', + 'content-length': sampleCSS.length, + }) + nock('https://github.github.com') + .get('/help-docs-archived-enterprise-versions/2.3/_next/static/only-on-2.3.css') + .reply(200, sampleCSS, { + 'content-type': 'text/css', + 'content-length': sampleCSS.length, + }) + nock('https://github.github.com') + .get('/help-docs-archived-enterprise-versions/2.3/_next/static/fourofour.css') + .reply(404, 'Not found', { + 'content-type': 'text/plain', + }) + nock('https://github.github.com') + .get('/help-docs-archived-enterprise-versions/2.3/assets/images/site/logo.png') + .reply(404, 'Not found', { + 'content-type': 'text/plain', + }) + }) + + afterAll(() => nock.cleanAll()) + + it('should proxy if the static asset is prefixed', async () => { + const res = await get('/enterprise/2.21/_next/static/foo.css', { + headers: { + Referrer: '/enterprise/2.21', + }, + }) + expect(res.statusCode).toBe(200) + checkCachingHeaders(res, true, 60) + }) + it('should proxy if the Referrer header indicates so', async () => { + const res = await get('/_next/static/only-on-proxy.css', { + headers: { + Referrer: '/enterprise/2.21', + }, + }) + expect(res.statusCode).toBe(200) + checkCachingHeaders(res, true, 60) + }) + it('should proxy if the Referrer header indicates so', async () => { + const res = await get('/_next/static/only-on-2.3.css', { + headers: { + Referrer: '/en/enterprise-server@2.3/some/page', + }, + }) + expect(res.statusCode).toBe(200) + checkCachingHeaders(res, true, 60) + }) + it('might still 404 even with the right referrer', async () => { + const res = await get('/_next/static/fourofour.css', { + headers: { + Referrer: '/en/enterprise-server@2.3/some/page', + }, + }) + expect(res.statusCode).toBe(404) + checkCachingHeaders(res, true, 60) + }) + + it('404 on the proxy but actually present here', async () => { + const res = await get('/assets/images/site/logo.png', { + headers: { + Referrer: '/en/enterprise-server@2.3/some/page', + }, + }) + // It tried to go via the proxy, but it wasn't there, but then it + // tried "our disk" and it's eventually there. + expect(res.statusCode).toBe(200) + checkCachingHeaders(res, true, 60) + }) +}) diff --git a/tests/routing/developer-site-redirects.js b/tests/routing/developer-site-redirects.js index 1351145efd..a4016caa86 100644 --- a/tests/routing/developer-site-redirects.js +++ b/tests/routing/developer-site-redirects.js @@ -1,6 +1,5 @@ import { jest } from '@jest/globals' import path from 'path' -import { eachOfLimit } from 'async' import enterpriseServerReleases from '../../lib/enterprise-server-releases.js' import { get } from '../helpers/supertest.js' import readJsonFile from '../../lib/read-json-file.js' @@ -8,8 +7,6 @@ const restRedirectFixtures = readJsonFile('./tests/fixtures/rest-redirects.json' const graphqlRedirectFixtures = readJsonFile('./tests/fixtures/graphql-redirects.json') const developerRedirectFixtures = readJsonFile('./tests/fixtures/developer-redirects.json') -const MAX_CONCURRENT_REQUESTS = 50 - jest.useFakeTimers('legacy') describe('developer redirects', () => { @@ -106,23 +103,23 @@ describe('developer redirects', () => { describe('fixtures', () => { // this fixtures file includes paths like /apps and /webhooks, plus /enterprise paths test('developer redirects', async () => { - await eachOfLimit( - developerRedirectFixtures, - MAX_CONCURRENT_REQUESTS, - async (newPath, oldPath) => { - const res = await get(oldPath) - const sameFirstPrefix = oldPath.split('/')[1] === newPath.split('/')[1] - expect(res.statusCode, `${oldPath} did not redirect to ${newPath}`).toBe( - sameFirstPrefix ? 301 : 302 - ) - expect(res.headers.location).toBe(newPath) - } - ) + // Don't use a `Promise.all()` because it's actually slower + // because of all the eventloop context switching. + for (const [oldPath, newPath] of Object.entries(developerRedirectFixtures)) { + const res = await get(oldPath) + const sameFirstPrefix = oldPath.split('/')[1] === newPath.split('/')[1] + expect(res.statusCode, `${oldPath} did not redirect to ${newPath}`).toBe( + sameFirstPrefix ? 301 : 302 + ) + expect(res.headers.location).toBe(newPath) + } }) // this fixtures file includes /v3 and /enterprise/v3 paths test('rest reference redirects', async () => { - await eachOfLimit(restRedirectFixtures, MAX_CONCURRENT_REQUESTS, async (newPath, oldPath) => { + // Don't use a `Promise.all()` because it's actually slower + // because of all the eventloop context switching. + for (let [oldPath, newPath] of Object.entries(restRedirectFixtures)) { // REST and GraphQL developer Enterprise paths with a version are only supported up to 2.21. // We make an exception to always redirect versionless paths to the latest version. newPath = newPath.replace( @@ -136,29 +133,27 @@ describe('developer redirects', () => { sameFirstPrefix ? 301 : 302 ) expect(res.headers.location, `${oldPath} did not redirect to ${newPath}`).toBe(newPath) - }) + } }) // this fixtures file includes /v4 and /enterprise/v4 paths test('graphql reference redirects', async () => { - await eachOfLimit( - graphqlRedirectFixtures, - MAX_CONCURRENT_REQUESTS, - async (newPath, oldPath) => { - // REST and GraphQL developer Enterprise paths with a version are only supported up to 2.21. - // We make an exception to always redirect versionless paths to the latest version. - newPath = newPath.replace( - '/enterprise-server/', - `/enterprise-server@${enterpriseServerReleases.latest}/` - ) - const res = await get(oldPath) - const sameFirstPrefix = oldPath.split('/')[1] === newPath.split('/')[1] - expect(res.statusCode, `${oldPath} did not redirect to ${newPath}`).toBe( - sameFirstPrefix ? 301 : 302 - ) - expect(res.headers.location, `${oldPath} did not redirect to ${newPath}`).toBe(newPath) - } - ) + // Don't use a `Promise.all()` because it's actually slower + // because of all the eventloop context switching. + for (let [oldPath, newPath] of Object.entries(graphqlRedirectFixtures)) { + // REST and GraphQL developer Enterprise paths with a version are only supported up to 2.21. + // We make an exception to always redirect versionless paths to the latest version. + newPath = newPath.replace( + '/enterprise-server/', + `/enterprise-server@${enterpriseServerReleases.latest}/` + ) + const res = await get(oldPath) + const sameFirstPrefix = oldPath.split('/')[1] === newPath.split('/')[1] + expect(res.statusCode, `${oldPath} did not redirect to ${newPath}`).toBe( + sameFirstPrefix ? 301 : 302 + ) + expect(res.headers.location, `${oldPath} did not redirect to ${newPath}`).toBe(newPath) + } }) }) }) diff --git a/tests/routing/redirects.js b/tests/routing/redirects.js index 07200e7961..27dd42623b 100644 --- a/tests/routing/redirects.js +++ b/tests/routing/redirects.js @@ -4,7 +4,6 @@ import { isPlainObject } from 'lodash-es' import supertest from 'supertest' import createApp from '../../lib/app.js' import enterpriseServerReleases from '../../lib/enterprise-server-releases.js' -import nonEnterpriseDefaultVersion from '../../lib/non-enterprise-default-version.js' import Page from '../../lib/page.js' import { get } from '../helpers/supertest.js' import versionSatisfiesRange from '../../lib/version-satisfies-range.js' @@ -21,38 +20,34 @@ describe('redirects', () => { redirects = JSON.parse(res.text) }) - test('page.redirects is an array', async () => { + test('page.buildRedirects() returns an array', async () => { const page = await Page.init({ relativePath: 'pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md', basePath: path.join(__dirname, '../../content'), languageCode: 'en', }) - page.buildRedirects() - expect(isPlainObject(page.redirects)).toBe(true) + const pageRedirects = page.buildRedirects() + expect(isPlainObject(pageRedirects)).toBe(true) }) - test('dotcom homepage page.redirects', async () => { + test('dotcom homepage page.buildRedirects()', async () => { const page = await Page.init({ relativePath: 'github/index.md', basePath: path.join(__dirname, '../../content'), languageCode: 'en', }) - page.buildRedirects() - expect(page.redirects[`/en/${nonEnterpriseDefaultVersion}/github`]).toBe('/en/github') - expect(page.redirects['/articles']).toBe('/en/github') - expect(page.redirects['/en/articles']).toBe('/en/github') - expect(page.redirects[`/en/${nonEnterpriseDefaultVersion}/articles`]).toBe('/en/github') - expect(page.redirects['/common-issues-and-questions']).toBe('/en/github') - expect(page.redirects['/en/common-issues-and-questions']).toBe('/en/github') - expect(page.redirects[`/en/enterprise/${enterpriseServerReleases.latest}/user/articles`]).toBe( - `/en/enterprise-server@${enterpriseServerReleases.latest}/github` + const pageRedirects = page.buildRedirects() + expect(pageRedirects['/articles']).toBe('/github') + expect(pageRedirects['/common-issues-and-questions']).toBe('/github') + expect(pageRedirects[`/enterprise-server@${enterpriseServerReleases.latest}/articles`]).toBe( + `/enterprise-server@${enterpriseServerReleases.latest}/github` ) expect( - page.redirects[ - `/en/enterprise/${enterpriseServerReleases.latest}/user/common-issues-and-questions` + pageRedirects[ + `/enterprise-server@${enterpriseServerReleases.latest}/common-issues-and-questions` ] - ).toBe(`/en/enterprise-server@${enterpriseServerReleases.latest}/github`) + ).toBe(`/enterprise-server@${enterpriseServerReleases.latest}/github`) }) test('converts single `redirect_from` strings values into arrays', async () => { @@ -61,8 +56,8 @@ describe('redirects', () => { basePath: path.join(__dirname, '../fixtures'), languageCode: 'en', }) - page.buildRedirects() - expect(page.redirects['/redirect-string']).toBe('/en/article-with-redirect-from-string') + const pageRedirects = page.buildRedirects() + expect(pageRedirects['/redirect-string']).toBe('/article-with-redirect-from-string') }) describe('query params', () => { @@ -101,12 +96,6 @@ describe('redirects', () => { const res = await get(reqPath) expect(res.statusCode).toBe(200) }) - - test('work on deprecated versions', async () => { - const res = await get('/enterprise/2.12/admin/search?utf8=%E2%9C%93&q=pulls') - expect(res.statusCode).toBe(301) - expect(res.headers.location).toBe('/enterprise/2.12/admin/search?utf8=%E2%9C%93&query=pulls') - }) }) describe('trailing slashes', () => { diff --git a/tests/unit/get-redirect.js b/tests/unit/get-redirect.js new file mode 100644 index 0000000000..5ad969f6ed --- /dev/null +++ b/tests/unit/get-redirect.js @@ -0,0 +1,151 @@ +import getRedirect from '../../lib/get-redirect.js' +import { latest } from '../../lib/enterprise-server-releases.js' + +describe('getRedirect basics', () => { + it('should sometimes not correct the version prefix', () => { + // This essentially tests legacy entries that come from the + // `developer.json` file. Normally, we would have first + // rewritten `/enterprise/3.0` to `/enterprise-server@3.0` + // and then, from there, worried about the remaining `/foo/bar` + // part. + // But some redirects from `developer.json` as old and static. + const uri = '/enterprise/3.0/foo/bar' + const ctx = { + pages: {}, + redirects: { + '/enterprise/3.0/foo/bar': '/something/else', + }, + } + expect(getRedirect(uri, ctx)).toBe('/en/something/else') + }) + + it('should return undefined if nothing could be found', () => { + const ctx = { + pages: {}, + redirects: {}, + } + expect(getRedirect('/foo/pizza', ctx)).toBeUndefined() + }) + + it('should just inject language on version "home pages"', () => { + const ctx = { + pages: {}, + redirects: {}, + } + expect(getRedirect('/github-ae@latest', ctx)).toBe('/en/github-ae@latest') + + expect(getRedirect('/enterprise-cloud@latest', ctx)).toBe('/en/enterprise-cloud@latest') + + expect(getRedirect('/enterprise-server@3.3', ctx)).toBe('/en/enterprise-server@3.3') + + expect(getRedirect('/enterprise-server@latest', ctx)).toBe(`/en/enterprise-server@${latest}`) + expect(getRedirect('/enterprise-server', ctx)).toBe(`/en/enterprise-server@${latest}`) + }) + + it('should always "remove" the free-pro-team prefix', () => { + const ctx = { + pages: {}, + redirects: { + '/foo': '/bar', + }, + } + expect(getRedirect('/free-pro-team@latest', ctx)).toBe('/en') + // Language is fine, but the version needs to be "removed" + expect(getRedirect('/en/free-pro-team@latest', ctx)).toBe('/en') + expect(getRedirect('/free-pro-team@latest/pizza', ctx)).toBe('/en/pizza') + expect(getRedirect('/free-pro-team@latest/foo', ctx)).toBe('/en/bar') + expect(getRedirect('/free-pro-team@latest/github', ctx)).toBe('/en/github') + }) + + it('should handle some odd exceptions', () => { + const ctx = { + pages: {}, + redirects: {}, + } + expect(getRedirect('/desktop/guides/foo/bar', ctx)).toBe('/en/desktop/foo/bar') + expect(getRedirect('/admin/guides/foo/bar', ctx)).toBe( + `/en/enterprise-server@${latest}/admin/foo/bar` + ) + expect(getRedirect('/admin/something/else', ctx)).toBe( + `/en/enterprise-server@${latest}/admin/something/else` + ) + expect(getRedirect('/insights/stuff', ctx)).toBe( + `/en/enterprise-server@${latest}/insights/stuff` + ) + }) + + it('should figure out redirect based on presence of pages in certain cases', () => { + const ctx = { + pages: { + '/en/enterprise-server@3.2/foo/bar': null, + '/en/enterprise-server@3.2/admin/github-management': null, + }, + redirects: {}, + } + // Replacing `/user` with `` worked because there exits a page of such name. + expect(getRedirect('/enterprise-server@3.2/user/foo/bar', ctx)).toBe( + '/en/enterprise-server@3.2/foo/bar' + ) + expect(getRedirect('/enterprise-server@3.2/admin/guides/user-management', ctx)).toBe( + '/en/enterprise-server@3.2/admin/github-management' + ) + }) + + it('should always correct the old enterprise prefix', () => { + const ctx = { + pages: {}, + redirects: { + '/enterprise-server@3.3/foo': '/enterprise-server@3.3/bar', + }, + } + expect(getRedirect('/enterprise', ctx)).toBe(`/en/enterprise-server@${latest}`) + expect(getRedirect('/enterprise/3.3', ctx)).toBe('/en/enterprise-server@3.3') + expect(getRedirect('/enterprise/3.3/something', ctx)).toBe( + '/en/enterprise-server@3.3/something' + ) + // but also respect redirects if there are some + expect(getRedirect('/enterprise/3.3/foo', ctx)).toBe('/en/enterprise-server@3.3/bar') + + // Unique snowflake pattern + expect(getRedirect('/enterprise/github/admin/foo', ctx)).toBe( + `/en/enterprise-server@${latest}/github/admin/foo` + ) + }) + + it('should not do anything on some prefixes', () => { + const ctx = { + pages: {}, + redirects: {}, + } + // Nothing's needed here because it's not /admin/guides and + // it already has the enterprise-server prefix. + expect(getRedirect(`/en/enterprise-server@${latest}/admin/something/else`, ctx)).toBeUndefined() + expect(getRedirect(`/en/enterprise-cloud@latest/user/foo`, ctx)).toBeUndefined() + }) + + it('should only inject language sometimes', () => { + const ctx = { + pages: {}, + redirects: { + '/foo': '/bar', + }, + } + // Nothing's needed here because it's not /admin/guides and + // it already has the enterprise-server prefix. + expect(getRedirect('/foo', ctx)).toBe('/en/bar') + expect(getRedirect('/en/foo', ctx)).toBe('/en/bar') + expect(getRedirect('/ja/foo', ctx)).toBe('/ja/bar') + }) + + it('should redirect both the prefix and the path needs to change', () => { + const ctx = { + pages: {}, + redirects: { + [`/enterprise-server@${latest}/foo`]: `/enterprise-server@${latest}/bar`, + }, + } + // Nothing's needed here because it's not /admin/guides and + // it already has the enterprise-server prefix. + expect(getRedirect('/enterprise-server/foo', ctx)).toBe(`/en/enterprise-server@${latest}/bar`) + }) +}) diff --git a/tests/unit/page.js b/tests/unit/page.js index 8ee036dba4..5a397e4148 100644 --- a/tests/unit/page.js +++ b/tests/unit/page.js @@ -113,6 +113,32 @@ describe('Page class', () => { ).toBeGreaterThan(0) }) + // Much of this test is based on making sure we don't + // repeat the bug introduced in issue 1545. + test('rewrites links correctly for unsupported enterprise-server links', async () => { + const page = await Page.init({ + relativePath: 'page-with-deprecated-enterprise-links.md', + basePath: path.join(__dirname, '../fixtures'), + languageCode: 'en', + }) + const context = { + page: { version: `enterprise-server@${enterpriseServerReleases.latest}` }, + currentVersion: `enterprise-server@${enterpriseServerReleases.latest}`, + currentPath: '/en/page-with-deprecated-enterprise-links', + currentLanguage: 'en', + } + const rendered = await page.render(context) + // That page only contains exactly 2 links. And we can know + // exactly what we expect each one to be. + const $ = cheerio.load(rendered) + const first = $('a[href]').first() + expect(first.text()).toBe('Version 2.22') + expect(first.attr('href')).toBe('/en/enterprise-server@2.22') + const last = $('a[href]').last() + expect(last.text()).toBe('Version 3.2') + expect(last.attr('href')).toBe('/en/enterprise-server@3.2') + }) + test('rewrites links on prerendered GraphQL page include the current language prefix and version', async () => { const graphqlVersion = allVersions[`enterprise-server@${enterpriseServerReleases.latest}`].miscVersionName 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 664c43aab5..b66f6d180b 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 @@ -38,7 +38,7 @@ Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, 1. Solicita el nombre de usuario de la persona a la que estás invitando como colaborador.{% ifversion fpt or ghec %} Si aún no tiene un nombre de usuario, puede registrarse para {% data variables.product.prodname_dotcom %} Para obtener más información, consulta "[Registrar una cuenta {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account)".{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%} {% data reusables.repositories.click-collaborators-teams %} 1. Da clic en **Invitar un colaborador**. ![botón de "invitar un colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png) 2. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field-user.png) 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-a-collaborator-from-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/removing-a-collaborator-from-a-personal-repository.md index 027c3629b8..9c9e625b8d 100644 --- a/translations/es-ES/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/es-ES/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,7 +30,7 @@ Aunque se borren las bifurcaciones de los repositorios privados cuando se elimin {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} 4. Da clic en {% octicon "trash" aria-label="The trash icon" %} a la derecha del colaborador que quieres eliminar. ![Botón para eliminar un colaborador](/assets/images/help/repository/collaborator-remove.png) {% else %} 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 3be45c2a1b..4dfccdaf02 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 @@ -21,7 +21,7 @@ shortTitle: Eliminarte a ti mismo --- {% data reusables.user_settings.access_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index d8335fc89f..5c314444e4 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -22,7 +22,7 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% note %} -**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 36a4e1b60b..d2da20b22b 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -69,7 +69,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build ``` @@ -106,7 +106,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Run the Gradle package task - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: -b ci.gradle package ``` @@ -135,7 +135,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build - uses: actions/upload-artifact@v2 diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 6ca54788a1..3795a144fd 100644 --- a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -47,7 +47,7 @@ Si defines el `entrypoint` en un archivo de metadatos de una acción, este inval La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. Para obtener más información acerca de las formas _exec_ y _shell_, consulta la sección [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) en la documentación de Docker. -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). +No deberías utilizar `WORKDIR` para especificar el punto de entrada en tu Dockerfile. En vez de esto, deberías utilizar una ruta absoluta. Para obtener más información, consulta la sección [WORKDIR](#workdir). Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`. @@ -101,7 +101,7 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s ### CMD -If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)". +Si defines el `args` en el archivo de metadatos de la acción, `args` invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)". Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos: 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 2eaa836207..3427268d05 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 %} -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. +Todas las acciones requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos en el archivo de metadatos definen las configuraciones de entradas, salidas y ejecuciones de tu acción. 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)". @@ -41,7 +41,7 @@ Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAM **Opcional** Los parámetros de entrada te permiten especificar datos que la acción espera para usar durante el tiempo de ejecución. {% data variables.product.prodname_dotcom %} almacena parámetros de entrada como variables de entorno. Las Id de entrada con letras mayúsculas se convierten a minúsculas durante el tiempo de ejecución. Recomendamos usar Id de entrada en minúsculas. -### Example: Specifying inputs +### Ejemplo: Especificar las entradas Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with` (con), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)". @@ -84,13 +84,13 @@ Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `oc **Opcional** Si se utiliza el parámetro de entrada, esta `string` se registrará como un mensaje de advertencia. Puedes utilizar esta advertencia para notificar a los usuarios que la entrada es obsoleta y mencionar cualquier alternativa. -## `outputs` for Docker container and JavaScript actions +## `outputs` para las acciones de contenedores de Docker y JavaScript **Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior. Por ejemplo, si tuviste una acción que realizó la adición de dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada. Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% 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 +### Ejemplo: Declarar las salidas para las acciones de contenedores de Docker y JavaScript ```yaml outputs: @@ -108,9 +108,9 @@ outputs: ## `outputs` para las acciones compuestas -**Optional** `outputs` use the same parameters as `outputs.` and `outputs..description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token. +Las `outputs` **opcionales** utilizan los mismos parámetros que `outputs.` y `outputs..description` (consulta la sección de "[`outputs` para acciones de contenedores de Docker y JavaScript](#outputs-for-docker-container-and-javascript-actions)"), pero también incluye el token `value`. -### Example: Declaring outputs for composite actions +### Ejemplo: Declarar las salidas para las acciones compuestas {% raw %} ```yaml @@ -135,13 +135,13 @@ Para obtener más información sobre cómo utilizar la sintaxis de contexto, con ## `runs` -**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed. +**Requerido** Especifica si es una acción de JavaScript, una acción compuesta o una acción de contenedor de Docker y cómo se ejecuta esta. ## `runs` para acciones de JavaScript **Requerido** Configura la ruta al código de la acción y el tiempo de ejecución que se utiliza para ejecutarlo. -### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %} +### Ejemplo: Utilizar Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %} ```yaml runs: @@ -162,7 +162,7 @@ runs: ### `runs.pre` -**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if). +**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. La acción `pre` siempre se ejecuta predeterminadamente, pero puedes invalidar esto utilizando [`runs.pre-if`](#runspre-if). En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`: @@ -365,11 +365,11 @@ runs: ``` {% endif %} -## `runs` for Docker container actions +## `runs` para las acciones de contenedores de Docker -**Required** Configures the image used for the Docker container action. +**Requerido** Configura la imagen que se utiliza para la acción de contenedores de Docker. -### Example: Using a Dockerfile in your repository +### Ejemplo: Utilizar un Dockerfile en tu repositorio ```yaml runs: @@ -377,7 +377,7 @@ runs: image: 'Dockerfile' ``` -### Example: Using public Docker registry container +### Ejemplo: Utilizar un contenedor de registro público de Docker ```yaml runs: @@ -391,7 +391,7 @@ runs: ### `runs.pre-entrypoint` -**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if). +**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `pre-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes anular esto utilizando [`runs.pre-if`](#runspre-if). El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. @@ -423,7 +423,7 @@ Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consu ### `post-entrypoint` -**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if). +**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `post-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes anular esto utilizando [`runs.post-if`](#runspost-if). ```yaml runs: @@ -447,7 +447,7 @@ Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta eje Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)". -#### Example: Defining arguments for the Docker container +#### Ejemplo: Definir argumentos para el contenedor de Docker {% raw %} ```yaml @@ -465,7 +465,7 @@ runs: Puedes usar un color y un icono de [Pluma](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -### Example: Configuring branding for an action +### Ejemplo: Configurar la personalización de una acción ```yaml branding: diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index b1bd8075ff..52cc87e50c 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New self-hosted runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %} {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} @@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} @@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise {% data reusables.enterprise-accounts.actions-runners-tab %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product 1. Click **Add new**, then click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} -{% ifversion ghec or ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -{% endif %} ### Making enterprise runners available to repositories diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index ebeb8d58da..12f78de075 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -46,7 +46,7 @@ Los ejecutores auto-hospedados se asignan automáticamente al grupo predetermina Cuando creas un grupo, debes elegir una política que defina qué repositorios tienen acceso al grupo ejecutor. -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} @@ -61,12 +61,11 @@ Cuando creas un grupo, debes elegir una política que defina qué repositorios t {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. En la sección de "Ejecutores auto-hospedados", haz clic en **Agregar nuevo** y luego en **Grupo nuevo**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**. ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group.png) 1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio. @@ -95,7 +94,7 @@ Los ejecutores auto-hospedados se asignan automáticamente al grupo predetermina Cuando creas un grupo, debes elegir la política que defina qué organizaciones tienen acceso al grupo de ejecutores. -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -113,8 +112,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -144,7 +142,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones ## Cambiar la política de acceso de un grupo de ejecutores auto-hospedados Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo. -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} 1. Modifica las opciones de acceso o cambia el nombre del grupo de ejecutores. @@ -158,8 +156,7 @@ Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} @@ -181,17 +178,18 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## Mover un ejecutor auto-hospedado a un grupo Si no especificas un grupo de ejecutores durante el proceso de registro, tus ejecutores auto-hospedados nuevos se asignarán automáticamente al grupo predeterminado y después se moverán a otro grupo. -{% ifversion ghec or ghes > 3.1 or ghae %} + {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} 1. En la lista de "Ejecutores", haz clic en aquél que quieras configurar. 2. Selecciona el menú desplegable del grupo de ejecutores. 3. En "Mover el ejecutor al grupo", elige un grupo destino para el ejecutor. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} -1. En la sección de "Ejecutores auto-hospedados" de la página de configuración, ubica el grupo actual del ejecutor que quieres mover y expande la lista de miembros del grupo. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png) +{% elsif ghae or ghes < 3.4 %} +1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png) 2. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. Para mover el ejecutor, da clic en el grupo de destino. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} + ## Eliminar un grupo de ejecutores auto-hospedados Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina. @@ -201,8 +199,7 @@ Los ejecutores auto-hospedados se devuelven automáticamente al grupo predetermi 1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 2. Para eliminar el grupo, da clic en **Eliminar grupo**. 3. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} +{% elsif ghes < 3.2 %} 1. En la sección de "Ejecutores auto-hospedados" de la página de ajustes, ubica el grupo que quieras borrar y haz clic en el botón {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. Para eliminar el grupo, da clic en **Eliminar grupo**. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 60cdee66e1..aad261e14c 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -30,20 +30,20 @@ shortTitle: Elimina ejecutores auto-hospedados Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)". {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Eliminar el ejecutor de una organización {% note %} @@ -57,19 +57,20 @@ Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)". {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghes > 3.3 or ghec %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% else %} +{% elsif ghes < 3.4 or ghae %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Eliminar un ejecutor de una empresa {% ifversion fpt %} @@ -85,19 +86,17 @@ Si utilizas {% endnote %} -{% data reusables.github-actions.self-hosted-runner-reusing %} +To remove a self-hosted runner from an enterprise, you must be an enterprise owner. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). -{% ifversion ghec %} -Para eliminar a un ejecutor auot-hospedado de una cuenta empresarial, debes ser un propietario de la empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo agregar un ejecutor auto-hospedado con la API de REST, consulta las [API de GitHub Actions para la Administración Empresarial](/rest/reference/enterprise-admin#github-actions). +{% data reusables.github-actions.self-hosted-runner-reusing %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% elsif ghae or ghes %} -Para eliminar un ejecutor auto-hospedado a nivel empresarial de -{% data variables.product.product_location %}, debes ser un propietario de empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index b1e805297d..e3b4ce03b5 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -19,13 +19,13 @@ Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} ## Crear una etiqueta personalizada -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} 1. En la sección de "Etiquetas", haz clic en {% octicon "gear" aria-label="The Gear icon" %}. 1. En el campo de "Encuentra o crea una etiqueta", teclea el nombre de tu etiqueta nueva y haz clic en **Crear etiqueta nueva**. La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} @@ -34,35 +34,38 @@ Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## Asignar una etiqueta a un ejecutor auto-hospedado -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. Para asignar una etiqueta a tu ejecutor auto-hospedado, en el campo de "Encuentra o crea una etiqueta", haz clic en ella. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. Da clic en la etiqueta para asignarla a tu ejecutor auto-hospedado. {% endif %} + ## Eliminar una etiqueta personalizada de un ejecutor auto-hospedado -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. En el campo "Encuentra o crea una etiqueta", las etiquetas asignadas se marcan con el icono {% octicon "check" aria-label="The Check icon" %}. Haz clic en una etiqueta marcada para desasignarla de tu ejecutor auto-hospedado. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## Utilizar el script de configuración para crear y asignar etiquetas Puedes utilizar el script de configuración en el ejecutor auto-hospedado para crear y asignar etiquetas personalizadas. Por ejemplo, este comando asigna una etiqueta llamada `gpu` al ejecutor auto-hospedado. diff --git a/translations/es-ES/content/actions/learn-github-actions/expressions.md b/translations/es-ES/content/actions/learn-github-actions/expressions.md index 091664c3ff..dc9f053988 100644 --- a/translations/es-ES/content/actions/learn-github-actions/expressions.md +++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md @@ -50,12 +50,12 @@ env: Como parte de una expresión, puedes usar tipos de datos `boolean`, `null`, `number` o `string`. -| Tipo de datos | Valor literal | -| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `boolean` | `verdadero` o `falso` | -| `null` | `null` | -| `number` | Cualquier formato de número compatible con JSON. | -| `secuencia` | 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. | +| Tipo de datos | Valor literal | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `boolean` | `verdadero` o `falso` | +| `null` | `null` | +| `number` | Cualquier formato de número compatible con JSON. | +| `secuencia` | 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. | #### Ejemplo diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index 12d581031b..c1397f7825 100644 --- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -96,7 +96,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -167,7 +167,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -246,7 +246,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: {% raw %} 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 b86900fd20..8394d835de 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 @@ -85,8 +85,8 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau | actions | read/write | none | read | | checks | read/write | none | read | | contents | read/write | read | read | -| deployments | read/write | none | read | -| id-token | read/write | none | read | +| deployments | read/write | none | read |{% ifversion fpt or ghec %} +| id-token | read/write | none | read |{% endif %} | issues | read/write | none | read | | metadata | read | read | read | | packages | read/write | none | read | diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md index 80516f0aec..b9f7499abf 100644 --- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md @@ -202,6 +202,10 @@ El mismo principio que se describió anteriormente para utilizar acciones de ter {% data reusables.actions.outside-collaborators-internal-actions %} Para obtener más información, consulta la sección "[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)". {% endif %} +## Using OpenSSF Scorecards to secure workflows + +[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions. + ## Impacto potencial de un ejecutor puesto en riesgo Estas secciones consideran algunos de los pasos que puede llevar a cabo un atacante si pueden ejecutar comandos malintencionados en un ejecutor de {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md index 92fad1018d..4425732fab 100644 --- a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/es-ES/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: @@ -996,9 +992,9 @@ on: ### `lanzamiento` -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------- | -| [`lanzamiento`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | Última confirmación en el lanzamiento etiquetado | Etiqueta de lanzamiento | +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------- | +| [`lanzamiento`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | Última confirmación en el lanzamiento etiquetado | Tag ref of release `refs/tags/` | {% note %} diff --git a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md index 788f2c0eda..cae52e535d 100644 --- a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -314,7 +314,9 @@ Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos tempor {% warning %} -**Advertencia:** en Windows, el PowerShell tradicional (`shell: powershell`) no utiliza el cifrado UTF-8 predeterminado. Asegúrate que escribes los archivos utilizando la codificación correcta. Por ejemplo, necesitas configurar la codificación UTF-8 cuando configuras la ruta: +**Advertencia:** en Windows, el PowerShell tradicional (`shell: powershell`) no utiliza el cifrado UTF-8 predeterminado. + +When using `shell: powershell`, you must specify UTF-8 encoding. Por ejemplo: ```yaml jobs: @@ -325,22 +327,7 @@ jobs: run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -O cambia a PowerShell Core, el cual tiene predeterminado el UTF-8: - -```yaml -jobs: - modern-pwsh-example: - uses: windows-2019 - steps: - - shell: pwsh - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8 -``` - -Puedes obtener más detalles sobre el UTF-8 y PowerShell Core en esta genial [respuesta de Stack Overflow](https://stackoverflow.com/a/40098904/162694): - -> ### Lectura opcional: La perspectiva multiplataforma: PowerShell _Core_: -> -> [PowerShell ahora es multiplataforma](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/)a través de su edición **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)**, cuyo cifrado ***se predetermina sensiblemente em ***BOM-less UTF-8****** en línea con las plataformas similares a las de Unix. +Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8. {% endwarning %} 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 2d62328779..f3c3379e0b 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 @@ -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: diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 61e750cc30..6afb61b812 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -699,7 +699,7 @@ All Storage tests passed `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}. -For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/). +For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). ### git-import-detect diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md index 81a40ba9f7..31a26cb6ef 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md +++ b/translations/es-ES/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/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md index 0a28fc6e08..13fc45c5ab 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md @@ -47,7 +47,7 @@ Probamos y damos compatibilidad oficial de los siguientes IdP. Para el SSO de SA | -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:| | 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" %} +| Okta | {% 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/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 4b55fc72f2..d36d729ba3 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,7 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index fd74f77479..d71f381530 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -22,7 +22,7 @@ shortTitle: Registro de seguridad La bitácora de seguridad lista todas las acciones que se llevaron a cabo en los últimos 90 días. {% data reusables.user_settings.access_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 1. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. ![Pestaña de registro de seguridad](/assets/images/help/settings/audit-log-tab.png) diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index df9cf5e4e1..8c0f496ee8 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -24,7 +24,7 @@ shortTitle: Actualizar las credenciales de acceso 1. Para solicitar una contraseña nueva, visita {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. 2. Ingresa la dirección de correo electrónico asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y luego haz clic en **Enviar correo electrónico para restablecer contraseña.** El correo electrónico se enviará a la dirección de respaldo en caso de que la hayas configurado. ![Diálogo de solicitud de correo electrónico de restablecimiento de contraseña](/assets/images/help/settings/password-recovery-email-request.png) 3. Te enviaremos por correo electrónico un enlace que te permitirá restablecer la contraseña. Debes hacer clic en este enlace dentro de las 3 horas posteriores a haber recibido el correo electrónico. Si no recibiste un correo electrónico de nuestra parte, asegúrate de revisar la carpeta de spam. -4. Si habilitaste la autenticación bifactorial, se te pedirán tus credenciales de 2FA. Teclea tus credenciales bifactoriales o uno de tus códigos de recuperación de 2FA y haz clic en **Verificar**. ![Mensaje de autenticación bifactorial](/assets/images/help/2fa/2fa-password-reset.png) +4. Si habilitaste la autenticación bifactorial, se te pedirán tus credenciales de 2FA. Type your authentication code or one of your recovery codes and click **Verify**. If you have added a security key to your account, you can insert the key and click **Use security key** instead of typing an authentication code. ![Mensaje de autenticación bifactorial](/assets/images/help/2fa/2fa-password-reset.png) 5. Teclea una contraseña nueva, confírmala y haz clic en **Cambiar contraseña**. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)." {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} ![Casilla de recuperación de contraseña](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index da0a24aa20..afa9fa9f67 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -20,7 +20,10 @@ shortTitle: Recuperar una cuenta con 2FA {% warning %} -**Advertencia**: {% data reusables.two_fa.support-may-not-help %} +**Advertencias**: + +- {% data reusables.two_fa.support-may-not-help %} +- {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} @@ -28,12 +31,21 @@ shortTitle: Recuperar una cuenta con 2FA ## Utilizar un código de recuperación de autenticación de dos factores -Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)." +Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/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. Da clic en **Ingresar un código de recuperación de dos factores** debajo de "¿Tienes Problemas?". ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %} -2. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**. ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -3. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**. ![Campo para escribir un código de recuperación y botón Verificar](/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. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**. + + ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} +1. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**. + + ![Campo para escribir un código de recuperación y botón Verificar](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) {% ifversion fpt or ghec %} ## Autenticar con un número de reserva @@ -43,38 +55,52 @@ Si pierdes el acceso a tu app TOTP principal o número de teléfono, puedes prop ## Autenticar con una clave de seguridad -Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". +Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/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 %} ## Autentificarse con un dispositivo verificado, token SSH, o token de acceso personal -Si conoces tu contraseña de {% data variables.product.product_name %} pero no tienes credenciales o códigos de autenticación bifactorial, se te puede enviar una contraseña de única ocasión a tu dirección de correo electrónico verificada para comenzar con el proceso de verificación y volver a obtener acceso a tu cuenta. +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 %} -**Nota**: Por razones de seguridad, recobrar el acceso a tu cuenta autenticándose con una contraseña de una sola ocasión puede demorar de 3 a 5 días hábiles. Las solicitudes adicionales emitidas durante este periodo no se revisarán. +**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time. {% endnote %} Puedes utilizar tus credenciales de autenticación de dos factores para recobrar el acceso a tu cuenta en cualquier momento durante el periodo de espera de 3 a 5 días. -1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación. Si no conoces tu contraseña de {% data variables.product.product_name %}, no podrás generar una contraseña de una sola ocasión. -2. Da clic en **¿No puedes acceder a tu dispositivo de dos factores o a tus códigos de recuperación válidos?** debajo de "¿Tienes Problemas ![Enlace si no tienes tu dispositivo de 2fa o códigos de recuperación](/assets/images/help/2fa/no-access-link.png) -3. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación. ![Botón de restablecimiento de configuración de autenticación](/assets/images/help/2fa/reset-auth-settings.png) -4. Da clic en **Enviar contraseña de una sola vez** para enviarla a todas las direcciones de correo electrónico asociadas con tu cuenta. ![Botón para enviar contraseña de una sola vez](/assets/images/help/2fa/send-one-time-password.png) -5. Debajo de "Contraseña de una sola vez", teclea la contraseña temporal del correo electrónico de recuperación que envió {% data variables.product.prodname_dotcom %}. ![Campo para contraseña de una sola vez](/assets/images/help/2fa/one-time-password-field.png) -6. Da clic en **Verificar dirección de correo electrónico**. -7. Escoge un factor de verificación alterno. +1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación. + + {% warning %} + + **Advertencia**: {% 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. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación. + + ![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. Debajo de "Contraseña de una sola vez", teclea la contraseña temporal del correo electrónico de recuperación que envió {% data variables.product.prodname_dotcom %}. + + ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png) +1. Da clic en **Verificar dirección de correo electrónico**. + + ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png) +1. Escoge un factor de verificación alterno. - Si utilizaste tu dispositivo actual para ingresar en esta cuenta anteriormente y te gustaría utilizarlo para verificación, haz clic en **Verificar con este dispositivo**. - Si has configurado una llave SSH previamente en esta cuenta y quieres utilizarla para verificación, da clic en **Llave SSH**. - - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**. ![Botones de verificación alternativa](/assets/images/help/2fa/alt-verifications.png) -8. Un miembro de {% data variables.contact.github_support %} revisará tu solicitud y te enviará un mensaje de correo electrónico dentro de los siguientes 3 a 5 días. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional. + - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**. + + ![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 three business days. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional. {% endif %} - -## Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" -- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index aad0d4625e..5a6a77e511 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -76,7 +76,7 @@ Al final de cada mes, {% data variables.product.prodname_dotcom %} calcula el co ### Ejemplo de cálculos de costo por minuto -Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %} y permite gastos ilimitados, utilizar 15,000 minutos podría tener un costo extra de almacenamiento y minutos de $56 USD dependiendo de los sistemas operativos que se utilizan para ejecutar jobs. +Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %} y permite gastos ilimitados, utilizar 5,000 minutos podría tener un costo extra de almacenamiento y minutos de $56 USD dependiendo de los sistemas operativos que se utilizan para ejecutar jobs. - 5,000 minutos (3,000 de Linux y 2,000 de Windows) = $56 USD ($24 USD + $32 USD). - 3,000 minutos de Linux a $0.008 USD por minuto = $24 USD. diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md index 6bc71eec09..4193fb6b34 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md @@ -54,10 +54,12 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el {% data reusables.codespaces.exporting-changes %} ## Administrar las notificaciones de uso y límite de gastos -Las notificaciones por correo electrónico se envían a los propietarios de las cuentas y gerentes de facturación cuando el límite de gastos llega a 50%, 75%, y 90% del límite de gastos de tu cuenta. +Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit. Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**. +![Screenshot of the billing email notification settings](/assets/images/help/billing/codespaces-spending-limit-notifications.png) + ## Leer más - "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md index 646ed3ccd5..b4db279d0b 100644 --- a/translations/es-ES/content/code-security/getting-started/github-security-features.md +++ b/translations/es-ES/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/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 25412c70df..d27d4e08ce 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 @@ -36,7 +36,7 @@ You can create a default security policy that will display in any of your organi {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. 1. Click your profile photo, then click **Organizations**. 2. Click **Settings** next to your organization. diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 947533b214..6e7ae7a841 100644 --- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -67,7 +67,14 @@ Before defining a custom pattern, you must ensure that {% data variables.product {% data reusables.repositories.navigate-to-security-and-analysis %} {% data reusables.repositories.navigate-to-ghas-settings %} {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} -{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} +1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**. +1. When the dry run finishes, you'll see a sample of results (up to 1000) from the repository. Review the results and identify any false positive results. + ![Screenshot showing results from dry run](/assets/images/help/repository/secret-scanning-publish-pattern.png) +1. Edit the new custom pattern to fix any problems with the results, then click **Save and dry run** to test your changes. +{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %} +{% endif %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." @@ -116,6 +123,7 @@ Before defining a custom pattern, you must ensure that you enable {% data variab {% data reusables.repositories.navigate-to-ghas-settings %} {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." @@ -139,6 +147,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin {% data reusables.enterprise-accounts.advanced-security-security-features %} 1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index a4c299c3dd..9b97e577a9 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -30,11 +30,17 @@ shortTitle: Use Dependabot with Actions {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently. -For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply: +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply: +{% endif %} - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %} - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available. +{% endif %} + For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). {% ifversion fpt or ghec or ghes > 3.3 %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 8b835ed644..9a41ccbd2a 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -58,7 +58,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md index 6d2de3a534..f0e5dc57aa 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md @@ -46,8 +46,6 @@ There are three reasons why an alert may have no pull request link: If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert. -![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) - ## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %} When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab. diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 2e0ad140d1..4a967cf2fb 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -103,17 +103,17 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the {% ifversion fpt or ghec %} ## Does each dependency vulnerability generate a separate alert? -When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability. +When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png) +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. -When you click to display the alert details, you can see how many vulnerabilities are included in the alert. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png) +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} ## Further reading diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index c2a6b0c128..4029faa7f6 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -25,7 +25,7 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% ifversion fpt or ghec or ghes > 3.2 %} You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." @@ -37,11 +37,30 @@ You can enable automatic security updates for any repository that uses {% data v ## About updates for vulnerable dependencies in your repository {% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. + +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`). + +Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %} {% endif %} ## Viewing and updating vulnerable dependencies -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-dependabot-alerts %} +1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. + ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png) +1. Click the alert that you would like to view. + ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png) +1. Review the details of the vulnerability and, if available, the pull request containing the automated security update. +1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**. + ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) +1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, 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)." +1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. + ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) + +{% elsif ghes = 3.3 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} @@ -54,7 +73,7 @@ You can enable automatic security updates for any repository that uses {% data v 1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) -{% elsif ghes > 3.0 or ghae-issue-4864 %} +{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 9dfc90486b..0956aede41 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -88,7 +88,7 @@ The recommended formats explicitly define which versions are used for all direct | 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`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | -{%- ifversion fpt or ghes > 3.3 %} +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} | 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` | diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md index e34257a9bd..4cd476335b 100644 --- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md +++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md @@ -21,6 +21,8 @@ Puedes reportar a los usuarios que hayan violado las condiciones de servicio o l Si se ha habilitado la capacidad para reportar contenido en un repositorio público, también puedes reportarlo directamente a los mantenedores del mismo. +Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer). + ## Informar un usuario {% data reusables.profile.user_profile_page_navigation %} diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 2d6b79b8a3..1bfa020663 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -293,10 +293,10 @@ El parámetro `redirect_uri` es opcional. Si se deja fuera, GitHub redireccionar El parámetro opcional `redirect_uri` también puede utilizarse para las URL de localhost. Si la aplicación especifica una URL y puerto de localhost, entonces, después de autorizar la aplicación, los usuarios se redireccionarán al puerto y URL proporcionados. La `redirect_uri` no necesita empatar con el puerto especificado en la url de rellamado para la app. -Para la URL de rellamado de `http://localhost/path`, puedes utilizar esta `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 ``` ## Crear tokens múltiples para Apps de OAuth 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 a0c48a6bdd..6a10d1d0c6 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. For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh` +2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, en un script de bash, el habilitar el reenvío de agentes se verá más o menos así: `ssh -A serverA 'bash -s' < deploy.sh` ## Clonado de HTTPS con tokens de OAuth -If you don't want to use SSH keys, you can use HTTPS with OAuth tokens. +Si no quieres utilizar llaves SSH, puedes utilizar HTTPS con tokens de OAuth. #### Pros @@ -57,7 +57,7 @@ If you don't want to use SSH keys, you can use HTTPS with OAuth tokens. #### Configuración -See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). +Consulta [nuestra guía para crear tokens de acceso personal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). ## Llaves de implementación @@ -78,7 +78,7 @@ See [our guide on creating a personal access token](/authentication/keeping-your #### Configuración -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. +1. [Ejecuta el procedimiento `ssh-keygen`][generating-ssh-keys] en tu servidor y recuerda dónde guardaste l par de llaves pública y privada de RSA generado. 2. En la esquina superior derecha de cualquier página de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego da clic en **Tu perfil**. ![Navegación al perfil](/assets/images/profile-page.png) 3. En tu página de perfil, da clic en **Repositorios** y luego en el nombre de tu repositorio. ![Enlace de los repositorios](/assets/images/repos.png) 4. Desde tu repositorio, da clic en **Configuración**. ![Configuración del repositorio](/assets/images/repo-settings.png) 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 index cd5871557a..2b722e32b8 100644 --- 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 @@ -46,10 +46,10 @@ Puedes integrar tu cuenta organizacional o personal en {% data variables.product ### 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. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 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. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 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/getting-started-with-git/managing-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md index 22af3c0bee..f41b494f8a 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -195,6 +195,8 @@ Utiliza el comando `git remote rm` para eliminar una URL remota de tu repositori El comando `git remote rm` toma un argumento: * El nombre de un remoto, por ejemplo `destination` (destino) +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. + ## Ejemplo Estos ejemplos asumen que estás[clonando con HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), lo cual se recomienda. @@ -217,7 +219,7 @@ $ git remote -v {% warning %} -**Nota**: `git remote rm` no elimina el repositorio remoto del servidor. Simplemente, elimina de tu repositorio local el remoto y sus referencias. +**Note**: `git remote rm` does not delete the remote repository from the server. Simplemente, elimina de tu repositorio local el remoto y sus referencias. {% endwarning %} diff --git a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md index 7f19a514f0..9d2a6a3c80 100644 --- a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md @@ -37,10 +37,29 @@ Una licencia de {% data variables.product.prodname_GH_advanced_security %} propo - **Resumen de seguridad** - Revisa la configuración de seguridad y las alertas para una organización e identifica los repositorios que tienen un riesgo mayor. Para obtener más información, consulta la sección "[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)". {% endif %} +{% ifversion fpt or ghec %} +The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. |{% ifversion fpt %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} +|:------------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| +| Escaneo de código | Sí | No | Sí | +| Escaneo de secretos | Yes **(limited functionality only)** | No | Sí | +| Revisión de dependencias | Sí | No | Sí |{% endif %} +| +{% ifversion ghec %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} +|:------------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| +| Escaneo de código | Sí | No | Sí | +| Escaneo de secretos | Yes **(limited functionality only)** | No | Sí | +| Revisión de dependencias | Sí | No | Sí | +| Resumen de seguridad | No | No | Sí | +{% endif %} + +{% endif %} + Para obtener más información sobre las características de {% data variables.product.prodname_advanced_security %} que se encuentran en desarrollo, consulta la sección "[Plan de trabajo de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para obtener un resumen de todas las características de seguridad, consulta la sección "[Características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". {% ifversion fpt or ghec %} -Las características de la {% data variables.product.prodname_GH_advanced_security %} se encuentran habilitadas para todos los repositorios públicos de {% data variables.product.prodname_dotcom_the_website %}. Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %} pueden habilitar estas características adicionalmente para repositorios privados e internos. También tienen acceso a un resumen de seguridad a nivel organizacional. {% ifversion fpt %}Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %} pueden habilitar estas características adicionalmente para repositorios privados e internos. They also have access to an organization-level security overview. {% ifversion fpt %}Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} {% ifversion ghes or ghec %} diff --git a/translations/es-ES/content/github/site-policy/github-community-guidelines.md b/translations/es-ES/content/github/site-policy/github-community-guidelines.md index ca8f4e0b39..0b69762ebc 100644 --- a/translations/es-ES/content/github/site-policy/github-community-guidelines.md +++ b/translations/es-ES/content/github/site-policy/github-community-guidelines.md @@ -22,7 +22,7 @@ El propósito principal de la comunidad de GitHub es colaborar en proyectos de s * **Se cordial y de mentalidad abierta** - Otros colaboradores pueden no tener el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para aportar. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar. -* **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones. +* **Respect each other** - Nothing sabotages healthy conversation like rudeness. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones. Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación. diff --git a/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md b/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md index c82741151b..2a4f9e4f65 100644 --- a/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md +++ b/translations/es-ES/content/github/site-policy/submitting-content-removal-requests.md @@ -23,3 +23,5 @@ La Política de Marcas de GitHub se puede utilizar para informar del contenido q ## [Política de Eliminación de Información Privada de GitHub](/github/site-policy/github-private-information-removal-policy) La Política de Eliminación de Información Privada de GitHub puede utilizarse para reportar datos que sean privados (confidenciales y que posean un riesgo de seguridad), pero que no se protege necesariamente por derechos de autor o comerciales. + +Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer). diff --git a/translations/es-ES/content/graphql/overview/about-the-graphql-api.md b/translations/es-ES/content/graphql/overview/about-the-graphql-api.md index 0219a1d363..c3e47bffc1 100644 --- a/translations/es-ES/content/graphql/overview/about-the-graphql-api.md +++ b/translations/es-ES/content/graphql/overview/about-the-graphql-api.md @@ -12,7 +12,7 @@ topics: ## Resumen -Aquí hay algunos enlaces rápidos para ponerte en marcha con la API de GraphQL v4: +Here are some quick links to get you up and running with the GraphQL API: * [Autenticación](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) * [Terminal raíz](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) @@ -36,9 +36,9 @@ El lenguaje de consulta de [GraphQL](https://graphql.github.io/) es: ## Por qué GitHub utiliza GraphQL -GitHub eligió GraphQL para la API v4 porque ofrece significativamente más flexibilidad para nuestros intregradores. La capacidad de definir precisamente los datos que quieres —y _únicamente_ estos— es una ventaja poderosa sobre las terminales de la API de REST v3. GraphQL te permite reemplazar varias solicitudes de REST con _una sola llamada_ para agregar los datos que especifiques. +GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. GraphQL te permite reemplazar varias solicitudes de REST con _una sola llamada_ para agregar los datos que especifiques. -Para obtener más detalles acerca de por qué GitHub se ha migrado a GraphQL, consulta la[publicación de anuncios del blog](https://githubengineering.com/the-github-graphql-api/). +For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/). ## Acerca de la referencia del modelo de GraphQL 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 index 9b7a3176c5..09ced50e76 100644 --- 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 @@ -19,9 +19,9 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 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) diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index 172b741d51..e08fcb498f 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -40,7 +40,7 @@ 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 or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} {% data reusables.organizations.invite-teams-or-people %} 5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches. diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md index a2e83c9e8c..0912210e99 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -28,9 +28,9 @@ Cuando eliminas a un colaborador de un repositorio en tu organización, el colab {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} -{% elsif ghes < 3.4 or ghae %} +{% else %} {% data reusables.repositories.navigate-to-manage-access %} {% endif %} {% data reusables.organizations.invite-teams-or-people %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md index 2daf35b81f..830749095f 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md @@ -24,7 +24,7 @@ Cuando inhabilitas los tableros de proyecto, ya no ves la información de los ta {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. Decide si deseas inhabilitar los tableros de proyecto que se usan en toda la organización, los tableros de proyecto de los repositorios de la organización, o ambos. Luego, en "Proyectos": diff --git a/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md index f17db4ef13..30bfbd3d25 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -10,12 +10,12 @@ versions: shortTitle: Integrar Jira --- -{% ifversion ghes > 3.3 or ghae-issue-5658 %} +{% ifversion ghes > 3.4 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**. ![Pestaña de aplicaciones OAuth de la barra lateral izquierda](/assets/images/help/organizations/org-oauth-applications-ghe.png) 1. Da clic en **Nueva App de OAuth**. -{% elsif ghes < 3.4 or ghae %} +{% else %} {% data reusables.user_settings.access_settings %} 1. En la barra lateral izquierda en **Organization settings** (Configuraciones de la organización), haz clic en el nombre de tu organización. ![Barra lateral Organization name (Nombre de la organización)](/assets/images/help/settings/organization-settings-from-sidebar.png) 1. En la barra lateral de **Developer settings** (Configuraciones del programador), haz clic en **OAuth applications** (Aplicaciones OAuth). ![Pestaña de aplicaciones OAuth de la barra lateral izquierda](/assets/images/help/organizations/org-oauth-applications-ghe.png) diff --git a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index a6fab36ae1..b7b22e5688 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -15,11 +15,15 @@ topics: shortTitle: Restringir la creación de repositorios --- -Puedes elegir si los miembros pueden crear repositorios en tu organización o no. Si permites que los miembros creen repositorios, puedes elegir qué tipos de repositorios pueden crear.{% ifversion fpt or ghec %} Para permitir que los miembros creen solo repositorios privados, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} Para obtener más información, consulta la sección "[Acerca de los repositorios](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" en la documentación de {% data variables.product.prodname_ghe_cloud %}{% endif %}. +Puedes elegir si los miembros pueden crear repositorios en tu organización o no. {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository. + +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization). +{% endif %} -Los propietarios de la organización siempre pueden crear cualquier tipo de repositorio. {% ifversion ghec or ghae or ghes %} -{% ifversion ghec or ghae %}Los propietarios de empresas{% elsif ghes %}Los administradores de sitio{% endif %} pueden restringir las opciones que tienes disponibles para la política de creación de repositorios de tu organización. {% ifversion ghec or ghes or ghae %} Para obtener más información, consulta la sección "[Restringir la creación de repositorios en tu empresa.](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% endif %}{% endif %} +Enterprise owners can restrict the options you have available for your organization's repository creation policy. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)". +{% endif %} {% warning %} @@ -36,5 +40,12 @@ Los propietarios de la organización siempre pueden crear cualquier tipo de repo ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + + {% note %} + + **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + + {% endnote %} {%- endif %} + 6. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md index 8cb00329e2..4e14267508 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md @@ -57,7 +57,7 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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** @@ -73,7 +73,7 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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** diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 1408b3e897..fb1dedf12d 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -21,7 +21,7 @@ topics: **Note:** When working with pull requests, keep the following in mind: * If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes. -* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. +* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index f9a5eda3a6..6a9ee0d344 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -16,7 +16,7 @@ topics: --- Forking a repository is similar to copying a repository, with two major differences: -* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository. +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. * You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository. {% data reusables.repositories.you-can-fork %} diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md index 79122863a5..7cd3d1e498 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md @@ -22,7 +22,7 @@ Si usas Zendesk para hacer el seguimiento de los tickets informados por el usuar {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. En la barra lateral izquierda, haz clic en **Autolink references** (Referencias de enlace automático). ![Pestaña Autolink references (Referencias de enlace automático) en la barra lateral izquierda](/assets/images/help/repository/autolink-references-tab.png) diff --git a/translations/es-ES/content/rest/reference/billing.md b/translations/es-ES/content/rest/reference/billing.md index 8876b25d3f..fe0cf42be4 100644 --- a/translations/es-ES/content/rest/reference/billing.md +++ b/translations/es-ES/content/rest/reference/billing.md @@ -4,6 +4,7 @@ intro: 'With the Billing API, you can monitor the charges and usage {% data vari versions: fpt: '*' ghec: '*' + ghes: '>=3.4' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md index d903396303..230e3f76b5 100644 --- a/translations/es-ES/content/rest/reference/enterprise-admin.md +++ b/translations/es-ES/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 @@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 %} ## Billing {% for operation in currentRestOperations %} diff --git a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md index 3a5a6c13cc..7e8bf148cb 100644 --- a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md @@ -921,6 +921,9 @@ _Equipos_ {% 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 %} ### Permiso sobre los "ejecutores auto-hospedados" diff --git a/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md b/translations/es-ES/data/reusables/accounts/you-must-know-your-password.md new file mode 100644 index 0000000000..f4795c3909 --- /dev/null +++ b/translations/es-ES/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/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md index d697ff8f8c..d645231024 100644 --- a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md +++ b/translations/es-ES/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/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md index 8669a6386e..9fd6e9c891 100644 --- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md @@ -2,6 +2,8 @@ 1. Debes proporcionar por lo menos el nombre de tu patrón y una expresión regular para el formato de tu patrón secreto. 1. Puedes hacer clic en **{% octicon "chevron-down" aria-label="down" %} Más opciones** para proporcionar otro tipo de contenido circundante o requisitos de coincidencia adicionales para el formato de secreto. 1. Proporciona una secuencia de pruebas de muestra para asegurarte de que tu configuración empate con los patrones que esperas. - + {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} ![Crear un formato de patrón personalizado del {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/secret-scanning-create-custom-pattern.png) -1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}. + {% else %} + ![Crear un formato de patrón personalizado del {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png) + {% endif %} diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md new file mode 100644 index 0000000000..8f4453f9fc --- /dev/null +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md @@ -0,0 +1 @@ +1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern**{% elsif ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. diff --git a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md index 3570a95f99..b657745630 100644 --- a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md +++ b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 1. En la barra lateral de Parámetros, haz clic en **Audit Log (Registro de auditoría)**. ![Parámetros de registro de auditoría de org en barra lateral](/assets/images/help/organizations/org-settings-audit-log.png) diff --git a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md index 5fa3e3d89e..a765d398be 100644 --- a/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md +++ b/translations/es-ES/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 3. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 3. En la barra lateral izquierda, haz clic en **Audit Log (Registro de auditoría)**. ![Pestaña de registro de auditoría](/assets/images/enterprise/site-admin-settings/audit-log-tab.png) diff --git a/translations/es-ES/data/reusables/billing/email-notifications.md b/translations/es-ES/data/reusables/billing/email-notifications.md index d63f90e91c..9ab590e394 100644 --- a/translations/es-ES/data/reusables/billing/email-notifications.md +++ b/translations/es-ES/data/reusables/billing/email-notifications.md @@ -1,3 +1,5 @@ -Las notificaciones por correo electrónico se envían a los propietarios de cuenta y gerentes de facturación cuando los gastos llegan a 50%, 75%, y 90% del uso incluido en tu cuenta y cuando llegan a 50%, 75%, y 90% del límite de gastos de la misma. +Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit. Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**. + +![Screenshot of the billing email notification settings](/assets/images/help/billing/actions-packages-spending-limit-notifications.png) diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md b/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md index 622983c8bc..ea5f3fdc9f 100644 --- a/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md +++ b/translations/es-ES/data/reusables/dependabot/dependabot-secrets-button.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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%} +{% else %} 1. En la barra lateral, haz clic en **{% data variables.product.prodname_dependabot %}**. ![Opción de la barra lateral de secretos del {% data variables.product.prodname_dependabot %}](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png) {% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md index 8c23fd1fdb..313c4302de 100644 --- a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md +++ b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md @@ -5,8 +5,8 @@ permissions: actions: read|write|none checks: read|write|none contents: read|write|none - deployments: read|write|none - id-token: read|write|none + deployments: read|write|none{% ifversion fpt or ghec %} + id-token: read|write|none{% endif %} issues: read|write|none discussions: read|write|none packages: read|write|none diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index 711516a636..984c076d12 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -12,6 +12,6 @@ 2. En la barra lateral izquierda, da clic en **Resumen empresarial**. 3. En la barra lateral de la empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Políticas**.{% endif %} 2. Navega a los ajustes de los "Grupos de ejecutores": - * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec %} y luego en **Grupos de ejecutores** debajo de ella{% endif %}.{% ifversion ghec or ghes or ghae %} - * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion ghec %}, y luego en la pestaña de **Grupos de ejecutores** {% endif %}.{% endif %} + * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %} + * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %} {% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/sidebar-secret.md b/translations/es-ES/data/reusables/github-actions/sidebar-secret.md index a2074b1dd5..0c5a37b1e5 100644 --- a/translations/es-ES/data/reusables/github-actions/sidebar-secret.md +++ b/translations/es-ES/data/reusables/github-actions/sidebar-secret.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral izquierda, haz clic en **Secrets** (Secretos). {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/billing_plans.md b/translations/es-ES/data/reusables/organizations/billing_plans.md index 4debbde75b..60b7acac48 100644 --- a/translations/es-ES/data/reusables/organizations/billing_plans.md +++ b/translations/es-ES/data/reusables/organizations/billing_plans.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral de configuración de tu organización, haz clic en **Planes & facturación**. ![Configuración de facturación](/assets/images/help/billing/settings_organization_billing_plans_tab.png) {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md index f897834b74..982008d449 100644 --- a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md +++ b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %}**. ![Ajustes de las {% data variables.product.prodname_github_apps %}](/assets/images/help/organizations/github-apps-settings-sidebar.png) {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/member-privileges.md b/translations/es-ES/data/reusables/organizations/member-privileges.md index bf781907c4..19bfc3fae5 100644 --- a/translations/es-ES/data/reusables/organizations/member-privileges.md +++ b/translations/es-ES/data/reusables/organizations/member-privileges.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 4. En la barra lateral izquierda, da clic en **Privilegios de los miembros**. ![Opción de privilegios de los miembros en la configuración de la organización](/assets/images/help/organizations/org-settings-member-privileges.png) {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/repository-defaults.md b/translations/es-ES/data/reusables/organizations/repository-defaults.md index b94201e0c1..4353dc97f8 100644 --- a/translations/es-ES/data/reusables/organizations/repository-defaults.md +++ b/translations/es-ES/data/reusables/organizations/repository-defaults.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral izquierda da clic en **Predeterminados del repositorio**. ![Pestaña de predeterminados del repositorio](/assets/images/help/organizations/repo-defaults-tab.png) {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/security-and-analysis.md b/translations/es-ES/data/reusables/organizations/security-and-analysis.md index 3a4f474484..6cfb829475 100644 --- a/translations/es-ES/data/reusables/organizations/security-and-analysis.md +++ b/translations/es-ES/data/reusables/organizations/security-and-analysis.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Pestaña de "Seguridad & análisis"](/assets/images/help/organizations/org-settings-security-and-analysis.png) {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/security.md b/translations/es-ES/data/reusables/organizations/security.md index cbd048958c..c0e89bec63 100644 --- a/translations/es-ES/data/reusables/organizations/security.md +++ b/translations/es-ES/data/reusables/organizations/security.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. En la barra lateral izquierda, da clic en **Seguridad de la organización**. diff --git a/translations/es-ES/data/reusables/organizations/teams_sidebar.md b/translations/es-ES/data/reusables/organizations/teams_sidebar.md index 082f84c9a5..59d119121d 100644 --- a/translations/es-ES/data/reusables/organizations/teams_sidebar.md +++ b/translations/es-ES/data/reusables/organizations/teams_sidebar.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/data/reusables/organizations/verified-domains.md b/translations/es-ES/data/reusables/organizations/verified-domains.md index 7702d9adbc..8a89d9f17c 100644 --- a/translations/es-ES/data/reusables/organizations/verified-domains.md +++ b/translations/es-ES/data/reusables/organizations/verified-domains.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral izquierda, haz clic en **Dominios verificados & aprobados**. ![pestaña de "dominios aprobados & verificados"](/assets/images/help/organizations/verified-domains-button.png) {% endif %} diff --git a/translations/es-ES/data/reusables/pages/sidebar-pages.md b/translations/es-ES/data/reusables/pages/sidebar-pages.md index 5744bf07f6..98cf17070e 100644 --- a/translations/es-ES/data/reusables/pages/sidebar-pages.md +++ b/translations/es-ES/data/reusables/pages/sidebar-pages.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %} +{% ifversion fpt or ghes > 3.4 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. En la barra lateral izquierda, da clic en **Páginas**. ![Pestaña de página en la barra lateral izquierda](/assets/images/help/pages/pages-tab.png) diff --git a/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md index 3dac684983..13dd07c7a0 100644 --- a/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md +++ b/translations/es-ES/data/reusables/repositories/actions-scheduled-workflow-example.md @@ -1,4 +1,4 @@ -Puedes programar un flujo de trabajo para que se ejecute en horarios UTC específicos usando [sintaxis de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Los flujos de trabajo programados se ejecutan en la confirmación más reciente en la rama base o en la rama por defecto. El intervalo más corto en el que puedes programar flujos de trabajo es cada 15 minutos. +Puedes programar un flujo de trabajo para que se ejecute en horarios UTC específicos usando [sintaxis de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Los flujos de trabajo programados se ejecutan en la confirmación más reciente en la rama base o en la rama por defecto. El intervalo más corto en el que puedes programar flujos de trabajo es cada 5 minutos. Este ejemplo activa el flujo de trabajo diariamente a las 5:30 y 17:30 UTC: diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md index 692a3dfcbe..d8fe749521 100644 --- a/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md +++ b/translations/es-ES/data/reusables/repositories/navigate-to-security-and-analysis.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![pestaña de "Seguridad & análisis" en la configuración de repositorio](/assets/images/help/repository/security-and-analysis-tab.png) {% endif %} diff --git a/translations/es-ES/data/reusables/repositories/repository-branches.md b/translations/es-ES/data/reusables/repositories/repository-branches.md index 3d0f401d22..8d0c4d1ece 100644 --- a/translations/es-ES/data/reusables/repositories/repository-branches.md +++ b/translations/es-ES/data/reusables/repositories/repository-branches.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. En el menú izquierdo, da clic en **Ramas**. ![Sub-menú de opciones de repositorio](/assets/images/help/repository/repository-options-branch.png) {% endif %} diff --git a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md index eb6745e85c..93a4ef9a2c 100644 --- a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md +++ b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md b/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md new file mode 100644 index 0000000000..2d3121b0cd --- /dev/null +++ b/translations/es-ES/data/reusables/secret-scanning/beta-dry-runs.md @@ -0,0 +1,6 @@ + +{% note %} + +**Note:** The dry run feature is currently in beta and subject to change. + +{% endnote %} 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 2fe392350c..766d040d6c 100644 --- a/translations/es-ES/data/reusables/user_settings/access_applications.md +++ b/translations/es-ES/data/reusables/user_settings/access_applications.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 6adb2aee80..bd0c4ea2bc 100644 --- a/translations/es-ES/data/reusables/user_settings/account_settings.md +++ b/translations/es-ES/data/reusables/user_settings/account_settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 5b3fb50d32..ef71e7c1e9 100644 --- a/translations/es-ES/data/reusables/user_settings/appearance-settings.md +++ b/translations/es-ES/data/reusables/user_settings/appearance-settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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**. 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 2313297a74..ba2bf33f9f 100644 --- a/translations/es-ES/data/reusables/user_settings/developer_settings.md +++ b/translations/es-ES/data/reusables/user_settings/developer_settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/data/reusables/user_settings/emails.md b/translations/es-ES/data/reusables/user_settings/emails.md index 4701b9b984..88122b4e3b 100644 --- a/translations/es-ES/data/reusables/user_settings/emails.md +++ b/translations/es-ES/data/reusables/user_settings/emails.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/data/reusables/user_settings/organizations.md b/translations/es-ES/data/reusables/user_settings/organizations.md index 0a19839a55..adb1d43dc5 100644 --- a/translations/es-ES/data/reusables/user_settings/organizations.md +++ b/translations/es-ES/data/reusables/user_settings/organizations.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 07a8e9af62..f4567a37a5 100644 --- a/translations/es-ES/data/reusables/user_settings/repo-tab.md +++ b/translations/es-ES/data/reusables/user_settings/repo-tab.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 b47b23628e..ef142883b7 100644 --- a/translations/es-ES/data/reusables/user_settings/saved_replies.md +++ b/translations/es-ES/data/reusables/user_settings/saved_replies.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 c54b43346e..73dd008738 100644 --- a/translations/es-ES/data/reusables/user_settings/security-analysis.md +++ b/translations/es-ES/data/reusables/user_settings/security-analysis.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/data/reusables/user_settings/security.md b/translations/es-ES/data/reusables/user_settings/security.md index ef37e871ec..93faa88e31 100644 --- a/translations/es-ES/data/reusables/user_settings/security.md +++ b/translations/es-ES/data/reusables/user_settings/security.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/es-ES/data/reusables/user_settings/ssh.md b/translations/es-ES/data/reusables/user_settings/ssh.md index 44d51f35ff..da561daf8d 100644 --- a/translations/es-ES/data/reusables/user_settings/ssh.md +++ b/translations/es-ES/data/reusables/user_settings/ssh.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 GitHub's Privacy Statement and users enabling the connection agree to the GitHub's Terms of Service. +- 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..7bfa6662a6 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.4 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..b6d25ac209 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.4 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..6b85b82136 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.4 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-user-account-settings/managing-your-theme-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 21a710c0d3..4e6f9ae2d8 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -22,7 +22,7 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% note %} -**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} 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-java-with-gradle.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 4192124281..9b265177e3 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -69,7 +69,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build ``` @@ -106,7 +106,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Run the Gradle package task - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: -b ci.gradle package ``` @@ -135,7 +135,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build - uses: actions/upload-artifact@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.` および `outputs..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.` and `outputs..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/)アイコンの名前。 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 %} + + ## 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/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index e148e0426a..643ae98159 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -37,20 +37,19 @@ Organization または Enterprise 管理者の場合は、Organization または 単一のリポジトリにセルフホストランナーを追加できます。 セルフホストランナーをユーザのリポジトリに追加するには、リポジトリのオーナーでなければなりません。 Organizationのリポジトリの場合は、Organizationのオーナーであるか、そのリポジトリの管理アクセスを持っていなければなりません。 For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New self-hosted runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. GitHub Insightsの -{% ifversion fpt or ghes > 3.1 or ghae or ghec %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 +{% ifversion ghes > 3.1 or ghae or ghec %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -59,20 +58,19 @@ Organization または Enterprise 管理者の場合は、Organization または セルフホストランナーをOrganizationのレベルで追加し、Organization内の複数のリポジトリのジョブを処理するために使うことができます。 Organizationにセルフホストランナーを追加するには、Organizationのオーナーでなければなりません。 For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. GitHub Insightsの -{% ifversion fpt or ghes > 3.1 or ghae or ghec %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 +{% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %} {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} @@ -88,7 +86,7 @@ Organization または Enterprise 管理者の場合は、Organization または 新しいランナーがデフォルトグループに割り当てられます。 ランナーを登録した後、ランナーのグループを変更できます。 詳しい情報については、「[セルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} セルフホストランナーを Enterprise アカウントに追加するには、Enterprise のオーナーである必要があります。 For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} @@ -97,10 +95,9 @@ Organization または Enterprise 管理者の場合は、Organization または {% data reusables.enterprise-accounts.actions-runners-tab %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} セルフホストランナーを -{% data variables.product.product_location %} の Enterprise レベルで削除するには、サイト管理者である必要があります。 +{% data variables.product.product_location %} の Enterprise レベルでを追加するには、サイト管理者である必要があります。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -108,11 +105,9 @@ Organization または Enterprise 管理者の場合は、Organization または 1. [**Add new**] をクリックし、[**New runner**] をクリックします。 {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} -{% ifversion ghec or ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -{% endif %} ### Enterprise ランナーをリポジトリで利用可能にする 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/managing-access-to-self-hosted-runners-using-groups.md b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index fa8c3eda50..840e62285a 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -46,7 +46,7 @@ Enterprise の管理者が Organization にランナーグループへのアク グループを作成する場合、ランナーグループにアクセスできるリポジトリを定義するポリシーを選択する必要があります。 -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} @@ -61,12 +61,11 @@ Enterprise の管理者が Organization にランナーグループへのアク {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. In the "Self-hosted runners" section, click **Add new**, and then **New group**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**. ![新しいランナーを追加](/assets/images/help/settings/actions-org-add-runner-group.png) 1. ランナーグループの名前を入力し、リポジトリアクセスのポリシーを割り当てます。 @@ -95,7 +94,7 @@ Enterprise は、セルフホストランナーをグループに追加して、 グループを作成するときは、ランナーグループにアクセスできる Organization を定義するポリシーを選択する必要があります。 -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -113,8 +112,7 @@ Enterprise は、セルフホストランナーをグループに追加して、 {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -144,7 +142,7 @@ Enterprise は、セルフホストランナーをグループに追加して、 ## セルフホストランナーグループのアクセスポリシーを変更する ランナーグループのアクセスポリシーを更新したり、ランナーグループの名前を変更したりすることができます。 -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} 1. Modify the access options, or change the runner group name. @@ -158,8 +156,7 @@ Enterprise は、セルフホストランナーをグループに追加して、 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。 {% endwarning %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} @@ -181,17 +178,18 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## セルフホストランナーをグループに移動する If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion ghec or ghes > 3.1 or ghae %} + {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} 1. In the "Runners" list, click the runner that you want to configure. 2. Select the Runner group dropdown menu. 3. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} -1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![ランナーグループのメンバーを表示](/assets/images/help/settings/actions-org-runner-group-members.png) +{% elsif ghae or ghes < 3.4 %} +1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![ランナーグループのメンバーを表示](/assets/images/help/settings/actions-org-runner-group-members.png) 2. セルフホストランナーの横にあるチェックボックスを選択し、[**Move to group**] をクリックして、利用可能な移動先を確認します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. 移動先のグループをクリックして、ランナーを移動します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} + ## セルフホストランナーグループを削除する セルフホストランナーは、グループが削除されると自動的にデフォルトグループに戻ります。 @@ -201,8 +199,7 @@ If you don't specify a runner group during the registration process, your new se 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 2. グループを削除するには、[**Remove group**] をクリックします。 3. 確認プロンプトを確認し、[**Remove this runner group**] をクリックします。 -{% endif %} -{% ifversion ghes < 3.2 or ghae %} +{% elsif ghes < 3.2 %} 1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. グループを削除するには、[**Remove group**] をクリックします。 ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-remove.png) 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 https://github.com/octo-org/octo-repo --pat ghp_abcd1234 +``` + +{% 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/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index a89dc27bce..68f8835ca9 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -30,20 +30,20 @@ shortTitle: Remove self-hosted runners ユーザリポジトリからセルフホストランナーを削除するには、リポジトリのオーナーでなければなりません。 Organizationのリポジトリの場合は、Organizationのオーナーであるか、そのリポジトリの管理アクセスを持っていなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Organizationからのランナーの削除 {% note %} @@ -57,19 +57,20 @@ shortTitle: Remove self-hosted runners Organizationからセルフホストランナーを削除するには、Organizationのオーナーでなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghes > 3.3 or ghec %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% else %} +{% elsif ghes < 3.4 or ghae %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Enterprise からランナーを削除する {% ifversion fpt %} @@ -85,19 +86,17 @@ Organizationからセルフホストランナーを削除するには、Organiza {% endnote %} -{% data reusables.github-actions.self-hosted-runner-reusing %} +To remove a self-hosted runner from an enterprise, you must be an enterprise owner. セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). -{% ifversion ghec %} -セルフホストランナーを Enterprise アカウントから削除するには、Enterprise のオーナーである必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). +{% data reusables.github-actions.self-hosted-runner-reusing %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% elsif ghae or ghes %} -セルフホストランナーを -{% data variables.product.product_location %}, you must be an enterprise owner. セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 +{% elsif ghae or ghes < 3.4 %} {% 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/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index e073245ffb..6a9a9e0bc6 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -19,13 +19,13 @@ shortTitle: Label runners {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} ## カスタムラベルの作成 -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}. 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**. カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} @@ -34,35 +34,38 @@ shortTitle: Label runners カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## セルフホストランナーへのラベルの割り当て -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. ラベルをクリックして、セルフホストランナーに割り当ててください。 {% endif %} + ## カスタムラベルのセルフホストランナーからの削除 -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. 割り当てられているラベルをクリックして、セルフホストランナーから削除してください。 {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## 設定スクリプトを使ったラベルの作成と割り当て セルフホストランナー上の設定スクリプトを使い、カスタムラベルの作成と割り当てを行えます。 たとえば、以下のコマンドは`gpu`というラベルをセルフホストランナーに割り当てます。 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..outputs` | `オブジェクト` | ステップに定義された出力のセット。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions#outputs)」を参照してください。 | +| `steps..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..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..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..outputs.` | `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..f014d3147a 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/expressions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/expressions.md @@ -50,12 +50,12 @@ env: 式の一部として、`boolean`、`null`、`number`、または`string`のデータ型を使用できます。 -| データ型 | リテラル値 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `boolean` | `true` または `false` | -| `null` | `null` | -| `number` | 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. | +| データ型 | リテラル値 | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `boolean` | `true` または `false` | +| `null` | `null` | +| `number` | 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. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. | #### サンプル @@ -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..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
[`jobs..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..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
[`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
[`jobs..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)
[`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)
[`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)
[`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)
[on..paths](/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..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/publishing-packages/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index c383e33d40..eb7b1c82ba 100644 --- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -96,7 +96,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -167,7 +167,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -246,7 +246,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: {% raw %} 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..8394d835de 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 @@ -85,11 +85,14 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau | actions | read/write | none | read | | checks | read/write | none | read | | contents | read/write | read | read | -| deployments | read/write | none | read | -| id-token | read/write | none | read | +| deployments | read/write | none | read |{% ifversion fpt or ghec %} +| id-token | read/write | none | read |{% endif %} | 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/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index 31a6985618..81aa817d3a 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -202,6 +202,10 @@ The same principles described above for using third-party actions also apply to {% data reusables.actions.outside-collaborators-internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." {% endif %} +## Using OpenSSF Scorecards to secure workflows + +[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions. + ## Potential impact of a compromised runner These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. 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..2b9b9f0cfe 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/`. @@ -1101,8 +917,6 @@ on: ```yaml on: push: - types: - - opened branches: - 'releases/**' paths: @@ -1113,7 +927,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 +940,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`): @@ -1144,8 +958,6 @@ on: ```yaml on: push: - types: - - opened branches: - 'releases/**' paths: @@ -1168,7 +980,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`されたときにワークフローを実行できます。 @@ -1180,9 +992,9 @@ on: ### `リリース` -| webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ------------ | -| [`リリース`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | リリースのタグが付いた直近のコミット | リリースのタグ | +| webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ----------------------------------------------- | +| [`リリース`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | リリースのタグが付いた直近のコミット | Tag ref of release `refs/tags/` | {% note %} @@ -1220,7 +1032,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 +1183,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 +1207,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..e47d9c88ba 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` @@ -865,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: @@ -1008,7 +973,7 @@ For more information about branch, tag, and path filter syntax, see "[`on. | `'**'` | すべてのブランチ及びタグ名にマッチします。 これは `branches`あるいは`tags`フィルタを使わない場合のデフォルトの動作です。 | `all/the/branches`

`every/tag` | | `'*feature'` | `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `mona-feature`

`feature`

`ver-10-feature` | | `v2*` | `v2`で始めるブランチ及びタグ名にマッチします。 | `v2`

`v2.0`

`v2.9` | -| `v[12].[0-9]+.[0-9]+` | メジャーバージョンが1もしくは2のすべてのセマンティックバージョニングブランチとタグにマッチします。 | `v1.10.1`

`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`

`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/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 61e750cc30..6afb61b812 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -699,7 +699,7 @@ All Storage tests passed `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}. -For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/). +For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). ### git-import-detect 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/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md index f0c603431c..872ff199c7 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md @@ -35,7 +35,7 @@ High Availability (HA) とクラスタリングはどちらも、障害の原因 ## バックアップとシステム災害復旧 -HAもクラスタリングも、定期的なバックアップに代わるものと考えるべきではありません。 詳しくは、"[ アプライアンスでのバックアップの設定](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)。"を参照してください。 +Neither HA nor Clustering should be considered a replacement for regular backups. 詳しくは、"[ アプライアンスでのバックアップの設定](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)。"を参照してください。 ## モニタリング 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://` 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..b4a52bbdf1 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" %} | | | 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 VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --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 VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER @@ -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 RESOURCE_GROUP -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 | 
git refs delete api
| Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation | | 
git refs update api
| Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation | | 
git repo contents api
| 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 %} | 
merge base into head
| 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)" | | 
pull request branch delete button
| 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)" | | 
pull request branch undo button
| 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..7281ee5a77 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.4 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..d9bf68921b 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.4 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/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 8ca974ea4b..fe97513d90 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -24,7 +24,7 @@ shortTitle: Update access credentials 2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) 3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. -4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**. +4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your authentication code or one of your recovery codes and click **Verify**. If you have added a security key to your account, you can insert the key and click **Use security key** instead of typing an authentication code. ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png) 5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)." {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 29f7fa70f6..cca33717f5 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -20,7 +20,10 @@ shortTitle: Recover an account with 2FA {% warning %} -**警告**: {% data reusables.two_fa.support-may-not-help %} +**警告**: + +- {% data reusables.two_fa.support-may-not-help %} +- {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} @@ -28,12 +31,21 @@ shortTitle: Recover an account with 2FA ## 2 要素認証リカバリコードを使用する -リカバリコードのうち 1 つを使用して、アカウントへのエントリを自動で再取得します。 リカバリコード は、多くの場合、パスワードマネージャまたはご使用のコンピュータのダウンロードフォルダに保存されています。 リカバリコードのデフォルトのファイル名は `github-recovery-codes.txt` です。 リカバリコードの詳しい情報については「[2 要素認証リカバリ方法を設定する](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)」を参照してください。 +リカバリコードのうち 1 つを使用して、アカウントへのエントリを自動で再取得します。 リカバリコード は、多くの場合、パスワードマネージャまたはご使用のコンピュータのダウンロードフォルダに保存されています。 リカバリコードのデフォルトのファイル名は `github-recovery-codes.txt` です。 リカバリコードの詳しい情報については「[2 要素認証リカバリ方法を設定する](/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. [Having Problems?] の下で、[**Enter a two-factor recovery code**] をクリックします。 ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %} -2. [2FA] ページで、[Don't have your phone?] の下にある [**Enter a two-factor recovery code**] をクリックします。 ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -3. リカバリコードを 1 つ入力して、[**Verify**] をクリックします。 ![リカバリコードを入力するフィールドおよび [Verify] ボタン](/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. [2FA] ページで、[Don't have your phone?] の下にある [**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. リカバリコードを 1 つ入力して、[**Verify**] をクリックします。 + + ![リカバリコードを入力するフィールドおよび [Verify] ボタン](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) {% ifversion fpt or ghec %} ## フォールバック番号による認証 @@ -43,38 +55,52 @@ shortTitle: Recover an account with 2FA ## セキュリティキーによる認証 -セキュリティキーを使用して 2 要素認証を設定した場合は、セキュリティキーをセカンダリ認証方式として使用すると、アカウントへのアクセスを自動で再取得できます。 詳しい情報については、「[2 要素認証を設定する](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。 +セキュリティキーを使用して 2 要素認証を設定した場合は、セキュリティキーをセカンダリ認証方式として使用すると、アカウントへのアクセスを自動で再取得できます。 詳しい情報については、「[2 要素認証を設定する](/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 %} ## 検証済みのデバイス、SSHトークン、または個人アクセストークンを使用した認証 -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 %} -**注釈**: セキュリティ上の理由から、ワンタイムパスワードで認証してアカウントへのアクセスを回復するには、3〜5 営業日かかる場合があります。 この間に送信された追加のリクエストはレビューされません。 +**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time. {% endnote %} 2要素認証の認証情報または 2 要素認証のリカバリコードを使用して、3〜5 日間の待機期間中にいつでもアカウントへのアクセスを回復できます。 -1. 認証を求めるためにユーザ名とパスワードを入力してください。 If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password. -2. [Having Problems?] の下で、[**Can't access your two factor device or valid recovery codes?**] をクリックします。 ![2fa デバイスまたはリカバリコードがない場合のリンク](/assets/images/help/2fa/no-access-link.png) -3. [**I understand, get started**] をクリックして、認証設定のリセットをリクエストします。 ![認証設定のリセットボタン](/assets/images/help/2fa/reset-auth-settings.png) -4. [**Send one-time password**] をクリックして、アカウントに関連付けられているすべてのメールアドレスにワンタイムパスワードを送信します。 ![ワンタイムパスワードの送信ボタン](/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. ![ワンタイムパスワードフィールド](/assets/images/help/2fa/one-time-password-field.png) -6. [**Verify email address**] をクリックします。 -7. 別の検証要素を選択します。 +1. 認証を求めるためにユーザ名とパスワードを入力してください。 + + {% 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. [**I understand, get started**] をクリックして、認証設定のリセットをリクエストします。 + + ![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. [**Verify email address**] をクリックします。 + + ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png) +1. 別の検証要素を選択します。 - 以前に現在のデバイスを使用してこのアカウントにログインしたことがあり、検証にそのデバイスを使用する場合は、[**Verify with this device**] をクリックします。 - - 以前にこのアカウントで SSH キーを設定しており、検証にその SSH キーを使用する場合は、[** SSH key**] をクリックします。 - - 以前に個人アクセストークンを設定しており、検証にその個人アクセストークンを使用する場合は、[**Personal access token**] をクリックします。 ![代替検証ボタン](/assets/images/help/2fa/alt-verifications.png) -8. {% data variables.contact.github_support %}のメンバーがリクエストをレビューし、3〜5 営業日以内にメールでお知らせします。 リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。 + - 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**. + + ![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 three business days. リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。 {% endif %} - -## 参考リンク - -- [2 要素認証について](/articles/about-two-factor-authentication) -- [2 要素認証の設定](/articles/configuring-two-factor-authentication) -- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods) -- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication) 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-github-actions/about-billing-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index a8cc636585..cd495e0341 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -76,7 +76,7 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e ### Sample minutes cost calculation -For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. +For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. - 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD). - 3,000 Linux minutes at $0.008 USD per minute = $24 USD. 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 --- - {% 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 --- - + {% 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 --- - + {% 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 --- - + 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 --- - {% 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 --- - {% 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 --- - + {% 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 --- - {% 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 --- - 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 --- - + {% 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 --- - 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 --- - + {% 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 --- - + {% 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 <database> --format=<format> \ | Option | Required | Usage | |--------|:--------:|-----| | `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. | -| `` | | 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 `//codeql/qlpacks/codeql-/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 %}. +| `` | | 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 `//qlpacks/codeql/-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 %}. | `--format` | {% 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)." | `--output` | {% 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 %} | `--sarif-category` | {% 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 --- - + {% 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 --- - 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 --- - + {% 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 --- - {% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} diff --git a/translations/ja-JP/content/code-security/getting-started/github-security-features.md b/translations/ja-JP/content/code-security/getting-started/github-security-features.md index 20286894cf..cb381c3d6c 100644 --- a/translations/ja-JP/content/code-security/getting-started/github-security-features.md +++ b/translations/ja-JP/content/code-security/getting-started/github-security-features.md @@ -83,6 +83,12 @@ Automatically detect tokens or credentials that have been checked into a reposit Pull Requestをマージする前に、依存関係に対する変更の影響を詳細に示し、脆弱なバージョンがあればその詳細を確認できます。 詳しい情報については「[依存関係のレビュー](/code-security/supply-chain-security/about-dependency-review)」を参照してください。 {% endif %} +{% ifversion ghec or ghes > 3.1 %} +### セキュリティの概要 + +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 %} + ## 参考リンク - "[{% data variables.product.prodname_dotcom %}の製品](/github/getting-started-with-github/githubs-products)" - 「[{% data variables.product.prodname_dotcom %}言語サポート](/github/getting-started-with-github/github-language-support)」 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..d27d4e08ce 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 @@ -36,7 +36,7 @@ You can create a default security policy that will display in any of your organi {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. 1. Click your profile photo, then click **Organizations**. 2. Click **Settings** next to your organization. @@ -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. | ------------------------- | ------------------------------ | | topic:TOPIC-NAME | *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..08083383df 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 %} @@ -30,11 +30,17 @@ shortTitle: Use Dependabot with actions {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently. -`pull_request`、`pull_request_review`、`pull_request_review_comment`、`push`イベントを使って {% data variables.product.prodname_dependabot %}によって開始されたワークフロー（`github.actor == "dependabot[bot]"`）については、以下の制限が適用されます。 +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply: +{% endif %} - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %} - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available. +{% endif %} + 詳しい情報については[GitHub Actionsとワークフローをセキュアに保つ: pwnリクエストの防止](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)を参照してください。 {% ifversion fpt or ghec or ghes > 3.3 %} @@ -66,7 +72,7 @@ For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/act ### Accessing secrets -When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. 詳しい情報については「[Dependabotの暗号化されたシークレットの管理](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)」を参照してください。 +When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)". {% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)." 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/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 8b835ed644..9a41ccbd2a 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -58,7 +58,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md index d06c5b70bb..f53f1f19ab 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md @@ -46,8 +46,6 @@ topics: エラーによって {% data variables.product.prodname_dependabot %} によるプルリクエストの作成がブロックされた場合は、アラートをクリックしてエラーの詳細を表示できます。 -![プルリクエストの作成をブロックしたエラーを示す {% data variables.product.prodname_dependabot %} アラート](/assets/images/help/dependabot/dependabot-security-update-error.png) - ## {% data variables.product.prodname_dependabot_version_updates %} でエラーを調査する {% data variables.product.prodname_dependabot %} がエコシステムの依存関係を更新するためのプルリクエストの作成をブロックされると、マニフェストファイルにエラーアイコンを投稿します。 {% data variables.product.prodname_dependabot %} によって管理されるマニフェストファイルは、[{% data variables.product.prodname_dependabot %}] タブに一覧表示されます。 このタブにアクセスするには、リポジトリの [**Insights**] タブで [**Dependency graph**] をクリックし、[**{% data variables.product.prodname_dependabot %}**] タブをクリックします。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 2e0ad140d1..4a967cf2fb 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -103,17 +103,17 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the {% ifversion fpt or ghec %} ## Does each dependency vulnerability generate a separate alert? -When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability. +When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png) +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. -When you click to display the alert details, you can see how many vulnerabilities are included in the alert. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png) +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} ## Further reading diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 17020fe9ea..2dc4bb9fc5 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -25,7 +25,7 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 {% ifversion fpt or ghec or ghes > 3.2 %} {% data variables.product.prodname_dependabot_alerts %} と依存関係グラフを使用するリポジトリの自動セキュリティ更新を有効にすることができます。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)」を参照してください。 @@ -37,11 +37,26 @@ Your repository's {% data variables.product.prodname_dependabot_alerts %} tab l ## リポジトリ内の脆弱性のある依存関係の更新について コードベースが既知の脆弱性のある依存関係を使用していることを検出すると、{% data variables.product.product_name %} は {% data variables.product.prodname_dependabot_alerts %} を生成します。 {% data variables.product.prodname_dependabot_security_updates %} が有効になっているリポジトリの場合、{% data variables.product.product_name %} がデフォルトのブランチで脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} はそれを修正するためのプルリクエストを作成します。 Pull Requestは、脆弱性を回避するために必要最低限の安全なバージョンに依存関係をアップグレードします。 + +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`). + +Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %} {% endif %} ## 脆弱性のある依存関係を表示して更新する -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-dependabot-alerts %} +1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png) +1. Click the alert that you would like to view. ![アラートリストで選択されたアラート](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png) +1. 脆弱性の詳細を確認し、可能な場合は、自動セキュリティアップデートを含むプルリクエストを確認します。 +1. 必要に応じて、アラートに対する {% data variables.product.prodname_dependabot_security_updates %} アップデートがまだ入手できない場合、脆弱性を解決するプルリクエストを作成するには、[**Create {% data variables.product.prodname_dependabot %} security update**] をクリックします。 ![{% data variables.product.prodname_dependabot %} セキュリティアップデートボタンを作成](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) +1. 依存関係を更新して脆弱性を解決する準備ができたら、プルリクエストをマージしてください。 {% data variables.product.prodname_dependabot %} によって発行される各プルリクエストには、{% data variables.product.prodname_dependabot %} の制御に使用できるコマンドの情報が含まれています。 詳しい情報については、「[依存関係の更新に関するプルリクエストを管理する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands) 」を参照してください。 +1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. ![[Dismiss] ドロップダウンでアラートを却下する理由を選択する](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) + +{% elsif ghes = 3.3 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} @@ -51,7 +66,7 @@ Your repository's {% data variables.product.prodname_dependabot_alerts %} tab l 1. 依存関係を更新して脆弱性を解決する準備ができたら、プルリクエストをマージしてください。 {% data variables.product.prodname_dependabot %} によって発行される各プルリクエストには、{% data variables.product.prodname_dependabot %} の制御に使用できるコマンドの情報が含まれています。 詳しい情報については、「[依存関係の更新に関するプルリクエストを管理する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands) 」を参照してください。 1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. ![[Dismiss] ドロップダウンでアラートを却下する理由を選択する](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) -{% elsif ghes > 3.0 or ghae-issue-4864 %} +{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} @@ -64,7 +79,7 @@ Your repository's {% data variables.product.prodname_dependabot_alerts %} tab l {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %} 1. 詳細な情報を表示する脆弱性のある依存関係のバージョン番号をクリックしてください。 ![脆弱性のある依存関係の詳細情報](/assets/images/enterprise/3.0/dependabot-alert-info.png) -1. 脆弱性の詳細をレビューして、更新する必要があるかを判断してください。 依存関係のセキュアなバージョンへマニフェストあるいはロックファイルを更新するPull Requestをマージすると、アラートは解決されます。 +1. 脆弱性の詳細をレビューし、依存関係を更新する必要があるかを判断してください。 依存関係のセキュアなバージョンへマニフェストあるいはロックファイルを更新するPull Requestをマージすると、アラートは解決されます。 1. **Dependencies（依存関係）**タブの上部のバナーは、脆弱性のある依存関係がすべて解決されるか、そのバナーを閉じるまで表示されます。 バナーの右上にある**Dismiss（却下）**をクリックして、アラートを却下する理由を選択してください。 ![セキュリティバナーを閉じる](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png) {% endif %} 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..0956aede41 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[1] | 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`* | -{%- ifversion fpt or ghes > 3.3 %} +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} | 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..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 = *_CONTAINER_REGISTRY_USER = -*_container_REGISTRY_PASSWORD = +*_CONTAINER_REGISTRY_PASSWORD = ``` 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 = *_CONTAINER_REGISTRY_USER = AWS -*_container_REGISTRY_PASSWORD = +*_CONTAINER_REGISTRY_PASSWORD = ``` 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/reporting-abuse-or-spam.md b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md index 89bcf4cde1..74c583d24e 100644 --- a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md +++ b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md @@ -21,6 +21,8 @@ You can report users that have violated {% data variables.product.prodname_dotco If reported content is enabled for a public repository, you can also report content directly to repository maintainers. +Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer). + ## Reporting a user {% data reusables.profile.user_profile_page_navigation %} 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 +--- + + +{% 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/building-oauth-apps/authorizing-oauth-apps.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index d390f9c8e5..2779cd7e7f 100644 --- a/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/ja-JP/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/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 `というコマンドは、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//upgrade// ``` 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..00820b68b5 --- /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, discussions, 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, discussions, releases, 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/getting-started-with-git/managing-remote-repositories.md b/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md index f90be1a859..6be7725c53 100644 --- a/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -195,6 +195,8 @@ Use the `git remote rm` command to remove a remote URL from your repository. `git remote rm` コマンドは 1 つの引数を取ります: * リモート名 (`destination` など) +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. + ## サンプル 次の例は (推奨されるとおり) [HTTPS を使用してクローンを作成](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)したと想定しています。 @@ -217,7 +219,7 @@ $ git remote -v {% warning %} -**メモ**: `git remote rm` はリモートリポジトリをサーバから削除するわけではありません。 リモートとその参照をローカルリポジトリから削除するだけです。 +**Note**: `git remote rm` does not delete the remote repository from the server. リモートとその参照をローカルリポジトリから削除するだけです。 {% endwarning %} 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/learning-about-github/about-github-advanced-security.md b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md index c8b27e59df..0231b06a5a 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md @@ -36,10 +36,31 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **Security overview** - Review the security configuration and alerts for an 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 %} +{% ifversion fpt or ghec %} +The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. + +{% ifversion fpt %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | +| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | +| Code scanning | Yes | No | Yes | +| Secret scanning | Yes **(limited functionality only)** | No | Yes | +| Dependency review | Yes | No | Yes | +{% endif %} +{% ifversion ghec %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | +| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | +| Code scanning | Yes | No | Yes | +| Secret scanning | Yes **(limited functionality only)** | No | Yes | +| Dependency review | Yes | No | Yes | +| Security overview | No | No | Yes | +{% endif %} + +{% endif %} + For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion fpt or ghec %} -{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} {% ifversion ghes or ghec %} @@ -59,9 +80,9 @@ The site administrator must enable {% data variables.product.prodname_advanced_s Once your system is set up, you can enable and disable these features at the organization or repository level. {%- elsif ghec %} -For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. +For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {%- elsif ghae %} You can enable and disable these features at the organization or repository level. 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: Ctrl+K or Ctrl+Alt+K - Mac: Command+K or Command+Option+K +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 Ctrl+Shift+K (Windows and Linux) or Command+Shift+K (Mac) to open the command palette in command mode. If you already have the command palette open, press > 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 Ctrl+Shift+K (Windows and Linux) or Command+Shift+K (Mac). If you already have the command palette open, press > 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 Enter 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: Esc or Ctrl+K (Windows and Linux) Command+K (Mac) - Command mode: Esc or Ctrl+Shift+K (Windows and Linux) Command+Shift+K (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 | キーボードショートカット | 説明 | | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 | -| g n | 通知に移動します。 詳しい情報については、{% 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 %}」を参照してください。 | -| esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | +| S または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 | +| G N | 通知に移動します。 詳しい情報については、{% 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 %}」を参照してください。 | +| Esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | {% if command-palette %} -controlk or commandk | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Ctlaltk or ⌘optionk. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +Command+K (Mac) or
Ctrl+K (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Command+Option+K or Ctrl+Alt+K. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} ## リポジトリ | キーボードショートカット | 説明 | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | [**Code**] タブに移動します | -| g i | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 | -| g p | [**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 %} -| g a | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %} -| g b | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | -| g w | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %} -| g g | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %} +| G C | [**Code**] タブに移動します | +| G I | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 | +| G P | [**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 %} +| G A | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %} +| G B | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | +| G W | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %} +| G G | 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 %} -| から実行されます。 | 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 %} -| control b または command b | 太字テキストの Markdown 書式を挿入します | -| control i または command i | イタリック体のテキストの Markdown 書式を挿入します | -| control k または command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %} -| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | -| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list | -| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %} -| e | [**Edit file**] タブでソースコードファイルを開きます | -| control f または command f | ファイルエディタで検索を開始します | -| control g または command g | 次を検索します | -| control shift g or command shift g | 前を検索します | -| control shift f or command option f | 置き換えます | -| control shift r or command shift option f | すべてを置き換えます | -| alt g | 行にジャンプします | -| control z または command z | 元に戻します | -| control y または command y | やり直します | -| command shift p | [**Edit file**] タブと [**Preview changes**] タブを切り替えます | -| control s or command s | Write a commit message | +| キーボードショートカット | 説明 | +| ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} +| から実行されます。 | 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 %} +| Command+B (Mac) or
Ctrl+B (Windows/Linux) | 太字テキストの Markdown 書式を挿入します | +| Command+I (Mac) or
Ctrl+I (Windows/Linux) | イタリック体のテキストの Markdown 書式を挿入します | +| Command+K (Mac) or
Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %} +| Command+Shift+7 (Mac) or
Ctrl+Shift+7 (Windows/Linux) | Inserts Markdown formatting for an ordered list | +| Command+Shift+8 (Mac) or
Ctrl+Shift+8 (Windows/Linux) | Inserts Markdown formatting for an unordered list | +| Command+Shift+. (Mac) or
Ctrl+Shift+. (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %} +| E | [**Edit file**] タブでソースコードファイルを開きます | +| Command+F (Mac) or
Ctrl+F (Windows/Linux) | ファイルエディタで検索を開始します | +| Command+G (Mac) or
Ctrl+G (Windows/Linux) | 次を検索します | +| Command+Shift+G (Mac) or
Ctrl+Shift+G (Windows/Linux) | 前を検索します | +| Command+Option+F (Mac) or
Ctrl+Shift+F (Windows/Linux) | 置き換えます | +| Command+Shift+Option+F (Mac) or
Ctrl+Shift+R (Windows/Linux) | すべてを置き換えます | +| Alt+G | 行にジャンプします | +| Command+Z (Mac) or
Ctrl+Z (Windows/Linux) | 元に戻します | +| Command+Y (Mac) or
Ctrl+Y (Windows/Linux) | やり直します | +| Command+Shift+P | [**Edit file**] タブと [**Preview changes**] タブを切り替えます | +| Command+S (Mac) or
Ctrl+S (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 | キーボードショートカット | 説明 | | ------------ | ------------------------------------------------------------------------------------------------------------------ | -| t | ファイルファインダーを起動します | -| l | コード内の行にジャンプします | -| w | 新しいブランチまたはタグに切り替えます | -| y | URL を正規の形式に展開します。 詳細は「[ファイルにパーマリンクを張る](/articles/getting-permanent-links-to-files)」を参照してください。 | -| i | 差分に関するコメントを表示または非表示にします。 詳細は「[プルリクエストの差分についてコメントする](/articles/commenting-on-the-diff-of-a-pull-request)」を参照してください。 | -| a | diff の注釈を表示または非表示にします | -| b | blame ビューを開きます。 詳細は「[ファイル内の変更を追跡する](/articles/tracing-changes-in-a-file)」を参照してください。 | +| T | ファイルファインダーを起動します | +| L | コード内の行にジャンプします | +| W | 新しいブランチまたはタグに切り替えます | +| Y | URL を正規の形式に展開します。 詳細は「[ファイルにパーマリンクを張る](/articles/getting-permanent-links-to-files)」を参照してください。 | +| I | 差分に関するコメントを表示または非表示にします。 詳細は「[プルリクエストの差分についてコメントする](/articles/commenting-on-the-diff-of-a-pull-request)」を参照してください。 | +| A | diff の注釈を表示または非表示にします | +| B | blame ビューを開きます。 詳細は「[ファイル内の変更を追跡する](/articles/tracing-changes-in-a-file)」を参照してください。 | ## コメント -| キーボードショートカット | 説明 | -| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| control b または command b | 太字テキストの Markdown 書式を挿入します | -| control i または command i | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %} -| control e or command e | Inserts Markdown formatting for code or a command within a line{% endif %} -| control k または command k | リンクを作成するための Markdown 書式を挿入します | -| control shift p または command shift p | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | -| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} -| control enter or command enter | コメントをサブミットします | -| control .、次に control [返信テンプレート番号] | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} -| control g または command g | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 +| キーボードショートカット | 説明 | +| ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Command+B (Mac) or
Ctrl+B (Windows/Linux) | 太字テキストの Markdown 書式を挿入します | +| Command+I (Mac) or
Ctrl+I (Windows/Linux) | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %} +| Command+E (Mac) or
Ctrl+E (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %} +| Command+K (Mac) or
Ctrl+K (Windows/Linux) | リンクを作成するための Markdown 書式を挿入します | +| Command+Shift+P (Mac) or
Ctrl+Shift+P (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %} +| Command+Shift+V (Mac) or
Ctrl+Shift+V (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +| Command+Shift+7 (Mac) or
Ctrl+Shift+7 (Windows/Linux) | Inserts Markdown formatting for an ordered list | +| Command+Shift+8 (Mac) or
Ctrl+Shift+8 (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %} +| Command+Enter (Mac) or
Ctrl+Enter (Windows/Linux) | コメントをサブミットします | +| Ctrl+. and then Ctrl+[saved reply number] | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +| Command+Shift+. (Mac) or
Ctrl+Shift+. (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} +| Command+G (Mac) or
Ctrl+G (Windows/Linux) | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 {% endif %} -| r | 返信で選択したテキストを引用します。 詳細は「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」を参照してください。 | +| R | 返信で選択したテキストを引用します。 For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | + ## Issue およびプルリクエストのリスト -| キーボードショートカット | 説明 | -| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Issueの作成 | -| control / または command / | 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)."| | -| u | 作者によりフィルタリングします | -| l | ラベルによりフィルタリグするか、ラベルを編集します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。 | -| alt およびクリック | ラベルによりフィルタリングすると同時に、ラベルを除外します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。 | -| m | マイルストーンによりフィルタリングするか、 マイルストーンを編集します。 詳細は「[Issue およびプルリクエストをマイルストーンでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。 | -| a | アサインされた人によりフィルタリングするか、 アサインされた人を編集します。 詳細は「[Issue およびプルリクエストをアサインされた人でフィルタリングする](/articles/filtering-issues-and-pull-requests-by-assignees)」を参照してください。 | -| o または enter | Issue を開きます | +| キーボードショートカット | 説明 | +| ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | Issueの作成 | +| Command+/ (Mac) or
Ctrl+/ (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)."| | +| U | 作者によりフィルタリングします | +| L | ラベルによりフィルタリグするか、ラベルを編集します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。 | +| Alt およびクリック | ラベルによりフィルタリングすると同時に、ラベルを除外します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。 | +| M | マイルストーンによりフィルタリングするか、 マイルストーンを編集します。 詳細は「[Issue およびプルリクエストをマイルストーンでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。 | +| A | アサインされた人によりフィルタリングするか、 アサインされた人を編集します。 詳細は「[Issue およびプルリクエストをアサインされた人でフィルタリングする](/articles/filtering-issues-and-pull-requests-by-assignees)」を参照してください。 | +| O or Enter | Issue を開きます | ## Issue およびプルリクエスト -| キーボードショートカット | 説明 | -| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| q | レビュー担当者にリクエストします。 詳細は「[Pull Request レビューをリクエストする](/articles/requesting-a-pull-request-review/)」を参照してください。 | -| m | マイルストーンを設定します。 詳細は「[Issue およびプルリクエストにマイルストーンを関連付ける](/articles/associating-milestones-with-issues-and-pull-requests)」を参照してください。 | -| l | ラベルを適用します。 詳細は「[Issue およびプルリクエストにラベルを適用する](/articles/applying-labels-to-issues-and-pull-requests)」を参照してください。 | -| a | アサインされた人を設定します。 詳細は「[{% data variables.product.company_short %} の他のユーザに Issue およびプルリクエストをアサインする](/articles/assigning-issues-and-pull-requests-to-other-github-users/)」を参照してください。 | -| cmd + shift + p または control + shift + p | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %} -| alt およびクリック | When creating an issue from a task list, open the new issue form in the current tab by holding alt 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)を参照してください。 | -| shift and click | When creating an issue from a task list, open the new issue form in a new tab by holding shift 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)を参照してください。 | -| command or control + shift and click | When creating an issue from a task list, open the new issue form in the new window by holding command or control + shift 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 %} +| キーボードショートカット | 説明 | +| ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Q | レビュー担当者にリクエストします。 詳細は「[Pull Request レビューをリクエストする](/articles/requesting-a-pull-request-review/)」を参照してください。 | +| M | マイルストーンを設定します。 詳細は「[Issue およびプルリクエストにマイルストーンを関連付ける](/articles/associating-milestones-with-issues-and-pull-requests)」を参照してください。 | +| L | ラベルを適用します。 詳細は「[Issue およびプルリクエストにラベルを適用する](/articles/applying-labels-to-issues-and-pull-requests)」を参照してください。 | +| A | アサインされた人を設定します。 詳細は「[{% data variables.product.company_short %} の他のユーザに Issue およびプルリクエストをアサインする](/articles/assigning-issues-and-pull-requests-to-other-github-users/)」を参照してください。 | +| Command+Shift+P (Mac) or
Ctrl+Shift+P (Windows/Linux) | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %} +| Alt およびクリック | When creating an issue from a task list, open the new issue form in the current tab by holding Alt 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)を参照してください。 | +| Shift and click | When creating an issue from a task list, open the new issue form in a new tab by holding Shift 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)を参照してください。 | +| Command and click (Mac) or
Ctrl+Shift and click (Windows/Linux) | When creating an issue from a task list, open the new issue form in the new window by holding Command or Ctrl+Shift 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 %} ## プルリクエストの変更 -| キーボードショートカット | 説明 | -| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | プルリクエスト内のコミットのリストを開きます | -| t | プルリクエストで変更されたファイルのリストを開きます | -| j | リストで選択を下に移動します | -| k | リストで選択を上に移動します | -| cmd + shift + enter | プルリクエストの差分にコメントを 1 つ追加します | -| alt およびクリック | `alt` を押しながら、[**Show outdated**] または [**Hide outdated**] をクリックして、期限切れのレビューコメントをすべて折りたたむか展開するかを切り替えます。|{% ifversion fpt or ghes or ghae or ghec %} -| クリック後、shift およびクリック | プルリクエストの複数行にコメントするには、行番号をクリックし、shift を押したまま、別の行番号をクリックします。 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。 +| キーボードショートカット | 説明 | +| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | プルリクエスト内のコミットのリストを開きます | +| T | プルリクエストで変更されたファイルのリストを開きます | +| J | リストで選択を下に移動します | +| K | リストで選択を上に移動します | +| Command+Shift+Enter | プルリクエストの差分にコメントを 1 つ追加します | +| Alt およびクリック | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %} +| Click, then Shift and click | Comment on multiple lines of a pull request by clicking a line number, holding Shift, 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 %} ## プロジェクトボード ### 列を移動する -| キーボードショートカット | 説明 | -| ------------------------------------------------------------------------------------------------------- | ----------------- | -| enter または space | フォーカスされた列を動かし始めます | -| escape | 進行中の移動をキャンセルします | -| enter | 進行中の移動を完了します | -| ← または h | 左に列を移動します | -| command + ← または command + h または control + ← または control + h | 左端に列を移動します | -| → または l | 右に列を移動します | -| command + → または command + l または control + → または control + l | 右端に列を移動します | +| キーボードショートカット | 説明 | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | +| Enter or Space | フォーカスされた列を動かし始めます | +| Esc | 進行中の移動をキャンセルします | +| Enter | 進行中の移動を完了します | +| ← or H | 左に列を移動します | +| Command+← or Command+H (Mac) or
Ctrl+← or Ctrl+H (Windows/Linux) | 左端に列を移動します | +| → or L | 右に列を移動します | +| Command+→ or Command+L (Mac) or
Ctrl+→ or Ctrl+L (Windows/Linux) | 右端に列を移動します | ### カードを移動する -| キーボードショートカット | 説明 | -| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | -| enter または space | フォーカスされたカードを動かし始めます | -| escape | 進行中の移動をキャンセルします | -| enter | 進行中の移動を完了します | -| ↓ または j | カードを下に移動します | -| command + ↓ または command + j または control + ↓ または control + j | カードを列の一番下に移動します | -| ↑ または k | カードを上に移動します | -| command + ↑ または command + k または control + ↑ または control + k | カードを列の一番上に移動します | -| ← または h | カードを左側の列の一番下に移動します | -| shift + ← または shift + h | カードを左側の列の一番上に移動します | -| command + ← または command + h または control + ← または control + h | カードを一番左の列の一番下に移動します | -| command + shift + ← または command + shift + h または control + shift + ← または control + shift + h | カードを一番左の列の一番上に移動します | -| → | カードを右側の列の一番下に移動します | -| shift + → または shift + l | カードを右側の列の一番上に移動します | -| command + → または command + l または control + → または control + l | カードを一番右の列の一番下に移動します | -| command + shift + → または command + shift + l または control + shift + → または control + shift + l | カードを一番右の列の一番下に移動します | +| キーボードショートカット | 説明 | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | +| Enter or Space | フォーカスされたカードを動かし始めます | +| Esc | 進行中の移動をキャンセルします | +| Enter | 進行中の移動を完了します | +| ↓ or J | カードを下に移動します | +| Command+↓ or Command+J (Mac) or
Ctrl+↓ or Ctrl+J (Windows/Linux) | カードを列の一番下に移動します | +| ↑ or K | カードを上に移動します | +| Command+↑ or Command+K (Mac) or
Ctrl+↑ or Ctrl+K (Windows/Linux) | カードを列の一番上に移動します | +| ← or H | カードを左側の列の一番下に移動します | +| Shift+← or Shift+H | カードを左側の列の一番上に移動します | +| Command+← or Command+H (Mac) or
Ctrl+← or Ctrl+H (Windows/Linux) | カードを一番左の列の一番下に移動します | +| Command+Shift+← or Command+Shift+H (Mac) or
Ctrl+Shift+← or Ctrl+Shift+H (Windows/Linux) | カードを一番左の列の一番上に移動します | +| → | カードを右側の列の一番下に移動します | +| Shift+→ or Shift+L | カードを右側の列の一番上に移動します | +| Command+→ or Command+L (Mac) or
Ctrl+→ or Ctrl+L (Windows/Linux) | カードを一番右の列の一番下に移動します | +| Command+Shift+→ or Command+Shift+L (Mac) or
Ctrl+Shift+→ or Ctrl+Shift+L (Windows/Linux) | カードを一番右の列の一番下に移動します | ### カードをプレビューする | キーボードショートカット | 説明 | | -------------- | ---------------- | -| esc | カードのプレビューペインを閉じる | +| Esc | カードのプレビューペインを閉じる | {% ifversion fpt or ghec %} ## {% data variables.product.prodname_actions %} -| キーボードショートカット | 説明 | -| ---------------------------------------------------------- | ------------------------------------ | -| command + space または control + space | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 | -| g f | ワークフローファイルに移動します | -| shift + t または T | ログのタイムスタンプを切り替えます | -| shift + f または F | フルスクリーン表示を切り替えます | -| esc | フルスクリーン表示を終了します | +| キーボードショートカット | 説明 | +| ---------------------------------------------------------------------------------------------------- | ------------------------------------ | +| Command+Space (Mac) or
Ctrl+Space (Windows/Linux) | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 | +| G F | ワークフローファイルに移動します | +| Shift+T or T | ログのタイムスタンプを切り替えます | +| Shift+F or F | フルスクリーン表示を切り替えます | +| Esc | フルスクリーン表示を終了します | {% endif %} ## 通知 {% ifversion fpt or ghes or ghae or ghec %} -| キーボードショートカット | 説明 | -| -------------------- | ------------ | -| e | 完了済としてマークします | -| shift + u | 未読としてマークします | -| shift + i | 既読としてマークします | -| shift + m | サブスクライブ解除します | +| キーボードショートカット | 説明 | +| ----------------------------- | ------------ | +| E | 完了済としてマークします | +| Shift+U | 未読としてマークします | +| Shift+I | 既読としてマークします | +| Shift+M | サブスクライブ解除します | {% else %} -| キーボードショートカット | 説明 | -| ---------------------------------------------- | ------------ | -| e または I または y | 既読としてマークします | -| shift + m | スレッドをミュートします | +| キーボードショートカット | 説明 | +| -------------------------------------------- | ------------ | +| E or I or Y | 既読としてマークします | +| Shift+M | スレッドをミュートします | {% endif %} ## ネットワークグラフ -| キーボードショートカット | 説明 | -| --------------------------------------------- | ------------ | -| ← または h | 左にスクロールします | -| → または l | 右にスクロールします | -| ↑ または k | 上にスクロールします | -| ↓ または j | 下にスクロールします | -| shift + ← または shift + h | 左端までスクロールします | -| shift + → または shift + l | 右端までスクロールします | -| shift + ↑ または shift + k | 上端までスクロールします | -| shift + ↓ または shift + j | 下端までスクロールします | +| キーボードショートカット | 説明 | +| ------------------------------------------------------------------------------------------ | ------------ | +| ← or H | 左にスクロールします | +| → or L | 右にスクロールします | +| ↑ or K | 上にスクロールします | +| ↓ or J | 下にスクロールします | +| Shift+← (Mac) or
Shift+H (Windows/Linux) | 左端までスクロールします | +| Shift+→ (Mac) or
Shift+L (Windows/Linux) | 右端までスクロールします | +| Shift+↑ (Mac) or
Shift+K (Windows/Linux) | 上端までスクロールします | +| Shift+↓ (Mac) or
Shift+J (Windows/Linux) | 下端までスクロールします | diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index 93d5ba76da..1893824f58 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -13,7 +13,7 @@ topics: - Pull requests --- -## プルリクエストをIssueにリンクする +## Pull RequestをIssueにリンクする To link a pull request to an issue to{% ifversion fpt or ghes or ghae or ghec %} show that a fix is in progress and to{% endif %} automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. For example, `Closes #10` or `Fixes octo-org/octo-repo#100`. 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 `‘

’` are of course found somewhere in the training set:
![Example repetitions](/assets/images/help/copilot/example_repetitions.png)
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 `‘

’` are of course found somewhere in the training set:
![Example repetitions](/assets/images/help/copilot/example_repetitions.png)
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:
![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[5](#footnote5) uses such code to parse a different article and goes on to do different things with the results.
![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png)
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[5](#footnote5) uses such code to parse a different article and goes on to do different things with the results.
![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png)
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[6](#footnote6), 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-community-guidelines.md b/translations/ja-JP/content/github/site-policy/github-community-guidelines.md index ef578e91c1..6989bc5a0e 100644 --- a/translations/ja-JP/content/github/site-policy/github-community-guidelines.md +++ b/translations/ja-JP/content/github/site-policy/github-community-guidelines.md @@ -22,7 +22,7 @@ GitHub コミュニティの主な目的は、ソフトウェアプロジェク * **広い心で受け入れる** - 他のコラボレータとあなたとでは、経験値やバックグラウンドが異なるかもしれませんが、だからといって相手がコントリビューションにつながる良いアイデアを持っていないということにはなりません。 新たなコラボレータや、かけだしのユーザーは歓迎してあげましょう。 -* **お互いを尊重し合うこと。**無礼な態度ほど、健全な会話を妨げるものはありません。 礼儀正しく、大人の態度を保ちましょう。一般的に攻撃的、虐待的、ヘイトスピーチとみなされるような内容を投稿しないでください。 嫌がらせや、人が悲しむような行為は禁止されています。 あらゆるやり取りにおいて、お互いに品位と配慮をもって接しましょう。 +* **Respect each other** - Nothing sabotages healthy conversation like rudeness. 礼儀正しく、大人の態度を保ちましょう。一般的に攻撃的、虐待的、ヘイトスピーチとみなされるような内容を投稿しないでください。 嫌がらせや、人が悲しむような行為は禁止されています。 あらゆるやり取りにおいて、お互いに品位と配慮をもって接しましょう。 意見に反対したいこともあるでしょう。 それは全くかまいません。 ただし、批判すべきはアイデアであって、人ではありません。 悪口、個人攻撃、投稿の内容ではなく口調に対する応答、脊髄反射的な反論を行うのではなく、 会話の質を高めるような、理論的な反論を行いましょう。 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/github/site-policy/submitting-content-removal-requests.md b/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md index a473a51ce0..e5d9e5cf14 100644 --- a/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md +++ b/translations/ja-JP/content/github/site-policy/submitting-content-removal-requests.md @@ -23,3 +23,5 @@ GitHub トレードマークポリシーは、ブランドまたはビジネス ## [GitHub個人情報削除ポリシー](/github/site-policy/github-private-information-removal-policy) GitHub個人情報削除ポリシーは、個人的 (機密性が高く、セキュリティリスクをもたらす) で、著作権または商標によって保護されていないデータの報告に使用できます。 + +Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer). diff --git a/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md b/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md index 9f3c2d16b9..dd618fe3d4 100644 --- a/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md +++ b/translations/ja-JP/content/graphql/overview/about-the-graphql-api.md @@ -12,7 +12,7 @@ topics: ## 概要 -以下は、GraphQL API v4を使い始めるためのクイックリンクです。 +Here are some quick links to get you up and running with the GraphQL API: * [認証](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) * [ルートエンドポイント](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) @@ -36,9 +36,9 @@ topics: ## GitHubがGraphQLを使う理由 -GitHubは、インテグレーターにとって大きな柔軟性を提供してくれることから、API v4にGraphQLを選択しました。 ほしいデータ_だけ_を正確に定義できるのは、REST API v3エンドポイントよりも強力な利点です。 GraphQLを使えば、指定したデータをフェッチするための複数のRESTのリクエストを_単一の呼び出し_で置き換えられます。 +GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. GraphQLを使えば、指定したデータをフェッチするための複数のRESTのリクエストを_単一の呼び出し_で置き換えられます。 -GitHubがGraphQLに移行した理由の詳細については、オリジナルの[アナウンスのblogポスト](https://githubengineering.com/the-github-graphql-api/)を参照してください。 +For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/). ## GraphQLのスキーマ参照について 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/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md index 7f2a1cc9fa..8b1419f01e 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md @@ -21,7 +21,7 @@ topics: プロジェクトボードを再びオープンする場合、自動化を*同期*するよう設定することができます。それにより、ボードに設定されている自動化設定に従ってボード上のカードのポジションが更新されます。 詳しい情報については、「[クローズされたプロジェクトボードを再びオープンする](/articles/reopening-a-closed-project-board)」や「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)」を参照してください。 -1. Navigate to the list of project boards in your repository or organization, or owned by your user account. +1. リポジトリまたは Organization中にある、あるいはあなたのユーザアカウントが所有するプロジェクトボードの一覧に移動します。 2. プロジェクトリストで、クローズしたいプロジェクトボードの隣にある {% octicon "chevron-down" aria-label="The chevron icon" %}をクリックします。 ![プロジェクトボードの名前の右にある、V 字型のアイコン](/assets/images/help/projects/project-list-action-chevron.png) 3. [**Close**] をクリックします。 ![プロジェクトボードのドロップダウンメニューにある [Close] アイテム](/assets/images/help/projects/close-project.png) diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md index 732a02e29d..852951aca0 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md @@ -1,6 +1,6 @@ --- title: クローズされたプロジェクトボードを再びオープンする -intro: You can reopen a closed project board and restart any workflow automation that was configured for the project board. +intro: クローズされたプロジェクトボードを再びオープンして、プロジェクトボードに設定されているワークフローの自動化を再開できます。 redirect_from: - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board - /articles/reopening-a-closed-project-board diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md index ffcfc22e6f..e0091d01e0 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md @@ -21,7 +21,7 @@ shortTitle: ボード上のカードのアーカイブ ## プロジェクトボード上のカードのアーカイブ -1. In a project board, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![プロジェクトボードカードの編集オプションのリスト](/assets/images/help/projects/select-archiving-options-project-board-card.png) +1. プロジェクトボードで、アーカイブしたいカードを見つけて {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![プロジェクトボードカードの編集オプションのリスト](/assets/images/help/projects/select-archiving-options-project-board-card.png) 2. [**Archive**] をクリックします。 ![メニューからのアーカイブオプションの選択](/assets/images/help/projects/archive-project-board-card.png) ## サイドバーからのプロジェクトボード上のカードのリストア diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md index 6d3e4db01e..2eda1a1f87 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md @@ -49,7 +49,7 @@ Issueの最新のコメントの情報を得ておきたい場合には、Issue ## Issueとディスカッションの比較 -Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Issueあるいはディスカッションを使う場合のガイダンスについては「[GitHubでのコミュニケーション](/github/getting-started-with-github/quickstart/communicating-on-github)」を参照してください。 +会話の中には、{% data variables.product.prodname_discussions %}に適しているものもあります。 {% data reusables.discussions.you-can-use-discussions %} Issueあるいはディスカッションを使う場合のガイダンスについては「[GitHubでのコミュニケーション](/github/getting-started-with-github/quickstart/communicating-on-github)」を参照してください。 Issue内での会話にディスカッションの方が適している場合は、Issueをディスカッションに変換できます。 {% endif %} 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..96feb7ad51 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 @@ -53,7 +53,7 @@ topics: {% tip %} -**Tip:** You cannot create task list items within closed issues or issues with linked pull requests. +**参考:** クローズされたIssueや、リンクされたPull Requestを持つIssue内では、タスクリストのアイテムを作成することはできません。 {% endtip %} @@ -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 %} -* "[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 %} +* 「[基本的な執筆とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」{% if code-scanning-task-lists %} +* 「タスクリストを使ったIssue内の[{% data variables.product.prodname_code_scanning %} アラートの追跡](/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..e2b9d62ad4 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 @@ -45,17 +45,17 @@ Issue は、バグ、拡張、その他リクエストの追跡に使用でき {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -## Creating an issue with {% data variables.product.prodname_cli %} +## {% data variables.product.prodname_cli %}でのIssueの作成 -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} {% data variables.product.prodname_cli %}について学ぶには、「[{% data variables.product.prodname_cli %}について](/github-cli/github-cli/about-github-cli)」を参照してください。 -To create an issue, use the `gh issue create` subcommand. To skip the interactive prompts, include the `--body` and the `--title` flags. +Issueを作成するには、`gh issue create`サブコマンドを使ってください。 対話的なプロンプトをスキップするには、`--body`及び`--title`フラグを含めてください。 ```shell gh issue create --title "My new issue" --body "Here are more details." ``` -You can also specify assignees, labels, milestones, and projects. +アサインされる人、ラベル、マイルストーン、プロジェクトを指定することもできます。 ```shell gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase" @@ -83,7 +83,7 @@ IssueもしくはPull Requestのコメントから、新しいIssueをオープ {% data reusables.repositories.navigate-to-repo %} 1. Issue で参照したいコードを探します。 - ファイルのコードに関する Issue を開くには、そのファイルに移動します。 - - プルリクエストのコードに関する Issue を開くには、そのプルリクエストに移動し、{% octicon "diff" aria-label="The file diff icon" %}[**Files changed**] をクリックします。 Then, browse to the file that contains the code you want included in your comment, and click **View**. + - プルリクエストのコードに関する Issue を開くには、そのプルリクエストに移動し、{% octicon "diff" aria-label="The file diff icon" %}[**Files changed**] をクリックします。 そして、コメントに含めたいコードを持つファイルを探し、** View（ビュー）**をクリックしてください。 {% data reusables.repositories.choose-line-or-range %} 4. コード範囲の左で、{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} をクリックします。 ドロップダウンメニューで、[**Reference in new issue**] をクリックします。 ![選択した行から新しいIssueを開くオプションのある三点メニュー](/assets/images/help/repository/open-new-issue-specific-line.png) {% data reusables.repositories.type-issue-title-and-description %} @@ -92,15 +92,15 @@ IssueもしくはPull Requestのコメントから、新しいIssueをオープ {% ifversion fpt or ghec %} -## Creating an issue from discussion +## ディスカッションからのIssueの作成 -People with triage permission to a repository can create an issue from a discussion. +リポジトリへのTriage権限を持つユーザは、ディスカッションからIssueを作成できます。 -When you create an issue from a discussion, the contents of the discussion post will be automatically included in the issue body, and any labels will be retained. Creating an issue from a discussion does not convert the discussion to an issue or delete the existing discussion. For more information about {% data variables.product.prodname_discussions %}, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." +ディスカッションからIssueを作成する場合、ディスカッションの投稿の内容は自動的にIssueの本文に含められ、ラベルがあればそのまま残されます。 ディスカッションからIssueを作成しても、そのディスカッションがIssueに変換されたり、既存のディスカッションが削除されたりすることはありません。 {% data variables.product.prodname_discussions %}に関する詳しい情報については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。 {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**. ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg) +1. 右のサイドバーで、{% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion（ディスカッションからIssueを作成）**をクリックします。 ![ディスカッションからIssueを作成するボタン](/assets/images/help/discussions/create-issue-from-discussion.jpg) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} @@ -129,7 +129,7 @@ Issueをオープンするのにクエリパラメータを利用できます。 {% endtip %} -クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 たとえばクエリパラメータの`labels`を使うには、Issueにラベルを追加する権限を持っていなければなりません。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 たとえばクエリパラメータの`labels`を使うには、Issueにラベルを追加する権限を持っていなければなりません。 詳しい情報については「[Organizationのためのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。 クエリパラメータを使うのに不正なURLを作成したり、適切な権限を持っていなかったりした場合には、そのURLに対して`404 Not Found`エラーページが返されます。 サーバーの限度を超えるURLを作成すると、そのURLは`414 URI Too Long`エラーページを返します。 @@ -143,11 +143,11 @@ 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 %} -## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert +{% if code-scanning-task-lists %} +## {% data variables.product.prodname_code_scanning %}アラートからのIssueの作成 {% data reusables.code-scanning.beta-alert-tracking-in-issues %} -If you're using issues to track and prioritize your work, you can use issues to track {% data variables.product.prodname_code_scanning %} alerts. +作業の追跡と優先順位付けにIssueを使っているなら、{% data variables.product.prodname_code_scanning %}アラートの追跡にIssueを使えます。 {% data reusables.code-scanning.alert-tracking-link %} {% endif %} diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/deleting-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/deleting-an-issue.md index 14336031c4..bfe9e2f21c 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/deleting-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/deleting-an-issue.md @@ -17,7 +17,7 @@ topics: 削除できる Issue は自分のユーザアカウントが所有するリポジトリのものだけです。 別のユーザアカウントが所有するリポジトリの Issue は、仮にあなたがコラボレーターであったとしても、削除することはできません。 -Organization が所有するリポジトリの Issue を削除するには、Organization のオーナーが Organization のリポジトリの削除を有効にし、さらに削除する人がそのリポジトリの管理者権限かオーナー権限を持っている必要があります。 For more information, see "[Allowing people to delete issues in your organization](/articles/allowing-people-to-delete-issues-in-your-organization)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +Organization が所有するリポジトリの Issue を削除するには、Organization のオーナーが Organization のリポジトリの削除を有効にし、さらに削除する人がそのリポジトリの管理者権限かオーナー権限を持っている必要があります。 詳しい情報については「[OrganizationのIssueの削除を許可する](/articles/allowing-people-to-delete-issues-in-your-organization)」と「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。 Issue を削除してもコラボレータには通知されません。 削除された Issue の URL にコラボレータがアクセスすると、その Issue が削除された旨のメッセージが表示されます。 リポジトリの管理者権限かオーナー権限を持っている人にはさらに、Issue を削除した人のユーザ名と、いつ削除されたのかが表示されます。 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index e4137fb95f..1cc1f3df5c 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -1,6 +1,6 @@ --- -title: Filtering and searching issues and pull requests -intro: 'To find detailed information about a repository on {% data variables.product.product_name %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.' +title: Issue及びPull Requestのフィルタリングと検索 +intro: '{% data variables.product.product_name %}上のリポジトリに関する詳細情報を見つけるために、そのリポジトリに関連するIssueやPull Requestをフィルタリング、ソート、検索できます。' redirect_from: - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees - /articles/filtering-issues-and-pull-requests-by-assignees @@ -41,23 +41,23 @@ versions: topics: - Issues - Pull requests -shortTitle: Filter and search +shortTitle: フィルタリングと検索 type: how_to --- {% data reusables.cli.filter-issues-and-pull-requests-tip %} -## Issue およびプルリクエストをフィルタリングする +## Issue およびPull Requestをフィルタリングする -Issue およびプルリクエストには、適用してリストを整理するためのデフォルトのフィルタが備わっています。 +Issue およびPull Requestには、適用してリストを整理するためのデフォルトのフィルタが備わっています。 {% data reusables.search.requested_reviews_search %} -Issue およびプルリクエストをフィルタリングして、以下を探すことができます: -- すべてのオープンな Issue およびプルリクエスト -- 自分で作成した Issue およびプルリクエスト -- 自分に割り当てられた Issue およびプルリクエスト -- 自分が [**@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)された Issue およびプルリクエスト +Issue およびPull Requestをフィルタリングして、以下を探すことができます: +- すべてのオープンな Issue およびPull Request +- 自分で作成した Issue およびPull Request +- 自分に割り当てられた Issue およびPull Request +- 自分が [**@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)された Issue およびPull Request {% data reusables.cli.filter-issues-and-pull-requests-tip %} @@ -65,9 +65,9 @@ Issue およびプルリクエストをフィルタリングして、以下を {% data reusables.repositories.sidebar-issue-pr %} 3. [**Filters**] をクリックしてフィルタの種類を選びます。 ![[Filters] ドロップダウンメニューを使用する](/assets/images/help/issues/issues_filter_dropdown.png) -## Issue およびプルリクエストをアサインされた人でフィルタリングする +## Issue およびPull Requestをアサインされた人でフィルタリングする -Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them. +[IssueあるいはPull Requestを誰かに割り当てたら](/articles/assigning-issues-and-pull-requests-to-other-github-users)、それらについての作業をしている人に基づいてアイテムを見つけることができます。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -80,9 +80,9 @@ Once you've [assigned an issue or pull request to someone](/articles/assigning-i {% endtip %} -## Issue およびプルリクエストをラベルでフィルタリングする +## Issue およびPull Requestをラベルでフィルタリングする -Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels. +[IssueあるいはPull Requestにラベルを適用したら](/articles/applying-labels-to-issues-and-pull-requests)、アイテムをラベルに基づいて見つけることができます。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -97,31 +97,31 @@ Once you've [applied labels to an issue or pull request](/articles/applying-labe ## プルリクエストをレビューステータスでフィルタリングする -フィルタを使用して、レビューステータスでプルリクエストをフィルタリングしたり、自分でレビューしたプルリクエストや他のユーザにレビューするよう依頼されたプルリクエストを検索したりできます。 +フィルタを使用して、レビューステータスでPull Requestをフィルタリングしたり、自分でレビューしたPull Requestや他のユーザにレビューするよう依頼されたPull Requestを検索したりできます。 -プルリクエストのリポジトリのリストをフィルタリングして、次の検索を行えます: -- まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないプルリクエスト -- マージの前に[レビューが必要](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)なプルリクエスト -- レビュー担当者が承認したプルリクエスト -- レビュー担当者が変更を求めているプルリクエスト -- Pull requests that you have reviewed{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} -- Pull requests that someone has asked you directly to review{% endif %} -- [自分、または自分のチームに誰かがレビューを依頼](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)したプルリクエスト +Pull Requestのリポジトリのリストをフィルタリングして、次の検索を行えます: +- まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないPull Request +- マージの前に[レビューが必要](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)なPull Request +- レビュー担当者が承認したPull Request +- レビュー担当者が変更を求めているPull Request +- 自分がレビューしたPull Request{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} +- 誰かから直接レビューを求められたPull Request{% endif %} +- [自分、または自分のチームに誰かがレビューを依頼](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)したPull Request {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} 3. 右上にある [Reviews] ドロップダウンメニューをクリックします。 ![プルリクエストのリストの上にあるフィルタメニュー内の [Reviews] ドロップダウンメニュー](/assets/images/help/pull_requests/reviews-filter-dropdown.png) -4. フィルタを選択してます。そのフィルタのステータスのプルリクエストすべてが検索されます。 ![[Reviews] ドロップダウンメニュー内のフィルタのリスト](/assets/images/help/pull_requests/pr-review-filters.png) +4. フィルタを選択してます。そのフィルタのステータスのPull Requestすべてが検索されます。 ![[Reviews] ドロップダウンメニュー内のフィルタのリスト](/assets/images/help/pull_requests/pr-review-filters.png) ## 検索を使用して Issue およびプルリクエストをフィルタリングする -You can use advanced filters to search for issues and pull requests that meet specific criteria. +特定の条件を満たすIssueやPull Requestを検索するために、高度なフィルターを使うことができます。 -### Searching for issues and pull requests +### IssueやPull Requestの検索 {% webui %} -Issue とプルリクエストの検索バーを使用すると、独自のカスタムフィルターを定義し、さまざまな基準で並べ替えることができます。 検索バーは、各リポジトリの [**Issues**] および [**Pull requests**] タブ、ならびに[Issues および Pull requests のダッシュボード](/articles/viewing-all-of-your-issues-and-pull-requests)にあります。 +Issue とPull Requestの検索バーを使用すると、独自のカスタムフィルターを定義し、さまざまな基準で並べ替えることができます。 検索バーは、各リポジトリの [**Issues**] および [**Pull requests**] タブ、ならびに[Issues および Pull requests のダッシュボード](/articles/viewing-all-of-your-issues-and-pull-requests)にあります。 ![Issue およびプルリクエストの検索バー](/assets/images/help/issues/issues_search_bar.png) @@ -137,15 +137,15 @@ Issue とプルリクエストの検索バーを使用すると、独自のカ {% data reusables.cli.cli-learn-more %} -You can use the {% data variables.product.prodname_cli %} to search for issues or pull requests. Use the `gh issue list` or `gh pr list` subcommand along with the `--search` argument and a search query. +{% data variables.product.prodname_cli %}を使ってIssueやPull Requestを検索できます。 `--search`引数や検索クエリとともに`gh issue list`あるいは`gh pr list`サブコマンドを使ってください。 -For example, you can list, in order of date created, all issues that have no assignee and that have the label `help wanted` or `bug`. +たとえば、アサインされた人がなく、`help wanted`あるいは`bug`というラベルを持つすべてのIssueを、作成された日付順にリストできます。 ```shell gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc' ``` -You can also list all pull requests that mention the `octo-org/octo-team` team. +`octo-org/octo-team`チームをメンションしているすべてのPull Requestをリストすることもできます。 ```shell gh pr list --search "team:octo-org/octo-team" @@ -153,22 +153,22 @@ gh pr list --search "team:octo-org/octo-team" {% endcli %} -### About search terms +### 検索語について -Issue およびプルリクエストの検索用語により、次のことができます: +Issue およびPull Requestの検索用語により、次のことができます: -- 作者による Issue とプルリクエストのフィルタリング: `state:open type:issue author:octocat` -- [特定の人に関連するが、必ずしも **@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)ではない Issue とプルリクエストのフィルタリング: `state:open type:issue involves:octocat` -- アサインされた人による Issues とプルリクエストのフィルタリング: `state:open type:issue assignee:octocat` -- ラベルにより Issue とプルエストをフィルタリング: `state:open type:issue label:"bug"` +- 作者による Issue とPull Requestのフィルタリング: `state:open type:issue author:octocat` +- [特定の人に関連するが、必ずしも **@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)ではない Issue とPull Requestのフィルタリング: `state:open type:issue involves:octocat` +- アサインされた人による Issues とPull Requestのフィルタリング: `state:open type:issue assignee:octocat` +- ラベルにより Issue とPull Requestをフィルタリング: `state:open type:issue label:"bug"` - 次の用語の前に `-` を使用して検索用語を除外: `state:open type:issue -author:octocat` {% ifversion fpt or ghes > 3.2 or ghae or ghec %} {% tip %} -**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND. -- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. -- To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`. +**参考:** 論理和あるいは論理積を使って、ラベルでIssueやPull Requestをフィルタリングできます。 +- 論理和を使ってIssueをフィルタリングするには、カンマ構文を使ってください:`label:"bug","wip"` +- 論理積を使ってIssueをフィルタリングするには、個別のラベルフィルタを使ってください:`label:"bug" label:"wip"` {% endtip %} {% endif %} @@ -176,34 +176,34 @@ Issue およびプルリクエストの検索用語により、次のことが {% ifversion fpt or ghes or ghae or ghec %} Issueについては、以下も検索に利用できます。 -- クローズしているリファレンス`linked:pr`によってプルリクエストにリンクされているIssueのフィルタリング +- クローズしているリファレンス`linked:pr`によってPull RequestにリンクされているIssueのフィルタリング {% endif %} -プルリクエストについては、検索を利用して以下の操作もできます。 -- [ドラフト](/articles/about-pull-requests#draft-pull-requests)プルリクエストのフィルタリング: `is:draft` -- まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないプルリクエストのフィルタリング: `state:open type:pr review:none` -- マージされる前に[レビューを必要とする](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)プルリクエストのフィルタリング: `state:open type:pr review:required` -- レビュー担当者が承認したプルリクエストのフィルタリング: `state:open type:pr review:approved` -- レビュー担当者が変更を要求したプルリクエストのフィルタリング: `state:open type:pr review:changes_requested` -- [レビュー担当者](/articles/about-pull-request-reviews/)によるプルリクエストのフィルタリング: `state:open type:pr reviewed-by:octocat` -- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} -- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %} -- レビューを要求されたチームによるプルリクエストのフィルタリング: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} -- プルリクエストでクローズできるIssueにリンクされているプルリクエストのフィルタリング: `linked:issue`{% endif %} +Pull Requestについては、検索を利用して以下の操作もできます。 +- [ドラフト](/articles/about-pull-requests#draft-pull-requests)Pull Requestのフィルタリング: `is:draft` +- まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないPull Requestのフィルタリング: `state:open type:pr review:none` +- マージされる前に[レビューを必要とする](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)Pull Requestのフィルタリング: `state:open type:pr review:required` +- レビュー担当者が承認したPull Requestのフィルタリング: `state:open type:pr review:approved` +- レビュー担当者が変更を要求したPull Requestのフィルタリング: `state:open type:pr review:changes_requested` +- [レビュー担当者](/articles/about-pull-request-reviews/)によるPull Requestのフィルタリング: `state:open type:pr reviewed-by:octocat` +- [レビューを要求された](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)特定のユーザーによるPull Requestのフィルタリング: `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} +- 誰かから直接レビューを求められたPull Requestのフィルタリング:`state:open type:pr user-review-requested:@me`{% endif %} +- レビューを要求されたチームによるPull Requestのフィルタリング: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} +- プルリクエストでクローズできるIssueにリンクされているPull Requestのフィルタリング: `linked:issue`{% endif %} -## Issue およびプルリクエストをソートする +## Issue およびPull Requestをソートする フィルターは、特定の期間の情報をよりよく提供するためにソートできます。 これらのフィルタービューでソートできます。 -* 一番新しく作成された Issue またはプルリクエスト -* 一番古くに作成された Issue またはプルリクエスト -* 最もコメントされた Issue またはプルリクエスト -* 最もコメントされていない Issue およびプルリクエスト -* 一番新しく更新された Issue またはプルリクエスト -* 一番古くに更新された Issue またはプルリクエスト -* The most added reaction on issues or pull requests +* 一番新しく作成された Issue またはPull Request +* 一番古くに作成された Issue またはPull Request +* 最もコメントされた Issue またはPull Request +* 最もコメントされていない Issue およびPull Request +* 一番新しく更新された Issue またはPull Request +* 一番古くに更新された Issue またはPull Request +* 最もリアクションがあったIssueまたはPull Request {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -214,7 +214,7 @@ Issueについては、以下も検索に利用できます。 ## フィルターを共有する -一定の Issue およびプルリクエストをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。 +一定の Issue およびPull Requestをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。 Issue が生成した URL は、どのユーザにも送れます。そして、あなたが見ているフィルタビューと同じフィルタで表示できます。 @@ -226,4 +226,4 @@ Issue が生成した URL は、どのユーザにも送れます。そして、 ## 参考リンク -- "[Searching issues and pull requests](/articles/searching-issues)" +- 「[Issue及びPull Requestの検索](/articles/searching-issues)」 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 1f2446f0d0..0c6c4064ee 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -1,6 +1,6 @@ --- -title: プルリクエストをIssueにリンクする -intro: プルリクエストをIssueにリンクして、修正が進行中であることを示し、プルリクエストがマージされるときIssueを自動的にクローズすることができます。 +title: Pull RequestをIssueにリンクする +intro: Pull RequestをIssueにリンクして、修正が進行中であることを示し、Pull RequestがマージされるときIssueを自動的にクローズすることができます。 redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue - /articles/closing-issues-via-commit-message @@ -21,21 +21,21 @@ shortTitle: IssueへのPRのリンク {% note %} -**注釈:** プルリクエストにおける特別なキーワードは、プルリクエストがリポジトリの*デフォルト* ブランチをターゲットするときに解釈されます。 ただし、PRのベースが*それ以外のブランチ*である場合、それらのキーワードは無視され、リンクは作成されません。PRのマージはこのIssueに対して何の効果も持ちません。 **キーワードの1つを使用してプルリクエストをIssueにリンクしたい場合は、PRがデフォルトブランチ上になければなりません。** +**注釈:** Pull Requestにおける特別なキーワードは、Pull Requestがリポジトリの*デフォルト* ブランチをターゲットするときに解釈されます。 ただし、PRのベースが*それ以外のブランチ*である場合、それらのキーワードは無視され、リンクは作成されません。PRのマージはこのIssueに対して何の効果も持ちません。 **キーワードの1つを使用してPull RequestをIssueにリンクしたい場合は、PRがデフォルトブランチ上になければなりません。** {% endnote %} -## リンクされたIssueとプルリクエストについて +## リンクされたIssueとPull Requestについて -{% ifversion fpt or ghes or ghae or ghec %}手動で、または{% endif %}プルリクエストの説明でサポートされているキーワードを使用して、Issueをプルリクエストにリンクすることができます。 +{% ifversion fpt or ghes or ghae or ghec %}手動で、または{% endif %}Pull Requestの説明でサポートされているキーワードを使用して、IssueをPull Requestにリンクすることができます。 -プルリクエストが対処するIssueにそのプルリクエストにリンクすると、コラボレータは、誰かがそのIssueに取り組んでいることを確認できます。 +Pull Requestが対処するIssueにそのPull Requestをリンクすると、コラボレータは、誰かがそのIssueに取り組んでいることを確認できます。 -リンクされたプルリクエストをリポジトリのデフォルトブランチにマージすると、それにリンクされているIssueは自動的にクローズされます。 デフォルトブランチの詳細については、「[デフォルトブランチを変更する](/github/administering-a-repository/changing-the-default-branch)」を参照してください。 +リンクされたPull Requestをリポジトリのデフォルトブランチにマージすると、それにリンクされているIssueは自動的にクローズされます。 デフォルトブランチの詳細については、「[デフォルトブランチを変更する](/github/administering-a-repository/changing-the-default-branch)」を参照してください。 -## キーワードを使用してプルリクエストをIssueにリンクする +## キーワードを使用してPull RequestをIssueにリンクする -プルリクエストの説明で、またはコミットメッセージで、サポートされているキーワードを使用してプルリクエストにIssueにリンクすることができます (プルリクエストはデフォルトブランチになければなりません)。 +Pull Requestの説明またはコミットメッセージで、サポートされているキーワードを使用すれば、Pull RequestをIssueにリンクできます (Pull Requestはデフォルトブランチになければなりません)。 * close * closes @@ -47,9 +47,9 @@ shortTitle: IssueへのPRのリンク * resolves * resolved -If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request will also close the referenced pull request. +他のPull RequestでPull Requestのコメントを参照するためにキーワードを使用すると、Pull Requestはリンクされます。 参照元のPull Requestをマージすると、参照先のPull Requestもクローズされます。 -クローズするキーワードの構文は、Issueがプルリクエストと同じリポジトリにあるかどうかによって異なります。 +クローズするキーワードの構文は、IssueがPull Requestと同じリポジトリにあるかどうかによって異なります。 | リンクするIssue | 構文 | サンプル | | ---------------- | --------------------------------------------- | -------------------------------------------------------------- | @@ -57,23 +57,23 @@ If you use a keyword to reference a pull request comment in another pull request | Issueが別のリポジトリにある | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | 複数の Issue | Issueごとに完全な構文を使用 | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -{% ifversion fpt or ghes or ghae or ghec %}手動でリンクを解除できるのは、手動でリンクされたプルリクエストだけです。 キーワードを使用してリンクしたIssueのリンクを解除するには、プルリクエストの説明を編集してそのキーワードを削除する必要があります。{% endif %} +{% ifversion fpt or ghes or ghae or ghec %}手動でリンクを解除できるのは、手動でリンクされたPull Requestだけです。 キーワードを使用してリンクしたIssueのリンクを解除するには、Pull Requestの説明を編集してそのキーワードを削除する必要があります。{% endif %} -クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むプルリクエストは、リンクされたプルリクエストとしてリストされません。 +クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むPull Requestは、リンクされたPull Requestとしてリストされません。 {% ifversion fpt or ghes or ghae or ghec %} -## 手動でプルリクエストをIssueにリンクする +## 手動でPull RequestをIssueにリンクする -リポジトリへの書き込み権限があるユーザなら誰でも、手動でプルリクエストをIssueにリンクできます。 +リポジトリへの書き込み権限があるユーザなら誰でも、手動でPull RequestをIssueにリンクできます。 -手動で1つのプルリクエストごとに最大10個のIssueをリンクできます。 Issueとプルリクエストは同じリポジトリになければなりません。 +手動で1つのPull Requestごとに最大10個のIssueをリンクできます。 IssueとPull Requestは同じリポジトリになければなりません。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -3. プルリクエストのリストで、Issueにリンクしたいプルリクエストをクリックします。 +3. Pull Requestのリストで、IssueにリンクしたいPull Requestをクリックします。 4. 右のサイドバーで、[**Linked issues**] をクリックします。 ![右サイドバーの [Linked issues]](/assets/images/help/pull_requests/linked-issues.png) -5. プルリクエストにリンクするIssueをクリックします。 ![Issueをリンクするドロップダウン](/assets/images/help/pull_requests/link-issue-drop-down.png) +5. Pull RequestにリンクするIssueをクリックします。 ![Issueをリンクするドロップダウン](/assets/images/help/pull_requests/link-issue-drop-down.png) {% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md index d7f2c04d44..9ee10df6d4 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md @@ -20,7 +20,7 @@ topics: ## 必要な環境 -Issueを作成するにはリポジトリが必要です。 書き込みアクセス権を持つ既存のリポジトリを利用することも、新しいリポジトリを作成することもできます。 {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 リポジトリでIssueが無効化されている場合、Issueを有効化する方法に関する情報については「[Issueの無効化](/github/administering-a-repository/managing-repository-settings/disabling-issues)」を参照してください。 +Issueを作成するにはリポジトリが必要です。 書き込みアクセス権を持つ既存のリポジトリを利用することも、新しいリポジトリを作成することもできます。 {% data reusables.enterprise-accounts.emu-permission-repo %} リポジトリはIssueを有効化していなければなりません。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 リポジトリでIssueが無効化されている場合、Issueを有効化する方法に関する情報については「[Issueの無効化](/github/administering-a-repository/managing-repository-settings/disabling-issues)」を参照してください。 ## 空のIssueのオープン @@ -81,7 +81,7 @@ Issueを既存のプロジェクトに追加できます。 {% ifversion fpt or ## コミュニケーション -Issueを作成した後は、そのIssueにコメントを追加して会話を続けてください。 コラボレータあるいはTeamを@メンションして、コメントに注意を惹きつけることができます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 くわしいじょうほうについては「[GitHubでの執筆](/github/writing-on-github)」を参照してください。 +Issueを作成した後は、そのIssueにコメントを追加して会話を続けてください。 コラボレータあるいはTeamを@メンションして、コメントに注意を惹きつけることができます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 くわしい情報については「[GitHubでの執筆](/github/writing-on-github)」を参照してください。 ![Issueのコメント](/assets/images/help/issues/issue-comment.png) diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md index 115cd4d317..2fe8f14655 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md @@ -1,6 +1,6 @@ --- -title: 他のリポジトリへ Issue を移譲する -intro: より適しているリポジトリに Issue を移動するため、オープン Issue を他のリポジトリに移譲できます。 +title: Transferring an issue to another repository +intro: 'To move an issue to a better fitting repository, you can transfer open issues to other repositories.' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/transferring-an-issue-to-another-repository - /articles/transferring-an-issue-to-another-repository @@ -13,27 +13,29 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Issueの移譲 +shortTitle: Transfer an issue --- - To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -同じユーザまたは Organization アカウントが所有するリポジトリ間においてのみ、Issue を移譲できます。 {% ifversion fpt or ghes or ghec %}プライベートリポジトリからパブリックリポジトリへIssueを移譲することはできません。{% endif %} +You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}You can't transfer an issue from a private repository to a public repository.{% endif %} -Issueを委譲する場合、コメントとアサインされた人は保持されます。 Issue のラベルとマイルストーンは保持されません。 このIssueは、ユーザー所有または組織全体のプロジェクトボードにとどまり、リポジトリのプロジェクトボードから削除されます。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 +When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)." -Issue でメンションされた人や Team は、Issue が新しいリポジトリに移譲されたことを知らせる通知を受け取ります。 当初の URL は、新しい Issue の URL にリダイレクトします。 新しいリポジトリの読み取り権限がない人には、アクセスできない新しいリポジトリに Issue が移譲されたことを知らせるバナーが表示されます。 +People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access. -## 他のリポジトリへオープン Issue を移譲する +## Transferring an open issue to another repository {% webui %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} -3. Issue のリストで、移譲したい Issue をクリックします。 -4. 右のサイドバーで [**Transfer this issue**] をクリックします。 ![Issue を移譲するボタン](/assets/images/help/repository/transfer-issue.png) -5. [**Choose a repository**] ドロップダウンメニューで、Issue の移譲先にするリポジトリを選択します。 ![リポジトリセレクションを選択](/assets/images/help/repository/choose-a-repository.png) -6. [**Transfer issue**] をクリックします。 ![Issue 移譲ボタン](/assets/images/help/repository/transfer-issue-button.png) +3. In the list of issues, click the issue you'd like to transfer. +4. In the right sidebar, click **Transfer issue**. +![Button to transfer issue](/assets/images/help/repository/transfer-issue.png) +5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to. +![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png) +6. Click **Transfer issue**. +![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png) {% endwebui %} @@ -49,8 +51,8 @@ gh issue transfer issue {% ifversion ghes %}hostname/{% endif %}own {% endcli %} -## 参考リンク +## Further reading -- 「[Issue について](/articles/about-issues)」 -- 「[セキュリティログをレビューする](/articles/reviewing-your-security-log)」 -- 「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)」 +- "[About issues](/articles/about-issues)" +- "[Reviewing your security log](/articles/reviewing-your-security-log)" +- "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)" diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index d6e62f29c5..25bc309b45 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -25,4 +25,4 @@ Issue およびPull Requestダッシュボードは、すべてのページの ## 参考リンク -- {% ifversion fpt or ghes or ghae or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listing the repositories you're watching](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" +- {% ifversion fpt or ghes or ghae or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}「[Watch しているリポジトリのリスト](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}」 diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md index 2725039d36..7f9fccd8f3 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/about-projects.md @@ -29,7 +29,7 @@ topics: - タスクの複雑さを追跡する数値フィールド - タスクの優先度が低、中、高なのかを追跡するための単一選択フィールド - クイックノートを追跡するテキストフィールド -- an iteration field to plan work week-by-week +- 週ごとの作業を計画するための繰り返しフィールド ### 様々な観点からプロジェクトを見る @@ -47,13 +47,13 @@ topics: 詳しい情報については「[プロジェクトのビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。 -### Working with the project command palette +### プロジェクトコマンドパレットでの作業 -You can use the project command palette to quickly change views or add fields. コマンドパレットは、カスタムキーボードショートカットを覚えておかなくてもいいようにガイドしてくれます。 詳しい情報については「[プロジェクトのビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。 +プロジェクトコマンドパレットを使って、素早くビューを切り替えたり、フィールドを追加したりできます。 コマンドパレットは、カスタムキーボードショートカットを覚えておかなくてもいいようにガイドしてくれます。 詳しい情報については「[プロジェクトのビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。 ### プロジェクト管理タスクの自動化 -Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." You can also use the GraphQL API and {% data variables.product.prodname_actions %} to automate routine project management tasks. For more information, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)" and "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)." +プロジェクト（ベータ）は、組み込みのワークフローを提供します。 たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 GraphQL APIと{% data variables.product.prodname_actions %}を使って、ルーチンのプロジェクトタスクを自動化することもできます。 詳しい情報については「[プロジェクトの自動化](/issues/trying-out-the-new-projects-experience/automating-projects)」及び「[APIを使ったプロジェクトの管理](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)」を参照してください。 ## プロジェクト（ベータ）と非ベータのプロジェクトの比較 diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md index 374fe7d144..b0fa4bc80d 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/automating-projects.md @@ -1,6 +1,6 @@ --- title: プロジェクト（ベータ）の自動化 -intro: 'You can use built-in workflows or the API and {% data variables.product.prodname_actions %} to manage your projects.' +intro: '組み込みのワークフロー、あるいはAPIと{% data variables.product.prodname_actions %}を使ってプロジェクトを管理できます。' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -17,13 +17,13 @@ topics: ## はじめに -You can add automation to help manage your project. Projects (beta) includes built-in workflows that you can configure through the UI. Additionally, you can write custom workflows with the GraphQL API and {% data variables.product.prodname_actions %}. +プロジェクトの管理に役立つ自動化を追加できます。 プロジェクト（ベータ）には、UIを通じて設定できる組み込みのワークフローが含まれています。 加えて、GraphQL APIと{% data variables.product.prodname_actions %}でカスタムのワークフローを書くことができます。 -## Built-in workflows +## 組み込みのワークフロー {% data reusables.projects.about-workflows %} -You can enable or disable the built-in workflows for your project. +プロジェクトでは、組み込みのワークフローを有効化あるいは無効化できます。 {% data reusables.projects.enable-basic-workflow %} diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md index 1f46ea5940..849048728c 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md @@ -49,7 +49,7 @@ IssueとPull Requestには、コラボレータと容易にコミュニケーシ You can automate tasks to spend less time on busy work and more time on the project itself. 手動でやることを覚えておく必要が減れば、それだけプロジェクトは耐震の状態に保たれるようになります。 -Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." +プロジェクト（ベータ）は、組み込みのワークフローを提供します。 たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review." diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md index 1a3f4355df..7e2f24fabc 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md @@ -152,7 +152,7 @@ You can later edit the drop down options for single select and iteration fields. {% data reusables.projects.about-workflows %} -You can enable or disable the built-in workflows for your project. +プロジェクトでは、組み込みのワークフローを有効化あるいは無効化できます。 {% data reusables.projects.enable-basic-workflow %} 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 %} + + +## {% 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..7e6798d605 --- /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.4 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 %}**. +{% else %} +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..5b9639cf00 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.4 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..35d7eef3e3 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.4 or ghae-issue-5658 %} +{% data reusables.repositories.click-collaborators-teams %} +{% else %} {% 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..a1235b20a2 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.4 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..1f221c13e1 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.4 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**] をクリックします。 +{% else %} {% 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-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index 2a8caf6896..d08ed171af 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -15,26 +15,37 @@ topics: shortTitle: リポジトリの作成の制限 --- -メンバーが Organization でリポジトリを作成できるかどうかを選択できます。 If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}. +メンバーが Organization でリポジトリを作成できるかどうかを選択できます。 {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository. + +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization). +{% endif %} -Organization のオーナーは、いつでもどんなタイプの リポジトリ でも作成できます。 {% ifversion ghec or ghae or ghes %} -{% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %} +Enterprise owners can restrict the options you have available for your organization's repository creation policy. 詳しい情報については、「[Enterprise でのリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)」を参照してください。 +{% endif %} {% warning %} -**警告**: この設定で制限されるのは、リポジトリを作成するときの可視性オプションだけです。後からリポジトリの可視性を変更する機能は制限されません。 For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." +**警告**: この設定で制限されるのは、リポジトリを作成するときの可視性オプションだけです。後からリポジトリの可視性を変更する機能は制限されません。 詳しい情報については「[Organization 内でリポジトリの可視性の変更を制限する](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)」を参照してください。 {% endwarning %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. Under "Repository creation", select one or more options. +5. [Repository creation] で、1 つ以上のオプションを選択します。 {%- ifversion ghes or ghec or ghae %} ![リポジトリ作成のオプション](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![リポジトリ作成のオプション](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + + {% note %} + + **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + + {% endnote %} {%- endif %} + 6. [**Save**] をクリックします。 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..c1414d4ace 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.4 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.4 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 %}/OWNER USERNAME:TOKEN 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/about-pull-requests.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 52fbe44335..18f9b8bc2e 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -22,7 +22,7 @@ topics: **メモ:** プルリクエストを使う際には以下のことを念頭に置いてください: * [共有リポジトリモデル](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)で作業をしている場合、プルリクエストにはトピックブランチを使うことをおすすめします。 ブランチあるいはコミットからプルリクエストを送ることもできますが、トピックブランチを使えば提案した変更を更新する必要がある場合、フォローアップのコミットをプッシュできます。 -* プルリクエストにコミットをプッシュする場合、フォースプッシュはしないでください。 Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. +* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} 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/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index 85c154a11d..e49a1ea145 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -17,7 +17,7 @@ topics: リポジトリのフォークはリポジトリのコピーと似ていますが、次の 2 つの大きな違いがあります。 -* プルリクエストを使ってユーザが所有するフォークからの変更をオリジナルのリポジトリ（*上流*のリポジトリとも呼ばれます）に提案できます。 +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. * 上流のリポジトリと自分のフォークを同期させることで、上流のリポジトリからの変更を自分のローカルフォークへ持ち込めます。 {% data reusables.repositories.you-can-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 新しい URL ``` -- 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..129ebd161c 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.4 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] に、リンク先の外部システムへのリンクを入力します。 参照番号の変数は``のままにしてください。 ![外部システムへの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ファイルを含むコミットあるいは一連の変更を見る場合 ``` -たとえばモデルの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 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/billing.md b/translations/ja-JP/content/rest/reference/billing.md index 0166fd4594..bae79da6e3 100644 --- a/translations/ja-JP/content/rest/reference/billing.md +++ b/translations/ja-JP/content/rest/reference/billing.md @@ -4,6 +4,7 @@ intro: 'With the Billing API, you can monitor the charges and usage {% data vari versions: fpt: '*' ghec: '*' + ghes: '>=3.4' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/ja-JP/content/rest/reference/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md index d903396303..230e3f76b5 100644 --- a/translations/ja-JP/content/rest/reference/enterprise-admin.md +++ b/translations/ja-JP/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 @@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 %} ## Billing {% for operation in currentRestOperations %} 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..4fdd204aef 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 -%} @@ -918,6 +921,9 @@ _Team_ {% 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 %} ### "self-hosted runners"に対する権限 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 検索結果を絞り込む他の方法としては、一定のサブセットを除外することです。 `-` のプリフィックスを修飾子に付けることで、その修飾子にマッチする全ての結果を除外できます。 -| クエリ | サンプル | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| -QUALIFIER | **[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. | +| クエリ | サンプル | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -QUALIFIER | **[`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:/` を使います。 または、ディレクトリやそのサブディレクトリ内に存在しているファイルを検索するには、ディレクトリ名もしくはディレクトリへのパスを明示してください。 -| 修飾子 | サンプル | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) は、リポジトリの root レベルに存在する 「octocat」という単語がある _readme_ ファイルにマッチします。 | -| path:DIRECTORY | [**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 cgi-bin directory, or in any of its subdirectories. | -| path:PATH/TO/DIRECTORY | [**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 app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) は、リポジトリの root レベルに存在する 「octocat」という単語がある _readme_ ファイルにマッチします。 | +| path:DIRECTORY | [**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 cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**`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 app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | ## 言語で検索 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` 修飾子を使います。 -| 修飾子 | サンプル | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) は、@codertocat が所有するパッケージにマッチします。 | -| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) は、{% data variables.product.prodname_dotcom %} Organization が所有するパッケージにマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat | +| org:ORGNAME | [**`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 リポジトリのコードの言語に基づいてリポジトリを検索できます。 -| 修飾子 | サンプル | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) は、JavaScript 形式で記述された「rails」という単語があるリポジトリにマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**`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)」を参照してください。 -| 修飾子 | サンプル | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) は、Topics「jekyll」で分類されたリポジトリにマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**`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:>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:>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:>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:>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)」を参照してください。 -| 修飾子 | サンプル | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) は、@defunkt にメンションしている「resque」という単語がある Issue にマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**`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 の名前に置き換えてください。 -| 修飾子 | サンプル | -| ------------------------- | ------------------------------------------------------------------------------------ | -| team:ORGNAME/TEAMNAME | **team:jekyll/owners** は、`@jekyll/owners` Team がメンションされている Issue にマッチします。 | -| | **team:myorg/ops is:open is:pr** は、`@myorg/ops` Team がメンションされているオープンなプルリクエストにマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **`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 | 修飾子 | サンプル | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) は、2011 年より前にマージされた JavaScript のリポジトリにあるプルリクエストにマッチします。 | +| merged:YYYY-MM-DD | [**`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/accounts/you-must-know-your-password.md b/translations/ja-JP/data/reusables/accounts/you-must-know-your-password.md new file mode 100644 index 0000000000..f4795c3909 --- /dev/null +++ b/translations/ja-JP/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/translations/ja-JP/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/ja-JP/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md index d697ff8f8c..d645231024 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md +++ b/translations/ja-JP/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/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..82d55ced2a 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.4 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..b3bc67e48c 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.4 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..50321fdaae 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.4 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 %}**. +{% else %} +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..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/github-token-available-permissions.md b/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md index acb289f986..5d51bf49fe 100644 --- a/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md +++ b/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md @@ -5,8 +5,8 @@ permissions: actions: read|write|none checks: read|write|none contents: read|write|none - deployments: read|write|none - id-token: read|write|none + deployments: read|write|none{% ifversion fpt or ghec %} + id-token: read|write|none{% endif %} issues: read|write|none discussions: read|write|none packages: read|write|none 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 https://github.com/octo-org/octo-repo --pat ghp_abcd1234 +``` \ 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/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index baa5494599..2eb1fcc98b 100644 --- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -12,6 +12,6 @@ 2. 左のサイドバーで**Enterprise overview（Enterpriseの概要）**をクリックしてください。 3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 2. Navigate to the "Runner groups" settings: - * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %} - * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghec %}, then click the **Runners groups** tab{% endif %}.{% endif %} + * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %} + * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %} {% 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..3bd2a38dda 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.4 or ghae-issue-5658 %} +1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**. +{% else %} 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

@@ -75,7 +75,7 @@ The macos-latest label currently uses the macOS 10.15 runner image. macOS Catalina 10.15 @@ -83,6 +83,12 @@ macOS Catalina 10.15
-macos-11 +macos-latestもしくはmacos-11 -The macos-latest label currently uses the macOS 10.15 runner image. +The macos-latest label currently uses the macOS 11 runner image.
-macos-latestもしくはmacos-10.15 +macos-10.15
+{% 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 %} Note: 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..b525e863e3 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.4 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**. +{% else %} 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..3e1866c909 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.4 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 %}**. +{% else %} 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..f8c48625f5 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.4 or ghae-issue-5658 %} +1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**. +{% else %} 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..28f1b30a6b 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.4 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**. +{% else %} 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..08466c36d6 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.4 or ghae-issue-5658 %} +1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**. +{% else %} 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..89ff33e85f 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.4 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..5c9046cef1 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.4 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..018cf275ad 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.4 or ghae-issue-5658 %} +1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**. +{% else %} 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..2ab65be81c 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.4 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/actions-scheduled-workflow-example.md b/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md index 08c318e42e..8f1d35ce55 100644 --- a/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md +++ b/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md @@ -1,4 +1,4 @@ -[POSIX クーロン構文](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)を使用して、特定の UTC 時間にワークフローを実行できるようスケジュール設定できます。 スケジュールしたワークフローは、デフォルトまたはベースブランチの直近のコミットで実行されます。 スケジュールされたワークフローを実行できる最短の間隔は、15 分ごとに 1 回です。 +[POSIX クーロン構文](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)を使用して、特定の UTC 時間にワークフローを実行できるようスケジュール設定できます。 スケジュールしたワークフローは、デフォルトまたはベースブランチの直近のコミットで実行されます。 スケジュールされたワークフローを実行できる最短の間隔は、5 分ごとに 1 回です。 この例では、ワークフローは毎日UTCの5:30と17:30にトリガーされます。 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..74975d6095 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.4 or ghae-issue-5658 %} +1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**. +{% else %} 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..dad1922717 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.4 or ghae-issue-5658 %} +1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**. +{% else %} 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..0d38e50c33 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.4 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..a557181afd 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.4 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..4cab6ba712 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.4 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..988a6f8745 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.4 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..077a127843 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.4 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..f1530271d3 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.4 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..416bd818e6 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.4 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..eda56038cf 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.4 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..cb8a30346e 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.4 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..a5440481d4 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.4 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..fab940b564 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.4 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..9843f20023 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.4 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の最新のパッチリリースではありません。' ghes_release_notes_upgrade_release_only: '📣 これはEnterprise Serverの最新リリースではありません。' ghes_release_notes_upgrade_patch_and_release: '📣 これはこのリリースシリーズの最新パッチリリースではなく、これはEnterprise Serverの最新リリースではありません。' + 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/ja-resets.csv b/translations/log/ja-resets.csv index 7dcbab7def..1b4d54ed97 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,9 @@ 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/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.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 +196,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/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..19c4857233 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: '*' @@ -38,7 +38,7 @@ Se você for integrante de um {% data variables.product.prodname_emu_enterprise 1. Pergunte o nome do usuário da pessoa que você está convidando a colaborar.{% ifversion fpt or ghec %} Caso a pessoa não tenha um nome de usuário ainda, deve se inscrever em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Inscrever-se em uma nova conta {% 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 or ghes > 3.3 or ghae-issue-5658%} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%} {% data reusables.repositories.click-collaborators-teams %} 1. Clique em **Convidar um colaborador**. ![Botão "Convidar um colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png) 2. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field-user.png) 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-a-collaborator-from-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/removing-a-collaborator-from-a-personal-repository.md index f9c9852e15..c88edc9073 100644 --- a/translations/pt-BR/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/pt-BR/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,7 +30,7 @@ Apesar de as bifurcações de repositórios privados serem excluídas quando um {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} 4. À direita do colaborador que deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Botão para remover o colaborador](/assets/images/help/repository/collaborator-remove.png) {% else %} 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 40b2260757..c8f4163bed 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,8 +21,8 @@ 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**. +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} +2. Na seção "código, planejamento e automação" na barra lateral, clique em **Repositórios de {% octicon "repo" aria-label="The repo icon" %}**. {% else %} 2. Na barra lateral esquerda, clique em **Repositories** (Repositórios). ![Guia Repositories (Repositórios)](/assets/images/help/settings/settings-sidebar-repositories.png) {% endif %} 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 474fd1449c..1a8c5abd63 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. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**. +1. Na barra lateral esquerda, clique em **Aparência de {% octicon "paintbrush" aria-label="The paintbrush icon" %}**. 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/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 0b050c4a08..3897143cc3 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -22,7 +22,7 @@ Você pode querer usar um tema escuro para reduzir o consumo de energia em certo {% note %} -**Nota:** Os temas para daltônicos e os temas com alto contraste de luz estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)". +**Observação:** Os temas coloridos estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)". {% endnote %} diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index e907da9c49..40fbd049e1 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -69,7 +69,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build ``` @@ -106,7 +106,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Run the Gradle package task - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: -b ci.gradle package ``` @@ -135,7 +135,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build - uses: actions/upload-artifact@v2 diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index bd68979d73..71d718f64c 100644 --- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -47,7 +47,7 @@ Se você definir o `entrypoint` em um arquivo de metadados de uma ação, ele ir A instrução do `ENTRYPOINT` do Docker tem forma de _shell_ e forma de _exec_. A documentação do `ENTRYPOINT` do docker recomenda o uso da forma _exec_ da instrução do `ENTRYPOINT`. Para obter mais informações sobre as formas _exec_ e _shell_, consulte a referência ENTRYPOINT [](https://docs.docker.com/engine/reference/builder/#entrypoint) na documentação do Docker. -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). +Você não deve usar `WORKDIR` para especificar seu ponto de entrada no seu arquivo Docker. Em vez disso, você edverá usar um caminho absoluto. Para obter mais informações, consulte [WORKDIR](#workdir). Se você configurar o seu contêiner para usar a forma _exec_ da instrução `ENTRYPOINT`, os `args` configurados no arquivo de metadados da ação não serão executados em um shell do comando. Se os `args` da ação contiverem uma variável do ambiente, esta não será substituída. Por exemplo, usar o formato _exec_ a seguir não imprimirá o valor armazenado em `$GITHUB_SHA`. Em vez disso, imprimirá `$GITHUB_SHA`. 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 d491d5c4f1..c55b527e76 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 %} -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. +Todas as ações exigem 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, saídas e executam a configuração para sua ação. 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)". @@ -41,7 +41,7 @@ Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que **Opcional**: parâmetros de entrada permitem que você especifique os dados que a ação espera usar no momento da execução. O {% data variables.product.prodname_dotcom %} armazena parâmetros como variáveis de ambiente. Identificações de entrada com letras maiúsculas são alteradas para letras minúsculas no momento da execução. Recomenda-se usar identificações de entrada com letras minúsculas. -### Example: Specifying inputs +### Exemplo: Especificando entradas Este exemplo configura duas entradas: numOctocats e octocatEyeColor. A entrada numOctocats não é necessária e assumirá o valor '1'. A entrada octocatEyeColor é necessária e não tem valor padrão. Arquivos de fluxo de trabalho que usam essa ação devem usar a palavra-chave `with` (com) para definir um valor de entrada para octocatEyeColor. Para obter mais informações sobre a sintaxe `with` (com), consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)". @@ -84,13 +84,13 @@ Por exemplo, se um fluxo de trabalho definiu as entradas `numOctocats` e `octoca **Opcional** Se o parâmetro de entrada for usado, esta `string` será registrada como uma mensagem de aviso. Você pode usar este aviso para notificar os usuários de que o valor de entrada está obsoleto e mencionar outras alternativas. -## `outputs` for Docker container and JavaScript actions +## `sapidas` para o contêiner do Docker e ações do JavaScript **Opcional** Os parâmetros de saída permitem que você declare os dados definidos por uma ação. As ações executadas posteriormente em um fluxo de trabalho podem usar os dados de saída definidos em ações executadas anteriormente. Por exemplo, se uma ação executou a adição de duas entradas (x + y = z), a ação poderia usar o resultado da soma (z) como entrada em outras ações. Se você não declarar uma saída no seu arquivo de metadados de ação, você ainda poderá definir as saídas e usá-las no seu fluxo de trabalho. Para obter mais informações sobre a definição de saídas em uma ação, consulte "[Comandos do fluxo de trabalho para {% 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 +### Exemplo: Declarando saídas para o contêiner do Docker e ações do JavaScript ```yaml saídas: @@ -447,7 +447,7 @@ Se você precisar passar variáveis de ambiente para uma ação, certifique-se d Para obter mais informações sobre o uso da instrução `CMD` com {% data variables.product.prodname_actions %}, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)". -#### Example: Defining arguments for the Docker container +#### Exemplo: Definir argumentos para o contêiner do Docker {% raw %} ```yaml @@ -465,7 +465,7 @@ runs: Você pode usar uma cor e o ícone da [Pena](https://feathericons.com/) para criar um selo para personalizar e distinguir a sua ação. Os selos são exibidos ao lado do nome da sua ação em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). -### Example: Configuring branding for an action +### Exemplo: Configurar a marca para uma ação ```yaml branding: diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md index e2b4a004fb..ebabfae7f8 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md @@ -90,8 +90,12 @@ Este procedimento demonstra como criar a conta de serviço para sua integração ``` $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ --member=serviceAccount:$SA_EMAIL \ - --role=roles/container.admin \ - --role=roles/storage.admin \ + --role=roles/container.admin + $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ + --member=serviceAccount:$SA_EMAIL \ + --role=roles/storage.admin + $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ + --member=serviceAccount:$SA_EMAIL \ --role=roles/container.clusterViewer ``` {% endraw %} 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 8572081125..d5a61922e2 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 @@ -29,7 +29,7 @@ Ao atualizar seus fluxos de trabalho para usar tokens do OIDC, você pode adotar - **Sem segredos na nuvem**: Você não vai precisar duplicar suas credenciais da nuvem como segredos de {% data variables.product.prodname_dotcom %} de longa duração. Em vez disso, você pode configurar a confiança do OIDC no seu provedor de nuvem, e, em seguida, atualizar seus fluxos de trabalho para solicitar um token de acesso curto do provedor de nuvem por meio do OIDC. - **Autenticação e gestão de autorização**: Você tem mais controle granular sobre como fluxos de trabalho podem usar credenciais, usando a autenticação de seu provedor de nuvem (authN) e ferramentas de autorização (authZ) para controlar o acesso a recursos na nuvem. -- **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. +- **Girando credenciais**: Com o OIDC, seu provedor de nuvem emite um token de acesso de curta duração que só é válido para uma única execução de um trabalho e, posteriormente, vence automaticamente. ### Introdução ao OIDC @@ -38,7 +38,7 @@ O diagrama a seguir fornece uma visão geral de como o provedor OIDC de {% data ![Diagrama do OIDC](/assets/images/help/images/oidc-architecture.png) 1. No seu provedor de nuvem, crie uma confiança do OIDC entre a sua função na nuvem e o(s) seu(s) fluxo(s) de trabalho {% data variables.product.prodname_dotcom %} que precisam acessar a nuvem. -2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. Esse token contém várias reivindicações para estabelecer uma identidade de segurança reforçada e verificável sobre o fluxo de trabalho específico que está tentando autenticar. +2. Toda vez que o seu trabalho é executado, o provedor OIDC de {% data variables.product.prodname_dotcom %} gera um token de OIDC automaticamente. Esse token contém várias reivindicações para estabelecer uma identidade de segurança reforçada e verificável sobre o fluxo de trabalho específico que está tentando autenticar. 3. Você pode incluir um passo ou ação no seu trabalho para solicitar este token do provedor do OIDC de {% data variables.product.prodname_dotcom %}, e apresentá-lo ao provedor da nuvem. 4. Uma vez que o provedor de nuvem valida as reivindicações apresentadas no token, ele irá fornecer, posteriormente, um token de acesso à nuvem de curta duração que está disponível apenas para a duração do trabalho. @@ -51,7 +51,7 @@ Ao configurar sua nuvem para confiar no provedor do OIDC de {% data variables.pr ### Entendendo o token do OIDC -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. Para validar o token, o provedor de nuvem verifica se o assunto do token do OIDC e outras reivindicações correspondem às condições que foram pré-configuradas na definição de confiança do OIDC da função da nuvem. +Cada trabalho solicita um token do OIDC de {% data variables.product.prodname_dotcom %}, que responde com um token web do JSON gerado automaticamente (JWT) que é único para cada trabalho de fluxo de trabalho em que é gerado. Quando o trabalho é executado, o token de OIDC é apresentado ao provedor de nuvem. Para validar o token, o provedor de nuvem verifica se o assunto do token do OIDC e outras reivindicações correspondem às condições que foram pré-configuradas na definição de confiança do OIDC da função da nuvem. O exemplo a seguir do token do OIDC usa um assunto (`sub`) que faz referência a um ambiente de trabalho chamado `prod` no repositório `octo-org/octo-repo`. @@ -147,7 +147,7 @@ Além disso, seu provedor de nuvem poderia permitir que você atribuísse uma fu ### Exemplos -Os exemplos a seguir demonstram como usar "Assunto" como uma condição. 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. As seguintes secções descrevem alguns assuntos comuns que você pode usar. +Os exemplos a seguir demonstram como usar "Assunto" como uma condição. O [assunto](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) usa informações do contexto [trabalho`` trabalho da execução do fluxo de trabalho](/actions/learn-github-actions/contexts#job-context) e orienta o seu provedor na nuvem que as solicitações do token de acesso só podem ser concedidas para solicitações de fluxos de trabalho em execução em branches e ambientes específicos. As seguintes secções descrevem alguns assuntos comuns que você pode usar. #### Filtragem para um ambiente específico 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 60fcaa150a..3f672a99b9 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 @@ -19,7 +19,7 @@ topics: O OpenID Connect (OIDC) permite aos seus fluxos de trabalho de {% data variables.product.prodname_actions %} efetuar a autenticação com um HashiCorp Vault para recuperar segredos. -This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault. +Este guia fornece uma visão geral sobre como configurar o cofre HashiCorp para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada e mostra como usar essa configuração na ação [hashicorp/vault-action](https://github.com/hashicorp/vault-action) para recuperar segredos do cofre HashiCorp. ## Pré-requisitos diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index b1bd8075ff..52cc87e50c 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New self-hosted runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %} {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} @@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} @@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise {% data reusables.enterprise-accounts.actions-runners-tab %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product 1. Click **Add new**, then click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} -{% ifversion ghec or ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -{% endif %} ### Making enterprise runners available to repositories diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index 6bd6e9ab96..d756d87773 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -32,7 +32,7 @@ Cada solução tem certas especificações que podem ser importantes para consid | Tempo de execução | Kubernetes | VMs do Linux e do Windows | | Nuvens compatíveis | Azure, Amazon Web Services, Google Cloud Platform, nos locais | Amazon Web Services | | Onde os executores podem ser dimensionados | Níveis de empresa, organização e repositório. Por etiqueta do executor e grupo de executores. | Níveis de organização e repositório. Por etiqueta do executor e grupo de executores. | -| How runners can be scaled | Webhook events, Scheduled, Pull-based | Webhook events, Scheduled (org-level runners only) | +| Como os executores podem ser dimensionados | Webhook events, Scheduled, Pull-based | Webhook events, Scheduled (org-level runners only) | ## Usaar executores efêmeros para dimensionamento automático @@ -54,25 +54,25 @@ O serviço {% data variables.product.prodname_actions %} irá cancelar o resgist {% endnote %} -## Controlling runner software updates on self-hosted runners +## Controlando atualizações de software dos executores em executores auto-hospedados -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. +Por padrão, os executores auto-hospedados realizarão automaticamente uma atualização de software sempre que uma nova versão do executor estiver disponível. Se você usar executoresefêmeros em contêineres, isso pode gerar a atualizações de software repetidas quando uma nova versão do executor for lançada. A desabilitação das atualizações automáticas permite que você atualize a versão do executor na imagem do contêiner diretamente no seu próprio agendamento. -If you want to turn off automatic software updates and install software updates yourself, you can specify the `--disableupdate` parameter when starting the runner. Por exemplo: +Se você deseja desativar as atualizações automáticas de software e instalar as atualizações de software, você poderá especificar o parâmetro `--disableupdate` ao iniciar o executor. Por exemplo: ```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. +Se você desabilitar as atualizações automáticas, você ainda deverá atualizar sua versão do executor regularmente. A nova funcionalidade em {% data variables.product.prodname_actions %} exige alterações no serviço de {% data variables.product.prodname_actions %} service _e_ no software do executor. O executor pode não conseguir de processar corretamente os trabalhos que aproveitam novas funcioanlidades em {% data variables.product.prodname_actions %} sem a atualização de um software. -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). Para obter mais informações, consulte “[Configurando notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)". +Se você desabilitar as atualizações automáticas, será necessário atualizar a versão do seu executor no prazo de 30 dias a contar da nova versão disponível. Você deverá assinar para receber as notificações de versões no repositório [`actions/runner` repository](https://github.com/actions/runner/releases). Para obter mais informações, consulte “[Configurando notificações](/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). +Para obter instruções sobre como instalar a versão mais recente do executor, consulte as instruções de instalação referentes [à última versão](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. +**Observação:** Se você não executar uma atualização de software em 30 dias, o serviço de {% data variables.product.prodname_actions %} não irá colocar trabalhos na fila para o seu executor. Além disso, se uma atualização crítica de segurança for necessária, o serviço de {% data variables.product.prodname_actions %} não colocará os trabalhos na fila do seu executor até que ele seja atualizado. {% endnote %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index f4f6d9c310..7c915d6208 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -46,7 +46,7 @@ Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão Ao criar um grupo, você deverá escolher uma política que defina quais repositórios têm acesso ao grupo do executor. -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} @@ -61,12 +61,11 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Na seção "Executores auto-hospedados", clique em **Adicionar novo** e, em seguida, **Novo grupo**. +1. Em {% ifversion ghes > 3.1 or ghae %}"Executores"{% elsif ghes < 3.2 %}"Executores auto-hospedados"{% endif %}, clique em **Adicionar novo** e, em seguida, **Novo grupo**. ![Adicionar grupo de executor](/assets/images/help/settings/actions-org-add-runner-group.png) 1. Insira um nome para o seu grupo de executor e atribua uma política para acesso ao repositório. @@ -95,7 +94,7 @@ Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão Ao criar um grupo, você deve escolher uma política que defina quais organizações têm acesso ao grupo de executores. -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -113,8 +112,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -144,7 +142,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç ## Alterar a política de acesso de um grupo de executores auto-hospedados Você pode atualizar a política de acesso de um grupo de executores ou renomear um grupo de executores. -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} 1. Modifique as opções de acesso ou altere o nome do grupo dp executor. @@ -158,8 +156,7 @@ Você pode atualizar a política de acesso de um grupo de executores ou renomear Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} @@ -181,17 +178,18 @@ Não foi possível encontrar nenhum grupo de executor auto-hospedado denominado ## Mover um executor auto-hospedado para um grupo Se você não especificar o grupo de um executor durante o processo de registro, seus novos executores auto-hospedados são automaticamente atribuídos ao grupo padrão e poderão ser transferidos para outro grupo. -{% ifversion ghec or ghes > 3.1 or ghae %} + {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} 1. Na lista de "Executores", clique no executor que você deseja configurar. 2. Selecione o menu suspenso do grupo do executor. 3. Em "Transferir executor para o grupo", escolha um grupo de destino para o executor. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} -1. Na seção "executores auto-hospedados" da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png) +{% elsif ghae or ghes < 3.4 %} +1. Na seção {% ifversion ghes > 3.1 or ghae %}"Grupos de executores"{% elsif ghes < 3.2 %}"Executores auto-hospedados"{% endif %} da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png) 2. Marque a caixa de seleção ao lado do executor auto-hospedado e, em seguida, clique em **Mover para o grupo** para ver os destinos disponíveis. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. Para mover o executor, clique no grupo de destino. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} + ## Remover um grupo de executor auto-hospedado Os executores auto-hospedados são retornados automaticamente ao grupo-padrão quando seu grupo é removido. @@ -201,8 +199,7 @@ Os executores auto-hospedados são retornados automaticamente ao grupo-padrão q 1. Na lista de grupos, à direita do grupo que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 2. Para remover o grupo, clique em **Remover grupo**. 3. Revise os avisos de confirmação e, em seguida, clique em **Remover este grupo de executores**. -{% endif %} -{% ifversion ghes < 3.2 or ghae %} +{% elsif ghes < 3.2 %} 1. Na seção "Executores auto-hospedados" da página de configurações, localize o grupo que você deseja excluir e clique no botão {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} . ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. Para remover o grupo, clique em **Remover grupo**. ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index cbc55ec1c3..0230c45041 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -30,20 +30,20 @@ shortTitle: Remover executores auto-hospedados Para remover um executor auto-hospedado de um repositório de usuário, você deve ser o proprietário do repositório. Para um repositório da organização, você deve ser um proprietário da organização ou ter acesso de administrador ao repositório. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Remover um executor de uma organização {% note %} @@ -57,19 +57,20 @@ Para remover um executor auto-hospedado de um repositório de usuário, você de Para remover um executor auto-hospedado de uma organização, você deve ser um proprietário da organização. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghes > 3.3 or ghec %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% else %} +{% elsif ghes < 3.4 or ghae %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## Remover um executor de uma empresa {% ifversion fpt %} @@ -85,19 +86,17 @@ Se você usar {% endnote %} -{% data reusables.github-actions.self-hosted-runner-reusing %} +Para remover um executor auto-hospedado de uma empresa, você deverá ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte [as APIs do GitHub Actions da administração da empresa](/rest/reference/enterprise-admin#github-actions). -{% ifversion ghec %} -Para remover um executor auto-hospedado de uma conta corporativa, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como adicionar um executor auto-hospedado com a API REST, consulte [as APIs do GitHub Actions da administração da empresa](/rest/reference/enterprise-admin#github-actions). +{% data reusables.github-actions.self-hosted-runner-reusing %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% elsif ghae or ghes %} -Para remover um executor auto-hospedado no nível da empresa de -{% data variables.product.product_location %}, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 573436c429..ceb170b4a8 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -19,13 +19,13 @@ Para obter informações sobre como usar etiquetas para encaminhar trabalhos par {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} ## Criar etiquetas personalizadas -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} 1. Na seção "Etiquetas", clique em {% octicon "gear" aria-label="The Gear icon" %}. 1. No campo "Encontrar ou criar uma etiqueta", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} @@ -34,35 +34,38 @@ Para obter informações sobre como usar etiquetas para encaminhar trabalhos par O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## Atribuir uma etiqueta a um executor auto-hospedado -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. Para atribuir uma etiqueta ao executor auto-hospedado, no campo "Localizar ou criar uma etiqueta", clique na etiqueta. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. Clique em uma etiqueta a ser atribuída ao seu executor auto-hospedado. {% endif %} + ## Remover uma etiqueta personalizada de um executor auto-hospedado -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. No campo "Encontre ou crie uma etiqueta", as etiquetas atribuídas são marcadas com a Ícone de {% octicon "check" aria-label="The Check icon" %}. Clique em uma etiqueta marcada para cancelar a atribuição do seu executor auto-hospedado. -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. Clique na etiqueta atribuída para removê-la do seu executor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## Usar o script de configuração para criar e atribuir rótulos Você pode usar o script de configuração no executor auto-hospedado para criar e atribuir etiquetas personalizadas. Por exemplo, este comando atribui ao executor auto-hospedado uma etiqueta denominada `gpu`. diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md index 652b73305d..6ea946014c 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md +++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md @@ -73,7 +73,7 @@ A tabela a seguir indica onde cada contexto e função especial pode ser utiliza | concorrência | github, entradas | | | env | github, segredos, entradas | | | jobs.<job_id>.concurrency | github, necessidades, estratégia, matriz, entradas | | -| jobs.<job_id>.container | github, necessidades, estratégia, matriz, entradas | | +| jobs.<job_id>.container | github, necessidades, estratégia, matriz, segredos, entradas | | | jobs.<job_id>.container.credentials | github, necessidades, estratégia, matrix, env, segredos, entradas | | | jobs.<job_id>.container.env.<env_id> | github, necessidades, estratégia, matrix, trabalho, executor, env, segredos, entradas | | | jobs.<job_id>.continue-on-error | github, necessidades, estratégia, matriz, entradas | | @@ -393,7 +393,7 @@ O contexto `etapas` contém informações sobre as etapas do trabalho atual que | Nome da propriedade | Tipo | Descrição | | --------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `steps` | `objeto` | Esse contexto altera cada etapa em um trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. Este objeto contém todas as propriedades listadas abaixo. | -| `steps..outputs` | `objeto` | Conjunto de saídas definidas para a etapa. 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..outputs` | `objeto` | Conjunto de saídas definidas para a etapa. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)". | | `steps..conclusion` | `string` | O resultado de uma etapa concluída após [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`. | | `steps..outcome` | `string` | O resultado de uma etapa concluída antes de [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`. | | `steps..outputs.` | `string` | Valor de uma saída específica. | diff --git a/translations/pt-BR/content/actions/learn-github-actions/expressions.md b/translations/pt-BR/content/actions/learn-github-actions/expressions.md index ad2c38f04f..2c7a72a544 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md @@ -50,12 +50,12 @@ env: Como parte da expressão, você pode usar os tipos de dados `boolean`, `null`, `number` ou `string`. -| Tipo de dados | Valor do literal | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `boolean` | `true` ou `false` | -| `null` | `null` | -| `number` | Qualquer formato de número aceito por JSON. | -| `string` | Você não precisa anexar strings em {% raw %}${{{% endraw %} e {% raw %}}}{% endraw %}. However, if you do, you must use single quotes around the string and escape literal single quotes with an additional single quote. | +| Tipo de dados | Valor do literal | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `boolean` | `true` ou `false` | +| `null` | `null` | +| `number` | Qualquer formato de número aceito por JSON. | +| `string` | Você não precisa anexar strings em `{% raw %}${{{% endraw %}` e `{% raw %}}}{% endraw %}`. No entanto, se o fizer, você deverá usar aspas simples (`'`) em torno da 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. | #### Exemplo diff --git a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md index 16fe3ea193..7e3f731724 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -47,7 +47,7 @@ Você pode pesquisar ações diretamente no seu editor do seu fluxo de trabalho Você pode adicionar uma ação ao seu fluxo de trabalho fazendo referência à ação no arquivo do seu fluxo de trabalho. -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).” +Você pode visualizar as ações referenciadas em seus fluxos de trabalho de {% data variables.product.prodname_actions %} como dependências no gráfico de dependências do repositório que contém seus fluxos de trabalho. Para obter mais informações, consulte “[Sobre o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”. ### Adicionando uma ação de {% data variables.product.prodname_marketplace %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md index ac13eaa5ff..7743a83067 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md @@ -259,4 +259,4 @@ Para entender como a cobrança funciona para {% data variables.product.prodname_ ## Leia mais {% 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 %} +- "[Sobre {% data variables.product.prodname_actions %} para as empresas](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %} 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 a949fddb04..5ac68ab8b2 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,12 +18,12 @@ 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 %} +{% data reusables.repositories.about-github-actions %} Para obter mais informações, consulte "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" e "[Sobre {% data variables.product.prodname_actions %} para empresas](/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 %} -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)." +O uso do GitHub Actions é grátis para instâncias de {% data variables.product.prodname_ghe_server %} que usam executores auto-hospedados. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% endif %} diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index a5a0da38a8..54770117e6 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -63,7 +63,7 @@ O Jenkins usa diretivas para gerenciar os _Declarative Pipelines_. Essas diretiv | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`ambiente`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
[`jobs..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..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
[`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
[`jobs..timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) | -| [`parâmetros`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)
[`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) | +| [`parâmetros`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`entradas`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)
[`saídas`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) | | [`gatilhos`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on)
[`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)
[on..paths](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) | | [`aciona { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs..needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) | | [Sintaxe cron do Jenkins](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/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index ff449845c9..d4617e6230 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -96,7 +96,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -167,7 +167,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -246,7 +246,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: {% raw %} 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 b7825a578f..cbb4a4a810 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 @@ -85,8 +85,9 @@ A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão | 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 | +| Implantações | leitura/gravação | nenhum | read |{% ifversion fpt or ghec %} +| id-token | leitura/gravação | nenhum | read +{% endif %} | Problemas | leitura/gravação | nenhum | leitura | | metadados | leitura | leitura | leitura | | pacotes | leitura/gravação | nenhum | leitura | 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 65f2a399db..01feec3181 100644 --- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md +++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md @@ -356,30 +356,30 @@ Os segredos são limitados a 64 kB. Para usar segredos maiores que 64 kB, você {% endraw %} -## Storing Base64 binary blobs as secrets +## Armazenar Blobs binários de Base64 como segredos -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). +Você pode usar a codificação de Base64 para armazenar pequenos blobs binários como segredos. Em seguida, você pode fazer referência ao segredo no seu fluxo de trabalho e decodificá-lo para usar no executor. Para os limites de tamanho, consulte ["Limites para segredos"](/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. +**Observação**: Observe que o Base64 só converte números binários em texto e não substitui a criptografia real. {% endnote %} -1. Use `base64` to encode your file into a Base64 string. Por exemplo: +1. Use `base64` para codificar seu arquivo em uma string de Base64. Por exemplo: ``` $ base64 -i cert.der -o cert.base64 ``` -1. Create a secret that contains the Base64 string. Por exemplo: +1. Crie um segredo que contenha a string de Base64. 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: +1. Para acessar a string de Base64 do seu executor, transforme segredo em `base64 --decode`. Por exemplo: ```yaml name: Retrieve Base64 secret diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md index 72a7a8808f..57905a4c44 100644 --- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -202,6 +202,10 @@ Os mesmos princípios descritos acima para o uso de ações de terceiros também {% data reusables.actions.outside-collaborators-internal-actions %} Para obter mais informações, consulte "[Compartilhando ações e fluxos de trabalho com a sua empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)". {% endif %} +## Usando os Scorecards OpenSSF para proteger fluxos de trabalho + +[Scorecards](https://github.com/ossf/scorecard) é uma ferramenta de segurança automatizada que sinaliza práticas arriscadas da cadeia de suprimentos. Você pode usar a [ação Scorecards](https://github.com/marketplace/actions/ossf-scorecard-action) e o [fluxo de trabalho iniciante](https://github.com/actions/starter-workflows) para seguir as práticas recomendadas de segurança. Uma vez configurada, a ação Scorecards é executada automaticamente nas alterações de repositórios e alerta de desenvolvedores sobre práticas arriscadas em cadeia de suprimentos que usam a experiência de digitalização embutida do código. O projeto Scorecards executa um número de verificações, incluindo ataques de injeção de script, permissões de token e ações fixadas. + ## Possível impacto de um executor comprometido Essas seções consideram alguns das etapas que um invasor pode dar se for capaz de executar comandos maliciosos em um executor de {% data variables.product.prodname_actions %}. diff --git a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md index cc041edef3..107c7b7fff 100644 --- a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/pt-BR/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: @@ -996,9 +992,9 @@ em: ### `versão` -| Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ------------- | -| [`versão`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | Último commit na versão com tag | Tag da versão | +| Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | +| ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ----------------------------------------------- | +| [`versão`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | Último commit na versão com tag | Tag ref of release `refs/tags/` | {% note %} diff --git a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md index 9a6a8a5595..33d61ce792 100644 --- a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md @@ -34,7 +34,7 @@ Se você reutilizar um fluxo de trabalho de um repositório diferente, todas as Quando um fluxo de trabalho reutilizável é acionado por um fluxo de trabalho de chamadas, o contexto `github` está sempre associado ao fluxo de trabalho de chamada. O fluxo de trabalho chamado tem acesso automaticamente a `github.token` e `secrets.GITHUB_TOKEN`. Para obter mais informações sobre o contexto do github ``, consulte "[Contexto e sintaxe de expressão para o 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).” +Você pode visualizar os fluxos de trabalho referenciados nos seus fluxos de trabalho de {% data variables.product.prodname_actions %} como dependências no gráfico de dependências do repositório que contém seus fluxos de trabalho. Para obter mais informações, consulte “[Sobre o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”. ### Fluxos de trabalho e fluxos de trabalho iniciais reutilizáveis diff --git a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md index bf4729df01..d25ca23a33 100644 --- a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md +++ b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md @@ -128,9 +128,9 @@ Use a chave `on` para especificar quais eventos acionam o seu fluxo de trabalho. {% 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 +## Definindo entradas, saídas e segredos para fluxos de trabalho reutilizáveis -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)." +É possível definir entradas e segredos que um fluxo de trabalho reutilizável deve receber de um fluxo de trabalho chamado. Também é possível especificar saídas que um fluxo de trabalho reutilizável disponibilizará para um fluxo de trabalho chamado. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/using-workflows/reusing-workflows)". {% endif %} @@ -140,7 +140,7 @@ As informações sobre o evento que desencadeou uma execução de fluxo de traba ### Visualizando todas as propriedades de um evento -Referência à documentação de evento de webhook para propriedades comuns e cargas de exemplo. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)." +Referência à documentação de evento de webhook para propriedades comuns e cargas de exemplo. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)". Você também pode imprimir o contexto inteiro de `github.event` para ver quais propriedades estão disponíveis para o evento que acionou o seu fluxo de trabalho: diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md index 4ca6ad2045..c92dd9632d 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -92,7 +92,7 @@ A tabela a seguir mostra quais funções do conjunto de ferramentas estão dispo Configura um parâmetro de saída da ação. -Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. 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)." +Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)". ### Exemplo @@ -314,7 +314,9 @@ Durante a execução de um fluxo de trabalho, o executor gera arquivos temporár {% warning %} -**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão. Certifique-se de escrever os arquivos usando a codificação correta. Por exemplo, você deve definir a codificação UTF-8 ao definir o caminho: +**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão. + +When using `shell: powershell`, you must specify UTF-8 encoding. Por exemplo: ```yaml jobs: @@ -325,22 +327,7 @@ jobs: run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Ou mude para PowerShell Core, cujo padrão é UTF-8: - -```yaml -jobs: - modern-pwsh-example: - uses: windows-2019 - steps: - - shell: pwsh - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8 -``` - -Mais detalhes sobre UTF-8 e PowerShell Core encontrados nesta excelente [resposta do Stack Overflow](https://stackoverflow.com/a/40098904/162694): - -> ### Leitura opcional: A perspectiva entre plataformas: PowerShell _Core_: -> -> [O PowerShell agora é multiplataforma](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), por meio da sua edição do **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)**, cuja codificação - sensívelmente - *** é igual a ***BOM-less UTF-8******, em linha com plataformas do Unix. +Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8. {% endwarning %} 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..a8337f8e28 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 @@ -757,6 +757,8 @@ strategy: ## `jobs..container` +{% data reusables.github-actions.docker-container-os-support %} + {% data reusables.actions.jobs.section-running-jobs-in-a-container %} ### `jobs..container.image` @@ -830,7 +832,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 +975,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`

`every/tag` | | `'*feature'` | O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `mona-feature`

`feature`

`ver-10-feature` | | `v2*` | Corresponde aos nomes de branches e tags que iniciam com `v2`. | `v2`

`v2.0`

`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`

`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`

`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/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index c441c63d2a..fc92d11de1 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -700,7 +700,7 @@ Todos os testes de armazenamento aprovados O `ghe-migrator` é uma ferramenta de alta fidelidade que ajuda a fazer migrações de uma instância do GitHub para outra. Você pode consolidar suas instâncias ou mover a organização, os usuários, as equipes e os repositórios do GitHub.com para o {% data variables.product.prodname_enterprise %}. -Para obter mais informações, consulte nosso guia sobre [como migrar dados de usuário, organização e repositório](/enterprise/admin/guides/migrations/). +Para obter mais informações, consulte nossos guias sobre [migração de dados para a sua empresa](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). ### git-import-detect 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 8d7334316d..36f66620c8 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. 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 `-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 "Usando comandos de backup e restauração" do [LEIAME do {% data variables.product.prodname_enterprise_backup_utilities %}](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 6cda083d1e..e90307d494 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,11 +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://` ao definir ou mudar a configuração de {% data variables.product.prodname_actions %}. -## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname +## Os executores não se conectam a {% data variables.product.prodname_ghe_server %} com um novo nome de host {% 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. +Se você implantar {% data variables.product.prodname_ghe_server %} no seu ambiente com um novo nome de host e o antigo nome de host não resolver mais a sua instância, os executores auto-hospedados não conseguirão conectar-se ao nome de host antigo e não executarão nenhum trabalho. 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/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 24633faf3d..d565787706 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -1,7 +1,7 @@ --- -title: About GitHub Actions for enterprises +title: Sobre o GitHub Actions para empresas shortTitle: Sobre ações do GitHub -intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.' +intro: '{% data variables.product.prodname_actions %} pode melhorar a produtividade do desenvolvedor automatizando o ciclo de desenvolvimento de software da sua empresa.' versions: ghec: '*' ghes: '*' @@ -12,31 +12,31 @@ topics: - Enterprise --- -With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow. +Com {% data variables.product.prodname_actions %}, você pode melhorar a produtividade do desenvolvedor automatizando todas as fases do fluxo de trabalho de desenvolvimento de software da sua empresa. -| Tarefa | Mais informações | -| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Automatically test and build your application | [Sobre integração contínua](/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)" | +| Tarefa | Mais informações | +| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Testar e compilar automaticamente o seu aplicativo | [Sobre integração contínua](/actions/automating-builds-and-tests/about-continuous-integration) | +| Implantar seu aplicativo | "[Sobre a implantação contínua](/actions/deployment/about-deployments/about-continuous-deployment)" | +| Empacotar código automaticamente e com segurança em artefatos e contêineres | "[Sobre empacotamento com {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" | +| Automatize suas tarefas de gerenciamento de projetos | "[Usando {% data variables.product.prodname_actions %} para gerenciamento de projeto](/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 %} ajuda a sua equipe a trabalhar mais rápido e em escala. Quando grandes repositórios começam a usar o {% data variables.product.prodname_actions %}, as equipes fazem merge de um número significativamente maior de pull requests por dia, e os pull requests são mesclados muito mais rapidamente. Para obter mais informações, consulte "[Gravação e envio mais rápido de código](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" no estado do 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 %} também fornece maior controle sobre implantações. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir ou restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos.{% ifversion ghec or ghae-issue-4856 %} Se os seus fluxos de trabalho precisarem acessar recursos de um provedor de nuvem compatível com o OpenID Connect (OIDC), você poderá configurar seus fluxos de trabalho para efetuar a autenticação diretamente no provedor de nuvem. Isso permitirá que você pare de armazenar credenciais como segredos de longa duração e irá fornecer outros benefícios de segurança. Para obter mais informações, consulte[Sobre segurança fortalecida com 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. +{% data variables.product.prodname_actions %} é intuitivo para o desenvolvedor, pois está integrado diretamente à experiência familiar de {% data variables.product.product_name %}. -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. Para obter mais informações, consulte "[Localizar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)". +Você pode criar suas próprias automações exclusivas ou você pode usar e adaptar os fluxos de trabalho do nosso ecossistema de mais de 10, 00 ações construídas por líderes do setor e pela comunidade de código aberto. Para obter mais informações, consulte "[Localizar e personalizar ações](/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)." +{% ifversion ghec %}Você pode desfrutar da conveniência de executores hospedados em {% data variables.product.company_short %}, que são mantidos e atualizados por {% data variables.product.company_short %} ou você{% else %}{% endif %} pode controlar a sua própria infraestrutura privada de CI/CD usando executores auto-hospedados. Os executores auto-hospedados permitem que você determine o ambiente exato e os recursos que completam suas compilações, testes e implantações sem expor o seu ciclo de desenvolvimento de software à internet. Para obter mais informações, consulte {% ifversion ghec %}"[Sobre executores auto-hospedados em {% data variables.product.company_short %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e {% endif %} "[Sobre executores auto-hospedados](/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. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". +{% data variables.product.prodname_actions %} também inclui ferramentas para governar o ciclo de desenvolvimento de software da sua empresa e atender às obrigações de conformidade. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/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. +Para saber mais sobre como você pode fazer a adoção de {% data variables.product.prodname_actions %} com sucesso para sua empresa, siga o caminho de aprendizado "[Adotando {% data variables.product.prodname_actions %} para a sua empresa](/admin/guides#adopt-github-actions-for-your-enterprise)". ## Leia mais -- "[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 %} +- "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %} +- "[Sobre a cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 9ddb86cb63..0d82557bc7 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -14,7 +14,7 @@ topics: ## Sobre {% data variables.product.prodname_actions %} para empresas -{% data reusables.actions.about-actions %} com {% data variables.product.prodname_actions %}, sua empresa pode automatizar, personalizar e executar seus fluxos de trabalho de desenvolvimento de software como testes e implantações. 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)." +{% data reusables.actions.about-actions %} com {% data variables.product.prodname_actions %}, sua empresa pode automatizar, personalizar e executar seus fluxos de trabalho de desenvolvimento de software como testes e implantações. Para obter mais informações, consulte a seção "[Sobre o {% data variables.product.prodname_actions %} para empresas ](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)". ![Diagrama de trabalhos em execução em executores auto-hospedados](/assets/images/help/images/actions-enterprise-overview.png) diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md index 5ca5675755..993c9e95cd 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md @@ -47,7 +47,7 @@ Nós testamos e oferecemos compatibilidade oficial os seguintes IdPs. Para o SSO | -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:| | 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" %} +| Okta | {% 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/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/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md index 94a59a4a6f..d666cf4502 100644 --- 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 @@ -1,6 +1,6 @@ --- -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.' +title: Acessando relatórios de conformidade para a sua empresa +intro: 'Você pode acessar as denúncias de conformidade de {% data variables.product.company_short %}, como nossos relatórios SOC e auto-avaliação da Cloud Security Alliance CAIQ (CSA CAIQ), para a sua empresa.' versions: ghec: '*' type: how_to @@ -9,23 +9,23 @@ topics: - Enterprise - Fundamentals permissions: Enterprise owners can access compliance reports for the enterprise. -shortTitle: Access compliance reports +shortTitle: Acessar relatórios de conformidade --- -## About {% data variables.product.company_short %}'s compliance reports +## Sobre os relatórios de conformidade de {% data variables.product.company_short %} -You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings. +Você pode acessar os relatórios de conformidade de {% data variables.product.company_short %} nas configurações da empresa. {% data reusables.security.compliance-report-list %} -## Accessing compliance reports for your enterprise +## Acessando relatórios de conformidade para a sua empresa {% 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**. +1. Em "Resources", à direita do relatório que você deseja acessar, clique em {% octicon "download" aria-label="The Download icon" %} **Download** ou {% octicon "link-external" aria-label="The external link icon" %} **Visualizar**. {% 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)" +- "[Acessando os relatórios de conformidade para a sua organização](/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/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index dadae44d60..576432e201 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -100,7 +100,7 @@ Você pode aplicar políticas para controlar como {% data variables.product.prod {% 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. +Se uma política for habilitada para uma empresa, ela poderá ser desabilitada seletivamente em organizações individuais ou repositórios. Se uma política estiver desabilitada para uma empresa, as organizações individuais ou repositórios não poderão habilitá-la. {% data reusables.github-actions.private-repository-forks-options %} 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 75aaf2ce9f..cebec74733 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 @@ -148,6 +148,6 @@ A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no {% ifversion ghec or ghae %} ## Leia mais -- "[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 %} +- "[Sobre a identidade e gerenciamento de acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %} +- "[Relatórios de conformidade para a sua empresa](/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 | -|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 
auto-merge deployment api
| 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 | -| 
blob#save
| Mudar para o conteúdo de um arquivo na interface web | "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)" | -| 
branch merge api
| Merge de um branch através da API | "[Mesclar um branch](/rest/reference/branches#merge-a-branch)" na documentação da API REST | -| 
branches page delete button
| 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)" | -| 
git refs create api
| 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 | -| 
git refs delete api
| 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 | -| 
git refs update api
| 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 | -| 
git repo contents api
| 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 | -| 
merge base into head
| 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)" | -| 
pull request branch delete button
| 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)" | -| 
pull request branch undo button
| 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)" | -| 
pull request merge api
| Merge de um pull request através da API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" na documentação da API REST | -| 
pull request merge button
| 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)" | -| 
pull request revert button
| Reverter um pull request | "[Reverter uma pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | -| 
releases delete button
| 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)" | -| 
stafftools branch restore
| Restauração de um branch do painel de administração do site | "[Painel de administração do site](/admin/configuration/site-admin-dashboard#repositories)" | -| 
tag create api
| 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 | -| 
slumlord (#SHA)
| Commit por meio do Subversion | "[Compatibilidade para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | -| 
web branch create
| 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 | +|:-------------------------- |:--------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 
auto-merge deployment api
| 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 | +| 
blob#save
| Mudar para o conteúdo de um arquivo na interface web | "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)" | +| 
branch merge api
| Merge de um branch através da API | "[Mesclar um branch](/rest/reference/branches#merge-a-branch)" na documentação da API REST | +| 
branches page delete button
| 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)" | +| 
git refs create api
| 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 | +| 
git refs delete api
| 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 | +| 
git refs update api
| 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 | +| 
git repo contents api
| 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 %} +| 
merge base into head
| 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)" | | 
pull request branch delete button
| 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)" | | 
pull request branch undo button
| 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)" | | 
pull request merge api
| Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation | | 
pull request merge button
| 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)" | | 
pull request revert button
| Revert of a pull request | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | | 
releases delete button
| Deletion of a release | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | | 
stafftools branch restore
| Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | | 
tag create api
| Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | | 
slumlord (#SHA)
| Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | | 
web branch create
| 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/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md index b9ee2bf230..68c26a6660 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md @@ -99,7 +99,7 @@ shortTitle: Exportar da sua empresa > logout > Connection to hostname closed. ``` -9. Copie o arquivo de migração para o seu computador usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp). O arquivo terá o nome do GUID de Migração: +9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. O arquivo terá o nome do GUID de Migração: ```shell $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop ``` diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md index 3d5fefbed1..12d9cca47a 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md @@ -20,7 +20,7 @@ shortTitle: Prepare-se para fazer a migração dos dados ## Preparar os dados migrados para importação para {% data variables.product.prodname_ghe_server %} -1. Usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie o arquivo de migração gerado na organização ou instância de origem para o destino no {% data variables.product.prodname_ghe_server %}: +1. Usando o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp), copie o arquivo de migração gerado na organização ou instância de origem para o destino no {% data variables.product.prodname_ghe_server %}: ```shell $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/ @@ -44,7 +44,7 @@ shortTitle: Prepare-se para fazer a migração dos dados $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv ``` - Se nenhum conflito for relatado, você poderá importar os dados com segurança seguindo as etapas em "[Migrar dados para a sua empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)". -2. Se houver conflitos, usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie *conflicts.csv* para o seu computador local: +2. Se houver conflitos, usando o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp), copie *conflicts.csv* para o seu computador local: ```shell $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop ``` @@ -134,7 +134,7 @@ O mesmo processo pode ser usado para criar mapeamentos em cada registro compatí ### Aplicar dados de migração modificados -1. Depois de fazer as alterações, use o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) para aplicar o seu *conflicts.csv* modificado (ou qualquer outro arquivo de mapeamento *.csv* no formato correto) para a instância de destino: +1. Depois de fazer as alterações, use o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) para aplicar o seu *conflicts.csv* modificado (ou qualquer outro arquivo de mapeamento *.csv* no formato correto) para a instância de destino: ```shell $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/ diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md index 417370582f..8b03a3ef80 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md @@ -29,7 +29,7 @@ Você pode recuperar uma lista de endereços IP do {% data variables.product.pro Esses endereços IP são usados por {% data variables.product.prodname_dotcom %} para fornecer nosso conteúdo, webhooks e executar compilações de {% data variables.product.prodname_actions %} hospedadas. -Esses intervalos estão na [notação CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). É possível usar uma ferramenta de conversão online, como essa [Calculadora Supernet CIDR/VLSM](http://www.subnet-calculator.com/cidr.php), para fazer a conversão de notação CIDR em intervalos de endereços IP. +Esses intervalos estão na [notação CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool to convert from CIDR notation to IP address ranges, for example: [CIDR to IPv4 conversion site](https://www.ipaddressguide.com/cidr). Nós alteramos nossos endereços IP de vez em quando. Não recomendamos permitir por endereço IP. No entanto, se você usar esses intervalos de IP, é altamente recomendável o monitoramento regular da nossa API. 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 1da8ac4c25..24a48ffcd1 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,8 +18,8 @@ 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**. +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} +3. Na seção "Segurança" na barra lateral, clique em **{% octicon "key" aria-label="The key icon" %} Implantar chaves**. {% 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 %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index 4e8b030f51..f0019c2183 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -22,8 +22,8 @@ shortTitle: Log de segurança O log de segurança lista todas as ações realizadas nos últimos 90 dias. {% data reusables.user_settings.access_settings %} -{% 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**. +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} +1. Na seção "Arquivos" da barra lateral, clique em **Registro de segurança de {% octicon "log" aria-label="The log icon" %}**. {% else %} 1. Na barra lateral de configurações do usuário, clique em **log de segurança**. ![Aba do log de segurança](/assets/images/help/settings/audit-log-tab.png) {% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 485706716c..b230ae40d3 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -24,7 +24,7 @@ shortTitle: Atualizar credenciais de acesso 1. Para solicitar uma nova senha, acesse {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. 2. Insira o endereço de e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e, em seguida, clique em **em Enviar e-mail de redefinição de senha.** O e-mail será enviado para o endereço de e-mail de backup, se você tiver um configurado. ![Caixa de diálogo para solicitar e-mail de redefinição de senha](/assets/images/help/settings/password-recovery-email-request.png) 3. Nós enviaremos por e-mail um link para você redefinir sua senha. Clique nele em até 3 horas após o recebimento do e-mail. Se você não receber o e-mail com o link, verifique sua pasta de spam. -4. Se você tiver habilitado a autenticação de dois fatores, será solicitado que você crie suas credenciais de 2FA. Digite as suas credenciais de 2FA ou um de seus códigos de recuperação de 2FA e clique em **Verificar**. ![Instrução de autenticação de dois fatores](/assets/images/help/2fa/2fa-password-reset.png) +4. Se você tiver habilitado a autenticação de dois fatores, será solicitado que você crie suas credenciais de 2FA. Digite o seu código de autenticação ou um dos seus códigos de recuperação e clique em **Verificar**. Se você adicionou uma chave de segurança à sua conta, você pode inserir a chave e clicar em **Usar a chave de segurança** ao invés de digitar um código de autenticação. ![Instrução de autenticação de dois fatores](/assets/images/help/2fa/2fa-password-reset.png) 5. Digite uma nova senha, confirme a sua nova senha e clique em **Alterar senha**. Para ajudar a criar uma senha forte, consulte "[Criar uma senha forte](/articles/creating-a-strong-password)". {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} ![Caixa para recuperar senha](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 9782828eb5..30eb1ff3ad 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -20,7 +20,10 @@ shortTitle: Recuperar uma conta com 2FA {% warning %} -**Aviso**: {% data reusables.two_fa.support-may-not-help %} +**Avisos**: + +- {% data reusables.two_fa.support-may-not-help %} +- {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} @@ -28,12 +31,21 @@ shortTitle: Recuperar uma conta com 2FA ## Usar um código de recuperação da autenticação de dois fatores -Use um dos códigos de recuperação para obter acesso automaticamente à sua conta. Seus códigos de recuperação podem estar salvos em um gerenciador de senhas ou na pasta de downloads do seu computador. O nome padrão do arquivo de códigos de recuperação é `github-recovery-codes.txt`. Para obter mais informações sobre códigos de recuperação, consulte "[Configurar métodos de recuperação da autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)". +Use um dos códigos de recuperação para obter acesso automaticamente à sua conta. Seus códigos de recuperação podem estar salvos em um gerenciador de senhas ou na pasta de downloads do seu computador. O nome padrão do arquivo de códigos de recuperação é `github-recovery-codes.txt`. Para obter mais informações sobre códigos de recuperação, consulte "[Configurar métodos de recuperação da autenticação de dois fatores](/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. Em "Encontrou algum problema?", clique em **Insira um código de recuperação de dois fatores**. ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %} -2. Na página da 2FA, em "Don't have your phone?" (Não está com seu telefone?), clique em **Enter a two-factor recovery code** (Digite um código de recuperação de dois fatores). ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -3. Digite um dos seus códigos de recuperação e clique em **Verify** (Verificar). ![Campo para digitar um código de recuperação e botão Verify (Verificar)](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) +{% data reusables.two_fa.username-password %} + +{% ifversion fpt or ghec %} +1. Em "Encontrou algum problema?", clique em **Use um código de recuperação ou solicite a redefinição**. + + ![Captura de tela do link para usar um código de recuperação](/assets/images/help/2fa/2fa-recovery-code-link.png) +{%- else %} +1. Na página da 2FA, em "Don't have your phone?" (Não está com seu telefone?), clique em **Enter a two-factor recovery code** (Digite um código de recuperação de dois fatores). + + ![Captura de tela do link para usar um código de recuperação](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} +1. Digite um dos seus códigos de recuperação e clique em **Verify** (Verificar). + + ![Campo para digitar um código de recuperação e botão Verify (Verificar)](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) {% ifversion fpt or ghec %} ## Autenticar com um número de telefone alternativo @@ -43,38 +55,52 @@ Se você perder o acesso ao seu aplicativo TOTP principal ou número de telefone ## Autenticar com uma chave de segurança -Se você configurou a autenticação de dois fatores com uma chave de segurança, você pode usar a chave de segurança como método de autenticação secundário para reaver automaticamente o acesso à sua conta. Para obter mais informações, consulte "[Configurar autenticação de dois fatores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". +Se você configurou a autenticação de dois fatores com uma chave de segurança, você pode usar a chave de segurança como método de autenticação secundário para reaver automaticamente o acesso à sua conta. Para obter mais informações, consulte "[Configurar autenticação de dois fatores](/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 %} ## Efetuar a autenticação com um dispositivo verificado, token SSH ou token de acesso pessoal -Se você sabe sua senha do {% data variables.product.product_name %} mas não tem credenciais de autenticação de dois fatores ou seus códigos de recuperação de autenticação de dois fatores, você pode ter uma senha única enviada para o seu endereço de e-mail verificado para começar o processo de verificação e recuperar o acesso à sua conta. +Se você souber a sua senha para {% data variables.product.product_location %}, mas não tiver credenciais de autenticação de dois fatores ou seus códigos de recuperação de autenticação em de dois fatores, você poderá receber por e-mail uma senha única para começar o processo de verificação e recuperar o acesso à sua conta. {% note %} -**Observação**: Por razões de segurança, recuperar o acesso à sua conta efetuando a autenticação com uma senha única pode levar de 3 a 5 dias úteis. Os pedidos adicionais enviados durante este período não serão revisados. +**Observação**: Por razões de segurança, a recuperação do acesso à sua conta efetuando a autenticação com uma senha única pode levar até três dias úteis. {% data variables.product.company_short %} não analisará solicitações adicionais enviadas nesse tempo. {% endnote %} Você pode usar as suas credenciais de autenticação de dois fatores ou os códigos de recuperação de dois fatores para recuperar o acesso à sua conta a qualquer momento no período de espera de 3 a 5 dias. -1. Digite seu nome de usuário e senha para solicitar autenticação. Se você não sabe sua senha de {% data variables.product.product_name %}, você não poderá gerar uma senha única. -2. Em "Encontrou algum problema?", clique em **Não consegue acessar seu dispositivo de dois fatores ou códigos de recuperação válidos?** ![Faça o link, se você não tiver seu dispositivo de 2FA ou códigos de recuperação](/assets/images/help/2fa/no-access-link.png) -3. Clique em **Eu entendo, começar** para solicitar uma redefinição das suas configurações de autenticação. ![Botão de redefinição da configuração de autenticação](/assets/images/help/2fa/reset-auth-settings.png) -4. Clique em **Enviar senha de uso único** para enviar uma senha de uso único para todos os endereços de e-mail associados à sua conta. ![Botão para enviar a senha de uso único](/assets/images/help/2fa/send-one-time-password.png) -5. Em "Única senha", digite a senha temporária do endereço e-mail de recuperação {% data variables.product.prodname_dotcom %} enviada. ![Campo para a senha de uso único](/assets/images/help/2fa/one-time-password-field.png) -6. Clique **Verificar endereço de e-mail**. -7. Escolha um fator de verificação alternativo. +1. Digite seu nome de usuário e senha para solicitar autenticação. + + {% warning %} + + **Aviso**: {% data reusables.accounts.you-must-know-your-password %} + + {% endwarning %} +1. Em "Encontrou algum problema?", clique em **Use um código de recuperação ou solicite a redefinição**. + + ![Captura de tela do link se você não tiver seu dispositivo 2FA ou códigos de recuperação](/assets/images/help/2fa/no-access-link.png) +1. À direita de "Bloqueado?", clique em **Tente recuperar sua conta**. + + ![Captura de tela do link para tentar recuperar sua conta](/assets/images/help/2fa/try-recovering-your-account-link.png) +1. Clique em **Eu entendo, começar** para solicitar uma redefinição das suas configurações de autenticação. + + ![Captura de tela do botão para iniciar a redefinição das configurações de autenticação](/assets/images/help/2fa/reset-auth-settings.png) +1. Clique em **Enviar senha de uso único** para enviar uma senha de uso único para todos os endereços de e-mail elegível associados à sua conta. Apenas e-mails verificados são elegíveis para a recuperação de conta. Se você restringiu as redefinições de senha para seus endereços primários e/ou de backup, esses endereços são os únicos elegíveis para a recuperação de conta. + + ![Captura de tela do botão para enviar uma senha única](/assets/images/help/2fa/send-one-time-password.png) +1. Em "Única senha", digite a senha temporária do endereço e-mail de recuperação {% data variables.product.prodname_dotcom %} enviada. + + ![Captura de tela do campo para digitar senha única](/assets/images/help/2fa/one-time-password-field.png) +1. Clique **Verificar endereço de e-mail**. + + ![Captura de tela do botão para verificar o endereço de e-mail](/assets/images/help/2fa/verify-email-address.png) +1. Escolha um fator de verificação alternativo. - Se você usou seu dispositivo atual para acessar essa conta antes e gostaria de usar o dispositivo para verificação, clique em **Verificar com este dispositivo**. - Se você já configurou uma chave SSH nesta conta e gostaria de usar a chave SSH para verificação, clique na **chave SSH**. - - Se você já configurou um token de acesso pessoal anteriormente e gostaria de usar o token de acesso pessoal para verificação, clique em **Token de acesso pessoal**. ![Botões de verificação alternativa](/assets/images/help/2fa/alt-verifications.png) -8. Um integrante do {% data variables.contact.github_support %} irá rever a sua solicitação e o seu endereço de e-mail de 3 a 5 dias úteis. Se a sua solicitação for aprovada, você receberá um link para concluir o processo de recuperação de conta. Se sua solicitação for negada, o e-mail incluirá uma forma de entrar em contato com o suporte para esclarecer outras dúvidas. + - Se você já configurou um token de acesso pessoal anteriormente e gostaria de usar o token de acesso pessoal para verificação, clique em **Token de acesso pessoal**. + + ![Captura de tela de botões para verificação alternativa](/assets/images/help/2fa/alt-verifications.png) +1. Um integrante de {% data variables.contact.github_support %} irá revisar a sua solicitação e enviar um e-mail para você em três dias úteis. Se a sua solicitação for aprovada, você receberá um link para concluir o processo de recuperação de conta. Se sua solicitação for negada, o e-mail incluirá uma forma de entrar em contato com o suporte para esclarecer outras dúvidas. {% endif %} - -## Leia mais - -- [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)" -- "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)" -- "[Configurar métodos de recuperação de autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)" -- "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication)" diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index f4a565e01c..4c757040af 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -76,7 +76,7 @@ No final do mês, {% data variables.product.prodname_dotcom %} calcula o custo d ### Cálculo de custo de amostra em minutos -Por exemplo, se sua organização usa {% data variables.product.prodname_team %} e permite gastos ilimitados, usando 15.000 minutos, poderia ter um custo total de armazenamento e custo médio de minuto de US$ 56,00, dependendo dos sistemas operacionais usados para executar trabalhos. +For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. - 5.000 (3.000 Linux e 2.000 Windows) minutos = US$ 56 (US$ 24 + US$ 32). - 3.000 minutos de Linux por US$ 0,008 por minuto = US$ 24. diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md index 351e6baf57..0cb030856c 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md @@ -54,10 +54,12 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim {% data reusables.codespaces.exporting-changes %} ## Gerenciamento de notificações por e-mail e limite de gastos -As notificações de e-mail são enviadas para os proprietários de contas e gerentes de cobrança quando os gastos chegam a 50%, 75% e 90% do limite de gastos da sua conta. +Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit. Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**. +![Screenshot of the billing email notification settings](/assets/images/help/billing/codespaces-spending-limit-notifications.png) + ## Leia mais - "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" 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 61f8068b26..3239198ecc 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 @@ -48,7 +48,7 @@ Por padrão, a página de verificação de código de alertas é filtrada para m 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)." +Para obter mais informações, consulte "[Sobre alertas de {% data variables.product.prodname_code_scanning %}](/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 %} @@ -77,7 +77,7 @@ Se você inserir vários filtros, a visualização mostrará alertas que corresp {% ifversion fpt or ghes > 3.3 or ghec %} -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 %} +Você pode prefixar o filtro `tag` com `-` para excluir resultados com essa tag. Por exemplo, `-tag:style` mostra apenas alertas que não têm a tag `estilo`{% if codeql-ml-queries %} e `-tag:experimental` omitirá todos os alertas experimentais. Para obter mais informações, consulte "[Sobre alertas de{% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %} {% endif %} @@ -120,7 +120,7 @@ Você pode pesquisar na lista de alertas. Isso é útil se houver um grande núm {% endif %} -{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %} +{% 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 %} 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/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 4271ef318a..aaeaf6d618 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 @@ -188,16 +188,16 @@ Se você dividir sua análise em vários fluxos de trabalho, conforme descrito a

Se sua análise ainda é muito lenta para ser executada durante eventos 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)".

-### Check which query suites the workflow runs +### Verifique qual conjunto de consultas que o fluxo de trabalho executa -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. +Por padrão, existem três principais conjuntos de consultas disponíveis para cada linguagem. Se você otimizar a compilação do banco de dados CodeQL mesmo assim o processo continuar sendo muito longo, você poderá reduzir o número de consultas que você executa. O conjunto de consulta padrão é executado automaticamente. Ele contém as consultas de segurança mais rápidas com as taxas mais baixas de resultados falso-positivos. -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)." +Você pode executar consultas adicionais ou conjuntos de consulta além das consultas padrão. Verifique se o fluxo de trabalho define um conjunto de consultas adicional ou consultas adicionais a serem executadas usando o elemento `consultas`. Você pode experimentar desabilitar o conjunto de consultas adicionais ou consultas. 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)." +**Observação:** Se você executar `security-extended` ou a consulta `security-and-quality` para o JavaScript, algumas consultas irão usar a tecnologia experimental. Para obter mais informações, consulte "[Sobre a alertas da digitalização de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)". {% endnote %} {% endif %} @@ -216,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" -On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. +Em projetos muito grandes, {% data variables.product.prodname_codeql %} pode ficar ficar sem disco ou sem memória no executor. {% 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/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-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-cli-in-your-ci-system.md index 482b8eacf8..2c94bf189c 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-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-cli-in-your-ci-system.md @@ -325,7 +325,7 @@ codeql database analyze <database> --format=<format> \ - Especifique pacotes ou consultas de {% data variables.product.prodname_codeql %} para executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, omita este parâmetro. 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. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte Criando conjuntos de consultas de CodeQL na documentação do {% data variables.product.prodname_codeql_cli %}. + Especifique pacotes ou consultas de {% data variables.product.prodname_codeql %} para executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, omita este parâmetro. Para ver os outros itens de consulta incluídos no pacote de {% data variables.product.prodname_codeql_cli %}, consulte /<extraction-root>/qlpacks/codeql/<language>-queries/codeql-suites. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte Criando conjuntos de consultas de CodeQL na documentação do {% data variables.product.prodname_codeql_cli %}. diff --git a/translations/pt-BR/content/code-security/getting-started/github-security-features.md b/translations/pt-BR/content/code-security/getting-started/github-security-features.md index 5c2be0d2d9..38d92740a4 100644 --- a/translations/pt-BR/content/code-security/getting-started/github-security-features.md +++ b/translations/pt-BR/content/code-security/getting-started/github-security-features.md @@ -83,6 +83,12 @@ Detectar automaticamente tokens ou credenciais que foram verificados em um repos Mostre o impacto completo das alterações nas dependências e veja detalhes de qualquer versão vulnerável antes de fazer merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". {% endif %} +{% ifversion ghec or ghes > 3.1 %} +### Visão geral da segurança + +Revise a configuração de segurança e os alertas para sua organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)". +{% endif %} + ## Leia mais - "[Produtos do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)" - "[Suporte à linguagem de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-language-support)" 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 25e29b59c1..06b8cdd44e 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 @@ -36,7 +36,7 @@ Você pode criar uma política de segurança padrão que será exibida em qualqu {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %} ## Gerenciar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências -{% ifversion fpt or ghec %}Por padrão, {% data variables.product.prodname_dotcom %} detecta vulnerabilidades nos repositórios públicos, gera {% data variables.product.prodname_dependabot_alerts %} e um gráfico de dependência. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta vulnerabilidades em repositórios públicos e exibe o gráfico de dependências. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios públicos pertencentes à sua organização. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização. 1. Clique na sua foto de perfil e clique em **Organizações**. 2. Clique em **Configurações** ao lado da sua organização. @@ -143,5 +143,5 @@ Você pode visualizar e gerenciar alertas de funcionalidades de segurança para {% 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)" +"[Acessando os relatórios de conformidade para a sua organização](/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/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 7917dc4cd7..75a95e8698 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -67,7 +67,13 @@ Antes de definir um padrão personalizado, você deve garantir que {% data varia {% data reusables.repositories.navigate-to-security-and-analysis %} {% data reusables.repositories.navigate-to-ghas-settings %} {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} -{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} +1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**. +1. When the dry run finishes, you'll see a sample of results (up to 1000) from the repository. Review the results and identify any false positive results. ![Screenshot showing results from dry run](/assets/images/help/repository/secret-scanning-publish-pattern.png) +1. Edit the new custom pattern to fix any problems with the results, then click **Save and dry run** to test your changes. +{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %} +{% endif %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} Após a criação do seu padrão, {% data reusables.secret-scanning.secret-scanning-process %} Para mais informações sobre visualização de alertas {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". @@ -116,6 +122,7 @@ Antes de definir um padrão personalizado, você deverá habilitar {% data varia {% data reusables.repositories.navigate-to-ghas-settings %} {% data reusables.advanced-security.secret-scanning-new-custom-pattern %} {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} Depois que o padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar todos os segredos nos repositórios {% ifversion fpt or ghec %}privados {% endif %} na sua organização, incluindo todo seu histórico do Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". @@ -139,6 +146,7 @@ Antes de definir um padrão personalizado, você deverá garantir que você habi {% data reusables.enterprise-accounts.advanced-security-security-features %} 1. Em "Padrões de personalização de digitalização de segredos", clique em {% ifversion ghes = 3.2 %}**Novo padrão personalizado**{% else %}**Novo padrão**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} +{% data reusables.advanced-security.secret-scanning-create-custom-pattern %} Depois que seu padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar se há segredos em repositórios {% ifversion fpt or ghec %}privados{% endif %} dentro das organizações da sua empresa com {% data variables.product.prodname_GH_advanced_security %} habilitado, incluindo toda a sua história de Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md index d9c8ee72aa..a8bc817e18 100644 --- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md @@ -28,7 +28,7 @@ shortTitle: Sobre a visão geral de segurança Você pode usar a visão geral de segurança para uma visão de alto nível do status de segurança da sua organização ou para identificar repositórios problemáticos que exigem intervenção. -- A nível da organização, a visão geral de segurança exibe informações de segurança agregadas e específicas para repositórios pertencentes à sua organização. You can also filter information per security feature. +- A nível da organização, a visão geral de segurança exibe informações de segurança agregadas e específicas para repositórios pertencentes à sua organização. Você também pode filtrar as informações por recurso de segurança. - No nível da equipe, a visão geral de segurança exibe informações de segurança específicas para repositórios para os quais a equipe tem privilégios de administrador. Para obter mais informações, consulte "[Gerenciando o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". - No nível do repositório, a visão geral de segurança mostra quais recursos de segurança são habilitados para o repositório e oferece a opção de configurar todos os recursos de segurança disponíveis que não estejam em uso atualmente. diff --git a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md index c47d8c895c..6c360c7fe2 100644 --- a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md @@ -27,7 +27,7 @@ shortTitle: Ver visão geral de segurança 1. Para visualizar informações agregadas sobre tipos de alertas, clique em **Mostrar mais**. ![Botão mostrar mais](/assets/images/help/organizations/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} {% 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) +1. Como alternativa, use a barra lateral à esquerda para filtrar informações por recurso de segurança. Em cada página, é possível usar filtros específicos para cada recurso para ajustar sua pesquisa. ![Captura de tela da página de digitalização específica do código](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) ## Visualizando alertas em toda a sua organização diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index 7df78c8222..3347986c1d 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/translations/pt-BR/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 o Dependabot com ações --- {% data reusables.dependabot.beta-security-and-version-updates %} @@ -30,11 +30,17 @@ shortTitle: Use Dependabot with Actions {% data variables.product.prodname_dependabot %} consegue acionar fluxos de trabalho de {% data variables.product.prodname_actions %} nos seus pull requests e comentários. No entanto, certos eventos são tratados de maneira diferente. -Para fluxos de trabalho iniciados por eventos de {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment` e `push`, aplicam-se as restrições a seguir: +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +Para fluxos de trabalho iniciados por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) que usam eventos de `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status`, aplicam-se as restrições a seguir: +{% endif %} - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` tem permissões somente leitura, a menos que seu administrador tenha removido as restrições.{% else %}`GITHUB_TOKEN` tem permissões somente leitura por padrão.{% endif %} - {% ifversion ghes = 3.3 %}Os segredos são inacessíveis, a menos que o seu administrador tenha removido restrições.{% else %}Os segredos são preenchidos a partir dos segredos de {% data variables.product.prodname_dependabot %}. Os segredos de {% data variables.product.prodname_actions %} não estão disponíveis.{% endif %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +Para fluxos de trabalho iniciados por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) que usam eventos de `pull_request_target`, se a referência da base do pull request foi criada por {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` será somente leitura e os segredos não estarão disponíveis. +{% endif %} + Para obter mais informações, consulte ["Manter seus GitHub Actions e fluxos de trabalho seguro: Evitando solicitações de pwn"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/). {% ifversion fpt or ghec or ghes > 3.3 %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md index e6afe728c3..741b68509d 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md @@ -27,9 +27,9 @@ shortTitle: Opções de configuração O arquivo de configuração do {% data variables.product.prodname_dependabot %} , *dependabot.yml*, usa a sintaxe YAML. Se você não souber o que é YAMLe quiser saber mais, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". -Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. 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)." +Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. Para obter mais informações e exemplos, consulte "[Habilitando e desabilitando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)". -Quaisquer opções que também afetem as atualizações de segurança são usadas na próxima vez que um alerta de segurança acionar um pull request para uma atualização de segurança. 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)." +Quaisquer opções que também afetem as atualizações de segurança são usadas na próxima vez que um alerta de segurança acionar um pull request para uma atualização de segurança. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)." O arquivo *dependabot.yml* tem duas chaves obrigatórias de nível superior: `versão`e `atualizações`. Opcionalmente, você pode incluir uma chave de `registro` de nível superior. O arquivo deve começar com a `versão: 2`. @@ -491,9 +491,9 @@ updates: ### `registros` -Para permitir que {% data variables.product.prodname_dependabot %} acesse um registro de pacote privado ao executar uma atualização de versão, você deverá incluir uma configuração de `registros` com a configuração de `atualizações` relevante. Pode permitir que todos os registros definidos sejam usados configurando `registros` como `"*"`. Como alternativa, você pode listar os registros que a atualização pode usar. Para isso, use o nome do registro conforme definido na seção de `registros` do arquivo _dependabot.yml_. For more information, see "[Configuration options for private registries](#configuration-options-for-private-registries)" below. +Para permitir que {% data variables.product.prodname_dependabot %} acesse um registro de pacote privado ao executar uma atualização de versão, você deverá incluir uma configuração de `registros` com a configuração de `atualizações` relevante. Pode permitir que todos os registros definidos sejam usados configurando `registros` como `"*"`. Como alternativa, você pode listar os registros que a atualização pode usar. Para isso, use o nome do registro conforme definido na seção de `registros` do arquivo _dependabot.yml_. Para obter mais informações, consulte "[Opções de configuração para registros privados](#configuration-options-for-private-registries)" abaixo. -Para permitir que {% data variables.product.prodname_dependabot %} use os gerenciadores de pacote `bundler`, `mix` e `pip` para atualizar dependências em registros privados, você pode optar por permitir a execução de código externo. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above. +Para permitir que {% data variables.product.prodname_dependabot %} use os gerenciadores de pacote `bundler`, `mix` e `pip` para atualizar dependências em registros privados, você pode optar por permitir a execução de código externo. Para obter mais informações, consulte [`insecure-external-code-execution`](#insecure-external-code-execution) acima. ```yaml # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 982e9cd23f..e6b09504d6 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -59,7 +59,7 @@ Para obter uma lista dos ecossistemas para os quais o {% data variables.product. {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e exibe o gráfico de dependências, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Proprietários de repositórios ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %} para repositórios públicos. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios pertencentes à sua conta de usuário ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md index b34478a84c..2fd57be3ac 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md @@ -46,8 +46,6 @@ Há três razões pelas quais um alerta pode não ter link de um pull request: Se um erro impediu que {% data variables.product.prodname_dependabot %} criasse um pull request, você pode exibir os detalhes do erro clicando no alerta. -![O alerta do {% data variables.product.prodname_dependabot %} que mostra que o erro que bloqueou a criação de um pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) - ## Investigar erros com {% data variables.product.prodname_dependabot_version_updates %} Quando {% data variables.product.prodname_dependabot %} está impedido de criar um pull request para atualizar uma dependência em um ecossistema, ele posta o ícone de erro no arquivo de manifesto. Os arquivos de manifesto gerenciados por {% data variables.product.prodname_dependabot %} estão listados na aba {% data variables.product.prodname_dependabot %}. Para acessar essa aba, na aba **Insights** para o repositório, clique no **Gráfico de Dependências**, e, em seguida, clique na aba **{% data variables.product.prodname_dependabot %}**. diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 842cc5a243..df01ad74b9 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -103,17 +103,17 @@ Uma vez que {% data variables.product.prodname_dependabot %} usa dados curados e {% ifversion fpt or ghec %} ## Cada vulnerabilidade de dependência gera um alerta separado? -Quando uma dependência tem várias vulnerabilidades, apenas um alerta agregado é gerado para essa dependência, em vez de um alerta por vulnerabilidade. +Quando uma dependência tem várias vulnerabilidades, gera-se um alerta para cada vulnerabilidade no nível da consultoria mais manifesto. -A contagem de {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.prodname_dotcom %} mostra um total para o número de alertas, ou seja, o número de dependências com vulnerabilidades, não o número de vulnerabilidades. +![Captura de tela da aba de {% data variables.product.prodname_dependabot_alerts %} que mostra dois alertas do mesmo pacote com manifestos diferentes.](/assets/images/help/repository/dependabot-alerts-view.png) -![Vista de {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-view.png) +O legado de {% data variables.product.prodname_dependabot_alerts %} foi agrupado em um único alerta agregado com todas as vulnerabilidades para a mesma dependência. Se você acessar um link para um alerta de legadode {% data variables.product.prodname_dependabot %}, você será redirecionado para a aba de {% data variables.product.prodname_dependabot_alerts %} filtrada para exibir vulnerabilidades para esse pacote e manifesto dependente. -Ao clicar para exibir os detalhes de alerta, você pode ver quantas vulnerabilidades são incluídas no alerta. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -![Múltiplas vulnerabilidades para um alerta de {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png) +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -**Verifique**: Se houver discrepância no total que você está vendo, verifique se você não está comparando números de alerta com números de vulnerabilidade. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} ## Leia mais diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 8c2421d757..f16fa4a212 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -25,7 +25,7 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -A aba de {% data variables.product.prodname_dependabot_alerts %} do seu repositório lista todos os {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} abertos e fechados correspondentes a {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. Você pode ordenar a lista de alertas selecionando o menu suspenso e você pode clicar em alertas específicos para obter mais detalhes. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" {% ifversion fpt or ghec or ghes > 3.2 %} É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." @@ -37,11 +37,26 @@ A aba de {% data variables.product.prodname_dependabot_alerts %} do seu reposit ## Sobre atualizações para dependências vulneráveis no seu repositório {% data variables.product.product_name %} gera {% data variables.product.prodname_dependabot_alerts %} quando detectamos que sua base de código está usando dependências com vulnerabilidades conhecidas. Para repositórios em que {% data variables.product.prodname_dependabot_security_updates %} estão habilitados, quando {% data variables.product.product_name %} detecta uma dependência vulnerável no branch padrão, {% data variables.product.prodname_dependabot %} cria um pull request para corrigi-la. O pull request irá atualizar a dependência para a versão minimamente segura possível, o que é necessário para evitar a vulnerabilidade. + +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`). + +Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %} {% endif %} ## Visualizar e atualizar dependências vulneráveis -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-dependabot-alerts %} +1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png) +1. Click the alert that you would like to view. ![Alerta selecionado na lista de alertas](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png) +1. Revise as informações da vulnerabilidade e, se disponível, o pull request que contém a atualização de segurança automatizada. +1. Opcionalmente, se ainda não houver uma atualização de {% data variables.product.prodname_dependabot_security_updates %} para o alerta, crie um pull request para resolver a vulnerabilidade. Clique em **Criar uma atualização de segurança de {% data variables.product.prodname_dependabot %}**. ![Crie um botão de atualização de segurança do {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) +1. Quando estiver pronto para atualizar a dependência e resolver a vulnerabilidade, faça merge da pull request. Cada pull request criado por {% data variables.product.prodname_dependabot %} inclui informações sobre os comandos que você pode usar para controlar {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciar pull requests para atualizações de dependências](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)". +1. Opcionalmente, se o alerta estiver sendo corrigido, se estiver incorreto, ou localizado em um código não utilizado, selecione o menu suspenso "Ignorar" e clique em um motivo para ignorar o alerta. ![Escolher o motivo para ignorar o alerta a partir do menu suspenso "Ignorar"down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) + +{% elsif ghes = 3.3 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} @@ -51,7 +66,7 @@ A aba de {% data variables.product.prodname_dependabot_alerts %} do seu reposit 1. Quando estiver pronto para atualizar a dependência e resolver a vulnerabilidade, faça merge da pull request. Cada pull request criado por {% data variables.product.prodname_dependabot %} inclui informações sobre os comandos que você pode usar para controlar {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciar pull requests para atualizações de dependências](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)". 1. Opcionalmente, se o alerta estiver sendo corrigido, se estiver incorreto, ou localizado em um código não utilizado, selecione o menu suspenso "Ignorar" e clique em um motivo para ignorar o alerta. ![Escolher o motivo para ignorar o alerta a partir do menu suspenso "Ignorar"down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) -{% elsif ghes > 3.0 or ghae-issue-4864 %} +{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 0374f432e7..e114976e99 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -38,7 +38,7 @@ A revisão de dependências está disponível quando o gráfico de dependências Às vezes, você pode apenas querer atualizar a versão de uma dependência em um manifesto e gerar um pull request. No entanto, se a versão atualizada desta dependência direta também atualizou as dependências, seu pull request pode ter mais alterações do que o esperado. A revisão de dependência para cada manifesto e arquivo de bloqueio fornece uma maneira fácil de ver o que foi alterado e se alguma das novas versões de dependências contém vulnerabilidades conhecidas. -Ao verificar as revisões de dependências em um pull request e alterar todas as dependências sinalizadas como vulneráveis, você pode evitar que vulnerabilidades sejam adicionadas ao seu projeto. 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)." +Ao verificar as revisões de dependências em um pull request e alterar todas as dependências sinalizadas como vulneráveis, você pode evitar que vulnerabilidades sejam adicionadas ao seu projeto. Para obter mais informações sobre como funciona a revisão de dependências, consulte "[Revisar as alterações de dependência em um 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 %} encontrará vulnerabilidades que já estão nas suas dependências, mas é muito melhor evitar a introdução de possíveis problemas do que corrigir problemas em uma data posterior. Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 65a374e371..fa6b543bf6 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -90,22 +90,22 @@ Os formatos recomendados definem explicitamente quais versões são usadas para | Go modules | Go | `go.mod` | `go.mod` | {%- 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`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} -{%- ifversion fpt or ghes > 3.3 %} +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} | 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..uses` will be parsed as dependencies. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)." +[1] Observe que os fluxos de trabalho de {% data variables.product.prodname_actions %} devem estar localizados no diretório `.github/workflows/` de um repositório para serem reconhecidos como manifestos. Todas as ações ou fluxos de trabalho referenciados que usam a sintaxe `jobs[*].steps[*].uses` or `jobs..uses` serão analisados como dependências. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o 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. +[2] Se você listar suas dependências do Python nas no arquivo `setup.py`, é possível que não possamos analisar e listar todas as dependências do seu projeto. {% 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. +[1] Se você listar suas dependências do Python no arquivo `setup.py`, é possível que não possamos analisar e listar todas as dependências do seu projeto. {% endif %} {% if github-actions-in-dependency-graph %} {% note %} -**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. +**Observação:** As dependências do fluxo de trabalho de {% data variables.product.prodname_actions %} são exibidas no gráfico de dependências para fins informativos. Os alertas de dependência não são atualmente compatíveis com os fluxos de trabalho de {% data variables.product.prodname_actions %}. {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index c5a28310de..48d4b1a9c3 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -12,7 +12,7 @@ shortTitle: Registro de imagem privada ## Sobre registros de imagens privadas e {% data variables.product.prodname_codespaces %} -Um registro é um espaço seguro para armazenar, gerenciar e buscar imagens privadas de contêineres. You may use one to store one or more images. Existem muitos exemplos de registros, como {% data variables.product.prodname_dotcom %} registro do contêiner, registro de contêiner do Azure ou DockerHub. +Um registro é um espaço seguro para armazenar, gerenciar e buscar imagens privadas de contêineres. Você pode usar uma para armazenar uma ou mais imagens. Existem muitos exemplos de registros, como {% data variables.product.prodname_dotcom %} registro do contêiner, registro de contêiner do Azure ou DockerHub. O registro do contêiner de {% data variables.product.prodname_dotcom %} pode ser configurado para puxar imagens container sem precisar fornecer qualquer credencial para {% data variables.product.prodname_codespaces %}. Para outros registros de imagem, você deve criar segredos em {% data variables.product.prodname_dotcom %} para armazenar os detalhes de acesso, o que permitirá que {% data variables.product.prodname_codespaces %} acesse imagens armazenadas nesse registro. diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md index 4ea668eeb6..882dc68f3a 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md @@ -19,7 +19,7 @@ Para saber mais sobre os preços para {% data variables.product.prodname_codespa {% data reusables.codespaces.codespaces-billing %} -- 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) +- Como proprietário de uma organização ou gerente de cobrança, você pode gerenciar a cobrança de {% data variables.product.prodname_codespaces %} para a sua organização: ["Sobre cobrança para codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces) - Para os usuários, há um guia que explica como a cobrança funciona: ["Entendendo a cobrança para codespace"](/codespaces/codespaces-reference/understanding-billing-for-codespaces) diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index e848a75561..42daae7578 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -41,7 +41,7 @@ Para criar segredos para um repositório da organização, você deve ter acesso {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -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 %}**. +1. Na seção "Segurança" da barra lateral, selecione **Segredos de {% octicon "key-asterisk" aria-label="The key-asterisk icon" %}** e, em seguida, clique em **{% data variables.product.prodname_codespaces %}**. 2. Na parte superior da página, clique em **Novo segredo de repositório**. 3. Digite um nome para o seu segredo na caixa de entrada **Nome**. 4. Insira o valor para o seu segredo. @@ -55,7 +55,7 @@ Ao criar um segredo em uma organização, você pode usar uma política para lim {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} -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 %}**. +1. Na seção "Segurança" da barra lateral, selecione **Segredos de {% octicon "key-asterisk" aria-label="The key-asterisk icon" %}** e, em seguida, clique em **{% data variables.product.prodname_codespaces %}**. 2. Na parte superior da página, clique em **Novo segredo de organização**. 3. Digite um nome para o seu segredo na caixa de entrada **Nome**. 4. Insira o **Valor** para o seu segredo. diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index 3c63bb096d..a44a51cce1 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -47,7 +47,7 @@ Se você adicionar uma política para toda a organização, você deverá config {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -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**. +1. Na seção "Código, planejamento e automação" da barra lateral, selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** e, em seguida, clique em **Política**. 2. Na página "Políticas do codespace", clique em **Criar política**. 3. Insira um nome para sua nova política. 4. Clique **Adicionar restrição** e escolha **Tipos de máquina**. diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md index f1f8f12a52..6ad3735102 100644 --- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md +++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md @@ -21,6 +21,8 @@ Você pode denunciar usuários que violaram Diretrizes da comunidade ou Termos d Se o conteúdo denunciado estiver ativado para um repositório público, você também poderá denunciar o conteúdo diretamente aos mantenedores do repositório. +Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer). + ## Denunciar um usuário {% data reusables.profile.user_profile_page_navigation %} 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 026aa0ca3d..1cfe6e0dcc 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. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**. +1. Na seção "Acesso" da barra lateral, selecione **Moderação de {% octicon "report" aria-label="The report icon" %}** e, em seguida, clique em **Limites de interação**. {% 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/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md index a8b174d854..35f0427660 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md @@ -33,7 +33,7 @@ Os proprietários da organização também podem bloquear os usuários por um de {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**. +1. Na seção "Acesso" da barra lateral, selecione **Moderação de {% octicon "report" aria-label="The report icon" %}** e, em seguida, clique em **Limites de interação**. {% data reusables.community.set-interaction-limit %} ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index 6e24974852..29df8518cb 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -28,7 +28,7 @@ Você também pode habilitar limitações de atividade em todos os repositórios {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**. +1. Na seção "Acesso" da barra lateral, selecione **Opções de moderação de {% octicon "comment-discussion" aria-label="The comment-discussion icon" %}** e, em seguida, clique em **Limites de interação**. {% data reusables.community.set-interaction-limit %} ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/repository/temporary-interaction-limits-options.png) diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md index 7df6fefda9..ee3d8db7a0 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md @@ -1,6 +1,6 @@ --- 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.' +intro: 'Você pode ver alguns desses erros comuns de validação ao criar, salvar ou visualizar formulários de problemas.' versions: fpt: '*' ghec: '*' @@ -13,16 +13,16 @@ topics: ## 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. +O modelo não contém um campo `nome`, o que significa que não está claro que nome dar ao seu modelo de problema ao fornecer aos usuários uma lista de opções. ### Exemplo ```yaml -description: "Thank you for reporting a bug!" +descrição: "Obrigado por relatar um erro!" ... ``` -The error can be fixed by adding `name` as a key. +O erro pode ser corrigido adicionando `nome` como chave. ```yaml name: "Bug report" @@ -30,13 +30,13 @@ description: "Thank you for reporting a bug!" ... ``` -## `key` must be a string +## a `chave` deve ser uma 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. +Esta mensagem de erro significa que uma chave permitida foi fornecida, mas seu valor não pode ser analisado porque o tipo de dado não é compatível. ### Exemplo -The `description` below is being parsed as a Boolean, but it should be a string. +A `descrição` abaixo está sendo analisada como um booleano, mas deve ser uma string. ```yaml name: "Bug report" @@ -44,7 +44,7 @@ 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. +O erro pode ser corrigido fornecendo uma string como o valor. As strings podem ter de ser envolvidas em aspas duplas para serem analisadas com sucesso. Por exemplo, as strings que contenham `'` devem estar entre aspas duplas. ```yaml name: "Bug report" @@ -52,7 +52,7 @@ description: "true" ... ``` -Empty strings, or strings consisting of only whitespaces, are also not permissible when the field expects a string. +As strings vazias ou que consistem em espaços em branco também não são permitidas quando o campo espera uma string. ```yaml name: "" @@ -61,7 +61,7 @@ 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. +O erro pode ser corrigido ajustando o valor como uma string não vazia. Se o campo não for obrigatório, você deverá excluir o par chave-valor. ```yaml name: "Bug Report" @@ -69,9 +69,9 @@ description: "File a bug report" ... ``` -## `input` is not a permitted key +## `entrada` não é uma chave permitida -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)." +Uma chave inesperada foi fornecida no nível superior do modelo. Para obter mais informações sobre quais chaves de nível superior são compatíveis, consulte "[Sintaxe para os formulários do problema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax). " ### Exemplo @@ -81,24 +81,24 @@ hello: world ... ``` -The error can be fixed by removing the unexpected keys. +O erro pode ser corrigido removendo as chaves inesperadas. ```yaml name: "Bug report" ... ``` -## Forbidden keys +## Chaves proibidas -YAML parses certain strings as `Boolean` values. To avoid this, we have explicitly forbidden the usage of the following keys: +O YAML analisa certas strings como valores `booleanos`. Para evitar isso, proibimos explicitamente o uso das seguintes chaves: `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. +O erro pode ser corrigido removendo as chaves proibidas. -## Body must contain at least one non-markdown field +## O texto deve conter pelo menos um campo que não seja markdown -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. +Os formulários de problemas devem aceitar a entrada do usuário, o que significa que pelo menos um dos seus campos deve conter um campo de entrada de usuário. Um elemento `markdown` é um texto estático. Portanto, uma matriz do `texto` não pode conter apenas elementos de `markdown`. ### Exemplo @@ -110,7 +110,7 @@ body: value: "Bugs are the worst!" ``` -The error can be fixed by adding non-markdown elements that accept user input. +O erro pode ser corrigido adicionando elementos que não são markdown que aceitam a entrada do usuário. ```yaml name: "Bug report" @@ -123,9 +123,9 @@ body: label: "What's wrong?" ``` -## Body must have unique ids +## O texto deve ter identificações únicas -If using `id` attributes to distinguish multiple elements, each `id` attribute must be unique. +Se você estiver usando `atributos de id` para distinguir vários elementos, cada atributo de `id` deverá ser único. ### Exemplo @@ -142,7 +142,7 @@ body: 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. +O erro pode ser corrigido alterando o `id` para uma dessas entradas, para que todo campo `entrada` tenha um atributo `id` único. ```yaml name: "Bug report" @@ -157,9 +157,9 @@ body: label: Last name ``` -## Body must have unique labels +## O texto deve ter etiquetas únicas -When there are multiple `body` elements that accept user input, the `label` attribute for each user input field must be unique. +Quando há vários elementos do `texto` que aceitam entrada do usuário, o atributo `etiqueta` para cada campo de entrada do usuário deve ser único. ### Exemplo @@ -174,7 +174,7 @@ body: 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. +O erro pode ser corrigido alterando o atributo `rótulo` para um dos campos de entrada para garantir que cada `etiqueta` seja única. ```yaml name: "Bug report" @@ -187,7 +187,7 @@ body: 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. +Os campos de entrada também podem ser diferenciados pelo seu atributo `id`. Se forem necessários atributos de `etiquetas` duplicadas, você poderá fornecer pelo menos um `id` para diferenciar dois elementos com etiquetas idênticas. ```yaml name: "Bug report" @@ -202,7 +202,7 @@ body: 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. +Os atributos de `id` não estão visíveis no texto do problema. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes. ## Labels are too similar @@ -297,7 +297,7 @@ body: - 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. +Os atributos de `id` não estão visíveis no texto do problema. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes. ## Body[i]: required key type is missing @@ -418,9 +418,9 @@ The error can be fixed by supplying a string value for `label`. If you want to u 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. +As strings vazias ou strings que consistem em apenas espaços em branco não são permitidas quando um atributo espera uma string. Por exemplo, `""` ou `" "` não são permitidos. -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. +Se o atributo é obrigatório, o valor deverá ser uma string não vazia. Se o campo não for obrigatório, você deverá excluir o par chave-valor. ```yaml body: @@ -429,9 +429,9 @@ body: label: "Name" ``` -## Body[i]: `id` can only contain numbers, letters, -, _ +## Body[i]: `id` pode apenas conter números, letras, -, _ -`id` attributes can only contain alphanumeric characters, `-`, and `_`. Your template may include non-permitted characters, such as whitespace, in an `id`. +Atributos de `id` podem conter apenas caracteres alfanuméricos, `-`, e `_`. Seu modelo pode incluir caracteres não permitidos, como espaços em branco, em um `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. @@ -446,7 +446,7 @@ body: label: First name ``` -The error can be fixed by ensuring that whitespaces and other non-permitted characters are removed from `id` values. +O erro pode ser corrigido garantindo que os espaços em branco e outros caracteres não permitidos sejam removidos de valores da `id`. ```yaml name: "Bug report" @@ -457,9 +457,9 @@ body: label: First name ``` -## Body[i]: `x` is not a permitted key +## Body[i]: `x` não é uma chave permitida -An unexpected key, `x`, was provided at the same indentation level as `type` and `attributes`. +Uma chave inesperada, `x`, foi fornecida no mesmo nível de indentação que `tipo` e `atributos`. 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. @@ -473,7 +473,7 @@ body: 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`. +O erro pode ser corrigido removendo chaves extras e usando apenas `tipo`, `atributos` e `id`. ```yaml body: @@ -482,9 +482,9 @@ body: 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 +## Body[i]: `label` contém a palavra proibida -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. +Para minimizar o risco de informações e credenciais privadas serem publicadas nos problemas do GitHub, algumas palavras comumente usadas por invasores não são permitidas na `etiqueta` de entrada ou elementos de texto. 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. @@ -500,7 +500,7 @@ body: label: Password ``` -The error can be fixed by removing terms like "password" from any `label` fields. +O erro pode ser corrigido removendo termos como "senha" de qualquer campo da `etiqueta`. ```yaml body: @@ -512,9 +512,9 @@ body: label: Username ``` -## Body[i]: `x` is not a permitted attribute +## Body[i]: `x` não é um atributo permitido -An invalid key has been supplied in an `attributes` block. +Uma chave inválida foi fornecida em um bloco de `atributos`. 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. @@ -525,10 +525,10 @@ body: - type: markdown attributes: x: "a random key!" - value: "Thanks for taking the time to fill out this bug!" + valor: "Obrigado por reservar um tempo tempo para preencher esse erro!" ``` -The error can be fixed by removing extra keys and only using permitted attributes. +O erro pode ser corrigido removendo chaves extras e usando apenas os atributos permitidos. ```yaml body: @@ -537,9 +537,9 @@ body: value: "Thanks for taking the time to fill out this bug!" ``` -## Body[i]: `options` must be unique +## Body[i]: `opções ` devem ser únicas -For checkboxes and dropdown input types, the choices defined in the `options` array must be unique. +Para caixas de seleção e tipos de entrada de menu suspenso, as escolhas definidas na matriz `opções` devem ser únicas. 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. @@ -556,7 +556,7 @@ body: - pie ``` -The error can be fixed by ensuring that no duplicate choices exist in the `options` array. +O erro pode ser corrigido garantindo que não existam opções duplicadas na matriz de `opções`. ``` body: @@ -568,9 +568,9 @@ body: - pie ``` -## Body[i]: `options` must not include the reserved word, none +## Body[i]: `options` não deve incluir a palavra reservada, nenhum -"None" is a reserved word in an `options` set because it is used to indicate non-choice when a `dropdown` is not required. +"Nenhum" é uma palavra reservada em um conjunto de `opções` porque é usado para indicar a não escolha quando não um `dropdown` não é necessário. 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. @@ -589,7 +589,7 @@ body: 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. +O erro pode ser corrigido removendo "Nenhum" como opção. Se você deseja que um contribuidor possa indicar que ele não gosta de nenhum desses tipos de tortas, você pode também remover a validação `necessária`. ``` body: @@ -601,11 +601,11 @@ body: - Chicken & Leek ``` -In this example, "None" will be auto-populated as a selectable option. +Neste exemplo, "Nenhum" será preenchido automaticamente como uma opção selecionável. -## Body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes +## Body[i]: `options` não deve incluir booleanos. Por favor, coloque os valores como "sim" e "verdadeiro" entre aspas -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. +Há uma série de palavras em inglês processadas em valores booleanos pelo analisador do YAML, a menos que sejam entre aspas. Para as `opções` do menu suspenso, todos os itens devem ser strings ao invés de booleanos. 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. diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 8c73064975..b942f72cf4 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -293,10 +293,10 @@ O parâmetro `redirect_uri` é opcional. Se ignorado, o GitHub redirecionará os O parâmetro opcional `redirect_uri` também pode ser usado para URLs do localhhost. Se o aplicativo especificar uma URL do localhost e uma porta, após a autorização, os usuários do aplicativo serão redirecionados para a URL e porta fornecidas. O `redirect_uri` não precisa corresponder à porta especificada na URL de retorno de chamada do aplicativo. -Para a URL de retorno de chamada `http://localhost/path`, você poderá usar este `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 ``` ## Criar vários tokens para aplicativos OAuth diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md index 941cd8fcdf..9caaa92bb5 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md @@ -60,4 +60,4 @@ Para obter um exemplo de um fluxo de trabalho de resposta de incidente, consulte Você deveria realizar varreduras regulares de vulnerabilidades de infraestrutura de produção. Você deve classificar os resultados de verificações de vulnerabilidades e definir um período de tempo no qual você concorda em remediar a vulnerabilidade. -Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)". +Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)". 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 index 086fc51c68..e477a3f6a3 100644 --- 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 @@ -45,10 +45,10 @@ You can integrate your personal or organization account on {% data variables.pro ### 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. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, 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. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, 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/getting-started-with-git/managing-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md index 23d5fdc08f..6c86f05757 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -195,6 +195,8 @@ Use o comando `git remote rm` para remover uma URL remota do seu repositório. O comando `git remote rm` tem um argumento: * O nome de um remote, como `destination` +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. + ## Exemplo Estes exemplos supõem que você está [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), que é o método recomendado. @@ -217,7 +219,7 @@ $ git remote -v {% warning %} -**Observação**: o comando `git remote rm` não exclui o repositório do remote no servidor. Ele simplesmente remove o remote e suas referências do repositório local. +**Note**: `git remote rm` does not delete the remote repository from the server. Ele simplesmente remove o remote e suas referências do repositório local. {% endwarning %} diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md index 9fea8d3212..0333d708ca 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md @@ -37,10 +37,29 @@ Uma licença de {% data variables.product.prodname_GH_advanced_security %} forne - **Visão geral de segurança** - Revise a configuração de segurança e os alertas para uma organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)". {% endif %} +{% ifversion fpt or ghec %} +The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. |{% ifversion fpt %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} +|:----------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| +| Varredura de código | Sim | Não | Sim | +| Varredura secreta | Yes **(limited functionality only)** | Não | Sim | +| Revisão de dependência | Sim | Não | Sim |{% endif %} +| +{% ifversion ghec %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} +|:------------------------:|:------------------------------------:|:------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| +| Varredura de código | Sim | Não | Sim | +| Varredura secreta | Yes **(limited functionality only)** | Não | Sim | +| Revisão de dependência | Sim | Não | Sim | +| Visão geral da segurança | Não | Não | Sim | +{% endif %} + +{% endif %} + Para obter informações sobre funcionalidades de {% data variables.product.prodname_advanced_security %} em desenvolvimento, consulte "[Plano de trabalho de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para uma visão geral de todas as funcionalidades de segurança, consulte "[ funcionalidades de segurança de{% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". {% ifversion fpt or ghec %} -As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão habilitadas para todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. Eles também têm acesso a uma visão geral de segurança a nível da organização. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. They also have access to an organization-level security overview. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} {% ifversion ghes or ghec %} 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 843ec9a968..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,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/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 1903c16a44..cf1ce86ba2 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -25,6 +25,11 @@ Para criar um título, adicione de um a seis símbolos # antes do tex ![Títulos H1, H2 e H6 renderizados](/assets/images/help/writing/headings-rendered.png) +When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section. + +![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png) + + ## Estilizar texto Você pode indicar ênfase com texto em negrito, itálico ou riscado em campos de comentários e arquivos de `.md`. diff --git a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md index 37bb94b91a..16621eb4c5 100644 --- a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md +++ b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md @@ -22,7 +22,7 @@ A finalidade principal da comunidade do GitHub é colaborar em projetos de softw * **Seja bem-vindo e venha com a mente aberta!** - Outros colaboradores podem não ter o mesmo nível de experiência ou o mesmo histórico que você, mas isso não significa que eles não tenham boas ideias para contribuir. Nós o encorajamos a receber com boas-vindas os novos colaboradores e aqueles que acabaram de chegar. -* **Respeitem-se.** Nada sabota tanto as conversas saudáveis quanto a grosseria. Seja cordial e profissional, e não publique nada que uma pessoa de bom senso considere como discurso ofensivo, abusivo ou de ódio. Não assedie ou constranja ninguém. Trate uns aos outros com dignidade e consideração em todas as interações. +* **Respect each other** - Nothing sabotages healthy conversation like rudeness. Seja cordial e profissional, e não publique nada que uma pessoa de bom senso considere como discurso ofensivo, abusivo ou de ódio. Não assedie ou constranja ninguém. Trate uns aos outros com dignidade e consideração em todas as interações. Você pode querer responder a algo discordando sobre o assunto. Tudo bem. Mas lembre-se de criticar ideias, não pessoas. Evite xingamentos, ataques diretos ad hominem, respondendo ao tom de um post em vez de seu conteúdo real, e reações impulsivas. Em vez disso, forneça contra-argumentos fundamentados que melhorem a conversa. diff --git a/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md b/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md index 57477530ca..ee59c92225 100644 --- a/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md +++ b/translations/pt-BR/content/github/site-policy/submitting-content-removal-requests.md @@ -23,3 +23,5 @@ A Política de Marca Registrada do GitHub pode ser utilizada para denunciar cont ## [Política de Remoção de Informações Privadas do GitHub](/github/site-policy/github-private-information-removal-policy) A Política de Remoção de Informações Privadas do GitHub pode ser usada para relatar dados privados (confidenciais e apresenta um risco de segurança), mas isso não é necessariamente protegido por direitos de autor ou por marcas registradas. + +Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer). diff --git a/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md b/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md index d82f9de964..9456cad5a4 100644 --- a/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md +++ b/translations/pt-BR/content/graphql/overview/about-the-graphql-api.md @@ -12,7 +12,7 @@ topics: ## Visão Geral -Aqui estão alguns links rápidos para ajudá-lo colocar em funcionamento a API v4 do GraphQL: +Here are some quick links to get you up and running with the GraphQL API: * [Autenticação](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) * [Ponto de extremidade raiz](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) @@ -36,9 +36,9 @@ A linguagem de consulta de dados do [GraphQL](https://graphql.github.io/) é: ## Por que o GitHub está usando GraphQL -O GitHub escolheu o GraphQL para a nossa API v4 porque ele oferece muito mais flexibilidade para os nossos integradores. A capacidade de definir precisamente os dados que você deseja—e _apenas_ os dados que você quer—é uma vantagem poderosa dos pontos de extremidades da API REST v3. O GraphQL permite que você substitua várias solicitações de REST por _uma única chamada_ para buscar os dados que você especificar. +GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. O GraphQL permite que você substitua várias solicitações de REST por _uma única chamada_ para buscar os dados que você especificar. -Para obter mais informações sobre por que o GitHub fez a migração para o GraphQL, consulte o [post de anúncio do blogue](https://githubengineering.com/the-github-graphql-api/) original. +For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/). ## Sobre a referência do esquema do GraphQL 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/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 index 6196197d3e..d668ef21f4 100644 --- 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 @@ -8,10 +8,10 @@ topics: - Organizations - Teams permissions: Organization owners can access compliance reports for the organization. -shortTitle: Access compliance reports +shortTitle: Acessar relatórios de conformidade --- -## About {% data variables.product.company_short %}'s compliance reports +## Sobre os relatórios de conformidade de {% data variables.product.company_short %} You can access {% data variables.product.company_short %}'s compliance reports in your organization settings. 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 index 96869d9fe2..808ca34918 100644 --- 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 @@ -19,9 +19,9 @@ 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 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 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) diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index 6c93e16be0..5747fb67d6 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -40,7 +40,7 @@ Para apoiar ainda mais as habilidades de colaboração da sua equipe, você pode {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} {% data reusables.organizations.invite-teams-or-people %} 5. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field.png) diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md index 10bfe07afc..5c530ecbb0 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -28,9 +28,9 @@ Ao remover um colaborador de um repositório de sua organização, o colaborador {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} -{% elsif ghes < 3.4 or ghae %} +{% else %} {% data reusables.repositories.navigate-to-manage-access %} {% endif %} {% data reusables.organizations.invite-teams-or-people %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md index 08391639b1..7f6f020979 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md @@ -24,7 +24,7 @@ Quando você desabilita quadros de projeto, deixa de ver informações relaciona {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. Decida se deseja desabilitar quadros de projeto em toda a organização, desabilitar quadros de projeto de repositório na organização ou ambos. Em seguida, em "Projects" (Projetos): diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md index 0020d467c3..84ff510c04 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -10,12 +10,12 @@ versions: shortTitle: Integrate Jira --- -{% ifversion ghes > 3.3 or ghae-issue-5658 %} +{% ifversion ghes > 3.4 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**. ![Aba OAuth applications (aplicativos OAuth) na barra lateral esquerda](/assets/images/help/organizations/org-oauth-applications-ghe.png) 1. Clique em **Novo aplicativo OAuth**. -{% elsif ghes < 3.4 or ghae %} +{% else %} {% data reusables.user_settings.access_settings %} 1. Na barra lateral esquerda, em **Organization settings** (Configurações da organização) clique no nome de sua organização. ![Barra lateral organization name (nome da organização)](/assets/images/help/settings/organization-settings-from-sidebar.png) 1. Na barra lateral esquerda, em **Developer settings** (Configurações do desenvolvedor), clique em **OAuth applications** (Aplicativos OAuth) ![Aba OAuth applications (aplicativos OAuth) na barra lateral esquerda](/assets/images/help/organizations/org-oauth-applications-ghe.png) diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index 49256606f0..8627a8be51 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -15,11 +15,15 @@ topics: shortTitle: Restringir criação de repositório --- -Você pode escolher se os integrantes podem criar repositórios na sua organização. Se você permitir que os integrantes criem repositórios, você poderá escolher quais tipos de repositórios os integrantes poderão criar.{% ifversion fpt or ghec %} Para permitir que os integrantes criem apenas repositórios privados, a sua organização deve usar {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} Para obter mais informações, consulte "[Sobre repositórios](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" na documentação de {% data variables.product.prodname_ghe_cloud %}{% endif %}. +Você pode escolher se os integrantes podem criar repositórios na sua organização. {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository. + +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization). +{% endif %} -Os proprietários da organização sempre podem criar qualquer tipo de repositório. {% ifversion ghec or ghae or ghes %} -{% ifversion ghec or ghae %}Proprietários corporativos{% elsif ghes %}administradores do site{% endif %} podem restringir as opções que você tem disponíveis para a política de criação de repositório da sua organização.{% ifversion ghec or ghes or ghae %} Para obter mais informações, consulte "[Restringindo a criação de repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %} +Enterprise owners can restrict the options you have available for your organization's repository creation policy. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)". +{% endif %} {% warning %} @@ -36,5 +40,12 @@ Os proprietários da organização sempre podem criar qualquer tipo de repositó ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + + {% note %} + + **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + + {% endnote %} {%- endif %} + 6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md index 140910d545..f823d2feba 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md @@ -57,7 +57,7 @@ Todos os integrantes da equipe que definiram seu status como "Ocupado" não ser {% 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 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**. {% else %} 1. Na barra lateral esquerda, clique em **Revisão de Código** ![Botão revisar código](/assets/images/help/teams/review-button.png) @@ -71,7 +71,7 @@ Todos os integrantes da equipe que definiram seu status como "Ocupado" não ser {% 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 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**. {% else %} 1. Na barra lateral esquerda, clique em **Revisão de Código** ![Botão revisar código](/assets/images/help/teams/review-button.png) diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index b205d0b9da..bb1babbfdb 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -22,7 +22,7 @@ topics: **Observação:** ao trabalhar com pull requests, lembre-se do seguinte: * Se estiver trabalhando no [modo de repositório compartilhado](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), é recomendável usar um branch de tópico para sua pull request. Embora você possa enviar pull requests de qualquer branch ou commit, com um branch de tópico, é possível fazer push de commits de acompanhamento caso seja preciso atualizar as alterações propostas. -* Ao fazer push de commits para uma pull request, não force o push. Faz push forçado das alterações no histórico do repositório e pode corromper o seu pull request. Se outros colaboradores fizerem o branch do projeto antes de um push forçado, este poderá substituir os commits nos quais os colaboradores basearam o seu trabalho. +* Be very careful when force pushing commits to a pull request. Faz push forçado das alterações no histórico do repositório e pode corromper o seu pull request. Se outros colaboradores fizerem o branch do projeto antes de um push forçado, este poderá substituir os commits nos quais os colaboradores basearam o seu trabalho. {% endnote %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index 98c84b7427..97e3527e29 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -17,7 +17,7 @@ topics: Bifurcar um repositório é semelhante a copiar um repositório, com duas grandes diferenças: -* Você pode usar uma pull request para sugerir alterações da sua bifurcação user-owned para o repositório original, também conhecido como o repositório *upstream*. +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. * Você pode transmitir alterações do repositório upstream para a sua bifurcação local sincronizando a bifurcação com o repositório upstream. {% data reusables.repositories.you-can-fork %} 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 b00a22be19..be5773f6bc 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 @@ -18,7 +18,7 @@ topics: As pessoas com permissões de administrador ou proprietário podem configurar um arquivo CODEOWNERS em um repositório. -As pessoas que você escolhe como proprietários do código devem ter permissões de gravação para o repositório. Quando o proprietário do código é uma equipe, essa equipe deverá ser visível e ter permissões de gravação, ainda que todos os membros individuais da equipe já tenham permissões de gravação diretamente, por meio da associação da organização ou por meio de outra associação à equipe. +The people you choose as code owners must have read permissions for the repository. Quando o proprietário do código é uma equipe, essa equipe deverá ser visível e ter permissões de gravação, ainda que todos os membros individuais da equipe já tenham permissões de gravação diretamente, por meio da associação da organização ou por meio de outra associação à equipe. ## Sobre proprietários do código @@ -104,11 +104,11 @@ apps/ @octocat # 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` +# 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. /apps/ @octocat -/apps/github +/apps/github ``` ### Exceções de sintaxe Existem algumas regras de sintaxe para arquivos gitignore que não funcionam em arquivos CODEOWNERS: diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md index 38d656eeba..ef402a1785 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md @@ -22,7 +22,7 @@ Se você usa o Zendesk para acompanhar tíquetes relatados pelo usuário, por ex {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. Na barra lateral esquerda, clique em **Autolink references** (Referências de link automático). ![Guia Autolink references (Referências de link automático) na barra lateral esquerda](/assets/images/help/repository/autolink-references-tab.png) 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/reference/billing.md b/translations/pt-BR/content/rest/reference/billing.md index ed6cb4eda8..5cd7d7d8d5 100644 --- a/translations/pt-BR/content/rest/reference/billing.md +++ b/translations/pt-BR/content/rest/reference/billing.md @@ -4,6 +4,7 @@ intro: 'Com a API de cobrança você pode monitorar as cobranças e uso {% data versions: fpt: '*' ghec: '*' + ghes: '>=3.4' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md index d903396303..230e3f76b5 100644 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ b/translations/pt-BR/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 @@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 %} ## Billing {% for operation in currentRestOperations %} diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md index 68849b2a03..dbd118c949 100644 --- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md @@ -921,6 +921,9 @@ _Equipes_ {% 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 %} ### Permissão em "executores auto-hospedados" 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/reusables/accounts/you-must-know-your-password.md b/translations/pt-BR/data/reusables/accounts/you-must-know-your-password.md new file mode 100644 index 0000000000..f4795c3909 --- /dev/null +++ b/translations/pt-BR/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/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md index d697ff8f8c..d645231024 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md +++ b/translations/pt-BR/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/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md index 03a6f893eb..5c4de1fea8 100644 --- a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md +++ b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md @@ -2,6 +2,8 @@ 1. Você deve fornecer, pelo menos, o nome para o seu padrão e uma expressão regular para o formato do seu padrão de segredo. 1. Você pode clicar em **Mais opções {% octicon "chevron-down" aria-label="down" %}** para fornecer outros conteúdos adjacentes ou requisitos adicionais de correspondência para o formato do segredo. 1. Provide a sample test string to make sure your configuration is matching the patterns you expect. - + {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} ![Crie um formulário de padrão personalizado de {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/secret-scanning-create-custom-pattern.png) -1. When you are satisfied with your new custom pattern, click {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. + {% else %} + ![Crie um formulário de padrão personalizado de {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png) + {% endif %} diff --git a/translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md new file mode 100644 index 0000000000..8f4453f9fc --- /dev/null +++ b/translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md @@ -0,0 +1 @@ +1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern**{% elsif ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. diff --git a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md index c245d3ddbe..a763a75baf 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md +++ b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 1. Na barra lateral Settings, clique em **Audit log**. ![Configurações de log de auditoria para organizações na barra lateral](/assets/images/help/organizations/org-settings-audit-log.png) diff --git a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md index b410a8053c..0f6217e1da 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md +++ b/translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} 3. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. {% else %} 3. Na barra lateral esquerda, clique em **Audit log**. ![Aba Log de auditoria](/assets/images/enterprise/site-admin-settings/audit-log-tab.png) diff --git a/translations/pt-BR/data/reusables/billing/email-notifications.md b/translations/pt-BR/data/reusables/billing/email-notifications.md index e6dfecd285..4b134cf465 100644 --- a/translations/pt-BR/data/reusables/billing/email-notifications.md +++ b/translations/pt-BR/data/reusables/billing/email-notifications.md @@ -1,3 +1,5 @@ -As notificações de e-mail são enviadas para os proprietários de contas e gerentes de cobrança quando os gastos chegam a 50%, 75%, e 90% do uso incluído na sua conta e quando os gastos chegam a 50%, 75%, e 90% do limite de gastos da sua conta. +Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit. Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**. + +![Screenshot of the billing email notification settings](/assets/images/help/billing/actions-packages-spending-limit-notifications.png) 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/dependabot/dependabot-secrets-button.md b/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md index ec922b1ac5..c97cd90ae3 100644 --- a/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md +++ b/translations/pt-BR/data/reusables/dependabot/dependabot-secrets-button.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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%} +{% else %} 1. Na barra lateral, clique em **{% data variables.product.prodname_dependabot %}**. ![Opção da barra lateral de segredos de {% data variables.product.prodname_dependabot %}](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png) {% endif %} 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/github-actions/docker-container-os-support.md b/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md index 6a6e7a60ed..81a27e5660 100644 --- a/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md +++ b/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md @@ -1,6 +1,6 @@ {% note %} -**Nota:** se seus fluxos de trabalho usam ações do contêiner Docker ou recipientes de serviço, você deve usar um executor Linux: +**Note:** If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runner: * Se você estiver usando executores hospedados em {% data variables.product.prodname_dotcom %}, você deverá usar um executor do Ubuntu. * Se você estiver usando executores auto-hospedados, você deve usar uma máquina Linux, pois seu executor e o Docker precisam ser instalados. diff --git a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md index 0a29042def..da96012798 100644 --- a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md +++ b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md @@ -5,8 +5,8 @@ permissions: actions: read|write|none checks: read|write|none contents: read|write|none - deployments: read|write|none - id-token: read|write|none + deployments: read|write|none{% ifversion fpt or ghec %} + id-token: read|write|none{% endif %} issues: read|write|none discussions: read|write|none packages: read|write|none diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index 1c973c16c3..d25129f56e 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -12,6 +12,6 @@ 2. Na barra lateral esquerda, clique em **Visão geral da empresa**. 3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 2. Navigate to the "Runner groups" settings: - * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %} - * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghec %}, then click the **Runners groups** tab{% endif %}.{% endif %} + * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %} + * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %} {% endif %} diff --git a/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md b/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md index 4adf6c9661..e23fedb78a 100644 --- a/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md +++ b/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral esquerda, clique em **Secrets** (Segredos). {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/billing_plans.md b/translations/pt-BR/data/reusables/organizations/billing_plans.md index 2ea9a5cf17..6036159319 100644 --- a/translations/pt-BR/data/reusables/organizations/billing_plans.md +++ b/translations/pt-BR/data/reusables/organizations/billing_plans.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral das configurações da sua organização, clique em **Planos de & cobrança**. ![Configurações de faturamento](/assets/images/help/billing/settings_organization_billing_plans_tab.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md index ed09054fd9..2e8823aed8 100644 --- a/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md +++ b/translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral esquerda, clique em **{% 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/pt-BR/data/reusables/organizations/member-privileges.md b/translations/pt-BR/data/reusables/organizations/member-privileges.md index fdd8fe2a7a..c791a7b7ab 100644 --- a/translations/pt-BR/data/reusables/organizations/member-privileges.md +++ b/translations/pt-BR/data/reusables/organizations/member-privileges.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 4. Na barra lateral esquerda, clique em **Member privileges** (Privilégios de membro). ![Opção de privilégios de membro nas configurações do org](/assets/images/help/organizations/org-settings-member-privileges.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/repository-defaults.md b/translations/pt-BR/data/reusables/organizations/repository-defaults.md index 6d44f46f55..391a6a4ad0 100644 --- a/translations/pt-BR/data/reusables/organizations/repository-defaults.md +++ b/translations/pt-BR/data/reusables/organizations/repository-defaults.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral esquerda, clique em **Padrões do repositório**. ![Aba Padrão do repositório](/assets/images/help/organizations/repo-defaults-tab.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/security-and-analysis.md b/translations/pt-BR/data/reusables/organizations/security-and-analysis.md index d0199f4410..77a2d097d4 100644 --- a/translations/pt-BR/data/reusables/organizations/security-and-analysis.md +++ b/translations/pt-BR/data/reusables/organizations/security-and-analysis.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral esquerda, clique em **Security & analysis** (Segurança e análise). !["Security & analysis" (Segurança e análise) aba nas configurações da organização](/assets/images/help/organizations/org-settings-security-and-analysis.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/security.md b/translations/pt-BR/data/reusables/organizations/security.md index 2d0a9d68f6..209240ce4f 100644 --- a/translations/pt-BR/data/reusables/organizations/security.md +++ b/translations/pt-BR/data/reusables/organizations/security.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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. Na barra lateral esquerda, clique em **Organization security** (Segurança da organização). diff --git a/translations/pt-BR/data/reusables/organizations/teams_sidebar.md b/translations/pt-BR/data/reusables/organizations/teams_sidebar.md index 31946ac488..a5a4901c03 100644 --- a/translations/pt-BR/data/reusables/organizations/teams_sidebar.md +++ b/translations/pt-BR/data/reusables/organizations/teams_sidebar.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/pt-BR/data/reusables/organizations/verified-domains.md b/translations/pt-BR/data/reusables/organizations/verified-domains.md index a10c7d9319..c79c87de48 100644 --- a/translations/pt-BR/data/reusables/organizations/verified-domains.md +++ b/translations/pt-BR/data/reusables/organizations/verified-domains.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral esquerda, clique em **Domínios & verificados e aprovados**. ![Aba "& domínios aprovados" verificados](/assets/images/help/organizations/verified-domains-button.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/pages/sidebar-pages.md b/translations/pt-BR/data/reusables/pages/sidebar-pages.md index ec65e49f5d..0238f6860b 100644 --- a/translations/pt-BR/data/reusables/pages/sidebar-pages.md +++ b/translations/pt-BR/data/reusables/pages/sidebar-pages.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %} +{% ifversion fpt or ghes > 3.4 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. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Aba de páginas na barra lateral esquerda](/assets/images/help/pages/pages-tab.png) diff --git a/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md index 050f0be94f..0f74abf51c 100644 --- a/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md +++ b/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md @@ -1,4 +1,4 @@ -É possível programar um fluxo de trabalho para ser executado em horários de UTC específicos usando a [sintaxe de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Fluxos de trabalho agendados executados no último commit no branch padrão ou branch de base. O intervalo mais curto que você pode executar fluxos de trabalho agendados é a cada 15 minutos. +É possível programar um fluxo de trabalho para ser executado em horários de UTC específicos usando a [sintaxe de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Fluxos de trabalho agendados executados no último commit no branch padrão ou branch de base. O intervalo mais curto que você pode executar fluxos de trabalho agendados é a cada 5 minutos. Este exemplo aciona o fluxo de trabalho todos os dias às 17:30 e 17:30 UTC: diff --git a/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md index 5eaf9fe7ed..aa2db8b271 100644 --- a/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md +++ b/translations/pt-BR/data/reusables/repositories/navigate-to-security-and-analysis.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. Na barra lateral esquerda, clique em **Security & analysis** (Segurança e análise). ![aba de "Segurança & análise" nas configurações do repositório](/assets/images/help/repository/security-and-analysis-tab.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/repository-branches.md b/translations/pt-BR/data/reusables/repositories/repository-branches.md index a93e602225..2922f65439 100644 --- a/translations/pt-BR/data/reusables/repositories/repository-branches.md +++ b/translations/pt-BR/data/reusables/repositories/repository-branches.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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 %} +{% else %} 1. No menu à esquerda, clique em **Branches**. ![Submenu de opções do repositório](/assets/images/help/repository/repository-options-branch.png) {% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md b/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md index 2e387d66c7..2b9aee5409 100644 --- a/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md +++ b/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta-dry-runs.md b/translations/pt-BR/data/reusables/secret-scanning/beta-dry-runs.md new file mode 100644 index 0000000000..2d3121b0cd --- /dev/null +++ b/translations/pt-BR/data/reusables/secret-scanning/beta-dry-runs.md @@ -0,0 +1,6 @@ + +{% note %} + +**Note:** The dry run feature is currently in beta and subject to change. + +{% endnote %} 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 7db741ea14..88ce4b3829 100644 --- a/translations/pt-BR/data/reusables/user_settings/access_applications.md +++ b/translations/pt-BR/data/reusables/user_settings/access_applications.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 ced72b8186..5c2f9130ac 100644 --- a/translations/pt-BR/data/reusables/user_settings/account_settings.md +++ b/translations/pt-BR/data/reusables/user_settings/account_settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 050370bf13..1969c21932 100644 --- a/translations/pt-BR/data/reusables/user_settings/appearance-settings.md +++ b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md @@ -1,5 +1,5 @@ -{% 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**. +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} +1. Na barra lateral esquerda, clique em **Aparência de {% octicon "paintbrush" aria-label="The paintbrush icon" %}**. {% else %} 1. Na barra lateral de configurações do usuário, clique em **Aparência**. 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 a7c3a03398..90e3bdeb9c 100644 --- a/translations/pt-BR/data/reusables/user_settings/developer_settings.md +++ b/translations/pt-BR/data/reusables/user_settings/developer_settings.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/pt-BR/data/reusables/user_settings/emails.md b/translations/pt-BR/data/reusables/user_settings/emails.md index ede0a651c5..30276c145e 100644 --- a/translations/pt-BR/data/reusables/user_settings/emails.md +++ b/translations/pt-BR/data/reusables/user_settings/emails.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/pt-BR/data/reusables/user_settings/organizations.md b/translations/pt-BR/data/reusables/user_settings/organizations.md index 2e922b6ced..56e71f320f 100644 --- a/translations/pt-BR/data/reusables/user_settings/organizations.md +++ b/translations/pt-BR/data/reusables/user_settings/organizations.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 bba693a256..dfca42af6f 100644 --- a/translations/pt-BR/data/reusables/user_settings/repo-tab.md +++ b/translations/pt-BR/data/reusables/user_settings/repo-tab.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 4518824f63..8c89dbb57f 100644 --- a/translations/pt-BR/data/reusables/user_settings/saved_replies.md +++ b/translations/pt-BR/data/reusables/user_settings/saved_replies.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 642735a0f6..aec1ce067f 100644 --- a/translations/pt-BR/data/reusables/user_settings/security-analysis.md +++ b/translations/pt-BR/data/reusables/user_settings/security-analysis.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/pt-BR/data/reusables/user_settings/security.md b/translations/pt-BR/data/reusables/user_settings/security.md index 5fd1ae50cd..fdc2ac26ab 100644 --- a/translations/pt-BR/data/reusables/user_settings/security.md +++ b/translations/pt-BR/data/reusables/user_settings/security.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) diff --git a/translations/pt-BR/data/reusables/user_settings/ssh.md b/translations/pt-BR/data/reusables/user_settings/ssh.md index 2ba12f8b8c..5122dd314e 100644 --- a/translations/pt-BR/data/reusables/user_settings/ssh.md +++ b/translations/pt-BR/data/reusables/user_settings/ssh.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %} +{% ifversion fpt or ghec or ghes > 3.4 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) 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 GitHub's Privacy Statement and users enabling the connection agree to the GitHub's Terms of Service. +- 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..c8a8983573 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.4 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..7587fc0c4d 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.4 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..30a8d93923 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.4 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-user-account-settings/managing-your-theme-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 5ed66d24b6..586f705ff5 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -22,7 +22,7 @@ shortTitle: 管理主题设置 {% note %} -**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." {% endnote %} 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-java-with-gradle.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index ca3c04e8dc..15b7173f8f 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -69,7 +69,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build ``` @@ -106,7 +106,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Run the Gradle package task - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: -b ci.gradle package ``` @@ -135,7 +135,7 @@ steps: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: build - uses: actions/upload-artifact@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/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md index 58f6227adc..5fabeae91b 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md @@ -56,7 +56,7 @@ shortTitle: Docker 容器操作 ## 创建 Dockerfile -在新的 `hello-world-docker-action` 目录中，创建新的 `Dockerfile` 文件。 Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。 +在新的 `hello-world-docker-action` 目录中，创建新的 `Dockerfile` 文件。 如果您有问题，请确保您的文件名正确大写（使用大写字母 `D` 但不要大写 `f`）。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。 **Dockerfile** ```Dockerfile{:copy} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md index 3952af62a5..e25ab3e0d1 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md @@ -37,7 +37,7 @@ shortTitle: JavaScript 操作 在开始之前，您需要下载 Node.js 并创建公共 {% data variables.product.prodname_dotcom %} 仓库。 -1. Download and install Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}, which includes npm. +1. 下载并安装 Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}，其中包含 npm。 {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %} 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..2e70f1799d 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)。 +您不应使用 `WORKDIR` 在 Dockerfile 中指定入口点。 而应使用绝对路径。 更多信息请参阅 [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..f018198405 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`。 元数据文件中的数据定义操作的输入、输出和主要进入点。 +所有操作都需要元数据文件。 元数据文件名必须是 `action.yml` 或 `action.yaml`。 元数据文件中的数据定义操作的输入、输出和运行配置。 操作元数据文件使用 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。 -### 示例 +### 示例：指定输入 此示例配置两个输入：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` +## 用于 Docker 容器和 JavaScript 操作的 `outputs` **可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。 例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。 如果不在操作元数据文件中声明输出，您仍然可以设置输出并在工作流程中使用它们。 有关在操作中设置输出的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)”。 -### 示例 +### 示例：声明 Docker 容器和 JavaScript 操作的输出 ```yaml outputs: @@ -107,13 +108,13 @@ outputs: ## 用于复合操作的 `outputs` -**可选** `outputs` 使用与 `outputs.` 及 `outputs..description` 相同的参数（请参阅“用于 {% data variables.product.prodname_actions %} 的 +**可选** `outputs` 使用与 `outputs.` 及 `outputs..description` 相同的参数（请参阅“用于 Docker 容器和 JavaScript 操作的 `outputs`”），但也包括 `value` 令牌。

-### 示例 +### 示例：声明复合操作的 outputs {% raw %} @@ -146,17 +147,17 @@ runs: ## `runs` -**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed. +**必要** 指定这是 JavaScript 操作、复合操作还是 Docker 容器操作以及操作的执行方式。 ## 用于 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 %} +### 示例：使用 Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %} @@ -184,9 +185,9 @@ runs: -### `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` 的脚本： @@ -203,7 +204,7 @@ runs: -### `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. @@ -221,7 +222,7 @@ runs: -### `post` +### `runs.post` **可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. @@ -241,7 +242,7 @@ runs: -### `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. @@ -341,6 +342,7 @@ runs: {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %} #### `runs.steps[*].if` @@ -378,6 +380,8 @@ steps: ``` +{% endif %} + #### `runs.steps[*].name` @@ -467,13 +471,13 @@ runs: -## 用于 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 @@ -486,7 +490,7 @@ runs: -### 使用公共 Docker 注册表容器的示例 +### Example: Using public Docker registry container @@ -505,9 +509,9 @@ runs: -### `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. @@ -550,7 +554,7 @@ runs: ### `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). @@ -581,7 +585,7 @@ runs: -#### 示例 +#### Example: Defining arguments for the Docker container {% raw %} @@ -607,7 +611,7 @@ runs: -### 示例 +### Example: Configuring branding for an action @@ -628,7 +632,12 @@ branding: ### `branding.icon` -要使用的 [Feather](https://feathericons.com/) 图标的名称。 +要使用的 [Feather](https://feathericons.com/) 图标的名称。 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 %} + + ## 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/adding-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index b1bd8075ff..52cc87e50c 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -37,19 +37,18 @@ For more information, see "[About self-hosted runners](/github/automating-your-w You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New self-hosted runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -58,19 +57,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %} {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} @@ -86,7 +84,7 @@ You can add self-hosted runners at the organization level, where they can be use New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} @@ -95,8 +93,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise {% data reusables.enterprise-accounts.actions-runners-tab %} 1. Click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -105,11 +102,9 @@ To add a self-hosted runner at the enterprise level of {% data variables.product 1. Click **Add new**, then click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} -{% ifversion ghec or ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -{% endif %} ### Making enterprise runners available to repositories 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/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index dc2789f2cf..3f69732a46 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -46,7 +46,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 创建组时，必须选择用于定义哪些仓库有权访问运行器组的策略。 -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} @@ -61,12 +61,11 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. 在“Self-hosted runners（自托管运行器）”部分，单击 **Add new（新增）**，然后单击 **New group（新组）**。 +1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**. ![添加运行器组](/assets/images/help/settings/actions-org-add-runner-group.png) 1. 输入运行程序组的名称，并分配仓库访问策略。 @@ -95,7 +94,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 创建组时，必须选择用于定义哪些组织有权访问运行器组的策略。 -{% ifversion ghec %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -113,8 +112,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 {% endwarning %} {% data reusables.github-actions.self-hosted-runner-create-group %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} @@ -144,7 +142,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 ## 更改自托管运行器组的访问策略 您可以更新运行器组的访问策略，或重命名运行器组。 -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} 1. 修改访问选项或更改运行器组名称。 @@ -158,8 +156,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 {% endwarning %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} @@ -181,17 +178,18 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 ## 将自托管的运行器移动到组 如果您在注册过程中没有指定运行器组，新的自托管运行器将自动分配到默认组，然后可以移到另一个组。 -{% ifversion ghec or ghes > 3.1 or ghae %} + {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} 1. 在“Runners（运行器）”列表中，单击您要配置的运行器。 2. 选择运行器组下拉菜单。 3. 在“Move runner to group（将运行器移动到组）”中，选择运行器的目的地组。 -{% endif %} -{% ifversion ghes < 3.2 or ghae %} -1. 在设置页面的“Self-hosted runners（自托管运行器）：部分，找到要移动的运行器的当前组，并展开组成员列表。 ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) +{% elsif ghae or ghes < 3.4 %} +1. In the {% ifversion ghes > 3.1 or ghae %}"Runner groups"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) 2. 选中自托管运行器旁边的复选框，然后单击 **Move to group（移动到组）**以查看可用的目的地。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. 要移动运行器，请单击目标组。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} + ## 删除自托管运行器组 自托管运行器在其组被删除时将自动返回到默认组。 @@ -201,8 +199,7 @@ Self-hosted runner groups are used to control access to self-hosted runners. 组 1. 在组列表中，在要删除的组右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 2. 要删除组，请单击 **Remove group（删除组）**。 3. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。 -{% endif %} -{% ifversion ghes < 3.2 or ghae %} +{% elsif ghes < 3.2 %} 1. 在设置页面的“Self-hosted runners（自托管运行器）”部分，找到要删除的组，然后单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 按钮。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. 要删除组，请单击 **Remove group（删除组）**。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-remove.png) 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 https://github.com/octo-org/octo-repo --pat ghp_abcd1234 +``` + +{% 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/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index dc2fcb9f87..27dcfa5717 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -30,20 +30,20 @@ shortTitle: 删除自托管的运行器 要从用户仓库删除自托管的运行器，您必须是仓库所有者。 对于组织仓库，您必须是组织所有者或拥有该仓库管理员的权限。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。 {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## 从组织中删除运行器 {% note %} @@ -57,19 +57,20 @@ shortTitle: 删除自托管的运行器 要从组织删除自托管的运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。 {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghes > 3.3 or ghec %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% else %} +{% elsif ghes < 3.4 or ghae %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner %} {% endif %} + ## 从企业中删除运行器 {% ifversion fpt %} @@ -85,19 +86,17 @@ shortTitle: 删除自托管的运行器 {% endnote %} -{% data reusables.github-actions.self-hosted-runner-reusing %} +To remove a self-hosted runner from an enterprise, you must be an enterprise owner. 建议您也访问自托管的运行器机器。 For information about how to remove a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). -{% ifversion ghec %} -要从企业帐户删除自托管运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 添加自托管运行器的信息，请参阅[企业管理 GitHub Actions API](/rest/reference/enterprise-admin#github-actions)。 +{% data reusables.github-actions.self-hosted-runner-reusing %} +{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% elsif ghae or ghes %} -要在 -{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是企业所有者。 建议您也访问自托管的运行器机器。 +{% elsif ghae or ghes < 3.4 %} {% 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/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 5cdb8720b9..e8637250d7 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -19,13 +19,13 @@ shortTitle: 标签运行器 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} ## 创建自定义标签 -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} 1. 在“Labels（标签）”部分，单击 {% octicon "gear" aria-label="The Gear icon" %}。 1. 在“Find or create a label（查找或创建标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} @@ -34,35 +34,38 @@ shortTitle: 标签运行器 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## 分配标签给自托管的运行器 -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. 要将标签分配给您的自托管运行器，在“Find or create a label（查找或创建标签）”字段中单击标签。 -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. 单击标签以将其分配给您的自托管运行器。 {% endif %} + ## 删除自托管运行器中的自定义标签 -{% ifversion fpt or ghec %} + +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} 1. 在“Find or create a label（查找或创建标签）”字段中，分配的标签使用 {% octicon "check" aria-label="The Check icon" %} 图标来标记。 单击标记的标签以将其从您的自托管运行器取消分配。 -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes < 3.4 %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} 1. 单击分配的标签以将其从您的自托管运行器中删除。 {% data reusables.github-actions.actions-unused-labels %} {% endif %} + ## 使用配置脚本创建和分配标签 您可以使用自托管运行器上的配置脚本创建和分配自定义标签。 例如，此命令将名为 `gpu` 的标签分配给自托管运行器。 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..outputs` | `对象` | 为步骤定义的输出集。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions#outputs)”。 | +| `steps..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..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..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..outputs.` | `字符串` | 特定输出的值。 | 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..88e983d799 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/expressions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/expressions.md @@ -50,12 +50,12 @@ env: 作为表达式的一部分，您可以使用 `boolean`、`null`、`number` 或 `string` 数据类型。 -| 数据类型 | 文字值 | -| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `布尔值` | `true` 或 `false` | -| `null` | `null` | -| `number` | JSON 支持的任何数字格式。 | -| `字符串` | 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. | +| 数据类型 | 文字值 | +| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `布尔值` | `true` 或 `false` | +| `null` | `null` | +| `number` | JSON 支持的任何数字格式。 | +| `字符串` | 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. | #### 示例 @@ -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..env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)
[`jobs..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..strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)
[`jobs..strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)
[`jobs..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)
[`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)
[`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)
[`on..types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)
[on..](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)
[on..paths](/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..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/publishing-packages/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index 3157700133..a27d3bf763 100644 --- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -96,7 +96,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -167,7 +167,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: @@ -246,7 +246,7 @@ jobs: - name: Validate Gradle wrapper uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b - name: Publish package - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@937999e9cc2425eddc7fd62d1053baf041147db7 with: arguments: publish env: {% raw %} 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..5f8c322fbf 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,21 @@ 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)." -| 作用域 | 默认访问
（允许） | 默认访问
（限制） | 复刻的仓库的最大访问权限
| -| ------------------- | ------------------ | ------------------ | ---------------------- | -| 操作 | 读/写 | 无 | 读取 | -| 检查 | 读/写 | 无 | 读取 | -| 内容 | 读/写 | 读取 | 读取 | -| 部署 | 读/写 | 无 | 读取 | -| id-token | 读/写 | 无 | 读取 | -| 议题 | 读/写 | 无 | 读取 | -| 元数据 | 读取 | 读取 | 读取 | -| 包 | 读/写 | 无 | 读取 | -| pull-requests | 读/写 | 无 | 读取 | -| repository-projects | 读/写 | 无 | 读取 | -| security-events | 读/写 | 无 | 读取 | -| 状态 | 读/写 | 无 | 读取 | +| 作用域 | 默认访问
（允许） | 默认访问
（限制） | 复刻的仓库的最大访问权限
| +| -------- | ------------------ | ------------------ | --------------------------------- | +| 操作 | 读/写 | 无 | 读取 | +| 检查 | 读/写 | 无 | 读取 | +| 内容 | 读/写 | 读取 | 读取 | +| 部署 | 读/写 | 无 | read |{% ifversion fpt or ghec %} +| id-token | 读/写 | 无 | read +{% endif %} +| 议题 | 读/写 | 无 | 读取 | +| 元数据 | 读取 | 读取 | 读取 | +| 包 | 读/写 | 无 | 读取 | +{%- 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/security-guides/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md index d8cfa79d92..b029a19ddd 100644 --- a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md @@ -202,6 +202,10 @@ The same principles described above for using third-party actions also apply to {% data reusables.actions.outside-collaborators-internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." {% endif %} +## Using OpenSSF Scorecards to secure workflows + +[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions. + ## 受损运行器的潜在影响 这些部分考虑了当攻击者能够对 {% data variables.product.prodname_actions %} 运行器运行恶意命令时可以采取的一些步骤。 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..bfa0d4d362 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/`. @@ -1101,8 +917,6 @@ on: ```yaml on: push: - types: - - opened branches: - 'releases/**' paths: @@ -1113,7 +927,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 +940,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`): @@ -1144,8 +958,6 @@ on: ```yaml on: push: - types: - - opened branches: - 'releases/**' paths: @@ -1168,7 +980,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` 时运行工作流程。 @@ -1180,9 +992,9 @@ on: ### `发行版` -| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ | -| [`发行版`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | 标记的发行版中的最新提交 | 发行版标记 | +| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------- | +| [`发行版`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published`
- `unpublished`
- `created`
- `edited`
- `deleted`
- `prereleased`
- `released` | 标记的发行版中的最新提交 | Tag ref of release `refs/tags/` | {% note %} @@ -1220,7 +1032,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 +1183,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..cb5565b451 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 %} ## `权限` @@ -865,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: @@ -1008,7 +973,7 @@ For more information about branch, tag, and path filter syntax, see "[`on. | `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | `all/the/branches`

`every/tag` | | `'*feature'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `mona-feature`

`feature`

`ver-10-feature` | | `v2*` | 匹配以 `v2` 开头的分支和标记名称。 | `v2`

`v2.0`

`v2.9` | -| `v[12].[0-9]+.[0-9]+` | 将所有语义版本控制分支和标记与主要版本 1 或 2 匹配 | `v1.10.1`

`v2.0.0` | +| `v[12].[0-9]+.[0-9]+` | 将所有语义版本控制分支和标记与主要版本 1 或 2 匹配. | `v1.10.1`

`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/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 61e750cc30..6afb61b812 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -699,7 +699,7 @@ All Storage tests passed `ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}. -For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/). +For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). ### git-import-detect 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/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md index f3f5dfa2f7..46445e5ec1 100644 --- a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md +++ b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md @@ -35,7 +35,7 @@ shortTitle: 选择集群或 HA ## 备份和灾难恢复 -HA 或集群都不应被视为常规备份的替代品。 更多信息请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)”。 +Neither HA nor Clustering should be considered a replacement for regular backups. 更多信息请参阅“[在设备上配置备份](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)”。 ## 监视 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://` 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..0eaf6791cf 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" %} | | | 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 VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --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 VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER @@ -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 RESOURCE_GROUP -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 | 
git refs delete api
| Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation | | 
git refs update api
| Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation | | 
git repo contents api
| 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 %} | 
merge base into head
| 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)" | | 
pull request branch delete button
| 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)" | | 
pull request branch undo button
| 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..fbfb3ee346 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.4 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..50e80e1834 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.4 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/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index bdf451e3c6..e6cf3e25a0 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -24,7 +24,7 @@ shortTitle: 更新访问凭据 1. 要请求新密码，请访问 {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}。 2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. ![密码重置电子邮件请求对话框](/assets/images/help/settings/password-recovery-email-request.png) 3. 我们将向您发送一封电子邮件，其中含有可让您重置密码的链接。 您必须在收到电子邮件后的 3 小时内单击此链接。 如果您没有收到来自我们的电子邮件，请确保检查垃圾邮件文件夹。 -4. 如果您启用了双重身份验证，将提示您获得 2FA 凭据。 键入您的 2FA 凭据或 2FA 恢复代码之一，然后单击 **Verify（验证）**。 ![双重身份验证提示](/assets/images/help/2fa/2fa-password-reset.png) +4. 如果您启用了双重身份验证，将提示您获得 2FA 凭据。 Type your authentication code or one of your recovery codes and click **Verify**. If you have added a security key to your account, you can insert the key and click **Use security key** instead of typing an authentication code. ![双重身份验证提示](/assets/images/help/2fa/2fa-password-reset.png) 5. 键入新密码，确认新密码，然后单击 **Change password（更改密码）**。 有关创建强密码的帮助，请参阅“[创建强密码](/articles/creating-a-strong-password)” {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} ![密码恢复框](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 78721b16ce..bf6ba3db75 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -20,7 +20,10 @@ shortTitle: 使用 2FA 找回帐户 {% warning %} -**警告**：{% data reusables.two_fa.support-may-not-help %} +**警告**： + +- {% data reusables.two_fa.support-may-not-help %} +- {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} @@ -28,12 +31,21 @@ shortTitle: 使用 2FA 找回帐户 ## 使用双因素身份验证恢复代码 -使用您的恢复代码之一自动重新进入您的帐户。 您可能已将恢复代码保存到密码管理器或计算机的下载文件夹中。 恢复代码的默认文件名为 `github-recovery-codes.txt`。 有关恢复代码的更多信息，请参阅“[配置双因素身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)”。 +使用您的恢复代码之一自动重新进入您的帐户。 您可能已将恢复代码保存到密码管理器或计算机的下载文件夹中。 恢复代码的默认文件名为 `github-recovery-codes.txt`。 有关恢复代码的更多信息，请参阅“[配置双因素身份验证恢复方法](/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. 在“Having Problems?（有问题？）”下，单击 **Enter a two-factor recovery code（输入双重恢复代码）**。 ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %} -2. 在 2FA 页面上的“Don't have your phone?（没有您的电话？）”下，单击 **Enter a two-factor recovery code（输入双因素恢复代码）**。 ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -3. 输入恢复代码之一，然后单击 **Verify（验证）**。 ![输入恢复代码的字段和验证按钮](/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. 在 2FA 页面上的“Don't have your phone?（没有您的电话？）”下，单击 **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. 输入恢复代码之一，然后单击 **Verify（验证）**。 + + ![输入恢复代码的字段和验证按钮](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) {% ifversion fpt or ghec %} ## 使用后备号码进行身份验证 @@ -43,38 +55,52 @@ shortTitle: 使用 2FA 找回帐户 ## 使用安全密钥进行身份验证 -如果您使用安全密钥配置双重身份验证，则可以使用安全密钥作为辅助身份验证方法来自动重新获得对帐户的访问权限。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。 +如果您使用安全密钥配置双重身份验证，则可以使用安全密钥作为辅助身份验证方法来自动重新获得对帐户的访问权限。 更多信息请参阅“[配置双重身份验证](/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 %} ## 使用经过验证的设备、SSH 令牌或个人访问令牌进行身份验证 -如果您知道 {% data variables.product.product_name %} 密码但无法访问双重身份验证凭据，或没有双重身份验证恢复代码，则可以将一次性密码发送到经验证的电子邮件地址，以开始验证过程，重新获得对帐户的访问权限。 +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 %} -**注**：出于安全原因，使用一次性密码验证来重新获得帐户访问权限可能需要 3-5 个工作日。 在此期间提交的其他请求将不予审查。 +**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time. {% endnote %} 在这 3-5 天的等待期内，您随时可以使用双重身份验证凭据或双重身份验证恢复代码重新获得对帐户的访问权限。 -1. 输入您的用户名和密码以提示身份验证。 如果您不知道 {% data variables.product.product_name %} 密码，将无法生成一次性密码。 -2. 在“Having Problems?（有问题？）”下，单击 **Can't access your two factor device or valid recovery codes?（无法访问双重设备或有效的恢复代码？）**。 ![没有 2fa 设备或恢复码时的链接](/assets/images/help/2fa/no-access-link.png) -3. 单击 **I understand, get started（我理解，开始）**请求重置身份验证设置。 ![重置身份验证设置按钮](/assets/images/help/2fa/reset-auth-settings.png) -4. 单击 **Send one-time password（发送一次性密码）**向与您的帐户关联的所有电子邮件地址发送一次性密码。 ![发送一次性密码按钮](/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. ![一次性密码字段](/assets/images/help/2fa/one-time-password-field.png) -6. 单击 **Verify email address（验证电子邮件地址）**。 -7. 选择替代验证因素。 +1. 输入您的用户名和密码以提示身份验证。 + + {% 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. 单击 **I understand, get started（我理解，开始）**请求重置身份验证设置。 + + ![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. 单击 **Verify email address（验证电子邮件地址）**。 + + ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png) +1. 选择替代验证因素。 - 如果您之前已经使用当前设备登录此帐户，并且想使用该设备进行验证，请单击 **Verify with this device（使用此设备进行验证）**。 - 如果您之前已在此帐户上设置 SSH 密钥，并且想使用此 SSH 密钥进行验证，请单击 **SSH key（SSH 密钥）**。 - - 如果您之前已经设置个人访问令牌，并且想使用个人访问令牌进行验证，请单击 **Personal access token（个人访问令牌）**。 ![替代验证按钮](/assets/images/help/2fa/alt-verifications.png) -8. {% data variables.contact.github_support %} 的成员将在 3-5 个工作日内审查您的请求并给您发送电子邮件。 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。 + - 如果您之前已经设置个人访问令牌，并且想使用个人访问令牌进行验证，请单击 **Personal access token（个人访问令牌）**。 + + ![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 three business days. 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。 {% endif %} - -## 延伸阅读 - -- "[关于双重身份验证](/articles/about-two-factor-authentication)" -- "[配置双重身份验证](/articles/configuring-two-factor-authentication)" -- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)" -- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。 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-github-actions/about-billing-for-github-actions.md b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index e1a1f1aa70..4d398cf069 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -76,7 +76,7 @@ shortTitle: GitHub Actions 的计费 ### 样品分钟数成本计算 -For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. +For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. - 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD). - 3,000 Linux minutes at $0.008 USD per minute = $24 USD. 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 --- - {% 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 --- - + {% 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 --- - + {% 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 --- - + 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 --- - {% 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 --- - {% 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 --- - {% 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 --- - + {% 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 --- - 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 --- - + {% 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 --- - 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 --- - + {% 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 --- - + {% 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 <database> --format=<format> \ | Option | Required | Usage | |--------|:--------:|-----| | `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. | -| `` | | 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 `//codeql/qlpacks/codeql-/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 %}. +| `` | | 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 `//qlpacks/codeql/-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 %}. | `--format` | {% 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)." | `--output` | {% 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 %} | `--sarif-category` | {% 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 --- - {% 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 --- - 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 --- - + {% 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 --- - {% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} diff --git a/translations/zh-CN/content/code-security/getting-started/github-security-features.md b/translations/zh-CN/content/code-security/getting-started/github-security-features.md index f9afc594a9..dd984cf9de 100644 --- a/translations/zh-CN/content/code-security/getting-started/github-security-features.md +++ b/translations/zh-CN/content/code-security/getting-started/github-security-features.md @@ -83,6 +83,12 @@ Automatically detect tokens or credentials that have been checked into a reposit 在合并拉取请求之前显示依赖项更改的全部影响以及任何有漏洞版本的详情。 更多信息请参阅“[关于依赖项审查](/code-security/supply-chain-security/about-dependency-review)”。 {% endif %} +{% ifversion ghec or ghes > 3.1 %} +### 安全概述 + +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 %} + ## 延伸阅读 - “[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products)” - "[{% data variables.product.prodname_dotcom %} 语言支持](/github/getting-started-with-github/github-language-support)" 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..d27d4e08ce 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 @@ -36,7 +36,7 @@ You can create a default security policy that will display in any of your organi {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. 1. Click your profile photo, then click **Organizations**. 2. Click **Settings** next to your organization. @@ -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. | ------------------------- | ----------------------- | | topic:TOPIC-NAME | 显示分类为 *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..1401e0a134 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 %} @@ -30,11 +30,17 @@ shortTitle: Use Dependabot with actions {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently. -对于 {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) 使用 `pull_request`、`pull_request_review`、`pull_request_review_comment` 和 `push` 事件发起的工作流程，适用以下限制： +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply: +{% endif %} - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %} - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5792 %} +For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available. +{% endif %} + 更多信息请参阅“[保持 GitHub Actions 和工作流程安全：阻止 pwn 请求](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)”。 {% ifversion fpt or ghec or ghes > 3.3 %} @@ -62,13 +68,13 @@ jobs: {% endraw %} -更多信息请参阅“[修改 GITHUB_TOKEN 的权限](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)”。 +For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)." ### 访问密钥 -When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. 更多信息请参阅“[管理 Dependabot 的加密密码](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)”。 +When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)". -{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. 更多信息请参阅“[加密密码](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)”。 +{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)." If you have a workflow that will be triggered by {% data variables.product.prodname_dependabot %} and also by other actors, the simplest solution is to store the token with the permissions required in an action and in a {% data variables.product.prodname_dependabot %} secret with identical names. Then the workflow can include a single call to these secrets. If the secret for {% data variables.product.prodname_dependabot %} has a different name, use conditions to specify the correct secrets for different actors to use. For examples that use conditions, see "[Common automations](#common-dependabot-automations)" below. 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/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 8b835ed644..9a41ccbd2a 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -58,7 +58,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md index 6d2de3a534..f0e5dc57aa 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md @@ -46,8 +46,6 @@ There are three reasons why an alert may have no pull request link: If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert. -![{% data variables.product.prodname_dependabot %} alert showing the error that blocked the creation of a pull request](/assets/images/help/dependabot/dependabot-security-update-error.png) - ## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %} When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab. diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 2e0ad140d1..4a967cf2fb 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -103,17 +103,17 @@ Since {% data variables.product.prodname_dependabot %} uses curated data in the {% ifversion fpt or ghec %} ## Does each dependency vulnerability generate a separate alert? -When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability. +When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, that is, the number of dependencies with vulnerabilities, not the number of vulnerabilities. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png) +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. -When you click to display the alert details, you can see how many vulnerabilities are included in the alert. +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png) +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} ## Further reading diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 5cc2ff8d17..4f6be9e0d5 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -25,7 +25,7 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. 您可以选择下拉菜单对警报列表进行排序，并且可以单击特定警报以获取更多详细信息。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。 +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。 {% ifversion fpt or ghec or ghes > 3.2 %} 您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)“。 @@ -37,11 +37,26 @@ Your repository's {% data variables.product.prodname_dependabot_alerts %} tab l ## 关于仓库中有漏洞的依赖项的更新 {% data variables.product.product_name %} 在检测到您的代码库正在使用具有已知漏洞的依赖项时会生成 {% data variables.product.prodname_dependabot_alerts %}。 对于启用了 {% data variables.product.prodname_dependabot_security_updates %} 的仓库，当 {% data variables.product.product_name %} 在默认分支中检测到有漏洞的依赖项时，{% data variables.product.prodname_dependabot %} 会创建拉取请求来修复它。 拉取请求会将依赖项升级到避免漏洞所需的最低安全版本。 + +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. The available filters are repository (for example, `repo:my-repository`), package (for example, `package:django`), ecosystem (for example, `ecosystem:npm`), manifest (for example, `manifest:webwolf/pom.xml`), state (for example, `is:open`), and whether an advisory has a patch (for example, `has: patch`). + +Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %} {% endif %} ## 查看和更新有漏洞的依赖项 -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-dependabot-alerts %} +1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png) +1. Click the alert that you would like to view. ![在警报列表中选择的警报](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png) +1. 查看漏洞的详细信息以及包含自动安全更新的拉取请求（如果有）。 +1. （可选）如果还没有针对该警报的 {% data variables.product.prodname_dependabot_security_updates %} 更新，要创建拉取请求以解决该漏洞，请单击 **Create {% data variables.product.prodname_dependabot %} security update（创建 Dependabot 安全更新）**。 ![创建 {% data variables.product.prodname_dependabot %} 安全更新按钮](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) +1. 当您准备好更新依赖项并解决漏洞时，合并拉取请求。 {% data variables.product.prodname_dependabot %} 提出的每个拉取请求都包含可用于控制 {% data variables.product.prodname_dependabot %} 的命令的相关信息。 更多信息请参阅“[管理依赖项更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。 +1. （可选）如果警报正在修复、不正确或位于未使用的代码中，请选择“Dismiss（忽略）”，然后单击忽略警报的原因。 ![选择通过 "Dismiss（忽略）"下拉菜单忽略警报的原因](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) + +{% elsif ghes = 3.3 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} @@ -51,7 +66,7 @@ Your repository's {% data variables.product.prodname_dependabot_alerts %} tab l 1. 当您准备好更新依赖项并解决漏洞时，合并拉取请求。 {% data variables.product.prodname_dependabot %} 提出的每个拉取请求都包含可用于控制 {% data variables.product.prodname_dependabot %} 的命令的相关信息。 更多信息请参阅“[管理依赖项更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。 1. （可选）如果警报正在修复、不正确或位于未使用的代码中，请选择“Dismiss（忽略）”，然后单击忽略警报的原因。 ![选择通过 "Dismiss（忽略）"下拉菜单忽略警报的原因](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) -{% elsif ghes > 3.0 or ghae-issue-4864 %} +{% elsif ghes = 3.1 or ghes = 3.2 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} 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..0956aede41 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[1] | 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`* | -{%- ifversion fpt or ghes > 3.3 %} +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} | +{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} | 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..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 = *_CONTAINER_REGISTRY_USER = -*_container_REGISTRY_PASSWORD = +*_CONTAINER_REGISTRY_PASSWORD = ``` 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 = *_CONTAINER_REGISTRY_USER = AWS -*_container_REGISTRY_PASSWORD = +*_CONTAINER_REGISTRY_PASSWORD = ``` 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/reporting-abuse-or-spam.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md index 89bcf4cde1..74c583d24e 100644 --- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md +++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md @@ -21,6 +21,8 @@ You can report users that have violated {% data variables.product.prodname_dotco If reported content is enabled for a public repository, you can also report content directly to repository maintainers. +Users in India can contact GitHub's Grievance Officer for India [here](https://support.github.com/contact/india-grievance-officer). + ## Reporting a user {% data reusables.profile.user_profile_page_navigation %} 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 +--- + + +{% 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/building-oauth-apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 1f8746b197..c74337bd71 100644 --- a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -293,10 +293,10 @@ Accept: application/xml 可选的 `redirect_uri` 参数也可用于本地主机 URL。 如果应用程序指定 URL 和端口，授权后，应用程序用户将被重定向到提供的 URL 和端口。 `redirect_uri` 不需要匹配应用程序回调 url 中指定的端口。 -对于 `http://localhost/path` 回调 URL，您可以使用此 `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 ``` ## 为 OAuth 应用程序创建多个令牌 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 ` 命令指示 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//upgrade// ``` 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..605b0a35f5 --- /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 %} 集成 + +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 您还可以执行关闭或打开议题等活动，并在不离开 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, discussions, releases, deployment reviews and deployment statuses. 您也可以执行一些活动，如关闭或打开议题、评论您的议题和拉取请求，以及提供丰富的议题和拉取请求引用而不离开 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/getting-started-with-git/managing-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md index 3da91c787d..d3496d0140 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -195,6 +195,8 @@ $ git remote -v `git remote rm` 命令使用一个参数： * 远程名称，例如 `destination` +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. + ## 示例 以下示例假设您[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，即推荐使用的方法。 @@ -217,7 +219,7 @@ $ git remote -v {% warning %} -**注**：`git remote rm` 不会从服务器中删除远程仓库。 它只是从本地仓库中删除远程及其引用。 +**Note**: `git remote rm` does not delete the remote repository from the server. 它只是从本地仓库中删除远程及其引用。 {% endwarning %} 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/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md index c8b27e59df..0231b06a5a 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md @@ -36,10 +36,31 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **Security overview** - Review the security configuration and alerts for an 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 %} +{% ifversion fpt or ghec %} +The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. + +{% ifversion fpt %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | +| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | +| Code scanning | Yes | No | Yes | +| Secret scanning | Yes **(limited functionality only)** | No | Yes | +| Dependency review | Yes | No | Yes | +{% endif %} +{% ifversion ghec %} +| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | +| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | +| Code scanning | Yes | No | Yes | +| Secret scanning | Yes **(limited functionality only)** | No | Yes | +| Dependency review | Yes | No | Yes | +| Security overview | No | No | Yes | +{% endif %} + +{% endif %} + For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion fpt or ghec %} -{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} {% ifversion ghes or ghec %} @@ -59,9 +80,9 @@ The site administrator must enable {% data variables.product.prodname_advanced_s Once your system is set up, you can enable and disable these features at the organization or repository level. {%- elsif ghec %} -For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. +For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {%- elsif ghae %} You can enable and disable these features at the organization or repository level. 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: Ctrl+K or Ctrl+Alt+K - Mac: Command+K or Command+Option+K +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 Ctrl+Shift+K (Windows and Linux) or Command+Shift+K (Mac) to open the command palette in command mode. If you already have the command palette open, press > 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 Ctrl+Shift+K (Windows and Linux) or Command+Shift+K (Mac). If you already have the command palette open, press > 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 Enter 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: Esc or Ctrl+K (Windows and Linux) Command+K (Mac) - Command mode: Esc or Ctrl+Shift+K (Windows and Linux) Command+Shift+K (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 | 键盘快捷键 | 描述 | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s 或 / | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 | -| g n | 转到您的通知。 更多信息请参阅{% 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 %}”。 | -| esc | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 | +| S 或 / | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 | +| G N | 转到您的通知。 更多信息请参阅{% 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 %}”。 | +| Esc | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 | {% if command-palette %} -controlk or commandk | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Ctlaltk or ⌘optionk. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +Command+K (Mac) or
Ctrl+K (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with Command+Option+K or Ctrl+Alt+K. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} ## 仓库 | 键盘快捷键 | 描述 | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | 转到 **Code（代码）**选项卡 | -| g i | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。 | -| g p | 转到 **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 %} -| g a | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %} -| g b | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 | -| g w | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion fpt or ghec %} -| g g | 转到 **Discussions（讨论）**选项卡。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。{% endif %} +| G C | 转到 **Code（代码）**选项卡 | +| G I | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。 | +| G P | 转到 **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 %} +| G A | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %} +| G B | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 | +| G W | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion fpt or ghec %} +| G G | 转到 **Discussions（讨论）**选项卡。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。{% endif %} ## 源代码编辑 -| 键盘快捷键 | 描述 | -| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} -| . | 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 %} -| control b 或 command b | 插入 Markdown 格式用于粗体文本 | -| control i 或 command i | 插入 Markdown 格式用于斜体文本 | -| control k 或 command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %} -| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | -| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list | -| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %} -| e | 在 **Edit file（编辑文件）**选项卡中打开源代码文件 | -| control f 或 command f | 开始在文件编辑器中搜索 | -| control g 或 command g | 查找下一个 | -| control shift g or command shift g | 查找上一个 | -| control shift f or command option f | 替换 | -| control shift r or command shift option f | 全部替换 | -| alt g | 跳至行 | -| control z 或 command z | 撤消 | -| control y 或 command y | 重做 | -| command shift p | 在 **Edit file（编辑文件）** 与 **Preview changes（预览更改）**选项卡之间切换 | -| control s 或 command s | 填写提交消息 | +| 键盘快捷键 | 描述 | +| ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} +| . | 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 %} +| Command+B (Mac) or
Ctrl+B (Windows/Linux) | 插入 Markdown 格式用于粗体文本 | +| Command+I (Mac) or
Ctrl+I (Windows/Linux) | 插入 Markdown 格式用于斜体文本 | +| Command+K (Mac) or
Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %} +| Command+Shift+7 (Mac) or
Ctrl+Shift+7 (Windows/Linux) | Inserts Markdown formatting for an ordered list | +| Command+Shift+8 (Mac) or
Ctrl+Shift+8 (Windows/Linux) | Inserts Markdown formatting for an unordered list | +| Command+Shift+. (Mac) or
Ctrl+Shift+. (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %} +| E | 在 **Edit file（编辑文件）**选项卡中打开源代码文件 | +| Command+F (Mac) or
Ctrl+F (Windows/Linux) | 开始在文件编辑器中搜索 | +| Command+G (Mac) or
Ctrl+G (Windows/Linux) | 查找下一个 | +| Command+Shift+G (Mac) or
Ctrl+Shift+G (Windows/Linux) | 查找上一个 | +| Command+Option+F (Mac) or
Ctrl+Shift+F (Windows/Linux) | 替换 | +| Command+Shift+Option+F (Mac) or
Ctrl+Shift+R (Windows/Linux) | 全部替换 | +| Alt+G | 跳至行 | +| Command+Z (Mac) or
Ctrl+Z (Windows/Linux) | 撤消 | +| Command+Y (Mac) or
Ctrl+Y (Windows/Linux) | 重做 | +| Command+Shift+P | 在 **Edit file（编辑文件）** 与 **Preview changes（预览更改）**选项卡之间切换 | +| Command+S (Mac) or
Ctrl+S (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 | 键盘快捷键 | 描述 | | ------------ | --------------------------------------------------------------------------------------- | -| t | 激活文件查找器 | -| l | 跳至代码中的某一行 | -| w | 切换到新分支或标记 | -| y | 将 URL 展开为其规范形式。 更多信息请参阅“[获取文件的永久链接](/articles/getting-permanent-links-to-files)”。 | -| i | 显示或隐藏有关差异的评论。 更多信息请参阅“[评论拉取请求的差异](/articles/commenting-on-the-diff-of-a-pull-request)”。 | -| a | 在差异上显示或隐藏注释 | -| b | 打开追溯视图。 更多信息请参阅“[跟踪文件中的更改](/articles/tracing-changes-in-a-file)”。 | +| T | 激活文件查找器 | +| L | 跳至代码中的某一行 | +| W | 切换到新分支或标记 | +| Y | 将 URL 展开为其规范形式。 更多信息请参阅“[获取文件的永久链接](/articles/getting-permanent-links-to-files)”。 | +| I | 显示或隐藏有关差异的评论。 更多信息请参阅“[评论拉取请求的差异](/articles/commenting-on-the-diff-of-a-pull-request)”。 | +| A | 在差异上显示或隐藏注释 | +| B | 打开追溯视图。 更多信息请参阅“[跟踪文件中的更改](/articles/tracing-changes-in-a-file)”。 | ## 评论 -| 键盘快捷键 | 描述 | -| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| control b 或 command b | 插入 Markdown 格式用于粗体文本 | -| control i 或 command i | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %} -| control e 或 command e | 在行内插入代码或命令的 Markdown 格式{% endif %} -| control k 或 command k | 插入 Markdown 格式用于创建链接 | -| control shift p 或 command shift p | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | -| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} -| control enter or command enter | 提交评论 | -| control .，然后 control [已保存回复编号] | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} -| control g 或 command g | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 +| 键盘快捷键 | 描述 | +| ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Command+B (Mac) or
Ctrl+B (Windows/Linux) | 插入 Markdown 格式用于粗体文本 | +| Command+I (Mac) or
Ctrl+I (Windows/Linux) | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %} +| Command+E (Mac) or
Ctrl+E (Windows/Linux) | 在行内插入代码或命令的 Markdown 格式{% endif %} +| Command+K (Mac) or
Ctrl+K (Windows/Linux) | 插入 Markdown 格式用于创建链接 | +| Command+Shift+P (Mac) or
Ctrl+Shift+P (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %} +| Command+Shift+V (Mac) or
Ctrl+Shift+V (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +| Command+Shift+7 (Mac) or
Ctrl+Shift+7 (Windows/Linux) | Inserts Markdown formatting for an ordered list | +| Command+Shift+8 (Mac) or
Ctrl+Shift+8 (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %} +| Command+Enter (Mac) or
Ctrl+Enter (Windows/Linux) | 提交评论 | +| Ctrl+. and then Ctrl+[saved reply number] | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +| Command+Shift+. (Mac) or
Ctrl+Shift+. (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} +| Command+G (Mac) or
Ctrl+G (Windows/Linux) | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 {% endif %} -| r | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 | +| R | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 | + ## 议题和拉取请求列表 -| 键盘快捷键 | 描述 | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | 创建议题 | -| control / 或 command / | 将光标聚焦于议题或拉取请求搜索栏。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| | -| u | 按作者过滤 | -| l | 按标签过滤或编辑标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。 | -| alt 并单击 | 按标签过滤时，排除标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。 | -| m | 按里程碑过滤或编辑里程碑。 更多信息请参阅“[按里程碑过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-milestone)”。 | -| a | 按受理人过滤或编辑受理人。 更多信息请参阅“[按受理人过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-assignees)”。 | -| o 或 enter | 打开议题 | +| 键盘快捷键 | 描述 | +| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | 创建议题 | +| Command+/ (Mac) or
Ctrl+/ (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)."| | +| U | 按作者过滤 | +| L | 按标签过滤或编辑标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。 | +| Alt 并单击 | 按标签过滤时，排除标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。 | +| M | 按里程碑过滤或编辑里程碑。 更多信息请参阅“[按里程碑过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-milestone)”。 | +| A | 按受理人过滤或编辑受理人。 更多信息请参阅“[按受理人过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-assignees)”。 | +| O or Enter | 打开议题 | ## 议题和拉取请求 -| 键盘快捷键 | 描述 | -| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| q | 请求审查者。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review/)”。 | -| m | 设置里程碑。 更多信息请参阅“[将里程碑与议题及拉取请求关联](/articles/associating-milestones-with-issues-and-pull-requests/)”。 | -| l | 应用标签。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests/)”。 | -| a | 设置受理人。 更多信息请参阅“[分配议题和拉取请求到其他 {% data variables.product.company_short %} 用户](/articles/assigning-issues-and-pull-requests-to-other-github-users/)”。 | -| cmd + shift + p 或 control + shift + p | 在 **Write（撰写）**和 **Preview（预览）**选项卡之间切换{% ifversion fpt or ghec %} -| alt 并单击 | 从任务列表创建议题时，按住 alt 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在当前选项卡中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。 | -| shift 并点击 | 从任务列表创建议题时，按住 shift 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在新选项卡中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。 | -| command 或 control + shift 并点击 | 从任务列表创建议题时，按住 command 或 control + shift 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在新窗口中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。{% endif %} +| 键盘快捷键 | 描述 | +| ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Q | 请求审查者。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review/)”。 | +| M | 设置里程碑。 更多信息请参阅“[将里程碑与议题及拉取请求关联](/articles/associating-milestones-with-issues-and-pull-requests/)”。 | +| L | 应用标签。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests/)”。 | +| A | 设置受理人。 更多信息请参阅“[分配议题和拉取请求到其他 {% data variables.product.company_short %} 用户](/articles/assigning-issues-and-pull-requests-to-other-github-users/)”。 | +| Command+Shift+P (Mac) or
Ctrl+Shift+P (Windows/Linux) | 在 **Write（撰写）**和 **Preview（预览）**选项卡之间切换{% ifversion fpt or ghec %} +| Alt 并单击 | When creating an issue from a task list, open the new issue form in the current tab by holding Alt 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)”。 | +| Shift 并点击 | When creating an issue from a task list, open the new issue form in a new tab by holding Shift 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)”。 | +| Command and click (Mac) or
Ctrl+Shift and click (Windows/Linux) | When creating an issue from a task list, open the new issue form in the new window by holding Command or Ctrl+Shift 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 %} ## 拉取请求中的更改 -| 键盘快捷键 | 描述 | -| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | 在拉取请求中打开提交列表 | -| t | 在拉取请求中打开已更改文件列表 | -| j | 将所选内容在列表中向下移动 | -| k | 将所选内容在列表中向上移动 | -| cmd + shift + enter | 添加一条有关拉取请求差异的评论 | -| alt 并单击 | 通过按下 `alt` 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。{% ifversion fpt or ghes or ghae or ghec %} -| 单击，然后按住 shift 并单击 | 单击一个行号，按住 shift，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。” +| 键盘快捷键 | 描述 | +| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | 在拉取请求中打开提交列表 | +| T | 在拉取请求中打开已更改文件列表 | +| J | 将所选内容在列表中向下移动 | +| K | 将所选内容在列表中向上移动 | +| Command+Shift+Enter | 添加一条有关拉取请求差异的评论 | +| Alt 并单击 | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %} +| Click, then Shift and click | Comment on multiple lines of a pull request by clicking a line number, holding Shift, 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 %} ## 项目板 ### 移动列 -| 键盘快捷键 | 描述 | -| ------------------------------------------------------------------------------------------------- | ----------- | -| enter 或 space | 开始移动聚焦的列 | -| escape | 取消正在进行的移动 | -| enter | 完成正在进行的移动 | -| ← 或 h | 向左移动列 | -| command + ← 或 command + h 或 control + ← 或 control + h | 将列移动到最左侧的位置 | -| → 或 l | 向右移动列 | -| command + → 或 command + l 或 control + → 或 control + l | 将列移动到最右侧的位置 | +| 键盘快捷键 | 描述 | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | +| Enter or Space | 开始移动聚焦的列 | +| Esc | 取消正在进行的移动 | +| Enter | 完成正在进行的移动 | +| ← or H | 向左移动列 | +| Command+← or Command+H (Mac) or
Ctrl+← or Ctrl+H (Windows/Linux) | 将列移动到最左侧的位置 | +| → or L | 向右移动列 | +| Command+→ or Command+L (Mac) or
Ctrl+→ or Ctrl+L (Windows/Linux) | 将列移动到最右侧的位置 | ### 移动卡片 -| 键盘快捷键 | 描述 | -| --------------------------------------------------------------------------------------------------------------------------------- | ------------- | -| enter 或 space | 开始移动聚焦的卡片 | -| escape | 取消正在进行的移动 | -| enter | 完成正在进行的移动 | -| ↓ 或 j | 向下移动卡片 | -| command + ↓ 或 command + j 或 control + ↓ 或 control + j | 将卡片移动到该列的底部 | -| ↑ 或 k | 向上移动卡片 | -| command + ↑ 或 command + k 或 control + ↑ 或 control + k | 将卡片移动到该列的顶部 | -| ← 或 h | 将卡片移动到左侧列的底部 | -| shift + ← 或 shift + h | 将卡片移动到左侧列的顶部 | -| command + ← 或 command + h 或 control + ← 或 control + h | 将卡片移动到最左侧列的底部 | -| command + shift + ← 或 command + shift + h 或 control + shift + ← 或 control + shift + h | 将卡片移动到最左侧列的顶部 | -| → | 将卡片移动到右侧列的底部 | -| shift + → 或 shift + l | 将卡片移动到右侧列的顶部 | -| command + → 或 command + l 或 control + → 或 control + l | 将卡片移动到最右侧列的底部 | -| command + shift + → 或 command + shift + l 或 control + shift + → 或 control + shift + l | 将卡片移动到最右侧列的底部 | +| 键盘快捷键 | 描述 | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | +| Enter or Space | 开始移动聚焦的卡片 | +| Esc | 取消正在进行的移动 | +| Enter | 完成正在进行的移动 | +| ↓ or J | 向下移动卡片 | +| Command+↓ or Command+J (Mac) or
Ctrl+↓ or Ctrl+J (Windows/Linux) | 将卡片移动到该列的底部 | +| ↑ or K | 向上移动卡片 | +| Command+↑ or Command+K (Mac) or
Ctrl+↑ or Ctrl+K (Windows/Linux) | 将卡片移动到该列的顶部 | +| ← or H | 将卡片移动到左侧列的底部 | +| Shift+← or Shift+H | 将卡片移动到左侧列的顶部 | +| Command+← or Command+H (Mac) or
Ctrl+← or Ctrl+H (Windows/Linux) | 将卡片移动到最左侧列的底部 | +| Command+Shift+← or Command+Shift+H (Mac) or
Ctrl+Shift+← or Ctrl+Shift+H (Windows/Linux) | 将卡片移动到最左侧列的顶部 | +| → | 将卡片移动到右侧列的底部 | +| Shift+→ or Shift+L | 将卡片移动到右侧列的顶部 | +| Command+→ or Command+L (Mac) or
Ctrl+→ or Ctrl+L (Windows/Linux) | 将卡片移动到最右侧列的底部 | +| Command+Shift+→ or Command+Shift+L (Mac) or
Ctrl+Shift+→ or Ctrl+Shift+L (Windows/Linux) | 将卡片移动到最右侧列的底部 | ### 预览卡片 | 键盘快捷键 | 描述 | | -------------- | -------- | -| esc | 关闭卡片预览窗格 | +| Esc | 关闭卡片预览窗格 | {% ifversion fpt or ghec %} ## {% data variables.product.prodname_actions %} -| 键盘快捷键 | 描述 | -| -------------------------------------------------------- | ----------------------- | -| command + space 或 control + space | 在工作流程编辑器中，获取对工作流程文件的建议。 | -| g f | 转到工作流程文件 | -| shift + t 或 T | 切换日志中的时间戳 | -| shift + f 或 F | 切换全屏日志 | -| esc | 退出全屏日志 | +| 键盘快捷键 | 描述 | +| ---------------------------------------------------------------------------------------------------- | ----------------------- | +| Command+Space (Mac) or
Ctrl+Space (Windows/Linux) | 在工作流程编辑器中，获取对工作流程文件的建议。 | +| G F | 转到工作流程文件 | +| Shift+T or T | 切换日志中的时间戳 | +| Shift+F or F | 切换全屏日志 | +| Esc | 退出全屏日志 | {% endif %} ## 通知 {% ifversion fpt or ghes or ghae or ghec %} -| 键盘快捷键 | 描述 | -| -------------------- | ----- | -| e | 标记为完成 | -| shift + u | 标记为未读 | -| shift + i | 标记为已读 | -| shift + m | 取消订阅 | +| 键盘快捷键 | 描述 | +| ----------------------------- | ----- | +| E | 标记为完成 | +| Shift+U | 标记为未读 | +| Shift+I | 标记为已读 | +| Shift+M | 取消订阅 | {% else %} -| 键盘快捷键 | 描述 | -| ---------------------------------------- | ----- | -| e、I 或 y | 标记为已读 | -| shift + m | 静音线程 | +| 键盘快捷键 | 描述 | +| -------------------------------------------- | ----- | +| E or I or Y | 标记为已读 | +| Shift+M | 静音线程 | {% endif %} ## 网络图 -| 键盘快捷键 | 描述 | -| ------------------------------------------- | ------ | -| ← 或 h | 向左滚动 | -| → 或 l | 向右滚动 | -| ↑ 或 k | 向上滚动 | -| ↓ 或 j | 向下滚动 | -| shift + ← 或 shift + h | 一直向左滚动 | -| shift + → 或 shift + l | 一直向右滚动 | -| shift + ↑ 或 shift + k | 一直向上滚动 | -| shift + ↓ 或 shift + j | 一直向下滚动 | +| 键盘快捷键 | 描述 | +| ------------------------------------------------------------------------------------------ | ------ | +| ← or H | 向左滚动 | +| → or L | 向右滚动 | +| ↑ or K | 向上滚动 | +| ↓ or J | 向下滚动 | +| Shift+← (Mac) or
Shift+H (Windows/Linux) | 一直向左滚动 | +| Shift+→ (Mac) or
Shift+L (Windows/Linux) | 一直向右滚动 | +| Shift+↑ (Mac) or
Shift+K (Windows/Linux) | 一直向上滚动 | +| Shift+↓ (Mac) or
Shift+J (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. 有些是长而重复的序列。 像下面的示例一样，在培训集的某个地方当然可以找到重复的 `‘

’` 块 ：
![Example repetitions](/assets/images/help/copilot/example_repetitions.png)
这样的建议可能会有所帮助（测试案例、正则表达式）或没有帮助（像本案例，我怀疑）。 但无论如何，它们并不符合我开始调查时所想到的死记硬背学习的想法。 +2. 有些是长而重复的序列。 Like the following example, where the repeated blocks of `‘

’` are of course found somewhere in the training set:
![Example repetitions](/assets/images/help/copilot/example_repetitions.png)
Such suggestions can be helpful (test cases, regular expressions) or not helpful (like this case, I suspect). 但无论如何，它们并不符合我开始调查时所想到的死记硬背学习的想法。 3. 有些是标准库存，如自然数字、质数、股市股票代码或希腊字母：
![希腊字母示例](/assets/images/help/copilot/example_greek.png) -4. 有些是常见的、直接的方式，甚至是普遍的方式，以很少的自然自由度做事。 例如， 下面的中间部分触发了我使用 BeautifulSoup 包解析维基百科列表的标准方法。 事实上， 在 {% data variables.product.prodname_dotcom %} Copilot 的培训数据[5](#footnote5) 中找到的最佳匹配片段使用这种代码解析不同的文章，并继续根据结果做不同的事情。
![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png)
这也不符合我对引文的想法。 这有点像有人说“我要把垃圾拿出来；我很快就会回来的”— 这是事实陈述，不是引文，尽管这句话以前已经说过很多次了。 +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 的培训数据[5](#footnote5) 中找到的最佳匹配片段使用这种代码解析不同的文章，并继续根据结果做不同的事情。
![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png)
这也不符合我对引文的想法。 这有点像有人说“我要把垃圾拿出来；我很快就会回来的”— 这是事实陈述，不是引文，尽管这句话以前已经说过很多次了。 5. 然后还有所有其他情况。 代码或评论中至少有一些特定重叠。 这些是我最感兴趣的，也是我从现在开始要集中精力的。 此存储桶必须有一些边缘案例[6](#footnote6)，并且您的里程可能因您认为应分类的方式而有所不同。 也许你甚至一开始就不同意整套存储桶。 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-community-guidelines.md b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md index 93671db3a5..604c3edecb 100644 --- a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md +++ b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md @@ -22,7 +22,7 @@ GitHub 社区的主要目的是协作处理软件项目。 我们希望人们能 * **包容开放** - 其他协作的经验水平或背景可能与您不同，但这并不意味着他们不能贡献好的想法。 鼓励大家欢迎新的协作者和刚入门的新手。 -* **互相尊重。**粗鲁是正常对话的天敌。 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。 +* **Respect each other** - Nothing sabotages healthy conversation like rudeness. 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。 您可能要发表反对的意见。 没问题。 但请记住，您的批评要对事不对人。 不要说脏话、人身攻击、纠结于帖子的语气而罔顾其实际内容或制造下意识的矛盾。 而应该提供合理的反驳论据，保持友善的对话。 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/github/site-policy/submitting-content-removal-requests.md b/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md index 4f02a715f8..921bbd2c20 100644 --- a/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md +++ b/translations/zh-CN/content/github/site-policy/submitting-content-removal-requests.md @@ -23,3 +23,5 @@ GitHub 商标政策可用于报告涉嫌使用您公司或企业的名称、徽 ## [GitHub 私人信息删除政策](/github/site-policy/github-private-information-removal-policy) GitHub 私人信息删除政策可用于报告私人（机密并且会造成安全风险）的数据，但这些数据不一定受版权或商标保护。 + +Users in India can contact GitHub's Grievance Officer [here](https://support.github.com/contact/india-grievance-officer). diff --git a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md index e9ebc3409d..2972924536 100644 --- a/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md +++ b/translations/zh-CN/content/graphql/overview/about-the-graphql-api.md @@ -12,7 +12,7 @@ topics: ## 概览 -下面是一些帮助您启动和运行 GraphQL API v4 的快速链接： +Here are some quick links to get you up and running with the GraphQL API: * [身份验证](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) * [根端点](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint) @@ -36,9 +36,9 @@ topics: ## GitHub 为什么使用 GraphQL -GitHub 选择将 GraphQL 用于 API v4，因为它可以为我们的集成商提供明显更高的灵活性。 准确定义所需数据—_仅仅_是您所需的数据—的能力是它超越 REST API v3 端点的强大优势。 GraphQL 可用于将多个 REST 请求替换为_单个调用_，以获取您指定的数据。 +GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. GraphQL 可用于将多个 REST 请求替换为_单个调用_，以获取您指定的数据。 -有关 GitHub 为什么移动到 GraphQL 的详细信息，请参阅原始[公告博客文章](https://githubengineering.com/the-github-graphql-api/)。 +For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/). ## 关于 GraphQL 架构引用 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 %} + + +## 允许 {% 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..3a30602e9f --- /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.4 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 %}**. +{% else %} +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..02d3b700b3 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.4 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..e5c3c0753d 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.4 or ghae-issue-5658 %} +{% data reusables.repositories.click-collaborators-teams %} +{% else %} {% 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..8c9dfb369a 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.4 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..94e8b3c7ba 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.4 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 应用程序）**。 +{% else %} {% 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-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index fe929d9881..3d1225948b 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -15,26 +15,37 @@ topics: shortTitle: 限制仓库创建 --- -您可以选择成员是否可以在组织中创建仓库。 If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}. +您可以选择成员是否可以在组织中创建仓库。 {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository. + +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization). +{% endif %} -组织所有者始终可以创建任何类型的仓库。 {% ifversion ghec or ghae or ghes %} -{% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %} +Enterprise owners can restrict the options you have available for your organization's repository creation policy. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。 +{% endif %} {% warning %} -**警告**：此设置仅限制在仓库创建时可用的可见性选项，而不会限制以后更改仓库可见性的能力。 For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." +**警告**：此设置仅限制在仓库创建时可用的可见性选项，而不会限制以后更改仓库可见性的能力。 有关限制更改现有仓库可见性的更多信息，请参阅“[限制组织的仓库可见性更改](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)”。 {% endwarning %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. Under "Repository creation", select one or more options. +5. 在“Repository creation（仓库创建）”下，选择一个或多个选项。 {%- ifversion ghes or ghec or ghae %} ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + + {% note %} + + **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + + {% endnote %} {%- endif %} + 6. 单击 **Save（保存）**。 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..4c1f6a07f8 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.4 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.4 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 %}/OWNER USERNAME:TOKEN 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/about-pull-requests.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index e882b1f808..a15a7a7cdd 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -22,7 +22,7 @@ topics: **注：**在处理拉取请求时，请记住： * 如果操作的是[共享仓库型号](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)，建议对拉取请求使用主题分支。 从任何分支或提交都可发送拉取请求，但如果需要更新提议的更改，则可使用主题分支推送跟进提交。 -* 在推送提交到拉取请求时，请勿强制推送。 Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. +* Be very careful when force pushing commits to a pull request. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on. {% endnote %} 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/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index ef6028cd86..cc39fced48 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -17,7 +17,7 @@ topics: 复刻仓库类似于复制仓库，主要有两点差异： -* 您可以使用拉取请求将更改从用户拥有的复刻提交到原始仓库，也称为*上游*仓库。 +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. * 您可以通过同步复刻与上游仓库，将更改从上游仓库提交到本地复刻。 {% data reusables.repositories.you-can-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 new_url ``` -- 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..902959798e 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.4 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）”中，输入您想要链接到的外部系统的链接。 确保将 `` 保留为引用号的变量。 ![要输入外部系统 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 目前不支持内联脚本或动画。 ``` -例如，如果您的型号的 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 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/billing.md b/translations/zh-CN/content/rest/reference/billing.md index 7d26c46737..e645927dbc 100644 --- a/translations/zh-CN/content/rest/reference/billing.md +++ b/translations/zh-CN/content/rest/reference/billing.md @@ -4,6 +4,7 @@ intro: 'With the Billing API, you can monitor the charges and usage {% data vari versions: fpt: '*' ghec: '*' + ghes: '>=3.4' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md index d903396303..230e3f76b5 100644 --- a/translations/zh-CN/content/rest/reference/enterprise-admin.md +++ b/translations/zh-CN/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 @@ -78,7 +78,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 %} ## Billing {% for operation in currentRestOperations %} 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..b7132b223d 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 -%} @@ -918,6 +921,9 @@ _团队_ {% 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 %} ### 有关“自托管运行器”的权限 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: 了解搜索语法 缩小搜索结果范围的另一种途径是排除特定的子集。 您可以为任何搜索限定符添加 `-` 前缀，以排除该限定符匹配的所有结果。 -| 查询 | 示例 | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| -QUALIFIER | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** 匹配提及 @defunkt 且不在 GitHub 组织仓库中的议题. | +| 查询 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -QUALIFIER | **[`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:/` 可搜索位于仓库根目录级别的文件。 或者，指定目录名称或目录路径以搜索位于该命令或其任何子目录中的文件。 -| 限定符 | 示例 | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) 匹配位于仓库根目录级别且含有 "octocat" 字样的 _readme_ 文件。 | -| path:DIRECTORY | [**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 cgi-bin directory, or in any of its subdirectories. | -| path:PATH/TO/DIRECTORY | [**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 app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) 匹配位于仓库根目录级别且含有 "octocat" 字样的 _readme_ 文件。 | +| path:DIRECTORY | [**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 cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**`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 app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | ## 按语言搜索 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` 限定符。 -| 限定符 | 示例 | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) 匹配 @codertocat 拥有的包 | -| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) 匹配 {% data variables.product.prodname_dotcom %} 组织拥有的包 | +| 限定符 | 示例 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat | +| org:ORGNAME | [**`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: 搜索仓库 您可以根据仓库中代码的语言搜索仓库。 -| 限定符 | 示例 | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) 匹配具有 "rails" 字样、以 JavaScript 编写的仓库。 | +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**`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)”。 -| 限定符 | 示例 | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults)匹配已归类为 "jekyll" 主题的仓库。 | +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**`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:>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:>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:>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:>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)”。 -| 限定符 | 示例 | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) 匹配含有 "resque" 字样、提及 @defunkt 的议题。 | +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | ## 按团队提及搜索 对于您所属的组织和团队，您可以使用 `team` 限定符查找提及该组织内特定团队的议题或拉取请求。 将这些示例名称替换为您的组织和团队的名称以执行搜索。 -| 限定符 | 示例 | -| ------------------------- | ------------------------------------------------------------- | -| team:ORGNAME/TEAMNAME | **team:jekyll/owners** 匹配提及 `@jekyll/owners` 团队的议题。 | -| | **team:myorg/ops is:open is:pr** 匹配提及 `@myorg/ops` 团队的打开拉取请求。 | +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **`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 %} -| 限定符 | 示例 | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| merged:YYYY-MM-DD | [**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 编写的拉取请求。 | +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| merged:YYYY-MM-DD | [**`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/accounts/you-must-know-your-password.md b/translations/zh-CN/data/reusables/accounts/you-must-know-your-password.md new file mode 100644 index 0000000000..f4795c3909 --- /dev/null +++ b/translations/zh-CN/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/translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md index d697ff8f8c..d645231024 100644 --- a/translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md +++ b/translations/zh-CN/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/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..7693927a99 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.4 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..c52188f4f4 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.4 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..1aed5cdf6b 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.4 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 %}**. +{% else %} +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..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/github-token-available-permissions.md b/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md index 4336f18187..0620d64524 100644 --- a/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md +++ b/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md @@ -5,8 +5,8 @@ permissions: actions: read|write|none checks: read|write|none contents: read|write|none - deployments: read|write|none - id-token: read|write|none + deployments: read|write|none{% ifversion fpt or ghec %} + id-token: read|write|none{% endif %} issues: read|write|none discussions: read|write|none packages: read|write|none 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 https://github.com/octo-org/octo-repo --pat ghp_abcd1234 +``` \ 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/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index 5f69552bc6..471c62ea06 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -12,6 +12,6 @@ 2. 在左边栏中，单击 **Enterprise overview（企业概览）**。 3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 2. Navigate to the "Runner groups" settings: - * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %} - * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghec %}, then click the **Runners groups** tab{% endif %}.{% endif %} + * **In an organization**: Click **Actions** in the left sidebar, then click {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}**Runner groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} below it.{% ifversion ghec or ghes or ghae %} + * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies", then click the {% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}**Runners groups**{% elsif ghae or ghes < 3.4 %}**Runners**{% endif %} tab.{% endif %} {% 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..7557c2ad5a 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.4 or ghae-issue-5658 %} +1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**. +{% else %} 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

@@ -75,7 +75,7 @@ The macos-latest label currently uses the macOS 10.15 runner image. macOS Catalina 10.15 @@ -83,6 +83,12 @@ macOS Catalina 10.15
-macos-11 +macos-latest 或 macos-11 -The macos-latest label currently uses the macOS 10.15 runner image. +The macos-latest label currently uses the macOS 11 runner image.
-macos-latest 或 macos-10.15 +macos-10.15
+{% 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 %} Note: 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..2980a65c03 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.4 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**. +{% else %} 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..a42349f5ed 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.4 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 %}**. +{% else %} 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..304c706a7e 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.4 or ghae-issue-5658 %} +1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**. +{% else %} 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..31d188fa73 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.4 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**. +{% else %} 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..b54d899179 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.4 or ghae-issue-5658 %} +1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**. +{% else %} 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..f44d33cd5a 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.4 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..d3a0aa94ee 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.4 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..bcd9a7872b 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.4 or ghae-issue-5658 %} +1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**. +{% else %} 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..9ceaa0a913 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.4 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/actions-scheduled-workflow-example.md b/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md index 6d51ab4287..ba514ece6b 100644 --- a/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md +++ b/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md @@ -1,4 +1,4 @@ -您可以使用 [POSIX cron 语法](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)安排工作流程在特定的 UTC 时间运行。 预定的工作流程在默认或基础分支的最新提交上运行。 您可以运行预定工作流程的最短间隔是每 15 分钟一次。 +您可以使用 [POSIX cron 语法](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)安排工作流程在特定的 UTC 时间运行。 预定的工作流程在默认或基础分支的最新提交上运行。 您可以运行预定工作流程的最短间隔是每 5 分钟一次。 此示例在每天 5:30 和 17:30 UTC 触发工作流程： 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..0afeb7673c 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.4 or ghae-issue-5658 %} +1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**. +{% else %} 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..e32f6b4e31 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.4 or ghae-issue-5658 %} +1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**. +{% else %} 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..a14fb131d9 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.4 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..eeff0867bd 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.4 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..1272ab7619 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.4 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..b27185f75a 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.4 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..acf04e6323 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.4 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..3d87b98068 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.4 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..5f8c0a6b4e 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.4 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..1d2472de6a 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.4 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..aab77e6046 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.4 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..f2c2a73773 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.4 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..2627493a70 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.4 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..3e031b70be 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.4 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 最新的补丁版本。' ghes_release_notes_upgrade_release_only: '📣 这不是 Enterprise Server 的最新版本。' ghes_release_notes_upgrade_patch_and_release: '📣 这不是此版本系列的最新修补版，也不是 Enterprise Server 的最新版本。' + 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 }} 指南'